wimb

@HKCU Thanks for your interest in the program usb_prep8.cmd. The USB_MultiBoot2.cmd is an improvement of usb_prep8. SEE: Make MultiBoot USB-Drive for Install of Windows XP You are welcome to write a guide in German language. @all It is easy to use the Program USB_MultiBoot2.cmd Important Help Instructions are given when Running USB_MultiBoot2.cmd Program. Read carefully the Help in the Intro for Making the MultiBoot USB-Drive and at the Exit of the Program for Using the prepared USB-Drive. These Instructions can also be read afterwards in the usb_prep.log File. Further Info is given in the Help_USB_MultiBoot2.txt File located in the Help_Info Folder. Besides there is an extensive Guide given at the CD Forum on how the MultiBoot USB-Drive is prepared. All Important Links are given below ( visible in all my posts ) Regards, wimb

In USB_MultiBoot2.cmd the check that the Target USB-Drive has FAT Format, was needed in view of making MS-DOS and FREEDOS Bootsector Files for MultiBoot Support. For Install of Windows XP from USB-Drive it is not necessary to limit to USB-Drives having FAT Format, but Real USB-Drives formatted with PeToUSB have always a FAT Format, and so it was thought also as userfriendly to present for Selecting as Target USB-Drive only Drives having FAT Format. In the next version of the Program I can move the FAT Format check for the Target USB-Drive to a later stage, where actually the Bootsector Files are made, so that the USB-drive in general can have any Format. To the Help File I will Add the very interesting and worthfull frase: - In Nlite do NOT select Operating System Options-->Manual Install and Upgrade for removal I will also try to make some check on this in the USB_MultiBoot2.cmd Program. Thanks ilko_t for your helpfull comment and advice on this. Regards, wimb

EXCELLENT idea. If, while doing the above, you could also avoid posting here offending people that have worked for months on this project would also be higly appreciated, and I guess ilko's poor innnocent pup would appreciate it too. jaclaz Yes ! The typical error with XP ntldr/ntdetect.com when arcpath or windows folder path is messed is "hal.dll is missing or corrupted", exactly what was mentioned a few posts above. Use ntldr/ntdetect.com from 2003, the same boot.ini, error becomes "ntoskrnl.exe is missing or..." . At least I am now aware, that the error message was changed in 2003. @ilko_t Thanks For INSTALL of Windows 2003 I added the following lines to Help_USB_MultiBoot2.txt in the Section C. for NON STANDARD INSTALLS ERROR Message for WIN2003: <Windows root>\system32\ntoskrnl.exe file missing indicates Install Foldername does not correspond to foldername in boot.ini For Windows 2003 one has to adjust Manually boot.ini in Advance. In makebt\boot.ini change foldername WINDOWS in WIN2003 or don't change boot.ini and use WINDOWS as Install Foldername instead of WIN2003 Regards, wimb

Did you use the winnt.sif file supplied with usb_prep8.zip ? It seems that Setup is looking for a CD which occurs when MsDosInitiated="0" The Correct value for Setup from USB-Drive is MsDosInitiated="1" wimb

I prefer not to use nLite. Try first USB_MultiBoot2.cmd on a clean xp sp2 source and if successfull then use RyanVM Integrator for integrating post-sp2 Update Pack, IE7 and WM11 Addon and after that use DPs_Base for integrating only DriverPack Mass Storage with text mode enabled. XPSOURCE Space Saving Tips see: http://unattended.msfn.org/unattended.xp/view/web/57/ You can Safely Remove the XPSOURCE folders: WIN9XMIG, WIN9XUPG and WINNTUPG - This will free up 37.6 MB LANG - 99 MB and cmpnents - 22.6 MB ( Needed for MCE / Tablet PC only ) Regards, wimb

