64-bitWindows 7 and 2006 Mac Pro

[Dae]

Bump. I too have a CACHE_MANAGER BSOD on Mac Pro early-2008 running Windows 7 Ultimate 64 bit after installation of Bootcamp 3.0 from Snow Leopard DVD. Any ideas how to fix it?

 

[slughead]

Bump. I too have a CACHE_MANAGER BSOD on Mac Pro early-2008 running Windows 7 Ultimate 64 bit after installation of Bootcamp 3.0 from Snow Leopard DVD. Any ideas how to fix it?

Uninstall bootcamp 3.0. It's not ready for Win7 yet.

 

[nanofrog]

Uninstall bootcamp 3.0. It's not ready for Win7 yet.

Anyone have any idea as to when Boot Camp 3.1 is set to release (Win7 ready)?

 

[gugucom]

Gugucom, could you give me the details on that HFS driver? If I can disable that particular driver, that would be great - but which driver / file / service is it? Is it a startup TSR I need to disable, a service I need to set to Disabled, a particular item in Programs and Features I need to uninstall?

Sorry to take so long on this. I found it out some days later but did not remember the info was requested.

The HFS driver is in the windows/system32/drivers/AppleHFS.sys location on your windows partition. Renaming it will be a simple cure for the problem. Afterwards you will not be able to read HFS files from Windows any more. If your system is stable long enough you can do the rename from Windows Explorer with the system files set to visible. If you crash before you get to that point you can do it from OS X with Finder.

There are two different cases again depending of the windows file system. As you are most likely running NTFS you cannot write to the file. You need to install a 3rd party NTFS driver like the free test version from Paragon. If you are running XP with a small FAT32 partition you can write to the file directly.

 

[gugucom]

Anyone have any idea as to when Boot Camp 3.1 is set to release (Win7 ready)?

Apple have said it will be released this year.

 

[nanofrog]

Apple have said it will be released this year.

At least it's not that long (less than 3 months), but those in need of it, are likely going nutz right about now...

 

[Dae]

Sorry to take so long on this. I found it out some days later but did not remember the info was requested.

The HFS driver is in the windows/system32/drivers/AppleHFS.sys location on your windows partition. Renaming it will be a simple cure for the problem. Afterwards you will not be able to read HFS files from Windows any more. If your system is stable long enough you can do the rename from Windows Explorer with the system files set to visible. If you crash before you get to that point you can do it from OS X with Finder.

There are two different cases again depending of the windows file system. As you are most likely running NTFS you cannot write to the file. You need to install a 3rd party NTFS driver like the free test version from Paragon. If you are running XP with a small FAT32 partition you can write to the file directly.

I think safe-mode is easier I will try in an hour.

 

[Dae]

Thank you very much Gugucom! Right after installing Bootcamp, I chose not to reboot and went to C:/Windows/system32/drivers and there renamed AppleHFS.sys to AppleHFS.disabled. After reboot there was no BSoD every 30 seconds anymore.

There appeared a new problem with inability of Bootcamp to change Fn key behavior on Apple Aluminium keyboard, but I fixed it using registry entry.

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\KeyMagic\OSXFnBehavior 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\KeyMagic\OSXFnBehavior

set to 00

Voila, Bootcamp 3.0 on Windows 7 64 bit works.

 

[ghislain]

run bootcamp64.msi

@Gugucom,

I did see that BootCamp64.msi file, and when I tried to run it, it said I can't run it without elevated privs, and it had to be run through Setup.exe (which told me no dice), so yeah - tried that, didn't for for me.

@Bozz,

If you're just loading Win7 in Parallels, you shouldn't have to mod the DVD - that's only if you need Boot Camp to work. I didn't have to do it in VMWare - the original DVD ran fine.

You know, it really depends on what you need Windows FOR, in the first place. I'm a gamer, and I kept around a Core 2 Quad / 9600 GT rig primarily to play Half-Life 2 and related games. But I just discovered Cider where PC games can be ported over to the Mac - I might try that. At the very least I can move my games to the living room PC - it would give me one less excuse to stop working if I didn't have the temptation in the office.

