Comments on: FreeBSD & WINDOWS VISTA http://www.clearchain.com/blog/posts/freebsd-windows-vista -= Daily Happenings =- Wed, 08 Feb 2012 11:15:17 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: DougRH http://www.clearchain.com/blog/posts/freebsd-windows-vista#comment-1056 DougRH Thu, 23 Dec 2010 15:38:16 +0000 http://www.clearchain.com/blog/?p=44#comment-1056 *The previous submission got SNAFU: The Implemented Solution: My BIOS has a Boot menu that doesn't care what Vista does or doesn't do to boot to any OS. Though it is a little inconvenient in that it defaults to (Re)Boot to Vista and not the other OS that I am on now and I can't change this. But this is the lesser of the two evils and I can live with this minor inconvenience in this environment but that ensures that I can still get up and running even if Vista (32) can't boot to anything anymore. I'm not 'gun shy' about using multiple boot software. I've used them successfully for many years. But this way I've completely bypassed any such problems that will most likely and inevitably happen again at some point in time. *These ARE still computers after all! But hey: It used to take rebooting several times a day to get a full days work out of them. Happily not anymore. At least PC/Macs etc have finally got to the point where they have enough Hardware capacity that we can actually do something useful such as utilizing great GUI interface and multi-task effectively with them now. But I'm STILL glad the MicroSoft doesn't make the OS that runs my vehicles! , , , )8 >( YET )< 8( 'nuf said! *The previous submission got SNAFU:

The Implemented Solution:
My BIOS has a Boot menu that doesn’t care what Vista does or doesn’t do to boot to any OS. Though it is a little inconvenient in that it defaults to (Re)Boot to Vista and not the other OS that I am on now and I can’t change this.

But this is the lesser of the two evils and I can live with this minor inconvenience in this environment but that ensures that I can still get up and running even if Vista (32) can’t boot to anything anymore.

I’m not ‘gun shy’ about using multiple boot software. I’ve used them successfully for many years.

But this way I’ve completely bypassed any such problems that will most likely and inevitably happen again at some point in time. *These ARE still computers after all!

But hey:
It used to take rebooting several times a day to get a full days work out of them. Happily not anymore.

At least PC/Macs etc have finally got to the point where they have enough Hardware capacity that we can actually do something useful such as utilizing great GUI interface and multi-task effectively with them now.

But I’m STILL glad the MicroSoft doesn’t make the OS that runs my vehicles! , , , )8 >( YET )< 8(

'nuf said!

]]> By: DougRH http://www.clearchain.com/blog/posts/freebsd-windows-vista#comment-1055 DougRH Thu, 23 Dec 2010 15:25:46 +0000 http://www.clearchain.com/blog/?p=44#comment-1055 Hi, You may note my series of inquiries here on multiple OS booting problems, specifically losing the capacity to boot to Vista 32 I was never able to 'resurrect' Vista to boot directly to it and ended up reinstalling it. I was going to turn all booting controls over to Vista. BUT: Hey, My HDD are mirrored arrays so why can't I boot of at least one of them that I have confirmation of access and functionality from another OS. So, I know the hardware is OK, but when the boot software is all messed up, it renders it a moot point. Comes back to the same thing that it has been for over 30 years with personal computers: regardless of what hardware 'flavor' or configuration that they are: BackUps! BakUps! BackUps! This INCLUDES the BOOT software in some form or other: be it an OffLine mirrored HDD or an emergency repair disk. Before I gave Vista total software control over all of the different OS's booting from it, I stopped and scratched that itch niggling away at me from my subconscious mind: So if I do give Vista the power to control all boot up OS, then if it crashes again, I've lost the capacity to boot to any of them! NOT good ! )( YET )< 8( 'nuf said! Hi,
You may note my series of inquiries here on multiple OS booting problems, specifically losing the capacity to boot to Vista 32
I was never able to ‘resurrect’ Vista to boot directly to it and ended up reinstalling it.
I was going to turn all booting controls over to Vista. BUT:
Hey, My HDD are mirrored arrays so why can’t I boot of at least one of them that I have confirmation of access and functionality from another OS.
So, I know the hardware is OK, but when the boot software is all messed up, it renders it a moot point.

Comes back to the same thing that it has been for over 30 years with personal computers: regardless of what hardware ‘flavor’ or configuration that they are:
BackUps! BakUps! BackUps!

This INCLUDES the BOOT software in some form or other: be it an OffLine mirrored HDD or an emergency repair disk.

Before I gave Vista total software control over all of the different OS’s booting from it, I stopped and scratched that itch niggling away at me from my subconscious mind:

