cdob

It's prepared already. Txtsetup.oem contains already Add a 2003 setup.exe as \setup\I386_03\setupORG.exe Examle: floppy image mounted in RAM as fd0 and fd1: #patch txtsetup.oem, use 2003 setuporg.exe cat --locate=setuporg.exe --number=1 (fd0)/TXTSETUP.OEM > nul || call :error firadisk.img file error.. set /a offset=%?% - 9 write --offset=%offset% (fd0)/TXTSETUP.OEM se03_32 dd if=(fd0)/TXTSETUP.OEM of=(fd1)/TXTSETUP.OEM cat (fd1)/TXTSETUP.OEM pause press a key Thank's for the RUN batch by Sratif, it's overwhelming. Grub4dos at max features. Did you solve missing floppy drive at 2003 install? Did you edited the ISO file? What about adding firadisk to ISO file? A floppy image is obsolete that way. Missing asms indicates (virtual) CD drive is missing.Could be a timing problem. USB drive has to be available first. Without a available USB drive, there is no ISO file. Firadisk can't find a ISO file. Different hardware, different USB port, file location, BIOS may get timing difficulties. IMA v05 used two drivers and automatic CriticalDeviceDatabase fix. The log file would be nice. I'm about IMA v06 at firadisk only and automatic CriticalDeviceDatabase fix. However no special hardware to test.

Thanks, that's a wonderful soltution. I like this.What about using file name %~pnx0 as tag file echo Locating %~pnx0 find --set-root --devices=fh %~pnx0 A menu.lst title Setup Windows XP from ISO : \nBoot once from USB set myISO=/images/XP_PRO_HP_OEM.iso #ilko_t http://www.msfn.org/board/topic/149675-install-xp-from-a-iso-file/page__view__findpost__p__988093 /boot/shifthd.bat find --set-root --devices=h %myISO% map %myISO% (222) map --mem /images/FIRADISK.IMG (fd0) #map --mem /images/FIRADISK.IMG (fd1) map --rehook #chenall's ntboot cat --locate=###### --number=1 (fd0)/TXTSETUP.OEM > nul || call :error firadisk.img file error.. set offset=%?% set fira.opt=cdrom,vmem=find:%myISO%; write --offset=%offset% (fd0)/TXTSETUP.OEM value=Parameters,StartOptions,REG_SZ,"%fira.opt%"\r\n cat --skip=%offset% --locate=/ --replace=\\ (fd0)/TXTSETUP.OEM cat (fd0)/TXTSETUP.OEM pause press a key root (222) chainloader (222)/I386/SETUPLDR.BIN

It's by chenall? http://chenall.net/post/ntboot/ That's a direct approach to boot once from USB. The firadisk registry entry is added to txtsetup.oem There are # added to txtsetup.oem title Setup Windows from ISO set XPISO=XP.ISO set fira.opt=cdrom,vmem=find:/images/%XPISO%; map /images/%XPISO% (222) map --mem /images/firadisk.IMG (fd0) map (hd0) (hd1) map (hd1) (hd0) map --hook #chenall's ntboot http://chenall.net/post/ntboot/ cat --locate=###### --number=1 (fd0)/TXTSETUP.OEM > nul || call :error firadisk.img file error.. set offset=%?% write --offset=%offset% (fd0)/TXTSETUP.OEM value=Parameters,StartOptions,REG_SZ,"%fira.opt%"\r\n cat --skip=%offset% --locate=/ --replace=\\ (fd0)/TXTSETUP.OEM chainloader (222)/I386/SETUPLDR.BIN This works at USB boot friendly BIOS, almost all cases nowadays. That's a nice approach. However redistribution of certain files is unclear.Do you have a idea: how does chinese friends solve hard disk mapping? Yes, for test purposes so far. Try and report 20 real world examples.Edited: %ISO_TYPE%/ removed

Which old hardware do you use? Is a USB 2.0 controller available? Does BIOS enable USB 2.0 speed at USB boot? Loading a file to RAM may take some time. Actually there are two textmode parts. First: boot to user selectable target drive. Second: Copy files to hard disk Which part(s) refers to slow on a old computer? Which time does it take? Name minutes and seconds. Which files are inside this ISO image?A tiny ISO trick will fail. If a small ISO contains first boot files to user selectable target drive, then first boot can be faster. Following parts may work or fail. It's possible to RAM load recovery console and install from flat file at same ISO file. Compare recovery console part There is a missing gap between tiny ISO file and ISOimage.ini.Firadisk may map small ISO file and big ISO file. And windows setup may boot from small ISO. Next search files inside small ISO to copy to hard disk. However there are no files inside How to satisfy setup?

