cdob

Grub4dos can chainload ntldr, setupldr.bin and bootmgr. This offfers more possibilities. .Back up is a good idea.But why do you like to change MBR at all? Keep default MBR. MBR dosn't call a raw location. Partition boot code of primary active partition is called. Neither use a raw location to load bootmgr. Or a edited partition boot code may load grldr.

Or keep bootmgr as default boot loader, but add grub4dos to \boot\bcd. \boot\bcd dosn't contains drive letters anyway.Add grub4dos, edit menu.lst: swap USB and internal hard disk.

Can you change BIOS boot order? Internal hard as default boot. And select a USB device at pressing a hot key like F12? Or use another boot loader at external device? Clarify previous steps more clearly. How did you prepare USB drive? Which hardware do you use? Which situation does relate bcdedit output? Do you use different machines? Do you use a single machine? Which machine do you use? Which OS is booted? Did you clone a hard disk? Which internal, external disks and other storage devices exists? Which partitions does exist at hard disks? Which drive letters go to this ones? Broken input, broken output. Do not change path.

XP is designed to launch setup.exe. A fake setup.exe is used to lauch setup.cmd. Source code is at WinSetup\files\winsetup\PyronSetup\setup.c Pyron created this approach This version calls presetup.cmd. A new name was chosen to keep old solutions working.

Which file system do you use at USB stick? Do you use FAT, FAT32, NTFS or another one? Run syslinux.exe, write bootsector output to a file. Run bcdedit.exe, add this file to bcd store.

Clarify connected hardware in addition. Which hard disk (manufacuter, modell, capacity, SATA speed) or optical drive do you use?

That's another case. Pre-Activation relates to

The manufactuer describes: Preserving OEM Pre-Activation when Re-installing Windows XP http://technet.microsoft.com/en-us/library/bb457078.aspx

Yes, use grldr as boot file: -bd:\super_aio\boot\syslinux\grldr Test this at available BIOS. You may use a CD-RW for basic testing. Use a current version instead http://code.google.com/p/grub4dos-chenall/downloads/list Grub4dos is case sensitive at case sensitive file system. Use something like chainloader /bootmgr || chainloader /BOOTMGR Select file systems and extensions for your collection. That's difficult decission. There are virtual machines for testing.

http://support.microsoft.com/lifecycle/?LN=en-gb&C2=1173 Extended Support End Date: 08/04/2014

Some sort of progress bar. Poor man approach: echo . start /wait echo .. start /wait echo ... start /wait echo .... start /wait

There is a Install Windows from USB section too. http://www.msfn.org/board/forum/157-install-windows-from-usb/ BSOD 0x7B refers to boot drive too. That's the USB Flash Drive. Do you like to copy a ISO file to USB Flash Drive? OS manufacturer provided software dosn't support this. There is no default ISO file driver. This task is impossible to solve. Contrary there are third party open source ISO file driver. And some Flash firmware can simulate a USB CD-ROM drive. Read the above link. OS manufacturer provided software does find single files at a USB Flash Drive. That's possible within OS manufacturer provided software.

Yes, that's part of fixBoot.USB. No, it's not normal at good hardware. That's required at USB boot unfriendly BIOS only

Which hardware do you use? Motherboard, BIOS, USB port at motherboard, USB drive Try edit floppy image, txtsetup.oem and enable fixBoot.USB

A idea, exptect a battery match a laptop. reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{72631E54-78A4-11D0-BCF7-00AA00B7B32A}\0000" && echo battery foundThis assumes a new installation, not a image restore. Or if a image is restored: image dosn't contain HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{72631E54-78A4-11D0-BCF7-00AA00B7B32A}\0000 already However, I doubt this command describe laptop or desktop always. Testing is required.

There is a zip file too: Intel® Rapid Storage Technology F6 Driver Diskettes Operating Systems: Windows 7, 64-bit http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2101&DwnldID=20216&ProductFamily=Chipsets&ProductLine=Chipset+Software&ProductProduct=Intel%C2%AE+Rapid+Storage+Technology〈=eng

I don't use EasyBoot. The boot sector file loads a file \i386\setupldr.bin.If you use another file name, you have to change the boot sector file. Patch the boot sector file accordingly. Yes, patch IX64 if you use a directory IX64. Or use another bootmanager, load setupldr.bin directly. Setupldr.bin contains a string winnt.sif. Patch a second renamed setupldr.bin (\IX64\setupldr.rep ): change winnt.sif to winnt.rep Patch a second boot sector file to load \IX64\setupldr.rep: change i386 to IX64 and change setupldr.bin to setupldr.rep.

Use a slightly different approach: SetupSourcePath and BootPath. Use one directory for unanttended and repair, adjust winnt.sif. Patch a second setupldr.bin to winnt .rep. unattended: use file \XP64\AMD64\WINNT.SIF repair use file: \XP64\AMD64\WINNT.REP As for 32 bit use a second setupldr.bin too and two files I386\WINNT.SIF I386\WINNT.REP

Which ahcix86.sys version do you use? Which BIOS setting do you use?

Did you disable mass storage controller at BIOS? Then use usbhub.sys from XP Embedded. http://msdn.microsoft.com/en-us/library/ee428799.aspx http://www.microsoft.com/download/en/details.aspx?id=11196 <POSready2009_CD.iso>\Setup\USB\usbhub.sys

Basically follow this Vista example Approach does works at win 7 too.

Yes, that's strange. SB8xx folder contains a txtsetup.oem. Contrary there is no txtsetup.oem at SB6xx, SB7xx. SB8xx txtsetup.oem refers to: PNP driver file SBDrv\SB7xx\RAID\XP\ahcix86.inf refers e.g. AMD dosn't provide XP textmode drivers for PCI\VEN_1002&DEV_4380&SUBSYS_* and PCI\VEN_1002&DEV_4381&SUBSYS_* What's going on?

Add and Remove Drivers Offline http://technet.microsoft.com/en-us/library/dd744355%28WS.10%29.aspx Example: NEC/Renesas USB3.0 Host Controller http://www2.renesas.com/usb/en/index.html Create a directory c:\mount Get NEC/Reneseas USB3 drivers. http://www.gigabyte.com/products/product-page.aspx?pid=3315 http://www.station-drivers.com/page/nec.htm Expand files and move driver files to C:\usb3\ Result: C:\usb3\Files\x86 C:\usb3\Files\x64 A wim file can contain several images. Apply drivers to all images. First read wim image contents Dism /Get-WimInfo /WimFile:U:\sources\boot.wim U:\ refers your Windwos 7 source drive at a writable media. Adjust this to your drive letter. Read your output, example could be Should refer to boot.wim index 2.Mount the boot.wim Dism /Mount-Wim /WimFile:U:\sources\boot.wim /Name:"Microsoft Windows Setup (x64)" /MountDir:c:\mount Add the drivers Dism /Image:C:\mount /Add-Driver /Driver:C:\usb3\Files\x64 Unmount Dism /unmount-Wim /mountdir:c:\mount /commit In addition feel free to repeat the steps for all images inside boot.wim, install.wim and <install.wim>\Windows\System32\Recovery\winRE.wim. That way USB3.0 drivers are available after installation and at a recovery.