It might be that your winnt.sif file is causing the error. Check this file in Notepad Editor.
You used usb_prep6.cmd where you had to give and change the product key in the given winnt_sif.txt file
and copy this file as winnt.sif in your XPSOURCE\i386 folder.

There is a newer version of the program named usb_prep8.cmd which makes the XP Bootfolder quite differently,
without running winnt32.exe . It might well be that in this case you don't have your problem.
In this case the given winnt.sif file needs to remain located in the usb_prep8 folder.
The winnt.sif file provides the answers needed for Unattended Install of Windows XP and needs your Product Key !
Did you try to use usb_prep8.cmd ?

Regards,

wimb

I'm pretty certain I'm using version 8 as I had downloaded it based off the link in wimb's sig. I am using an OEM {Dell} xp s2 source and a customized winnt.sif that I made using a combination of nlite & my knowledge of the available options/commands in said file. I didn't use the nlite created nor the usb_prep ones, I just cut & paste as well as compared versions for things I was missing.

I wasn't sure where I was supposed to put the drivers so I put them in both places (the usb_prep $oem folder & the one in the XPSource\$oem folder). But I didn' t get that far in the installation. Sorry it took so long to reply but until I can get a "stable" copy of XP running I don't exactly have a working PC at work.

I reimaged my machine but the image we have is bad so I still need to figure out how to get this to work as I need to create a new image as well.

Oh, I also slipstreamed the recent updates into the OEM folders as there are like 60 of them for the version I have.

Thanks & Happy New Year (Joyeux Noel & Prospero Ano)!

In your Private communication you were speaking of errors when using usb_prep6.cmd
So I supposed that you did not use version 8, but it is clear now that you did use version 8

Can you post your winnt.sif file (after wiping the product key) ?
Where did you put your winnt.sif file ?
And what did you do with the well working winnt.sif file provided in the usb_prep8 folder ?

It is worthwhile to try the winnt.sif file provided in the usb_prep8 folder
and keep it there and change only the product key.
And I prefer not to use nLite.

Try first usb_prep8.cmd on a clean xp sp2 source and if successfull
then use RyanVM Integrator for integrating post-sp2 Update Pack, IE7 and WM11 Addon
and after that use DPs_Base for integrating only DriverPack Mass Storage with text mode enabled.
Everything is described in the provided Help_usb_prep.txt file, see section D.

Regards,

wimb

Happy New Year everyone

@pucelle- your information is confusing

The above message indicates that there is something wrong within your winnt.sif, look here:
http://support.microsoft.com/kb/247882

At the same time you said that you used USB_Prep8, which doesn't use winnt32.exe parsing winnt.sif. In version 8 winnt.sif is simply copied, in all previous versions it's parsed by winnt32.exe.
The rest of your errors are because winnt32.exe didn't complete it's job creating ~BT and ~LS folders from your source.




Regards,
ilko


edit:
wimb, may be you should remove the check for winnt32.exe in source and check for some other file(s), since it's no longer used and there are people, which remove this functionality from their source.


Another idea is not to use tmpdrive and vdk anymore, either copy to a temporary folder or right to the USB destination, this will simplify the procedure and give x64 compatibility.

Just a quick remind to anyone with 64bits source and USB hard disk- rdummy.sys won't work on 64 bit windows. If there are requests for it I will compile it for x64 too.

I will change the program such that dosnet.inf file is used as a marker to indicate a valid xp source directory.
It is a very good idea to change that since winnt32.exe is no longer used.

At the moment I am working on integrating USB_MultiBoot.cmd in usb_prep8.cmd.
In the new concept I removed already the use of a Virtual tmpdrive,
since it is no longer needed and gives problems with x64 versions of XP.

I am very interested in rdummy.sys version for 64 bit windows,
so that we can use this in the usb_prep8.cmd program and so improve the compatibility.
It would be very helpfull ilko_t if you can make that, because I have no experience about this subject.

@ilko_t
I thank you very much for your pioneering effort in this project and for your helpfull comments.

Cheers,

wimb

