I'm having a problem with this...
The TXT-mode install works great and so does the GUI. Problem is: When I try to boot after everything is done I'm missing hal.dll. :/
I'm guessing my boot.ini is messed up or something and that's why it can't find the file but I could be wrong. Downloading WinPE now to try and see if it is (Not using BartPE because it doesn't work, just decides to use 100% cpu and after waiting 10-15 minutes I got sick of waiting and killed the process).
Anyone have any other ideas? Would really appreciate some help.

Please read this post and the next few:
http://www.msfn.org/board/boot_install_USB...762#entry698762

I think you unplugged USB stick before first logon. Do not do that if you did. Stick MUST be left plugged until you COMPLETE your first logon, when 2 batch files are executed, fixing BOOT.INI and renaming back the 2 source folders+txtsetup.sif on stick.

If that's not the case please post your boot.ini on the destination hard drive. The problem is with it.
Another way- what's the name of 2 WINNT folders on stick after installation?

I have no idea what really happened but everything works now at least. First time when I tried to install after TXT and GUI was done, when I tried to boot (without removing the stick or anything) hal.dll was missing. When I tried to reinstall with that version it said winnt.sif didn't exist and it couldn't boot the installer.
Gave it another go with different sources and after that install was done, same thing there was no hal.dll and didn't remove stick. However my WIN.LS and BT folders disappeared...
Anyway, fixed it by getting WinPE on my USB-stick and changing my boot.ini-file.
After that everything worked out fine.

@flasklax

Can you post some details:

1. What motherboard/model/BIOS version
2. What storage devices you have (SATA/IDE disks, DVD/CD, card readers, printer with card reader...)
3. In case of SATA disks how are they set up in BIOS? In SATA/ACPI/IDE/RAID mode...Where are IDE devices connected if you have such?
4. How do you choose to boot from USB? By going in BIOS and changing boot order or pressing F8/F12/something_else at boot and choosing USB or....
5. What entries did you have in BOOT.INI on destination hard drive, before you edited it? If don't remember there must be a backup file of BOOT.INI in your destination root.

Thanks.

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

So, strangely enough.. I have found a bug perhaps.
I believe it is hardware specific though.

I have a Corsair Flash Voyager 4gb usb stick.
One of its features is wear leveling.

http://www.corsair.com/_faq/FAQ_flash_driv...ar_leveling.pdf



After doing several reads and writes and modifications to the files on this usb stick, it somehow became unbootable.
Since the ntldr is geometry specific, and this drive moves data around for wear leveling, I belive its somehow related.

Solution, please make it possible to rewrite the mbr and extract the bootsector without having to format.

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

Also, though rather difficult to get the hang of, FINDPART can be useful:
http://www.partitionsupport.com/utilities.htm

FINDPART CHSDIR <drive letter>

will give you the position of files.

jaclaz

Rats.. I just ordered a Corsair GT 4Gig just for this.
Guess I'll find out if "wear leveling" is an issue when it gets here.

By reading the doc though it doesn't look like it should be an issue.

The addressing of data is the same to the computer, it's the lookup table
in the stick itself that does the remapping and is supposed to be
transparent to the system.

It isn't doing this at an OS/FS level.

But we shall see.

I haven't had the chance to investigate any further but I should have some time in a few days.

I have another question though, I noticed with the scripts there are a bunch of $OEM$ and registry files.
But I have noticed they do not copy (nor does my OEMinfo.ini and OEM.bmp)

There seems to be a discrepancy in which option in the winnt.sif that copies files from the $OEM$ folder.
Its supposed to be OEMPreinstall option - the one that breaks F6 compatibility.. but..
In fact I made a cd with Nlite to see what was going on, and it still didn't copy those files.

Very strange.

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

Correct , the "wear leveling" thingy does NOT affect the position of files on the stick (as seen by the OS), but other things may cause it, most probably previously deleted/overwritten files, incorrect order when copying files to it, and what not.

