ilko_t

This has been taken care of, look here for details: http://www.msfn.org/board/index.php?showto...st&p=705697 Restrictions- works on XP 32 bits only.

If I may add- all this is also displayed in the program everywhere I could put it: The tooltip above refresh button has the same info...

WSFUSB will not show USB disks which do not have a MBR and an active partition set. Since it showed after reformat with HP tool this means the first time it was not formatted properly.

You may try, however, you may need to play with boot.ini entries (rdisk(N) values) if during Text mode the card reader drives shift down the internal disk. Was the inserted card properly formatted, with MBR and active partition?

Is it like this after you reboot the newly installed Windows? The responsible driver is supposed to stop after first restart.

Glad you have all this sorted

Did you delete all ( this means all, not all but one) partitions and create a single one on the SSD? What file system did you format it in? Do you have an option in BIOS "OS Installation"? Also: http://wiki.eeeuser.com/windowsxpusb

Thanks, so 2003 is not affected.

@NT Man Lets check something if you don't mind, it seems grubinst fails on NTFS and Vista/7, maybe it doesn't like 2003 too... Please open up CMD and cd to \winsetupfromusb\files\grub4dos\ Then run: grubinst -v -l (hd3) If that's the USB stick according to partition size then run: grubinst -v (hd3,0) I need the result of both commands.

A few fixes made to the program, here is 0-2-2pre2: http://www.datafilehost.com/download-3697ab94.html edit: Downloaded and tested both archives and they were ok, just redownload the second one if you get again broken archive.

You may get PartedMagic and put it on the USB stick, delete all partitions and start Setup again. Well, this is different that what you posted in your first post Is Windows 2003 what you run WSFUSB under, or what you put onto the USB stick? Here is a link to pre 0.2.2, which has some checks if grub4dos BS is installed properly and if not- puts grub4dos MBR instead. Please try it and let me know the result. If still have problems- attach WinSetupFromUSB.log file found in program directory. http://www.datafilehost.com/download-adccfd78.html

Please zip and attach your txtsetup.sif file from USB stick root directory.

Well, are you sure that the key is typed correctly and is valid indeed? This shouldn't have anything to do with the program.

This shouldn't have anything to do with the versions. The programs which format drive are external and never been changed. Reformat the stick, try another stick, double check BIOS settings. How large is the USB stick? What files system did you use to format it with? Using PEtoUSB or HP format utility? Did you format it at all?

1) XP SP3 is fine too, no files will be deleted. I thought I had corrected readme.txt... 2) Sorry, I don't know how to explain it any better in short. Which part you do not understand?To perform Setup you start from USB, do the first part (Text mode), where you select partitions etc., then reboot, start from USB again and do the second part (GUI mode). USB stick stays plugged in all the time. Do NOT remove it after first part and DO start from it for the second part as well. In versions prior to 0.2.0 you had to start third time from USB- to start Windows for a first time. 3) The nLite option mentioned removes a couple of files (\I386\usetup.exe and \I386\ntdll.dll), depending on nLite version, which are needed when installing from hard disk like media, this includes USB disk. Without these files Text mode cannot start. They are needed only to start the setup, without them you will get BSOD, and do not play role when installing from a CD. If you have the option already applied, look here for possible workaround: http://www.msfn.org/board/index.php?showto...st&p=846339 If files are missing you may get them from a similar XP source and copy them to the destination mentioned. WinSetupFromUSB may detect the option had been applied and refuse to accept such source. To "trick" it, simply create a blank file called winnt32.exe in \I386 folder in your source, prepare the stick and then copy manually the files mentioned to the USB stick. Is it any clearer now?

Just another brilliant work of cdob, thanks.

