Install XP from USB, Prepare Bootable USB-drive with USB_MultiBoot.cmd Options

[wimb_2]

================================================================================

From Tutorial at Boot Land Forum http://www.boot-land.net/forums/index.php?showtopic=4900

================================================================================

***** USB_MultiBoot.cmd - Install XP from USB *****

1. Introduction

The Batch Program USB_MultiBoot.cmd can prepare a Bootable USB-Stick,
which can be used to Install XP from USB.
Install from USB-Drive is of general use, it's convenient and faster than installing from CD or DVD,
but is limited to computers that are able to boot from USB, as determined by BIOS and Motherboard.
Updating and Changing an USB-stick is also easier than preparing a new Bootable CD or DVD.
Install XP from USB is very useful when the computer does not have a optical drive,
like e.g. ASUS Eee subnotebook.

Preparing a Bootable USB-Drive with USB_MultiBoot.cmd Involves:

• Format USB-stick like a Bootable Harddisk Drive with NTLDR BootSector
  using PeToUSB or HP USB Format Tool
• Select from the Main Menu of USB_MultiBoot.cmd
  1 - Give XP Setup Source Folder and give UserData for XP Setup
  2 - Give USB-Drive Target
  3 - Make Bootable USB-Drive with XP Setup Folders

Installing XP from USB requires a Reboot from USB-Drive
and Select from Boot Menu: 1. Begin TXT Mode Setup Windows XP

- Download Direct from CD Forum: USB_MultiBoot_10.zip

Or from BootLand Forum: USB_MultiBoot_10.zip

Or from Mirror (Thanks to Siginet) - USB_MultiBoot_10.zip

- Unpack USB_MultiBoot.zip to your Harddisk in a simple Path without SPACES.

USB_MultiBoot.cmd is Vista Compatible, but requires User Account Control OFF.
In this case a BOOTMGR type BootSector is made when Formatting the USB-Drive.
Such Bootsector is Detected and Auto Converted by BootSect.exe to
NTLDR type Bootsector required for booting with boot.ini Menu
XP as OS is Preferred for Speed of FileCopy to USB ( 10 min instead of 30 minutes for Vista OS )

The procedure for installing Windows XP from a bootable USB-stick was developed by
ilko_t , jaclaz , cdob, porear and wimb at MSFN Forum

- Install XP from USB at MSFN Forum /157-install-windows-from-usb/

- List of FAQs

- More Info See Guide with ScreenShots

- More Help with Bookmarks is available in the Help_Info Folder in USB_MultiBoot.zip

- Use of MultiBoot.cmd and everything in this Guide is COMPLETELY use at your own risk.


2. XP-Source Preparation - *** BEFORE YOU START ***

Make sure that your XPSOURCE Folder is located on your Harddisk in a simple Path without SPACES.
Copy the Contents of your Windows XP Setup CD to your XPSOURCE Folder on Harddisk.

Siginet's RyanVM Integrator or nLite can be used to Integrate Windows UpdatePacks in the XP-Source.
http://integrator.siginetsoftware.com/index.php?download
http://www.nliteos.com/

Windows XP UpdatePacks and Addons:
http://www.ryanvm.net/msfn/
http://www.ryanvm.net/msfn/updatepack-sp2.html
http://integrator.siginetsoftware.com/index.php?addons
http://www.ryanvm.net/forum/

Supports the use of BTS DriverPacks located in OEM Folder on USB-Drive
http://driverpacks.net/downloads
For installing XP on modern systems with SATA Drives it is needed to use DPsBase.exe
for Integrating in your XPSOURCE BTS DriverPack Massstorage with TXT Mode Enabled.
In that case a lot of Extra RAID SCSI and SATA Drivers (about 120 extra) are Integrated and will appear in the
XP Setup BootFolder $WIN_NT$.~BT on USB-Drive and can prevent a lot of XP Installation Boot Problems.
First use RyanVM Integrator and then use DPsBase to Improve your XP-Source.
The program supplies a Customized presetup.cmd and changes the winnt.sif file for use of DriverPacks.

The Complete XP-Source is Copied by USB_MultiBoot.cmd to XP LocalSource Folder $WIN_NT$.~LS on USB-Drive
Computation of Estimated XP Folder Size is used to prevent USB-stick overflow
and includes $WIN_NT$.~BT + cmpnents + I386 + AMD64 + $OEM$ + OEM Folders.