Why is the virtual drive even used and how is it being made? Funny enough, before seeing the tempdrive made, I made my own temp drive with the Windows source files in it so there wouldn't be spaces in the name. I think I saw that vdk.exe is being used, but why do this? I just put "subst O: C:\[xp files source]" for mine. Is it not different somehow?

In first scripts winnt32.exe was used, will it like subst? If yes- good idea, where were you a few months ago ? Why virtual drive was used- post #295 and the next few.
Anyway, winnt32.exe is no longer used and virtual drive will not be used in next versions.

About rdummy.sys- I hoped for a simple recompiling, but that was no go, the code must be rewritten/changed, so we need a proper programmer to do this. I have something in mind, but am not sure at all whether I can get him to do that.

There is a complete New Program Available: USB_MultiBoot2.cmd

I have integrated usb_prep8.cmd in USB_MultiBoot2.cmd Batch Program, which:
- Prepares MultiBoot USB-Drive provided with Windows XP Setup LocalSource
- Supports Booting: MS-DOS FREEDOS BartPE WinPE 2.0 and Setup Windows XP
- Supports GRUB4DOS with DOS FLOPPY IMAGES + Linux and Supports SYSLINUX Menu
- Supports Portable WinTools which run direct from GO-Menu button

Changes:
- Virtual Drive is no longer used
Instead in MultiBoot2 Folder a Temporary Folder usb_xpbt is made with all Custom made Files,
and where the XP BootFolder $WIN_NT$.~BT is created by parsing DOSNET.INF from XP Source.
The XP Source is copied direct to the $WIN_NT$.~LS Folder on the USB-Drive
and not to the Temporary Folder usb_xpbt.

- Install of BartPE by PeToUSB is supported, where a 2-byte hexedit of peldr enables its use
in combination with coexisting XP Setup files, thus resolving possible conflict.

- New is the USB Content Source Folder U_CONTENT which is copied to USB-Drive,
and which can contain additional DOS, Linux and Win PE 2.0 files,
but one might also select the complete Content of an earlier made USB-stick.
Or one may select an empty Content Folder containing a needed empty usbflash TAGFILE.
The Bootsector Files, Install of Syslinux, peldr and migrate.inf are Renewed to make the MultiBoot USB-Drive.

- New is also the wintools folder with Portable win32 WinTools.
Double-click on GO_WINTOOLS_MENU.BAT on USB-drive provides WinTools Menu from GO button.


Very interesting, Hopefully the next version of MultiBoot2.cmd will also support rdummy.sys necessary
for Install of 64-bit version of XP from USB-Harddisk

Regards,

wimb

***** NOTE *****
The Attachment contains USB_MultiBoot2_X.zip with limited U_CONTENT folder due to Upload limitation.
The Full Version USB_MultiBoot2.zip with U_CONTENT folder containing a lot of FREEWARE programs
is available at the CD Forum: http://www.911cd.net/forums//index.php?showtopic=20089

Download Direct USB_MultiBoot2.zip from CD Forum: USB_MultiBoot2.zip

Every time I try this I end up with an error before GUI setup:

Windows could not start because of the following file is missing or corrupt: <Windows root>\system32\ntoskrnl.exe

This happened with both of the latest versions. I was doing the fix at the end to make the USB drive U:, and the textmode setup would default to asking me if I was to install to the U: drive, and I would have to hit Esc and pick C. Is this normal? I tried without the fix at the end and it wouldn't ask anything at all before writing to the USB drive.

I don't understand why it always says that the file is missing. I'm using an nLited version of Windows Server 2003. I just want to install Windows. I tried using the BartPE and UBCD4Win environments and had no luck, the setup with winnt32.exe doesn't work and I don't know how I can just copy the files to the hard drive and somehow have it enter the textmode setup at boot.

How many partitions you have you your HD?
Where do you install windows to?
Do you have any hidden or non-standard ones?
Try in BIOS to play with LBA and LARGE mode if it is AUTO.
Do you have any other USB mass storage devices plugged, including card readers, smartfones etc.
What do you mean
?