That's havily modded. Try a vanilla 2003 image. I'm getting missing firadisk at XP size about 300 MB. It's size or nlited version? Does your txtsetup.sif calls sfloppy.sys still? Which Dell desktop do you use? Which boot drive do you use by default? Which XP/2003 target do you install to? Edit menu.lst, replace two checkrange lines with #checkrange 0x80 read 0x8280 && geometry (hd1) && map (hd0) (hd1) #checkrange 0x80 read 0x8280 && geometry (hd1) && map (hd1) (hd0) clear echo existing hd: echo geometry (hd9) && echo geometry (hd8) && echo geometry (hd7) && echo geometry (hd6) && echo geometry (hd5) && echo geometry (hd4) && echo geometry (hd3) && echo geometry (hd2) && echo geometry (hd1) && echo geometry (hd0) && echo pause pause clear echo mapping hd #calculate max HDD set /a hdN=*0x475&0xff + 0x80 - 1 echo max HDD (%hdN%) geometry (hd9) && map (hd9) (hd8) && echo map (hd9) (hd8) && echo geometry (hd8) && map (hd8) (hd7) && echo map (hd8) (hd7) && echo geometry (hd7) && map (hd7) (hd6) && echo map (hd7) (hd6) && echo geometry (hd6) && map (hd6) (hd5) && echo map (hd6) (hd5) && echo geometry (hd5) && map (hd5) (hd4) && echo map (hd5) (hd4) && echo geometry (hd4) && map (hd4) (hd3) && echo map (hd4) (hd3) && echo geometry (hd3) && map (hd3) (hd2) && echo map (hd3) (hd2) && echo geometry (hd2) && map (hd2) (hd1) && echo map (hd2) (hd1) && echo geometry (hd1) && map (hd1) (hd0) && echo map (hd1) (hd0) && echo geometry (hd0) && map (hd0) (%hdN%) && echo map (hd0) (%hdN%) && echo map --hook pause pause clear echo mapped hd echo geometry (hd9) && echo geometry (hd8) && echo geometry (hd7) && echo geometry (hd6) && echo geometry (hd5) && echo geometry (hd4) && echo geometry (hd3) && echo geometry (hd2) && echo geometry (hd1) && echo geometry (hd0) && echo pause pausePost the output messages. Does boot.ini work now?

@thangpro2921 And list used hardware. This includes BIOS. Do you use a Toshiba laptop?

A default 2003 SP2 32bit trial does install fine here.Did you edited the ISO file? Which file size do you use? Which hardware and grub4dos version do you use?Try fd0 only map --mem /images/XP_INST.IMA (fd0) #map --mem /images/XP_INST.IMA (fd1) And about false hdN machines: can you name a example? Which disks are connected? Boot grub4dos, press c to command line. Which fd and hd devices are listed? Which device match USB drive? Which device match internal hard disks?

Thanks, this is a good idea at a default image. What about a multi boot iso image without /I386/SETUPLDR.BIN ? What about ls (222)BOOTFIX.BIN && chainloader (222)/I386/SETUPLDR.BIN ls (222)/I386/BOOTFIX.BIN || chainloader (222) At second glance this is broken: firadisk search firadisk.img at a disk, but there is RAM loaded floppy used too.Should be: write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/images/winsetup.iso;\n\0Can you test this at real hardware? Much simple menu.lst than mine.But you have more testing hardware. I'm used to one hard disk (read: BIOS maps target hard disk as hd1 at USB boot) and one usb drive. Any map (hd?) real experince is highly welcome. FiraDisk StartOptions is in investigation. Remember the name: a start option is valid at start: at firadisk driver start. Firadisk is running after reboot already. A simple registry add won't work after driver is started. And firadisk is marked as a boot driver: a net stop is rejected. At a addional reboot there is a drive load order and drive intialization. USB drivers has to be loaded, initialized, USB drive available. Next firadisk could find a file. Unfortunately different hardware may gives different timing results. A solution may work at known hardware, but fail at other hardware. At second glance: a driver pair firadisk/imdisk gives predictable timing. Should work at more machines.

