
   Program  usb_prep8.cmd  -  04 dec 2007

   Program  usb_prep8.cmd  Prepares Windows XP Setup LocalSource for Copy to Bootable USB-Drive.
   Also Updating Existing USB-Drive having NTLDR Bootsector and Multi BOOT.INI Menu is possible.   
   The Bootable USB-Drive is used for Install of Windows XP on Computer Harddisk.

   *** BEFORE YOU START: *** Use 2 GB USB-stick with High Read/Write Speed
   First Format to Make Bootable USB-stick with FAT FileSystem, FAT = Faster
   such that USB-stick has NTLDR Bootsector and is seen by BIOS as Harddisk
   
   Use PeToUSB.exe with Settings: Enable Disk Format with LBA FAT16X

   USB-sticks Used with Success for Install of Windows XP in ca 30 minutes:
   Apacer HT203 1, 2 and 4 GB
   Buffalo FireStix 2GB type R RUF2-R2G-S - 16 min
   
   OR Use Existing USB-stick with NTLDR Bootsector and Multi BOOT.INI Menu 
   GUIDE: http://www.911cd.net/forums//index.php?showtopic=20089 
   
   For AUTOSTART: COPY PeToUSB.exe in your usb_prep folder
   http://gocoding.com/page.php?al=petousb

   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

   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 )

   FOR USB-Harddisk make 1900 MB 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
   Without Set Active 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 


   ***** WARNINGS *****
   HP USB Disk Storage Format Tool 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.

   Using PeToUSB.exe is SAFE, 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_prep.cmd and everything in this guide is COMPLETELY at your own risk. 

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

A. ***** Most Frequently Encountered User ERRORS *****

   1. Premature Unplugging USB-Drive

      In this case boot.ini on Harddisk was not properly corrected by binifix4.cmd 
      which has to occur at First Logon of Windows XP.
      binifix4 changes boot.ini on Harddisk, such that Default rdisk(1) is replaced by rdisk(0)

      ***** NEVER UNPLUG USB-Drive ***** Until After First Logon of Windows XP
      
      Without binifix.cmd the boot.ini on our Harddisk 0 is still referring to booting from Harddisk 1
      which is our USB-stck or no disk, where in any case no WINDOWS folder is found.
      The result is ERROR: Unable to start Windows with ERROR Messages:
      a. WINDOWS\system32\hal.dll file missing ( USB-Drive again plugged in )
      b. Disk Config Problem ( USB-Drive Unplugged )

   2. C-drive is not seen as a Harddisk Drive, when Booting Windows XP Setup from USB-Drive
 
      but C-drive is no disk at all (Optical Drive, Cardreader) or C-drive is USB-Drive
      When in TXT Mode Setup you have to indicate which drive will be used for Install of Windows XP,
      look very carefully at Drive Letters and Identify to which Disk they belong.
      
      Select always the partition C: of your Computer Harddisk as the partition 
      on which you are going to Install Windows XP, and then Select Quick Format with NTFS FileSystem.
      For NON Standard Installs see Section C
      
      If the C-drive is not visible as belonging to your Harddisk, then ***** STOP *****
      There are two possible sources for this Problem to occur:

      a. New Harddisk without partitions
         In this case use Option C of Windows XP Setup to make partitions in Unused Space
         where e.g. 3 Partitions would get Unwanted Drive Letters e.g. I, J, K 
         for Computer with 2 Optical Drives + Cardreader ( 4 drives ) having Drive Letters C D E F G H 
         Then STOP Setup by SWITCHING OFF your Computer
         and Reboot again from USB-Drive in TXT Mode Setup of Windows XP 
         Then you will observe that the 3 new partitions on your Harddisk have now Drive Letters C D E
         and everything is now OK and you can Continue with Install of Windows XP
       
         For a brand new harddisk Reboot the computer after creating partitions with TXT mode Setup.
         So in this case one boots twice in the TXT-mode Setup, 
         so that after the reboot drive letters get their correct value.

         When Booting from USB-Drive, than Direct after Deleting and Creating New partitions, 
         you have to Switch OFF your Computer and Boot from USB-Drive again and 
         run 1. TXT Mode Setup again so that DriveLetters get their correct value.


      b. Mixed Config of SATA / PATA Harddisks
         In this case you have to change the computer SATA / PATA configuration (unplugging) such that 
         the C-drive is recognised as belonging to the Harddisk on which you want to Install XP
         If during TEXT MODE your usb Drive is listed first when SETUP searches for disks , 
         above SATA/SCSI disks, disable in BIOS IDE channels including the ones with CDROM/DVD attached 
         or disconnect them, this should fix the order. 
         Do not continue install if USB-Drive is listed first, this will corrupt files and MBR on it.


   3. Unable to Boot From USB-Drive

      For Windows XP Setup from bootable USB-Drive it is necessary to enter BIOS Setup by pressing [Del]
      and change Boot settings more permanent so that Harddisk is used as first Boot device type
      and USB-Drive is seen as first Harddisk. In this case everything works very well.
      In Windows Setup from USB-Drive it is essential that also after Restart for the GUI-mode of Setup, 
      booting occurs again from USB-Drive and that USB-Drive remains to be seen as first harddisk = rdisk(0).
      After Setup has completed, binifix4.cmd will make 
      the necessary correction in boot.ini on computer harrddisk by changing rdisk(1) in rdisk(0).

      Don't Select USB-Drive as Boot Device from a BIOS Boot Menu by Pressing F8 F11 or F12
      This is not a permanent Change of Boot Sequence 
      and the Reboot from USB-Drive for the GUI Mode of Windows XP Setup does not occur.

      In the case of problems with booting from USB-Drive, it is advisable to do a BOOTTEST
      to determine if your computer is able to boot from your USB-Drive.
      If not successfull, you have to use a different Computer / USB-Drive combination.

      First Format to Make Bootable USB-Drive with NTLDR Bootsector Using:
      PeToUSB.exe with Settings: Enable Disk Format with LBA FAT16X
      OR Use Existing USB-stick with NTLDR Bootsector and Multi BOOT.INI Menu 

      For AUTOSTART: COPY PeToUSB.exe in your usb_prep folder
      http://gocoding.com/page.php?al=petousb

      BOOTTEST:
      When you format it copy on USB Drive ONLY ntdetect.com, NTLDR from your XP source, 
      and create BOOT.INI in USB Drive root:

