cdob

Disconnect external card readers if possible. This reduce the risk. What's a ramdom reboot? How often did the machine reboot?Can you attach the presetup.log file? There is a fix drive letter enabled by default. This may add one reboot. Did you used fixDrive.USB option? This may add a reboot too. I doubt this. This principal loop is used since several years. Most likely there exist a c: drive then. Thanks for the hint. Add a "DIR %%i: &&" FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO ( FOR %%j in (%ISO_file_search%) DO ( echo search ISO file "%%i:%%j">>presetup.log DIR %%i: && IF EXIST "%%i:%%j" ( SET ISOfile=%%i:%%j goto :ISO_file_found) ) )

Which driver did you include? Did you include one driver? Did you incldue two drivers? Did you include both toshiba and the new ICH6 driver? Which driver does windows use currently? KR10N or iastor.sys?

Thanks, a volunteer Can you forward the command line? At fake setup: read the given command line and forward the command line to presetup.cmd? XP 64: still no USB hard disk explanation. Work arround updated: Boot driver settings enhanced at presetup.cmd. Txtsetup.sif can be adjuted at [bootBusExtenders.Load] and at [inputDevicesSupport.Load]. This is not necessary. 1) If USB drive is available, just continue. 2) If USB drive is missing, set minimal USB driver settings and reboot. PNP overwrite the settings later. After installation there are default USB settings. 3) If USB drive is missing still, set enhanced USB driver settings and reboot. There are non default settings after full installation. 4) If USB drive is available still, no further trials, just continue and read the error. At pyron's fake, 64 bit compiled @echo off setlocal EnableExtensions EnableDelayedExpansion SET TAGFILE=\WIN_SETUP FOR %%h IN (U C D E F G H I J K L M N O P Q R S T V W X Y) DO ( IF EXIST "%%h:%TAGFILE%" ( SET CDDRIVE=%%h: goto :CDDRIVE_found ) ) echo no %TAGFILE% drive found echo no %TAGFILE% drive found >> winsetup.log REM +=======================================================+ REM | prepare USB boot configuration | REM |-------------------------------------------------------| echo presetup fixBoot.USB set reboot= rem second trial: permanent USB changes if exist reboot.1 if not exist reboot.2 ( set reboot=true echo reboot ÚSB driver setting >reboot.2 echo prepare USB boot configuration %date% %time% - permanent changes >>winsetup.log call :set_usb_boot_setting_full SYSTEM CurrentControlSet reg.exe load HKLM\loaded_SYSTEM config\system.sav call :set_usb_boot_setting_full loaded_SYSTEM ControlSet001 reg.exe unload HKLM\loaded_SYSTEM ) rem first trial: minimal, no permanent changes if not exist reboot.1 ( set reboot=true echo reboot ÚSB driver setting >reboot.1 echo prepare USB boot configuration %date% %time% - minimal changes>>winsetup.log call :set_usb_boot_setting SYSTEM CurrentControlSet reg.exe load HKLM\loaded_SYSTEM config\system.sav call :set_usb_boot_setting loaded_SYSTEM ControlSet001 reg.exe unload HKLM\loaded_SYSTEM ) REM +=======================================================+ REM | reboot the machine once, avoid endless loop | REM |-------------------------------------------------------| if defined reboot ( (echo reboot %date% %time% &echo.)>> winsetup.log goto :eof ) :CDDRIVE_found =============================================== set srcpath=\??\%CDDRIVE%%TAGFILE%\XP_X64\ echo CDDRIVE %CDDRIVE% - srcpath %srcpath% echo CDDRIVE %CDDRIVE% - srcpath %srcpath% >> winsetup.log if exist $winnt$.new del /f $winnt$.new FOR /F "tokens=1* delims== " %%a in ($winnt$.inf) DO ( set line=%%a = %%b if %%b.==. set line=%%a rem requires a drive letter still rem IF /I sourcepath.==%%a. set line=sourcepath = "\\?\GLOBALROOT\Device\Harddisk1\Partition1\WIN_SETUP\XP_X64" IF /I sourcepath.==%%a. set line=sourcepath = "%srcpath%" IF /I dospath.==%%a. set line=; echo !line!>>$winnt$.new ) if exist $winnt$.new ( ren $winnt$.inf $winnt$.0 if exist $winnt$.inf del /f $winnt$.inf ren $winnt$.new $winnt$.inf ) findstr.exe "sourcepath" $winnt$.inf findstr.exe "sourcepath" $winnt$.inf >> winsetup.log rem required at all? rem start /min "USB keep mount work arround" pushd %CDDRIVE% REM +=======================================================+ REM | Finally start the installation | REM |-------------------------------------------------------| if exist setupold.exe del /f setupold.exe >> winsetup.log if exist setup.exe ren setup.exe setupold.exe if exist setupORG.exe ren setupORG.exe setup.exe rem often setup.exe -newsetup FOR /F "tokens=1-2*" %%a IN ('reg.exe query "HKLM\SYSTEM\Setup" /v "CmdLine"') DO ( set CmdLine=%%c) IF "%CmdLine:~-2%"=="\0" set CmdLine=%CmdLine:~0,-2% (echo. &echo run setup CmdLine: %CmdLine% - %date% %time%) (echo. &echo run setup CmdLine: %CmdLine% - %date% %time%) >> winsetup.log start /WAIT %CmdLine% REM +=======================================================+ EXIT goto :eof ============================================================= :set_usb_boot_setting ================================================= set Services=HKLM\%1\%2\Services echo on reg.exe query "%Services%\usbohci" | findstr.exe /I "Start" && ( reg.exe add "%Services%\usbohci" /f /t REG_DWORD /v "Start" /d 0 reg.exe add "%Services%\usbohci" /f /v "Group" /d "Boot Bus Extender" ) reg.exe query "%Services%\usbuhci" | findstr.exe /I "Start" && ( reg.exe add "%Services%\usbuhci" /f /t REG_DWORD /v "Start" /d 0 reg.exe add "%Services%\usbuhci" /f /v "Group" /d "Boot Bus Extender" ) reg.exe query "%Services%\usbehci" | findstr.exe /I "Start" && ( reg.exe add "%Services%\usbehci" /f /t REG_DWORD /v "Start" /d 0 reg.exe add "%Services%\usbehci" /f /v "Group" /d "Boot Bus Extender" ) reg.exe add "%Services%\usbhub" /f /t REG_DWORD /v "Start" /d 0 reg.exe add "%Services%\usbhub" /f /v "Group" /d "System Bus Extender" reg.exe add "%Services%\usbstor" /f /t REG_DWORD /v "Start" /d 0 reg.exe add "%Services%\usbstor" /f /v "Group" /d "System Bus Extender" @echo off goto :eof === end set_usb_boot_setting =============================== :set_usb_boot_setting_full ============================================ set CriticalDeviceDatabase=HKLM\%1\%2\Control\CriticalDeviceDatabase set Services=HKLM\%1\%2\Services echo on reg.exe add "%CriticalDeviceDatabase%\PCI#CC_0C0300" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-444553540000}" reg.exe add "%CriticalDeviceDatabase%\PCI#CC_0C0300" /f /v "Service" /d "usbuhci" reg.exe add "%CriticalDeviceDatabase%\PCI#CC_0C0310" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-444553540000}" reg.exe add "%CriticalDeviceDatabase%\PCI#CC_0C0310" /f /v "Service" /d "usbohci" reg.exe add "%CriticalDeviceDatabase%\PCI#CC_0C0320" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-444553540000}" reg.exe add "%CriticalDeviceDatabase%\PCI#CC_0C0320" /f /v "Service" /d "usbehci" reg.exe add "%CriticalDeviceDatabase%\USB#CLASS_08" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-444553540000}" reg.exe add "%CriticalDeviceDatabase%\USB#CLASS_08" /f /v "Service" /d "usbstor" reg.exe add "%CriticalDeviceDatabase%\USB#CLASS_09" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-444553540000}" reg.exe add "%CriticalDeviceDatabase%\USB#CLASS_09" /f /v "Service" /d "usbhub" reg.exe add "%CriticalDeviceDatabase%\USB#ROOT_HUB" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-444553540000}" reg.exe add "%CriticalDeviceDatabase%\USB#ROOT_HUB" /f /v "Service" /d "usbhub" reg.exe add "%CriticalDeviceDatabase%\USB#ROOT_HUB20" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-444553540000}" reg.exe add "%CriticalDeviceDatabase%\USB#ROOT_HUB20" /f /v "Service" /d "usbhub" reg.exe add "%Services%\usbohci" /f /v "Group" /d "Boot Bus Extender" reg.exe add "%Services%\usbohci" /f /t REG_DWORD /v "Tag" /d 3 reg.exe add "%Services%\usbohci" /f /t REG_DWORD /v "ErrorControl" /d 1 reg.exe add "%Services%\usbohci" /f /t REG_DWORD /v "Start" /d 0 reg.exe add "%Services%\usbohci" /f /t REG_DWORD /v "Type" /d 1 reg.exe add "%Services%\usbuhci" /f /v "Group" /d "Boot Bus Extender" reg.exe add "%Services%\usbuhci" /f /t REG_DWORD /v "Tag" /d 3 reg.exe add "%Services%\usbuhci" /f /t REG_DWORD /v "ErrorControl" /d 1 reg.exe add "%Services%\usbuhci" /f /t REG_DWORD /v "Start" /d 0 reg.exe add "%Services%\usbuhci" /f /t REG_DWORD /v "Type" /d 1 reg.exe add "%Services%\usbehci" /f /v "Group" /d "Boot Bus Extender" reg.exe add "%Services%\usbehci" /f /t REG_DWORD /v "Tag" /d 3 reg.exe add "%Services%\usbehci" /f /t REG_DWORD /v "ErrorControl" /d 1 reg.exe add "%Services%\usbehci" /f /t REG_DWORD /v "Start" /d 0 reg.exe add "%Services%\usbehci" /f /t REG_DWORD /v "Type" /d 1 reg.exe add "%Services%\usbhub" /f /v "Group" /d "System Bus Extender" reg.exe add "%Services%\usbhub" /f /t REG_DWORD /v "Tag" /d 2 reg.exe add "%Services%\usbhub" /f /t REG_DWORD /v "ErrorControl" /d 1 reg.exe add "%Services%\usbhub" /f /t REG_DWORD /v "Start" /d 0 reg.exe add "%Services%\usbhub" /f /t REG_DWORD /v "Type" /d 1 reg.exe add "%Services%\usbstor" /f /v "Group" /d "System Bus Extender" reg.exe add "%Services%\usbstor" /f /t REG_DWORD /v "Tag" /d 7 reg.exe add "%Services%\usbstor" /f /t REG_DWORD /v "ErrorControl" /d 1 reg.exe add "%Services%\usbstor" /f /t REG_DWORD /v "Start" /d 0 reg.exe add "%Services%\usbstor" /f /t REG_DWORD /v "Type" /d 1 @echo off goto :eof === end set_usb_boot_setting_full ============================