Firaidk and imdisk drver update in XP_INST_v05.7z at first post. A flat ISO file is possible in addition. No need to RAM load ISO image. At proper hardware RAM load approach is faster. Example menu.lst, ISO file /images/winsetup.iso. Or try a simple automatic map --mem /images/winsetup.iso (222) || map /images/winsetup.iso (222) However: How much RAM requires textmode setup? How to calculate free RAM at grub4dos? How to calculate free RAM and subtrahend textmode part?

That's nice. Thanks for report. Yes, flat file mapped IMA writes to hardware. This require a friendly BIOS too. Don't rely on that. Be aware, that's under construction still. Most likely I'll change the approach. Call "setup.cmd -cleanup" late at [GuiUnattended]. This restores default registry settings.Can you accept one more reboot at setup.cmd approach? Add registry setting inside setup.cmd and reboot. ImDisk is obsolete that way. Yes, that's possible. However this would require to edit a ISO file. Do you like to edit a iso file? There are different approaches to add registry settings.

Don't you remember? I recommended this approach at reboot.pro. Yes, I like it. I dislike the technical requirement of two different drivers. A one driver approach seems to be nicer. I did this years ago to support a default ISO image. It's a user personal choice: Some users prefers default ISO file and a virtual floppy image. Drawback, you can't use a USB floppy anymore to load F6 drivers. Grub4dos and BIOS has to support this. The virtual floppy approach fails at some BIOS. Other users prefers all drivers and addons inside the ISO file. This can be done too. There is no one size fit all solution. Firadisk read settings from registry too. The other approach uses hivesys.inf Firadisk read registry and search \images\winsetup.iso.No need for a second boot to USB. Seems to be a grub4dos error. Try remove %XPISO%, use a fixed name at menu.lst. Thanks for asking. Give me this weekend to validate the newer setup.cmd again.Automatic usb drivers load is nice for the pubilic at troublesome BIOS. And I dislike the requirement to edit setup.cmd. All user settings should be at menu.list or a ini file. Of course you may setup.cmd in addition, but default should be to keep it. Do you use a approach at work? Do you remove firadisk and imdisk at end of installation? Do you need default USB settings at end of installation? The CriticalDeviceDatabase approach changes default behaviour. Do you restrict end users at USB usage, disallow USB storage? If you set relating permissions, it may be a good idea to remove USB CriticalDeviceDatabase at end of installation.

Goto grub4dos command line: which devices exist? Boot from internal hard disk for gui mode.Set BIOS to boot from inernal hard disk always. Press a hot key (could be ESC, F9, F11, F12) at boot to select a boot device. Next select XP install from USB device. Machine continues at internal hard disk a next reboot. It's another approach. With less addional code. XP_INST.IMA uses imdisk to mount ISO file.New approach uses new firadisk feature to search and mount the ISO file. That's one driver for textmode and gui mode. USB drivers has to lauch first, ISO file can be found next. This works directly at a friendly BIOS. And does require addional settings at a unfriendly BIOS. Hence the CriticalDeviceDatabase setttings. Try to RAM load the floppy image and direct map for the iso.You may write different ISO file name to floppy image. Read ISO RAM thread for examples.. This uses imdisk to mount the ISO file. That's a marker for firadisk driver. Firadisk does search files on its own and mount the found images. Use current firadisk. And be aware: There has to be one /images/winsetup.iso at all drives. If there are several /images/winsetup.iso at differnt drives, you may get a BSOX 0x7b. Well, it's a personal choice.At some machines/BIOS setup dosn't detect floppy image at textmode: Driver load does work, but driver copy fails. A full ISO file integrated solution would be nice in that cases.

Yes, it does. fixBoot.USB is automatic there. USB BIOS boot is strange sometimes. Can you name some hardware examples? Do you use Dell? a optiplex 845?