Did you change winnt.sif AFTER usb_prep...? You have to remove the whole section [UNATTENDED], so the installer would prompt you where to install. Also make sure in [DATA] AutoPartition=0

First,big Thanx for your work with this tool "wimb"!
I'am not try your latest one:USB_MultiBoot2.cmd,but yesterday I try usb_prep8.cmd,the boot from usb is going well,but I have an error when windows prepare to install and the error message say something about:can't find corred cd drive,please quit with F 3.
I will try today with your latest version.

I tried it both with and without the Unattended sections and I always get the same error about that one file. I've made at least 10 builds with this utility alone and it hasn't worked.

Winnt32.exe doesn't work because of nLite, most likely. I've seen this happen before when I tried to run setup from inside Windows and it would skip to the last step and say it didn't work, and have me click Finish. Despite this not working, I have always been able to install Windows when I boot from the CD.

Like I said, I can copy the setup files to the HD in BartPE, but does that get me anywhere?

I try the latest version and now not have the error with cd drive and I can select the partition to install,but after that I have this error message:
The following value in the .SIF file used by setup is corrupted or missing:

Value 0 on the line in section (SourceDiskFiles)

Setup cannot continue,press F3.

I'am not change anything in sif file.What I'am doing wrong to have this error?

I prefer not to use nLite.

Try first USB_MultiBoot2.cmd on a clean xp sp2 source and if successfull
then use RyanVM Integrator for integrating post-sp2 Update Pack, IE7 and WM11 Addon
and after that use DPs_Base for integrating only DriverPack Mass Storage with text mode enabled.

XPSOURCE Space Saving Tips see: http://unattended.msfn.org/unattended.xp/view/web/57/
You can Safely Remove the XPSOURCE folders:
WIN9XMIG, WIN9XUPG and WINNTUPG - This will free up 37.6 MB
LANG - 99 MB and cmpnents - 22.6 MB ( Needed for MCE / Tablet PC only )

Regards,

wimb

Did you use the winnt.sif file supplied with usb_prep8.zip ?

It seems that Setup is looking for a CD which occurs when MsDosInitiated="0"
The Correct value for Setup from USB-Drive is MsDosInitiated="1"

wimb

I'am made a new usb image with new version USB_MultiBoot2 and still not worked correct.
I have the new Asus EeePC and I have only options to install xp from Usb disk.I'am try 2 times with clean XP SP2 disk and I'am not use any other tool like nlite!When I boot to Usb and begin to install work just fine,but when the labtop is restarted I have this error message in both try the same:

Windows could not start becouse the following file is missing or corrupt:
<Windows root>system32\hal.dll
Please re-install a copy of the above file


I just like to know why just the same xp disk work really fine when use it from CD boot,but fail in usb?
I can use another method explained from Lambo,but this is to slow and it take hours to install xp to this asus toy!
link:

I'am just fix this problem.Looks like that I'am read the instruction to fast and not see that I must in restart choose the gui mode.I'am boot again and choose usb disk and then the gui mode and the setup is continue!
Thanx guys for this great tool and your work!Now I have windows xp installed to Asus EeePC from usb.
Maybae you can do it just better if we can use nlited xp too.I'am not try nlited xp yet,but for shure we can save a lot of free space in this slim disk.Thanx again,you save me a lot of time and some money too!

You did not answer most of my question, neither confirmed if the other suggestions were tried...how can I help you?!

Sorry, but you should do 10 rebuilds with Nlite, not with usb_prep.., since the problem is in your source.
Deleting [unattended] is to prevent TXT Setup NOT asking you where to install windows to and has nothing to do with ntoskrnl.exe error.

Nlited sources do work, just you have to be careful and understand what you are removing.

@Rudi1- thanks for feedback

Well that makes no sense. If the nLite build is perfectly fine, then there's only the possibility of the problem being at this tool. If it can't accept an nLited source, nLite still doesn't have any reason to change for this. Clearly the install method is doing something that is very different from what would normally happen for the textmode and GUI steps.

