Spawn

It turns out the files you download are compressed, and nobody bothered to say anything about that. Just uncompress and place the file in the same folder as the executable.

This is just plain old dos dual boot. It is still not going to read nor can it be loaded on to NTFS partitions.

Why don't you just use ghost 2003 or something dos based. make the cd with the image bootable to a dos environment run ghost and deploy the image. seems to me that Winpe is overkill if all you are going to do is dump an image on the harddrive. Just my humble opinion.

Porting dos applications to winpe Applications that require direct access to the hardware will not work. http://www.msfn.org/board/index.php?showtopic=18936&hl=

looks like someone didn't read the FAQ. check out number 17 & 18 FAQ

it would seem to me that X86 has abandoned this thread. does anyone else have any information that is relative to this. I would appreciate if someone could explain how to tie into the file copy process through the exra.inf. Here is what I know, You can place an aditional entry into the extra.inf [extrafiles] section and it will get processed but, the file has to be in the same directory as the extra.inf and all those files. What I would like to do is to be able to point extra. inf to another directory where the files are located. I tried placing a winntdirectories section in the extra.inf but it didn't work. any ideas?

why would you need ntfs for DOS in winpe. Winpe is supposed to have native support for NTFS. Or maybe I didn't understand it right. there is a guide around this forun on how to get Dos applications to work on winpe. Applications that need direct access to the hardware don't work though. (Protected Mode, same as XP) I think the post is called Porting Dos Applications to Winpe. EDIT Porting Dos Applications on WinPe

No to my knowledge X86 never posted the code anywhere or provided a link to his program or script. He didn't specify how to add to the file copy process ether so... I'm stuck

yes the batch file should copy files to the i386, i386/system, and i386/system32 directories. also, this batch copies files from the os that is currently running. I am using windows xp pro.

very odd did you copy all the needed files? as a test point the batch file to a directory other than your isoroot. something like c:\dospe\. make sure all the files copy properly. I found that if you do not put the trailing backslash on the isoroot path it tries to rename the files as they are copied. so instead of getting the directory structure you get a file called i386 instead of the folder.

I think you are in the wrong forum. this forum is mainly for the M$ version of winpe. if you use BartPE you may get a better response here

could you post it? it would be a great help. I wrote a vbs script to convert the registry part of bartpe inf files but I was unable to figure out how to integrate the sourcediskfiles sections. If I could look at how you do it... maybe I could figure out the soucedisk files conversion. anyway I only know a little vb. if its in some other code it may take me longer to figure out how it works, but I think I can do it. the way I use the config.inf is by making pointers to three inf files that hold the keys for hkcu, hklm/software and hklm/system. i have never used sam and security but I don't think it is any different. the registry sections get sorted and copied to the appropriate file at build time, then mkimg.cmd gets called and you know the rest. I use a batch file process to copy the files for the iso structure since I couldn't figure out how to do it through the inf process. I use this method to keep stuff separate. like pluggins. makes it so much easier to work with programs. I imagine it must be hell to work with an iso structure directly(I got away from it quick). If something fails there is no easy way to undo the work. thats why I like my method, you just add a line to the batch file to integrate the plugin and if it works great, if it doesn't I can easily modify it or remove it. we may be on our way to automation here