So I've decided I can live without the PC, run just the Pro in the office (instead of 2 computers heating up the room like you would not believe), and run Win7 in VMWare, which honestly runs great because the "Hard disk" is running off the Mac's RAID. If I need a PC for something (flashing a firmware, doing something that REQUIRES a native Windows environment, something), I have the PC in the LR - I've just discovered Boot Camp ain't all that. Which is huge for me - I'm a PC die-hard.

Anyway, everyone goes their own way.

JP

You have to disable UAC in W7 before you can run the bootcamp64.msi file

 

[eyeamfrustrated]

windows 7/ 64 bit/ internet explorer problem???

I have a new macbook pro. I downloaded the latest parallels desktop 5 for
MAC, which also runs windows 7. I loaded windows 7-64 bit. Everything works ok,
EXCEPT it can't find the internet. I can pick up wireless no problem with
safari; internet explorer will not connect at all. I have reset advances
settings in the internet options- still nothing. The message I get is
:Currently connected to: unidentified network No Internet access"
I don't think it is a parallel problem, as I loaded parallels on my home computer which has vista and there are no problems.

Any suggestions please?
Kathy

 

[Dae]

You have to disable UAC in W7 before you can run the bootcamp64.msi file

If we're talking about the latest Bootcamp 3.0 from Snow Leopard DVD, you don't. I installed it on my Windows 7 64bit with UAC on default settings.

Earlier versions of Bootcamp (2.1, for example) ask you to run though Setup.exe and even crash.

 

[gugucom]

I have a new macbook pro. I downloaded the latest parallels desktop 5 for
MAC, which also runs windows 7. I loaded windows 7-64 bit. Everything works ok,
EXCEPT it can't find the internet. I can pick up wireless no problem with
safari; internet explorer will not connect at all. I have reset advances
settings in the internet options- still nothing. The message I get is
:Currently connected to: unidentified network No Internet access"
I don't think it is a parallel problem, as I loaded parallels on my home computer which has vista and there are no problems.

Any suggestions please?
Kathy

It has something to do with a parallels setting for networking. I found this with Google: http://forum.parallels.com/showthread.php?t=92146

Are you using host only networking in parallels. If you are change to bridged or shared networking. You should be able to set up a home network in windows 7 once you change your access in parallels.

 

[eyeamfrustrated]

Windows 7 & MacPro network change

Thank you GuGuCom

I finally got through to Parallels support and sure enough, all I had to do was change to bridged and voila....internet.

I will have to change my sign in name.

Are you using host only networking in parallels. If you are change to bridged or shared networking. You should be able to set up a home network in windows 7 once you change your access in parallels.

 

[21ce]

2006 Mac Pro

I have a 2006 mac pro 1,1 and installed 64-bit windows 7 professional about 3 days after it came out. I've played resident evil 5, fallout, benchmark tests etc... It reads all my ram as well and I have had no issues with it at all, even running dual monitors on my 4890. I use it heavily for my school work and I DIDN'T do anything special during the install, my school provided me the professional edition ISO and all I did was burn it to a DVD. I do have to option boot to get into OS X but that doesn't feel like a big deal...Also using Boot camp

 

[Infrared]

The HFS driver is in the windows/system32/drivers/AppleHFS.sys location on your windows partition. Renaming it will be a simple cure for the problem.

There's a good chance it can be prevented from loading by a change to
the registry. For example, changing the "Start" subkey value from 3 to 0
in this key allows the AHCI driver to be loaded on boot:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci

So, is there a similar key for Apple's HFS driver? If so, I would suggest
experimenting with that. It might be a cleaner solution.

This is a description of what the Start subkey values mean:

[ Quoted From: http://support.microsoft.com/kb/103000 ]

Start     REG_DWORD     Start constant
Specifies the starting values for the service as follows:

START TYPE     LOADER     MEANING

0x0            Kernel     Represents a part of the
(Boot)                    driver stack for the boot
                          (startup) volume and must
                          therefore be loaded by the
                          Boot Loader.

0x1            I/O        Represents a driver to be loaded
(System)       subsystem  at Kernel initialization.

0x2            Service    To be loaded or started
(Auto load)    Control    automatically for all startups,
               Manager    regardless of service type.

0x3            Service    Available, regardless of type,
(Load on       Control    but will not be started until
demand)        Manager    the user starts it (for example,
                          by using the Devices icon in
                          Control Panel).

0x4            Service    NOT TO BE STARTED UNDER ANY
(disabled)     Control    CONDITIONS.
               Manager

 

[gugucom]

1. This is an interesting idea! I will have a look if there is something similar in Windows the next time I boot into Windows.

2. This also sounds interesting for AHCI. I was always changing the value from 4 -> 0 in the registry. Now we probably have to find out if changing from 4 -> 3 will do the trick without patching the MBR.

 

[Nadav35]

who the F cares about this anymore!

Unless you are very keen to run Blu-Ray and boot ODD from SATA the 2008 may be the better deal. It is surely not as fast in cinebench as the W5590s but no slouch either. I was in a position to go for Blu-Ray with Windows which only works with SATA and AHCI. I also wanted only one ODD that would also boot from SATA. This is because I want the space for up to four SSDs in the second optical bay. So I had no alternative but the 2009.

If Blu-Ray and SSDs are not so much a concern to you a high end 2008 should be a very good option. It has EFI64 and will run K64. You also have 6 SATA ports plus 2 IDE. The RAM is better value and over all the value for money is quite high.

THIS WILL BE TAKEN CARE OF IN BOOTCAMP 3.1 BECAUSE OF A NEW FIRMWARE COMING OUT WHICH WILL ALLOW ODD SATA PORTS TO BE BOOTABLE IN NON MAC OS SIDE.

Besides, at this moment I could give a flying ****.

 

[gugucom]

Speculating for Apple to update firmware on two year old machines is like unprotected sex with a hooker. There is a small chance that you will be happy but a wise man will not take chances. If you really need a 4,1 firmware feature there is only one safe way. Buy a MP4,1.

 

[bozz2006]

yep. if you're a wise man you'll make sure your hooker sex is protected. that's the wise thing to do.

 

[Cromulent]

I like the MS concept of running 32-bit apps seamlessly on a 64-bit kernel. That way you can take advantage of the power kernel for stuff that profits from it and still use your 32-bit apps.

I like that better than having to alternatively boot into K32 and K64.

You can run 32 bit apps fine on the 64 bit Mac OS X kernel. Just as you can run 64 bit apps fine on the 32 bit Mac OS X kernel. This is not something that is special about Microsoft.

 

[gugucom]

You can run 32 bit apps fine on the 64 bit Mac OS X kernel. Just as you can run 64 bit apps fine on the 32 bit Mac OS X kernel. This is not something that is special about Microsoft.

That wasn't the point. The point is that any MS 64-bit OS since 2005 and on any 64-bit machine will always run the kernel and drivers with 64 bit while 32-bit apps are also enabled.

Apple will have machines that are 64-bit capable and will never run 64-bit apps (PPC). Then there will be 64-bit capable machines that will only run Microsoft 64-bit kernels. And finally there will be machines which are capable to switch between 64-bit kernel and 32-bit kernel. To me this is confusion and chaos compared to a clear strategy.

 

[Infrared]

That wasn't the point. The point is that any MS 64-bit OS since 2005 and on any 64-bit machine will always run the kernel and drivers with 64 bit while 32-bit apps are also enabled.

Apple will have machines that are 64-bit capable and will never run 64-bit apps (PPC). Then there will be 64-bit capable machines that will only run Microsoft 64-bit kernels. And finally there will be machines which are capable to switch between 64-bit kernel and 32-bit kernel. To me this is confusion and chaos compared to a clear strategy.

Apple should have gone fully 64-bit at the time of the Intel transition
and skipped the Core Duo machines. For kernel extensions that would
have meant PPC->Intel x64 rather than PPC->Intel x86->Intel x64,
a two step update (= more work for developers).