23 replies to this topic

[stayboogy]

Have fun with this.  This was written in Visual Studio 2015 and is a simple Shell for WinPE that I prefer to anything else I have ever seen or used.

 

You can use my skeleton code to create a shell that will launch any tool that you have added to your PE.  If the tool works, the RunBar will launch it if you provide the needed info to the code.

 

This is for advanced users only.

 

here's a video of the RunBar in action with my own personal build for my WinPE needs.  The skeleton is not as advanced or thorough but it doesn't take much to make it so.

 

https://github.com/stayboogy/RunBar

 

https://youtu.be/wGn7AOD_lFI

 

[stayboogy]

Will this work with an installed Windows? I've been looking for a super lean shell. Right now I use BlackBox and LiteStep.

Can you compile a native x64 binary?

 

yep, it works fine in a full windows environment as well.

 

it can be compiled for native x64 and x86.  x64 release build for the skeleton is in the git repo

[stayboogy]

Will this work with an installed Windows? I've been looking for a super lean shell. Right now I use BlackBox and LiteStep.

Can you compile a native x64 binary?

 

now, i used absolute paths for WinPE to call these few programs, so in order for it to actually open the programs in question, variable paths will have to be used, or absolute paths pointing to C: drive.

 

I suggest downloading Visual Studio 2015 Enterprise from M$ website and giving it a go.  I've left the most important code, which is the method of running an exe through system.diagnostics class mapped to a button click.

Edited by stayboogy, 01 January 2019 - 09:46 PM.

[stayboogy]

Will this work with an installed Windows? I've been looking for a super lean shell. Right now I use BlackBox and LiteStep.

Can you compile a native x64 binary?

 

there is now an x86 and x64 exe in the github, in /bin/arch/release correspondingly

[Wonko the Sane]

Is this .NET based, right?

 

Wonko

[Atari800XL]