BOOTTEST BOOT.INI CODE:

[Boot Loader]
Timeout=10
Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[Operating Systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="TEST" /FASTDETECT 
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="TEST 1" /FASTDETECT

     Start the PC and if you see the menu, your USB-Drive is ready- format it again and use usb_prep.cmd
     PEtoUSB has an option for LBA, use it first, if doesn't boot use without that option.


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


B. ***** Description of usb_prep.cmd Program *****

   Program  usb_prep.cmd  Prepares Windows XP Setup LocalSource for Copy to Bootable USB-Drive.
   Also Updating Existing USB-Drive having NTLDR Bootsector and Multi BOOT.INI Menu is possible.   
   The Bootable USB-Drive is used for Install of Windows XP on Computer Harddisk.

   The First Working usb_prep Program was made by ilko_t based on the Procedure 
   he has developed with help of jaclaz, porear and cdob and described in 
   http://www.msfn.org/board/boot_install_USB_key_t61384.html&st=199
   MakeBS.cmd and binifix4.cmd used by usb_prep.cmd were made by jaclaz to 
   Create the USB-Drive BootSector File and for Fixing boot.ini on Harddisk
   
   Later improving and testing of the usb_prep.cmd Program was done by wimb
   The code for making Windows XP Setup Bootfolder $WIN_NT$.~BT by Parsing DOSNET.INF was made by wimb
   In this way launching winnt32.exe /noreboot .... was avoided, which would otherwise
   delete LocalSource folder $WIN_NT$.~LS in ROOT of ANY Drive, e.g. existing on USB-Harddisk or USB-stick.

   A very important step in the development of the XP Setup from USB-Drive Procedure
   was given by cdob for the WriteProtect of the USB-Drive with migrate.inf
   Without the WriteProtect $WIN_NT$.~LS Folder and partly $WIN_NT$.~BT Folder will be Removed
   during XP Setup, so that the USB-Drive would be Usable Once.
   But Fortunately this Problem was solved and the USB-Drive can be used many times for XP Setup. 

   For UNATTENDED Install make Changes in usb_prep folder:
   Change Product Key in winnt.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.

   Change $OEM$ folder to your needs, usb_prep.cmd Copies $OEM$ folder in $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/   Reference

   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 and winnt.sif from usb_prep 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 usb_prep folder. Then there is no problem at all.

   NLite does not make an $OEM$ folder for Registry Tweaks and UserAccounts.
   NLite makes in i386 folder the file NLITE.IN_  with Registry Tweaks and UserAccounts Info.

   Remove Any Floppy Disk / CD / DVD 
   A:\winnt.sif file with MsDosInitiated="0" might ask Unwanted for Install from CD



   ************* Use of VBScript with cscript.exe and wscript.echo ******************************

   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

   For Info on Batch Programs
   http://www.ss64.com/index.html
   http://www.robvanderwoude.com/batchfiles.html
   http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/batch.mspx?mfr=true

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

   Start Program usb_prep.cmd - The Flow of the Program is Shown below:

   Program  -  usb_prep8.cmd  -  04 dec 2007
   Prepares Windows XP Setup LocalSource for Copy to USB-Drive

   *** BEFORE YOU START: *** Use 2 GB USB-stick with High Read/Write Speed
   First Format to Make Bootable USB-stick with FAT FileSystem, FAT = Faster
   such that USB-stick has NTLDR Bootsector and is seen by BIOS as Harddisk
   
   Use PeToUSB.exe with Settings: Enable Disk Format with LBA FAT16X

   USB-sticks Used with Success for Install of Windows XP in ca 30 minutes:
   Apacer HT203 1, 2 and 4 GB
   Buffalo FireStix 2GB type R RUF2-R2G-S - 16 min
   
   OR Use Existing USB-stick with NTLDR Bootsector and Multi BOOT.INI Menu 
   GUIDE: http://www.911cd.net/forums//index.php?showtopic=20089 
   
   For AUTOSTART: COPY PeToUSB.exe in your usb_prep folder
   http://gocoding.com/page.php?al=petousb

   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

   FOR USB-Harddisk make 1900 MB 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


   Prepares Windows XP LocalSource for Copy to USB-Drive:

     0) Change Type of USB-Drive, currently [%usb_type%]

     1) Change XP Source Path, currently [%xpsource%]

     2) Change Virtual TempDrive, currently [%tmpdrive%]

     3) Change Target USB-Drive Letter, currently [%usbdrive%]

     4) Make Tempimage with XP LocalSource and Copy to USB-Drive

     5) Use Existing Tempimage with XP LocalSource and Copy to USB-Drive

     F) Change Log File - Simple OR Extended, currently [%logtype%]

     Q) Quit


   choice of Source and Target Drive are selectable at the beginning in a Start Menu.

   The Program Flow is Recorded in a Simple usb_prep.log file.
   In the Extended logfile All FileCopy Details are Recorded.

	***** WARNING Existing Folder $WIN_NT$.~LS on USB-Drive Detected   *****
        ***** Files will be Replaced when Tempimage is Copied to USB-Drive *****
 
   Making in TEMPDRIVE the XP Setup LocalSource folders $WIN_NT$.~LS and $WIN_NT$.~BT

   Parse DOSNET.INF for making Windows XP Setup Bootfolder $WIN_NT$.~BT
 
   Copy XPSOURCE folders cmpnents and i386 to TempDrive folder $WIN_NT$.~LS

   Copying custom files to temp drive ....
   binifix4.cmd   migrate.inf    winnt.sif      boot.ini   ren_fold.cmd   undoren.cmd

   Copying XP Setup Root files to temp drive ....
   txtsetup.sif   bootfont.bin   ntdetect.com   ntldr      setupldr.bin

   Adding lines to TXTSETUP.SIF ....
   Extra SourceDisksFiles: ren_fold.cmd  undoren.cmd  binifix4.cmd

   Adding rdummy.sy_ to make Fixed USB-Harddisk seen in XP Setup as Removable Device
   
   Adding lines to WINNT.SIF ....
   Extra SetupParams: ren_fold.cmd
   Extra GuiRunOnce: undoren.cmd  binifix4.cmd
   For USB-Harddisk Only:  Extra GuiRunOnce: sc config rdummy start= disabled

   $OEM$\CMDLINES.TXT is used for making UserAccounts and install of Registry Tweaks at T-12
   Info see: http://unattended.msfn.org/unattended.xp/   Reference

   Adding $OEM$ folder with UserAccounts and Registry Tweaks if present ....
   Adding OEM folder with BTS DriverPacks if they were used ....
   INFO http://driverpacks.net/DriverPacks/overview.php
   Adding Custom presetup.cmd for BTS DriverPacks ....
   presetup.cmd could give Windows ERROR Alert: No Disk due to Cardreader, Use 4x Continue XP Setup
   presetup.cmd was changed to limit the range for Finding Drives with OEM TAGFILE
   presetup.cmd was changed to Delete setupold.exe , necessary for Repair Install Windows XP option

   Copy TempDrive Files to USB-Drive in about 15 minutes  Continue   Enter Y
   Update USB-Drive use Total Commander Synchronize Dirs  END PROGR  Enter N

   FileCopy to USB-Drive Start
   Root Files
   Add entry in BOOT.INI to launch TXT Mode Setup  using makeBS.cmd
   Added to boot.ini menu "1. TXT Mode Setup Windows XP, Never unplug USB-Drive Until After First Logon"

   $WIN_NT$.~BT Folder   Copy to USB-Drive
   $WIN_NT$.~LS Folder   Copy to USB-Drive
   OEM Folder with BTS DriverPacks Copy to USB-Drive

   MkMigrateInf2.cmd
   Would you like USB-Drive to be preferred Boot Drive U:  Enter: y
   In that case migrate.inf is changed with MkMigrateInf2.cmd
  
   For Mixed SATA / PATA Config: Don't change migrate.inf  Enter: n
   For Bootable USB-Harddisk   : Don't change migrate.inf

   Would you like to unmount the Virtual Drive ? 

   End Program - USB_PREP.CMD will be Closed


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