Read more sites and combine another approach. Dietmar explained USB boot basics in 2005 http://www.911cd.net/forums//index.php?showtopic=14181 http://winusb.de/download.html Based on this there is a another approach by Emanuel http://web.archive.org/web/20100406060758/http://www.ngine.de/article/id/8 OS manufacturer confims basic USB boot settings in 2009 http://msdn.microsoft.com/en-us/library/ee428799.aspx Don't you edit the ISO image anyway? There is another approach: combine existing parts new: use firadisk search feature and configure USB boot settings. To boot once from USB: Edit \i386\txtsetup.sif http://web.archive.org/web/20100406060758/http://www.ngine.de/article/id/8 No need to edit [inputDevicesSupport] section.Given a file \images\winsetup.iso: Edit \i386\hivesys.inf [AddReg] ;search ISO image HKLM,"SYSTEM\CurrentControlSet\Control\FiraDisk","StartOptions",0x0,"cdrom,vmem=find:\images\winsetup.iso" ;edit txtsetup.sif move USB controller, hub and storage to Boot Bus Extender ;and add USB CriticalDeviceDatabase settings HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#CC_0C0300",ClassGUID,0x00000000,{36FC9E60-C465-11CF-8056-444553540000} HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#CC_0C0300",Service,0x00000000,usbuhci HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#CC_0C0310",ClassGUID,0x00000000,{36FC9E60-C465-11CF-8056-444553540000} HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#CC_0C0310",Service,0x00000000,usbohci HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#CC_0C0320",ClassGUID,0x00000000,{36FC9E60-C465-11CF-8056-444553540000} HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#CC_0C0320",Service,0x00000000,usbehci HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\USB#CLASS_09",ClassGUID,0x00000000,{36FC9E60-C465-11CF-8056-444553540000} HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\USB#CLASS_09",Service,0x00000000,usbhub HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\USB#ROOT_HUB",ClassGUID,0x00000000,{36FC9E60-C465-11CF-8056-444553540000} HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\USB#ROOT_HUB",Service,0x00000000,usbhub HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\USB#ROOT_HUB20",ClassGUID,0x00000000,{36FC9E60-C465-11CF-8056-444553540000} HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\USB#ROOT_HUB20",Service,0x00000000,usbhub HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\USB#CLASS_08",ClassGUID,0x00000000,{36FC9E60-C465-11CF-8056-444553540000} HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\USB#CLASS_08",Service,0x00000000,usbstorAdjust \images\winsetup.iso to your configuration. menu.lst title Setup Windows from ISO : Boot from ISO, with virtual CD+Floppy map /images/winsetup.iso (222) map /images/firadisk.img (fd0) map /images/firadisk.img (fd1) map --mem (md)0x800+4 (99) checkrange 0x80 read 0x8280 && geometry (hd1) && map (hd0) (hd1) checkrange 0x80 read 0x8280 && geometry (hd1) && map (hd1) (hd0) map --hook write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/images/winsetup.iso;floppy,vmem=find:/images/firadisk.img;\n\0 chainloader (222) Drawback: ISO images has to be edited. Benefit: ISO images has to be edited. Next step would be include firadisk in ISO image. Well both are nice. One is nicer at given hardware, BIOS and requested approach. There is no better one. Can you name some examples? How many internal and external disks does exists? This assumes one USB drive and install to first internal hard disk.first internal hard disk as for BIOS sort order at USB boot. I've no experience. Ilko solved this more clearly.

Trim won't work at a nForce 4 chipset running XP/2003. Use a SSD with medium garbage collection. I recommend a Samsung 470 at given hardware. Or use a Intel 320.

WinPE with SystemRoot on C:\ (or anything)

I like this too. Did you tried the sorted ISO file? Haven't used this in conjunction with RyanVM updates. Technically you don't loose the WinVBlock driver. Underling USB connection is installed. The existing USB connection is lost and a new one builded. This part kills connection to WinVBlock driver. No, second USB boot is required still.