Stayboogy, I like your idea, it's actually a bit similar to my idea of using AutoHotkey as a PE "shell". The first time I tried it (a couple of years ago) it really was just for fun, but actually, it works quite well (and I'm using it ever since). Think about it: as long as you have a "persistent" part in your code (Autohotkey.ahk) the shell never "exits", so the shell is kept "alive" (running). Other parts of the code can be used for GUIs like the one in your screenshot, and of course all sorts of other things (I even made a diskpart/ apply GUI and lots of other stuff). Hotkeys for your favourite programs are also easy to create (after all, it's called "AutoHotkey"...)

 

I don't want to soil the topic, but after reading Wonko's post, I just wanted to share that there are other possibilities for simple PE shells, that don't even require extra runtimes or libraries. You don't even need to compile anything, any .ahk code runs as-is!

 

(Just put x:\autohotkey.exe in winpeshl.ini, put the exe with autohotkey.ahk in your wim, make sure this file uses the "#persistent" directive, then call any .ahk file from that. If you use some "find usb letter" code in the main file, this sub file can be located on the usb, which makes for easy testing and editing, without any rebuilds).

[Wonko the Sane]

I don't want to soil the topic, but after reading Wonko's post, I just wanted to share that there are other possibilities for simple PE shells, that don't even require extra runtimes or libraries. You don't even need to compile anything, any .ahk code runs as-is!

 

(Just put x:\autohotkey.exe in winpeshl.ini, put the exe with autohotkey.ahk in your wim, make sure this file uses the "#persistent" directive, then call any .ahk file from that. If you use some "find usb letter" code in the main file, this sub file can be located on the usb, which makes for easy testing and editing, without any rebuilds).

You perfectly interpreted the unwritten part of my post. 

 

Now, if you have made such a small PE menu tool in Auto-Hoykey, is it "public"?

 

Wonko

[slore]

actually, this is not shell, but Launcher.

 

there are a lot things like it but powerful, because developed in years.

 

for developing, it is a good start, but for end user, it needs more improve.

 

 

TrueLaunchBar(http://www.truelaunchbar.com/)

 

 

Dock

 

 

 

Claunch

 

 

 

WinXShell's UI_Launcher(left-bottom one) all the GUI(s) maked by xml+lua script, easy to customize.

 

 

 

this one is real "Shell" which one can show/switch tasks, show tray icons, and has desktop. 

 

 

Others ...

Edited by slore, 03 January 2019 - 03:24 PM.

[stayboogy]

actually, this is not shell, but Launcher.

there are a lot things like it but powerful, because developed in years.

for developing, it is a good start, but for end user, it needs more improve

this one is real "Shell" which one can show/switch tasks, show tray icons, and has desktop.


Others ...

So.... you came by just to deuce on my thread and simple free offering, which i prefer over any of the crap you posted—especially when it’s a dumb idea to want a full desktop environment in pe anyway, total waste of time in fact... great offering on your part

Edited by stayboogy, 04 January 2019 - 05:53 AM.

[stayboogy]

And, windows natively tasks switches with alt tab so nothing special with regards to winx shell since it works in pe natively too...

[slore]

I posted 4 tools, but you only focus on WinXShell.exe.

WinXShell.exe can run only the UIs without full desktop.

 

What about if I only posted the left-bottom UI_Launcher screenshot?

How would you say?

(I can't upload picture here, so I have to link the full UI screenshot what is exist on github.)

 

 

I came by , want to see what your shell to be as I'm  developing the PE Shell,

see what I can learn something from it, but disappointed me.

you either didn't know what is "shell". if you said "Build Your Own WinPE Launcher", I will not reply here.

 

wikipedia:

The Windows shell is the graphical user interface for the Microsoft Windows operating system. Its readily identifiable elements consists of the desktop, the taskbar, the Start menu, the task switcher.

 

 

 

If you want me to comment your "Shell".

yours is too simple, I stated it is good develop start, but needs more improve.

what it is now, why not just run a batch window.

 

echo 1.cmd

echo 2.bootice

echo 3.taskmgr

...

 

+ mouse.exe to select the menu.

 

small, no need complie, easy to config.

Edited by slore, 04 January 2019 - 06:51 AM.

[slore]

And, windows natively tasks switches with alt tab so nothing special with regards to winx shell since it works in pe natively too... 

 

 

and if here are 10 windows you like window UI on other windows?

even it can be miniminize, there block the bottom window.

(I mean taskbar tasks switcher)

[Atari800XL]

Well, I think slore is techically correct with his quoted definition of the "Windows shell".

But isn't the whole point of the "PE shell" (at least in Microsoft's default environment) that you can even use cmd.exe as your "shell" (or setup.exe, autohotkey.exe, etc.)? Cmd.exe is the default ADK PE shell, right?

After all, you decide which shell (program) to use in WinPEshl.ini, don't you?

 

I think we shouldn't attack stayboogy on this shell terminology. I look at it this way: It's great to have choices and alternatives, I think it's too bad Microsoft does nothing to support this "out of the box", so I think it's great that there are so many open-source projects to choose from.

[erwan.l]

My 2 cents in that discussion since I am also a "WinPE hobbyist"

 

I have read no attack from Slore and I believe it is indeed important to make a clear distinction between a shell (as defined by wikipedia) and a launcher.

Lots of ppl make that confusion (including myself).

Slore being an experienced developper who made significant contributions to the WinPE world, it is worth listening what he has to say.

WinXshell (here), IHMO, is probably one of the few "true" WinPE shell alternatives outthere and I would definitely not qualify it as "crap".

 

The point raised by Wonko (.Net) is also worth keeping in mind.

Although there is nothing wrong with .Net (i have been a .net developper for some years), it comes with a price (a framework to be exact) and this is, IMHO, a show stopper when it comes to WinPE.

 

As a whole, it is nice to see new comers, new (open source) initiatives, etc but accepting constructive criticism is a must have in order to progress.

 

Actually, the program name is all fine ("RunBar") but the title of this thread is misleading ("build your own winpe shell").

Replacing the word "shell" by "launch bar" could avoid lenghty discussions around "shell" vs "launcher" and help everyone focus on the software itself

 

I am looking forward to see this initiative develop and possibly take new ideas on board like :

use a dynamic approach based on a ini file where one could easily customize the launcher,

possibly use the icon from the launched binary,

choose horizontal or vertical display,

go full native (i.e kill as many dependencies as possible,

cover all possible WinPE starting with WinPE 2.0, ...

 

Cheers,

Erwan

[slore]

@Atari800XL

 

Thanks for correct me about the "WinPE Shell". In a way, cmd.exe is also shell in PE.

but I never call it as shell indeed.

 

winpeshl.exe is windows PE shell Launcher in my mind. see winpeshl.log.

 

It launchs the shell program wallpaperhost.exe. Microsoft makes it as "REAL" shell in programing in PE.

that's why, we need kill it when you use explorer.exe or winxshell.exe as shell.

 

With my preconceived notions, I real want to see something else(new) about the shell, so I came by,

but this is not what I want to see then replied.

 

 

@erwan.l

Thanks for your cents. I actually didn't wanto to attack someone(what I can gain from it?).

 

Histroy:

I wanted to release WinXShell.exe here first(I didn't know other site before) with explorer addtions topic.

but I can't upload attachments(screenshots, files) even now.

and there was a time reboot.pro service down for weeks.

so it is on other site.

 

but I read both sites normally, I can feel in reboot.pro, people is not active on WinPE now, but BOOT things(what reboot be).

 

so I just check the new topics about WinPE.

 

you can see here is two topics only recently, and both posted by stayboogy. I replied as I do the

answer and suggestion.

 

http://reboot.pro/to...y-key-location/

http://reboot.pro/to...wn-winpe-shell/

 

before is noel's topic about modifying the services.exe, and we finally worked out the MTP support for WinPE in the end of 2018.

 

return to this topic.

 

but stayboogy's reply is real nauseous --- crap, dumb, total waste of time.

 

He didn't real see what's good develop direction on his RunBar. He ignored Wonko's reply.

 

So I want to leave the next words in the topic, because I was total waste of time to do suggestion and tested it in PE.

 

RunBar is a appliaction that when you want to add command items or change paths you need install Visual Studio then recompile it,

It can't read configure file to do it like others.

You can run it in WinPE, give you a message about "the application is wrong(0x0000135), please close it" with very low 135KB memory 

natively. or you can extract your read-only ISO, and rebuild the wim file with add 1000 times bigger size than RunBar's .NET support to run it by yourself.

 

Have fun with this.

 

compare with this great shell, others is totally crap. @stayboogy thanks, I agree with you, THIS  significant shell real give me fun.

[Wonko the Sane]

Hey peeps, why doesn't everyone take a chill pill of sorts?

 

stayboogy did use an improper term (objectively) and an improper framework (subjectively, in my perverted mind).

 

slore did make a *somehow aggressive comment* (objectively), most probably largely due to some language barrier of sorts and proposed (without any reason that I can understand ) a link to a Commercial program and a number of (again subjectively, in my perverted mind) completely meaningless screenshots of other shells or menu launchers or whatever you want to call them

 

Let's get to the usual automotive comparison :

stayboogy posted "Hey peeps look at this sports car" (while posting a golf cart)
slore posted "Hey, that is a golf cart" (and could have well avoided to post several examples of sports cars, including a link to the dealer of one of them)

 

There are cases where a golf cart is more useful than a sports car and cases where a sports car is more useful than a golf cart, but there is nothing bad inherently in either golf carts or sports cars, and conversely no reason to dislike the one or the other or their respective manufacturers.

 

Come on, be nice guys .

 

Wonko

 

P.S. : @Slore: JFYI there is a minimum number of posts (50 if I recall correctly) before you can attach files/images, but if you contact Nuno (via e-mail and NOT via PM) or erwan.l (via PM possibly) and ask nicely, they will promote you to "developer" (or *whatever*) and allow you to upload files and images.

[slore]

HI, Wonko

 

proposed (without any reason that I can understand ) a link to a Commercial program and a number of (again subjectively, in my perverted mind) completely meaningless screenshots of other shells or menu launchers or whatever you want to call them

 

 

>proposed (without any reason that I can understand ), completely meaningless

 

Can not you see the screenshots what are have items, click to startup any applications like his "shell" do?

BUT they don't claim themself as "Shell" but launcher.

AND they can run in WinPE freely, natively.

 

>a link to a Commercial program

 

WinXShell's UI part is created with XML(UI) + lua script(action control), which is open source, use without any limit,

and full customization by userself, and develop any UI they like with scripts.

the shell part is open source in LGPL.

 

I don't know where you see a  Commercial program.

 

as a developer, I saw similar applications I will test them, find out what's the different,

and learn something and improve with source or just binary.

 

the example about sports car+golf cart is not like this topic as I readed.

 

Build your Own IDE, but whom just posted a Editor. 

I posted EmEditor, UltraEdit, notepad++,sublime text...

to show somethings they called Editor, then with Eclipse or Visual Stido screenshots tell him,

Hey they are called IDE.

 

actually, this is not shell, but Launcher.

 

there are a lot things like it but powerful

 

I thought I was clear about this with the screenshots.

 

 

Thanks for the information about attach files/images, funny with this topic I will soon reach it.

I will waste of time to do other crap things like, make printer, Eject USB Storage work in WinPE.

[Wonko the Sane]

I don't know where you see a Commercial program.

The ONLY actual link you posted (besides the screenshot):

actually, this is not shell, but Launcher.

there are a lot things like it but powerful, because developed in years.

for developing, it is a good start, but for end user, it needs more improve.


TrueLaunchBar(http://www.truelaunchbar.com/)

If you prefer you posted four screenshots of four different (alternative) programs, while providing ONLY one link (and ONLY to the first program, which happens to be a Commercial one: https://www.truelaun....com/order.html ).

Besides, as said most probably because of some (BTW perfectly understandable) difficulties with English, you didn't introduce the REASON WHY you posted those screenshots.

Something *like*:
"Here are some examples of other launcher tools that are more complete/mature ..."
would have done nicely.

Unfortunately, as is, your post came out exacty like an automated bot/troll/spammer would have made it:
1) Some text, possibly in incorrect English
2) some pictures
3) only one clickable link, leading to the *whatever* the spammer is promoting.


Wonko

[slore]

 

you didn't introduce the REASON WHY you posted those screenshots.
Something *like*:
would have done nicely.

 

 

"Here are some examples of other launcher tools that are more complete/mature" by your suggestion

"there are a lot things like it but powerful"  by me

 

in my mind, that are exactly same, so I already done what you suggested in my stance, but you didn't read/get (the REASON WHY).

 

Besides, as said most probably because of some (BTW perfectly understandable) difficulties with English

 

there are = here are

a lot = some

things = examples/launcher tools

powerful = more complete/mature

 

in your mind, are they different meaning? if it is true, English is really difficult.

 

 

about the url, because Dock have many MyDock, CairoDock, XXDock...  I just searched a picture for show the launcher,

CLaunch's Home page is gone(I used in PE long time ago), so no URL for it too, I copy screenshots from some user's blog.

 

WinXShell is made by me, I don't want others think I'm pushing my tool, so either it has no URL.

TLB has homepage, and there are a lot of screenshots, I think it is good to see them, so put it URL.

It should have free version. at least some time before as I know.

 

but I mainly want to show the launcher UI on screenshots, the url is just appendant, WHY you focused on it... 

well, different people(country, area, culture ...) see things with his experience.

 

1) Some text, possibly in incorrect English

 

  I wonder automated bots make mistake in spelling ...

Edited by slore, 05 January 2019 - 05:18 PM.

[stayboogy]

Let me just say, some of you are so ridiculous...

1) .net added to PE doesn't make it 1000s times bigger, difference is less than 100mb, and an x64 WinPE with about 12 OC's from the ADK added, and with WOW64 support added, my .wim is right under 500mb. my .wim with all my tools including RunBar is 508mb so...

2) if you don't have 10mb of memory free in PE, or can't afford 10mb of memory use in PE, then your configuration is crap, because with every tool that I have in my .wim RunBar only uses up to about 11mb of memory when you have launched 10+ tools with it and kept those tools running.