C. ***** NON-STANDARD INSTALLS OF WINDOWS XP *****

   Install of XP Windows from the bootable USB-Drive 
   next to WINDOWS on the same or on a different partition of the harddisk, 
   was realised successfully by proper manually adjustment in advance 
   of the BOOT.INI file on the USB-Drive.

   Adjust BOOT.INI on USB-Drive:
   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 FoderName, e.g. WINDOWS51

   So these non-standard installs are still possible,
   but require only small changes in the BOOT.INI on the USB-Drive in advance.
   Examples of such boot.ini files are given in the Help_Info folder.

   USB-Repair Install of Windows XP is Supported with the rdisk(1) rule in boot.ini on Harddisk.
   However, it is advisable to use a Fresh Install of Windows XP in only 30 min.
   In case of Windows ERROR Alert: No Disk due to Cardreader, Use 4x Continue XP Setup


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


D. ***** Further Improvements of (Multi) Bootable USB-Drive: *****

   Using Windows XP Source with Updates and DriverPacks Integrated:
   first using RyanVM Integrator http://integrator.siginetsoftware.com/index.php?download
   with Update Packs and Addons http://www.ryanvm.net/forum/index.php?sid=58adec10fb305c75d490d2bd5184b68a
   and then for DriverPacks using DP Base http://driverpacks.net/DriverPacks/overview.php
   and for Unattended Install use winnt.sif file http://unattended.msfn.org/unattended.xp/ 

   $OEM$\CMDLINES.TXT can be used for making UserAccounts and install of Registry Tweaks at T-12
   On first logon the Extracted BTS DriverPacks are deleted, which normally takes a long time,
   because SystemRestore copies them to System Volume Information folder.
   The Disable_SystemRestore.reg Registry Tweak prevents this action, so that first logon is much faster.

   It is interesting to integrate only 2 BTS DriverPacks: LAN and Mass Storage with text mode enabled.
   This approach makes the Install Procedure most suitable for a great variety of computers.
   Make a Ghost System Backup after Setup has completed.
   Then Use Computer Custom Driver-CD OR Use the other DriverPacks Manually when Updating Drivers.
   The extraction and deletion of these large DriverPacks would take a lot of time during Setup. 


   Guide for MultiBoot USB-stick with boot.ini Menu made by wimb
   FROM: http://www.911cd.net/forums//index.php?showtopic=20089

   In this Guide is described How to Make a MultiBoot USB-stick, where boot options
   as MS-DOS, FREEDOS 1.0, GRUB4DOS, BartPE, TXT-mode Setup Windows XP, WinPE 2.0 and SYSLINUX 
   can be used directly from boot.ini Menu.

   The booting mechanism of NTLDR with boot.ini Menu and the use of Bootsector Files in boot.ini 
   has been excellently explained by jaclaz
   http://www.911cd.net/forums//index.php?showtopic=16980&st=8


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