That's a good question, let's investigate: Toshiba txtsetup.oem Intel txtsetup.oem There is a AHCI PCI\VEN_8086&DEV_2653&CC_0106, contrary there is no RAID PCI\VEN_8086&DEV_2653&CC_0104.Toshiba uses a the hardware at RAID mode. This hardware usage maybe with or without Intel support. Compare the ICH6R example too: there is "PCI\VEN_8086&DEV_2652&CC_0104" and "PCI\VEN_8086&DEV_2652&CC_0106". The Intel driver works, if you set a BIOS mode relating to PCI\VEN_8086&DEV_2653&CC_0106. Intel iastor.sys may work at this controller too, but this is not supported by Intel. A adjusted iastor.inf maybe nice for testing. But be aware, this is experimental: there is data loss possible if driver is changed from KR10N.sys to iastor.sys Seems to be a bad idea at second glance. @shadesters Try the Toshiba drivers first.

Yes. I've the same experience and no explanation still.XP SP2 64 bit: A average USB stick or SD card reader inserted: PNP does detect the SD card reader and load drivers. This SD card reader does get a drive letter.The strange SD card reader inserted to new installed windows. PNP does detect the SD card reader and load drivers. However next there is a message: This SD card reader dosn't get a drive letter.USB hard disk dosn't get a dive letter too. All USB drivers are loaded (demand start by HKLM\SYSTEM\CurrentControlSet\Enum), but no letter assigned. At first reboot system is in SystemSetupInProgress mode, hence PE. This remids to: At PE a USB hard disk dosn't get a drive letter if connected after boot. Work arround: load USB drivers at [bootBusExtenders.Load] and disable at [inputDevicesSupport.Load]. I used pyron's 64 bit debug fake setup for debug reasons: nice to get a output on screen. @echo off setlocal EnableExtensions EnableDelayedExpansion SET TAGFILE=\WIN_SETUP FOR %%h IN (U C D E F G H I J K L M N O P Q R S T V W X Y) DO ( IF EXIST "%%h:%TAGFILE%" ( SET CDDRIVE=%%h: goto :CDDRIVE_found ) ) echo no %TAGFILE% drive found echo no %TAGFILE% drive found >> winsetup.log :CDDRIVE_found set srcpath=\??\%CDDRIVE%\%TAGFILE%\XP_X64\ echo CDDRIVE %CDDRIVE% - srcpath %srcpath% echo CDDRIVE %CDDRIVE% - srcpath %srcpath% >> winsetup.log echo adjust $winnt$.inf: sourcepath = \??\%CDDRIVE%\%TAGFILE%\XP_X64\ >> winsetup.log if exist $winnt$.new del /f $winnt$.new FOR /F "tokens=1* delims== " %%a in ($winnt$.inf) DO ( set line=%%a = %%b if %%b.==. set line=%%a IF /I sourcepath.==%%a. set line=sourcepath = "%srcpath%" IF /I dospath.==%%a. set line=; echo !line!>>$winnt$.new ) if exist $winnt$.new ( ren $winnt$.inf $winnt$.0 if exist $winnt$.inf del $winnt$.inf ren $winnt$.new $winnt$.inf ) rem start /min "USB keep mount work arround" pushd %CDDRIVE% REM +=======================================================+ REM | Finally start the installation | REM |-------------------------------------------------------| if exist setupold.exe del /f setupold.exe >> winsetup.log if exist setup.exe ren setup.exe setupold.exe if exist setupORG.exe ren setupORG.exe setup.exe rem often setup.exe -newsetup FOR /F "tokens=1-2*" %%a IN ('reg.exe query "HKLM\SYSTEM\Setup" /v "CmdLine"') DO ( set CmdLine=%%c) IF "%CmdLine:~-2%"=="\0" set CmdLine=%CmdLine:~0,-2% (echo. &echo run setup CmdLine: %CmdLine% - %date% %time%) (echo. &echo run setup CmdLine: %CmdLine% - %date% %time%) >> winsetup.log start /WAIT %CmdLine% REM +=======================================================+ In addition there are strange machines. USB hardware is initialized late at boot. No hardware to test.

