Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

[SOLVED] Install Multiple XP/Vista/PE/2003 from USB


  • Please log in to reply
67 replies to this topic

#1
andy_le2k

andy_le2k

    Newbie

  • Member
  • 25 posts
  • Joined 03-January 04
This post has evolved quite a bit since I started out on my quest to boot from a single USB hard drive which will then be able to launch every single OS install as well as every diagnostic tool from it as well. So below I will list the methods I use to get my USB hard drive working, of course you don't have to follow this but it's here as a guide.

Thanks:

Without these guys this would not have been possible!

  • wimb
  • cdob
  • jaclaz
  • ilko_t

AIM:

To be able to install multiple OS installs from the single USB hard drive

Software needed:

wimb's usb_multiboot - check the stickies in this forum for the download details.

a hex editor

WAIK (if you want to have multiple Vista sources)

a DOS menu program or an autoplay creator (for multiple Vista)

OS/TOOLS Sources

Hardware:

USB Hard drive preferably > 20GB

Outline:

Use wimb's usb_multiboot to create XP sources as well as adding the boot sector onto the hard drive and load it with NTLDR.

NTLDR uses boot.ini which then launches grub4dos automatically

Reason for not using boot.ini is because grub4dos is superior in handling and loading bootloaders whereas boot.ini needs boot sectors which will cut out one extra step. Grub4dos has extra functionality which we can add to later such as emulating virtual hard disks and fdd's, it can load Vista's BOOTMGR directly and also its menu is also better to look at ;)

Reason why I personally did not load grub4dos's bootsector directly to the hard drive but went through the trouble of using NTLDR (boot.ini) then loading grub4dos is because I already have grub4dos installed on my other hard drive and grub4dos's bootsector looks for the file "grldr" automatically which is already present on my other hard drive so it might load my permanent hard drive instead of my USB. So I have renamed and hex edited the grldr on the USB drive to look for "brldr" and set boot.ini to load brldr instead. If you do not have this dillema, feel free to use grub4dos's boot sector installer if you wish to cut out the extra step of loading NTLDR then grub4dos.

Currently working on:

  • [SOLVED]Trying to get multiple versions of Windows 2003 to co-exist on the USB hard drive.


---------------
Multiple PE
---------------
This applies to anything that uses WINPE1 (Windows FLP install, BartPE, ERD Commander, etc)
As PE was initially intended to be run off a CD the original structure for them would be inside the [i386] folder.
If your PE came from a USB source it would be in the folder [minint].
It's not important which folder it is in because we will rename them once it is copied to the USB hard drive anyways. Make sure you copy winbom.ini to the USB root as well.

The convention you should stick to is:
[mini01]
[mini02]
[mini03]
[minixx]

So once we have the folders copied to our hard drive and renamed appropriately we will need to also copy the setupldr.bin file from the [minixx] folder to the root of the USB and rename them according to this convention:
peld1
peld2
peld3
peldx

Now you will need to change the first occurrence of txtsetup.sif in PELDx to notsetup.sif.

gsar -sBT:x00:x00:x00\:x00:x00:x00txtsetup -rBT:x00:x00:x00\:x00:x00:x00notsetup %USB%:\PELDx -b -o

Change all occurances of minint to minixx.

gsar -i -o -s\minint -r\minixx peldx

Notes:

WinFLP requires all additional folders on the CD to be on the USB root, such as the [Setup] which houses the flp.wim which setup requires. So as a rule of thumb: copy all folders from the source CD for WinFLP, ERD Commander and BartPE to the root of USB drive and rename the i386 folder to minixx.

WinFLP's setupldr.bin has a checksum protection which will error if you hex edit it, I suggest you use BartPE's one.

---------------
Multiple Vista
----------------
Ok this is not much of an automated process but it is somewhat more streamlined than my original concept.

Dump all your Vista sources onto the USB hard drive (11 gigs for me - x86 + x64 Vista + x86 + x64 Server 2008) - Best if they are in a separate folder... tree view for mine is below