E. ***** Use Total Commander For Update of Existing USB-Drive *****

   Total Commander Synchronize Dirs in Asymmetric mode Results in an Update of the Right Directory

   Use Total Commander For Update of Existing USB-Drive having XP LocalSource Folders:

1. Before the FileCopy to USB-Drive starts, it is possible to Leave the usb_prep.cmd Program,
   while keeping the tempimage.img with XP Setup LocalSource Mounted in the Virtual TEMPDRIVE
   Otherwise use Mount_TempImage.cmd for Mounting Existing some tempimage.img file in TEMPDRIVE

2. Plugin Your USB-Drive having XP LocalSource Folders

3. Start Total Commander
   Select as Left  Directory Your TEMPDRIVE as Source
   Select as Right Directory Your USB-Drive as Target

4. Open on Both sides $WIN_NT$.~BT Folder

5. Select Commands / Synchronize Dirs ...
   Select Asymmetric and Subdirs On
   Select Show - Green and Blue On
   Select Show - duplicates and singles On ( Default )

6. Select Compare to Start the comparison between the two chosen directories

   The symbol in the middle defines the copy direction, which can be chosen by the end user. 
   The coloring of the text defines the default copy direction determined by the comparison:
   Green: Copy from left to right
   Blue:  Delete on the right side (Asymmetric mode, the file has a Red cross symbol X in the middle)

   Never Make a Blue Arrow because that has a Copy direction from Target to Source (Unwanted)
   
   The symbol in the middle is not Selected when the Source File is Older then the Target File.
   In general Update of such files must be Accepted giving them the Green Arrow,
   because our TEMPDRIVE Source is always considered better than the USB-Drive Target.
   An Exception is migrate.inf ( and boot.ini in Root Dir ) which must NOT be replaced on USB-Drive.

   The Bootsector Files SETUPLDR.bs and BackupBS.ori in the Root of the Right Directory 
   would get in Comparison a Red Cross, but these files must not be Deleted from the USB-Drive.
   So for these 2 files the Red Cross must be removed by mouseclick.