There is a complete New Program Available: USB_MultiBoot2.cmd I have integrated usb_prep8.cmd in USB_MultiBoot2.cmd Batch Program, which: - Prepares MultiBoot USB-Drive provided with Windows XP Setup LocalSource - Supports Booting: MS-DOS FREEDOS BartPE WinPE 2.0 and Setup Windows XP - Supports GRUB4DOS with DOS FLOPPY IMAGES + Linux and Supports SYSLINUX Menu - Supports Portable WinTools which run direct from GO-Menu button Changes: - Virtual Drive is no longer used Instead in MultiBoot2 Folder a Temporary Folder usb_xpbt is made with all Custom made Files, and where the XP BootFolder $WIN_NT$.~BT is created by parsing DOSNET.INF from XP Source. The XP Source is copied direct to the $WIN_NT$.~LS Folder on the USB-Drive and not to the Temporary Folder usb_xpbt. - Install of BartPE by PeToUSB is supported, where a 2-byte hexedit of peldr enables its use in combination with coexisting XP Setup files, thus resolving possible conflict. - New is the USB Content Source Folder U_CONTENT which is copied to USB-Drive, and which can contain additional DOS, Linux and Win PE 2.0 files, but one might also select the complete Content of an earlier made USB-stick. Or one may select an empty Content Folder containing a needed empty usbflash TAGFILE. The Bootsector Files, Install of Syslinux, peldr and migrate.inf are Renewed to make the MultiBoot USB-Drive. - New is also the wintools folder with Portable win32 WinTools. Double-click on GO_WINTOOLS_MENU.BAT on USB-drive provides WinTools Menu from GO button. Very interesting, Hopefully the next version of MultiBoot2.cmd will also support rdummy.sys necessary for Install of 64-bit version of XP from USB-Harddisk Regards, wimb ***** NOTE ***** The Attachment contains USB_MultiBoot2_X.zip with limited U_CONTENT folder due to Upload limitation. The Full Version USB_MultiBoot2.zip with U_CONTENT folder containing a lot of FREEWARE programs is available at the CD Forum: http://www.911cd.net/forums//index.php?showtopic=20089 Download Direct USB_MultiBoot2.zip from CD Forum: USB_MultiBoot2.zip USB_MultiBoot2_X.zip

I will change the program such that dosnet.inf file is used as a marker to indicate a valid xp source directory. It is a very good idea to change that since winnt32.exe is no longer used. At the moment I am working on integrating USB_MultiBoot.cmd in usb_prep8.cmd. In the new concept I removed already the use of a Virtual tmpdrive, since it is no longer needed and gives problems with x64 versions of XP. I am very interested in rdummy.sys version for 64 bit windows, so that we can use this in the usb_prep8.cmd program and so improve the compatibility. It would be very helpfull ilko_t if you can make that, because I have no experience about this subject. @ilko_t I thank you very much for your pioneering effort in this project and for your helpfull comments. Cheers, wimb

In your Private communication you were speaking of errors when using usb_prep6.cmd So I supposed that you did not use version 8, but it is clear now that you did use version 8 Can you post your winnt.sif file (after wiping the product key) ? Where did you put your winnt.sif file ? And what did you do with the well working winnt.sif file provided in the usb_prep8 folder ? It is worthwhile to try the winnt.sif file provided in the usb_prep8 folder and keep it there and change only the product key. And I prefer not to use nLite. Try first usb_prep8.cmd on a clean xp sp2 source and if successfull then use RyanVM Integrator for integrating post-sp2 Update Pack, IE7 and WM11 Addon and after that use DPs_Base for integrating only DriverPack Mass Storage with text mode enabled. Everything is described in the provided Help_usb_prep.txt file, see section D. Regards, wimb

It might be that your winnt.sif file is causing the error. Check this file in Notepad Editor. You used usb_prep6.cmd where you had to give and change the product key in the given winnt_sif.txt file and copy this file as winnt.sif in your XPSOURCE\i386 folder. There is a newer version of the program named usb_prep8.cmd which makes the XP Bootfolder quite differently, without running winnt32.exe . It might well be that in this case you don't have your problem. In this case the given winnt.sif file needs to remain located in the usb_prep8 folder. The winnt.sif file provides the answers needed for Unattended Install of Windows XP and needs your Product Key ! Did you try to use usb_prep8.cmd ? Regards, wimb

That's a pity. I did not know, thanks for the Info.By the way, it would not be so difficult to change the program such that the content for the USB-drive is written first to a harddisk folder or direct to the USB-drive, instead of using the Virtual tmpdrive. Regards, wimb