Bcraid.sys is a storport.sys driver model. http://www.microsoft.com/windowsserver2003...rt/default.mspx The driver expect 2003, not XP.

No warez support. http://www.msfn.org/board/forum-rules-upda...ead-t18408.html

USB drivers was set at txtsetup.sif [bootBusExtenders.Load] section.USB drive got a letter. That's a very good question. It turned out:I used previously a micro SC card and a USB micro SD card reader. PNP did disable USB drive. This can be avoided with "pushd %CDDRIVE%". Next i used the same micro SC card, but another USB SD card reader. presetup.cmd edited: "pushd %CDDRIVE%" was NOT launched. PNP does keep the USB drive. Installation does complete without a error. To crosscheck I used the old broken USB micro SD card reader. Once again the same micro SD card, no editing at all now. PNP does disable the USB drive. The USB SD card reader makes the difference. Strange, I'm surprised and confused. No explanation. No idea. Ignore this part so far. Idea was to use dosdev.exe and use this to set sourcepath. That's note necessary, your solution works fine. My testing hardware use a 32 bit CPU. No 64 bit testing possible.The good 64 bit hardware is used for importand work, not to be used for testings. Used for testings currently.

Setupldr.bin location doesn't matter at grub4dos. Load the appropiate file. The edited Setupldr.bin was at /XP64/SETUPLDR.BIN. If you like this one, chainload this one. If you like to use another one, chainload the another one. The original one was at /XP64/I386/SETUPLDR.BIN Use grub4dos to change this file in RAM. Keep all files as described previously, there is no change.