So if I do give Vista the power to control all boot up OS, then if it crashes again, I’ve lost the capacity to boot to any of them! NOT good ! )( YET )< 8(

'nuf said!

]]> By: wacky mixed up boot loader: Multi-booting Vista, Ubuntu and PCBSD http://www.clearchain.com/blog/posts/freebsd-windows-vista#comment-742 wacky mixed up boot loader: Multi-booting Vista, Ubuntu and PCBSD Sun, 12 Dec 2010 13:04:01 +0000 http://www.clearchain.com/blog/?p=44#comment-742 [...] only brought up Ubuntu and Windows. Next I followed the instructions at the end of this article http://www.clearchain.com/blog/posts...-windows-vista (don't ask why), specifically, entering this in the Command Prompt: BCDEDIT /set {bootmgr} device [...] [...] only brought up Ubuntu and Windows. Next I followed the instructions at the end of this article http://www.clearchain.com/blog/posts…-windows-vista (don't ask why), specifically, entering this in the Command Prompt: BCDEDIT /set {bootmgr} device [...]

]]> By: catfish http://www.clearchain.com/blog/posts/freebsd-windows-vista#comment-264 catfish Thu, 19 Nov 2009 01:47:52 +0000 http://www.clearchain.com/blog/?p=44#comment-264 Thanks, I was able to get my system going. In my case, I had installed FreeBSD and then installed Vista. I used easybcd to get back to FreeBSD. For a lark I installed boot0mgr. Attempting to reboot into Vista brought me here via google. Anyway, for whatever reason, I too got errors when trying to run the BCDEDIT commands. I suspect it is because of EasyBCD. I found out the default BCD store is C:\boot\bcd. I added this to the above commands and successfully repaired Vista. i.e.: BCDEDIT /store C:\boot\BCD /set {bootmgr} device boot etc. Thanks for the handy guide! Thanks, I was able to get my system going.

In my case, I had installed FreeBSD and then installed Vista. I used easybcd to get back to FreeBSD. For a lark I installed boot0mgr. Attempting to reboot into Vista brought me here via google.

Anyway, for whatever reason, I too got errors when trying to run the BCDEDIT commands. I suspect it is because of EasyBCD. I found out the default BCD store is C:\boot\bcd. I added this to the above commands and successfully repaired Vista.

i.e.:
BCDEDIT /store C:\boot\BCD /set {bootmgr} device boot

etc.

Thanks for the handy guide!

]]> By: Benjamin Close http://www.clearchain.com/blog/posts/freebsd-windows-vista#comment-91 Benjamin Close Sun, 22 Mar 2009 12:21:43 +0000 http://www.clearchain.com/blog/?p=44#comment-91 Hi DougRH, Sorry I'm out of ideas, if you do manage to work it out, please let me know as I'm interested in a working solution. Hi DougRH,
Sorry I’m out of ideas, if you do manage to work it out, please let me know as I’m interested in a working solution.

]]> By: DougRH http://www.clearchain.com/blog/posts/freebsd-windows-vista#comment-90 DougRH Sat, 21 Mar 2009 21:11:06 +0000 http://www.clearchain.com/blog/?p=44#comment-90 My above response got butchered and most of it didn't post so here goes another try: I have tried pretty well everything that you suggested Benjamin without success before I read your reply. Except for these: Inputting the 3 BSD commands below in a DOS window with administrative privileges within Windows results in the first command being accepted OK, but I get an error message for the second and third ones and it doesn't accept them. BCDEDIT /set {bootmgr} device boot ----> OK BCDEDIT /set {default} device boot ----> Error BCDEDIT /set {default} osdevice boot --> Error Thanks again, DougRH My above response got butchered and most of it didn’t post so here goes another try:

I have tried pretty well everything that you suggested Benjamin without success before I read your reply.

Except for these: Inputting the 3 BSD commands below in a DOS window with administrative privileges within Windows results in the first command being accepted OK, but I get an error message for the second and third ones and it doesn’t accept them.

BCDEDIT /set {bootmgr} device boot —-> OK
BCDEDIT /set {default} device boot —-> Error
BCDEDIT /set {default} osdevice boot –> Error

Thanks again,
DougRH

]]> By: DougRH http://www.clearchain.com/blog/posts/freebsd-windows-vista#comment-89 DougRH Sat, 21 Mar 2009 21:02:06 +0000 http://www.clearchain.com/blog/?p=44#comment-89 Hi Benjamin et all, Sorry I didn't respond sooner, but I couldn't get onto this site for quite a while for unknown reasons ) OK BCDEDIT /set {default} device boot ----> Error BCDEDIT /set {default} osdevice boot --> Error Thanks for everyone's suggestions (< 8) Regards, DougRH Hi Benjamin et all,
Sorry I didn’t respond sooner, but I couldn’t get onto this site for quite a while for unknown reasons ) OK
BCDEDIT /set {default} device boot —-> Error
BCDEDIT /set {default} osdevice boot –> Error

Thanks for everyone’s suggestions (< 8)

