ilko_t

1. Did you have boot.ini, ntdetect.com and ntldr on the hard disk? They are hidden system files. 2. Did you install Windows to C: as listed during Text mode? 3. Did you have any other partitions on the internal hard drive? Which one is active? Is any of them hidden? 4. Post contents of \windows\system32\$winnt$.inf in the internal hard disk, hiding any sensetive information it may consist. You should be able to start freshly installed Windows booting from the USB stick and selecting Second part of Setup. 5. Zip and attach WinSetupFromUSB.log found in program's directory. If it's too short- backups are cab compressed in \backups folder in case you started the program again. Undoren.cmd is no longer used. Presetup is launched right before start of GUI mode, executes binifix5.cmd, which fixes boot.ini on C: and changes msdosinitiated to 0 in $winnt$.inf, thus preventing setup from deleting ~BT and ~LS folders. Something along that way failed in your case.

@gagagoogoo Don't give up Reformat the stick usign WinSetupFromUSB, make sure the radio button is on FIXED and prepare it as usual. Try setup again. Attach the new WinSEtupFromUSB.log file.

Can you post what it says about C: Partition - 1, disk 0 or 1 at what? There should be mentioned driver name as well.What hardware is this? Laptop? Model? Desktop? Motherboard model? What windows version are you installing? WinSetupFromUSB.log found in program's directory could be handy. Backups are in \backups\ folder, cab compressed edit: post a few more file names reported as missing.

You are right, as always. Clean explanation would be nice. However, wouldn't 6,7 and 8 & ParentIDPrefix & 0 cover all possible cases when USB/memory stick is prepared on 2k/xp/2k3 machine? This means 3 letters...

I meant radio button in WinSetupFromUSB, when you open the program you will see it. Anyway, if no references about rdummy in txtsetup.sif then most likely button was not used. Can you zip and attach with your next post txtsetup.sif in USB root? Can you take a picture of the partitioning screen and post it? Did USB stick take letter U:?

It's easier simply not to add it For those interested- trigger is in ~LS\I386\presetup.cmd- binifix5.cmd and /norepair option. Remove it and you will get USB repair line, if switch is present- USB repair option is not added.

Did you play with Removable/Fixed radio button in the GUI? Search txtsetup.sif in root for 'rdummy', is there anything?

Thanks cdob.Maybe add W: with 8&*&0 for cases when stick is prepared on machine using 7&*&0, and installed on machine using 8&*&0.

You are welcome You may replace \WinSetupFromUSB\files\winsetup\MkMigrateInf3.cmd with the new version. It will be used in the next version of the program.

What version of WinSetupFromUSB did you use? There should be more lines in presetup.cmd if any of the latest was used, unattended section should be fully supported, with some workarounds done by the program.

I meant funny like odd, strange, unusual, nothing interesting inside the T&C, should have been clearer.

It's in Russian, nothing funny there.Just tested it- seems like someone has translated/coded USB_prepare/multiboot suite, or hit the same troubles as we did and resolved them in the same manner... - Migrate.inf is used, SYSTEM\ControlSet001\Control\StorageDevicePolicies is set - BT and LS folders are renamed at SetupParams stage during GUI and renamed back at first logon. - boot.ini is recreated with fixed values during first logon - there is 'activate product' button, maybe it's going to become commercial

Why do you keep insisting on some "virtual" way of providing drivers?! You have been told already many times- there is no such thing. There are proper solutions to the problem: 1) Providing drivers via floppy, that includes USB one. 2) Manually integrating the proper drivers into the source: http://unattended.msfn.org/unattended.xp/view/web/36/ 3) Integrating the drivers using nLite 4) Integrating a bunch of mass storage drivers (BTS driver pack for example) and hoping your hardware is among the supported ones. If not- post to the support forum providing details. Most likely they will be included in the next release and you would also help other guys with the same problem: http://forum.driverpacks.net/

Where did you download them from?If they are on a CD you have, simply zip and upload them to www.datafilehost.com and provide download link. Simply forget that story about virtual floppy and providing drivers that way, at least until the drivers currently being developed and mentioned above reach some stable stage and their usage tested. Something which won't happen today, tomorrow or next Monday

What error message Setup crashes with, please provide details, error code, exact moment of the error etc. You should also provide a link to the drivers you integrated with nLite.

I wonder- what would happen if we put in migrate.inf both values 7 and 8 pointing to the same drive letter? If not possible- maybe put first entry, with 7 as U: and 8 for say W:, would that cover all possibilities? Has anyone seen prefix starting with 6, or 9? @Jaclaz- thanks for cleaning up @macster Did you prepare on AND install Windows to the same machine? If yes- does it have USB card reader? If no- does both machines have USB card readers? Can you test with the attached migrate.inf, does USB stick get letter U:? If doesn't work- change the second U: to W:. migrate.inf

Good idea

Try the attached migrate.inf, place it in ~BT directory on the USB stick. Did USB stick get letter U: ? migrate.inf

MkMigrateInf.cmd has been updated as per this topic: http://www.msfn.org/board/2-t131770.html What Windows did you run the program under? Was it the same Windows as before, when it worked? Was it the same USB stick? Please attach migrate.inf in ~BT directory on the USB stick.

Ahh you, finder So 2K will let you create multiple partitions, but won't assign drive letter to the others that the first, correct?

Well, NO... Searched a bit and found the discussion where I made conclusion:http://img86.imageshack.us/i/deletepartitiongu3.jpg/ http://img246.imageshack.us/i/pqice0.jpg/ 2000 SP4. The reported said he was able to partition the USB stick just fine using disk management, no filter driver used. It could be well wrong report, or stick with flipped bit...

Just a small correction- as far as I remember 2000 treats removable USB sticks just as fixed disks, thus no need of filter driver.

Check txtsetup.sif in USB stick root for duplicated entries for those files, comment out (put ; sign at fron of the line) the duplicates. Copy edited txtsetup.sif to $WIN_NT$.~BT directory. If unable to figure out- zip and attach with your next post txtsetup.sif.

You should be seeing only one partition.XP displays only the first partition when dealing with removable devices. You can: 1) flip permanently the removable bit of the USB stick with the appropriate manufacturer tool. 2) Use a filter driver (dummydisk.sys or cfadisk.sys), which hooks the result removable/fixed and returns always fixed to the query "what type are you, dear USB stick", made from Windows. This way USB stick will be present as fixed disk, allowing all operations. Look in \WinSetupFromUSB\MULTIpartitionUSBstick\, there are a couple of batch files for easy installing and removing dummydisk filter driver.

Windows installer may create logical partition(s) inside extended in case 2 or more primary partitions are already present. In such case you need to play a bit with with boot.ini values. Not sure about the exact behavior. The error you got most likely is due to incorrect ARC path (multi(0)disk(0)rdisk(X)partition(Y)\WINDOWS) to the windows folder and should have nothing to do with Windows version or something similar. XP Pro may have started properly, depending how the hard disk was partitioned, just guessing. You haven't installed Home in other directory, not "Windows", have you?