[javamyster]

I am unable to launch common applications in WinPE such as notepad and regedit. Whenever I try to launch them from the command line I receive the message "The system cannot execute the specified program"


According to Microsoft this is a common result of Group Policies being set to restrict an application in Windows, but I did not find any reference to Windows PE. Possibly this is a limitation of WinPE or I need to edit something?

I was wondering if anyone else has seen this, and/or if there is any know solution.

Thanks

[gosh]

I don't have that problem so either your winpe is corrupted or you're doing something you're not telling us.

-gosh

[scankurban]

Example
One problem;Partition Magic didn't work
One solution:You must add ramdrive your winpe.most programs want temp location

Windows based like a Notepad,Regedit simple programs working if you dont change anything.

Some multi boot managers bypassing blocking winpe systems resources.Check boot configration.

If you change setupreg.hiv records (may be corrupted) rebuild you winpe

[Bachus]

I'm also having some difficulties running programs within WinPE. I either get the error javamyster has mentioned or a "the program is not a valid win32 application" error. I used Bart's PEBuilder to make the WinPE directory and then I've burned that (with some other stuff) with Nero. I'm going to try letting pebuilder make the iso and see if that helps any.

[SlimShady]

I thought the ONLY WAY for BartPE (or as you call it WinPE) to work is let the PEBuilder make the ISO. Because there is a limitation with standard ISO makers/builders.
I was going to do the same thing as you did, but then I read the manual and realized: it's impossible (anyways at the moment I think it is)
Here is what he put on his website:

Quote

Q: What's wrong with the ISO image generated by PE Builder? I cannot view/edit/rebuild it with most ISO utilities/programs...
A: The ISO image created by PE Builder is using the (new) ISO 9660:1999 standard.
Specifications can be found here: http://www.y-adagio.com/public/standards/i...romr/tocont.htm
This new specification says that the length of Directory and File Identifier is limited to 207.
So the file and directory names can be up to 207 characters. Most ISO build/edit programs and operating systems (like Dos) that are based on ISO 9660:1988 do not like those long names and may not work.

Even an ISO 9660:1999 image made by mkisofs v2.01a17 (the best ISO build tool ever) did not boot properly. I had to patch it (v2.01a17-bart) before things worked OK.
Isobuster will view/extract OK

[Bachus]

I guess I'll just have to use mkisofs then...Dang, I didn't want to have to learn its syntax.

Well, using mkisofs fixed part of the problem, but I'm still getting the "not a valid win32 app" crap.

[Bachus]

So no ideas about my problem then?

[larrysilver]

PE does not support 16 bit applications so unlees the app is 32 bit you will get that message

hope that explains the not a valid win32 app

Larry

[gosh]

WinPE uses the same files as xp, why wouldn't it support 16 bit apps?

-gosh

[larrysilver]

they did not include the subsytem for Wow 32 ( not sure if this is the right name) within WinPE it is detailed in the ref.chm included with PE they also note that the 64bit itanium version only runs 64 bit

below is the actual text

The "Windows on Windows 32" (WOW32) subsystem was introduced into Windows NT to allow 16-bit applications to run on the Windows NT 32-bit platform. Similarly, a new 32-bit subsystem called "Windows on Windows 64" (WOW64) has been introduced into Windows XP 64-bit versions. This subsystem provides all the 32-bit Windows services needed for 32-bit applications to run properly. However, the WOW32 subsystem is not included in 32-bit versions of Windows PE, so 16-bit applications will not function. And in 64-bit versions of Windows PE, there is no WOW64 subsystem, so 32-bit applications will also not function.

[prathapml]

SlimShady, on Dec 27 2003, 09:03 PM, said:

I thought the ONLY WAY for BartPE (or as you call it WinPE) to work is let the PEBuilder make the ISO. Because there is a limitation with standard ISO makers/builders.............
Here is what he put on his website:  .................................

Read slimshady's post above for context

Yes, that's actually the reason. I've been using bartPE 3.22 (onwards) with ultraISO 6.50, and (touchwood, thankfully) not faced a single problem. Even tried MS's own cdimage app, but it's not up to the task. UltraISO was able to successfully view,extract,modify,change-boot-sector and all that on my bart's WinPE ISO.

The developers of ultraiso (ezbsystems.com) seem to be a bit short on knowledge of english grammar, but otherwise, the app is totally blemishless.