ilko_t

Format the USB key in NTFS if you have files above 4GB, or FAT32 if not. Install grub4dos bootloader, or chainload it: http://diddy.boot-land.net/grub4dos/Grub4dos.htm http://www.boot-land.net/forums/index.php?showforum=66 Extract contents of the ISO in the USB disk, as they are. Next create a menu entry to chainload bootmgr. That's it. Or with syslinux: http://www.boot-land.net/forums/index.php?showtopic=8457 You can install and use any other bootloader which can chainload bootmgr.

0x0ff should be 0xff. In addition- I don't think firadisk driver will work on 2003 setup, at least last versions I've tested did not. Most likely you will get BSOD 0x7B. But please, test and report back, including firadisk driver version.

You can start installation from grub4dos by chainloading the appropriate file. 2000/XP/2003-->setupldr.bin Vista/7-->bootmgr Linux-->kernel & initrd files For 2000/XP/2003 default MS method when installing from HD-like media ( winnt.sif-->'data' section-->msdosinitiated=1 )is use of ~BT (boot) and ~LS (local source) folders. However, there are number of glitches on the way, which were somehow sorted out or workarounds found while this project was being developed. There are still limitations, which cannot be overcame, at least not easily. All are mentioned several times in the "historic" thread and scattered around this subforum. That's why now you can find several improved methods in the pinned topics. If you want to go the path which took several forum members many months experimenting and finding resolutions- sure, why not, there is a lot to be learned, in many areas. But do not expect this to go easy as 1,2,3, boot files are just the first problem, many other to follow At least now we have answers for all or most of them, so you would not be banging your head wondering why the heck something is(not) happening. If you search the subforum a bit you will find a few posts of mine where the whole procedure is summarized, step by step, and where the issues are. If you want to save yourself time and headaches- use well tested method in any of the pinned topics and focus on it, why not even on improving it. Added:

You may be able just to copy the missing files, but you'd have to ask in the nLite forum what exactly is removed by that option. An advice- remove only stuff you know what it is about and you won't need it for sure. The time wasted in troubleshooting/repairing/reinstalling does not compare at all with the imaginary time saved using trimmed down Windows.

Look at the added part in my reply

The problem is with the system you are running the script on, not the source you have nLited. Line 21 of USB_multiboot_10.cmd VER | find "6.0." > nul Do you have find.exe in C:\WINDOWS\system32 ? Try this: Added: On a second read- you have run the script on the trimmed down XP, so I guess the option in question would be Operating System Options -->Command-line tools

What are contents of usb_log.txt in usb_multiboot_10.cmd directory?

If you search a bit the subforum you will find number of topics where this has been discussed with the possible options Edit menu.lst on the USB disk: Added: http://www.msfn.org/board/install-windows-winsetupfromusb-t120444-pid-901978.html/page__view__findpost__p__901978

A few ideas: Test in QEMU just to see if it boots, do not install further, do not perform write operations in QEMU. When using the USB stick it's good idea to unplug it any after write operations, using safely remove hardware. As for the nLite problem- Google returns quite a lot of results, have you looked? At what stage exactly this is happening?

At what stage do you get these errors? Text mode? Checked for few of them in txtsetup.sif, none was mentioned, so I guess they are copied during GUI part, right? Where are they mentioned? I see a typo, missing backslash: WINSETUP\XPpSP3I386\SVCPACK WINSETUP\XPpSP3\I386\SVCPACK Can you attach the whole HFSLIP.CMD if it does the job?

Zip and attach txtsetup.sif too, with a few names of the missing files.

Someone familiar with HFSlip may comment on that. That's not me

It all depends if the install script for the applications being added use hardcoded paths. These paths may need to be modified. I personally do not use HFSlip and cannot comment further.

Check in WinSetupFromUSB\files\winsetup\PyronSetup\i386 if setup.ex_ exist. If not- download a new copy of the program or just put there the attached file, unzip it first. Some antivirus programs still detect it falsely as a virus, despite all the emails sent to major vendors: http://www.msfn.org/board/virus-suspected-inst-v047z-t141734.html Turn off any antivirus protection while doing that and using the program. setup.zip