In the famous "Dietmar's Thread" on 911CD, experiments proved that the best way to make sure that USB booting procedure is to start from a "wiped" drive, though noone was able to pinpoint the actual cause of the occasional failures.
However, there is no need to write 00's or (better) F6's to the whole device, but doing so for the first, say, 100 sectors, i.e 51200 bytes, should ensure that there are no "leftovers" that can cause problems to filesystem.

jaclaz

Still waiting for the Corsair GT to get here so in the meantime decided to try this out on a generic PQI 4GB stick.

1. The text mode copy took about an hour.

I bench'd the stick on the same system prior to the install and got 12MB reads.
While not great, it seems it shouldn't have been that slow on the copy.

I saw another reference here to larger sticks and fat32 being slow.
The total space being used on the stick now is 522MB so going to try to partition it as 700MB with FAT16 for grins.

2. The key doesn't show as C: during the partition portion of the setup.

Think this lead to the boot.ini issues that showed up after text mode install.

And yes, I'm making sure the boot selection of the stick is done in BIOS.
Stick was never removed.

What's also kind of odd is when the stick had a dos image on it, it did boot up as C:

System Info:
Abit NFM2 - BIOS 214
Single PATA with 2 partitions (30Gig primary active + 200Gig primary)

During text mode setup I deleted the 30Gig partition and selected it to install on.

When text mode finishes, reboot, and select GUI, I got an error that is a bit misleading. "missing <Windows root>\system32\hall.dll" due to boot.ini telling it to look at the other partition (which has NTFS on it).

I had to set the boot.ini GUI line to partition 2 (original had 1) on the stick for it to work. And of course it errored out trying to put a boot.ini on the hdisk after login. Had to manually put one on.

The resulting install did end up with a C:

So it looks like to setup I have 2 partitions but it's treating the second as C: and the first as D: which is weird (c: was partitioned first).

I'm backing up the D: partition and going to nuke both and try again.
So while off to somewhat of a rough start I have some things to try.

The Program asked you to do:

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

For whatever reason you can't use FAT16 on this 4GB stick (or the Corsair 4GB - it just arrived) using the HP USB Disk Disk Storage Format Tool. I had ignored the FAT16 requirement mentioned for PeToUSB as being needed for all and didn't see it as a requirement.

PeToUSB did format the sticks as FAT16.

Suggestion for a change to the wording to: or something similar. It might make it even better to mention up front you can't use some 4GB with the HP Tool (and obviously larger sticks will need some extra work).



Ok - seemed to have missed that bit in the doc.