I've compiled a 64 bit version of Pyron's fake setup.exe. Don't you remember from ISO RAM load?As long as you use 64 bit only applications, setup behave consistent. As you like. No explanation. Contrary missing USB is reported at 32 bit ISO RAM load too: some strange BIOS. Missing USB seems to be more common. PNP works up to USB Root Hub device, installation does fails. Driver not found anymore.Add a work around to presetup.cmd, open drive U: [BootBusExtenders.Load] usbehci = usbehci.sys usbohci = usbohci.sys usbuhci = usbuhci.sys usbhub = usbhub.sys usbstor = usbstor.sys [InputDevicesSupport.Load] ;usbohci = usbohci.sys ;usbuhci = usbuhci.sys ;usbehci = usbehci.sys ;usbhub = usbhub.sys ;usbstor = usbstor.sys [BootBusExtenders] usbehci = "Enhanced Host Controller",files.usbehci,usbehci usbohci = "Open Host Controller",files.usbohci,usbohci usbuhci = "Universal Host Controller",files.usbuhci,usbuhci usbhub = "Generic USB Hub Driver",files.usbhub,usbhub usbstor = "USB Storage Class Driver",files.usbstor,usbstor USB drives are available at first reboot. Next USB hardware did break, hardware not detected anymore. New hardware prepared: dosn't boot anymore: biosinfo.inf not found. Reason: FAT16 formated, directory WIN_SETUP not found. WIN_SETUP renamed to WINSETUP (8.3 name) and config adjusted. XP installation does work again. Dosdev.exe from resource kit list device names. Did you tried USB SourcePath "Device\Harddisk1\DP(1)0-0+2\WIN_SETUP\XP_x64\AMD64\" at $winnt$.sif? USB stick keeps available, but PNP freeze. Be aware, testings are done at one machine only. Different BIOS may get different results. PyronSetup.7z