Thanks for the details. FYI - files are compressed, and extracted before copied to destination, that's why they end with _. Another idea- Text part of setup attempts to delete them, but the USB stick is write-protected by entries in migrate.inf. At the same time setup is instructed to copy the same file to another destination right after the same file was attempted to be deleted. It could be timing issue. This does not happen when installing from a CD since Setup would not attempt to delete the files in question. If you move just the lines we commented out to the bottom of the same section [sourceDisksFiles] in txtsetup.sif, right below tempunat.inf=1,,,,,,,2,0,0 , uncommenting them, so Setup has some time before attempting to copy the same file for a second time, you may not get the error messages, hopefully. Just an idea... Still not sure if such duplicated lines should be present at first place. You may also watch when the duplicated lines show up, after HFSlip or after using nLite.

Thanks for noticing, my bad. Editing the post above.

Thanks for sharing the result. It's interesting to look a bit deeper why this happens. Using this as reference: http://www.msfn.org/board/index.php?showtopic=127677 1005 means the file goes to system32\en-US\ subdirectory, whereas 2 stands for \system32\. So advpack.mui for example should be copied twice- to \system32\en-US\ and to \system32\ renamed to advpack.dll.mui. Logically if the file is not deleted during the first copy (you can check if file is still present after setup), no errors should occur since its location on source disk is the same in both lines, it simple would be copied twice. If the file does get deleted from USB stick during Text, then other files should be missing too. Is the file still on USB stick after setup? As for iedw.mui = 1,,,,,,,,3,3 I can't find reference what the missing target subdir location defaults to, thus why no errors are displayed about this file Same for why no errors when installing from a CD, maybe if the file is deleted during copying, but cannot be from a CD... No idea also are the files supposed to be in both system32 and system32\en-US\, or this is wrongly set.

Prepare the stick as usual, if already prepared do not again. Download the new MkMigrateInf_b.cmd and save it in a path without spaces in it. http://www.msfn.org/board/index.php?showto...st&p=852822 Open up command prompt, cd to that directory and run: MkMigrateInf_b.cmd H: H:\migrate.infReplace H: with the current USB stick drive letter. Copy H:\migrate.inf to H:\$WIN_NT$.~BT\ replacing the existing file. edit: file names corrected

There are strange duplicate lines in txtsetup.sif, which may not play role when installing from a CD, but may do from USB. Comment out the first line in USB_root\txtsetup.sif and \$WIN_NT$.~BT\txtsetup.sif of the duplicates: advpack.mui = 1,,,,,,,2,0,0,advpack.dll.mui advpack.mui = 1,,,,,,,1005,0,0,advpack.dll.mui To become: ;advpack.mui = 1,,,,,,,2,0,0,advpack.dll.mui advpack.mui = 1,,,,,,,1005,0,0,advpack.dll.mui ieframe.mui = 1,,,,,,,2,0,0,ieframe.dll.mui ieframe.mui = 1,,,,,,,1005,0,0,ieframe.dll.mui ;ieframe.mui = 1,,,,,,,2,0,0,ieframe.dll.mui ieframe.mui = 1,,,,,,,1005,0,0,ieframe.dll.mui The rest of the similar files do NOT have such duplicated lines, such as: Didn't iedw.mui also give you an error?: iedw.mui = 1,,,,,,,1005,0,0,iedw.exe.mui iedw.mui = 1,,,,,,,,3,3Search for "1,,,,,,,1005" and find any other duplicated entries for the same file name, leave the ones with "1,,,,,,,1005" and comment out the other. This is problem of nLite or HFSLIP, or improper usage one after another, and the error may occur if installing from a CD as well.

Can you find these files on the USB stick? Where are they located? Does the error occur during Text mode or during GUI mode? Please attach txtsetup.sif file from USB root.

Here you go: http://www.msfn.org/board/index.php?showtopic=122170

Are you talking about the same issue: http://www.msfn.org/board/index.php?showtopic=133164

I am just coding a few checks if grub4dos BS was successfully installed, if not- install grub4dos MBR, if not- abort, or maybe add a line to boot.ini as a last resort for those cases where grubinst completely fails. Wimb also pointed me to a bug in touchdrv usage in the program. Hopefully these improvement will get rid of all similar issues. Don't want to take the risk with bootlace as behavior under 2003, Vista and 7 is unknown and lately have quite limited spare time to do extended testing or code such changes.