@signal64
FAT16 is for USB boot compatibility and sometimes speed. If FAT32 works for you, that's ok.
About slow speed- 1) check your USB speed settings in BIOS and 2) do some benchmarks with small files, the speed you mentioned is probably valid ONLY for large files. A few posts before (post #386) you will find link to a good program, it will tell you how fast your stick is with small files, like the most of source files are.

At times I have seen some boards running USB 1.0 speed with certain USB CD drives when installing Windows.
This is even though USB 2.0 is enabled in BIOS so was wondering if that was the issue in this case.

I used bench32 for the speed test I mentioned earlier.
Here's the results on my victim Abit NFM2 system I'm testing the install with.

PQI 4GB:
http://img206.imageshack.us/img206/8015/000001vb3.jpg

And for grins the Corsair 4GB Voyager GT:
http://img141.imageshack.us/img141/7081/000002go1.jpg

Now that things are clearer I did a quick install with the Corsair (FAT16) and text mode took about 15min to copy.
I wasn't timing it closely as I was just seeing if it would work at this stage.

If anyone is interested I'll do some comparison testing (and timing things closely this time) with FAT32/FAT16 on these sticks with a 680i motherboard.
Need to load that puppy up again tomorrow.

Finally got it working with USB hard drives.
Dummydisk.sys was remade, many many thanks to Anton Bassov, who responded to my emails and gave the hint what had to be changed in source code, despite being a single statement.

The new rdummy.sys worked fine loaded from txtsetup.sif , USB hard drives are now seen as removable, thus having lower priority when getting drive letters. To be tested on other machines and sources.

Without rdummy.sys:


With rdummy.sys:


Furthermore- Setup considers it as critical SCSI driver and adds it as service in the new installation starting at boot time. Every USB hard disk attached is seen as removable. This is not wanted, will be taken care of.



A little bug in the driver- if during Txt Setup when disks are detected and/or format or repartitioning performed, quit by pressing F3 causes BSOD, without any harms though. The driver doesn't have unload functionality, I believe that's why, may be Anton or anyone else familiar with this matter could add such.
If Setup is let to finish copying files and restart everything is fine, no BSODs, unattended install was performed without any glitches with XP SP2 source. Boot.ini and source folders are as with USB sticks.

Next days I'll add the necessary changes to the bat files, wimb already included an excellent help file so not much left to be done here.

A few more results:
Make small (15MB) image file, mount it as disk, copy boot files there ($win_nt$.~bt folder, setupldr.bin, ntdetect.com and txtsetup.sif in root), use Grub4Dos to mount it as fd0- no go, Setup starts, but cannot find biosinfo.inf in $win_nt$.~bt. Grub4Dos floppy is ignored, why it searches in $win_nt$.~bt? TXT Setup considers it as hard disk. Copy all files for ~BT folder to root- same result.
Mount it as non- existing HD- hd5. Same story, in previous tests I found that setup insist on having all boot files on first HD or complains about biosinfo.inf
setupldr.bin in 6 XP boot floppies differs from normal XP setupldr.bin. Using it didn't help, neither disk101 marker files.

I've tried also to speed up USB boot, moving usbstor.sys, disk.sys and all usb drivers to earlier stages, like in [BootBusExtenders], this didn't help. It seems like Setup loads all drivers, but actually starts them when "WINDOWS IS STARTING" is displayed. I've read similar statement in the past, no idea where it was.

Regards,
ilko

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

That's strange, I have small HD images of recovery console working allright, directly or from grub4dos, both "directly" and using the 2003 RAMDISK.SYS to boot them.
I have experimented with /minint, /CMDCONS and $win_nt$.~bt
(but this works with image mounted as HD0)

Some info is on this thread:
http://www.boot-land.net/forums/index.php?...=2692&st=10

Most probably it won't work on "FD" type of image, but maybe one can use once again the grub4dos mapping features to exchange drives?

Can you post a DIR /S>Setupdir.txt of your 15 Mb image?

I'll see if I can re-create it in a way that it works.

jaclaz

Good going, ilko!
Keep on the great work!

Hi all,

Sorry about the delay, lack of spare time lately.

Here is what has to be added to usbprep.cmd to add rdummy driver.




rdummy.sy_ and it's source code are in the attachment.
Installation tested with XP SP2 source, 80GB IDE HD, generic IDE-USB adapter. Drive formated FAT16x with 1.9GB partition using PEtoUSB. XP built-in format didn't make it bootable.
On first GUI logon rdummy service is disabled, on next reboot it'll be inactive. If one needs to reenable it simply change startup type in services to 0, or use "sc config rdummy start= boot".

WARNING!!! There is no warranty whatsoever for this driver and it's behavior, use it COMPLETELY at your own risk.
The only issue I've seen by now is BSOD 7B when F3 is pressed to quit from Setup, but there may be others. Not tested with 2K/2K3.


@wimb- would you add this as an option, the same way we choose source path etc. I didn't want to mess with the batch file.

A few minor suggestions for usbprep.cmd-

1. boot.ini options on stick could be easier to be like:


2. For the usbprep.cmd options- I'd rather "dumb" copy all files and folders from source\I386 to ~LS\I386 skipping existing files, instead of having option 0. This doesn't add too much space, USB sticks are bigger and if one would like smaller source, he would do that in advance. It's also safer.

@all- Question- xcopy /d would copy non-existing files to target, I read that if files are NOT newer than 1 day they'd not be copied, is that right? What would happen if one makes a new XP source today, NLite it and use xcopy /D ?
http://www.ss64.com/nt/xcopy.html

3. Boot.ini on target drive- the second entry is "USB Repair Microsoft Windows XP Professional", may be is good idea to add "do NOT use to start", or something similar.

4. Option to delete tempimage.img could be nice after unmounting virtual drive.

What do you guys think?

@jaclaz- I wanted to boot from mapped by Grub4Dos floppy image, containing all boot files. Setup keeps looking for bioinfo.sif in ~BT folder. That means for me it does not recognize the mounted floppy as such, but rather as a hard drive.
Then I saw cdob posted some results trying to achieve the same goal, post #189. I am curious if boot files when he was getting BSOD 7B were in ~BT folder or in root. I couldn't go that far when files are in root. For now I'd rather not play again after reading his results.

@tonich-Thanks, nice to see you around.
This above applies for all in here

regards,
ilko

@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 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

Glad it worked, I gonna have a beer for it tonight

Anyone thinking of GUI ?

Regards,
ilko

Microsft Deploy let's you install windows xp / vista / server 2008 from a flash drive.

-gosh

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

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

download microsoft deploy from the microsoft download center. I installed it and used it to do an unattended install of xp sp2 from a 1 gig flash drive. MS Deploy let's you add your own apps and hotfixes and custom settings. I only did a basic install to test functionality.

-gosh

Thanks for that, please enlighten us some more

As far as I saw it, MS prepares WinPE with the setup source you provide. This WinPE could be booted from USB media, CD or whatever. Or did I miss something?
Unfortunately my fresh installation of Microsoft Deployment keeps freezing when building WinPE ISO, so I couldn't dig much.

@wimb I think you are going to need this:
Microsoft Deployment:
http://download.microsoft.com/download/b/3...Toolkit_x86.msi

It may download the necessary components for you, or get WAIK from here (992.2 MB ), extract image and place WAIK MSI and WinPE.zip in the temporary folder, which will be created when you start download via Microsoft Deployment in \program files....

http://www.microsoft.com/downloads/info.as...5-LRMAIK_EN.img

Quoting file names by memory, installation is in my home PC, if you have troubles I can post exact names and paths.

@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


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

Hmm..., no, sorry.

However, I am very partial, not being at all a programmer, to the Wizard's Apprentice:
http://wizapp.sourceforge.net/
the exe is just 70 Kb in size and has all the needed features.

Since the original procedure has been written in batch (no .NET installation required ) it would be very easy to "convert" it in a way that uses this little proggie's features, when compared to other viable solutions (like AutoIT).

wimb, are you reading this?

Have a look at my VDK pseudo-GUI batch that uses it to have an idea of it's potentiality:
http://home.graffiti.net/jaclaz:graffiti.n...ts/VDM/vdm.html

jaclaz

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

Cheers,

wimb

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

http://www.bootdisk.com/ is a great site that may help. You may wish to check out their utilities section.

Can I ask you the meaning of your post in this thread?

What would bootdisk.com help for?

Which utility on that site would help, and it would help who?

A good idea, expecially for people at their second post, would be to actually read what the thread is about, before posting unrequested and generic info.

jaclaz

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

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



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

thank you
tried it and works fine

Hiya

Got problem when trying to install... I run TXT mode and it loads up all drivers... at some point at very end of "first" txt mode it says on the bottom bar "Preparing to run Windows...." NOW i have blue screen. No folders on drive C: was created, no folders on USB drive created aswell... I cant see screen when you press Enter and than f8.

Ive seen taht usb_prep8 takes ntldr and other files from C: is it possible that it might be fault o my C: files?
Other thing is that my usb is seen as fixed not removable. So when PEtoUSB loads i need to chage category to fixed.

Got 3 partitions c-ntfs d-fat e-ntfs f-cd g-usbfixed. Should all be same? Should i combine them all to one partition?
Im lost i tried few times. Is there way ti change my usb to removable instead fixed?

Many thanks
Kind regards
Locaj

Hi Locaj,

If I understood you correctly I see 2 problems:
1. BSOD
2. Your stick seen as fixed

To resolve them:
1. What hardware you are booting on? Dell?
Try to overwrite on stick ntdetect.com with Dietmar's modified ntdetect.com. Details here:
http://www.911cd.net/forums//index.php?showtopic=14181

2. Did you try in usb_prep.cmd changing USB drive type to USB hard drive? Please try so, I think it was option 0.

Few other questions-
3. What is the windows version you are installing, is it customized?
4. Did you insert custom mass storage drivers?
5. What do you mean here-

You should provide details about your stick model etc. Some manufacturers have utilities for that purpose, did you have a look at it's web site? jaclaz may help you more on this question.

@wimb- nice work
I haven't tested latest batch, no spare time at all, just a quick question which bothers me- are we sure there are not "not documented" actions from winnt32.exe? In case of such it would be tricky to replicate it's behavior. You say the problem with winnt32 is that it deletes any $win_nt$... folders, I think for regular user that shouldn't be a problem. How many have those folders on their hard drives? If they have it intentionally, probably deletion of such wouldn't bother them much, warning should be enough. Just my opinion.
Thanks again for your time and enthusiasm

Regards,
ilko

Now WINPE is very good.
this problem should can slove

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

Hiya

Thanks... I will try ntdetect.com. Will try to chage type to 0.

Im trying defoult english windows xp sp2 from oryginal cd =-].
I dont have any custom mass stroge drivers... WinXp automaticly detect and install it.
I meant i got 3 partitions... Disk C: which is NTFS. Next is D: and its Fat32 and E: NTFS. So maybe its problem that i have few different partitions.