USB
|
|----->BOOTMGR
|
|----->[Boot]
| |
| |--->Modified BCD store
|
|----->[SOURCES]
| |
| |--->x86.wim
|
|----->[Vista]
|
|----->[Vistax86]
| |
| |--->[SOURCES]
|
|
|----->[Vistax64]
| |
| |--->[SOURCES]
|
|
|----->[Serverx86]
| |
| |--->[SOURCES]
|
|
|----->[Serverx64]
|--->[SOURCES]


First thing is to copy the BOOTMGR file along with the [SOURCES] and [BOOT] folders from any Vista source to the root of the USB hard drive. You can delete the Install.wim from the [SOURCES] folder.

Now what you will need to do is create a new Windows PE 2.0 (x86) from WAIK - I won't go into details about that here but it's very simple. Reason we use the x86 version of WINPE2 is because the 32bit version of WINPE2 can launch the setup of both 64 and 32 versions (with some tweaking as discussed below).

Mount your WINPE2 image on a local hard drive folder with read/write and you will need to modify your WINPE2 with:

Create a text file in [mounted_wim_folder]\Windows\System32\ and name it: winpeshl.ini
Edit the winpeshl.ini with:
[LaunchApp]
   AppPath=%SYSTEMDRIVE%\menu.cmd
What the winpeshl.ini file will do is start up WINPE2 and run whatever your AppPath program is as a shell. So you can make a simple DOS batch menu for you to select whichever Vista/Server 2008 you want to install. What I did was made an autorun program using Autoplay Studio which will prompt me with 4 options and whatever I click on, it will launch a batch file which will run the setup for that OS. Two important things you need to keep in mind is:

1) You will need to find the USB hard drive before you can launch the setup. So you may want to add this line to your batch files:

FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\usb_tag_file SET USB=%%i:\

You can then launch the setup by adding this line to your batch file:

%USB%\Vista\Vistax86\sources\setup.exe

2) You cannot load a x64 setup from a x86 WINPE2, the workaround for this is to copy contents of the SOURCES folder (including Setup.exe but excluding boot.wim and install.wim) from the x86 version of the Vista source. **IMPORTANT** do not overwrite the install.wim in the destination folder or you will just be installing the x86 version!

Once you have modified the WINPE2, make sure you commit the changes. If you have more than one WINPE2 on your USB, you will then need to edit the bcd store inside the BOOT folder on the root of your USB using bcdedit.exe - if you don't have any other WINPE2, you can just copy the BOOT and SOURCES folders and the BOOTMGR file from any Vista source to the <ROOT> of the USB hard drive, then name your newly created WINPE2 as boot.wim and copy it over to the SOURCES folder and overwrite the original.

So now, from your USB's grub4dos menu, load the bootmgr on the root of your USB it will then load the bcd store. If you have more than one WINPE2 it will load the BOOTMGR menu, if not it will load into the WINPE2 that you have created. Once that WINPE2 loads, it should load your batch menu or VBS or if you really want to be fancy... an autoplay application.




------------------------
Multiple Windows 2003
------------------------

The process of getting multiple sources of Windows 2003 onto your USB hard drive is pretty much the same as making multiple sources of XP with a few more extra steps.

First, you will need these files:

Cracked setupldr.bin : http://www.msfn.org/...PLDR-1-.BIN.zip
ModifyPE : http://unattended.ms...al/MODIFYPE.EXE