OSCDIMG creates a El Torito multiboot version. Specs http://www.phoenix.com/NR/rdonlyres/98D321.../specscdrom.pdf This feature was seldom supported by BIOS in the past. http://www.nu2.nu/bootcd/#howboot May be EFI mainboards are different now. oscdimg.exe -bootdata:2#p0,b".\x86\boot\etfsboot.com"#pEF,b".\amd64\boot\etfsboot.com" . o.isoCreated ISO image does boot at VMware Playes, but x86 etfsboot.com is launched directly. Multiboot does fail at this example.

Try at any mkisofs version you can find: mk_XP64.cmd mkisofs -iso-level 3 -N -D -d -relaxed-filenames -allow-multidot -joliet-long ^ -r -b grldr -hide boot.catalog -no-emul-boot -boot-load-size 4 ^ -o XP64.iso -o XP64.iso iso_root Yes, /XP64/I386/SETUPLDR.BIN is the original file. Yes, should work title Loading XP install - plain /I386/SETUPLDR.BIN chainloader /I386/SETUPLDR.BIN

@ilko_t Wow64FsRedirection did confuse me. Brute force approach did work using fake setup.exe from WinSetupFromUSB 0.2.4. Can you name a good x64 txtsetup.sif example?Dietmar's usbboot.inf. and txtsetup.sif [bootBusExtenders.Load] set. After reboot there is d: USB drive available. Presetup.cmd and fixsrcpath.exe does adjust $winnt.sif$. Setup does continue. Next drive d: disappear. Setup holds, missing files. Try editing usb*.inf or do you have another suggestion? @Siginet Different txtsetup.sif is a inter media step. Use ONE ISO image finally. Load this to RAM. Use grub4dos to change txtsetup.sif in RAM. There are dd, write and 'cat --locate --replace' to edit txtsetup.sif.

