ilko_t

Did you try what I wrote you, post #8 ?

Cannot spot anything. I wish I could help you... edit: have look in event viewer if the are any errors, which might give a clue, if it's working.

Yep. Can you post your nLite settings, lastsession.ini?

Try if you can run this VBS script. It makes a list of your services and their status. Since it's using WMI as well, it may not start. If it does start, please attach here C:\ServiceList\OnlyOnRequest\services.txt If it does not start, hmm, maybe a screenshot of your services? The only way I can reproduce this error on my side is to stop WMI service, however, there might be other dependent services or unregistered dll files- you may try dial-a-fix and re-register everything, it does not harm, although I'd prefer to find out why exactly WMI fails.

Check if Windows Management Instrumentation service is running. Enable it if it's disabled. The programs makes a few WMI queries to obtain USB information.

Try deleting BOTH partitions on the hard disk while in Text mode and create 2 new ones. Do NOT continue, but rather hit F3 and restart again in Text mode. Install XP in the first one of the newly created partitions. In BIOS do you have a setting for hard disk mode AUTO, LARGE, LBA? Try changing it too.

You should remove your links, please read board rules. As for what you want to accomplish- the program already can put up to 10 different Windows 2000/2003/XP sources on the USB disk. But you do need to run the program 10 times- giving path to each source you have. If you want to stay on the safe side- use unmodified sources, or at least not like those, which were modified to fit all in a multi-boot DVD.

warlock554, you need to read carefully FAQ #4. If you did so, you should have posted your partition number as well, which is as important as the harddisk number. Windows folder matters as well. There is no point to use different installers etc. Better take a picture of this screen: Does partitionN match what you have in boot.ini on USB disk? In this example Windows was installed to partition2. Partition(1) is hidden. Boot.ini has ....rdisk(1)partition(2)\.... Did you boot again from USB after the Text mode part of Setup?

You can't. Even if you start the ISO, when it goes in protected mode it will BSOD 0x0000007B, unless someone writes NT drivers, which work for grub4dos emulation. Even if one makes those drivers, at some point Setup reads BIOS devices, your emulated ISO is ignored. Winnt.sif is read from BIOS device... Even if you pass the Text mode part, how GUI mode will find files? You need to mount that ISO again and point GUI mode to the emulated device... Using ram drivers from 2003 does not help as well, read here: http://www.msfn.org/board/index.php?showto...st&p=776205 This question has been asked and answered numerous times in details, search here, at 911cd.net and boot-land.net. Possible path to take, many questions, no answers: http://www.boot-land.net/forums/index.php?showtopic=6010

Thanks It was another unforeseen contents of dosnet.inf, changed the procedure which is parsing it and now should be less sensitive to funny contents of directories section. Please try this version, just download the file and place it in WinSetupFromUSB directory, use it to launch the program: http://www.mediafire.com/download.php?hdmtejok5yt Please let me know if everything works fine. Will include the update in 0.2. BTW what version of nLite the source was prepared with?

Thanks for reporting Please let me have a look at the log files, the latest one is in WinSetupFromUSB\WinSetupFromUSB.log and the older ones are archived in WinSetupFromUSB\backup\$date$-$time$-log.cab I would need all these log files. Please put them in a zip file and either upload it on a file sharing server such as http://www.mediafire.com/ , or attach it to your next post if size is small enough. Please add DOSNET.INF from your unattended windows\I386 folder too, the problem is most likely in parsing it. You should be using partition 2 in your case, no matter that the first partition is hidden, it's still partition 1 and windows goes on partition 2.Forget about C,D etc., those are not number of partitions and are used rather for user's convenience, than describing exactly your partitioning. Simply change partition(1) to partition(2) in both lines and "hd 0 part 1" to "hd 0 part 2". BTW for grub4dos numbering partition numbers start from 0, so (hd1,1) means second hard disk (USB is first), second partition. In Windows disk numbering starts from 0 too, but partition numbers from 1. harddisk1\partition2 means second hard disk, second partition. ARC path for that would be rdisk(1)partition(2). If you hold the mouse over partition or disk boxes in the GUI part of this information is displayed.

Nice catch The file should be called migrate.inf and should go in ~BT folder. It does the write-protection during Text mode and sets letter U to the USB disk. MkMigrateInf2.cmd is the script, which generates migrate.inf. Will have a look why spaces are problem, I guess it's called improperly from my program as spaces were not taken into account. BTW it should be "\DosDevices\U:, did you post the orphan file?

mmg1818, this is good to know, but how it relates to the specific subject in the posts above yours?

QED- just tested to slipstream SP3 in SP2 source- no files were deleted, so it is well possible that update after SP3 causes USB write-protection to be ignored. If that's the case, someone with the willingness to test may reveal what file(s) cause this behavior, by replacing usb drivers, setupdd.sy_, \system32\ntdll.dll in ~BT filder with those from SP3 archive. My first bet would be on usb drivers (usbstor.sy_ etc.) and setupdd.sy_. As for the re-sync option- since we don't know which files were deleted, comparing the whole contents of I386 folders is needed, I can't think of faster and more reliable way to sync them, apart from writing a separate procedure, which first compares both folders and then copies only the difference. This will require some time to implement and test.

08-08-2008 was giving problems on other systems...Please report to grub4dos developers, including what versions you used, your motherboard model and description of the error: http://www.boot-land.net/forums/index.php?showforum=66 Look if you have in BIOS option to disable SATA/AHCI and run in native IDE.Other way is to slipstream BTS mass storage driver pack in your XP source: http://www.driverpacks.net/ http://www.driverpacks.net/DriverPacks/DriverPack.php?pag=m http://forum.driverpacks.net/viewtopic.php?id=1449

