cdob

I'm a human only and the crystal ball is empty Well maybe another kernel, hal or ACPI configuration does interfere too? Device tree is a good explanation in general: does match in most cases. Of coure there exeptions. Given removable USB Stick direct attached to USB port: ParentIdPrefix 7&*&0 Driver stack: 1 ntoskrnl.exe, hal.dll 2&daba3ff&0 acpi.sys 3 pci.sys - no ParentIdPrefix 4&11cdd0bd&0 usbehci.sys 5&38c8e674&0 usbhub.sys 6 usbstor.sys - no ParentIdPrefix 7&776bc3a&1 disk.sys Next remove USB Stick, attach a USB hub. And insert USB Stick to the USB hub. Device tree is one step deeper: I expected ParentIdPrefix 8&*&0 However ParentIdPrefix stays at 7&*&0. A double usbhub.sys dosn't matter, driver is loaded and used once. I recogiced strange behaviour using a USB controller without a SerialNumber. This is a fixed USB hard disk. MountedDevies does NOT use ParentIdPrefix. Windows PNP the hard disk for each USB port. [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_05e3&Pid_0702\5&38c8e674&0&2] "Service"="USBSTOR" "ParentIdPrefix"="6&27caf906&2" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_05e3&Pid_0702\5&38c8e674&0&5] "Service"="USBSTOR" "ParentIdPrefix"="6&28d260fd&2" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{53f56307-b6bf-11d0-94f2-00a0c91efb8b}\##?#USBSTOR#Disk&Ven_SAMSUNG&Prod_HM160HC&Rev_0811#6&27caf906&2#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}] "DeviceInstance"="USBSTOR\\Disk&Ven_SAMSUNG&Prod_HM160HC&Rev_0811\\6&27caf906&2" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{53f56307-b6bf-11d0-94f2-00a0c91efb8b}\##?#USBSTOR#Disk&Ven_SAMSUNG&Prod_HM160HC&Rev_0811#6&28d260fd&2#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}] "DeviceInstance"="USBSTOR\\Disk&Ven_SAMSUNG&Prod_HM160HC&Rev_0811\\6&28d260fd&2" Recogince the main difference: USB hard disk, ParentIdPrefix 6&28d260fd&2 usbstor.sys. (6th driver in stack) USB stick, ParentIdPrefix 7&776bc3a&1 disk.sys (7th driver in stack) Idea: Drive SerialNumber and relating windwos configuration (GlobalDisableSerNumGen, IgnoreHWSerNum*) may be importand. A USB stick with a serial number get ParentIdPrefix 7&*&0 at the same USB port. I don't pocess a USB stick without a serial number and can't test this. Finally: yes, the driver stack does set ParentIdPrefix N&*&*. Windows may connect ParentIdPrefix to different drivers. True reason is unkown. Added, more ideas: A addional (non windows default) driver in stack may cause ParentIdPrefix 8&*&*. A default windows installation set ParentIdPrefix 7&*&0. A end user install some addional USB driver into driver stack: ParentIdPrefix is changed to 8&*&*.

As far as I know VirtualBox mount the USB stick to a virtual internal hard disk.There are no USB drivers used. This does not test USB boot. Installation way work anyway, but test internal hard disk behaviour. I'm using VMWare Player, mount the USB drive, boot a PLoP Boot Manager floppy image and continue USB boot. Windows setup use USB drivers for the USB drive. This does test USB boot. Try file names used by a default XP CD: that's 8.3 names.Long names are renamed at installation. The CD does contain file name aaclient.mui, not aaclient.dll.mui.nLlite breaks XP defaults A long name is used at CD. Try a 8.3 file name at ISO image. A XP default CD dosn't contain SetupSourceDevice, delete this line.And if you use one hard disk, dosn't use grub4dos hd swap.

Multiple boot partitions on the same drive: http://www.boot-land.net/forums/index.php?showtopic=7138 As far as I remember, XP maps (hd0,0) at USB flash drive. Maybe it't time to split this multi partitions posts.