7. Select Synchronize to Automatically
   Copy    the Green selected files from Left to Right Dir ( Use No Confirm Overwrites )
   Deletes the Blue  selected files on the Right Directory ( marked with Red Cross in the middle )

8. Repeat Steps 4-7 for the $WIN_NT$.~LS Folder and the OEM Folder if present

9. Open on Both sides the Root directory

10. Copy txtsetup.sif from the Left Source Dir to the USB-Drive Target Directory on the Right side

Instead of the Copy of about 6000 files in 15 minutes to USB-Drive,
one needs to copy may be only 150 files in the Asymmetric Synchronize Update.

***** GOOD LUCK *****

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

F. ***** USB-stick Requirements and Benchmarking *****

   A tool to test your USB key (speed...), Fart and Convenient:
   http://www.flashmemorytoolkit.com/
   My Apacer HT203 with nominally Read/Write Speed 30/18 MByte/sec is benched as 11/8 MByte/sec

   Very nice program to test your sticks speed, AFAIK backing up data is not required, but you never know... 
   http://www.hugesystems.com/supportspace/bench32.exe

   Test on many different USB sticks, thread is in bulgarian, but pictures give very clear idea:
   http://www.hardwarebg.com/forum/showthread.php?t=92033


From: http://www.abxzone.com/forums/f55/where-get-atto-44211.html

ATTO
http://www.attotech.com

Directory
http://www.attotech.com/software/app1.html

The Disk Benchmark is part of this Utility package.
Windows SCSI Utilities Version 1.63 
http://www.attotech.com/software/files/ept163.exe

All you probably will want to use is the benchmark utility. Out of the 3 programs installed.
Since you actually don't have an ATTO SCSI card in your system (unless you really do), 
I would recommend not using the SCSI utilities that are also installed.

You can go into the C:\ATTO directory where the program was installed and copy these three files:
bench32.cnt
bench32.exe
bench32.hlp
And copy them to a safe place because you don't need to Install the utility again, 
you just need these three files. 
You can now delete the C:\ATTO folder because you have a safe copy of the 3 files 
that make up the ATTO Disk Benchmark.

Just run Bench32.exe directly, whenever you want to run the ATTO Disk Benchmark program.

You will want to leave all the settings at Default.
Also you can look and see how others in the Forums are using the settings in the Benchmark program, 
to make sure you are comparing Apples with Apples..... Or should we say PC's with PC's! *heh heh heh*

Be sure to choose the Drive you want tested before pressing the "START" button.

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