Excluding LANG and WIN98X Folders from Copying to USB can be Selected
from USB_MultiBoot.cmd Main Menu, which can reduce the XP-Source on USB-Drive by 135 MB.
Reduction of the XP WINDOWS Folder can be achieved with nLite
but do NOT select Operating System Options-->Manual Install and Upgrade for removal.
If you do you will get BSOD, error 0x0000006F during Text mode Setup of Windows XP.

=========================================================================

3. Making a Bootable USB-Drive with USB_MultiBoot.cmd

- Remove all other Removable Drives, like USB Backup Harddisks and Memory Cards
- Use USB-sticks with High Read/Write Speeds of about 15 MB/sec
- Unpack USB_MultiBoot.zip to your Harddisk in a simple Path without SPACES.

- Launch USB_MultiBoot.cmd and Display the Format Menu
- Format the USB-Drive with FAT or NTFS. Note: FAT32 is very SLOW for installing XP

• P) - PeToUSB - FAT Format - Max 2 GB
  To Format USB-Drive : Enable Disk Format with LBA FAT16X
  Do NOT Select "Enable File Copy" of BartPE File Copy Options.
  FAT Format Supports Direct Booting with MS-DOS using MULTI_CONTENT
  Installing XP from USB takes 30 minutes - Buffalo FireStix 2 GB
  
  
• H) - HP USB Disk Storage Format Tool V2.0.6 - NTFS Format - use X_CONTENT
  NTFS Format Supports DOS Boot Floppy Images via GRUB4DOS Menu
  Installing XP from USB takes 16 minutes - Corsair Flash Voyager 4 GB
  Do NOT use the HP Tool for USB-Harddisks having more than 1 Partition
  WARNING - HP Tool Formats whole Disk - Second Partition is Lost
  
  
• N) - No Format - Use USB-Drive with FAT or NTFS formatted by Windows XP
  Or Update Existing Bootable USB-Drive having NTLDR Bootsector

- For USB-Harddisk use Main Menu Option 0) to Change from USB-stick to USB-Harddisk.
Because this makes use of rdummy.sys and is essential for using USB-Harddisk.
rdummy.sys makes Fixed USB-Harddisk seen in XP Setup as Removable Device.

- Select from the Main Menu of USB_MultiBoot.cmd
1 - Give XP Setup Source Folder and give UserData for XP Setup
2 - Give USB-Drive Target
3 - Make Bootable USB-Drive with XP Setup Folders



4. XP Setup Parameters in winnt.sif file and $OEM$ folder

Display and Edit of the 8 required parameters for Unattended Setup allows you
to give your ProductKey and TimeZone used in the Current_winnt.sif and copies your winnt.sif file.
The Current_winnt.sif file is auto adjusted for the Installation of XP from USB and then
copied by USB_MultiBoot.cmd to $WIN_NT$.~BT folder on USB-Drive.

The file useraccounts.cmd with UserName is made in the $OEM$ Folder
copied to $WIN_NT$.~LS folder on USB-Drive.
CMDLINES.TXT is used for making UserAccounts and install of Registry Tweaks at T-12
Info see: http://unattended.msfn.org/unattended.xp/

For the Option Edit UserData for XP Setup we have:

A. Unattended Install - UserName = YourName
in winnt.sif file - unattendswitch="Yes" - UserName is used Automatically
useraccounts.cmd with UserName is created in $OEM$ Folder copied to USB-drive

B. Semi-Unattended Install - UserName = None
in winnt.sif file - unattendswitch="No" - UserNames are given Manually at Windows Welcome Screens
useraccounts.cmd is Renamed to Inactive txt file in $OEM$ Folder copied to USB-drive

C. Undefined Install - UserName = Unknown
No Changes are made in winnt.sif file or $OEM$ folder

In all cases Selecting Cancel keeps given Settings for winnt.sif file and $OEM$ folder Unchanged

Selecting Unattended Install in the Editor instead of Cancel will enable to skip the Welcome Screens
by automatic adding the unattendswitch="Yes" Setting to the [Data] Section of the Current_winnt.sif file.
The UserName given at Edit Screen 8 will not be used in the case of XPSOURCE made by nLite.