The code of BT_folder.cmd program for making Windows XP Setup Bootfolder $WIN_NT$.~BT by Parsing DOSNET.INF , which was added to the usb_prep8.cmd program, so that launching of winnt32.exe /noreboot .... can be avoided, makes the program much simpler and more direct. It was tested several times and as far as I see there are no problems using it. When a Bootable USB-harddisk with XP Install files is connected and at the same time an USB-stick is prepared, then winnt32.exe would give unwanted effects, when it deletes $WIN_NT$.~LS folder of USB-harddisk. So I see only advantages in not using winnt32.exe anymore in preparing the $WIN_NT$.... Folders. Windows XP PowerPacker of Siginet is also using Parsing of DOSNET.INF instead of launching winnt32.exe for making the $WIN_NT.~BT XP BootFolder. So in my opinion everything is save and even saver as before. @Locaj Your USB-stick is seen as Fixed instead of Removable, that might be the cause of your problem. What is the size and the make of the stick ? You can try to use Option 0) Change Type of USB-Drive, and use USB-Harddisk as Setting for a Fixed Device, so that rdummy.sys makes USB Fixed Device being seen as Removable in Windows XP Setup. Regards, wimb

The Batch Program usb_prep8.cmd can be used to make Bootable USB-stick or USB-Harddisk for Install of Windows XP. Important Changes in usb_prep8.cmd Batch Program: The code of BT_folder.cmd program for making Windows XP Setup Bootfolder $WIN_NT$.~BT by Parsing DOSNET.INF was added to the usb_prep8.cmd program, so that launching of winnt32.exe /noreboot .... can be avoided and is no longer needed. A Custom winnt.sif file in the usb_prep folder is needed now, which will be copied by the usb_prep8.cmd program to the $WIN_NT$.~BT Bootfolder. For UNATTENDED Install make Changes in usb_prep folder: Change Product Key in winnt.sif and winnt_dp.sif and Change $OEM$ folder to your needs. Use for Preparing USB-Drive Only winnt.sif file without an [unattended] Section. Don't change commands for using BTS DriverPacks. winnt_dp.sif is used by usb_prep.cmd when using XPSOURCE with DriverPacks Integrated. It is not needed anymore to Set the Drive Letter for the Virtual TempDrive, since there is used now an Automatic Preset Value (mostly Drive T: is used). VBScript was used for making GUI enhancements for the usb_prep8.cmd Batch Program. When a .vbs script file is executed by cscript.exe from a Command Window, then the wscript.echo of VBScript is send as output of cscript to that Command Window instead of giving for the wscript.echo a GUI pop-up. When a .vbs script is executed by doubleclick then a wscript.echo statement is giving as you can try just only a GUI pop-up message with the echo of the return value e.g. displaying the return value of a VBScipt Function. The return value of the VBScript Function given as output of cscript to the Command Window, can be evaluated by using the FOR /F command according to FOR /F "tokens=*" %%A IN ('CSCRIPT.EXE //NoLogo u_script\FolderSel.vbs') DO SET src_ok=%%A This mechanism enables the possibility to use GUI enhancements in a CMD Batch Program. Rob van der Woude gives very valuable information on this subject. SEE: http://www.robvanderwoude.com/usermessages.html And a lot of handy Windows Script Host Examples, among which BrFolder.vbs implemented as FolderSel.vbs http://www.robvanderwoude.com/wshexamples_b.html#B MsgBox References: http://www.w3schools.com/vbscript/func_msgbox.asp http://msdn2.microsoft.com/en-us/library/sfw6660x.aspx The Wizard's Apprentice as proposed by jaclaz, can provide also GUI enhancements in a Batch Program, but that would require an additional download, since adding the 82 kB of this program would make the usb_prep.zip file larger than the 200 kB Upload limit of MSFN. So I decided to use a similar but integrated solution using cscript.exe with VBScript files, which has the advantage that it requires only a very small amount of extra code in the Batch Program. The usb_prep8.cmd program is given in the Attachment as usb_prep8.zip file Regards, wimb Edit 4dec7: Small changes in usb_prep8.zip Attachment: mainly MsgBox icons and Help_usb_prep.txt file usb_prep8.zip