My usb is complete noname. I cant even take the cover off to look at chips. Its glued and very hard to take off. Tried few times... only way is to crush the cover totaly ...

So rdummy.sys will make my usb seen as removable? So prep8 can do it right?
But it will be only short time coz after reinstall winXP will detect as fixed... something like that ?

Many Thanks
Locaj

Well, the idea is to find the VID and PID of the device via SOFTWARE, without being cruel to the poor little thing....

See these:
http://www.911cd.net/forums//index.php?showtopic=15776
http://www.boot-land.net/forums/index.php?showtopic=1659

jaclaz

Hiya

Ive just changed Fixed to Removablo with this utility



So easy...
Now it should bo all right ? =-]

usb_prep8.cmd doesn't support x64 because Virtual Disk Driver doesn't support it

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

So I tried this and I'm getting the following error message:
"The specified Setup script file (C:\XPSOURCE\i386\winnt.sif) is inaccessible or invalid. Contact your system administrator."

I have no idea why I'm getting this message. Then when I hit ok, I get Making of LocalSource folder $WIN_NT$.~LS Ready Press any key to continue... Copying custom files to temp drive.... The system cannot find the path specified. It then takes forever to CRTL+C out before getting :

Does T:\$WIN_NT$.~LS\I386 specify a file name or directory name on the target (F = file, D = directory)?

C:migrate.inf 1 file copied
same question as above

more files are copied and then I get an error message about not being able to read/edit the tstsetup.sif file.

I checked the names, locations, cases, & attributes on said files, what else am I missing?

Maybe the SOURCE files are in some way nonstandard.

I mean whence they come from?

An OEM release (DELL,HP, etc.)?

Have they been modified in some way (slipstreaming, nlite, HFSLIP, etc.) ?

Most probably it's the first error (WINNT.SIF error) that triggers a chain of errors.

jaclaz