Sidebar Sidebar
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

nanofrog said:
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. :p


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. ;)
Click to expand...


thank you for the link ! Didn't know its that simple. I had some trouble on my MacBook Pro just installing official nVidia drivers. I needed to install them from laptopvideo2go.com manually.

@ installing driver
 

Attachments

  • Capture.JPG
    Capture.JPG
    116.4 KB · Views: 85
gugucom said:
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
Click to expand...

I want no backup for now.

what about editing registry and making a note of drive internal code number? I guess the other points are in some other threads'?
 
seisend said:
I want no backup for now.

what about editing registry and making a note of drive internal code number? I guess the other points are in some other threads'?
Click to expand...

The minimum you need is to set a system restore point or I gurantee you, you will regret it. Do you know how to do that?
 
gugucom said:
The minimum you need is to set a system restore point or I gurantee you, you will regret it. Do you know how to do that?
Click to expand...

Well I know how to backup. But at the momentan can't say what a system restore point is. it's now 3.30 in the morning in switzerland.... ughhh ;-)

I have all my programms on my discs. If something would hapen to my OS, I just reinstall it and if I wouldn't now how to do, I just will follow this thread again.
 
It is dead simple. In German it is called Wiederherstellungspunkt. It is in the maintenance program folder. Wartungsprogramme. But I agree, if you are not doing anything tonight you can do it first thing before you touch it again.
 
gugucom said:
It is dead simple. In German it is called Wiederherstellungspunkt. It is in the maintenance program folder. Wartungsprogramme. But I agree, if you are not doing anything tonight you can do it first thing before you touch it again.
Click to expand...

Okey thank you.

Thank you bove again : gugucom and nanofrog. You were a big help for me today. So I can go now to sleep with good feelings :) I'm gonna be back tomorrow.
 
gugucom said:
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.
Click to expand...

How does one know that all the Apple supplied drivers have installed ok?

Note: the Windows 7 ISO may contain sufficient drivers to at least give
the appearance of a fully functioning system. If an Apple supplied driver
fails to install it may not, therefore, be obvious that that has happened.
 
Infrared said:
How does one know that all the Apple supplied drivers have installed ok?

Note: the Windows 7 ISO may contain sufficient drivers to at least give
the appearance of a fully functioning system. If an Apple supplied driver
fails to install it may not, therefore, be obvious that that has happened.
Click to expand...

This is very true. But in my experience I have never had a system that ran all devices in device manager and missed some invisible system drivers. The exception could be SATA devices needing AHCI or RAID mode.
 
gugucom said:
This is very true. But in my experience I have never had a system that ran all devices in device manager and missed some invisible system drivers. The exception could be SATA devices needing AHCI or RAID mode.
Click to expand...

What I had in mind was a scenario like the one where you end up with
the standard dual PCI-IDE (or whatever it's called) driver. There are no
warning symbols, everything seems to work, and yet the system is not
as fast as it should be.

Now that one's easy. I'd spot that a mile away. Ditto for the standard
VGA graphics adapter driver. But suppose there's something else, a bit
less obvious, and with a performance impact.

The trouble with the Boot Camp driver installer is that it's just a dumb
wrapper. It won't necessarilly pause and give you an error message if
something fails to install.
 
You can't be too paranoid about Windows drivers. Best is allways to check everything manually. On Mac Pros its fairly easy. The MBPs are a bitch sometimes with their partitioned drives and their Nvidia chipset. I still havn't figured out how to set AHCI driver to my uMBP.
 
hey I'm back, guess I've to get the AHCI drivers working
Are those the final steps for me? (tutorial by gugucom)

When you are done and have installed all the updates you need to activate the AHCI drivers. They will not be running at that stage. Copy the instructions from Ludachris at http://www.insanelymac.com/forum/ind...dpost&p=939694 . Download the patch from Johnsock. The next step is editing the registry as directed by Ludachris. Next go to disk utility in OS X and make a list of the identifiers of your installed partitions. There is an info button which tells you the internal name of each partition. Make a paper record of the partiton name and that code. You will need this later when you have no access to disk utility. Finally here make a backup with Winclone or at least set a restore point for Windows to get back to that stage if you screw up the next step.

The next step is executing Johnsocks patch program. Pay particular attention to patch the right partition/disk. For this you will need the codes that you have noted. The program tries to find your Windows disk but you have to make sure it finds the right one. It often suggests a wrong disk. When you are done with patching your MBR you shut down Windows and restart it. Then you bring up the Windows device manager. Go to ATA devices and click properties and update drivers. Disregard all automatic searching and force the system to load the AHCI driver from your USB stick, CD or floppy. For non Nehalem Mac Pros the right controller is ESB2 for Nehalem I believe it is ICH10. If the system tells you the driver is wrong disregard that and force the driver to load. Then shut down Windows and restart. If you have done the patch right and selected the right controller for your chipset Windows should now use basic AHCI drivers. If you got it wrong windows will malfunction on load. You can use special load options to go back to the last known good configuration which you hopefully established by setting the restore point in the last paragraph or you can restore Windows by Winclone. Start all over with this paragraph until you got it right.
 
gugucom said:
Yep, that should work. Have you made a system restore point? Btw, I have repaired the link which was down.
Click to expand...

Yes I think it's done. I am now able to set a restore for yesterday and so on. That should be fine now. So I am gonna follow your tutorial .
 
seisend said:
is the patch from johnsock the AHCI modification file ?
Click to expand...

Well I can't download this file :

"Sorry, but you do not have permission to use this feature. If you are not logged in, you may do so using the form below if available." - I am logged in.

Do you mean the files from Post #4 ?
 
seisend said:
is the patch from johnsock the AHCI modification file ?
Click to expand...

The script modifies the master boot record to allow Windows to use AHCI instead of the legacy driver.

Ludachris says in his tutorial that it is only required for XP, but I found I had Windows Vista also crashed on me unless I used this script.

There may be different results depending of your choice of partition table. I was using GUID and in Ludachris example he was using MBR table.

I believe from my own results that the script works on MBR and GUID tables. So my recommendation is to use it. But do not forget to edit the registry before.
 
gugucom said:
You can't be too paranoid about Windows drivers. Best is allways to check everything manually.
Click to expand...

Ok. Here's one for you (a little test):

driver.png

Is that the best driver or not? Note: the driver provider is Microsoft.
That probably means it was not put there by the Boot Camp driver
installer. Similarly, most of these drivers under the "System Devices"
branch are provided by Microsoft, not by Intel. Is that what one
would expect for this Intel chipset?

Something odd I noticed: when I checked "Programs and Features"
in the control panel, it was clear that Apple's program had installed
support for iSight, infrared remote, multitouch and touchad. I don't
think a Mac Pro has any hardware that would justify installing that
stuff. Bizarre.

On Mac Pros its fairly easy. The MBPs are a bitch sometimes with their partitioned drives and their Nvidia chipset. I still havn't figured out how to set AHCI driver to my uMBP.
Click to expand...

Ouch! :)
 
gugucom said:
My MacPro1,1 has an Intel driver.
Click to expand...

That's interesting. Also, the driver dates:

For you: 15/09/2006
For me: 21/06/2006

So yours is newer than mine.

Do you know where it came from (from which file)?

Thanks.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back