Jump to content

USB multiboot Windows 7 x86 and Windows 7 x64


zetan

Recommended Posts

Hi to all,

I try to put the Win7_x86 and Win7_x64 installer on the same usb key. My main problem is that they both use 'bootmgr'. For Grub4dos to differentiate, I placed the two installers in separate folders. Now my problem is that I don't know what to write in menu.lst. Let say I've put the Win7_x68 installer in a folder named W786. Installation starts fine but real soon it hangs and I am told a particular file in /boot/the_name_of_the_file does not exist. It's normal because now the file is in /W786/boot/the_name_of_the_file. So is there a way to force, by using Grub4dos, a new 'root folder' for the installation. If so, waht should be put in menu.lst?

I came across this post by Wimb:

There is no need to make multiple partitions on your USB-stick.

Vista Setup Source can be located in a folder on USB-stick so that it does not interfere with other Setup Sources like folders with Vista x64 or Windows 7 Setup Source.

Booting in 40 sec with pe21.iso loaded by GRUB4DOS from HD into RAMDISK X:

allows then to Launch Vista or Windows 7 Setup.exe from folder on USB-stick.

http://www.boot-land.net/forums/index.php?showtopic=5306

That's what I'm looking for but I don't understand the third sentence: "Booting in 40 sec with pe21.iso loaded by GRUB4DOS from HD into RAMDISK X:".

Last thing, the link for the topic 5306 is broken. Maybe my answer is in this topic. Is there a way to retrieve the info. TOPIC FIXED. Maybe server was down...

Thanks for any help,

Zetan

Edited by zetan
Link to comment
Share on other sites


That's what I'm looking for but I don't understand the third sentence: "Booting in 40 sec with pe21.iso loaded by GRUB4DOS from HD into RAMDISK X:".

You miss some history. ;).

Basically the "Install XP from USB" that started it all:

http://www.msfn.org/board/install-xp-usb-f157.html

and that was, as the name implies, initially aimed at XP only, was more or less originated by this:

http://www.msfn.org/board/installing-unatt...ive-t81788.html

http://www.msfn.org/board/installing-unatt...788-page-6.html

To this you add that there are at least 4 possible ways to install XP:

1) from a booted 16-bit environment through WINNT.EXE

2) from a booted 32-bit environment through WINNT32.EXE

3) from a \I386 or \minint folder by invoking SETUPLDR.BIN (which is what the normal install CD does)

4) from an "expanded" pre-install bootfolder $WIN_NT$.~BT like in the flyakite multiboot DVD tutorial

to which you can add:

5) from an .iso using Windows Server 2003 Sp1 or greater SETUPLDR.BIN and RAMDISK.SY_ a method that needing a HUGE amount of RAM for a RAMDISK, requires most probably at least 1Gb of Ram installed

Of the 5 "hinted" methods, #1 was already documented/possible (with a few limitations) #2 was as well known/reknown, and all efforts went in #3 and #4, here:

http://www.msfn.org/board/boot-install-usb-key-t61384.html

The #5 was set aside, and it has been found a solution for it only very recently, thanks to cdob:

http://www.msfn.org/board/install-xp-lite-...pid-876839.html

Once found a possible solution for XP, which actually resulted in something somewhat midway between #3 and #4, wimb "went back" to #2 (which, though reknown, was not easily replicable by people not familiar with BartPE or Winbuilder - please read familiar with PE 1.x) and provided an easy way (using the LiveXP project of Winbuilder) to implement it.

Later the problem of Vista (and Windows 7 which is very similar in this respect to Vista) was put on the table.

After finding a solution conceptually similar to the already seen #3/#4 above, something correspondent to #2 above was devised: boot a PE (2.x or 3.x this time) and from it install Vista/7.

The given thread:

http://www.boot-land.net/forums/index.php?showtopic=5306

Explains in detail how to use a PE 2.x to achieve that.

You need to follow the given links and get familiar with the WAIK and Winbuilder to be able to create either a PE 2.x:

http://www.boot-land.net/forums/index.php?showtopic=7053

or a VistaPE:

http://www.boot-land.net/forums/index.php?showforum=51

or a PE 3.x:

http://www.boot-land.net/forums/index.php?showforum=91

Explanation of numbers:

Microsoft released initially

WinPE versions 1.2 (XP based)

then WinPE 1.5 and 1.6 (XP or Server 2003 based)

since originally the use of WinPE was reserved to an "elite", Bart Lagerwej developed PEbuilder, an app to create a PE from XP or Server 2003 sources.

Later Nuno Brito wrote batcher openbuilder Winbuilder a more "generic" engine capable to replicate the needed functions, and a number of projects based on XP and Server 2003 files were developed.

Everything built taking as Source XP or 2003 files is "generally speaking" a PE 1.x.

Together with Vista, Microsoft released a ne version of WinPE, PE 2.x ??, a Pre-installation Environment similar to the above but based on Vista/Server 2008 files.

Projects were made for winbuilder to replicate this environment.

Everything built taking Vista or Server 2008 files is "generally speaking" a PE 2.x.

With the advent of Windows 7, Microsoft released a new version of WinPE, PE 3.x ??, a Pre-installation Environment based on Windows 7 files.

Projects were made for Winbuilder to make use of the latter.

Everything built taking Windows 7 files is "generally speaking" a PE 3.x.

You will need some time to get familiar with the building of a PE, being it a 1.x, a 2.x or a 3.x.

jaclaz

Edited by jaclaz
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...