Could you elaborate a little? I know how to use the config.inf to add to the registry. Are you suggesting to add to the extra.inf.(that may cause some problems, or result in a very long extra.inf, Or do you think the extra.inf could be used as a pinter to other inf files somehow. I just don't see how.

I don't mean to answer with a question but, does anybody know how to integrate an .inf into the winpe build process? I have converted some Bartpe infs manually but I only know how to integrate the registry build (by putting entries into the winpe inf files such as winpesys.inf used to buld HKLM\System). What I need to know is how to integrate the file copy process. Right now i am copying the files manually.

Which command.com is that? the one that comes with windows XP, or 9x, or dos 6.*? anyway. I tried running the W98 command.com and winpe said "Incorrect Dos Version" and that is all. that is the same message that I get when trying it on a true win xp. Here is the updated reg entries. as far as I can tell only one line chaged. how are you integrating them into your setupreg.hiv? Make sure that you run the batch file to copy the necessary files also. HKLM,"ControlSet001\Control\WOW" HKLM,"ControlSet001\Control\WOW","cmdline",0x00020000, "%SystemRoot%\system32\ntvdm.exe" HKLM,"ControlSet001\Control\WOW","DefaultSeparateVDM",, "no" HKLM,"ControlSet001\Control\WOW","LPT_timeout",, "15" HKLM,"ControlSet001\Control\WOW","size",, "0" HKLM,"ControlSet001\Control\WOW","wowsize",, "16" HKLM,"ControlSet001\Control\WOW","wowcmdline",0x00020000, "%SystemRoot%\system32\ntvdm.exe -a %SystemRoot%\system32\krnl386" HKLM,"ControlSet001\Control\WOW","KnownDLLs",, "comm.drv commdlg.dll ctl3dv2.dll ddeml.dll keyboard.drv lanman.drv mmsystem.dll mouse.drv netapi.dll olecli.dll olesvr.dll pmspl.dll shell.dll sound.drv system.drv toolhelp.dll vga.drv wfwnet.drv win87em.dll winoldap.mod winsock.dll winspool.exe wowdeb.exe timer.drv rasapi16.dll compobj.dll storage.dll ole2.dll ole2disp.dll ole2nls.dll typelib.dll msvideo.dll avifile.dll msacm.dll mciavi.drv mciseq.drv mciwave.drv progman.exe avicap.dll mapi.dll" HKLM,"ControlSet001\Control\WOW","SharedWowTimeout",65537,3600 HKLM,"ControlSet001\Control\WOW","RomFontPointers",1,\ b0,52,00,c0,b0,4a,00,c0,b0,4e,00,c0,b0,60,00,c0,c0,60,00,c0,c0,70,00,c0 HKLM,"ControlSet001\Control\Session Manager\Environment","PATHEXT",,".COM;.EXE;.BAT;.CMD" HKLM,"ControlSet001\Control\VirtualDeviceDrivers" HKLM,"ControlSet001\Control\VirtualDeviceDrivers","VDD",0x00010000, ""

jeffwitt41, ntvdm process did start when I ran Hedit.exe If your application is trying to write to a temp file you might want to copy it to a ramdrive and execute it from there. What application are you trying to run anyway? Maybe I can give it a shot. Also I do have some modifications to the reg entries, well at least one. but I am not at my pc right now and I don't have it with me. I will repost as soon as i can. Zen, I found that the plugin.htm that is included with pebuilder(bartpe) has a lot of information about how plugins' sections are supposed to work. It explains the format that each section is supposed to have. It is kind of brief, but it covers most of the stuff. you might do a search for bartpe plugin for more help.

well I tested it with simple dos applications. choice.com I also used a utility called Hexedit.exe a small hex editor. I will go through the reg entries to see if there is anything wrong.

@Jeffwitt41 hey I sorry I skipped the part about the missing files. I don't know what the deal is with those. I just translated it from Bartpe. reading the pluggin it seems I should have translated some of those as If %filename% exist then copy... sorry about that. but i guess you don't need them. My guess is that since bartpe can be compiled from xp home and windows 2000(I think) then maybe those OS's have those files.

Guess I wasn't Clear. You got most of it right though. Since you are doing the winpesys.inf method. All you need to do is remove these lines from your modified winpesys.inf [DefaultInstall] AddReg = Setupreg.addreg [setupreg.addreg] Notice My Previous post says: add the lines of code after [setupreg.addreg] from the second code window above to winpesys.inf To clarify, Add the lines below [setupreg.addreg] from the second code window above to winpesys.inf but DO NOT include [setupreg.addreg] or anything above it. Just like this HKLM, "ControlSet001\Control\WOW" HKLM, "ControlSet001\Control\WOW", "cmdline",0x00020000, "%SystemRoot%\system32\ntvdm.exe" HKLM, "ControlSet001\Control\WOW", "DefaultSeparateVDM",, "no" HKLM, "ControlSet001\Control\WOW", "LPT_timeout",, "15" HKLM, "ControlSet001\Control\WOW", "size",, "0" HKLM, "ControlSet001\Control\WOW", "wowsize",, "16" HKLM, "ControlSet001\Control\WOW", "wowcmdline",0x00020000, "%SystemRoot%\system32\ntvdm.exe -a %SystemRoot%\system32\krnl386" HKLM, "ControlSet001\Control\WOW", "KnownDLLs",, "comm.drv commdlg.dll ctl3dv2.dll ddeml.dll keyboard.drv lanman.drv mmsystem.dll mouse.drv netapi.dll olecli.dll olesvr.dll pmspl.dll shell.dll sound.drv system.drv toolhelp.dll vga.drv wfwnet.drv win87em.dll winoldap.mod winsock.dll winspool.exe wowdeb.exe timer.drv rasapi16.dll compobj.dll storage.dll ole2.dll ole2disp.dll ole2nls.dll typelib.dll msvideo.dll avifile.dll msacm.dll mciavi.drv mciseq.drv mciwave.drv progman.exe avicap.dll mapi.dll" HKLM, "ControlSet001\Control\WOW", "SharedWowTimeout", 0x00000e10 HKLM, "ControlSet001\Control\WOW", "RomFontPointers",1,\ b0,52,00,c0,b0,4a,00,c0,b0,4e,00,c0,b0,60,00,c0,c0,60,00,c0,c0,70,00,c0 HKLM, "ControlSet001\Control\Session Manager\Environment", "PATHEXT",,".COM;.EXE;.BAT;.CMD" HKLM, "ControlSet001\Control\VirtualDeviceDrivers" HKLM, "ControlSet001\Control\VirtualDeviceDrivers", "VDD",0x00010000, "" By the way the reason you got that message is because If you notice in config.inf it says winpesys.inf.,AddReg. So it is looking for the addreg section. but, this line acts like a pointer that says addreg = setupreg.addreg. and since there is no setupreg.addreg section it fails. so you in fact created an empty setupreg.hiv@Jeffwitt41 I am running Windows XP and using windows xp cd as my source cd.

seems like a lot of waste. why not just buy a cd-rw disk

Ok, The first code window is a batch file. so simply copy and paste it into a text file and remame the file with a .bat extension, for example Ramdisk.bat You have to edit the first line of this batch file to point to your iso set isoroot= c:\winpe\iso\ so modify the part in blue to point to the root of your iso before you make the image As far as the registry part, I don't know how you create you registry files. There are three Main registry files that you can edit SetupReg.hiv --> isoroot\I386\SYSTEM32\ = HKLM\System Default --> isoroot\I386\SYSTEM32\CONFIG = HKCU (current user) Software --> isoroot\I386\SYSTEM32\CONFIG = HKLM\Software Sam and Security I have never used. When you run the batch file(mkimg.cmd ) that makes the winpe iso it creates the above files that later turn into the Winpe registry when you boot it. (with me so far?) There are two ways to edit these files. You can edit them before or after they are created. mkimg.cmd creates the registry by settings stored in config.inf. One line in this file reads setupreg.hiv = .\winpesys.inf,AddReg. This means that it uses winpesys.inf [addreg] section to create the setupreg.hiv file. So, if you add the lines of code after [setupreg.addreg] from the second code window above to winpesys.inf. The next time you run mkimg.cmd to create your iso, the SetupReg.hiv will have those keys added to it. Yes it's confusing, but that's wipe for you. In order to edit the SetupReg.hiv after it has been created you have to import it into the registry. so run regedit click on HKEY_LOCAL_MACHINE go to File and select Load Hive Find the hive file and load it. it will ask you what you want to load it as. You can use any name except for the ones that already exist. eg, software,system. From there you can use a .reg or .inf file to import settings. Use the previous post for further directions Hope it helps, Sorry I coldn't be any clearer. sometimes I get all tied up in the Acronyms myself!

@ CuBie Weird! I just downloaded the reg file you created and imported it and for me it worked perfectly. Are you sure you are logged in with admin rights? Don't know what else it could be.

Worked for me! In fact it works for me every time because i rebuild the registry each time I recreate the ISO. Better luck next time!

I have translated DosPE from BartPE for use with M$ WinPE It worked perfectly for me. ran dos programs just like xp just save the files section with a .bat extension and the Setupreg.addreg section as an .inf extension. Be sure to modify the first line to the path to your ISO in order to copy the needed files to the correct place. set isoroot=c:\winpe\iso\set ToDo=copy if not exist %isoroot%\null md %isoroot%if not exist %isoroot%\i386\null md %isoroot%\i386REM; SystemRoot%ToDo% c:\windows\_default.pif %isoroot%\I386\%ToDo% c:\windows\system.ini %isoroot%\I386\%ToDo% c:\windows\win.ini %isoroot%\I386 if not exist %isoroot%\i386\system32\null md %isoroot%\i386\system32REM system32%ToDo% c:\windows\System32\ansi.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\autoexec.nt %isoroot%\I386\System32\%ToDo% c:\windows\System32\avicap.dll %isoroot%\I386\System32%ToDo% c:\windows\System32\avifile.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\config.nt %isoroot%\I386\System32\%ToDo% c:\windows\System32\command.com %isoroot%\I386\System32\%ToDo% c:\windows\System32\comm.drv %isoroot%\I386\System32\%ToDo% c:\windows\System32\commdlg.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\compobj.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\country.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\crtdll.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\ctl3dv2.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\ddeml.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\dosx.exe %isoroot%\I386\System32\%ToDo% c:\windows\System32\ega.cpi %isoroot%\I386\System32\%ToDo% c:\windows\System32\gdi.exe %isoroot%\I386\System32\%ToDo% c:\windows\System32\himem.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\keyboard.drv %isoroot%\I386\System32\%ToDo% c:\windows\System32\keyboard.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\krnl386.exe %isoroot%\I386\System32\%ToDo% c:\windows\System32\lanman.drv %isoroot%\I386\System32\%ToDo% c:\windows\System32\lzexpand.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\mapi.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\mciavi.drv %isoroot%\I386\System32\%ToDo% c:\windows\System32\mciseq.drv %isoroot%\I386\System32\%ToDo% c:\windows\System32\mciwave.drv %isoroot%\I386\System32\%ToDo% c:\windows\System32\mmsystem.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\mouse.drv %isoroot%\I386\System32\%ToDo% c:\windows\System32\msacm.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\mscdexnt.exe %isoroot%\I386\System32\%ToDo% c:\windows\System32\msvideo.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\netapi.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\ntdos.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\ntdos404.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\ntdos411.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\ntdos412.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\ntdos804.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\ntio.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\ntio404.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\ntio411.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\ntio412.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\ntio804.sys %isoroot%\I386\System32\%ToDo% c:\windows\System32\ntvdm.exe %isoroot%\I386\System32\%ToDo% c:\windows\System32\ntvdmd.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\ole2.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\ole2disp.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\ole2nls.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\olecli.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\olesvr.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\pmspl.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\progman.exe %isoroot%\I386\System32\%ToDo% c:\windows\System32\rasapi16.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\redir.exe %isoroot%\I386\System32\%ToDo% c:\windows\System32\shell.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\sound.drv %isoroot%\I386\System32\%ToDo% c:\windows\System32\storage.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\system.drv %isoroot%\I386\System32\%ToDo% c:\windows\System32\timer.drv %isoroot%\I386\System32\%ToDo% c:\windows\System32\toolhelp.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\typelib.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\user.exe %isoroot%\I386\System32\%ToDo% c:\windows\System32\vcdex.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\ver.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\vga.drv %isoroot%\I386\System32\%ToDo% c:\windows\System32\wfwnet.drv %isoroot%\I386\System32\%ToDo% c:\windows\System32\win87em.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\winoldap.mod %isoroot%\I386\System32\%ToDo% c:\windows\System32\winsock.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\winspool.exe %isoroot%\I386\System32\%ToDo% c:\windows\System32\wow32.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\wowdeb.exe %isoroot%\I386\System32\%ToDo% c:\windows\System32\wowexec.exe %isoroot%\I386\System32\%ToDo% c:\windows\System32\wowfax.dll %isoroot%\I386\System32\%ToDo% c:\windows\System32\wowfaxui.dll %isoroot%\I386\System32\ If not exist %isoroot%\i386\system\null md %isoroot%\i386\systemREM System%ToDo% c:\windows\System\avicap.dll %isoroot%\I386\System\%ToDo% c:\windows\System\avifile.dll %isoroot%\I386\System\%ToDo% c:\windows\System\commdlg.dll %isoroot%\I386\System\%ToDo% c:\windows\System\keyboard.drv %isoroot%\I386\System\%ToDo% c:\windows\System\lzexpand.dll %isoroot%\I386\System\%ToDo% c:\windows\System\mciavi.drv %isoroot%\I386\System\%ToDo% c:\windows\System\mciseq.drv %isoroot%\I386\System\%ToDo% c:\windows\System\mciwave.drv %isoroot%\I386\System\%ToDo% c:\windows\System\mmsystem.dll %isoroot%\I386\System\%ToDo% c:\windows\System\mmtask.tsk %isoroot%\I386\System\%ToDo% c:\windows\System\mouse.drv %isoroot%\I386\System\%ToDo% c:\windows\System\msvideo.dll %isoroot%\I386\System\%ToDo% c:\windows\System\olecli.dll %isoroot%\I386\System\%ToDo% c:\windows\System\olesvr.dll %isoroot%\I386\System\%ToDo% c:\windows\System\shell.dll %isoroot%\I386\System\%ToDo% c:\windows\System\sound.drv %isoroot%\I386\System\%ToDo% c:\windows\System\stdole.tlb %isoroot%\I386\System\%ToDo% c:\windows\System\system.drv %isoroot%\I386\System\%ToDo% c:\windows\System\tapi.dll %isoroot%\I386\System\%ToDo% c:\windows\System\timer.drv %isoroot%\I386\System\%ToDo% c:\windows\System\ver.dll %isoroot%\I386\System\%ToDo% c:\windows\System\vga.drv %isoroot%\I386\System\%ToDo% c:\windows\System\wfwnet.drv %isoroot%\I386\System\this section contains the needed registry entries. depends on how you create your registry files. if you edit the registry files directly then you will need to put the name of the imported SetupReg.hiv file. for example if you imported SetupReg.hiv as PeSetupReg then you would modify the code like this: HKLM, "PeSetupReg\ControlSet001\Control\WOW" OR add the [setupreg.addreg] section (excluding the section marker) to winpesys.inf in order to merge this into the registry while creating the hives. [Version]signature = $CHICAGO$SetupClass=BASE [DefaultInstall]AddReg = Setupreg.addreg [setupreg.addreg] HKLM, "ControlSet001\Control\WOW"HKLM, "ControlSet001\Control\WOW", "cmdline",0x00020000, "%SystemRoot%\system32\ntvdm.exe"HKLM, "ControlSet001\Control\WOW", "DefaultSeparateVDM",, "no"HKLM, "ControlSet001\Control\WOW", "LPT_timeout",, "15"HKLM, "ControlSet001\Control\WOW", "size",, "0"HKLM, "ControlSet001\Control\WOW", "wowsize",, "16"HKLM, "ControlSet001\Control\WOW", "wowcmdline",0x00020000, "%SystemRoot%\system32\ntvdm.exe -a %SystemRoot%\system32\krnl386"HKLM, "ControlSet001\Control\WOW", "KnownDLLs",, "comm.drv commdlg.dll ctl3dv2.dll ddeml.dll keyboard.drv lanman.drv mmsystem.dll mouse.drv netapi.dll olecli.dll olesvr.dll pmspl.dll shell.dll sound.drv system.drv toolhelp.dll vga.drv wfwnet.drv win87em.dll winoldap.mod winsock.dll winspool.exe wowdeb.exe timer.drv rasapi16.dll compobj.dll storage.dll ole2.dll ole2disp.dll ole2nls.dll typelib.dll msvideo.dll avifile.dll msacm.dll mciavi.drv mciseq.drv mciwave.drv progman.exe avicap.dll mapi.dll"HKLM, "ControlSet001\Control\WOW", "SharedWowTimeout", 0x00000e10HKLM, "ControlSet001\Control\WOW", "RomFontPointers",1,\ b0,52,00,c0,b0,4a,00,c0,b0,4e,00,c0,b0,60,00,c0,c0,60,00,c0,c0,70,00,c0HKLM, "ControlSet001\Control\Session Manager\Environment", "PATHEXT",,".COM;.EXE;.BAT;.CMD"HKLM, "ControlSet001\Control\VirtualDeviceDrivers"HKLM, "ControlSet001\Control\VirtualDeviceDrivers", "VDD",0x00010000, ""Hope I wasn't too confusing

which method did you use? did you remember to copy ramdriv.sys to your iso' s system32/drivers directory? this is the ramdisk that comes with Bartpe and that's what these registry entries are for. Did it work for you CuBie??