||Parallels Desktop 3.0 for Mac Run all the applications you need without switching between Windows and Mac OS X! New features include: 3D Graphics Support, SmartSelect, SnapShots and Security Manager to truly enjoy the best of both worlds.
"If your goal is tight integration between one or more Windows applications and Mac OS X, Parallels is the clear winner when running either XP or Vista." --MacTech Magazine
Updated October 7, 2007
On this page:
If you're having a cross-platform problem specific to Intel-powered Macs
Other MacWindows pages about Intel Macs:
For the most part, Macs with Intel processors inside behave the same as PowerPC Macs when it comes to cross-platform issues, such as functioning on Windows networking or sharing files with PCs. The Intel Powered-Macs have no built-in problems, nor do they have any advantages over PowerPC Macs for these types of activities. For the most part, Mac OS X interacts with Windows networks and files in the same way, regardless of the processor.
Occasionally, however, we de receive reports of a problem that is specific to Intel Macs. This page covers these issues. At this time, we only know of one issueand the fix.
This page does not cover running Windows on Intel Macs, such as with Boot Camp or Parallels. For those topics, see our special report page Running Windows on Intel Macs.
Intel Mac MS UAM doesn't work with Windows Servers
The first group of messages report this problem, in which Intel Macs are unable to connect to Services for Macintosh on Windows Servers using the Microsoft UAM. After that are suggested workaround. There is also a .
January 18, 2006
We have discovered that our new Intel based Macs will not connected to our Windows 2003 Server. The Microsoft UAM is not compatible with the new OS version.
February 13, 2006
Jason Martinez is having the previously reported problem of non-working AFP UAM on Intel Macs:
The first iMac Duo Core appeared at our school last week and we are having problems with them accessing our Windows 2003 file server. I can bind the machine to the windows domain and use it to authenticate my UAM login, but I cannot connect to the file server. When we try to connect we get "Connection Failed; error 2".
February 20, 2006
Doug Ward responded to our recent reports of the AFP Microsoft UAM not working on Intel Macs.
We are also having this problem at a small college using Windows Server 2003.
March 3, 2006
Alexandre verifies previous reports of the Microsoft UAM on Intel Macs not being able to connect to Services for Macintosh:
We have the same problem on Intel iMac trying to connect to our Windows 2000 Advanced Server " error 22." It works without the UAM package but then you are not allowed to have long passwords.
March 9, 2006
Byron Watanabe confirms the problem with Intel Macs not being able to run the Microsoft UAM for Services for Macintosh file sharing. He also found a case when signing on with the UAM, in cleartext, didn't work either. He found a way around the latter problem:
I just wanted to add my observations on the problem with the UAM. After trying several different methods, I have found that if the Windows 2003 server is raised from the default Server 2000 native or mixed level to Windows Server 2003 domain functional level you can't connect to the server even if it is setup for clear text. You can see the netlogon and Microsoft UAM Volume but none of the shares.
I then pointed the Intel Mac to another Windows 2003 Server that was still set at the default Windows 2000 mixed domain functional level and I could connect to the shares on that server without the MS UAM software.
March 15, 2006 -- T. Reid Lewis of Group Logic tells us that replacing Services for Macintosh with solution to the problem described below gets around the incompatibility that the Microsoft SFM UAM has with Intel Macs:
I read your story “Microsoft may not fix UAM incompatibility with Intel Mac “ with interest.
Your readers should know that there is an solution. Mac OS X, on both PowerPC and Intel, supports encrypted logins with two built-in UAMs provided by Apple, DHX and Kerberos.
ExtremeZ-IP File Server supports both Apple provided secure UAMs offering a secure alternative to SFM for Intel Macs as well as many other advantages.
ExtremeZ-IPThe Solution: OS X 10.4.6 includes UAM that works with Intel Macs
June 9, 2006 -- Michael Perbix reports that a Microsoft UAM that comes with Mac OS X 10.4.6 works on Intel Macs to connect to Services for Macintosh on Windows servers:
It has been mentioned that the MSUAM to use Services For Macintosh on Windows 2000 servers does not work on Intel Macs. Interesting note in the 10.4.6 Server Knowledgebase is that Apple included an enhanced MSUAM for Intel machines.
There was no mention in the 10.4.6 client update, however, it does indeed work, for BOTH PPC and Intel machines. If you go to /Library/Filesystems/AppleShare/Authentication and remove the MicrosoftUAM.uamx you can STILL connect to SFM shares set to REQUIRE MSUAM.
If you use the GO and CONNECT TO SERVER and type in the server name, you are presents with a normal AppleShare authentication dialog. However, I can confirm that I am connecting in the same manner as MSUAM....since the server does NOT support connections otherwise.
June 12, 2006
Steve Baxter verified the tip:
I noticed a couple of days ago that I could now connect to AFP shares on our W2K servers from my Intel iMac - we require the UAM, so this definitely works!
June 26, 2006
We have tried to connect an Intel-Mac as well as the G5-iMac (both with 10.4.6) without the origin MS-UAM to the W2K-Domain-Server. We have not been that lucky! The G5 Mac will connect only if MS-UAM is installed, the Intel Mac shows the AppleShare authentication dialog even if the MS-UAM is installed. In any case the connection between the Intel Mac and the Windows 2000 Server doesn't work.
If you've tried this fix
April 18, 2006 -- When Hansueli Schiller updated his Intel-powered iMac to Mac OS X 10.4.6, he could no longer connect to his Windows server because of an Ethernet duplex problem. The workaround was to replace the 10.4.6 Ethernet driver with the 10.4.5 version:
We work in a Windows 2000 environment using an Intel iMac (with firmware update 1.0). The network connection worked well with manual Ethernet settings of 100BaseTX Full-Duplex. Our switches are set to full duplex and we are not authorized at all to change this setting.
After the 10.4.6 Update, the network-connections of the Intel iMac were completely broken. To get any connection we had to change the settings to autosense or half-duplex which made the network connections really SLOW. We were not able to communicate with our Servers at an appropriate speed.
We could fix the problem on our Intel iMac: Full Duplex can be enabled by replacing the new version of the networking extension, which includes the Ethernet driver with an older version of the same extension. E.g. the one that came with OS 10.4.5.
- Remove the newer IONetworkingFamily.kext from this location: System/Library/Extensions/ (but keep it safe for further use). If you are asked by this procedure for the admin-password, type it.
- Install the older IONetworkingFamily.kext to this location: System/ Library/Extensions/. If you are asked by this procedure for the admin- password, type it.
- Use Disk Utility to repair the admission-permissions on your hard drive.
- Restart the Mac.
- Open the network settings and set the parameters for the Ethernet manually to 100baseTX - Full Duplex. Activate this setting!
I do not like this fix, but it works! I hope I will not have any problems with system-updates in the future. I really hope Apple will fix this problem soon.
I read your post about the 10.4.6 update causing an Ethernet Duplex problem on an Intel iMac. I'm experiencing the same phenomena on an iMac in our department. Is the solution still to roll-back the driver to the 10.4.5 version?
March 23, 2007
At this point, it is. In fact, another reader,PolinkoJack Crabb, just wrote to verify this fix:
We experienced this problem and your solution worked.
March 23, 2007
Peter Herrmann says this approach doesn't work on Mac Pros:
I have also experience the problem with manual config of network setting with Tiger, beginning with 10.4.6. As of 10.4.9, it still is not fixed! I have also discovered that the workaround, going back to the 10.4.5 network extension, does not work with the mac pro duel network cards. I also called Apple about it last week.
If you've seen this problem or the workaround
This a problem reported by many readers in August of 2006 with then-new MacBook and MacBook Pros. The MacBook would shutdown while running Windows in Boot Camp. Later reports noted that it could happen without running Boot Camp. It was latter determined that the problem was one of defective batteries in the MacBooks. The MacBook's energy conservation measures would not kick in while running Windows, creating a lot of heat that the defective battery was sensative to.
August 28, 2006
Matthew Yezuita’s MacBook Pro is shutting down unexpectedly when running Boot Camp:
Intel MacBook pro shuts down randomly when loading Windows and stops seeing USB devices at random times, etc.
When booting from Windows XP a MacBook pro using Boot Camp, sometimes Windows will start to load and then the computer will completely shut down for no reason.
Other times, when Windows is running, it randomly will stop "seeing" the USB keyboard or other USB device and/or when a USB device is accessed (like my scanner in Photoshop), other USB devices will stop being "seen" by Windows or computer will just shut down randomly or hang and stop responding.
If you’ve seen this issue
" + contact + "MacBook shutdowns may not be limited to Boot Camp
August 29, 2006
Several readers say that the , which we reported yesterday as a problem with Boot Camp, also occurs without Windows.
Grant Davis sees the problem on machines without Boot Camp:
We've got a MacBook that just shuts down--dies completely--whenever it feels like it. Restarts OK and runs for irregular periods. We've upgraded to OS 10.4.7 and the Firmware upgrade that stops the Mooing fan but it still does it: pow, gone black screen. No Boot Camp installed either so it sounds like an odd hardware fault with some machines.
Bob Savage sees it with both Windows and Mac OS X on Intel Macs, but Windows is worse. He also finds that battery heat prevents Windows from loading:
I am seeing the problem with shutdowns with MacBook Pro. I also have Boot Camp and the problem might be worse when booting into Windows, but it seems to occur when OS X is loaded as well (although it takes longer to occur). There might be a connection to heat, but I don't think it has anything to do with the battery. I've noticed that, if I leave the notebook plugged in (but not booted up) the rear of the computer (behind the battery, and close to the hinge) gets and stays hot. In this condition, Windows cannot successfully load, however unplugging the computer for a while allows it to cool off. I can then use it for some time (even under Windows) without the problem.
I haven't worked out the timing on everything (the problem seemed to get worse, but now that I think there is a connection to being plugged in, I would want to observe in relation to a COLD start).
Pete Lavergne thinks it might be bad RAM:
Run the Apple hardware test for the memory.
Richard Lorrain sees it only with Boot Camp, as did yesterday’s reader:
I do experience the same thing with boot camp. Unfortunately, I'm not a geek, I can't help you guys. Glad I am not the only one.
If you’ve seen this issue
MacBook shutdown problem widespread;
Apple replacing logic boards, some readers pointing to battery and heat.
August 31, 2006
We’ve received dozens of reports from readers about the problem of " + contact + ". Many are having Apple replace their motherboards, some more than once. Other readers report that the problem is related to batteries and battery heat, or that replacing the batteries fixes the problem. The link to heat could explain why some readers found the problem worse with Boot Camp, since Windows does not have the power management for Apple hardware that Mac OS X does.
David Mydans says “My MacBook is in the hospital getting a new Logic Board.”
Todd Jackson has had two logic boards and a slight alteration:
My MacBook has had two new logic boards in attempts to fix the random shutdown issue. With this last repair, the technician incorporated a possible fix having to do with a spacer in the case (I think first reported on Macfixit.) I pick it up today and we'll see if it works.
Diego fixed the problem with a new, cooler battery:
I was having the same problem until I replaced the battery, now it's cooler and has not shut down without warning in over a week. With the old battery it shut off completely 4 to 6 times a day.
Chris Crews found burnt plastic on his battery:
Got the same problem, no Boot Camp or Windows ever installed on this one. With all the battery news floating around out there I decided to check the battery's physical condition after one of these shutdowns and found the pungent odor of burning plastic along with several brown spots that look like arc burns between the case and battery.
I was wondering if any other MacBook owners could check for these symptoms after an unexpected shutdown.
Brandon Quintana had his battery replaced, but is not having problems with Parallels Desktop:
I have one of the black MacBooks that just came back from repair…The fan would spin up and the machine would shut down. My machine did not have the Mooing as some other people have experienced but I installed the Firmware update anyway. I was going to backup the machine before sending it into repair but then the battery stopped charging and the video died so I had the local Apple Store reformat the drive before sending it in. I received the machine yesterday and they had replaced the heatsink and gave me a new battery.
The machine appears to be functioning properly, but now I am having trouble installing Parallels Desktop with Windows XP. I think it is an issue with Parallels but at this point I'm not really sure.
Vincent Borrel in Paris sees the problem when running on battery power:
I experienced them two or three times, on battery. It seems it appears after some inactivity. It may be hardware related, since the SMC decides when the processor is not doing much and tries to put it to sleep.
I only use Mac OS X. Latest firmware and SMC. It didn't appear since I'm on 10.4.6, but may be unrelated to the change.
Moreover, I have a slight buzz, and I think I saw somewhere (not sure) that it could be related to the same problematic motherboards that exhibit this sound. I'm waiting 3 more weeks then sending the book for a motherboard exchange.
I began to notice intermittent shutdowns Friday, 8/25. Perhaps two occurred with an hour or two in between. Starting the next morning the shutdowns began in ernest. I began to backup everything manually, directory by directory, as shutdowns would occur with such frequency that the entire backup process would never finish. By the time Apple had been called the shutdowns had occurred about 10 - 15 times over 3 hours.
The machine left Las Vegas that afternoon 8/26, for Memphis. I received it the following Tuesday, 829. The trackpad had been replaced as requested. Nothing else had been touched.
I am presently using the machine and hope to get back to work without incident. We shall see.
Matthew started a MacBooks shutting down at random problem.
blog on the MacBook Random shutdownCisco VPN client kernel panics on Mac Pro and other Intel Macs
A number readers report this problem.Readers identified the Cisco kernel extension as the incompatible piece causing the problem; removing the extention file before shutting down will prevent a kernel panic. Another reader showed that the incompatibility began recently with Mac Pro system software. However, readers are now reporting that the problem applies to other Intel-powered Macs as well, those with newer builds of Mac OS X.
September 25, 2006
Michael Curtis reports that the Cisco VPN Client causes Mac Pros to crash:
We have just had three Mac Pros delivered. I cloned two of them from the first one and then noticed that these two would kernel panic on a restart and not shutdown, they would immediately reboot.
I then had to install the Cisco VPN Client (4.9.00) on the first one and that did the same thing. I had already installed it on the other two.
September 27, 2006
Glenn Reid has a theory
We use the Cisco VPN client, and when I installed it I noticed that it was adding a kernel extension. It might be necessary to do a full install of the client, rather than to "clone" it, since it may have some logic in the installer to install something different in the Intel case.
It's also possible that the kernel extension simply doesn't work on the Intel-based Macs. I haven't tried it yet, and since I saw your post I'm afraid to try it with my new Mac Pro.
October 2, 2006
Fran Hopp, who sees the problem with an iMac, discovered that it problem is caused by the Cisco VPN Client kernel extention:
We just received a 20" Intel iMac. After installing Cisco VPN Client 4.9.00.0050 a kernel panic was generated on every shutdown. Removing the added kernel extension from System/Library/Extensions eliminated the kernel panic. Reinstalling again produced the problem.
October 2, 2006
Fredrich Dengel also found that Cisco kernel extension file is incompatible:
I can confirm shutdown panics on my 24" Duo 2 iMac using the universal Cisco VPN client software. The application works well, building a stable tunnel, etc.
However, the Cisco VPN kext file in the system/extension folder causes a shutdown panic that can be avoided by removing the file if you must shutdown or restart. A panic will also ensue if you try to reinstall/upgrade the app without removing the offending kext file first.
The only solution I have found is to not shutdown or restart your computer with removing the extension. Since I rarely shutdown my computers, I probably would have never realized the source of the problem had I not coincidentally installed the VPN client and then updated airport security (requiring a shutdown or restart) on my new computer (day one) within a time frame that allowed rapid conclusions to be made from very limited trouble shooting.
October 2, 2006
Michael Curtis, who first reported the problem, responded to another reader’s note from Wednesday:
A response to Glenn Reid. The third Mac Pro machine wasn't cloned and was a full install. It does work fine, but just messes up the shutdown and reboot. It also didn't break my MacBook Pro.
October 2, 2006
Brad Allen says that the incompatibility began with a recent change to Apple system software.:
We first saw this problem on a MacPro, but hadn't seen the problem on earlier Intel Macs such as MacBook or MacBook Pro. So, I thought the problem must be related to the new Core 2 chips. However, we tried cloning the OS from a Mac Pro tower to a MacBook Pro, and the problem followed the cloned software to the MacBook Pro. That points to the software that shipped with the Mac Pro tower.
When we used an older config image created for the MacBook Pro (from the MacBook Pro install DVD) on the same MacBook Pro hardware, the MacBook Pro had no more kernel panics with the CiscoVPN client installed.
So, it looks a lot like the incompatibility was introduced with the Mac Pro system software.
October 2, 2006
Wayne Wilkin saw the problem with iMacs:
I, too, have experienced the same using the Cisco 4.9 client on the new iMac Duos. Same exact symptoms.
October 2, 2006
I also ran into the Cisco VPN client crashing the MacPro towers. Fortunately, these machines are to be deployed on campus so it is not an issue right now. This issue I have is that the Mac Pro Towers die (multi-lingual "You must reboot by pressing power key" crash screen) on shutdown or reboot.
October 2, 2006
I installed the Cisco VPN client (4.9.00.0050) and it consistently crashed the Mac Pro on attempts to shutdown or restart. I had to boot without extensions and then ran the uninstaller. It's a pity as I really need VPN access to my university for my work.
The Fix from Apple
October 6, 2006
Fredrich Dengel reported that the 10.4.8 update fixes the .
If you’ve seen this
October 6, 2006
This weekend I upgraded the Mac Pro to 10.4.8 and installed the firmware updates. I reinstalled the VPN software and so far, I haven't experienced any kernel panics.
October 6, 2006
10.4.8 seems to have fixed this issue. I removed the the CiscoVPN folder from system/library/startupitems so that I could restart or shutdown my machine before I installed 10.4.8. I restarted. Did a permissions check. Install 10.4.8 and the re-installed the Cisco VPN client and now it works fine.
NOTE: This problem has been identified as not specific to Intel-Macs. Nor is it specific to any server platform. Therefore, this set of reports has been moved to our .
Read this report
Read current MacWindows news here.Word crashing Intel Mac minis
Wednesday, October 17, 2007
Derek Smith reports of a problem with Word and Mac minis:
We have a slew of Dual-core Intel Mac minis in a lab and in two classrooms that are throwing panic crashes when Word prints.
This link gives me a clue as to what is going on here:
Do your readers have any hints or tips on how to fix this problem?
If you've seen this problem