Step instructions for installing BootCamp manually - HELP.

[Spacedust]

Your steps there probably would be bad. Unless your windows machine had identical hardware to the MacPro. During installation Windows installs for specific hardware.

I think it's worth it to go BootCamp if you're not satisfied with your Fusion performance. I have Fusion and Parallels both. Fusion is the worst and Parallels isn't that much better. Fusion is part of a much larger suite that is just awesome for data-center level virtual desk-top computing so a lot of SSE / SE types like it a lot. I dunno Parallels's background history but on my machine it's more stable and faster. Still neither are really very good. Thus BC. BC runs faster (like normal windows) but booting and rebooting into different OS's without data sharing across storage devices is just lame for anything other than gaming. Parallels will supposedly mount and boot from a BC drive which almost makes the setup bearable from the Apple side. Maybe Mac Drive or something like that would work the same from the Windoze side too - I dunno, I haven't gotten that far yet.

EDIT: Yup, it works!

.

How many cores can you see ?

 

[Tesselator]

How many cores can you see ?

You can see it in the screen shot.

Core 1
Core 2
Core 3
Core 4

 

[gugucom]

Now with two SSDs in an OS X boot RAID0. I would definitely recommend to do the AHCI driver first and then do a RAID array. I have done it that way.

All 8 cores are running under Vista64.

 

[Tesselator]

All 8 cores are running under Vista64.

Yeah, but that's not Parallels right? I get all 8 cores in BC of course.

 

[gugucom]

I never bought Parallels. How much is it?

 

[Tesselator]

I never bought Parallels. How much is it?

It says here http://www.parallels.com/ that it's $175.00 but I got mine at a show for about $50 if I remember right.

 

[Tesselator]

OK, BootCamp 3.0 drivers are out and hitting the torrents. I thought I would try to install them as the blurb is that they're better for 64-bit OS's and I'm running Vista Ultimate 64.

So I burn the ISO, insert the DVD in Bootcamp Windows Vista, and asks to run, I allow it, and it says:

"Boot Camp x64 is unsupported on this computer model"


Grrr, What gives? And more importantly how to cheat? Or do I even want these drivers installed?

Thanks all!

 

[gugucom]

You will find that they are SL compatible only. At least that is where they came from.

 

[weckart]