I have made a tiny Batch Program named BT_folder.cmd (see Attachment) which from a given XPSOURCE directory will create the Windows XP Setup Bootfolder $WIN_NT$.~BT named as XPBT folder in a given destination directory. The BT_folder.cmd program makes the Bootfolder by parsing the dosnet.inf file. Every [FloppyFiles.*] section in dosnet.inf is referring to the files needed in the boot folder. The d1 is referenced in the [Directories] section, which shows the path of where the file resides. I will integrate BT_folder.cmd program in the usb_prep.cmd program so that Windows XP Setup Bootfolder can be made without launching winnt32.exe /noreboot .... A disadvantage and danger of using winnt32.exe is that it Deletes LocalSource folder $WIN_NT$.~LS in ROOT of ANY Drive which needs precautions by renaming such existing folders on USB-stick or USB-harddisk. This is no longer a problem when we use the code of BT_folder, which is also faster. Before presenting a new version of usb_prep.cmd with integrated BT_folder.cmd and hopefully some GUI enhancements, I would like to know if BT_folder.cmd is working well for all versions of Windows XP. I have tested BT_folder.cmd for Windows XP Professional and it works OK, but I have no Media Center Edition or Tablet PC and would like to hear about test results for these or other versions. The program was designed to take all versions of Windows XP into account. Synchronize dirs ... Command of Total Commander with the Compare command and using for Show only Green and Blue Arrows selected, can be used for comparing XPBT Bootfolder with existing Windows XP Setup $WIN_NT$.~BT Bootfolder. The differece will only be the migrate.inf and winnt.sif files which are added afterwards with the usb_prep.cmd program as Custom files. Regards, wimb Edit 27nov7: BT_folder.cmd2.cmd was slightly modified to make it more general. Edit 29 feb 2008: Updated to BT_folder3.cmd Removed in some cases possible DOSNET.INF Parsing Error BT_folder3.cmd

In usb_prep7.cmd we make the Boot folder $WIN_NT$.~BT by launching winnt32.exe /noreboot .... When making MultiBoot DVD's with the very handy program Windows XP PowerPacker of Siginet, I realised that Siginet is using a more sophisticated way to collect the files for the Boot folder. See also: http://www.siginetsoftware.com/forum/index.php Siginet makes the Boot folder by parsing the dosnet.inf file. Every [FloppyFiles.*] section in dosnet.inf is referring to the files needed in the boot folder. The d1 is referenced in the [Directories] section, which shows the path of where the file resides. Since we copy the complete XP Source to the LocalSource folder $WIN_NT$.~LS and we can make the Boot folder $WIN_NT$.~BT from the Info in the dosnet.inf file, it would not be necessary to launch winnt32.exe anymore. wimb

@jaclaz Interesting, I will have a look at it. Thanks a lot. Cheers, wimb

