Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Bootcamp doesn't work on new Mac Pro 2009
- Thread starter seisend
- Start date
- Sort by reaction score
..Fortunately, everything I've come across (originally Vista 64) has worked in Win7. MS is depending on that one I suspect, as it's built from Vista's code, and really what Vista should have been when it was released (ugh.. pre SP1 was hell).
Never underestimate the complexity of Windows in an EFI/GPT environment. Things that are so easy in BIOS/MBR become devilishly difficult.
Yep, and the Apple update never works in stand alone. You allways need a leopard disk first. Major PITA!
guess what, I got my Mac Pro since Monday. So I think there will be the newest version on it. gonna install the file :
Bootcamp/drivers/apple/bootcamp64
Bootcamp/drivers/apple/bootcamp64
I should've know. I've helped a few others with this (separate disk, single drive operation), and didn't think it would be an issue, as the OS X was separate, keeping the GPT & MBR interaction out of it. I would imagine they didn't check the compatibility (one person IIRC, with Win7), and got lucky. What MS is hoping for; Vista 64 drivers being fully functional in Win7, and skip the nightmare Vista 64 was upon release. The other members used Vista 64.
That would suck.
Bootcamp DVD doesn't work. There are compatibly errors when I start the install file from the DVD. Otherwise I could start the 2.0 installation.
It says Bootcamp installation finished. Gonna restart now
It says Bootcamp installation finished. Gonna restart now
If you do not partition the drive and go MBR partition table you still have the EFI issues to deal with. Like the 32-bit EFI machines not being able to boot anytime upgrade DVDs. They simply lock down on the install because the EFI bootloader cannot handle multiple images.
Very Strange: It has always an error with a code when I want to install from the DVD. Press Install and then the error is here.
Installing Bootcamp64 2.0 from gugucom worked.
Installing Bootcamp64 2.1 from gugucom failed.
Reason: "A further version of this product already installed)
?!
Well - Can't I delete the 2.0 version and install the 2.1 version instead ?
Installing Bootcamp64 2.0 from gugucom worked.
Installing Bootcamp64 2.1 from gugucom failed.
Reason: "A further version of this product already installed)
?!
Well - Can't I delete the 2.0 version and install the 2.1 version instead ?
When it is up again, go to the device manager and check if all the devices are up and running. Don't proceed with a crippled system but go back to the driver installation until everything is functional.
Ok. 2.1 is installed . It's 8.53 MB large.
volume and eject button doesn't work. Are all drivers now installed ? No graphics drivers to install?
volume and eject button doesn't work. Are all drivers now installed ? No graphics drivers to install?
I'd think gugucom could help far more with the eject button and volume controls than I. I do seem to recall some posts/threads on this before, but can't recall enough details to offer any real direction. So I'm chickening out, and passing the buck.
Might save you a disaster that way. But to check the other drivers, first open up the Device Manager, and check for the yellow triangle with an exclaimation mark (no drivers) for every bit of hardware listed.
Assuming there's not, you've got drivers for the entire system. You can run the update tool to see what Win7 can find on it's own, and then check those items it didn't find manually for newer versions. This take time, but it's free. There are some utilities that check for you, but it costs ~$30USD. But this one has a free trial (Driver Detective), if you wish. I've not tried it with Win7, but it does work with Vista.
Personally, I'd play it safe and go at it manually, but it's up to you.
That's one way to help.
seisend, you'd also want to expand everything before making the screen shot (gives the actuall hardware used, not just device type/description). That way everything's exposed.
That's one way to help.
seisend, you'd also want to expand everything before making the screen shot (gives the actuall hardware used, not just device type/description). That way everything's exposed.
expansion is sufficient to the items that show unusual signs and ATA which we are going to tweak. If necessary we need to go into system devices and see if everything is there. but we will deferr this at the moment.
You will probably still find some Apple devices not working. You will then go back manually to the Apple folder, compatibility mod the individual drivers and install them. Thats just for the principle.
Bloody marvelous mate!!
Note the standard IDE controller on your two ATA devices! The upper one is for the four internal four HDD SATA ports. The lower one is for the two ODD-SATA ports. Your chipset uses different devices there.
EDit: You have a 5520 chipset with ICH10 controller. Make a note of that!
You can now update Windows and either make a backup with Winclone or set a system breakpoint.
Note the standard IDE controller on your two ATA devices! The upper one is for the four internal four HDD SATA ports. The lower one is for the two ODD-SATA ports. Your chipset uses different devices there.
EDit: You have a 5520 chipset with ICH10 controller. Make a note of that!
You can now update Windows and either make a backup with Winclone or set a system breakpoint.
I'd mentioned it to make sure the chipset (System Devices) area's are good. I had an issue with that on mine, and it didn't show up until it was expanded.
uploaded on Windows 7 ;-)
what do you think ?
edit: I dont like driver detective .
Graphicscard driver seems strange:
Got a GT 120 and there is nvidia geforce 9500 gt listed
what do you think ?
edit: I dont like driver detective
.Graphicscard driver seems strange:
Got a GT 120 and there is nvidia geforce 9500 gt listed
I wouldn't trust it for Win7 right now at all. It did help me locate some firmware before, so it's not totally useless.edit: I dont like driver detective
These should be the right ones, but take a good look first (new as they're dated 21.07.2009). I presumed you'd want them in Deutsch.
Getting the best Nvidia driver isn't so inportant because you are using an INtel Chipset not NVIDIA. It can be fixed at a later time.
Now to Windows update.
Backing up with Winclone or setting Breakpoint
Editing registry
Make note of drive internal code number
Applying Johnsocks patch
Loading AHCI for the first time
Installing IMSM
Now to Windows update.
Backing up with Winclone or setting Breakpoint
Editing registry
Make note of drive internal code number
Applying Johnsocks patch
Loading AHCI for the first time
Installing IMSM