Actually it's insane. A commercial software called Universal Restore dosn't support basic functions. They should be ashamed. Strange world: http://kb.acronis.com/content/8814 Acronis does distribute a MS KB311272 devcon.exeUSB_batch.bat Technically a nice approach. But why a fixed letter c: at a univeral restore? There may be no c: at all. At a similar ACPI machine shutdown may work. Or drink one or more cup of tea, actually power down the system next. Registry should be saved then. To enable KB938596 settings, boot a PE and run a batch against offline windows c:\windows is a example, adjust to your configuration.suppress_PNP_UI_messages.cmd @echo off pushd %~dp0 rem suppress_PNP_UI_messages.cmd v0.01 rem created by cdob echo suppress Plug and Play-related UI messages echo http://support.microsoft.com/kb/938596/ echo. set SysRoot=\Windows if not %1.==. set SysRoot=%1 if not exist "%SysRoot%\system32\config\system" set /P SysRoot=Path to your SystemRoot folder on usb drive (e:\Windows\SysRoot): if not exist "%SysRoot%\system32\config\system" (echo Error: target not found &pause &popd &goto :eof) rem Windows Server 2003 and Windows XP 64 bit copy "%SysRoot%\system32\config\system" "%SysRoot%\system32\config\system_%random%.sav" reg.exe load HKLM\loaded_SYSTEM "%SysRoot%\system32\config\system" rem detect Clone control CurrentControlSet for /f "tokens=3" %%a in ('reg.exe query "HKLM\loaded_SYSTEM\Select" /v "Default"') do set /a ControlSet=%%a set ControlSet=00000%ControlSet% set ControlSetNNN=ControlSet%ControlSet:~-3% echo. &echo ControlSet "%ControlSetNNN%" used. set Services=HKLM\loaded_SYSTEM\%ControlSetNNN%\Services reg.exe add "%Services%\PlugPlay\Parameters" /f /t REG_DWORD /v "SuppressUI" /d 1 reg.exe unload HKLM\loaded_SYSTEM rem Windows XP 32 bit versions copy "%SysRoot%\system32\config\software" "%SysRoot%\system32\config\software_%random%.sav" reg.exe load HKLM\loaded_SOFTWARE "%SysRoot%\system32\config\software" set Software=HKLM\loaded_SOFTWARE reg.exe add "%Software%\Policies\Microsoft\Windows\DeviceInstall\Settings" /f /t REG_DWORD /v "SuppressNewHWUI" /d 1 reg.exe unload HKLM\loaded_SOFTWARE

Yes, it's about cmd line processor. You may run reg.exe or regedit.exe. Load a 2003 system hive from hard disk, change 2003 settings and unload the hive. Reboot to hard disk next. At this point you use Windows 7 PE. USB keboard does work. I don't know either: what's first: PNP or "Agree the license"? Did you used a USB keyboard at old motherboard in the past? Another approach: enable USB drivers and USB HID devices early. Use Universal Imaging as a key word. http://www.911cd.net/forums//index.php?showtopic=22092 http://www.911cd.net/forums//index.php?showtopic=19397 A search revealed too http://kb.acronis.com/content/8814

Boot Windows 7 at AHCI mode. Run regedit. Set service pciide to start=0

I'm lost: which BIOS setting do you use now? Do you use IDE, AHCI or RAID? Do you use RAID at Intel controller and IDE at Marvell controller? The Chicken or the egg causality dilemma: USB controller drivers are not loaded. And no USB keyborad drivers. Windows default drivers are sufficient at USB keyboard. Yes, you may ignore this part.Do you have a Windows 7 or Windows 8 DVD available? Boot, press Shift-F10. Can you read 2003 files? Apply SuppressUI to 2003 at hard disk. And verify Umpnpmgr.dl version. http://support.microsoft.com/kb/938596/en-us 2003 should install USB controller, USB keyboard and USB mouse at next boot.

Do you have a full backup? Which keyboard and mouse do you use? PS/2 or USB Can you boot a PE from USB? Or can you boot Windows 8 Developer from USB? I would boot a external operating system. And fix CriticalDeviceDatabase\PCI#VEN_8086&DEV_2822&CC_0104 And adjust mouse keyboard settings Next reboot should work. A repair installation is not required.

Nvgts.sys is a 32 bit driver. What about using nvgts64.sys at a XP 64bit ?

As indicated already: not required at 5 similar machines. Which machines do you use? Can you´list processor and chipset? The last years multi-core chipset are used. Kernel and hal is not a big matter anymore.

I don't understand. Which approach do you compare? Why do you have to back up something before? Which part is overwritten? Suggestion was to add a boot manager at external hard disk. As for testing: add grub4dos to \boot\bcd at external drive. Windows boot rely on BIOS drive numbers. Boot from external USB hard disk, map internal drive to drive 0x80 and continue internal drive. Which grub do you use?It's a mistake to install grub to MBR at multi boot internal hard disk. Use a dump MBR, but use several partitions. Include different boot loader to different partition boot codes. Grub dosn't support windows boot loader, kernel or similar. Grub4dos does support a windows boot loader. Use grub or grub4dos as you like. Where do you like to install grub4dos or grub? Use windows default MBR and PBR at internal single boot hard disk. Can you clarify: What's overall requirement? Which operating systems do you like to install? Which hardware do you use? Can you change BIOS boot order: default internal and external at manual choice?