OEM or nLite winnt.sif file is detected in XPSOURCE and Auto Changed for the Installation of XP from USB.
In that case All Setup Parameters come from XPSOURCE and therefore Empty $OEM$_X Folder is Selected.

Windows XP file SETUPLDR.BIN is Renamed to XPSTP according to the 5-letter limit requirement
for making NTFS BootSector Files using MakeBS3.cmd of jaclaz
http://www.boot-land.net/forums/?showtopic=2362

In the Attended Install all Setup Parameters are given Manually during the GUI Mode of Setup Windows XP.
For each XP Source the Program Supports to launch Unattended or Attended Setup.
For Attended Setup a second SetupLoader XATSP is made ,
where winnt.sif is Patched as winat.sif using gsar.exe
So the extra Setup Option does not take extra space from the USB-stick.
Attended Install is always available as Extra Option in the boot.ini Menu.


5. Installing XP from USB

• Remove all other Removable Drives, like USB Backup Harddisks and Memory Cards
  This will enable that your Computer Harddisk in XP Setup gets DriveLetter C
• Boot with the USB-Drive plugged in and Press [Delete] key or F2 to Enter BIOS Setup
  Your BIOS may use a different key for starting BIOS Setup.
• Change BIOS Boot Priority Settings: (your USB device is listed as Harddisk)
  Make First Boot Device Type is Harddisk and give your USB device the First Priority of Harddisks
• Boot from USB-Drive and Select 1. Begin TXT Mode Setup Windows XP
  Use Only C: Drive of Computer Harddisk as Partition for Installing Windows XP
  and then Select Quick Format with NTFS FileSystem, XP Install is Automatic
  
  ***** NEVER UNPLUG USB-Drive ***** Until After First Logon of Windows XP
  
  
• New Harddisk and Creating Partitions after Booting from USB-Drive:
  Direct after Deleting and Creating New partitions, Quit XP Setup with F3
  OR Switch OFF your Computer and Boot in any case from USB-Drive again and
  Run 1. TXT Mode Setup again so that DriveLetters get their Correct Value
  So in this case one Boots ** TWICE ** in the TXT-mode Setup XP
  
  
• USB_MultiBoot.cmd can make USB-stick to be seen in XP Setup as Boot Drive U:
  In this preferred case the driveletters of Harddisk Partitions and Optical Drives
  will get there desired normal value.
  Otherwise the USB-stick will get Drive Letter D: and other drives will get shifted drive letters.
  
  The same shifting of drive letters occurs for Installing from USB-Harddisk,
  for which it is not possible to make it seen as Boot Drive U: by changing migrate.inf
  After First Logon there is only 1 USB-Harddisk partition visible as a Removable Drive.
  After Reboot for Second Logon then 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
  
  
• NON-STANDARD INSTALLS OF WINDOWS XP AND INSTALL OF WIN2003
  Install of Windows XP from bootable USB-Drive
  next to WINDOWS on the same or on a different partition of the harddisk,
  is possible by proper manually adjustment in advance of the BOOT.INI file on the USB-Drive.
  
  Adjust BOOT.INI on USB-Drive: ( Or Select Correct boot.ini Using Option B in Menu Screen )
  For Install on the Second Partition, change partition(1) in partition(2)
  For Install Next to WINDOWS, change WINDOWS to
  what will be used as Install FolderName, e.g. WINDOWS.51
  Windows Install Folder Name required according to MS-DOS 8.3 format
  
  So these non-standard installs are still possible,
  but require only small changes in the BOOT.INI on the USB-Drive in advance.
  Otherwise an ERROR Message for Setup of WINDOWS XP: WINDOWS\system32\hal.dll file missing
  will orccur on Reboot for GUI Mode.

hal.dll ERROR for Install of XP from USB
=========================================================================
In case of hal.dll Error on Reboot for GUI-mode of XP Setup:
The Error means only that in GUI mode the Windows folder is NOT found on the default location
which is normally partition(1) of your internal harddisk and would need in boot.ini Menu to Select rdisk(1)partition(1)

The error can be due to a Hidden First Partition (case of HP Computer) so that you Install on partition(2)

For your Netbook it can be that you Install on partition(3)
In that case you Select in GUI-mode and on Start of XP the line in boot.ini Menu with HD 1 - Part 3

