ilko_t

Please run this in command prompt on the machine in question and post the output: sc query rdummy Then attach USB_root\$WIN_NT$~BT\winnt.sif, removing any personal data you may have in it, including windows serial number/id.

You need to reboot it once in order the driver responsible to be uninstalled. XP what Service Pack was the source?

Did you test on real hardware or on virtual machine? Did you try to prepare the USB stick with the latest WinSetupFromUSB and see if USB stick gets letter U:? Attach your current migrate.inf.

You should not have copied the files from USB stick to the USB hard disk manually, for the same time WSFUSB would have prepared the stick with rdummy.sys.As for the suggestion- the program is not intended to fix previously prepared USB disk/stick, except the part for synchronizing sources. There are so many changes currently made to the source, so checking each of them becomes too much of work for the purpose. Much easier would be to format the disk and prepare it properly. Please post contents of the USB disk, which files did you patch and did you put XP setup when ERD files were already there.

If you have fixed disk (normal USB hard disk) then radio button should be at FIXED DISK, wasn't it selected automatically? This way the program will put rdummy.sys driver to the XP installation files making the necessary changes in txtsetup.sif.

Just to clarify- if BIOS supports booting from USB, giving disk number to the USB the following is possible and working: Start internal disk Load grub4dos USB disk is (hd1) and accessible Start PartedMagic for example from the USB disk. So in this case PLoP is not needed.

Would be simple, yes, there is workaround, but there are number of limitations and to know if that suits your needs, we need to know what you are trying to boot, including what's on the USB stick.Plus your question could mean "Can I boot USB stick if my BIOS/motherboard do not provide USB boot". How would we know what you mean? To boot BIOS hard disk device you cannot use NTLDR, you can use it to chainload grub4dos, the chainload disk MBR, bootsector on partition on disk, or another bootloader on partition. But in this case HD numbering is as BIOS provides it- internal HD is disk0 (you booted from it), USB (in case on other disks)- disk1. Number of applications would refuse to start, including XP setup when NOT launched from first hard disk as BIOS reports it. Grub4dos provides ways to "shift" hard disk numbering, but you will fall into other difficulties. So use BIOS boot options and select USB when needed, unless you want to learn more.

What do you need to boot from that USB disk? Is the motherboard capable of USB boot? What exactly are you trying to achieve? I am sure there are way better approaches if you answer the questions above. To answer- USB drivers are not loaded at that stage, NTLDR works with whatever BIOS provides, unless a driver is loaded by (renamed to NTBOOTDD.SYS and using SCSI syntax in BOOT.INI). http://blogs.msdn.com/ntdebugging/archive/...the-second.aspx

First 2 are not present, as is the third one.Under HKLM\SYSTEM\ControlSet001\Enum\STORAGE\ there are only Volume and VolumeSnapshot subkeys. The equivalent of the third on would be: HKLM\SYSTEM\ControlSet001\Enum\STORAGE\Volume\_??_USBSTOR#Disk&Ven_JetFlash&Prod_TS1GJF110&Rev_0.00#5ad00f612a5447&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

Here is how ParentIDPrefix generated in 2000, most likely in XP too: http://bbs.driverdevelop.com/read.php?tid=96099 http://translate.google.com/translate?hl=e...3Den%26num%3D50

Have you had a look what's inside \WinSetupFromUSB\MULTIpartitionUSBstick\ ? This works on XP 32 bit windows only. edit: How to use it- 1) unplug your USB stick 2) launch InstallStartDummyDisk.cmd 3) Plug USB stick 4) Partition and format it from Disk Management console, setting the first partition as active 5) Put whatever you want on it. If putting XP setup make sure you move the radio button force disk type to REMOVABLE in program interface. 6) When no longer need this USB stick to be presented to Windows as normal fixed disk, thus allowing work with multiple partitions, unplug USB stick, launch StopRemoveDummyDisk.cmd and restart your computer.

Hiren's BCD is WAREZ and you won't get any support about it here

1. Prepare the stick with XP setup files as usual. 2. Download ubcd50b12.iso 3. Copy it to root of USB stick 4. Open up menu.lst in USB root in Notepad and add these lines at the bottom: title Boot UBCD 5 beta 12 ISO find --set-root /ubcd50b12.iso map /ubcd50b12.iso (0xff) || map --mem /ubcd50b12.iso (0xff) map --hook root (0xff) configfile /ubcd/menus/grub4dos/main.lst Simple enough?

