Installing Windows 7 64-Bit Using BootCamp on Mac Pro 2,1 (Early 2007)

I was waiting to see if the original poster was still intent on going through with it, since it's (a) lot of work, and (b) an unsupported configuration. Unless he's using > 4GB of memory I'm not sure why he needs the 64 bit version of Win7 (there's even less reason to run 64-bit Windows as a VM). I'm not prepared to assume the responsiblity of solving any/all current and future problems he may run into, especially if this is for "work" and not a hobby-level, "I just want Win7-64bit" situation. If he's reading this and wants to proceed -

The Jowie page, while workable, requires a more steps (i.e. even more work); plus, the screenshots used are from an earlier release of imgburn, which has different options from the current version, and if the original poster needs that much handholding he could be put off.

Win7 AIK is "needed" because of the oscdimg.exe that is included. It is the "official Microsoft sanctioned" way of generating Windows ISO images. It's a one-line command that outputs an ISO image file once you have the Win7 disc in the drive, no need to muck about checking/unchecking boxes etc., and running the risk of burning coasters (since there's no way of knowing whether your output works until you actually run it, and imgburn has too many ways of messing up when you don't know what you're doing).

There are alternate "direct" sources for oscdimg.exe, which are smaller downloads than Win7 AIK http://www.microsoft.com/downloads/en/details.aspx?FamilyID=696dd665-9f76-4177-a 811-39c26d3b3b34&displaylang=en , but I'm a little chary of "programs sourced from unidentified hosts", even though I'm certain most of them are just being helpful and are not malicious (have you read Ken Thompson's Reflections on Trusting Trust - http://cm.bell-labs.com/who/ken/trust.html )

If the original poster (or anyone else reading) is interested, either the jowie.com method can be used, if you are averse to a command line or have poor download bandwidth, or you can get oscdimg.exe (however you choose to do so) and execute:

oscdimg -n -m -bd:\boot\etfsboot.com d:\ c:\iso\win7dvd.iso

assuming oscdimg.exe is in your path (or your current directory), and you've created a directory c:\iso

Incidentally, after getting 64-bit Win7 installed your problems aren't over yet, because Boot Camp will refuse to install the 64 bit version on your "unsupported" machine. There is a workaround (see my post in the thread http://discussions.apple.com/thread.jspa?threadID=2589967&tstart=0 ) but I do not know if there will be a future release of Boot Camp that would defeat this.

weileongtan wrote:
Incidentally, after getting 64-bit Win7 installed your problems aren't over yet, because Boot Camp will refuse to install the 64 bit version on your "unsupported" machine. There is a workaround (see my post in the thread http://discussions.apple.com/thread.jspa?threadID=2589967&tstart=0 ) but I do not know if there will be a future release of Boot Camp that would defeat this.

incidentally, if anybody's reading this: this workaround - while it works (heh), there's an issue in that Apple Software Update won't recognise it - the supplied version of Boot Camp on the Snow Leopard disc is v3.0, and there is a v3.1 update out. Apple Software Update will install it ("successfully"), and then the next time round, it'll report that that v3.1 is "not installed" and ask to install it. You can select the v3.1 update option in ASU and select it to be "ignored", but I do not know the implications of this if v3.2 is ever released.

One possible/alternate way of installing v3.0 boot camp (that may or may not solve this - I've seen it work, I've seen it not work) is to manually edit the BootCamp64 to drop the version check on launch, but to do that you're going to need something called the "orca database editor" (the installer of which is part of the Windows Installer SDK, i.e. not the actual orca executable, so even more steps).

So, seriously, don't use 64-bit Win7 unless you really have to (and that does not include "losing" a bit of addressable memory, i.e. if you're slightly above 4GB (inclusive of vram), it might not be worth the hassle and you could just live with "excess" unuseable memory).

it's gonna take a lot of work. basically the 2,1 has EFI32 so the installation will stall you at "select cd rom boot type" with the default Win7 boot disk. The workaround will require you to build a Win7 boot disk with a different feature set - you'll need to have a working Windows installation (so, either access to another PC, or run it in parallels or vmware), AND you need to get ahold of the Windows 7 Automated Installation Kit (well, just one program out of the whole 1.7GB download, but there's no other "official" source), a blank DVD, and a lot of time.

it's gonna take a lot of work.

Ah, does that help? think not, while it has rough outlines just confuses. A YES/NO? no links? No, "this is what I did" steps?

It isn't that hard.

Yes, you might one to use a VM, VirtualBox is free and works.

You can also install 32-bit version and from inside that, do a separate install to another partition for 64-bit.

Imgburn is what I used. There are other tips - MacRumors, Google etc.

Windows 7 Automated Installation Kit - whatever for? never needed.

It isn't Apple, not totally. It is how EFI based computers, and 64-bit Windows - anything from Vista SP1 forward.

This is all I needed to use:
Select-CD-ROM-Boot

I had a long thread but that is old and got moved.

I have Mac Pro 2,1 (early 2007) 8-core, my OS X is 10.6.4

You don't know Mac Pro I guess? dual processor and most people definitely have more than or at least 4GB. 64-bit has better memory handling and support for today's graphics cards which can have 1GB VRAM.

I did the upgrade multiple times on my 2006 "unsupported."

I have one.

The 2,1 was shipped with 1GB. Not everyone would have hit or exceeded 4GB with upgrades, particularly considering the requirement for Apple heat sinks (or the fans run all the time) for RAM upgrades for that model, and Apple RAM prices. It would've been better to wait for the original poster's response to see what he actually has/wants, rather than encouraging him to start burning discs right off.

It's not a question of whether or not the drivers "can" be installed, it's whether it "should". I was not aware you're in a position to guarantee that Apple will never release updates that would have problems.

"you can install 32 bit and then install 64 bit on another partition from there"


does that mean with no other hoops to jump thru with image burn and on? i already have winxp on macpro and am looking to install some version of win 7, maybe pro to get dual processor and 64 bit for memory handling

bigboots1 wrote:
"you can install 32 bit and then install 64 bit on another partition from there"

err, where did you get that from? I don't think I said it. I wouldn't do it that way. I don't know how the bootloader would work. You don't want to be in a situation where the bootloader of the 64 bit OS is residing on the 32 bit partition - the day could (will?) come when you forget about it, nuke the 32 bit partition, and then the next bootup you find you can't get into the 64-bit partition.