It is also recommended to remove any Additional USB-drive like USB Backup Harddisk or External Cardreader
since these extra USB-drives may interfere in Harddisk numbering and can cause then also the hal.dll Error.

In TXT-mode of XP Setup, where you Select the partition on which you are going to Install,
you must count the partition number and use this in your boot.ini Menu on your USB-stick
on Reboot for GUI-mode of XP Setup and for Start of XP.

To solve your hal.dll Error you need to Change the boot.ini file on your USB-stick.
It can be handy to make a boot.ini with multiple entries like this:

CODE

[Boot Loader]
Timeout=20
Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[Operating Systems]
C:\btsec\XPSTP.bs="1. Begin TXT Mode Setup Windows XP, Never unplug USB-Drive Until Logon"
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Continue GUI Setup + Start XP from HD 0 - Part 1" /FASTDETECT
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Continue GUI Setup + Start XP from HD 1 - Part 1" /FASTDETECT
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Continue GUI Setup + Start XP from HD 1 - Part 2" /FASTDETECT
multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="Continue GUI Setup + Start XP from HD 1 - Part 3" /FASTDETECT
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Continue GUI Setup + Start XP from HD 2 - Part 1" /FASTDETECT

Partition Numbering starts with 1
Harddisk Numbering starts with 0
On booting from USB-stick it will count in the arcpath as rdisk(0) and your Internal Harddisk will then normally be rdisk(1)

As alternative you can try:
Install XP from USB AFTER Booting with PE from HDD or USB
http://www.boot-land.net/forums/?showtopic=5306
In this way you are insensitive to the hal.dll Error
Moreover, after booting with LiveXP into PE environment you are able to
use Disk Manager and can see what is the partitioning of your harddisk and
see which is the Active Partition e.g. the partition from which the computer will try to boot.
Also you can make then appropriate changes using Disk Manager or Acronis Disk Director available in LiveXP
=========================================================================

6. Post-Install of Drivers and Programs

The Folder usb_cfg_extra provides a script for Windows Post-Install Wizard (WPI) - http://wpiw.net/
WPI is very handy for the Automatic Install of Programs after Install of XP from USB.

In WPI script there is the option to run SFC /purgecache which deletes the dll cache
by deleting the files in Folder C:\WINDOWS\system32\dllcache
This is a very simple way to reduce the WINDOWS Folder Size by 360 MB
The Result is a XP WINDOWS Folder Size on Harddisk of only 785 MB inclusive all Updates.


================================================================================

Advanced Use of USB_MultiBoot.cmd for making MultiBoot USB-Drives

7. Adding Extra Sources for Booting with BartPE, UBCD4WIN, Windows PE 2.0 and Vista Setup

BartPE - http://www.nu2.nu/pebuilder/
or
UBCD4Win - http://www.ubcd4win.com/index.htm
can be added to USB-Drive by Selecting BartPE Source Folder in the Main Menu. Remove with Cancel.

The Folder usb_cfg_extra provides scripts for BartPE Menu

Install of Vista from USB is supported and launched via GRUB4DOS Menu
http://www.msfn.org/board/vista-t114092.html&st=6
http://www.msfn.org/board/Install-Vista-fr...6.html&st=2
For Vista Install from USB, Remove on first Restart your USB-stick.

Overflow Control is used by measuring DiskSize, FreeSize, XP-Source and
Extra Source Folders using ASP Drive Object and Visual Basic Scripting.
http://www.w3schools.com/asp/asp_ref_drive.asp
http://www.robvanderwoude.com/index.html


8. Multiple XP Install from USB and Multiple PE (BartPE and UBCD4Win) Booting from USB

Multiple XP Install from USB is Supported (max 9 sources)
http://www.msfn.org/board/SOLVED-Install-M...SB-t114543.html
Run USB_MultiBoot.cmd again using New XP Source and Empty XX_CONTENT Source Folder

Multiple PE (BartPE and UBCD4Win) from USB is supported using Multi_Partition USB-Drives.
Multi-Partition an USB-stick after using INSTALL_DUMMY.cmd from makebt Folder.
When dummy.sys is Installed in your OS, then USB-sticks are seen as Fixed Local Harddisks.
In that case you can make Multiple Partition USB-sticks with NTFS format,
allowing to combine BartPE and UBCD4WIN or different Vista Versions x86 and x64
http://www.msfn.org/board/Multiple-PE-from....html&st=11
http://www.911cd.net/forums//index.php?sho...20089&st=24
Run USB_MultiBoot.cmd again using New BartPE Source and
using Empty XX_CONTENT Source Folder and No Copy of XP Source.