Thanks for getting back. Have you tried 0.4.3-2008-05-14 ? FYI USB_multiboot uses grub4dos as well, just an older version. I decided to use newer versions as grub4dos is constantly developed and many bugs have been fixed since 0.4.3. Hopefully soon we will have a stable 0.4.4. edit: other download links for older grub4dos versions: http://download.gna.org/grub4dos/ http://grub4dos.jot.com/WikiHome

You mean you don't get the menu entries? Look at post #133 and 134, replace grldr. What hardware are you booting it on?

Hi, thanks for your comment, that's always needed Program detects if source is different from XP SP2 or SP3 and displays a message box Is that enough? Need to correct in ReadMe.txt and include SP3, thanks. It doesn't copy all of them, however it's checks if each file is present. The operation is similar to normal copy from explorer, with NO overwriting and should be faster than a full copy. Since you are the first one reporting an issue I assumed everything was normal at this front. Program contains number of tools and files, which should be easily accessible (log files, backups etc.) and I prefer not to bury it in C:\Program Files\WinSetupFromUSB or whatever. In other hand this type of install still requires some knowledge. I wish we could make it easy as for grandmothers, but for now this is what MS gave us as options. I haven't seen this since I am not using Program Files at all. I guess MkMigratInf.cmd doesn't like spaces in the path, will have a look. If there are other requests for that I can implement it. For now I'd rather concentrate on more important features. The reason behind this is described at the bottom of first page of this topic- it's to be able to perform unattended installations, where second part is auto selected if the first part was launched. Another reason is that main menu gets overloaded with entries if one adds number of Windows sources + GParted + Vista + something else. I noticed that as well, it's already fixed in 0.2, which I am testing. For now everything is ready, but x64 installs are giving headaches. The major difference is that user has to boot from USB twice only. This eliminates all the cases when impatient or those not reading instructions and dialog boxes unplug their stick as soon as they see GUI mode is completed. Believe me, to test 0.2 alone I have made already more than umm... 50 or 70, I don't know how many installs. Jaclaz is also helping with the new binifix.cmd, which has an option NOT to add USB repair entry in boot.ini. Hope that answers your next question too.The reason behind USB repair entry at first place, was to get as close as possible to normal setup- if you don't have this entry Repair install is NOT possible, and I'd rather have it there, instead of inability when Windows is screwed not to be able to repair it. However, this is what we concluded during the first programs (USB_prepare). Since feedback is VERY limited, but downloads in total could be well above 100 000, I wonder why people are not complaining. Thanks again for your feedback

Thanks for sharing this

Here is 2003 SP2, after the copy part on destination drive are 3444 files, occupying 554MB. FAT16: Text mode copy part without USB write-protection- 8:04 FAT32: Text mode copy part without USB write-protection- 9:18 NTFS: Text mode copy part without USB write-protection- 2:46 FSK-JoKeR- as far as I remember the old GParted 0.3.4-8 does work from NTFS, but is a bit outdated. PartedMagic 3.0 also worked from NTFS.

Here there are- 2000 SP4, 5738 files / 611MB. After the copy part on destination drive are 2697 files, occupying 290MB. FAT16: Stick prepared for ~16 min. (987 secs.) Text mode copy part without USB write-protection- 3:47 FAT32: Stick prepared for ~21 min. (1282 secs.) Text mode copy part without USB write-protection- 3:36 NTFS: Stick prepared for ~5 min. (297 secs.) Text mode copy part without USB write-protection- 4:18 What the heck were MS screwing with those drivers? Will test 2003 SP1 too, will it be the same as XP SP2...?

Thanks for the feedback It's grub4dos issue, please get the latest possible from here and replace only grldr in USB disk root as you did before. Let me know if it worked and what version you tried. http://nufans.net/grub4dos/ If the latest doesn't work, I guess grub4dos developers will be interested in details about your motherboard/BIOS: http://www.boot-land.net/forums/index.php?showforum=66

I have done a few tests to measure copy speed during Text portion of setup. Here are the results: NLited XP source, 5251 files occupying 399.7 MB. After the copy part on destination drive are found 2850 files, occupying 476MB. Preparation made by WinSetupFromUSB 0.1.1, run on XP SP2 system, C2D 4300@2.9GHz. USB stick- Lexar JD Lightening 1100 1GB, which is relatively fast: In all cases stick was quick formatted using HP USB format tool 2.0.6. To check if USB write protection via migrate.inf plays role I tested without it as well. All tests performed intentionally on an old Celeron 1.7MHz/384MB RAM/VIA 266KM chipset, which supports USB 2.0 once the USB drivers are loaded. FAT16: Stick prepared for ~15 min. (899 secs.) Text mode copy part with USB write-protection- 4:10 Text mode copy part without USB write-protection- 6:13 FAT32: Stick prepared for ~21 min. (1253 secs.) Text mode copy part with USB write-protection- 12:58 Text mode copy part without USB write-protection- 7:15 NTFS: Stick prepared for ~4 min. (238 secs.) Text mode copy part with USB write-protection- 1:42 Text mode copy part without USB write-protection- 1:45 It really puzzles me why FAT32 is so slow compared to FAT16 If your system supports USB boot from NTFS formatted partitions AND you are not planning excessive usage of the USB stick in terms of write operations, where NTFS may wear it out (disputable with modern USB sticks), NTFS seems to be the way to go.

Good to know, thanks. About the slow copying- did you format USB stick using FAT32? Try NTFS, it's WAY faster, FAT16 also may give way better results, don't use it on larger than 2GB partition though.

Vers. 0.1.1 uploaded, please refer to first post for list of changes and download links.