@ilko_t Thanks for the download link for Microsoft Deployment Toolkit The Results of my first experience with Microsoft Deployment is given below: You might also need to install additionally: Microsoft Management Console 3.0 for Windows XP (KB907265) and .NET 2.0 The WAIK .img file was mounted as .iso using DaemonTools, and then Installed using STARTCD.EXE Then Microsoft Deployment Toolkit was installed. After Launching the Deployment Workbench, I followed the Information Center > Getting Started Info After Update Deployment Point, the folder Media\Content was copied to USB-stick. The USB-stick was previously formatted with PeToUSB and was given a BOOTMGR type Bootsector using: Open CMD Window and use bootsect.exe to change the bootsector for use with bootmgr bootsect.exe /nt60 R: where R: is your USB-stick drive. In this way I could boot from USB-stick with Windows PE 2.0 After Auto Partitioning and Format, the $ LocalSource folders are generated on Harddisk. After Restart you have to boot from Harddisk, otherwise only PE is launched. So instead of Rebooting Windows PE, I shutdown the computer and removed the stick. Then start the computer without stick and Install of XP Runs as usual, except for a STOP Alert for giving Administrator Password, which can easily be avoided. At Windows Logon the stick was asked to be plugged in again to Finish Install. Well it worked, but the result was UNWANTED and in a way unexpected. The XP Install claimed the whole disk of my testcomputer for making a new partition. This means the Partition Table was gone and my 2 Data partitons were inaccessible Moreover the disc geometry was quite different from the usual one. The Drive C Bootsector is now sector 2048 (0x800) instead of normally 63 (0x3F) In CHS terms sector 2048 corresponds to CHS 0 32 33, which is not a head boundary, whereas sector 63 corresponds to CHS 0 1 1 and the MBR is at sector 0 = CHS 0 0 1 The result is that Partition Magic and Partition Info give a lot of Error Messages and are useless. Luckily I had a backup of the original MBR with the correct Partition Table, and the mirror MFT of the new partition was made well below the beginning of my original second partition. Restoring the original MBR with TinyHexer and then booting with Ghost for System Restore was applied. After again Rebooting I was able to access my 2 lost DATA partitions This method of XP Install from USB-stick takes at least 10-20 minutes extra time for booting with Windows PE and making the LocalSource folders on Harddisk. It is worthwhile to mention that the USB-stick can be used repeatedly, there was no change. Preparing the USB-stick is also taking much more time than with usb_prep7.cmd Besides Windows PE (2x) takes a lot of extra space requiring about 300 MB. So be very carefull and test USB-stick made with Microsoft Deployment only on test computer without important DATA. Regards, wimb

Is it in this case possible to use the flash drive repeatedly to make a hardware independent fresh install on different computers ? Or is it necessary to prepare the USB-stick each time for the next install ? Can you give some more help on how to use this approach for Install of Windows XP from USB flash drive and do you have a download link for the specific files that you use. I would like to try the procedure that you propose. Regards, wimb

May be Siginet can make a GUI for the usb_prep7.cmd Batch Program, such that it will fit in the family of RyanVM Integrator and Windows XP PowerPacker. http://www.siginetsoftware.com/forum/ Regards, wimb

The usb_prep.cmd Batch Program was changed so that it can be used also for preparing the LocalSource for Install of Windows XP from USB-Harddisk using rdummy.sys as developed by ilko_t see: http://www.msfn.org/board/index.php?showto...1384&st=421 FOR USB-Harddisk make 1900 MB FAT Partition at beginning of the USB-Harddisk. Use FAT Format and Set Active OR use PeToUSB to Format such partition. rdummy.sys makes Fixed USB-Harddisk seen in XP Setup as Removable Device. XP FAT Format is OK but without Set Active of partition you will get DISK BOOT FAILURE. USB-Harddisk will get during XP Setup DriveLetter D: and migrate.inf cannot change that. After First Logon there is only 1 USB-Harddisk partition visible as Removable Drive. After XP Setup and Reboot for second Logon than all partitions of USB-Harddisk will become visible as Fixed Local Drives and the highest partition number of USB-Harddisk will get DriveLetter D: This reversal and use of DriveLetters might be unwanted and consequently the use of USB-stick for XP Setup is Preferred, so that this DriveLetter Problem does not occur ***** WARNING ***** HP USB Disk Storage Format Tool 2.0.6 Destroys Partition Table of USB-Harddisk and cannot be used to Format one single partition of USB-Harddisk. Using HP Tool makes Data partitions of USB-Harddisk inaccessible !! So don't use HP USB Disk Storage Format Tool to Format USB-Harddisk. The HP Tool is usefull to Format USB-sticks, especially to make a MS-DOS Bootable USB-stick. Using PeToUSB.exe is SAFE for USB-Harddisk, it can only Format partitions with size less than 2 GB without destroying the existing partition table, so that Data partitions are still accessible. Use of usb_prep7.cmd and everything in the Help guides is COMPLETELY at your own risk. ALL files of cmpnents and i386 folder of XPSOURCE are copied now to $WIN_NT$.~LS LocalSource folder. XPSOURCE Space Saving Tips see: http://unattended.msfn.org/unattended.xp/view/web/57/ You can Safely Remove in advance the following XPSOURCE folders: WIN9XMIG, WIN9XUPG and WINNTUPG - This will free up 37.6 MB LANG - 99 MB and cmpnents - 22.6 MB ( Needed for Tablet PC only ) undoren.cmd and ren_fold.cmd and Customized presetup.cmd for BTS DriverPacks: First Limited Drive Range for searching TAGFILE is used to Prevent Windows No Drive Alert due to Cardreader. For case of Repair Install from USB-Harddisk with Shifted DriveLetters, than Drive with TAGFILE is not found. In that case Full DriveRange is used for finding TAGFILE. On Windows XP Repair Setup we get than: No Drive Alert - Press 4x Continue for Cardreader Drives I did not observe any problem (BSOD) using F3 to Quit from XP Setup, direct after Delete and Create of Partitions. Quit with F3 Enables Rebooting a Second time in TXT Mode of XP Setup, which is necessary after Repartitioning to give DriveLetters their Correct Value. The Attachment gives the usb_prep7.zip file. GOOD LUCK ! The usb_prep7.cmd Batch Program was tested for Fresh and Repair Install both from USB-stick and two different USB-Harddisks using a Laptop and a Desktop computer. Only in the case of Repair Install of Windows XP from USB-Harddisk there are Windows NO Drive Alerts to be expected due to Cardreaders, which require 4x mouseclick on Continue Button. Regards, wimb usb_prep7.zip