================================================================================

This post has been edited by wimb_2: Mar 23 2010, 10:41 AM

[jech]

the removable usb can't be detected when i choose the PeToUSB.

[DirtyTodd]

I followed the process booted from the usb all went well but i got an error after files got copied PC restarted stating hal.dll is corrupt...

I used the attended option from it while booting because i have 2 sata HDD in my PC what can be the problem...

Also I forgot to mention i used the above solution but no luck....

This post has been edited by DirtyTodd: May 5 2009, 02:01 PM

[bonbonboi]

Hi I have created my Windows XP installation on my USB Flash Memo. but after the setup was done. I notice that it deletes the two directories $win_nt$.~bt and $win_nt$.~ls automatically. how to prevent that to be happen ?
thanks

[wimb_2]

***** NEVER UNPLUG USB-Drive ***** Until After First Logon of Windows XP

Did you unplug the USB-stick earlier or is it something else ?

[bonbonboi]

No I did not, just i noticed that in the last stage of the installation my flash memo. blinking much at The "Removing Temporary File" stage... and when later I check my flash memory I found that the windows installation files has gone!
Wondering if there is any setting could prevent the installation of removing those two directories off the flash memo.

[wimb_2]

Yes,

Normally ren_fold.cmd will rename at T-9 folder $WIN_NT$.~BT as WIN_NT.BT and $WIN_NT$.~LS as WIN_NT.LS to prevent these folders to be erased at T-1 where the blinking occurs.
Then undoren.cmd will undo the renaming at logon with [GuiRunOnce]

So something goes wrong for you, but why ....

Check your winnt.sif file in WIN_NT$.~BT folder and see if these entries are made:

CODE

[GuiRunOnce]
"binifix4.cmd c:"
"undoren.cmd"

[SetupParams]
UserExecute = "ren_fold.cmd"

Check if ren_fold.cmd and undoren.cmd occur in $WIN_NT$.~LS\I386 folder on USB-stick.

And please report your observations. May be we can find out what is going on.

This post has been edited by wimb_2: May 21 2009, 01:10 AM

[wimb_2]

=
PROGRAM UPDATE - U_XP_SET Package - Install XP from USB

USB_XP_Setup.exe has Changed:
For Install of XP from any Harddisk folder or from CD / DVD disk,
the XP Source is always Copied to $WIN_NT$.~LS folder on Target Install-drive, which enables to make use of TEXTMODE Drivers defined in winnt.sif and located in $OEM$\TEXTMODE folder of the XP Source.

USB-Harddisk with XP source can be removed after running USB_XP_Setup.exe so that it does not give unwanted DriveLetter shifting in XP Setup.
Also using rdummy.sys for USB-Harddisk is no longer needed this way.
Using $WIN_NT$.~LS as XP source folder on Target Install-drive, makes the procedure more looking like using winnt32.exe but it does NOT have the usual errors occurring when using winnt32.exe on SP3 XP Sources integrated with UpdatePacks.

Copy is NOT necessary when XP Source is on USB-stick and without using TEXTMODE Drivers, thus saving some copytime.
In this case SetupSourcePath and SetupSourceDevice are specified in txtsetup.sif to find XP Setup Source Folder on USB-stick.

General Changes for using Windows PE 2 ISO images:
The Grub4dos menu.lst Menu entries for Windows PE 2.1 or VistaPE ISO images has been modified
by using chainloader (0xff) instead of chainloader /BOOTMGR
It works quite well this way and allows to use the FileSelector also for other CD ISO images without BOOTMGR file.

Download - U_XP_SET
=

=

This post has been edited by wimb_2: May 26 2009, 07:05 AM

[EngHai]

Good day,

I have managed to install the entire Windows XP with your guide on a test PC but met with some problems and would like to seek your assistance.

Firstly

Attempting Boot from CD
Attempting Boot from Hard Drive

A Disk Read error occur.
Press Alt+Ctrl+Del to restart

I had check inside the My Computer > Manage > Disk Management and find that C: Drive is inactive.

Which part of the installation I would have done wrongly?