Frankly I guess I ignored the top section where the bulk of your questions were, because I was in a rush and they don't seem to apply in my case. I have a single SATA drive with nothing on it. I couldn't get AHCI mode to work at all, so it's in IDE mode. Really nothing else I can configure there.

Install form a CD and install using winnt32.exe, which you reported not to work differ. Why- ask Microsoft.
Here, for now, we can use only the winnt32.exe approach, in earlier versions using directly winnt32.exe, in latest by "cloning" its functionality.
If you can help to develop a way to prepare stick like if using CD- please do so, you are more than welcome.
Why your nlited source didn't work with winnt32.exe you have to figure out. Start with a clean, not Nlited source, and find when functionality gets broken. This may take you more than 10 builds.

The questions I asked may not seem relevant for you, but to ask them I have reasons. If have to explain in details, this is going to take time, more than the one I could afford, so feel free to pay or not attention at all.
And I asked you to check LBA and LARGE hard disks mode, not AHCI or SATA. In some cases when hard drive is not seen properly this may lead to all kinds of "not making sense" results, as are their resolutions, this is not very likely, as I believe the problem is in your source, but would have taken you way less time to check settings, than the time I've spent to type all this.

Gee, this is just fanfriggingtastic. Screw you, and your little dog, too. People just don't seem to listen to reason....

Considering that I have a brain, I was able to figure it out and not come up with ridiculous non-sequiturs and imaginary reasoning.


Well... I ran this damn utility again, and as expected got the error about the file missing. I also ran UBCD4Win and looked at the HD, which revealed everything was just sitting there as it should. No missing files.

So what was that about using Winnt32.exe? First of all, I don't know why this crap wouldn't just emulate everything the normal textmode setup would do and then not require you to use the USB stick ever again. That is, when I use a CD I only boot from it once, this way here it just a hassle. Also using winnt32.exe here can't be the same way it is used when you run it from a Windows environment, and I would venture to guess you're just wrong in assuming winnt32 is being utilized.

So now what? Well since the garbage is copied to the HD, but it says files are missing, perhaps it refers to the wrong location. A quick guess was that, since this is but a simple script, it's assuming parameters are static when they are not, like how you can rename the Windows folder to whatever you want (which is what I had done). So I renamed "Win2003" to "Windows", and booya. It started up into the GUI setup after reimaging my damn USB stick once again. Further investigation reveals the culprit is the unchanging and assuming boot.ini file.


Also note: I completely left in the [Unattended] section and did NOT even reboot after creating the partition on my HD. By the way, you're welcome, for me sharing my genius with you here today.

Yep, you are genius indeed.
The typical error with XP ntldr/ntdetect.com when arcpath or windows folder path is messed is "hal.dll is missing or corrupted", exactly what was mentioned a few posts above.
Use ntldr/ntdetect.com from 2003, the same boot.ini, error becomes "ntoskrnl.exe is missing or..." . At least I am now aware, that the error message was changed in 2003. Thanks for the clue.

It seems you didn't pay attention to this question, which answer would have helped right away:


Not to mention how reading previous posts...


Or help files:

Help_USB_Multiboot2.txt

could save geniuses some time, unneeded arrogance and ignorance.

Thanks for your input anyway.

Boy I love vague questions. Yes, your ugly list of questions should have clearly directed me to say "it's installed to X folder", which I guess is now standard computer terminology for "where" with no other arguments attached. And yeah, attacking nLite constantly and whatever other nonsense options sure really did a lot here. Good try on the attempt to save some face, though.

But really, if you think it would be useful to scour through all you peoples' old post from months prior, I might as well not ask for any help and save the time by answering my own questions.

Plus I looked specifically for anything at all that could have been said about my issue, but I guess I can't expect a bunch of Internet Experts to compile a decent ReadMe when they come up with a final release.

EXCELLENT idea.

If, while doing the above, you could also avoid posting here offending people that have worked for months on this project would also be higly appreciated, and I guess ilko's poor innnocent pup would appreciate it too.

jaclaz

Yes !