Use clean source files. Don't integrate IE7. As ilko_t requested already: which txtsetup.sif and menu.lst do you use? Which hardware do you use?Try fixBoot.USB, compare first message and http://www.msfn.org/board/index.php?s=&amp...st&p=888710 Did you try RAM load that way?How do you integrate the usb flash drive? A virtual physicaldrive isn't a USB drive anymore.

This confirms: another driver usbstor.sys result another "ParentIdPrefix". This knowledge is new. This is another surprise.The Realtek driver does interfere a USB stick too. This is rather strange. If need be, you may create one migrate.inf, use different letters for USB Stick and SD card. Why does Acer offer a USB SD driver at all?You may intergrate the driver again as PNP driver, textmode setup use usbstor.sys ParentIdPrefix. If you prefer a most confusing configuration: Add the Realtek driver as a textmode driver. You get very funny results again at different machines. Avoid this driver! No, the USB port dosn't matter. Congratulations.

A NON windows default driver is used. This driver cause a ParentIdPrefix.A windows default driver may cause a different ParentIdPrefix. Or the same. Currently at textmode setup default drivers are used. Can you confirm: open device manager, change view per connection. Is the SD card connected to this Realtek Card Reader(0159)? Can you make another XP installation? Remove the Realtek Card Reader(0159) driver (rename RTS5121.inf RTS5121.inf.txt). Install XP again. Which driver and ParentIdPrefix goes now to USB\VID_0BDA&PID_0159 ?

Which windows source files do you use? Do you use a OEM verison? Did you add any custom drivers? How did you add drivers? Did you add Realtek Card Reader drivers as textmode drivers? Did you add Realtek Card Reader drivers as PNP drivers? Does current XP use Realtek Card Reader drivers? devcon.exe driverfiles *http://support.microsoft.com/kb/311272/ Does a default XP USB massstorage driver support the internal reader? Does a default XP USB massstorage driver result one ParentIdPrefix? Does Realtek Card Reader drivers result another ParentIdPrefix?

Once again. It's rather confusing still. Which laptop give this result?Can you run usbHistory.exe at both laptops? Is this (3) the internal USB card device? http://www.msfn.org/board/index.php?s=&amp...st&p=891644Is this a external USB card device? Did you used one SD card at two different Card devices? Try one migrate.inf for the "AsusEee" and another migrate.inf for the "Acer5738". Yes, a BIOS update is recommended http://customercare.acer-euro.com/customer...&IType=JV50 More strange, Acer offers Realtek Card Reader drivers. RTS5121.inf contain the string "USB Mass Storage Device". Which OS do you use at "Acer5738" currently, XP, Vista or other? Does you windows use a windows default driver or a realtek RTS5121.sys driver?

The Acer5738 does map the drive different, e.g. as a USB floppy. Or the BIOS set a fixed drive to the SD card at boot. Hence the blank screen at ISO RAM load approach too. Does exist a BIOS option to force USB hdd to the SD Card?

Maybe a bad burned media, e.g. low quality media or half broken writer. Try ImgBurn again. Fix the error source.

Overwrite old files with the new ones.This was the hint at Post #16. ilko_t explained this already. To clarify, can clarify again? I like to know the reason, may be a fix is required. How did you prepared the 2GB, 4GB and 8GB drive? Did you copy files from 2GB to 4GB drive? Did you run MULTIBOOT_USB_10 to each drive? A correct migrate.inf should be added that way?

Do you use always the internal Card reader? How is the internal Card reader connected? Does this internal Card reader use a USB connection? Do you use a external USB Card reader? Which ParentIdPrefix does current windows use at Acer5738? Which ParentIdPrefix does exist at migrate.inf? Which ParentIdPrefix does ùse a freshly installed windows? BTW: to enhance the confusion. There is a new firadisk 0.0.1.14 http://www.boot-land.net/forums/index.php?...ost&p=83637