Secondly,

This version of Windows have been "nlited" which I have tested and installed countless PCs. However some of the setting inside Nlite do not match, examples :

- I used to be able to auto-login into Windows on the very first boot without asking if I want to turn on Protection, create user and stuff;

- My Windows Classic settings was not port over from the Nlited CD;

- Power settings like disable "Turning off Monitors" was not port over from Nited CD.

Again which part of the guide did I follow wrongly.

Thanks,

Eng Hai.

[wimb_2]

First problem:
How come that your C-drive was Not Active ?
Which partition was Active before you made changes ?
USB_MultiBoot_10.cmd did not change anything on that.

Second problem:
In case of problems of USB_MultiBoot_10.cmd with XP Source prepared with nLite,
you can use New procedure and Boot first from HD into RAMDISK with LiveXP BootSDI.img Image
and use USB_XP_Setup.exe of U_XP_SET package to prepare your BootDrive for Install of XP.

http://www.boot-land.net/forums/index.php?showtopic=5306

This post has been edited by wimb_2: Jun 3 2009, 06:34 AM

[JoysBoy]

I been trying too make my own "boot disk" for, well, ever.. it feels like it any ways, but know I feel for the first time that some one has guided my right, I think I finally can make my own boot-cd/dvd/usb-stick, with rescue programs, and other recovery programs, I just wanted to say thanks and introduce myself, this is my first post @911cd.. but I hope to contribute with some informations 'bout stuff I know and "master"....

Many thx, Joys666!

[jimw456]

Most of my UFD files are deleted when I use it to install XP. I think this is the same problem reported by bonbonboi on 5/20/09.

I performed the ren_fold.cmd and undoren.cmd checks suggested by wimb 2 in his 5/21/09 response. Everything seems OK.

Are there any other suggestions to help me troublwshoot this problem?

Thanks

[wimb_2]

What version of XP do you want to Install ?

Try the new and more general approach for Install of XP:
Install of XP from USB without booting from USB using U_XP_SET with GUI programs
http://www.911cd.net/forums//index.php?showtopic=21883
http://www.boot-land.net/forums/index.php?showtopic=5306

In case of x64 XP you need the New approach for Not loosing files on USB-stick.

Otherwise try GUI program of ilko_t
http://www.msfn.org/board/index.php?&showtopic=120444

This post has been edited by wimb_2: Aug 9 2009, 04:05 AM

[jimw456]

Thanks wimb for your response to my UFD files deleted problem. I have started reading your
suggested reference http://www.msfn.org/board/index.php?&showtopic=120444. This will take
me some time to complete.

I am installing XP SP3 Home from a UFD and it works except for the file delete problem. I
pulled the UFD at T-9 and found that $WIN_NT$.~BS was renamed. $WIN_NT$.~LS was not
renamed. I assume this is why $WIN_NT$.~LS is deleted by the Windows Install clean up
process. I noticed that the ren_fold.cmd code renames these files one right after the
other.

Any ideas on what could cause one file to be renamed and not the other?

Thanks

[wimb_2]

Is your computer New or Old ?

The $WIN_NT$.~LS folder has more than 7000 files
Timing can be the problem. The process may be proceeds before renaming is ready

The renaming occurs also for Install of XP from USB-stick prepared with program of ilko_t.

Using USB_XP_Setup.exe of U_XP_SET can solve your problem,
since the renaming of folders is not needed and not used in this approach.

[jimw456]

Thanks again wimb for your quick response to my UFD files deleted problem.

My computer is 2 years old and is reasonably fast (2.2 Ghz). In any case, I put a "pause" command in ren_fold.cmd before the ren $WIN_NT$.~LS command so I could stop program execution for a while. I held up execution for about a minute and this fixed the problem.

I think I will put a fixed delay there instead of the pause. However, I don't have any idea how much delay I will need and a trial and error approach will take forever. Do you have any recommendations in this area? Is there an easy way to automatically check and see when processing can continue? I have very little experience in this area.

I think I will also pursue the U_XP_SET approach that you recommended.

Thanks much for your help

[wimb_2]

I don't know how much delay you need, but 3-5 seconds should be sufficient
http://www.robvanderwoude.com/bht.php#Delay

But U_XP_SET is much better and recommended at any time.
Last year all development effort was spend on U_XP_SET