I didn't get your question.
Txtsetup.sif is parsed by setupldr.bin. Hex edit all occurrences of txtsetup.sif to txtset01.sif and the latter is used. That's for setupldr.b01.
For setupldr.b02 use txtset02.sif.
Text mode Setup completes fine. GUI part to be tested. There is 1 occurrence in setupdd.sys, may have to be changed too.
PE and winnt32.exe have always been an option, mind you, for many users building PE is hard and unknown, they need just a single install off USB.

edit: GUI part worked just fine, no need to HEX edit setupdd.sys for txtsetup.sif.
Here is the step I forgot in the previous post:
In \$win_01$.~ls\I386\ren_fold.cmd change



to



In \$win_01$.~ls\I386\undoren.cmd change



to



Do the same for both files in $WIN_02$.~LS and use $WIN_02$.~*** and txtset02.***

This post has been edited by ilko_t: Mar 28 2008, 12:23 AM

Thanks very much for your hard work ilko_t!! Very much appreciated it and I'm glad you got it working.

(Un)fortunately I have to go out with the misses now but would much rather stay in all night and get this to work for me too.

I'll give this a shot when I get home and hopefully I can share some of your success.

Thanks again.

After all I wasn't too far off the road.




Very good!



Yes, but since andy_le2k already has/wants to have a BartPE.....

But still noone has been documenting the minimal PE files needed to run successfully WINN32....

jaclaz

Congratulations cdob and ilko_t with Multiple XP Install from USB

All Information has been added to New Release of USB_MultiBoot7.zip

This post has been edited by wimb: Mar 28 2008, 03:05 AM

Very good!

Just think how much money people will save by avoiding to buy a second USB stick!

Another small victory against the ever increasing entropy.


jaclaz

Am I to understand that I can have in install for XP Pro and install for XP x64 on one stick, and choose which one I want to install?

Not yet, x64 is not fully working, but ilko_t is working on it:
http://www.msfn.org/board/XP-x64-Install-t114022.html

Hopefully it will soon be possible.

jaclaz

You should be able to to that, however, using x64 some of the compressed files will get deleted during Text mode. You will need after install to copy AMD64 and I386 folders from your source to ~LS folder, skipping existing files until workaround is found. KillCopy or Volkov Commander are handy for this task.

Note when using usb_multibootX.cmd- bootsectors to be HEX edited setupldr.b01 for multiple OS install are in \btsec on stick, NOT SETUPLDR1.bs and SETUPLDR2.bs in root.

Credits should go to their place- cdob

This post has been edited by ilko_t: Mar 28 2008, 12:32 PM

Thanks, that's better solution. Hexediting idea is outdated from 2006.

Just wondering: there are hard links at NTFS (USB) media
A duplicate file can be replaced by hard link.
example: two times 500 mb installation files maybe require 600 mb space.

And there is Duplicate File Hard Linker (DFHL) http://www.jensscheffler.de/dfhl_en.html

Hey guys,

I was just wondering if you guys had that time and effort, can you please write a simple step by step guide to get this to work for idiots like me who still can't?!

I'm getting stuck on how to get the boot sectors to load properly. What do you do to get the setupldr1.bs and setupldr2.bs? - SOLVED - use MakeBS3.cmd from the USB_Multiboot package

Exactly which files need to be hexed and renamed? The ones from the root or the ones inside $WIN_01~.BT or both? - Still a bit unsure about this, apparently you need to hexed setupdd.sys but even with that hexed txtsetup still gives me an error saying it cant find source folders.

And finally what about the .LS folder where the actual source is.. can you just leave it as $WIN_01~.LS or does need to be $WIN_NT~.LS in order for setup to work?

Thanks again.

This post has been edited by andyle2k: Mar 28 2008, 05:29 PM

Did you mean here XPS01 instead of SETUPLDR1
Same for index 2


In setupdd.sys there is no $WIN_NT.~LS string
Did you mean :x00B:x00T instead of :x00L:x00S

Your detailed description of post #1 corresponds to what ilko_t and cdob have given,
but unfortunately I was not able in all cases (3 attempts) to reach the GUI Mode of Setup.

TXT Mode Setup was running well, but TXT mode could not continue after the first question.
Setup cannot Find Install Files - Setup Cannot Continue - Message Occurs. So NOT SOLVED for me

@ilko_t Would it bepossible that a modified NTDETECT.COM bring the solution?
What kind of USB-Drive and Format did you use ?
I have tried USB-Harddisk with NTFS and FAT Format, and USB-stick with NTFS Format

wimb

This post has been edited by wimb: Mar 29 2008, 11:34 AM

Wimb, here is setupdd.sys from Tiny Hexer:


Yep, must be XPS01 instead of SETUPLDR1 if using NTFS. If it's FAT16/32 then setupldr.bin names should be used.
May be it's a good idea in next release to use only XPSTP, no matter what FS, also to copy only bootsectors and setupldr.bin for the chosen options as we discussed. I.e. BartPE not selected- do not copy PELDR and bootsector for it, same for DOS/Syslinux etc.

I used FAT16 and usb_prepare8, normal ntdetect.com, no need to HEX edit it. Strings replacements with gsar as more convenient.


ilko

Hi ilko,

In my setupdd.sys there is no $WIN_NT.~LS string,
but in yours I can see there is one.

My Source is XP SP2 NLD file 03-08-2004

Mystery SOLVED, I changed Search Settings to Yours and Now I found the String.

Search with: Unicode (little endian) and Ignore case

Thanks a lot

This post has been edited by wimb: Mar 29 2008, 12:08 PM

Did you select unicode? Without that, Tiny Hexer won't find the string.

Mine is from XP Pro SP2 Eng, setupdd.sys version 5.1.2600.2180 from 03-08-2004.
What do you have at that offset?

This post has been edited by ilko_t: Mar 29 2008, 12:07 PM

Unicode made the difference, Thanks

Will try again now.

Thx guys,

Multiple XP Install from USB SOLVED for me by ilko_t with TinyHexer ScreenShot and andy_le2k and cdob
Install of XP from USB was now OK

My problem was that in TinyHexer I used wrong setting for search of $WIN_NT$.~LS string.
Now I know that I have to use Unicode (little endian) and Ignore case.

But it is much better to use GSAR for the search and replace, then there is no problem.

@andy_le2k Your GSAR Instruction is OK, no need to change

wimb

This post has been edited by wimb: Mar 30 2008, 08:58 AM

Good

I'm still puzzled about this unicode thingie, why only ~LS string
First time when thread was started I opened setupdd.sys in Tiny Hexer and searched for ~LS- not