Hi HJW and ilko_t,

Thanks for your Support and for starting this subject on Install of Vista from USB.

In fact when we use USB_MultiBoot2.cmd for making a MultiBoot USB-Drive,
the possibility to Install Vista from USB is already build in.
As ilko_t indicated we need to make a BootSector File which refers to BOOTMGR
and that is exactly what occurs with USB_MultiBoot2.cmd Program.

In my Guide for MultiBoot USB-stick with boot.ini Menu I indicated in Section B-6
the possibility to Boot from Windows PE 2.0 and than launch Vista Setup.
For this purpose I used an USB-Harddisk with 2 partitions,
where the first partition is 1900 MB and is SET Active and has FAT Format (using PeToUSB)

Add Windows PE 2.0 files to the U_CONTENT Source Folder and
Run USB_MultiBoot2.cmd to make the MultiBoot USB-Drive.
On the second partition we have enough room to place our Vista Setup Installation Files,
whereas an USB-stick will in general be too small.

Boot with Windows PE 2.0 from USB-Drive and in the cmd Window
Run Vista Setup from the second partition of the USB-Drive.
It is important to take care that at the Restart after Expanding Files,
Booting occurs from the Harddisk on which we Install Vista.

In a modern BIOS having a BIOS Bootmenu via Press F8 or Esc,
we can select to Boot only once from USB-Drive and default from Harddisk.
So than everything is easy.

For older BIOS it is needed to unplug the USB-Drive just at the Restart of Vista Install.
Earlier unplugging gives Install Error (cannot be solved).
To late unplugging USB-Drive gives Boot Failure, which is solved by
Restart of the computer enabling to Continue Vista Setup.
So in this case everything runs also fine for Install Vista from USB.

Booting with Windows PE 2.0 does not take extra time,
since it is otherwise included in Vista Setup.

Regards,

wimb

EDIT: I have tried also to Boot from BartPE and than Run Vista Setup,
however this FAILED. Vista says: Incompatible PE Version !!

This post has been edited by wimb: Jan 26 2008, 03:59 PM

Having just recently increased the length (for the record from 5' to 7 1/2' ) of the stick with which I won't touch Vista , I have no idea how a VISTA-made NTFS bootsector invokes bootmgr.

If anyone is kind enough to post or however send me a complete NTFS bootsector (8.192 bytes) made natively under VISTA, I will gladly try and find the differences as compared to a normal 2K/XP-made one and hopefully find a way to avoid the renaming of bootmgr.

jaclaz

Hi jaclaz,

Here is the NTFS BootSector invoking BOOTMGR made by Vista Format.

Hope you can find something interesting .....

Cheers,

wimb

This post has been edited by wimb: Jan 27 2008, 04:43 PM

At first sight, it seems NOT like a "good" done-from-scratch VISTA format, as the string "GRLDR" is present at offset 604.

On the other hand, it seems like the string "BOOTMGR" is at offset 514 (where in the "old" bootsector NTLDR was).

So, it seems that the previous:

has become:


i.e. it seems like the bootloader name is "terminated" by a
04 00 24 00 49 00 33 00 30 00 00 E0 00 00 00 30
sequence.

If this is confirmed, this would open the possibility of overcoming the current "5 letter length" limit for the name of the loader in the MakeBS batch.

The leading "05" in my example above comes from a NTFS sector done under Windows 2000, the new "07" is Vista, would it be possible that a XP NTFS bootsector has "06"?

Iìll need to do some tests...

jaclaz

This post has been edited by jaclaz: Jan 27 2008, 02:02 PM

Has Uploaded a better Vista NTFS Bootsector.

In my XP NTFS Bootsector I have also a leading "05" as in your example for Windows 2000.
Also the "terminated" sequence is the same in XP NTFS Bootsector.

It seems you are right in that the current "5 letter length" limit for the name of the loader
in the MakeBS batch can be overcome.

However, Comparing the Bootcode itself of XP NTFS and Vista NTFS BootSectors,
reveals that the code is completely different, so that simply replacing NTLDR by BOOTMGR will not work.

wimb

This post has been edited by wimb: Jan 28 2008, 04:45 AM

I would be interested in both XP and Vista running from one USBflashdrive.
Since I am going to buy a fast 8GB flashdrive soon I was hoping to put my DVDrw in trash and look forward to fast installations

If you want to only have 1 source of Vista on your USB the easiest way is to use the usb_multiboot.cmd program then copy over the [BOOT] [SOURCES] folders and BOOTMGR to the root of the USB.

Then edit the grub4dos menu.lst with:



this will work if you only need one version of Vista to be on the usb but more than one will not work.

So what if you needed more than one version, say x86 and x64 (well there's a guide out there to combine them into one install.wim) or what if you had one integrated with SP1 and one original?

Honestly I have tried many methods - adding new entry to BCD, hex editing, renaming install.wim (works but messy), renaming folders (works but also messy).

The best way that I have found so far is to create a Windows PE 2, boot into that with your usb and launch the setup program directly. This actually works very well because when Vista installs it requires to load Windows PE 2 anyways so you already crossed that bridge. What's best is the ability to have the source files in any folder you want just as long as you have install.wim in the same folder as setup.exe. Also WinPE2 can run both x86 and x64 files so u can launch both setups from one PE.

I hope this helps.

This post has been edited by andy_le2k: Apr 4 2008, 06:13 AM

Your solutions for Install of Vista from USB were already described here

http://www.msfn.org/board/vista-t114092.html&st=6
http://www.msfn.org/board/vista-t114092.html&st=7
http://www.msfn.org/board/Install-Vista-US...6.html&st=2

and GRUB4DOS menu.lst of USB_MultiBoot_8.zip provides already entries for Install of Vista from USB
using chainload of BOOTMGR

This post has been edited by wimb: Apr 7 2008, 02:39 AM

I tried to use SETUPLDRBIN and SETUPLDR.BIN instead of NTLDR in NTFS BootSector File using the same
byte sequence for terminating the bootloader name, but booting did not occur.

So it seems to me that we have to live with the 5-letter limit of bootloader name in NTFS BootSector File.
Actually renaming SETUPLDR.BIN as XPSTP is OK and is used now for all FileSystems by USB_MultiBoot_8.cmd
in order to avoid confusion.

wimb