Given a 4GB SanDisk SD Plus USB, this is both a SD card and a USB stick. USB SD card reader, no card inserted: XP assign a drive letter F: The drive letter goes to the card reader, not the SD card itself. ParentIdPrefix: 7&776bc3a&1 USB SD card reader disconnected. SD card inserted to another USB SD card reader. XP assign a drive letter F:, however MountedDevices is changed. ParentIdPrefix: 7&524fc66&0 USB SD card reader disconnected. Flash card connected as USB stick: XP assign a drive letter F:, MountedDevices is changed again. ParentIdPrefix: 7&3157a48c&0 The same SD card may use different ParentIdPrefix. Migrate.inf goes to the SD card storage controller, not to the SD card. Which laptop do you use to prepare the SD card? Which laptop do you like to install XP to?

OEMScan - Automated Multi Manufacture Pre-Activation Utility http://www.msfn.org/board/oemscan-automate...ity-t82638.html

Read johnhc's post to Disable OEM Preinstall in the Unattended Task Which USB floppy drive did you purchased? XP doesn't support all USB floppy drives: http://support.microsoft.com/kb/916196 Which HardwareID goes to your drive? To include missing HardwareID read http://www.msfn.org/board/using-f6-driver-...ppy-t82711.html

@kDn It's fun to read http://forum.ru-board.com/ with google translation. I don't understand some translation parts. I understand: a Asus A6Q00VM, Pentimum M call, I915 chipset does require fixBoot.USB. I expect a USB boot nightmare (Dell Dimension 5150) would require this too. fixBoot.USB. does require a addional reboot and is disabled by default therefore. I may change fixBoot.USB settings at setup.cmd: detect missing USB drive Understood finally, I'll add too: if exist c:%ISO_file_search% set reassign=true Need some time. This includes mkISO_RAMload_sort.cmd, read below. Yes, winnt.sif [MassStorageDrivers] and floppy txtsetup.oem fails. Driver not found. Another idea: write to winnt.sif inside RAM ISO, disable [MassStorageDrivers]. Recovery Console: Sort some files at mkISO_RAMload_sort.cmd rem sort some recovery console files FOR %%a in (autochk.ex? autofmt.ex? kbd*.dl?) do ( call :sort_boot ./%boot_directory% %%a) if exist ASMS echo ./%boot_directory%/ASMS/* -7000>>%sort_lst%And load first 20mb: map --mem (0xFE)+10000 (0xFF) Does mentioned recovery console start by default? Do you have to press F10 at F6 message? Compare: Adding Windows Recovery Console, Without having to press F10 or R in setup http://www.msfn.org/board/adding-windows-r...le-t139069.html There was a question about mkisofs -input-charset utf-8 and -duplicates-once. http://forum.ru-board.com/topic.cgi?forum=...mp;start=1680#3 http://forum.ru-board.com/topic.cgi?forum=...p;start=1720#19 I don't understand clearly: does this refer to windows or another operating system? Alex Kopylov (former bootcd.ru) added -duplicates-once and -force-uppercase in 2004. This mingw32 version isn't supported since 2004. There is no charset utf-8. Mkisofs uses iconv nowadays http://en.wikipedia.org/wiki/Iconv. And cygwin file cygiconv-2.dll does offer charset utf-8. Integrate -duplicates-once source code to current cdrtools version and compiled at cygwin: Source code cdrtools-2.01.01a66-bootcd.ru-mkisofs.tar.gz Win32 binaries cdrtools-2.01.01a66-bootcd.ru-mkisofs.7z This version support -input-charset utf-8 and -duplicates-once, however russian characters are not tested. @robekia Sorry, no more idea. There is a strange BIOS.

Don't worry. Txtsetup.sif is used at textmode setup only. This name is displayed at textmode part. Driver is installed at gui mode. Settings and name are used from Iaahci.inf and iastor.inf. There is a nice displayed device manager. Use txtsetup.sif [SCSI] ahcix86 = "AMD AHCI Compatible RAID Controller-x86 platform" iaStor = "Intel® SATA AHCI/RAID Controller"