@ilko_t
Thanks
For INSTALL of Windows 2003 I added the following lines to Help_USB_MultiBoot2.txt
in the Section C. for NON STANDARD INSTALLS

ERROR Message for WIN2003: <Windows root>\system32\ntoskrnl.exe file missing
indicates Install Foldername does not correspond to foldername in boot.ini
For Windows 2003 one has to adjust Manually boot.ini in Advance.
In makebt\boot.ini change foldername WINDOWS in WIN2003
or don't change boot.ini and use WINDOWS as Install Foldername instead of WIN2003

Regards,

wimb

This latest days I'am try several xp install from Usb with wimb program and I must say that work really fine with original windows xp sp 2 pro version and if you read carefully instruction how you must do it
I also try different usb keys and it work well,but I have a problem with nlited xp.The nlite xp is important for me,becouse I have the new Asus EeePc laptop which one have only 4 gb disk and full xp install take almost half of it.
I like to ask if is posible to made this program with support for installing all xp version(pro,home,nlite..)?
I know we can do it with boot usb and winnt.exe command,but this options take a lot of time to install.
Wimb and some other guys here is made almost impossible tool .With this tool we can install windows xp like in the CD way,but from usb key,so maybae is the way for this option...

Unfortunately there is not a "standard" nlited Xp, it all depends on what you remove with nlite.

You just remove one component too much and bam! it won't work anymore.

Just for the record, since you own a Eeepc, a "NICK" guy here:
http://www.digwin.com/view/installing-wind...usb-flash-drive
is distributing wimb's (and ilko_t's, and all the other people who contributed to this project) work without mentioning them (us) nor MSFN.

If you have some spare time, can you (and other members, of course) post there, expressing how this way of publishing and distributing other people's work without citing them is an unfair practice?

(I tried to, but my current setup is not working on that site)

jaclaz

@all
Please when using Nlite do NOT select Operating System Options-->Manual Install and Upgrade for removal. This reduces in my setup source only 11.12MB, AFAIK has no effect on targed size, but screws up DOSNET.INF in way, so we can't use it for purpose of this project.

Here is report, of differences found in DOSNET.INF before and after nlite, used only with the above mentioned option.

@Rudi1- make a new source and make sure you do not select that option, please report if that was the problem.

@wimb- I don't get the idea why this check for FAT. I used USB_MultiBoot2 on FAT32 virtual drive and couldn't go further. There is also possibility to install from NTFS formatted USB hard drive. makeBS.cmd is happy with NTFS, thanks to jaclaz, only boot file name length must be 5 symbols exactly.
Can you also have a look at the attached report.html, may be some check if the mention option in Nlite was used should be done, this will avoid a lot invalid preparations.

@jaclaz- with the Asus EeePC expect a lot of traffic

Regards,
ilko

In USB_MultiBoot2.cmd the check that the Target USB-Drive has FAT Format,
was needed in view of making MS-DOS and FREEDOS Bootsector Files for MultiBoot Support.
For Install of Windows XP from USB-Drive it is not necessary to limit to USB-Drives having FAT Format,
but Real USB-Drives formatted with PeToUSB have always a FAT Format,
and so it was thought also as userfriendly to present for Selecting as Target USB-Drive only Drives having FAT Format.

In the next version of the Program I can move the FAT Format check for the Target USB-Drive to a later stage,
where actually the Bootsector Files are made, so that the USB-drive in general can have any Format.

To the Help File I will Add the very interesting and worthfull frase:
- In Nlite do NOT select Operating System Options-->Manual Install and Upgrade for removal
I will also try to make some check on this in the USB_MultiBoot2.cmd Program.
Thanks ilko_t for your helpfull comment and advice on this.

Regards,

wimb

I'am made a new install with ilko_t suggestion and I keep Operating System Options-->Manual Install and Upgrade for removal in nlite and I can install windows xp pro sp2 without any problems in my EeePC.So far I'am try only pro version,so I don't know about home version,but looks like if we keep Manual Install and Upgrade for removal in nlite we can install nlited xp without problems.