Regards,
DougRH

]]> By: Benjamin Close http://www.clearchain.com/blog/posts/freebsd-windows-vista#comment-87 Benjamin Close Thu, 12 Mar 2009 22:00:26 +0000 http://www.clearchain.com/blog/?p=44#comment-87 By not having the Vista HDD's plugged in whilst installing XP, XP cannont enumerate those drives at install time - despite the fact you have the drivers loaded. Though Admittedly I'm guessing here. http://discussions.hardwarecentral.com/showthread.php?t=167275 seems to indicate that ntldr & ntdetect.com play a role in things not working. Have you tried changing the boot order in bios? It's possible this will reorder your drives allowing XP to boot. By not having the Vista HDD’s plugged in whilst installing XP, XP cannont enumerate those drives at install time – despite the fact you have the drivers loaded. Though Admittedly I’m guessing here.
http://discussions.hardwarecentral.com/showthread.php?t=167275 seems to indicate that ntldr & ntdetect.com play a role in things not working. Have you tried changing the boot order in bios? It’s possible this will reorder your drives allowing XP to boot.

]]> By: DougRH http://www.clearchain.com/blog/posts/freebsd-windows-vista#comment-86 DougRH Thu, 12 Mar 2009 18:00:46 +0000 http://www.clearchain.com/blog/?p=44#comment-86 Hi Benjamin, I am using the BCDedit.exe and the other utilities that I mentioned for editing & managing the (Vista) boot process on the Vista HDDs as when I try to do it on the XP drives, I am unable to edit with the Vista Boot manager/Utilities/files etc. I have the drivers for both cards loaded when I install both operating system, FYI: I know it is risky but out of desperation I have tried leaving the PCIe SATA RAID card in while installing XP, but don't have the HDDs pluged into it. Once I am in XP I then I plug the SATA HDDs into the PCIe card then plug the power connector into the SATA HDDs. (Hot PnP) I can then reboot into XP, but then I can't get into Vista )< 8) When I load the drivers for the PCIe during the XP install, I utilize the XP *.Inf file and it recognizes it just fine. When I load both of the drivers during teh Vista install, the most recent one is Windows 2003, which is working just fine for the PCIe card. The PCIe card is a HighPoint Rocket RAID 2300. THe PCI card is a Silicon Image Sil 0680R ATA-133 Medley RAID Controller. Thus both RAID cards are recognized and work just fine once I am into both XP & Vista. I have what you suggested covered and implemented but alas it doesn't work. Thanks anyway though (< 8) DougRH Hi Benjamin,

I am using the BCDedit.exe and the other utilities that I mentioned for editing & managing the (Vista) boot process on the Vista HDDs as when I try to do it on the XP drives, I am unable to edit with the Vista Boot manager/Utilities/files etc.

I have the drivers for both cards loaded when I install both operating system,

FYI: I know it is risky but out of desperation I have tried leaving the PCIe SATA RAID card in while installing XP, but don’t have the HDDs pluged into it. Once I am in XP I then I plug the SATA HDDs into the PCIe card then plug the power connector into the SATA HDDs. (Hot PnP) I can then reboot into XP, but then I can’t get into Vista )< 8)

When I load the drivers for the PCIe during the XP install, I utilize the XP *.Inf file and it recognizes it just fine.
When I load both of the drivers during teh Vista install, the most recent one is Windows 2003, which is working just fine for the PCIe card.

The PCIe card is a HighPoint Rocket RAID 2300.
THe PCI card is a Silicon Image Sil 0680R ATA-133 Medley RAID Controller.

Thus both RAID cards are recognized and work just fine once I am into both XP & Vista.

I have what you suggested covered and implemented but alas it doesn’t work.

Thanks anyway though (< 8)
DougRH

]]> By: Benjamin Close http://www.clearchain.com/blog/posts/freebsd-windows-vista#comment-84 Benjamin Close Thu, 12 Mar 2009 12:59:27 +0000 http://www.clearchain.com/blog/?p=44#comment-84 Since the pcie card is always found first you must put the boot loader on that disk. I think the problem may be related to how windows detects disks. Chances are your XP install is on your PCIHDD drive that XP considers to be C: however vista believes the PCIEXHDD drive is C:. I'd say that the the problem may be resolved by making sure that XP has drivers for the PCIEX card at installation time. This way XP will probe the drives in order and consider it's PCIHDD to be D: not C:. This hopefully will allow it to resolve it's drives correctly at boot. Good Luck! Since the pcie card is always found first you must put the boot loader on that disk. I think the problem may be related to how windows detects disks. Chances are your XP install is on your PCIHDD drive that XP considers to be C: however vista believes the PCIEXHDD drive is C:.

I’d say that the the problem may be resolved by making sure that XP has drivers for the PCIEX card at installation time. This way XP will probe the drives in order and consider it’s PCIHDD to be D: not C:. This hopefully will allow it to resolve it’s drives correctly at boot.

Good Luck!

]]>