@ilko_t I will add to usb_prep.cmd the possibility to use rdummy.sys for Install of Windows XP from USB-IDE Harddisk, in the way as given by you. It will take some time, since I like also to test the usb_prep.cmd program with such USB-IDE Harddisk. I have a 20 GB IDE Harddisk available for testing purposes, but must first get a suitable USB-IDE HDD case for that. I can make some minor changes to boot.ini, but it is also important that the numbering of options will fit easily and logically in the boot.ini for the MultiBoot Menu as described in my Guide. The idea to copy in any case all files and folders from source\I386 to ~LS\I386 is a very good idea. It is simpler, does not take to much space and moreover the USB-stick XP-source is always more complete. I will also change boot.ini such that "USB Repair......" option is clearly not meant to be used as Start option, allthough this choice would not be harmfull. I think that Delete and Renaming of tempimage.img is easier and better done with the Windows Explorer FileManager. Quite often instead of Delete, one would like to Rename tempimage.img for future use. And if not Renamed, than the choice to Delete tempimage.img is offered on next running of the usb_prep.cmd Batch Program. Greetings, wimb

The Batch Program usb_prep6.cmd was further improved: - More Help at Begin and End of the Program - Delete of tempimage.img needs now User Approval This is good in view of the possibility to use tempimage.img again for copy to USB-stick - $OEM$ folder is now only copied if CMDLINES.TXT does not Exists already in LocalSource on TEMPDRIVE The Attachment gives the new version in the usb_prep6.zip file @ilko_t Congratulations with the possibility to use USB hard drives in future versions. I hope that you can use this new version of the Batch Program for adding the necessary changes to the bat files for support of rdummy.sys Regards, wimb usb_prep6.zip

The Program asked you to do: First Format to Make Bootable USB-stick with NTLDR Bootsector Using: PeToUSB.exe OR HP USB Disk Storage Format Tool Version 2.0.6 Settings PeToUSB: Enable Disk Format with LBA FAT16X Did you use PeToUSB to Format the USB-stick with FAT16 ? This is Normal, the USB-stick will normally get U: and otherwise it will get D: if you did not select to change migrate.inf This is Normal, when booting with MS-DOS from USB-stick seen as Harddisk. You should NOT Delete the Active Partition having DriveLetter C: Just Select the partition C: as the partition on which you are going to Install Windows XP, and then Select Quick Format with NTFS FileSystem. There is no need at all to Delete Partitions. If you Delete and Create New partitions, you have to Finish with F3 and Boot from USB-stick again and run 1. TXT Mode Setup again so that DriveLetters get their correct value, just as for a new harddisk Help_usb_prep.txt