Premilary note: Test version WinSetupFromUSB 0.2.4 XP SP2 64 bit I'm using -graft-points to create the ISO file. Files are read from USB drive. \WIN_SETUP\mkiso.cmd set win_root=%~dp0 set win_files=XP_x64 mkisofs.exe -graft-points -o %win_root%/%win_files%.ISO ^ /I386/SETUPLDR.BIN=%win_root%\%win_files%\I386\SETUPLDR.BIN ^ /I386/NTDETECT.COM=%win_root%\%win_files%\I386\NTDETECT.COM ^ /AMD64/TXTSETUP.SIF=%win_root%\%win_files%\AMD64\TXTSETUP.SIF 32 bit fake setup complains: C:\WINDOWS\system32\presetup.cmd : file not found C:\WINDOWS\system32\setupORG.exe : file not found Both file does exit at hard disk. Fake setup.exe is 28 kb size, that's the BTS one, not Pyron's. PE booted: setuporg.exe renamed to setup.exe. The same experience: USB drive is missing. Next idea add Dietmar's usbboot.inf. USB drive should be available at first reboot. To be continued. Grub4dos support hex editing in RAM nowadays. Add one setupldr.bin and different renamed txtsetup.sif. Patch setupldr.bin on the fly.

Grub4dos is a multi boot loader. Grub4dos was enhanced recently, 14th Nov 2009: http://nufans.net/grub4dos/tinybit/ Editing in RAM is possible now. Previous editing is not required anymore. General grub4dos informations: integrated help file http://grub4dos.sourceforge.net/wiki/index...ub4dos_tutorial http://diddy.boot-land.net/grub4dos/Grub4dos.htm Grub4dos can chainload setupldr.bin: no need for a boot sector file. title Loading XP install - plain /I386/SETUPLDR.BIN chainloader /I386/SETUPLDR.BIN title Windows XP PRO 64 SP2 - multi boot map --mem /XP64/I386/SETUPLDR.BIN (rd) #checksum: geitonaki http://www.msfn.org/board/index.php?showtopic=58410 write --offset=0x2060 (rd)+1 \xEB\x1A #cdob SetupSourcePath="\XP64\"; BootPath=\XP64\AMD64\ #http://www.msfn.org/board/index.php?s=&showtopic=126480&view=findpost&p=814566 cat --locate="\\i386\\ntdetect" --replace="\\XP64\\ntdetect.com" (rd)+1 cat --locate="amd64\\" --replace="XP64\\\x00" (rd)+1 cat --locate="AMD64\\" --replace="XP64\\\x00" (rd)+1 cat --locate="\\AMD64" --replace="\\XP64\x00" (rd)+1 cat --locate=I386 --replace=XP64 (rd)+1 chainloader (rd)+1 root ()