Windwos support one volume-name at CD. Do you need different volume names?To maintain the original CD folder structure is possible, if there are tiny differences: different winnt.sif or similar. You have to use another folder structure, if two OS contains major differences. This old release dosn't support XP SP2. BCDW 2.01a support XP SP2 x32. http://www.wolfgang-brinkmann.de/bcdw_e.html However no idea about XP x64, this may work or not. To clarify, that's two $OEM$ folders. The root of the dual-boot-installer is not the root of CD.A XP x64 example, slightly different to flyakite's guide: http://www.msfn.org/board/index.php?s=&amp...st&p=814566 You may use \XP_1\$OEM$ and \XP_2\$OEM$

Windows setup is more picky than windows. Installation may reject the hard disk anyway, partition detection hang at more reasons.Can you try a installation CD? Did you zero the hard disk first? e.g. WinDlg http://support.wdc.com/download/windlg/WinDLG.zip Or a ACPI issue. Try press F7 at F6 message. Disconnect as much hardware as possible. Or try different map (hdN) (hdN). Actually no idea, I don't use a ACER5738.

Sorry late answer, got distracted. Some vacation preparations: I'm offline next december.Diff are spaces in most cases $ diff setup.cmd setup.cmd.edited 44c44 < echo presetup log %date% %time% > presetup.log --- > for %%a in (presetup.log) do if not exist %%a echo presetup log %date% %time% > presetup.log 49c49 < for %%a in (reg.exe) do if not exist %%a echo Error: missing file: %%a >>presetup.log --- > for %%a in (reg.exe) do if not exist %%a echo Error: missing file: %%a >> presetup.log 53c53 < echo presetup fixDrive.USB > presetup.log --- > echo presetup fixDrive.USB >> presetup.log 58c58 < if /I not %SystemDrive%.==C: echo setup SystemDrive %SystemDrive% >>presetup.log --- > if /I not %SystemDrive%.==C: echo setup SystemDrive %SystemDrive% >> presetup.log 62,63c62,65 < if exist c:\Inst\XP_*.ISO set reassign=true < if exist c:\Inst\2003*.ISO set reassign=true --- > > set ISO_file_search=\Inst\XP_RAM.ISO > if exist ISOimage.ini for /f "eol=;" %%a in (ISOimage.ini) do if not %%a.==. set ISO_file_search=%%a > if exist c:%ISO_file_search% set reassign=true 68c70 < echo reg delete MountedDevices \DosDevices\C: and \DosDevices\%SystemDrive%>> presetup.log --- > echo reg delete MountedDevices \DosDevices\C: and \DosDevices\%SystemDrive% >> presetup.log 85c87 < echo presetup fixBoot.USB > presetup.log --- > echo presetup fixBoot.USB >> presetup.log 106c108 < if not exist %%a echo Error: missing file: %%a >>presetup.log) --- > if not exist %%a echo Error: missing file: %%a >> presetup.log) 129c131 < if defined sourcepath (echo sourcepath %sourcepath%)>>presetup.log --- > if defined sourcepath (echo sourcepath %sourcepath%) >> presetup.log 143c145 < echo search ISO file "%%i:%%j">>presetup.log --- > echo search ISO file "%%i:%%j" >> presetup.log 149c151 < (echo Error: no ISO file found &echo.)>>presetup.log --- > (echo Error: no ISO file found &echo.) >> presetup.log 153c155 < echo found ISOfile %ISOfile%>>presetup.log --- > echo found ISOfile %ISOfile% >> presetup.log 156c158 < echo mount ISOfile %ISOfile% >>presetup.log --- > echo mount ISOfile %ISOfile% >> presetup.log 165c167 < echo.>>presetup.log --- > echo. >> presetup.log 167c169 < echo.>>presetup.log --- > echo. >> presetup.log 171c173 < (echo. &echo mount ISOfile V:\XP_RAM.ISO) >>presetup.log --- > (echo. &echo mount ISOfile V:\XP_RAM.ISO) >> presetup.log 174c176 < echo.>>presetup.log --- > echo. >> presetup.log 176c178 < echo.>>presetup.log --- > echo. >> presetup.log 205c207 < echo call presetup.cmd >>presetup.log --- > echo call presetup.cmd >> presetup.log 208c210 < echo end presetup.cmd >>presetup.log --- > echo end presetup.cmd >> presetup.log 222c224 < (echo. &echo run setup CmdLine: %CmdLine% - %date% %time%)>>presetup.log --- > (echo. &echo run setup CmdLine: %CmdLine% - %date% %time%) >> presetup.log 233c235 < (echo. &echo prepare USB boot configuration %date% %time% )>>presetup.log --- > (echo. &echo prepare USB boot configuration %date% %time% ) >> presetup.logI like to keep this lines: if exist c:\Inst\XP_*.ISO set reassign=true Idea, USB drive got letter c:, let windows reassing drive letters. Internal hard disk may get c: or windows assign c: for USB again. Do you have different results? Can you describe the conditions? Thanks, I missed a > at 'echo presetup fixBoot.USB > presetup.log'. Yes, use 'echo presetup fixBoot.USB >> presetup.log' I'm glad to keep the fixBoot.USB section, actually I might have deleted this part. Now this is usefull at some conditions. Do you have some examples? Which systems dosn't initialize USB properly. Another idea for multiple installation: add several floppy images XP_INST.IMA to multi boot ISO image. Load the ISO image to RAM first, and load a appropiate floppy image from ISO image next. Windows setup hang at partition detection/mounting. Does internal hard disk contain partitions already? Does a Memory stick 8GB/1GB/4GB work at the ACER5738 ?