http://www.msfn.org/board/index.php?showtopic=116766 Q2/A2, missing winnt32.exe is a good sign the option mentioned above had been applied. This is frequently asked question indeed

I would null the first 100-200 sectors, replug the stick and reformat it with HP format tool in NTFS to start with. Refer to this post for details:http://www.msfn.org/board/index.php?showto...st&p=852517

1) Sure, just go ahead 2) According to ISO size you may need to extract the ISO, copy it to USB and add Syslinux bootsector to the USB stick. This would work in FAT16/32 partitions only, which downside is that are slowing down Text mode files copy part of XP setup a lot, compared to using NTFS. Choice is yours, multiple partitions in the flash drive is also an option- first one NTFS for XP setup, second one FAT16/32 for Backtrack. 3) You'd better use the beta of vers. 5, which can be loaded as ISO: http://www.boot-land.net/forums/index.php?showtopic=7312 IF you want to stick with vers. 4, then extract the ISO somewhere, select Syslinux option and browse to the directory where you extracted it. Not quite sure if would work on NTFS partitions. Here are also some options: http://www.boot-land.net/forums/index.php?...486&hl=ubcd If you need further details please open another topic.

To remind you- there were some attempts to use MS RAMDISK.SYS: http://www.msfn.org/board/index.php?showtopic=81788 http://www.msfn.org/board/index.php?showto...st&p=776205

Lets make it clear The point is to prepare USB stick with XP setup files under Vista/7, where the keys in MountedDevices cannot be used right away to create migrate.inf. In other words- running MkMigrateInf.cmd under 7 (and most likely Vista too) produces migrate.inf file, which is not applied during XP setup due to the different values in MountedDevices and USB stick gets letter different than U:.

Short answer- no with some little hopes here. Long answer- http://www.boot-land.net/forums/index.php?showtopic=8076 and the links within.

That was the output from ListUsbDrives under XP SP3. Here is output from the same program under Windows 7: ListUsbDrives V1.7.9.22 Lists attached USB drives and their USB port names for USBDLM Freeware by Uwe Sieber - www.uwe-sieber.de Can use the file usb.ids from [url="http://www.linux-usb.org/usb.ids"]http://www.linux-usb.org/usb.ids[/url] for USB device information Operating System = 6.1 SP0 type=1 suite=100 Win32 Current User = ilko LogonType = local Member of groups = HomeUsers, Administrators Admin = no Elevation type = limited MountPoint = G:\ Volume Label = --- Volume Size = 1 GB (NTFS) Volume Serial = C434-F898 Volume Name = \\?\Volume{e84fe82b-5925-11de-a126-001422e056f4}\ Partition Name = \Device\Harddisk1\Partition1 Bus Type = USB Drive Type = removable Device Types = --- NoMediaNoLetter = configure >= 3 INI Sections = --- Drive DevID = USBSTOR\DISK&VEN_LEXAR&PROD_JD_LIGHTNING_II&REV_1100\AA04015900000158&0 Ctrl DevID = USB\VID_05DC&PID_A640\AA04015900000158 Host Controller = Intel® 82801FB/FBM USB2 Enhanced Host Controller - 265C Volume DosDevName = \Device\HarddiskVolume5 Disk DosDevName = \Device\00000060 Removal Policy = surprise removal ('Optimize for quick removal') Partition Number = 1 of 1 Friendly Name = LEXAR JD LIGHTNING II Requested Power = 500 mA (bus powered) USB Version = 2.0 (high speed) USB Friendl. Name = LEXAR MEDIA JD LIGHTNING II USB Serial = AA04015900000158 USB Port Name = 5-8 MountPoint = H:\ Volume Label = --- Volume Size = 1 GB (FAT) Volume Serial = 90E4-5FE9 Volume Name = \\?\Volume{662b209a-59df-11de-9b1f-001422e056f4}\ Partition Name = \Device\Harddisk2\Partition1 Bus Type = USB Drive Type = removable Device Types = --- NoMediaNoLetter = configure >= 3 INI Sections = --- Volume DevID = STORAGE\VOLUME\_??_USBSTOR#DISK&VEN_JETFLASH&PROD_TS1GJF110&REV_0.00#5AD00F612A5 447&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B} Drive DevID = USBSTOR\DISK&VEN_JETFLASH&PROD_TS1GJF110&REV_0.00\5AD00F612A5447&0 Ctrl DevID = USB\VID_0457&PID_0151\5AD00F612A5447 Host Controller = Intel® 82801FB/FBM USB2 Enhanced Host Controller - 265C Volume DosDevName = \Device\HarddiskVolume6 Disk DosDevName = \Device\00000066 Removal Policy = surprise removal ('Optimize for quick removal') Partition Number = 1 of 1 Friendly Name = JetFlash TS1GJF110 Requested Power = 98 mA (bus powered) USB Version = 2.0 (high speed) USB Friendl. Name = USB Mass Storage Device USB Serial = 5ad00f612a5447 USB Port Name = 5-5 Search in Windows 7 registry for "C0E6684" or "16f722a4" returns no results.