3) PE's built with all the non-needed tools so over-marketed here mess up your build more than they help it. most any builds of any PE built with anything I've found here mess with the Windows PATH in such a way that yeah, you might have errors running the builds I linked here in this thread because running the cmd "cmd.exe" might not work, it doesn't in a very well known PE builder found all over this site which i don't feel the need to name specifically here, but, I know what I'm talking about.
I make my own PE's from the ADK and manage them with the dism, I don't need a builder or someone else's work to do so. when a proper build is made, RunBar works perfectly.

4) the reason I made this open source is so that others could build their own shell/launcher, which are not two different things and are not two separate things, tit for tat, silly argument for no reason other than to try to show yourself superior on some message board. This so much better than some shitty batch file. my youtube video is to show that every tool one has programmed to the RunBar can be launched and run all at once and not increase its memory usage by much, not to just load them because that is the RunBar's purpose, so simple minded some seem to be.

5) i don't care about other tools, if i did, i wouldn't have made my own, which is better in my estimation and for my uses since it doesn't need anything other than what Windows already has, which is enough if you know what you're doing and know how to manipulate a .wim without relying on others' very imperfectly made tools.

6) this was simply to share to inspire, not to measure cocks. either be positive, or gtfo. thanks.

Edited by stayboogy, 06 January 2019 - 06:10 AM.

