VistaBootPro and x64 - multiboot BCD

[- Bobb -]

I had " previous version" , and "Windows" (X86) for boot options.
After I installed x64 I had :
1."Previous version" (legacy boot)
2."Windows" (which was x64)
3."Windows" (which was x86)
I used VistaBootPro to identify in better. I called them

1. XP and X64 (Boot.ini)
2. Vista x64
3. Vista x86

THEN, I wanted to change the ORDER on the screen to be:

XP
Vista x86
Vista x64

I could NOT change the order because VistaBootPro would only do so if a
letter assigned to boot. Xp and x86 were Ok - they had a drive letter ,
but x64 had a PATH like boot.ini \dev.. \.... I checked in the
leftmost tab and could see the path , but I didn't know - from ITS
view - what letter is VistaBootPro talking about - the letter from xp
disk mgmt view ? SO I had to leave it alone. So for others who
multiboot, by default it is
XP
Vista x64 and
Vista x86

Bobb

 

[Colin Barnhorst]

Don't try to change any drive letters that way. You can't change system
drive letters anyway. You are trying to view the system as a whole but each
OS has its own scheme independently of the others. They may line up the way
you want depending how you install each edition of Vista but it will likely
drive you nuts if you try to sort it out from your perspective. Just go by
the volume names and let the respective operating systems handle lettering.

 

[Charlie Russel - MVP]

In addition, VistaBootPro has been superceded on my machines by easyBCD.
More options, and it works with later builds.

 

[Colin Barnhorst]

I'll have to check that one out. For 5456 I had to copy bcdedit.exe out of
the System32 folder and replace the file in VBP with it. Then it worked
fine.

 

[John Barnes]

Thanks for the heads-up Charlie.

In addition, VistaBootPro has been superceded on my machines by easyBCD.
More options, and it works with later builds.

 

[- Bobb -]

Guys,
I wasn't trying to change anything but the order. Let me rephrase it:
Why did Xp and Vista x86 have drive letters assigned and Vista x64 did not -
it had just the path ?

Wait a second - it may have been my oversight - I formatted it from Vista
x86 - MAYBE I didn't assign that partition a letter in XP's drive view !!
And I was runnning VBP from XP !

I'm in x86 now ( sending lots of feedback reports) but when I'm done I'll
reboot and view disk mgr in XP and update here - for others info.

Bobb

 

[- Bobb -]

Thanks Charlie, I'll check it out.

In addition, VistaBootPro has been superceded on my machines by easyBCD.
More options, and it works with later builds.

 

[- Bobb -]

That's what it was - Doh !
View from XP shows no drive letter assigned - so I gave it one !

 

[- Bobb -]

Uninstalled VBP , installed EasyBCD and ( now that I have a drive letter
assigned to x64 drive) it looks good.

Thanks guys.

 

[Charlie Russel - MVP]

Looks like a falling out between the person who wrote VBP originally, and
the folks he was working with. So he went off on his own and wrote a new
version. It's better, IMHO.

 

[Colin Barnhorst]

Yes. The drivers option looks very interesting.

Looks like a falling out between the person who wrote VBP originally, and
the folks he was working with. So he went off on his own and wrote a new
version. It's better, IMHO.

 

[Charlie Russel - MVP]

Use with caution - I've seen reports of drivers loaded that way that then
blue screened. OTOH, I know Barb is using it to get her Wireless card
working, since the driver isn't signed.

 

[Barb Bowman]

yup. no problems so far.

OTOH, I know Barb is using it to get her Wireless card
working, since the driver isn't signed.

--

Barb Bowman
MS Windows-MVP
Expert Zone & Vista Community Columnist
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/