I found a folder containing the old Windows Entertainment Pack games. I copied it to a USB stick and I can play them on my XP notebook which made me believe they were portable. But when I try them with BartPE I get a "Not a valid Win32 app" which surprised me. What do we add to BartPE to add Win32 support??

I assume you'll need to add 16-bit subsystem support to your PE.

Regards,
Galapo.

I don't understand. Most 16-bit search results from Google are for DOS problems and 16-bit Windows error msg problems. These games are definitely Windows not DOS and the error is about Win 32 not Win 16. I'm confused.

I think you'll get the error message if the OS doesn't support the architecture of the app. That is, you'll get the same error message if you try to run an x64 app in x86 XP.

In your case, I assume they are 16-bit windows apps: https://secure.wikimedia.org/wikipedia/en/w...ertainment_Pack. If that's the case, they require the 16-bit subsystem support to be working in the PE.

Regards,
Galapo.

Ok, Galapo, now I understand. Can you point me to where I can find the subsystem? It's not in Add/Remove programs or in a folder in the Windows folder that I could see. And thank you for your help.

-update-

I just started Jezzball from a command prompt window!! I was thinking these games were Win 98 based but they may go back to Win 3.1!! So by a 16-bit subsystem you mean DOS??

PEBuilder delivers a default plugin "Dos 16-bit support for WinPE".
Did you enable this plugin?

Hi cdob, no skiing this Dec?

Thank you for the plugin reference. No, I do not have it enabled, I don't remember if I ever did, and it appears to add a lot to the ISO. But now that I know what it will take I will try it and see what happens. I'm just not sure Jezzball and the other games deserve the overhead.

That DOS plugin does indeed solve the WEP situation and it only adds 2MB to the ISO, I thought it would be much more. And many of the WEP files are dated 1992!!! Wow!!

Thank you cdob.

No, not this Dec. I crossed 'Dolma La Pass' this year already.

That's pretty new files

Thanks to Galapo for the 16 bit reminder.

Indeed. Thank you Galapo.

You could try to open it in some hex editor to check the header. If it's PE (Portable Executable) file - do not mistake with Preinstallation Environment file, you would see the usual dos stub whitch is shown when you run win32 exe on dos and it's on the first couple of bytes in the target exe. And yes, there're alot exes that are used in dos
Try PEiD, it shows waht application/compiler/packed is used, but it also checks if the file is valid windows executable whitch is the most important.
Teh error may also pop out if the exe is corrupt or there's no such required runtime installed or the architecture isn't supported on it

It's definitely a Windows app.

Not a PE or PA.c app.