I'm not commenting the tone Sancho used, but really, you can't expect people to go through all 24 pages of this thread. Not everybody got enough time nor will to "learn and learn and learn", some just want a solution to their problem. By the time few will have read this thread's first page, that alone contains 20 links, thousands will give credit to people like Nick, not for your (huge) work, research and achievements, but just for him putting it all in a few lines. Someone needs to summarize this thread, be it in the 1st post or by making a sticky. Please don't flame me, I think I'm just being realistic.

I took great pleasure in reading every last page of this thread to be honest. I know it's nice to have a little summary but...don't be ungracious for the immense work these people have done. They have provided a solution to what you are looking for. If you are too lazy to even read....think! These people were in your position and had to *write* a solution!!

[for the record - I submitted a post on 'Nick's site...and it got deleted. What a tool...sometimes militant solutions really do seem attractive...]

Hi guys... great work here!!!

I installed Windows XP Pro, both english and german version, several times on my ASUS Eee PC using usb_prep8.

Starting with a full source over with some nlite versions. I can confirm that you run only in problems, when you remove "Manual Install and Upgrade" under Operating System Options. Now my final nlite Version is only around 195MB and consumes around 650MB of space (excluded pagefile.sys and hiberfile.sys) after installing to the 4GB SSD of the Eee PC.

As i'm from Germany, i wanna write a guide in German language, how to use usb_prep8. Many people are not so familiar with english language and the result of translation tools are often poor.

But i don't wanna make the mistake not to mention the creator of it or MSFN. Just wanna ask about your opinion before i start with it.

Once again... great work.

@HKCU
Thanks for your interest in the program usb_prep8.cmd.
The USB_MultiBoot2.cmd is an improvement of usb_prep8.
SEE: Make MultiBoot USB-Drive for Install of Windows XP

You are welcome to write a guide in German language.

@all
It is easy to use the Program USB_MultiBoot2.cmd
Important Help Instructions are given when Running USB_MultiBoot2.cmd Program.
Read carefully the Help in the Intro for Making the MultiBoot USB-Drive
and at the Exit of the Program for Using the prepared USB-Drive.
These Instructions can also be read afterwards in the usb_prep.log File.

Further Info is given in the Help_USB_MultiBoot2.txt File located in the Help_Info Folder.
Besides there is an extensive Guide given at the CD Forum on how the MultiBoot USB-Drive is prepared.

All Important Links are given below ( visible in all my posts )

Regards,

wimb

On the contrary, I was commenting EXACTLY the tone he used and the extreme lack of any kind of gracefulness in the posts this guy made.

Noone is required to read the entire thread, everyone is kindly asked to act politely, and give the required info to:
1) make us be able to help him/her
2) possibly find and fix any flaw in the procedure (for everyone)

That's the whole idea of developing and beta testing something, interactive feedback until problem is solved.

I tried to somehow "code" this in "Common Sense Advice" given here:
http://www.boot-land.net/forums/index.php?act=boardrules

but more generally the idea is that you shouldn't ever post on a board something that, if said in "real life", as an example at the pub, would probably get you a punch in the mouth.

Now, is this way (posting on a single thread on a board) the ideal situation for developing an app and to support it?

Surely not, it would be much better if this thingy here had it's own Homepage, Online Help and dedicated Forum, but life is tough, you have to live with some shortcomings.

The good news is that, little by little and thanks to the efforts of wimb and the cooperation of several users, there is some help and usability and dependability has vastly increased.

Maybe it's time to ask some Admin/Mods of MSFN if they think this project be worth it's own sub-forum in "Member Contributed Projects", or in "Member Contributed Projects\Other Member Contributed Projects"; that would surely better the quality of the support.

jaclaz

UPDATE!

In one of the fastest and swiftest move I've ever witnessed ,

THERE IS NOW A NEW SUB-FORUM DEDICATED TO THIS PROJECT

Here:
http://www.msfn.org/board/Install-XP-USB-f157.html

Please, from now on, leave this thread, which will be maintained for historical reasons, alone and start posting on the new subforum.

jaclaz