You can't use a folder name boot\pro1.Contrary you may add directory I386 to PRO1. Set SetupSourcePath and BootPath at txtsetup.sif. That's similiar to flyakite and different. SetupSourcePath = "\PRO1\" BootPath = \PRO1\I386\ There are three fixed file names to define basic boot: setupldr.bin, ntdetect.com and txtsetup.sif Layout at DVD Your boot sector file or boot loader load file \PRO1\SETUPLDR.BINThe result is more organized, one folder at root per OS. That's a nice idea too.

Can you boot at IDE mode still? Copy over the good ahcix86.sys to system32\drivers again.

Sorry for the answer, requires a lot of reading and work.I don't know a solution to load direct Recovery Console with single files at CD. Contrary you may create a proper hard disk ímage. Load the hard disk image with your multi boot loader. That way the Recovery Console start by default, no need to press F10. /cmdcons parameter http://www.boot-land.net/forums/index.php?...ost&p=18878 There is a bootsector at a partition, but not at CD/DVD. Setupldr.bin dosn't support /cmdcons. Several different approaches are dicussed at http://www.boot-land.net/forums/index.php?showtopic=5316 There are different soltions to load the disk image nowadays 2003 SP1 setupldr.bin isolinux memdisk: winvblock http://www.boot-land.net/forums/index.php?...ost&p=77450 grub4dos map: firadisk http://www.boot-land.net/forums/index.php?showtopic=8804

PeToUSB is used to format the USB drive. A addional batch does copy XP installation files to USB drive. How do you run nLite currently? Open VMBox, run nLite, create a ISO image. Transfer this ISO image to Ubuntu or USB Pendrive. Burn the ISO image at Ubuntu.

PeToUSB dosn't support XP installation.http://gocoding.com/page.php?al=petousb The Genius Hackers distribute a outdated usb_prep8.cmd. The source is not mentioned, that's a bad example. This has been developed at msfn http://www.msfn.org/board/install-windows-usb-f157.html This maybe a BIOS issue. There is USB FDD floppy emulation and USB HDD hard disk emulation. Use USB HDD hard disk emulation for the USB Drive. Or CHS to LBA translation fails. Try the LBA option at PeToUSB. Create a ISO image at nLite. Use ImgBurn to burn the image to a CD or a DVD media.Use high qualtiy media at a decent speed.