[slore]

rebuild the wim file with add 1000 times bigger size than RunBar's .NET support to run it by yourself.

 

 

 

my Engish maybe bad, but why you both in English and math.

 

1) .net added to PE doesn't make it 1000s times bigger, difference is less than 100mb

 

 

your RunBar is 48kb, 100mb=102400kb, then, 102400kb/48kb = 2133 times bigger.

oh, sorry my math is also bad, I said 1000 times, but even double.

 

I use PE for maintenance system, and reinstall Windows is 100MB~200MB(with NETWORK feature), and enough to use.

and have more usable memory, what your PE is, I don't care.

 

2) if you don't have 10mb of memory free in PE, or can't afford 10mb of memory use in PE, then your configuration is crap

 

as I know, lots people  use 10MB XP PE, <30MB 2003 PE for old machine.

Win7, 8.1 PE is also in less size. for those, then your RunBar is crap, because it can't run for those PE.

even Windows 10 PE, very few PE has .NET framework. you can make PE by ADK.

Do you will help others to add .NET to their PE? add show the clear files/dlls/registy items for those PE?

 

2). RunBar only uses up to about 11mb of memory when you have launched 10+ tools with it and kept those tools running.

 

 

Have you run my posted tools to test it?

 

at less I tested WinXShell.exe.

