64-Bit Bootcamp on MBP

I bought a MBP last year around this time (2.4 GHz model, 4GB RAM). I have always wanted to install 64-bit Vista so I could use all of RAM (32-bit only recognizes only 2.98GB). Now to my knowledge, you can now install a 64-bit windows OS on a Mac Pro, but can you install a 64-bit on a MBP without losing any function? (e.g. backlight keyboard, iSight, eject button, F1-F10 specialty keys)
I know this is a topic that has been long discussed, but I cannot find a recent one nor did I spend more than 10 minutes looking for one either. I wold like to know if anyone is currently using a 64-bit windows OS and any troubles they've encountered. Thanks guys!

Vista 64 bit does address all 4 gigs of memory. That's the configuration I'm running.
Boot Camp though, doesn't support anything. You're not "running" boot camp when you're using Windows, so in the future, if you want to install an accessory, instal a program, whatever it may be, completely forget the word Boot Camp. You have a PC (gasp!) contained in an Apple branded case.

Similar Messages

ATI HD 2600 PRO WINDOWS 7 64 BIT BOOTCAMP DRIVER ERROR

as with the windows xp bootcamp insatllation my grahics card the ATI RADEON PRO HD 2600 shows up under device manager as the Ati MOBILITY 2600 XT, this is NOT correct and wasnt correct when i had windows xp installed via bootcamp but the online trick/fix worked by installing the newer updated drivers for the ATI RADEON HD 2600 PRO by manually pointing the installer to the newly download drivers for xp and once that was done my card read correctly under the device manegr in xp and my performance was quadrupled !!!! however since i have now installed Windows 7 64 bit,the same problem appears agin but when i download the correct 64 bit windows 7 drivers form the ati site and even the dedicated bootcamp windows 7 64 bit drivers nad attempt to point the installer to them the error appears "This driver does not appear to work with this version of windows" so basically the old xp bootcamp fix doesnt work with windows 7 64 bit with bootcamp running. There has got to be an easy workaround or fix for this! Tons of windows 7 64 bit bootcamp users are experienceing this install error and without the driver being installed and updating the card to what it truly is and NOT THE MOBILITY VERSION THAT IS BEING DETECTED, we can all run games like before in xp with way better performace. until then we are all screwed and are forced to run the updated drivers for the mobility XT card. PLEASE PLEASE HELP US IF YOU UNDERSTAND WHAT I AM SAYING. look around on the apple bootcamp forums and you will see a bunch of people complaining about the same thing with no solution for over 2 years. i have sent an email to AMD formerly ATI requesting assistance but i am sur ethey will just blow me off. this is a very easy problem that could be fixed by a tech savy person. WHoever can fix this problem at least for me personally,i will gladly sned you at least $100 via paypal for your hard work and time. without this being fixed i have no choice but to buy anothermac with a better graphics card since the imac i have is not upgradeable beyond RAM. Like i said this was the same problem with windows xp in bootcamp before i installed lion. the fix worked. i dont want to hear that the card is NOT a true hd 2600 PRO whn i know it is and have succesfully used the driver hack before with awesome results. it is NOT a mobility card whatsoever. it is an ATI RADEON 2600 HD with 256 megs of VRAM,not the best but still ok to run even the latest pc games with bootcamp. Please please help me! Thank you very much in adfvance for reading this!