I think the winnt.sif file in your XPSOURCE\I386 folder contains an [unattended] Section with OemPreinstall=Yes which [unattended] Section should be removed completely for making XP LocalSource for bootable USB-stick, which will be nevertheless suitable for UNATTENDED INSTALL !! When the [unattended] Section is present, an empty $OEM$ folder wil be made in the $WIN_NT$.~LS folder. I am using RyanVM Integrator and have not all the knowledge about what NLite is doing with $OEM$ folder. May be ilko_t can comment on that. If an EXISTING (empty) $OEM$ folder is detected in the $WIN_NT$.~LS folder of the TEMPDRIVE, then the $OEM$ folder of usb_prep5 folder is not copied to the $WIN_NT$.~LS folder of the TEMPDRIVE. This was introduced on request of ilko_t in relation to using NLite, see: http://www.msfn.org/board/boot_install_USB...html&st=360 Anyway it is very good to check the composition of your $OEM$ folder in the $WIN_NT$.~LS folder of the TEMPDRIVE before the FileCopy to USB-stick begins. Help_usb_prep.txt Edit 24-10: The problem when an empty $OEM$ folder is detected in the $WIN_NT$.~LS folder of the TEMPDRIVE, which blocks the copy of the $OEM$ folder from usb_prep5 folder, can be overcome by using in the usb_prep5.cmd program a different markerfile e.g. CMDLINES.TXT in $OEM$ folder , instead of the $OEM$ folder itselves. I will change that in the next version. That covers better the different cases. Edit 25-10: It is the posisition of the $OEM$ folder in the XPSOURCE which plays an interesting and important role. If $OEM$ is located outside i386 folder in XPSOURCE , which is normal for an XP Setup CD, then it is not used in making a LocalSource and [unattended] Section with OemPreinstall=Yes will generate an empty $OEM$ folder in the $WIN_NT$.~LS folder of the TEMPDRIVE. But when $OEM$ is located inside i386 folder in XPSOURCE , then [unattended] Section with OemPreinstall=Yes will use this $OEM$ folder to generate a correct $OEM$ folder in the $WIN_NT$.~LS folder of the TEMPDRIVE. However, the best way is to use $OEM$ folder from usb_prep5 folder and adapt it to your needs and keep it there. Remove completely in winnt.sif file the [unattended] Section with OemPreinstall=Yes and place winnt.sif file in XPSOURCE\I386 folder. Then there is no problem at all wimb

ntldr is not geometry specific and it is unlikely that the NTLDR Bootsector of the USB-stick has changed. You can use HDHacker to Save and Write the USB-stick Logical Drive bootsector http://dimio.altervista.org/eng/ The files NTLDR, ntdetect.com, boot.ini and SETUPLDR.bs ( =Bootsector file for launching TXT Mode XP Setup) are essential for booting. Check if they are still present on the USB-stick. These files might be corrupt or there position on the stick might give the boot problem. Tiny Hexer has an option Compare to check if the files are corrupt http://www.mirkes.de/en/freeware/tinyhex.php The position of files on the USB-stick can be analysed with WinHex using 1stSector column http://www.x-ways.net/winhex/ wimb

The program has been further improved, providing Simple and Extended Log Files using TEE.BAT integrated for redirecting xcopy output towards usb_prep.log file and to Screen. Thanks to jaclaz for the reference on how to make use of TEE.BAT Update of Existing Bootable USB-stick having XP LocalSource Folders is possible now. Also there is no need anymore to Format an Existing MultiBoot USB-stick having boot.ini Menu. Total Commander Synchronize Dirs in Asymmetric mode is very usefull for Updating the $WIN_NT$.~BT and $WIN_NT$.~BT Folders using a previously made (renamed) tempimage.img which can be Mounted with the Mount_TempImage.cmd Instead of the Copy of about 6000 files in 15 minutes to USB-stick, one needs to copy may be only 150 files in the Asymmetric Synchronize Update. Thanks to jaclaz for the routine for parsing the VDK.exe output to determine the Drive Letter of the TEMPDRIVE, needed when an existing tempimage.img was mounted. An Extended Help File was made with Most Frequently Encountered User ERRORS, and further Description of the use of usb_prep5.cmd Program and the Use of Total Commander to Update Existing Bootable USB-stick having XP LocalSource Folders. The Attachment gives the usb_prep5.zip File Regards, wimb usb_prep5.zip