I had the same problems installing Windows 7 on my Macbook Pro. The default setup.exe will not work in x64, you have to drill down in the drivers into the Apple folder, then the x64 folder and run setup64.exe (or whatever it is called, can't remember offhand) from there. Everything should install from there. Depending upon the age of your machine, you should pick the right driver pack. I have a Santa Rosa model and Boot Camp drivers 2.1 worked best for me. The beta BC 3.0 drivers would not install fully.

 

[Tesselator]

You will find that they are SL compatible only. At least that is where they came from.

What do you mean SL only? I thought these drivers were for Mac Hardware under the Windows OS. What could SL possibly have to do with it at all?

In BootCamp I assume Windows as no idea at all about what OS is installed for Mac - if any. I've even heard of people removing or formatting their Mac OS drive completely and just using the thing as PC.

 

[nanofrog]

What do you mean SL only? I thought these drivers were for Mac Hardware under the Windows OS. What could SL possibly have to do with it at all?

In BootCamp I assume Windows as no idea at all about what OS is installed for Mac - if any. I've even heard of people removing or formatting their Mac OS drive completely and just using the thing as PC.

Perhaps it's not the fact it's from SL, but due to the EFI32 version of firmware rather than EFI64 on the later machines?

I'm wondering if Apple has blown BC for older systems (perhaps inadvertantly, but I'd think they'd have sorted this by now).

 

[Tesselator]

Perhaps it's not the fact it's from SL, but due to the EFI32 version of firmware rather than EFI64 on the later machines?

I'm wondering if Apple has blown BC for older systems (perhaps inadvertantly, but I'd think they'd have sorted this by now).

You might be right on with this. I went into the DVD and installed a few things by hand anyway.

64-Bit NVidia Drivers,
RealTek Drivers,
x64/AppleKeyboard
x64/AppleODD
IntelEthernet 64-bit
And chipset drives in 64-bit too even though it said this in the readme:

************************************************************
* Product: Intel(R) Chipset Device Software
* Release: Production Version
* Version: 9.1.0.1007
* Target Chipset#: 5520/5500/X58
* Date: August 19 2008
************************************************************

...
...
...


************************************************************
* 3. CONTENTS OF THE DISTRIBUTION PACKAGE
************************************************************
The Intel(R) Chipset Device Software package contains the
following items:

File(s)
-------
INFINST_AUTOL.EXE -or- INFINST_AUTOL.ZIP
README.TXT, RELEASE_xxx.HTM

*** NOTE:

Only the files that reference the currently
detected devices are copied to the system.​

************************************************************
​

So that's interesting. Only support for Chipsets 5520, 5500 and X58? That's the 2008, the 2009 and iMac? Not sure about the iMacs but the 2006 MacPro is 5000X. Hehehe I installed it anyway and there were like 4 or 5 files that were installed anew. All the others reported "not required".

My windows Vista64 Ultimate is now much faster booting and network I/O has seemingly improved. The Graphics driver supplied is slower: Speed = 4.1 instead of 4.4 in the Windows Experience registry, but I don't notice any difference so far. However my Windoze now has printed on the bottom right of the screen:

Windows Vista (TM)
Build 6002
This copy of Windows is not genuine​

And I have to manually set the wallpaper after every boot if I don't like 100% solid black.

Which is probably not related to anything I installed from the bootcamp drivers. But yeah, this IMO shows that 2006 owners have been kicked out of the car. They didn't even slow down or pull over to the curb!

 

[gugucom]

There is a new driver in the package that is supposed to work with SL only. On installation Windows will be able to read and write to OS X.

The chipsets mentioned in the driver are all Nehalem only. That could mean that Apple wants to cut off everything except the Nehalems from Bootcamp 3.0.

 

[Tesselator]

There is a new driver in the package that is supposed to work with SL only. On installation Windows will be able to read and write to OS X.

But neither OS X nor SL are running AT ALL when BC Windows is... So that's like impossible.

The chipsets mentioned in the driver are all Nehalem only. That could mean that Apple wants to cut off everything except the Nehalems from Bootcamp 3.0.

OK. I was thinking one of those might be for the 2008 machines. Bummer that even they're getting the boot... Or, umm NOT getting the boot as is the case.

 

[gugucom]

But neither OS X nor SL are running AT ALL when BC Windows is... So that's like impossible.

Not impossible. Same thing as an NTFS driver for OS X. That one enables you to write to Windows drives. Now turn the thing around and make the Windows people write to OS X drives. The OS needn't be booted to do that.

 

[nanofrog]

You might be right on with this. I went into the DVD and installed a few things by hand anyway.

64-Bit NVidia Drivers,
RealTek Drivers,
x64/AppleKeyboard
x64/AppleODD
IntelEthernet 64-bit
And chipset drives in 64-bit too even though it said this in the readme:

************************************************************
* Product: Intel(R) Chipset Device Software
* Release: Production Version
* Version: 9.1.0.1007
* Target Chipset#: 5520/5500/X58
* Date: August 19 2008
************************************************************

...
...
...


************************************************************
* 3. CONTENTS OF THE DISTRIBUTION PACKAGE
************************************************************
The Intel(R) Chipset Device Software package contains the
following items:

File(s)
-------
INFINST_AUTOL.EXE -or- INFINST_AUTOL.ZIP
README.TXT, RELEASE_xxx.HTM

*** NOTE:

Only the files that reference the currently
detected devices are copied to the system.​

************************************************************
​

So that's interesting. Only support for Chipsets 5520, 5500 and X58? That's the 2008, the 2009 and iMac? Not sure about the iMacs but the 2006 MacPro is 5000X. Hehehe I installed it anyway and there were like 4 or 5 files that were installed anew. All the others reported "not required".

My windows Vista64 Ultimate is now much faster booting and network I/O has seemingly improved. The Graphics driver supplied is slower: Speed = 4.1 instead of 4.4 in the Windows Experience registry, but I don't notice any difference so far. However my Windoze now has printed on the bottom right of the screen:

Windows Vista (TM)
Build 6002
This copy of Windows is not genuine​

And I have to manually set the wallpaper after every boot if I don't like 100% solid black.

Which is probably not related to anything I installed from the bootcamp drivers. But yeah, this IMO shows that 2006 owners have been kicked out of the car. They didn't even slow down or pull over to the curb!

No sign posts or announcements either.

At least you've got it working, but it's only meant for the '09 models, as all the chipset's listed are exclusive to Nehalem. No support for the earlier models at this point.

Not impossible. Same thing as an NTFS driver for OS X. That one enables you to write to Windows drives. Now turn the thing around and make the Windows people write to OS X drives. The OS needn't be booted to do that.

That should be an adjustment in the GPT (from my way of thinking), and might help later down the road (type of situation you're encountering now). But that assumes a few things, such as the GPT methodologies between both OS's are the same, rather than some sort of patch/add-in to Windows to enable this.

 

[Tesselator]

Not impossible. Same thing as an NTFS driver for OS X. That one enables you to write to Windows drives. Now turn the thing around and make the Windows people write to OS X drives. The OS needn't be booted to do that.

Still impossible. NTFS and HFS/HFS+ are filing systems they run within the OS that is running at the time. Either Apple added HFS/HFS+ support for windows or they didn't. If they did then everyone will be able to use it. If they didn't then no one will. It won't matter what OS is installed on some drive that may or may not be connected to the computer. So it still doesn't make any sense.