General grub4dos informations: integrated help file http://grub4dos.sourceforge.net/wiki/index...ub4dos_tutorial http://diddy.boot-land.net/grub4dos/Grub4dos.htm Grub4dos can chainload setupldr.bin: no need for a boot sector file. Grub4dos was enhanced recently, 14th Nov 2009: http://nufans.net/grub4dos/tinybit/ Editing in RAM is possible now. title Loading XP install - plain /I386/SETUPLDR.BIN chainloader /I386/SETUPLDR.BIN title Windows XP Home\n Windows XP Home - multi boot - unattended map --mem /XHO1/SETUPLDR.BIN (rd) cat --locate=i386 --replace=XHO1 (rd)+1 chainloader (rd)+1 root () title Windows XP Home\n Windows XP Home - multi boot - attended map --mem /XHO1/SETUPLDR.BIN (rd) cat --locate=i386 --replace=XHO1 (rd)+1 cat --locate=WINNT.SIF --replace=WINNT.OFF (rd)+1 chainloader (rd)+1 root () title Windows XP Home System Builder\n Windows XP Home - multi boot - mass storage drivers floppy image map --mem /INST/F6FLOPPY.IMA (fd0) map --mem /INST/F6FLOPPY.IMA (fd1) map --hook map --mem /XHO1/SETUPLDR.BIN (rd) cat --locate=i386 --replace=XHO1 (rd)+1 chainloader (rd)+1 root () title Windows XP PRO 64 SP2 - multi boot map --mem /XP64/I386/SETUPLDR.BIN (rd) #checksum: geitonaki http://www.msfn.org/board/index.php?showtopic=58410 write --offset=0x2060 (rd)+1 \xEB\x1A #cdob SetupSourcePath="\XP64\"; BootPath=\XP64\AMD64\ #http://www.msfn.org/board/index.php?s=&showtopic=126480&view=findpost&p=814566 cat --locate="\\i386\\ntdetect" --replace="\\XP64\\ntdetect.com" (rd)+1 cat --locate="amd64\\" --replace="XP64\\\x00" (rd)+1 cat --locate="AMD64\\" --replace="XP64\\\x00" (rd)+1 cat --locate="\\AMD64" --replace="\\XP64\x00" (rd)+1 cat --locate=I386 --replace=XP64 (rd)+1 chainloader (rd)+1 root () @meowing Yes 0x00 is importand, space won't work.

No, there are no addional steps required. However it's reccomended to "gzip.exe -9 UBCD4WIN.ISO" Required disk space and boot time is reduced. http://www.gzip.org/ and ubcd4win\plugin\Add-Ons\UnxUtils\files\gzip.exe title mem Loading UBCD4Win.GZ /I386/SETUPLDR.BIN ls /images/UBCD4WIN.GZ || find --set-root /images/UBCD4WIN.GZ map --mem /images/firadisk.ima (fd0) map --mem /images/UBCD4WIN.GZ (0xFF) map --hook chainloader (0xFF)/I386/SETUPLDR.BIN A classic XP/2003 won't boot without additional drivers. Yes, a BootSDI version does work, because this use RAM load already (2003 SP1 setupldr.bin based).

CD Shell contain a loader.bin. It's recommended to use this loader for CD Shell. What's a leading booter?There are two open source booter developed currently: grub4dos and syslinux.

No, loader.bin is not located at sector 17. Read the CD boot specs again. Loader.bin load cdshell main application: cdsh.bin. By the way: cdshell is not developed since 2005.

The BIOS read sector 17 of last session.“El Torito” Bootable CD-ROM Format Specification http://www.phoenix.com/NR/rdonlyres/98D321.../specscdrom.pdf Given cdshell: the Boot Catalog contain a pointer to another sector. This sector contain data from loader.bin.

Yes, it is.

Command does NOT replace all amd64. Try and report.Don't compare different setupldr.bin. They goes to different solutions. Again, you are mixing solutions, ask details at proper thread.

Yes, this is valid for XP x64 SP2. What's (SP2+) ? Apply this for relocated versions.There is no need to change setupldr.bin at original location. However mixing original and relocated versions may get strange results. Or work without any issue. No idea. Yes, it is. BBIE - Bart's Boot Image Extractor http://www.nu2.nu/bbie/ spcmdcon.sys contains the boot image too. At offset 0x17F00, size one CD data sector.

Sorry I didn't understand there are different ISO files. I understood you used the nLite ISO image always.To allow multiple dots at ISO 9660: mkisofs -allow-multidot Yes, or add Joliet file system: mkISO_RAMload_sort.cmd -joliet-long Rock Ridge extension won't matter in that case. Anyay use -r instead of -R at windows in future. Yes, winnt.sif is not WINNT.SIF. Grub4dos ignore case at (floppy, hard) disk file system, your USB stick.Grub4dos is case sensitive at ISO 9660 file system, your CD.

Use any working multi boot loader, there is no limitation. Use the classic boot sector file. Edited files, compare flyakite guide. multi boot loader -> boot sector file -> setupldr.bin The boot sector file solution is outdated nowadays. Chainload different (edited) setupldr.bin: multi boot loader -> setupldr.bin No idea about EasyBoot. Ask further questions in another thread.