Below is what I had to do to work around this issue - I've been running with the modified graphics drivers for over a week now, including running some games under Windows 7. Apologies if this is too basic, but I figured I would write it out step-by-step for anyone who needed the background, rationale, plus instructions:
Procedure to manually update iMac Radeon HD 2600 PRO video card under Windows 7 (64 bit).
Rationale:
> Boot Camp drivers incorrectly identify the video card my 24" iMac (24-inch Mid 2007 2.8 GHz Intel Core 2 Duo - the graphics card is shown as a "ATI Mobility Radeon HD 2600 XT") - this has been a long-standing problem when using my iMac under Boot Camp. You can find procedures online about how to update the drivers manually by obtaining them from AMD then installing them.
Background:
> When I was previously running Windows XP, I was able to perform the graphics driver update per the online instructions, without any problems.
> When I updated to Windows 7, 64-bit (because I updated my Mac OS to 10.7 [Lion] and Windows XP was no longer supported in Boot Camp), I could no longer update the graphic card drivers to the Win7 64-bit version (it was giving an error that the driver was not supported) using the same procedure.
> The solution I finally came upon was to modify the INF file that comes with the drivers from AMD. I take no credit for this, except for the fact that I adapted a procedure I found for doing this for graphics cards in notebooks. The original place I found this is here <http://forum.notebookreview.com/gaming-software-graphics-cards/370695-guide-upda ting-your-ati-drivers-manually.html>.
NOTE & DISCLAIMER: This is the first time I have done something like this, so I don't claim to fully understand every step that is going on here, nor if every step is needed. I based this on the procedure referenced in link immediately above and it seems to be working for me (that is, my graphics card driver was ultimately updated for Win7, 64-bit just like had been previously under WinXP) - YMMV.
>> This procedure was done with the AMD Radeon™ Desktop Video Card Drivers for "64 bit Windows Vista/Windows 7 "; Version 11.7, posted 2011-07-27 (main page: http://support.amd.com/US/Pages/AMDSupportHub.aspx)
1. Driver only was downloaded from AMD.
2. Downloaded file was installed to default location: C:\ATI
3. Gather info about the graphics card:
3a. Open the Device Manager (Start>Computer [right-click]>Properties)
3b. Expand the "Display Adapters" item to reveal the GPU (mine was listed as "ATI Mobility Radeon HD 2600 XT", same as it was under XP)
3c. Right-click on the GPU and select "Properties"
3d. Click the "Details" tab in the Properties window.
3e. Click the drop-down under "Property" (top item should say "Device description) - find the item in the list that says "Hardware Ids"
>> There were four values for my card, shown below:
PCI\VEN_1002&DEV_9583&SUBSYS_0083106B&REV_00
PCI\VEN_1002&DEV_9583&SUBSYS_0083106B
PCI\VEN_1002&DEV_9583&CC_030000
PCI\VEN_1002&DEV_9583&CC_0300
3f. Right click on the first value and select "Copy" - paste it into a separate document. I actually copied all these items and pasted them into a separate text document, but only ended up using the first one.
3g. Go back and click the drop-down under "Property" - find the item in the list that says "Inf section" (it was far down the list).
3h. Copy the value shown there and paste into a separate document; my value read: ati2mtag_M76
4. Modify the INF file from AMD:
4a. First thing I did was make a backup copy of the directory containing the files that were installed in step 2 (located at C:\ATI) - my directory was called "11-7_vista64_win7_64_dd".
4b. Go into this path: C:\ATI\Support\11-7_vista64_win7_64_dd\Packages\Drivers\Display\W76A_INF
4c. Find the INF files (icon is a document with a gear on it), that start with "C7..." and "CH..." (mine were called "C7122569" & "CH122569").
4d. Open the "C7..." file (it opens in Notepad). Go down to the section called "[ATI.Mfg.NTamd64.6.1]".
4e. Do a "Find" command for "ATI Radeon HD 2600 PRO" (if you search for a shorter phrase, be aware there are other "2600 PRO" cards in the list).
>> The exact line I found was <"ATI Radeon HD 2600 PRO" = ati2mtag_RV630, PCI\VEN_1002&DEV_9589>
4f. Replace that line with the Inf section value and the first Hardware ID value, using the same format as the orginal line.
>> The new entry I made read:
"ATI Radeon HD 2600 PRO" = ati2mtag_M76, PCI\VEN_1002&DEV_9583&SUBSYS_0083106B&REV_00
4g. Close the file, saving your changes.
4h. Repeat steps 4d - 4g, using the "CH..." file.
5. Updating the graphics driver using the modified INF files:
5a. Go back to the Device Manager and expand the "Display Adapters" item again to show the "ATI Mobility Radeon HD 2600 XT" GPU
5b. Right-click on the GPU and select "Update Driver Software..."
5c. In the resulting window, choose "Browse my computer for driver software".
5d. I navigated to the "C7..." file along the following path: <C:\ATI\Support\11-7_vista64_win7_64_dd\Packages\Drivers\Display\W76A_INF>
5e. At this point, I was shown a window that showed "ATI Radeon HD 2600 PRO" twice (that's all that was in the list). I selected the first instance and it moved on.
5f. I got a warning that the driver was unsigned, obviously I allowed it to move forward with the installation.
5g. The updating proceeded and the screen momentarily went black, twice. After the second time the description in the Device Manager changed to reflect that the GPU was now "ATI Radeon HD 2600 PRO".
FINAL NOTE: as of right now everything seems to be running properly and I have experienced no problems or graphical glitches. If anyone reading this sees an obvious problem with what I've done, please let me know.

Magic Trackpad pairs with Bootcamp (Win7) MBP instead of another MBP w/Yosemite?

I've 2 MBP's - a Yosemite MBP and one running Win7 via Bootcamp. When the Yosemite MBP is off, the Magic Trackpad pairs with the old MBP (Win7/Bootcamp). I see no clear way to disable this pairing in Win7/Bootcamp or a clear way to disable Bluetooth on the Bootcamp/Win7 MBP either. I can shut down the Win7/Bootcamp PC, but this gets old very quick, as I tend to carry my Yosemite MBP w/me at the end of the day.
Any suggestions from the Mac Geniuses? Thank you.
Martin

Based on the multiple issues, I think I would reinstall OS X 10.10 from the recovery disk (your data is untouched). As always though, make a good backup before doing anything (I use Time Machine and I also make a bootable clone).
Barry

Random BSODs disappear when I uninstall BootCamp on MBP 13" late 2011, w7 x64

Hi, I am wondering if there are faulty drivers in the latest version of BootCamp 4.0 (downloaded on 29.05.2012).
I have MBP 13", late 2011 (MBP81.88Z.0047.B27.1201241646, 24/01/2012), and have installed on it Windows7 Ultimate SP1 x64 using BootCamp. Prior to unistalling BootCamp software, MBP was randomly freezing under Windows7 with a clumsy display. It was logging nothing to the dump files. I have run several times driver verifier and all the times recieved c2 BSOD until I unistalled BootCamp!!! (I can post the dump files if needed.) After that, although I have no access to special features of keyboard and trackpad, I have no problems in Windows and MBP runs fine under driver verifier's stress tests.
An interesting observation that I can make is that without BootCamp CPU cooler seems to be noisier.
Vjerb

Get out a pencil and paper. Open the dictionary.
Your computer came with instructions and booklet.
http://www.apple.com/support/my_mac_computer_model
http://www.apple.com/support/macbookpro
http://www.apple.com/support/
ie, look up the manual for your macbookpro model

Some Solutions, 1 remaining prob with MBP, Windows 7 64-bit, Bootcamp

It has taken me about 3 months to get Windows 7 64-bit (OEM disk purchased from TigerDirect) to work on my MacBook PRO 17" 2.4GHz, and it is still not quite there.
FIRST: It seemed impossible to load. I put the disk in the drive, held Option key down, selected Windows (from the DVD), and was presented with a black screen with white writing that said: 1. 2. Select Boot Type. That would be it. No response from the keyboard or even a USB keyboard. I read about an incompatibility with EFI naming conventions between Apple and Microsoft. Something about naming conventions. The solution is elsewhere in these discussions and involves re-creating the Windows install DVD with an EFI naming convention that apple likes. That worked, and the re-burned Windows disk booted! Hurrah?? No.
NEXT: The installation process started - all the correct Windows screens popped up, but it was incredibly slow. In fact, the installation process took 24 hours (YES!) to complete. Once it was done, I rebooted. The flying orbs started. I was excited! But instead of a login screen, I was presented with a black screen and a movable white mouse cursor, and that was it. I left it on this screen for 24 hours, with no change whatsoever. No sound. No response to CTL-ALT-DELETE. No response to holding the shift key down or pressing it 5 times - all things recommended by some folks who were able to pull up taskmgr this way and launch Explorer. For me, this was not possible. Nothing worked.
NEXT: I thought I'd check to see if Windows 7 64-bit really installed on the bootcamp partition. I did this by firing up Parallels 5 and pointing it at the bootcamp partition, where it found Windows and cheerfully offered to boot it for me. It worked, but this is not what I wanted. Still, it was enough to prove to me that the install was complete, valid, and bootable.
Months passed with trying various things.
Finally, I read about something involving memory. I fired up parallels, went to a dos prompt in my Windows 7 install thanks to Parallels access to it, and typed MSCONFIG. There's a boot tab there, and when you click on Advanced, you'll see a Maximum Memory box. Type a number in here like 2000 or 3000 (I have 8GB RAM installed, so I typed in 4000) and applied the change, then shut down windows in Parallells. Then, I restarted my mac and booted into Windows. Guess what??!? It BOOTED!! Now, all memory tests tell me that all 8GB of my RAM are fine. I swapped the two DIMMS and no change, so one DIMM is not bad. My EFI is 64-bit capable. My Windows version is 64-bit. So, when I right click on My Computer, select Properties, and read the screen it says: MEMORY: 8GB installed, 2.97GB usable. Now, I understand that some of the 4GB is used up by devices so I get this 2.97 number, but what gives??
So this is where I need some brilliant guy's help: What's the deal with the RAM? If I type a number above 4000 in the box in Windows, I can go up to about 4080 but after that, the number won't stick (goes to 2 or 3 or something crazy). Again - EVERYTHING is 64-bit: The EFI, the Windows 7 install, and my MBP is one of the supported ones. So what on earth could be the problem?
(Oh, and yes, I loaded the Bootcamp 2.2 drivers from my Snow Leopard DVD, then loaded the Bootcamp 3.1 updates and drivers, yes my Magic Mouse works, yes the screen is perfect, yes I do have sound, yes Windows Properties says it's Windows 7 64-bit, but I do have the heat problem mentioned elsewhere in these forums.)
Your thoughts would be very appreciated!

I'm looking into running Windows 7 64bit on the exact same MBP you have, so I'm curious as to whether or not you've found a solution yet outside of the forums.
Do you think it might be that the bootcamp 3.1 update is only for Windows 7 32bit and not for the 64bit version?

Macbook Pro (Late 2008) - Windows 7 64-bit, Bootcamp 3.1 - Wireless Issue

Hi Everyone,
I have a Macbook Pro (15-inch, Late 2008) model with Snow Leopard and Windows 7 64-bit dual boot. I have done a search and cannot find any reference to this problem on my hardware.
I have had no issues in Windows 7 when using Bootcamp v3.0. In the last week I have upgraded to Bootcamp v3.1. (completed twice, rolled back in between to prove that the issues was related to the Apple Update)
After I update to v3.1, I have issues with my wireless network. The network cannot resolve the name for any internet address. I can connect to wireless networks (tried multiple networks), all the DHCP settings seem to be retrieved correctly (Gateway, DNS etc) and I can ping local and machines outside my network without an issue provided I use the IP address. (Skype works - which uses direct IPs rather than names I have found over time)
As soon as I use a name for a destination for Web traffic, Mail, pinging (any application), my Macbook Pro cannot resolve the address and just bombs out.
If I connect to a wired network, the machine works perfectly and name resolution on that interface works. If I rollback (using Windows 7 rollback capability) to before the v3.1 Bootcamp is installed, the wireless networking also works perfectly.
I noticed this in the support area at apple:
http://support.apple.com/kb/TS3196
But this refers to wireless issues in Bootcamp drivers prior to v3.1 and on 13 inch Macbook. Wonder if this is a similar issue or related?
Anyone else seen this or point me in the direction of a fix?
Thanks,
Thommo

I'm looking into running Windows 7 64bit on the exact same MBP you have, so I'm curious as to whether or not you've found a solution yet outside of the forums.
Do you think it might be that the bootcamp 3.1 update is only for Windows 7 32bit and not for the 64bit version?

Sharing experience with BootCamp on MBP 13" 2010 model

Hello,
i want to share my bootcamp experience with other Macbook owners. Today i tried install Windows XP and Windows Vista, as a second OS.
Windows XP - OS installation without any problems. Bootcamp installation, i cant even call this process "installation". First when i tried to install BC (bootcamp) i had BSOD ( happens everytime, reinstalled system and tried again ), when i restarted MBP and tried install BC again, "process" was done without errors. But i-Sight, Bluetooth, and ethernet drivers are not working. So there is no internet connection. Also audio is not working with BC 3.1, but 3.2 update ( if u manage to install it... .download in osx, move to windows partition and install from windows, because of no internet connection ) fixes audio issue. ( Windows XP proffesional SP2 32bit ).
Windows Vista business 64bit - same problems like windows xp. I googled a lot, trying to find some solutions, but nothing worked for me.
Verdict - no offence, but i think somewhere near this advertising "Mom always said, “Play nice with others.” Your computer should, too. With Mac OS X, you can use Microsoft Office, connect to most printers and cameras, join PC networks, and even run Windows." should be written - at the moment you can enjoy windows experience without internet.

I agree, I think a couple things would make it a lot easier.
The method for MacBook Air of creating a set of drivers to put on USB thumb/flash drive.
http://support.apple.com/kb/HT4407
Full download of Boot Camp 3.2, no pre-requisite needed (maybe put your SL DVD in to "authenticate/activate" though it would be useless for any PC, and is aimed at people running Tiger/Leopard to have to get $29 DVD if they don't already want/need 10.6.
Skip Windows XP. Only SP3 is supported, Vista is a shame, and 32-bit OS are history, so just support Windows 7 64-bit Home Premium and above.
Apple BC FAQ
http://support.apple.com/kb/HT3777
http://www.apple.com/support/bootcamp/
iMac Black screen (maybe generalize this for other users)
http://support.apple.com/kb/TS3173
Boot Camp drivers (MacBook 2010 support drivers_
http://support.apple.com/downloads/#bootcamp
About Boot Camp Software Update 3.2 for Windows 64 bitThis update adds support for the ATI-Radeon HD 5870 graphics card, Apple USB Ethernet Adapter, MacBook Air SuperDrive, and addresses critical bug fixes. This update is highly recommended for all Boot Camp 3.1 users.
http://support.apple.com/kb/DL979
EFIupdate improves the performance and reliability of (.....) processors and fixes issues with Boot Camp for MacBook computers.
Doesn't tell us if it 'fixes' thermal fan control or what it does, and could be said of most any and all updates you see.
Mac users are not always versed in having to find and manually install audio drivers, issues with graphic card and drivers (and graphic drivers are a bit of a pain) and some expect full graphic driver support, when the ideal would be to direct to AMD or Nvidia and get current driver. Same with RealTek and Cirrius audio.
Thermal fan control: SpeedFan has not worked but would be a logical utility to get working if possible.
This results in higher temperatures because there is no driver or service to provide the fans with input from thermal sensors to regulate rpm and heat.
Not having internet connection is a "catch-22" (often but not always wireless won't but wired will, and good idea to first establish a wired connection and make network configurations first).
Boot Camp 3.0 drivers - copy to a folder where you can use "Troubleshoot Compatibility" and run
Apple\Drivers\Bootcamp64.msi
Where 'catch-22' if you can't use control + click or touchpad, you are also stuck and need a wired USB kb and mouse.
+note: Some articles link to Apple Downloads, which will all 'break' when Apple Downloads section is removed come 2011? seems odd but have to stay tuned how it works.+

Bootcamp issues MBP Retina 13" 2015

Hi all,
I've been playing with my new mac for a few days now and I've got a few issues - not with OSX, but with Windows 8.1 (Bootcamp).
Eventually everything installed ok and it's been running fine, however here are the problems:
1) the force trackpad doesn't work reliably in Windows - Primarily this is related to clicking and dragging, which can take a few tries before it responds properly. Also the right click sometimes doesn't respond at all (though i get the feedback from the force touch track pad). I've tinked with the various settings in the bootcamp control panel but nothing has improved it.
2) My external monitor, when connected to the MBP via DisplayPort, keeps losing sync and produces a black screen for a few seconds. Initially I though this was completely random, but I can now reliably recreate the issue in some instances - e.g. when i load gmail via googlechrome, it loads fine, but then the screen goes blank for a few seconds. The MBP display doesn't turn off. This happens in both extended display and duplicate display (mirror) modes, at any resolution. the odd thing is it only happens when the monitor is connected via DisplayPort - HDMI and VGA connections work fine. I have to connect via DisplayPort though as I want to run the monitor at its full resolution (2560x1440) which isn't supported on the HDMI output of the MBP. Note every time the monitor drops out, a short, static noise emits from the monitor speakers.
In relating to 2), i've also noticed an issue when playing YouTube videos - they either play too fast or too slow (causing intermittent monitor dropouts as above). This is really odd! Disconnecting the external monitor and it works fine on the MBP.
I suspect both of the above issues are driver related - anyone else had similar issues and/or can offer advice on how to fix??
Thanks in advance
Mike

OK so i've isolated the display issue - it appears to be related to 'hot swapping' - if i boot the macbook in windows (from off) with the display already connected, it works fine with no problem. However, if i connect the display after it's booted, or disconnect and reconnect the display, the problems return.
I'm guessing this is related to the fact i'm using a thunderbolt port, and it's not hot pluggable in my version of the mac - Thunderbolt ports and displays: Frequently asked questions (FAQ) - Apple Support
however i'm a bit annoyed as it's not a thunderbolt display - it's a displayport display. I know windows starts up quickly but it's still a pain to have to reboot every time i want to connect a display.
Anyone any thoughts on this or the trackpad issue?

Bootcamp on MBP vs Windows laptop

I have an HP laptop to run specific Windows software and for travel. I also have a MBP with VMWare Fusion. But I can't run all the Windows software I need on the MBP because it would grind to a halt. However, I don't like Windows' laptops. I'd rather get another MBP and use Bootcamp. It would always be in Bootcamp running WinXP. With the MBP, I can than take advantage of the MBP's superior trackpad and hardware, among other things. I'd also be able to run WinXP, which you can no longer get on laptops.
For those using Bootcamp and Windows on a Macbook, have you noticed any disadvantages vs using a dedicated Windows laptop?
Price aside, is there any reason to get a dedicated Windows laptop vs a MBP running Bootcamp?

brett romero wrote:
I have an HP laptop to run specific Windows software and for travel. I also have a MBP with VMWare Fusion. But I can't run all the Windows software I need on the MBP because it would grind to a halt. However, I don't like Windows' laptops. I'd rather get another MBP and use Bootcamp. It would always be in Bootcamp running WinXP. With the MBP, I can than take advantage of the MBP's superior trackpad and hardware, among other things. I'd also be able to run WinXP, which you can no longer get on laptops.
For those using Bootcamp and Windows on a Macbook, have you noticed any disadvantages vs using a dedicated Windows laptop?
Price aside, is there any reason to get a dedicated Windows laptop vs a MBP running Bootcamp?
Your MacBook Pro must be a little dated, likely a dual core 32 bit processor with 4GB RAM limit.
I can tell you these quad core I7's MacBook Pro's are awesome.
This is what I suggest you do based upon my expereince with this new machine:
1: Get a high end 15" or 17" anti-glare MacBook Pro and max out the RAM to 8GB.
2: Get the 7,200 RPM performance drive if your on power most of the time, if not, then the 5,400 RPM drive as it gives a bit more battery life. (you can set the drives to spin down when not in use as well to consever battery). Apple Stores only carry 5,400 drives in their computers, however online you can special order the 7,200 RPM drive. I don't recommend SSD, too expensive per GB, limited writes and not being erased. So you lose a important security option for Windows, completely erasing the drive of any malware. Also if you travel between countries some have more stringent rules concerning adult content than others. Technology exists to inhale all data off computers, smartphones etc. with plug and play ease.
3: Before setting up the new machine, c boot off the OS X installer disk and use Disk Utility to Secure Erase/Zero your boot drive. This will map off bad sectors ahead of time and greatly improve reliability. Install OS X when finished.
4: Setup your new machine, don't use your real info in the setup or Apple places it all over the place and Windows/Fusion copies that and displays it online for everyone to see (so and so's network and computer for instance). Use Apple's Bootcamp to install Windows 7 Pro 64bit. 32 bit is history, and Win 7 Pro (and above) will allow you to virtualizes XP so you can run your XP programs. You will need the FULL disk, not the upgrade disk natrually.
5: Once you got that all setup and your XP programs installed. Install VMFusion in OS X, have it use the Bootcamp partition as your virtual machine! Give Windows 7 Pro in VM (based upon my experience) 2 processor cores and half your RAM (either 2GB or 4GB) If you give Win 7 four cores (out of 8 hyperthreaded cores) your going to slightly better performance, but at a cost to stability with OS X. That might change with giving Win 7 Pro 4GB of RAM instead (I got only 4GB total right now so 7 gets only 2GB)
6: As you know, Mac video cards use OpenGL, not Direct X. So any 3D games not using OpenGL drivers is going to suffer performance loss either in Windows VM or Bootcamp.
I ran Cube 2 in both Windows 7 Pro in VM and directly in OS X, it uses OpenGL drivers. In OS X I get solid 200 fps. On Windows +100 fps constantly. Naturally the OS X version was more stable. But just goes to show the extereme performance of these new i7's and their video cards.
I get 6.0 scoring (out of 7.9 max) on Windows 7 Pro in VM with four cores and 3GB of RAM, but my drawbacks are the slow 5,400 RPM drive and the limited 4GB of RAM I have. I tend to upgrade to better quality drives later, also RAM from Crucial since Apple charges so much.
So now if you need full performance you can direct boot into Windows 7 Pro, run all your XP programs with maximum RAM and processsors cores (4, 8GB) or half that in virtual machine under OS X. Also I might add that I think VM Fusion 3 will be needing a update to work better with these new Sandy Bridge processors. Just a few glitches here and there, minor ones.
Oh, and the anti-glare will allow you to use the computer in nearly any condiiton. A small cost for 100% improvement in viewing the screen clearly.
Good Luck and hope this helps
17" MBP i7 2.3 Sandy Bridge 2820QM Radeon HD 6750, Mac OS X (10.6.7), VM-ed: Windows XP, Vista, 7, Linux Mint, MacBuntu, Like XP, Puppy, TinyCore, DSL

Re: ATI HD 2600 PRO WINDOWS 7 64 BIT BOOTCAMP DRIVER ERROR

Okay - I *think* I was able to get the modified INF to work properly now - it turns out there were many more instances where changes needed to be made that my original procedure did not address. The updated procedure is below with additional steps added.
Procedure to manually update iMac Radeon HD 2600 PRO video card under Windows 7 (64 bit).
Rationale:
> Boot Camp drivers incorrectly identify the video card my 24" iMac (Dual core; 2.8 GHz - graphics card is shown as a "ATI Mobility Radeon HD 2600 XT") - this has been a long-standing problem when using my iMac under Boot Camp. There have been reports about how to update the drivers manually by obtaining them from ATI/AMD then installing them.
Background:
> When I was previously running Windows XP, I was able to perform the graphics driver update per the online instructions, without any problems.
> When I updated to Windows 7, 64-bit (because I was updated my Mac OS to 10.7 [Lion] and Windows XP was no longer supported in Boot Camp), I could no longer update the graphic card drivers to the Win7 64-bit version (it was giving an error that the driver was not supported).
> The solution I finally came upon was to modify the installer .INF file that comes with the drivers from AMD. I take no credit for this, except from the fact that I adapted a procedure I found for doing this for graphics cards in notebooks. The original place I found this is here <http://forum.notebookreview.com/gaming-software-graphics-cards/370695-guide-upda ting-your-ati-drivers-manually.html>.
NOTE & DISCLAIMER: I don't claim to fully understand every step that is going on here, nor if every step is needed. I based this on the procedure referenced in link immediately above and it seems to be working for me (that is, my graphics card driver was updated for Win7, 64-bit just like had been previously under WinXP) - YMMV.
>> This procedure was done with the AMD Radeon™ Desktop Video Card Drivers for "64 bit Windows Vista/Windows 7 "; Version 11.7, posted 2011-07-27 (main page: http://support.amd.com/US/Pages/AMDSupportHub.aspx)
1. Driver only was downloaded from AMD.
2. Downloaded file was installed to default location: C:\ATI
3. Gather info about the graphics card:
a. Open the Device Manager (Start>Computer [right-click]>Properties)
b. Expand the "Display Adapters" item to reveal the GPU (mine was listed as "ATI Mobility Radeon HD 2600 XT")
c. Right-click on the GPU and select "Properties"
d. Click the "Details" tab in the Properties window.
e. Click the drop-down under "Property" (top item should say "Device description) - find the item in the list that says "Hardware Ids"
>> There were four values for my card, shown below:
PCI\VEN_1002&DEV_9583&SUBSYS_0083106B&REV_00
PCI\VEN_1002&DEV_9583&SUBSYS_0083106B
PCI\VEN_1002&DEV_9583&CC_030000
PCI\VEN_1002&DEV_9583&CC_0300
f. Right click on the first value and select "Copy" - paste it into a separate document.
g. Go back and click the drop-down under "Property" - find the item in the list that says "Inf section" (it was far down the list).
h. Copy the value shown there and paste into a separate document; my value read: ati2mtag_M76
4. Modify the INF file from AMD:
a. First thing I did was make a copy of the directory containing the files that were installed in step 2 (located at C:\ATI) - my directory was called "11-7_vista64_win7_64_dd".
b. Go into this path: C:\ATI\Support\11-7_vista64_win7_64_dd\Packages\Drivers\Display\W76A_INF
c. Find the INF files (icon is a document with a gear on it), that start with "C7..." and "CH..." (mine were called "C7122569" & "CH122569").
d. Open the "C7..." file (it opens in Notepad).
e. The first thing I did was find and replace all existing instances of "M76" in the INF (I arbitrarily replaced it with the following value "M7a6"). There are a number of existing references to this property type in the original INF.
> I do not know if this is absolutely necessary but I found that it helped me to distinguish what was originally there with what I was modifying.
f. Do a "Find" command for "ATI Radeon HD 2600 PRO" (if you search for a shorter phrase, be aware there are other "2600 PRO" cards in the list).
> The exact line I found was <"ATI Radeon HD 2600 PRO" = ati2mtag_RV630, PCI\VEN_1002&DEV_9589>
g. Replace that line with the Inf section value and the first Hardware ID value, using the same format as the original line. The new entry I made read (notice that each successive entry has an addition <space> between the end of 'PRO' and the ending double quote):
"ATI Radeon HD 2600 PRO" = ati2mtag_M76, PCI\VEN_1002&DEV_9583&SUBSYS_0083106B&REV_00
"ATI Radeon HD 2600 PRO " = ati2mtag_M76, PCI\VEN_1002&DEV_9583&SUBSYS_0083106B
"ATI Radeon HD 2600 PRO " = ati2mtag_M76, PCI\VEN_1002&DEV_9583&CC_030000
"ATI Radeon HD 2600 PRO " = ati2mtag_M76, PCI\VEN_1002&DEV_9583&CC_0300
h. Next do a find for all instances of "ati2mtag_RV630"; for every instance you will need to replace that value with " ati2mtag_M76".
i. Next do another find for "RV630" and make sure to replace all instances with "M76" (this is to catch the couple of places where it doesn't have the "ati2mtag" prefix)
j. Close the file, saving your changes.
k. Repeat steps 4d - 4i, using the "CH..." file.
> I personally do not think this is needed since I believe the "C7…" INF is for Windows 7 and "CH…" is for Vista, but I modified both anyway.
5. Update the graphics driver using the modified INF files:
a. Go back to the Device Manager and expand the "Display Adapters" item again to show the "ATI Mobility Radeon HD 2600 XT" GPU
b. Right-click on the GPU and select "Update Driver Software..."
c. In the resulting window, choose "Browse my computer for driver software".
d. I navigated to the "C7..." file along the following path: <C:\ATI\Support\11-7_vista64_win7_64_dd\Packages\Drivers\Display\W76A_INF>
e. At this point, I was shown a window that showed "ATI Radeon HD 2600 PRO" twice (that's all that was in the list). I selected the first instance and it moved on.
f. I got a warning that the driver was unsigned, obviously I allowed it to move forward with the installation.
g. The updating proceeded and the screen momentarily went black, twice. After the second time the description in the Device Manager changed to reflect that the GPU was now "ATI Radeon HD 2600 PRO".
FINAL NOTE: as of right now everything seems to be running properly and I have experienced no problems or graphical glitches. If anyone reading this sees an obvious problem with what I've done, please let me know. I have run benchmarks between this and the standard installed mobility driver and I get about a 10% increase in overall FPS (using the free "NovaBench" app by NovaWave).
< Edited By Host >

look what this guy said:
Hi Guys,
I've spent a few hours over the last week trying to find something that works to update the driver. Using the Mobility Modder from Driverheaven I managed to install the Catalyst 7.8 but not the actual driver - you need to modify the INF for this. The only problem is that I can't be sure what the differences are between the mobility 2600 and the standard-computer 2600. I would like to assume it's just a few settings such as power saving and interal/ external displays.
I tried to modify the INF and used the settings for the standard graphics card. It worked fine, but I put the original Apple driver back on because I didn't want to find out I was overclocking the Graphics CPU accidentally.
After using mobility modder I added this line just after the mobility 2300 graphics card entry:
"ATI MOBILITY RADEON X2600 XT " = ati2mtag_RV630, PCI\VEN1002&DEV9583
If you notice and compare the mobility and standard entries, the mobilities have the same ati2mtag but followed by M-something rather than RV-something.
This appears to direct the INF to the correct setup of the Catalyst software for that card - as I say, I used the settings for the standard 2600 card and it installed ok. I didn't try any games though.
On another note, I'm resisting doing anything further or testing any games until I have the screen issue resolved - after exchanging the naff 20" screen with it's horizontal shading (a dark shade at the top to a light shade at the bottom - very noticeable with darkish solid colours!) I've found my new (more costly!) 24" is having some problems with picture breakup, though so far only in Vista which I installed via Bootcamp.
I wish Apple would get there act together. It's my first Apple and I was expecting great things! So far, I would have had less hassle if I had built my own computer with Vista on and thats saying something!!
Matt
he added the RV630 string. but i tried that with my exact windows xp driver device ids and yes it still completed the installation successfully,but the fps sill stayed the same

Fn F7 keys won't work in BootCamp on MBP

I'm trying to use a projector with my MBP to teach CAD in BootCamp. The problem is that I can't mirror my screen when using bootcamp, like I can in OS X. I can get an extension of my screen, but can't display the contents of my screen on the projector.
Normally you would use the fn F7 keys to toggle through the display options, but in Windows XP the fn F7 won't work.
Does anyone have any ideas? A remapping program for MBP? Please Help.
Brett

Have you tried the windows way (right click on desktop > properties > settings and uncheck Extend my Windows desktop... ?
Hope this helps...

Bootcamp, XP, MBP 13" and trackpad

Is there any way to get the trackpad to work under Windows XP on a MBP 13 using bootcamp? I am working a cunning plan to get a devout PC user over to a Mac and a right-click capability is an absolute must on this trackpad. I use the magic trackpad and the two-finger click is second nature, can I do anything like it for XP on the MBP. The Control Panel only has controls for a mouse, is there one for a trackpad?
Thanks - Lawrence

MBP keyboard mapping in Windows http://support.apple.com/kb/HT1220
Usage of Microsofts Keyboard Layout Creator http://support.apple.com/kb/HT2587
Multi Trackpad support in Windows http://support.apple.com/kb/HT4273
Some gestures are simply not supported in Windows.
Stefan

Bootcamp and MBP Retina

Anyone know when the Bootcamp drivers will be made available?

Factory Unlock wrote:
Hi Rudegar,
Thnaks for feedback but what do u suggest? should i uninstall windows and try again. I did checked the option in bootcamp during win install "Download windows support software" but my MBP got stuck while downloading win support software.. i waited for more than 3 hours but it never moved ahead after 50 odd %. So i tried again with unchecking this option and once win were installed i downloaded bootcamp 5.0 and installed it but my display was not detected.
Have you restarted Windows since installing, if not try it.

Bootcamp installation MBP 2013

Hi everyone,
I've just purchased myself a one of the new MBPs today and am required to run Windows 7 on it via Bootcamp as I need it to run some windows based software for the dissertation I am currently writing.
Anyhow, onto the topic at hand, I am getting really confused with how to set up bootcamp. Especially how to do it without the CD drive. ie I'm unsure of how to create the ISO on a usb stick and whether or not I need to buy a physical copy of windows or can I download the ISO, put it on a usb, and then purchase a license for Windows 7 (Can you get these on Amazon?).
Any help would be much appreciated.
Cheers
ipto442

You only need the iso and an usb stick. The process is explained here:
http://manuals.info.apple.com/MANUALS/1000/MA1636/en_US/boot_camp_install-setup_ 10.8.pdf
Im getting mine on monday, could you tell me if everything works ok, please ?

Rescue Vista Ultimate SP1 64 bit Bootcamp Installation as Hard Drive Fails

I have been using a Bootcamp installation of Vista Ultimate SP1 64-bit retail since May 2008 without a problem. Vista was installed (accidentally) on two drives, both of which are separate from the two Mac OS drives. I would have preferred to install it on only one drive, and thought that I had done so.
All my Windows documents and programs are on Drive C (Bay 2), which appears as a Master Boot Record Partition in Disk Utility. Drive D (Bay 3) contains some of the Vista files (including the Boot directory and bootmgr), but nothing else, and appears as a GUID Partition Table in Disk Utility.
I have now begun to receive an S.M.A.R.T. warning that Disk D is failing. It was backed up last week before the warning to a Windows Home Server, but no longer backs up. I would like to replace Drive D with a brand new drive, but know from past experience that Vista will not boot if I simply remove Drive D. Aside from the Vista boot content, there is nothing on drive D that I need.
How should I best proceed to avoid losing programs/data on drive C when replacing drive D? Should I remove drive D, and try to boot from the Vista Ultimate SP1 retail CD to "repair" drive C? Is there some other approach that would avoid having to start from scratch with a new Vista installation?
Starting from scratch is very unattractive. The initial installation of Vista was a difficult chore that involved "cleaning" the brand new hard disk from the Vista CD (with Microsoft support), since it would not install on the Bootcamp-formatted drive. In addition, Drive C has software and documents that I use regularly and would rather not have to recreate.
Many thanks in advance for your suggestions.

So you do have at least one good backup. And you have used Vista file and PC backup as well, so you could do a restore if needed?
Whatever you do, I would pull all your drives and drop in one or two fresh drives.
I've never felt comfortable or safe with Acronis - doesn't support GPT.
Prosoft DataBackupPC 1.0 - used to use for backups but never did a restore.
Paragon HD Manager 2009 - seems to have a lot of tools but someone said it doesn't yet have full Mac and Boot Camp support.
My system is Vista and Windows 7 on one drive, data and such on #2 and multiple backup drives - one internal and a couple hot swap external.
SMART is not very good at predicting and you are at the point where what? I/O errors? bad or weak sector(s)? have you ever used the disk check to repair files and attempt to fix any bad blocks?
Depending on the make of the drive, you want to use the vendor's utility - often before even using a drive - to do a full surface scan and repair.
I remember when you had trouble installing.
Oh, and I would make a new backup. Even if it means pulling your OS X drive and dropping a new drive in there, and make it a backup of programs, files, documents, whatever, and maybe a system image backup.
Can you restore from the server? while booted from Vista DVD?
I have a somewhat similar problem with a drive "D" with nothing on it now that is "owned" by Vista that I want to get rid of and strip so I can use it for backup or something else.... but afraid to.

64-Bit Bootcamp on MBP

Similar Messages

Maybe you are looking for