Version 0.2.2 released. Please refer to the first post for download links.

The question is how to create acceptable/working migrate.inf on Windows 7/Vista out of the info in MountedDevices, where apparently ParrentIdPrefix is not present. Seems attachments in were not uploaded with my previous post, here are migrate.inf produced by MkMigrateInf_b.cmd for the same USB stick under XP and Windows 7. The latter does not work as expected, drive letter U: is not applied to the USB stick. migrateXP.inf migrate7.inf

The posted snippets are from HKLM\SYSTEM\MountedDevices --> DosDevices...and ParrentIdPrefix which obviously plays role is not present in 7/Vista.

It appears WIndows 7 (and most likely Vista) use other syntax for those keys in MountedDevices: XP: MountPoint = G:\ Volume Label = --- Volume Size = 1 GB (FAT) Volume Serial = 90E4-5FE9 Volume Name = \\?\Volume{35703e27-2c34-11de-b2dc-005056c00008}\ Partition Name = \Device\Harddisk1\Partition1 Bus Type = USB Drive Type = removable Device Types = --- NoMediaNoLetter = configure >= 3 INI Sections = --- Volume DevID = STORAGE\REMOVABLEMEDIA\7&C0E6684&1&RM Drive DevID = USBSTOR\DISK&VEN_JETFLASH&PROD_TS1GJF110&REV_0.00\5AD00F612A5447&0 Ctrl DevID = USB\VID_0457&PID_0151\5AD00F612A5447 Host Controller = Intel® 82801FB/FBM USB2 Enhanced Host Controller - 265C Volume DosDevName = \Device\Harddisk1\DP(1)0-0+8 Disk DosDevName = \Device\000000c0 Removal Policy = surprise removal ('Optimize for quick removal') Partition Number = 1 of 1 Friendly Name = JetFlash TS1GJF110 Requested Power = 98 mA (bus powered) USB Version = 2.0 (high speed) USB Friendl. Name = USB Mass Storage Device USB Serial = 5ad00f612a5447 USB Port Name = 5-8 ========================================================= MountPoint = H:\ Volume Label = --- Volume Size = 1 GB (NTFS) Volume Serial = 9088-DFCD Volume Name = \\?\Volume{35703e28-2c34-11de-b2dc-005056c00008}\ Partition Name = \Device\Harddisk2\Partition1 Bus Type = USB Drive Type = removable Device Types = --- NoMediaNoLetter = configure >= 3 INI Sections = --- Volume DevID = STORAGE\REMOVABLEMEDIA\7&16F722A4&1&RM Drive DevID = USBSTOR\DISK&VEN_LEXAR&PROD_JD_LIGHTNING_II&REV_1100\AA04015900000158&0 Ctrl DevID = USB\VID_05DC&PID_A640\AA04015900000158 Host Controller = Intel® 82801FB/FBM USB2 Enhanced Host Controller - 265C Volume DosDevName = \Device\Harddisk2\DP(1)0-0+a Disk DosDevName = \Device\000000c3 Removal Policy = surprise removal ('Optimize for quick removal') Partition Number = 1 of 1 Friendly Name = LEXAR JD LIGHTNING II Requested Power = 500 mA (bus powered) USB Version = 2.0 (high speed) USB Friendl. Name = LEXAR MEDIA JD LIGHTNING II USB Serial = AA04015900000158 USB Port Name = 5-7 Any ideas?

Hal.dll error is not related to integration of mass storage drivers