would dosbox or any other dos util be able to run inside of winpe7SE? I was able to create the necessary batch files to load all files into the %target_sys% along with the 16 bit executables that launch if they are in a regular dos boot disk. If I launch those commands in command prompt, they are initiated but promptly get a error message that quickly closes out the command prompt within winpe7. The reason for it is that I use those same files to run certain repairs to the MBR belonging to a encrypted drive.
If you're having trouble with your 16bit app, you might try (for a start) adding Sysinternals ProcMon.exe to your build (such that it's on the ramdrive). Fire it up just before you attempt to execute the 16 bit app. Execute the 16 bit app and as soon as it fails, stop logging in ProcMon (the logs can get quite large). Filter out all the *success* entries, and Fast IO Not allowed... etc.. essentially you're looking primarly for your EXE, or it's dependencies not finding what they're looking for ... like *file not found* or *path not found* etc..
If you can, test this as a virual ISO mounted on a VM with a test install of Win 7 / XP... this way you'll be able to grab possibly needed files off of the VM hard drive and drop them into %WinDir% on X drive (ram drive) where the program you're testing can find them. Rinse, lather, repeat... and maybe you'll get your app working. This is essentially how I created this DOS script in the first place. Additional files (that I didn't need, but were present both in XP & Win 7) were added based on what had been added in Smiley's DOS PE script for XP.
TheFuse: Your modification --> you're simply using XP as the source for the DOS files in the PE3.0 Build? Interesting! If so I could (when I get around to it) add a check box to allow this as an alternative way to add DOS to PE3.0.
Edited by FerrariGuy, 28 September 2011 - 11:40 PM.