it is only use 4mb~6mb memory when you have launched 20+ even more tools.

Clauch is more, use <1mb memory on it, even it has powerful configuration.

configuration won't lead more memory usage.

 

so I don't know why you have such superiority feeling about your simple tool.

 

 

3),4), 5),6)  to difficult English for me to read, I can't get the point what you want to say.

 

Windows PATH

the RunBar can be launched and run all at once and not increase its memory usage by much

 

I don't know which one mess the PATH I have posted. they inherit OS's PATH.

I can't feel others increase much memory by launch other programs( by use CreateProcess() API).

I said nothing about open source, I can't understand why you talk about the season.

 

 

 

as you still didn't see what your tool's problem, and what needs to be improved, I have no more to say.

Edited by slore, 06 January 2019 - 07:33 AM.

[Wonko the Sane]

in your mind, are they different meaning? if it is true, English is really difficult.

 

English, like any other language is difficult.

 

Don't take this as an offence , as said i perfectly understand - not being myself a native English speaker - how difficult it can be to speak or write properly in "another" language , but what you originally posted is not English, it is a quick assembly of English words that additionally,. due to the lack of some (needed) parts, like articles, convey the idea of "sloppy".

Noone here is obviously (nor anyone expects someone else to be) a new Shakespeare,  but even in the plainest possible English some forms must be respected, your post looks (to me at least) a lot like a "Me Tarzan, you Jane" (which BTW was never said in a movie):

http://www.thisdayin...n-you-jane.html

 

 

Here is an English translation of your post:

 

actually, this is not shell, but Launcher. = Actually, this is not a shell, but rather a launcher.