Sure , it's the good guys at MS that invented a stupid format where multiple sections with same name are possible. A similar issue has already been noted at the time and the original USB multiboot did use fedit "add once": http://www.msfn.org/board/index.php?showtopic=61384&st=393 Maybe a good idea would be to pre-process these files to remove duplicate secions by merging them. Something like this: http://mindprod.com/project/inifiletidier.html http://mindprod.com/products1.html#INI http://www.boot-land.net/forums/index.php?autocom=Downloads&showfile=154 http://www.codeproject.com/KB/applications/iniutils.aspx jaclaz Thanks for the links. Here is the thread in AutoIt forum: http://www.autoitscript.com/forum/index.php?showtopic=113318 I'll see what I can do when get a chance.

Are you running Windows from USB device? For some reason the selected disk appears as PHYSICALDRIVE0, which the program will not operate on for safety reasons. 2010/04/22 16:30:17- TOSHIBA TransMemory USB Device 2010/04/22 16:30:17- DeviceID: \\.\PHYSICALDRIVE0 2010/04/22 16:30:17- PNPDeviceID: USBSTOR\DISK&VEN_TOSHIBA&PROD_TRANSMEMORY&REV_6.51\0DD0757001F35ABF&0 2010/04/22 16:30:17- Partitions count: 1 2010/04/22 16:30:17- Disk--Partition: Disk #0, Partition #0 2010/04/22 16:30:17- Logical Disk: D: File system: NTFS Primary: True ..... 2010/04/22 16:30:17- Drive letter of the selected partition- D: 2010/04/22 16:30:17- Drive letter of the first primary partition in selected disk- D: 2010/04/22 16:30:17- Disk number of the selected disk- 0 2010/04/22 16:30:17- PNPId of the selected disk- USBSTOR\DISK&VEN_TOSHIBA&PROD_TRANSMEMORY&REV_6.51\0DD0757001F35ABF&0 2010/04/22 16:30:17- File system type of the selected partition- NTFS 2010/04/22 16:30:17- Disk type of the selected disk- Removable 2010/04/22 16:30:17- Total target size avialable- 3791 MB Can you check in advanced options to display drives on all interfaces, not only USB and post the new log?

Please post WinSetupFromUSB.log file found in program directory.

I guess you'd need to figure out what exactly that addon does and what paths it uses, thus what has to be changed in order to support different paths. Maybe good idea to ask where it's being developed. I have no clues, sorry.

Can you provide a link to that activator?

You have been replied in the thread you started. Why are you double posting? http://www.msfn.org/board/when-reinstall-winxp-pool-header-blue-screen-t143453.html

Does it happen during Text or GUI mode? Is there any error code on the BSOD? Have you tried without the ICH drivers? Which method/program (incl. version)/instructions did you use to prepare your USB stick?

Then rebuild the stick. This is how the program detects windows 2000 (looks for string '2000' in wks_id value) and amends txtsetup.sif accordingly, differently than XP/2003. I'll add in the next version a check for wkscd = ..... if wks_id is missing. Thanks for reporting. You can find wks_id in second [strings] section. Thanks, didn't expect another section. It appears AutoIt internal function IniRead reads just the first section. Will have to dig in their support forums if it's a bug or expected behavior. Meanwhile, to get you going, just merge these two sections into single one.

In your source change txtsetup.sif and add the following line in Strings section: Then rebuild the stick. This is how the program detects windows 2000 (looks for string '2000' in wks_id value) and amends txtsetup.sif accordingly, differently than XP/2003. I'll add in the next version a check for wkscd = ..... if wks_id is missing. Thanks for reporting.

Please zip and attach with your reply these three files: 1) From USB \WINSETUP\ISO files name for 2000 --> txtsetup.sif 2) From USB \WINSETUP\2000 directory\I386\txtsetup.sif 3) From WinSewtupFromUSB directory--> WinSetupFromUSB.log, if it's small find the appropriate one in \backups\ directory, it would be cab compressed.

Happy to read that.Was LocalSourceOnCD="1" the problem?