Steps:

  • Copy and replace the cracked setupldr.bin to the i386 folder of your source before you use usb_multiboot.
  • Create the source using usb_multiboot, for this example we will assume the source folders are [$WIN_xx$.~LS] and [$WIN_xx$.~BT]
  • [left]Goto [$WIN_xx$.~BT] and you should find both setupdd.sys and setupdd.sy_ Delete setupdd.sy_ and apply the following to setupdd.sys
    modifype.exe setupdd.sys -c
  • [center]
    makecab setupdd.sys
  • I have not yet tested putting a checksum on setupldr.bin but I would assume this method will work as well. So if you don't want to download the cracked setupldr.bin you may wish to try the following but it may not work.


    [center]
    modifype.exe XATxx -c
    and
    modifype.exe XPSxx -c

    ----------------
    Multiple XP
    ----------------
    This has changed a lot since wimb updated the usb_multiboot to automatically do this, so basically, run the usb_multiboot program twice (or however many times you want) making sure you carefully select the settings again for each time you run it.

    Below are the original instructions for historic and nostalgic reasons.

    Thanks to everybody who made this possible for me - especially these superstars: jaclaz, ilko_t, cdob and wimb

    I just want to list the steps I took below, I can't promise that it will work for all of you but it worked for me.

    01 - Make XP1 Source using usb_multiboot.cmd

    02 - Rename $WIN_NT$.~BS and $WIN_NT$.~LS to $WIN_01$.~BS and $WIN_01$.~LS

    03 - Rename SETUPLDR.BIN to XPS01 and rename TXTSETUP.SIF to TXTSET01.SIF

    04 - Make XP2 Source using usb_multiboot.cmd

    05 - Rename $WIN_NT$.~BS and $WIN_NT$.~LS to $WIN_02$.~BS and $WIN_02$.~LS

    06 - Rename SETUPLDR.BIN to XPS02 and rename TXTSETUP.SIF to TXTSET02.SIF

    07 - HEX Edit XPS01 replace every reference of "$WIN_NT" to "$WIN_01"
    - HEX Edit XPS01 replace every reference of "txtsetup" to "txtset01"

    08 - HEX Edit XPS02 replace every reference of "$WIN_NT" to "$WIN_02"
    - HEX Edit XPS02 replace every reference of "txtsetup" to "txtset02"

    09 - EXPAND setupdd.sy_ to setupdd.sys located in your ~BS folders
    - For $WIN_01$.~BT\setupdd.sys run "GSAR -i -o -s$:x00W:x00I:x00N:x00_:x00N:x00T:x00$:x00.:x00~:x00L:x00S:x00 -r$:x00W:x00I:x00N:x00_:x000:x001:x00$:x00.:x00~:x00L:x00S:x00 setupdd.sys"
    - For $WIN_02$.~BT\setupdd.sys run "GSAR -i -o -s$:x00W:x00I:x00N:x00_:x00N:x00T:x00$:x00.:x00~:x00L:x00S:x00 -r$:x00W:x00I:x00N:x00_:x000:x002:x00$:x00.:x00~:x00L:x00S:x00 setupdd.sys"

    10 - MAKECAB setupdd.sys for each of the ~BS folders

    11 - Use MakeBS3.cmd (located in your usb_multiboot package under \makebt)
    "MakeBS3.cmd [USB_DRIVE_LETTER]:\XPS01" and
    "MakeBS3.cmd [USB_DRIVE_LETTER]:\XPS02"
    - This will make 2 boot sector files in your [USB_DRIVE_LETTER]:\btsec folder named
    XPS01.bs and XPS02.bs

    12 - EDIT boot.ini and add the lines "C:\btsec\XPS01.bs" and "C:\btsec\XPS02.bs"


    13 - In \$win_01$.~ls\I386\ren_fold.cmd change

    SET TAGFILE=\$WIN_NT$.~BT

    ren %USBDRIVE%\txtsetup.sif txtsetup.bak
    ren %USBDRIVE%\$WIN_NT$.~BT WIN_NT.BT
    ren %USBDRIVE%\$WIN_NT$.~LS WIN_NT.LS


    to

    SET TAGFILE=\$WIN_01$.~BT

    ren %USBDRIVE%\txtset01.sif txtset01.bak
    ren %USBDRIVE%\$WIN_01$.~BT WIN_01.BT
    ren %USBDRIVE%\$WIN_01$.~LS WIN_01.LS


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

    SET TAGFILE=\$WIN_NT$.~BT

    ren %USBDRIVE%\txtsetup.bak txtsetup.sif
    ren %USBDRIVE%\WIN_NT.BT $WIN_NT$.~BT
    ren %USBDRIVE%\WIN_NT.LS $WIN_NT$.~LS

    to

    SET TAGFILE=\$WIN_01$.~BT

    ren %USBDRIVE%\txtset01.bak txtset01.sif
    ren %USBDRIVE%\WIN_01.BT $WIN_01$.~BT
    ren %USBDRIVE%\WIN_01.LS $WIN_01$.~LS

    14 - Repeat the above for the batch files in \$win_02$.~ls\ making sure you replace 01 with 02

    0

    Edited by andy_le2k, 24 June 2008 - 04:58 PM.



    How to remove advertisement from MSFN

    #2
    jaclaz

    jaclaz

      The Finder

    • Developer
    • 14,392 posts
    • Joined 23-July 04
    • OS:none specified
    • Country: Country Flag
    I already replied you on the other thread:
    http://www.msfn.org/...ve-t114523.html
    there is NO need to DOUBLE POST.
    Read Rules:
    http://www.msfn.org/...ead-t18408.html

    2.a Use some common sense. Don't post your question under multiple topics. Think before posting and choose the right topic for you question or answer. When posting, have something to say, not just "My First post!" or "Cool site!!!" We sort of have the idea by now :-).


    (bolding is mine)

    I pointed you here to make you read what is already done, and to give you a starting point, I don't think anyone is going to do your homework, as said, start with the known-to-be-working method:
    http://www.msfn.org/...SB-t111406.html
    http://www.911cd.net...showtopic=20089
    (just one flavour of XP install), add a PE, when you have ONE install working, try with a second one.

    Always do one thing at the time, otherways it will be impossible to troubleshoot the problems.


    jaclaz

    Edited by jaclaz, 25 March 2008 - 09:37 AM.


    #3
    andy_le2k

    andy_le2k

      Newbie

    • Member
    • 25 posts
    • Joined 03-January 04
    Thanks again for the links.

    Been trying so hard to get this to work but no hope.

    First when I tried the usb_multiboot6 program it works perfectly when installing XP but the problem now is that I can only have 1 xp source. The program makes hard drive setup folders $WIN_NT$.~BT and $WIN_NT$.~LS. This makes it very difficult to add a second source as they would need to replace the default folders. I also tried renaming these folders as well as the txtsetup.sif and bootldr files and replace them with another source but that didn't work either.

    Grub4dos:
    I kept getting the txtsetup.sif corrupted, status 14 error whenever it loads a hex edited \PRO1\setupldr.bin

    Heaps of thanks to jaclaz for letting me learn so much and actually getting at least one xp to setup from usb hard drive. I'm very sorry for double posting just thought this project of mine should be in this forum rather than the other.

    #4
    wimb

    wimb

      Senior Member

    • Developer
    • 679 posts
    • Joined 21-March 07

    Vista source folders can't be renamed or moved to subfolders and as such only one Vista edition can be present on the hard drive.

    Install of Vista from Folder on NTFS USB-stick was realised as described here
    http://www.msfn.org/...14092.html&st=6

    Boot in this case via boot.ini Menu > GRUB4DOS Menu > Select Windows PE 2.0
    Then the Windows Boot Manager Menu Appears and one can launch Windows PE 2.0
    In Win PE 2.0 Command Window > Select USB-Drive and Folder with Vista Setup > Run Vista Setup


    It will be possible to combine XP , Vista x86 and Vista x64 for Install from USB.
    Different versions of XP cannot be combined on one stick,
    but it is very convenient to use different sticks for this purpose.

    #5
    jaclaz

    jaclaz

      The Finder

    • Developer
    • 14,392 posts
    • Joined 23-July 04
    • OS:none specified
    • Country: Country Flag
    Generally speaking, two different installs of XP use, say, 95% of the same files.

    Now, if you use the normal USBmultiboot setup, and image/backup the resulting install directories, then re-use USBmultiboot for the different install, you can make a compare/diff between the two copies.

    Nothing prevents you from having two directories anywhere on the stick, like:
    \setup01
    and
    \setup02

    containing the ONLY the files that change between the two versions of setup.

    Then you boot from the PE on the stick (or also from a DOS flavour) and simply copy the files in one of the two setup directories overwriting those already in $WIN_NT$.~BT or $WIN_NT$.~LS, writing a simple batch for doing the above should be trivial.

    Sure, you cannot choose at boot whether you instal setup01 or setup02, but making the switch should not be difficult, it's just a reboot and a few xcopy/robocopy commands away. ;)

    Strings $WIN_NT$.~BT and $WIN_NT$.~LS are hardcoded in SETUPLDR.BIN, though I don't remember anyone previously experimenting with this, it should be perfectly possible to hexedit SETUPLDR.BIN jsut like we do for \I386 or \minint. :unsure:

    jaclaz

    Edited by jaclaz, 26 March 2008 - 11:19 AM.


    #6
    wimb

    wimb

      Senior Member

    • Developer
    • 679 posts
    • Joined 21-March 07

    Strings $WIN_NT$.~BT and $WIN_NT$.~LS are hardcoded in SETUPLDR.BIN, though I don't remember anyone previously experimenting with this, it should be perfectly possible to hexedit SETUPLDR.BIN jsut like we do for \I386 or \minint. :unsure:

    Interesting ideas :)

    String $WIN_NT$.~BT occurs twice in SETUPLDR.BIN but $WIN_NT$.~LS is not found there.
    TXTSETUP.SIF does NOT contain string $WIN_NT$.~LS and SetupSourcePath = "\"
    It seems that hexediting will not bring the desired solution .... ;)

    May be a second stick with other XP version is more convenient ;)

    #7
    ilko_t

    ilko_t

      MSFN Addict

    • Super Moderator
    • 1,722 posts
    • Joined 06-December 06
    • OS:none specified
    • Country: Country Flag
    There is an old MS article for NT, which gives some clues, I have no idea if this could be used for 2000/XP/2003.
    I did play with these settings in the past without much luck. Didn't test for this particular scenario.
    http://support.microsoft.com/kb/150497

    txtsetup.sif:

    [SetupData]
    ;
    ; SetupSourceDevice is optional and specifies the nt device path
    ; of the device to be used as the setup source. This overrides
    ; the CD-ROM or winnt local source.
    ;
    ;***remove the semicolon from the following line and make sure it
    ;***references the physical location of the system files.
    ;***In the example this will be partition1 since C: is the first
    ;*** partition on the disk.
    ;
    SetupSourceDevice = \device\harddisk0\partition1
    ;
    ; SetupSourcePath specifies the path relative to the source device
    ; where the setup source tree is to be found.
    ; All media descriptors are relative to this.
    ;
    ;*** Change the "SetupSourcePath" line to the path of your system
    ;*** repair files.
    ;*** In the example, I would change the variable to equal \repair.
    ;
    SetupSourcePath=\repair
    MajorVersion = 4
    MinorVersion = 0
    DefaultPath=\WINNT
    OsLoadOptions = "/nodebug"


    Install Windows from USB, boot Linux, multiboot and a lot more with WinSetupFromUSB


    #8
    cdob

    cdob

      MSFN Expert

    • Member
    • PipPipPipPipPipPip
    • 1,000 posts
    • Joined 29-September 05
    First congratulations to new section at MSFN.

    If I recall correctly from 2006 http://www.msfn.org/...p...st&p=584906

    Txtsetup.sif [SetupData] SetupSourcePath is ignored at USB.

    Using a different directory set:
    change setupldr.bin and setupdd.sys.

    #9
    ilko_t

    ilko_t

      MSFN Addict

    • Super Moderator
    • 1,722 posts
    • Joined 06-December 06
    • OS:none specified
    • Country: Country Flag
    Thanks cdob, very useful info.

    Have you tested with this line included?

    SetupSourceDevice = \device\harddisk0\partition1

    From the above article

    ; SetupSourceDevice is optional and specifies the nt device path
    ; of the device to be used as the setup source. This overrides
    ; the CD-ROM or winnt local source.


    edit: Never mind, seems I did:

    http://www.msfn.org/...730#entry684730
    Memory is getting shorter and shorter, I should start again taking the medicine :lol:

    Edited by ilko_t, 26 March 2008 - 01:09 PM.

    Install Windows from USB, boot Linux, multiboot and a lot more with WinSetupFromUSB


    #10
    threeply

    threeply

      Newbie

    • Member
    • 10 posts
    • Joined 10-June 07

    Vista source folders can't be renamed or moved to subfolders and as such only one Vista edition can be present on the hard drive.

    Install of Vista from Folder on NTFS USB-stick was realised as described here
    http://www.msfn.org/...14092.html&st=6

    Boot in this case via boot.ini Menu > GRUB4DOS Menu > Select Windows PE 2.0
    Then the Windows Boot Manager Menu Appears and one can launch Windows PE 2.0
    In Win PE 2.0 Command Window > Select USB-Drive and Folder with Vista Setup > Run Vista Setup


    It will be possible to combine XP , Vista x86 and Vista x64 for Install from USB.
    Different versions of XP cannot be combined on one stick,
    but it is very convenient to use different sticks for this purpose.


    Unless the stick is multipartitioned then different versions can be combined but of course this is only theoretical.

    Automating the process is kinda of non-trivial, we need a utility something like vlite/nlite for multi-install so the images can be created and copied over to a stick.

    The requirement would go something like this:

    1) Select the Destination type (usb-hd/usb-stick)
    2) Select the source OS (multi-checkboxes)
    3) Determine if Destination space is sufficent
    4) Partition the Drive
    5) Copy over the Source Files
    6) Setup the boot menu and bcd store
    7) Give final directions on reboot

    #11
    andy_le2k

    andy_le2k

      Newbie

    • Member
    • 25 posts
    • Joined 03-January 04

    Then you boot from the PE on the stick (or also from a DOS flavour) and simply copy the files in one of the two setup directories overwriting those already in $WIN_NT$.~BT or $WIN_NT$.~LS, writing a simple batch for doing the above should be trivial.


    This is what I did, I kind of gave up on the idea of a smooth menu where you can install multiple flavours on the fly. But this method still does not work!

    What I did:

    I renamed the <$WIN_NT$.~BT> and <$WIN_NT$.~LS> folders as well as the txtsetup.sif and setupldr.bin on the root to <SETUP01-BT>, <SETUP-01-LS>, txtsetup01.sif and setup01ldr.bin.

    I then used multibootxp6.cmd to add the other xp setup to the hard drive.

    Everything seems fine but during the txtsetup phase it fails to format or gives an error about the txtsetup.sif file being missing or corrupted.

    May be a second stick with other XP version is more convenient


    The whole point of my project is to have ALL the OS that I frequently need to install on one usb hdd to make things more convenient.


    Thanks everybody so much for the replies and ideas this is very facinating as it is much as it is annoying ;)

    #12
    cdob

    cdob

      MSFN Expert

    • Member
    • PipPipPipPipPipPip
    • 1,000 posts
    • Joined 29-September 05

    but during the txtsetup phase it fails to format or gives an error about the txtsetup.sif file being missing or corrupted.

    Did you edited setupldr.bin? Change setupldr.bin, apply renamed names.
    And edit setupdd.sys.

    #13
    andy_le2k

    andy_le2k

      Newbie

    • Member
    • 25 posts
    • Joined 03-January 04

    but during the txtsetup phase it fails to format or gives an error about the txtsetup.sif file being missing or corrupted.

    Did you edited setupldr.bin? Change setupldr.bin, apply renamed names.
    And edit setupdd.sys.


    Yep, I went to great lengths to make sure everything is renamed, backed up then made another source, then to restore the previous source i renamed and backed up everything again!

    Every single file gets renamed/replaced but txtsetup will still give me errors. I will try to get screenshots of these errors and post them here.

    #14
    ilko_t

    ilko_t

      MSFN Addict

    • Super Moderator
    • 1,722 posts
    • Joined 06-December 06
    • OS:none specified
    • Country: Country Flag
    You are installing from USB hard disk, right?
    Did you select for disk type USB hard disk in USB_multibot6.cmd?

    Install Windows from USB, boot Linux, multiboot and a lot more with WinSetupFromUSB


    #15
    andyle2k

    andyle2k
    • Member
    • 4 posts
    • Joined 09-June 06

    You are installing from USB hard disk, right?
    Did you select for disk type USB hard disk in USB_multibot6.cmd?


    yep!

    #16
    jaclaz

    jaclaz

      The Finder

    • Developer
    • 14,392 posts
    • Joined 23-July 04
    • OS:none specified
    • Country: Country Flag

    This is what I did, I kind of gave up on the idea of a smooth menu where you can install multiple flavours on the fly. But this method still does not work!


    For the record, what I suggested lately was NOT to rename ANYTHING:

    Generally speaking, two different installs of XP use, say, 95% of the same files.

    Now, if you use the normal USBmultiboot setup, and image/backup the resulting install directories, then re-use USBmultiboot for the different install, you can make a compare/diff between the two copies.

    Nothing prevents you from having two directories anywhere on the stick, like:
    \setup01
    and
    \setup02

    containing the ONLY the files that change between the two versions of setup.

    Then you boot from the PE on the stick (or also from a DOS flavour) and simply copy the files in one of the two setup directories overwriting those already in $WIN_NT$.~BT or $WIN_NT$.~LS, writing a simple batch for doing the above should be trivial.


    Sure the above is not the "best" way, but "A bird in the hand is worth two in the bush" ;)

    Another possibility, that noone has fully explored AFAIK is method #2 in my post here:
    http://www.msfn.org/...t...8.html&st=6

    I am pretty sure that a very small PE build, probably in the 20 to 40 Mb range should be able to run correctly WINNT32, thus allowing a "real" Windows NT/2K/XP/2003 install from ANY source.

    jaclaz

    #17
    cdob

    cdob

      MSFN Expert

    • Member
    • PipPipPipPipPipPip
    • 1,000 posts
    • Joined 29-September 05

    Yep, I went to great lengths to make sure everything is renamed, backed up then made another source, then to restore the previous source i renamed and backed up everything again!

    Every single file gets renamed/replaced but txtsetup will still give me errors.

    I don't understand clearly: did you hexedited file setupldr.bin?

    I get: given a USB hard disk:

    File txtsetup.sif renamed to txtset01.sif
    Folder $WIN_NT$.~BT renamed to $WIN_01$.~BT

    setupldr.bin hexedited:
    txtsetup.sif changed to txtset01.sif
    $WIN_NT$.~BT changed to $WIN_01$.~BT

    Setupldr.bin does boot.
    Destination hard disk can be selected. Pressed F3 to cancel at this point.

    #18
    andyle2k

    andyle2k
    • Member
    • 4 posts
    • Joined 09-June 06
    Hex editing won't (or didn't) work because to I think hard drive installations look specifically for the $WIN_NT$.~BT and $WIN_NT$.~LS folders.

    What I did was rename those folders for each flavour of XP so if I wanted to change the flavour of XP I would of had to boot into PE or use another comp to rename the current $WIN_NT$.~BT and $WIN_NT$.~LS folders to something else then rename the desired XP source and boot folders into $WIN_NT$.~BT and $WIN_NT$.~LS. I went so far as to rename every single file from the root of the hard drive as well (setupldr.bin, txtsetup.sif, ntldr and so forth).

    So just to be completely clear:

    - I use multibootxp6.cmd program.
    - choose the first XP source
    - choose my usb hdd destination
    - copy the source and make the boot sectors.
    - test with the hard drive and setup will work no problems
    - then I would move everything on the hard drive to a different drive (backup)
    - use multibootxp6.cmd again.
    - choose the second XP source.
    - copy the source files and make the boot sectors.
    - test the bootable usb hard drive and setup will work again.
    - I rename or move everything on the usb hard drive to a sub folder i.e. [XP2]
    - I copy back the first XP source
    - Boot up from the hdd is fine
    - TXTSETUP stage is fine until it starts copying files or format stage which then errors, corrupted or missing files.

    #19
    ilko_t

    ilko_t

      MSFN Addict

    • Super Moderator
    • 1,722 posts
    • Joined 06-December 06
    • OS:none specified
    • Country: Country Flag
    Just a quick check list- to have lets say XP1 and XP2
    In root:
    \$win_01$.~bt
    \$win_01$.~ls

    \$win_02$.~bt
    \$win_02$.~ls
    ntdetect.com
    NTLDR
    txtset01.sif
    txtset02.sif


    setupldr.b01
    setupldr.b02
    Both HEX edited to $win_01$.~bt and $win_02$.~bt and txtsetup.sif to txtset01.sif and txtset02.sif

    SETUPLDR1.bs
    SETUPLDR2.bs
    Both HEX edited setupldr.bin to setupldr.b01 and setupldr.b02

    boot.ini
    [Boot Loader]
    Timeout=10
    Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
    [Operating Systems]
    C:\SETUPLDR1.bs="1. TXT Mode Setup Windows XP1, Do NOT unplug USB-Drive Until After First Logon"
    C:\SETUPLDR2.bs="1. TXT Mode Setup Windows XP2, Do NOT unplug USB-Drive Until After First Logon"
    multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="2. GUI Mode Setup Windows XP + First Start XP" /FASTDETECT

    In $win_01$.~bt setupdd.sy_ expanded and HEX edited $WIN_NT$ to $WIN_01$ and re-compressed ( necessary ? )
    In $win_02$.~bt setupdd.sy_ expanded and HEX edited $WIN_NT$ to $WIN_02$ and re-compressed ( necessary ? )

    Did you miss a step? Did I miss a step :unsure: ?

    ilko

    Install Windows from USB, boot Linux, multiboot and a lot more with WinSetupFromUSB


    #20
    andy_le2k

    andy_le2k

      Newbie

    • Member
    • 25 posts
    • Joined 03-January 04

    Both HEX edited to $win_01$.~bt and $win_02$.~bt and txtsetup.sif to txtset01.sif and txtset02.sif


    How would setup know to load txtset01.sif an txtset02.sif?

    Every other steps seems right and could possibly work. I think the best way is probably still to boot into PE and run winnt32!

    #21
    ilko_t

    ilko_t

      MSFN Addict

    • Super Moderator
    • 1,722 posts
    • Joined 06-December 06
    • OS:none specified
    • Country: Country Flag
    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

    ren %USBDRIVE%\txtsetup.sif txtsetup.bak
    ren %USBDRIVE%\$WIN_NT$.~BT WIN_NT.BT
    ren %USBDRIVE%\$WIN_NT$.~LS WIN_NT.LS

    to

    ren %USBDRIVE%\txtset01.sif txtset01.bak
    ren %USBDRIVE%\$WIN_01$.~BT WIN_01.BT
    ren %USBDRIVE%\$WIN_01$.~LS WIN_01.LS

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

    ren %USBDRIVE%\txtsetup.bak txtsetup.sif
    ren %USBDRIVE%\WIN_NT.BT $WIN_NT$.~BT
    ren %USBDRIVE%\WIN_NT.LS $WIN_NT$.~LS

    to

    ren %USBDRIVE%\txtset01.bak txtset01.sif
    ren %USBDRIVE%\WIN_01.BT $WIN_01$.~BT
    ren %USBDRIVE%\WIN_01.LS $WIN_01$.~LS

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

    Edited by ilko_t, 28 March 2008 - 12:23 AM.

    Install Windows from USB, boot Linux, multiboot and a lot more with WinSetupFromUSB


    #22
    andy_le2k

    andy_le2k

      Newbie

    • Member
    • 25 posts
    • Joined 03-January 04
    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.

    #23
    jaclaz

    jaclaz

      The Finder

    • Developer
    • 14,392 posts
    • Joined 23-July 04
    • OS:none specified
    • Country: Country Flag
    After all I wasn't too far off the road. ;)

    Strings $WIN_NT$.~BT and $WIN_NT$.~LS are hardcoded in SETUPLDR.BIN, though I don't remember anyone previously experimenting with this, it should be perfectly possible to hexedit SETUPLDR.BIN jsut like we do for \I386 or \minint.


    GUI part worked just fine, no need to HEX edit setupdd.sys for txtsetup.sif.


    Very good! :thumbup

    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.


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

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

    jaclaz

    #24
    wimb

    wimb

      Senior Member

    • Developer
    • 679 posts
    • Joined 21-March 07

    edit: GUI part worked just fine, no need to HEX edit setupdd.sys for txtsetup.sif.

    Congratulations cdob and ilko_t with Multiple XP Install from USB :thumbup

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

    Edited by wimb, 28 March 2008 - 03:05 AM.


    #25
    jaclaz

    jaclaz

      The Finder

    • Developer
    • 14,392 posts
    • Joined 23-July 04
    • OS:none specified
    • Country: Country Flag

    Different versions of XP cannot be combined on one stick,
    but it is very convenient to use different sticks for this purpose.

    :unsure:

    May be a second stick with other XP version is more convenient

    :blink:

    Congratulations cdob and ilko_t with Multiple XP Install from USB

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

    :whistle:


    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. :thumbup


    jaclaz


    Back to Install Windows from USB


    0 user(s) are reading this topic

    0 members, 0 guests, 0 anonymous users



    How to remove advertisement from MSFN