there are a lot things like it but powerful, because developed in years. = There are a lot of similar programs, but most of them are more powerful, because they have been developed since a long time (or over the course of several years).

for developing, it is a good start, but for end user, it needs more improve.=As an in-development tool, it is a good start, but before being useful to the end user, it needs to be improved (or needs improvements).

 

Believe me that however (no matter what message you actually wanted to transmit) it is not particularly difficult to read/understand it as having a (as said "aggressive") meaning:

 

 

actually, this is not shell, but Launcher. = you are lying,

there are a lot things like it but powerful, because developed in years. = your project is useless,

for developing, it is a good start, but for end user, it needs more improve.= and not ready for being released.

 

 

About bots/spammers, nowadays they (roughly) work like this:
1) they crawl forums and blogs for certain keywords/topics
2) when they find one that is suitable, they take a snippet from another forum post /blog post that they believe is related and post it

3) adding at the bottom, or editing part of the snippet, the link(s) to the whatever they promote

 

The source of #2 is what it is, and if it has incorrect grammar, or punctuation or both, it remains incorrect, and often this is made more evident because the snippet is taken out of context.

 

Wonko

[erwan.l]

This thread is going nowhere and this is disappointing

 

Initially we had a newcomer (always a good thing), posting a new opensource software (another good thing).

And ideally, this thread should have turned into :

-community feedback as after all this is why developpers post/advertise here

-possible improvements based on the community feedback

 

Unfortunately and obviously now, reading the last author's post, the author does not like criticism which indeed sometimes can be "direct" but also can be misinterpreted/cloumsily expressed due to language matters.

 

Being a developper myself, I confess : yes, i would like everyone to clap with both hands everytime I post a new software.

I would like to hear some "wow!", "amazing!", "you nailed it!" but in reality, the users (and their needs) is what matters and many times I have been posting softwares which had little or no positive feedback and I accepted such feedback - no big deal by the end of the day, my ego did survive and I looked for another fun project.

 

Put in simple words and without any criticism : RunBar is a very minimalist launcher coded in C sharp meant for WinPE.

Some users will definitely appreciate the minimalist/simple approach.

I had myself proposed a similar software in the past so I definitely support/welcome the approach (i.e a  "minimalist launchbar").

 

Now on the dependencies and again, no criticism on my end, just pure facts which I wanted to highlight and possibly discuss in a peacefull way :

-It does require the user to modify and recompile the source code if he wishes to add a new shortcut and therefore to install Visual Studio (a few gigs worth) on his workplace.

-Also because it is C sharp, the user will also have to use ADK or WAIK (and no any other known method discussed on this forum) and will have to add the dotnet packages.

Now again, these dependencies may be fine for some users but I feel this will be a show stopper for many users (not mentionning the fact that you need to know a bit of C sharp).

 

Now, about WinPE size, some may like it "fat", some may like "thin" .

Some may like the "official" way (ADK/WAIK), some may like it the "custom" way.

 

I myself dont want to be hardware and/or software dependent : i want my winpe to be as lightweith as possible as I use it for tshooting reasons only.

I myself dont want to have to install ADK/WAIK and/or VisualStudio on my workplace to generate a WinPE with a launcher as i want to be able to generate my winpe anytime, anywhere

I myself dont want to have to increase hardware (memory or network) on my clients just because of WinPE (250mb is my big max - 200 is better - 500 is unacceptable).

The above are my own personal specs so I appreciate others may see it differently.

 

To conclude, this will be my last post as I feel we are doing round circles here and I read way too much anger and frustration which is definitely not we should be looking for.

Along my feedback (in previous post), I have suggested some possible improvements to the author (which again I feel is what these posts should be about) but they seemed to have been lost in the frustration/anger waves.

 

All I can advise to the author/developer here is a bit of modesty and avoid calling others "ridiculous" or criticizing other people software.

Since you are the one posting/advertising your work, just accept the damn feedback over your software, dont feel you are being personally attacked, and argue gently : you will do youself and your work a favor.

 

To not feed this fire anymore, I will withdraw/unsubscribe from this thread and hope that discussion will cool down.

 

Cheers,

Erwan