HT3258 OS X Mountain Lion and Parallels

I`ve just installed OS X Mountain Lion and, out of the blue, it turns out that it is incompatible with Parallels? What options do I have? This just makes no sense!

If only I had just those. I'm using Parallels 8 with a fresh reinstall of OSX 10.8.2. Witness:
Dec 18 17:43:24 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.printtool.agent[2625]): Exited: Killed: 9
Dec 18 17:43:24 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2625 [printtool]
Dec 18 17:43:25 173-22-144-11 com.apple.launchd[1] (com.apple.ShareKitHelper[2352]): Exited: Killed: 9
Dec 18 17:43:25 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2352 [com.apple.ShareK]
Dec 18 17:43:26 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.pbs[2344]): Exited: Killed: 9
Dec 18 17:43:26 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2344 [pbs]
Dec 18 17:43:27 173-22-144-11 com.apple.launchd.peruser.89[2312] (com.apple.cfprefsd.xpc.agent[2316]): Exited: Killed: 9
Dec 18 17:43:27 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2316 [cfprefsd]
Dec 18 17:43:27 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.tccd[192]): Exited: Killed: 9
Dec 18 17:43:27 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 192 [tccd]
Dec 18 17:43:27 173-22-144-11 com.apple.launchd[1] (com.apple.xpcd.F5010000-0000-0000-0000-000000000000[179]): Exited: Killed: 9
Dec 18 17:43:28 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 179 [xpcd]
Dec 18 17:43:28 173-22-144-11 com.apple.launchd.peruser.88[173] (com.apple.cfprefsd.xpc.agent[177]): Exited: Killed: 9
Dec 18 17:43:28 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 177 [cfprefsd]
Dec 18 17:43:28 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.accountsd[171]): Exited: Killed: 9
Dec 18 17:43:28 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 171 [accountsd]
Dec 18 17:43:29 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.CalendarAgent[159]): Exited: Killed: 9
Dec 18 17:43:29 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.coreservices.appleid.authentication[158]): Exited: Killed: 9
Dec 18 17:43:29 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 159 [CalendarAgent]
Dec 18 17:43:29 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 158 [AppleIDAuthAgent]
Dec 18 17:43:29 173-22-144-11 com.apple.launchd[1] (com.apple.sleepservicesd[41]): Exited: Killed: 9
Dec 18 17:43:29 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 41 [SleepServicesD]
Dec 18 17:43:31 173-22-144-11.client.mchsi.com WindowServer[72]: kCGErrorIllegalArgument: _CGXRemoveWindowFromWindowMovementGroup: Window not in group
Dec 18 17:43:31 173-22-144-11.client.mchsi.com locationd[2668]: Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatiblity mapping behavior in the near future.
Dec 18 17:43:31 173-22-144-11.client.mchsi.com locationd[2668]: NOTICE,Location icon should now be in state 0
Dec 18 17:43:34 173-22-144-11.client.mchsi.com WindowServer[72]: kCGErrorIllegalArgument: _CGXRemoveWindowFromWindowMovementGroup: Window not in group
Dec 18 17:43:39 173-22-144-11 com.apple.launchd[1] (com.apple.sleepservicesd[2665]): Exited: Killed: 9
Dec 18 17:43:39 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2665 [SleepServicesD]
Dec 18 17:43:41 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.tccd[2666]): Exited: Killed: 9
Dec 18 17:43:41 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2666 [tccd]
Dec 18 17:43:42 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.CalendarAgent[2664]): Exited: Killed: 9
Dec 18 17:43:42 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2664 [CalendarAgent]
Dec 18 17:43:49 173-22-144-11 com.apple.launchd[1] (com.apple.sleepservicesd[2670]): Exited: Killed: 9
Dec 18 17:43:50 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2670 [SleepServicesD]
Dec 18 17:43:52 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.cfprefsd.xpc.agent[133]): Exited: Killed: 9
Dec 18 17:43:53 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 133 [cfprefsd]
Dec 18 17:43:53 173-22-144-11 com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[21]): Exited: Killed: 9
Dec 18 17:43:53 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 21 [cfprefsd]
Dec 18 17:43:58 173-22-144-11 kernel[0]: PRLUFS: starting (version 2010.12.28, May 5 2011, 01:26:58)
Dec 18 17:44:00 173-22-144-11 com.apple.launchd[1] (com.apple.sleepservicesd[2671]): Exited: Killed: 9
Dec 18 17:44:01 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2671 [SleepServicesD]
Dec 18 17:44:07 173-22-144-11 kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
Dec 18 17:44:07 173-22-144-11 kernel[0]: macx_swapon SUCCESS
Dec 18 17:44:11 173-22-144-11 com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[2679]): Exited: Killed: 9
Dec 18 17:44:11 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2679 [cfprefsd]
Dec 18 17:44:11 173-22-144-11 com.apple.launchd[1] (com.apple.sleepservicesd[2682]): Exited: Killed: 9
Dec 18 17:44:11 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2682 [SleepServicesD]
Dec 18 17:44:11 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.cfprefsd.xpc.agent[2673]): Exited: Killed: 9
Dec 18 17:44:11 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2673 [cfprefsd]
Dec 18 17:44:28 173-22-144-11 com.apple.launchd[1] (com.apple.sleepservicesd[2684]): Exited: Killed: 9
Dec 18 17:44:28 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2684 [SleepServicesD]
Dec 18 17:44:29 173-22-144-11 com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[2687]): Exited: Killed: 9
Dec 18 17:44:29 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2687 [cfprefsd]
Dec 18 17:46:49 173-22-144-11 com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[2696]): Exited: Killed: 9
Dec 18 17:46:49 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2696 [cfprefsd]
Dec 18 17:46:51 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.cfprefsd.xpc.agent[2692]): Exited: Killed: 9
Dec 18 17:46:51 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2692 [cfprefsd]
Dec 18 17:46:53 173-22-144-11 com.apple.launchd[1] (com.apple.sleepservicesd[2690]): Exited: Killed: 9
Dec 18 17:46:53 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2690 [SleepServicesD]
Dec 18 17:47:35 173-22-144-11.client.mchsi.com WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
Dec 18 17:47:36 173-22-144-11.client.mchsi.com WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Console" after 1.65 seconds (server forcibly re-enabled them after 1.00 seconds)
Dec 18 17:48:06 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.tccd[2709]): Exited: Killed: 9
Dec 18 17:48:06 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2709 [tccd]
Dec 18 17:48:07 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.CalendarAgent[2708]): Exited: Killed: 9
Dec 18 17:48:07 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2708 [CalendarAgent]
Dec 18 17:48:12 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.pbs[2707]): Exited: Killed: 9
Dec 18 17:48:12 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2707 [pbs]
Dec 18 17:48:16 173-22-144-11 com.apple.launchd.peruser.501[127] (com.apple.accountsd[2706]): Exited: Killed: 9
Dec 18 17:48:16 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2706 [accountsd]
Dec 18 17:48:16 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2703 [xpcd]
Dec 18 17:48:16 173-22-144-11 com.apple.launchd[1] (com.apple.xpcd.F5010000-0000-0000-0000-000000000000[2703]): Exited: Killed: 9
Dec 18 17:48:17 173-22-144-11 com.apple.launchd[1] (com.apple.ShareKitHelper[2702]): Exited: Killed: 9
Dec 18 17:48:17 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2702 [com.apple.ShareK]
Dec 18 17:48:18 173-22-144-11 com.apple.launchd[1] (com.apple.sleepservicesd[2699]): Exited: Killed: 9
Dec 18 17:48:18 173-22-144-11 kernel[0]: memorystatus_thread: idle exiting pid 2699 [SleepServicesD]

Similar Messages

Anyone else having crash problems with mountain lion and parallels 8.0?

Anyone else having crash problems running Mountain Lion and Parallels 8.0 ?

Works OK so far for me. Take you issues to their forums for more direct help. These forums do not provide suport for Parallels.

Mountain Lion and Parallels 7

I am not sure people here can help but it is worth a try.
I upgraded my wife's 13" MBP (mid 2011) to Mountain Lion this morning. Everything went well except Parallels 7 will not launch. It is listed on Parallels' site and on Roaringaps as compatible with Mountain Lion. The dock icon and the icon in the applications folder have a universal stop sign (circle with a slash through it) positioned on them. I get one of two error messages when trying to Launch it. Either it says the program is not supported on this Mac or not supported by this OS. We had Parallels 7 working nicely in Lion.   I did not get a message about incompatble software at the end of the upgrade and I do not have an incompatible software folder at the root level of her home folder.
I've tried the following without success.
     Logged in as another user
     Restarted in Safe Mode
     Reset PRAM
     Pulled all the Parallels plists from the ~/Library/Preferences folder then logged out and back in again
     Searched the Console app for strings containing the word Parallels and there are no results.
I can dowload Parallels 7 again but am not sure what would happen to our Windows 7 files if I repalced it.
Has anyone else experienced this problem with Parallels 7?   I submitted the issue to the Parallels forum but so far there are no asnwers.   This is the fourth Mac I upgraded to Mountain Lion in the past few days and the only one with Parallels 7 on it.
Thanks in advance for any advice.
Jay

I have build 7.0.15052 Rev 710728.
Without being able to launch the app I am not sure how to update it. Can I get the latest version from their web sit and just install it replacing what I have?
Jay

Mountain Lion and Parallels Desktop 7

When I updated My Late 2011 Macbook Air to Mountain Lion, I could not open Parallels Desktop 7 any more.
It would say that it cannot be used with this version of OS X.
Does it mean I have to buy a better version of Parallels?
What should I do?
I dont want to buy it again

roro again,
Reinstalling parallels is a different issue to reinstalling windows on parallels.
Keep you existing virtual machines and when parallels is re-installed use the create virtual machine menu to add an existing machine, when it asks you if this is a copy or you have moved it, reply 'moved' so that windows activation is satisfied that it is the same machine.
If reloading Parallels tools doesn't work for you, or if you can't get Parallels to start at all, I suggest uninstall then reinstall as it will create a clean copy of parallels. You may have to re-register/activate again with parallels but this is free and a relatively small effort.
Message was edited by: roro the hawk

Mountain lion and parallels

since installing mountain lion my Paralles has now stopped how do I get paralles running again

Parallels 7 is supported in Mountain Lion, so you must upgrade to this version

Mountain Lion and Parallel desktop 8

I have parallel desktop 8 installed windows xp in it. Lt me know if it can attract any virus or malware which in turn affect the mac performance as well.

No. Windows malware will not affect OS X, but it will impact on your Windows system. It would be wise to protect your Windows system.

I updated to Mountain Lion and now my Parallels application no longer works; please help! What to do???

I updated to Mountain Lion and now my Parallels application no longer works; please help! What to do???

Make sure you have the latest version of parrallels. Think older versions are not compatible.

Is anyone experiencing problems with opening mission control from the desktop. Running mountain lion with parallels 7 and windows 7

is anyone experiencing problems with opening mission control from the desktop. Running mountain lion with parallels 7 and windows 7

I had been having a similar problem on Lion with Safari pdf files despite downloading the latest Adobe Reader XI.
I would constantly get the same messages - There was an error opening this document. The file is damaged and could not be repaired. And I would get a blank page when I tried to print the pdf if I tried printing from the Safari web page using File - Print from the top toolbar on my laptop.
Then I came across the grey Safari lozenge with action icons.
This allowed me, without downloading the pdf, to print the pdf file direct from the Safari page by using the Print icon on the grey lozenge that appears centrally three quarters down the screen.
Then I discovered that if I save the pdf using the Save icon from this same grey lozenge on the Safari page I can open and print this pdf version from my desktop.
I've tested it with a couple of different pdf files and these methods work using the grey lozenge icons but the same pdfs files don't work using File - Save As on the Tool Bar.

I have just installed the new os x mountain lion - and now i cant enter the parallels desktop 6. does this version support parallels? what can i do? thanx

i have just installed the new os x mountain lion - and now i cant enter the parallels desktop 6. does this version support parallels? what can i do? thanx

You'll need to upgrade to Parallels Desktop 7 to regain compatibility. Good luck....
On Edit: A minute late!

HT4889 Used migration assistant to move from Lion to Mountain Lion and an entire user account did not move over.

The user name (account) was the same on the source and the new computer. Is this why the data could not move over? I did not see this user account in the list of users presented by migration assistant. Thought it was default so that is why it wasn't shown. I can move the data over manually, but this was a surprise. Any feedback on why this happened?

I migrated Office 2011 and other than forcing me to enter the license code again (all 2 million letters of it) everything went OK.
Note that when I tried to open Parallels desktop 6 it wouldn't open and said that it wasn't compatible with Mountain Lion and the icon had a sort of greyed out look. I upgraded to 8 and it started working. I wonder if there is any issue with Office 2008 and Mountain Lion? Probably not but it's a possibility.
You can buy an external superdrive too from Apple. I bought one for my 2010 Air. But CD sharing from another computer should work. I bring it with me when I travel to watch DVDs.

I've upgraded to mountain lion and now cannot use microsoft office--what happened?

I've upgraded to ox Mountain Lion and now cannot use any of my Microsoft office software. What happened?

It appears that you upgraded your computer to Mountain Lion and were using Microsoft Office 2004. In the short term, if you need to open and modify Word files, go to the file in the Finder and Control-Click on it. A menu will come up: go to Open With... and select TextEdit. This should allow you to open, modify and save the file for the short term.
You can do the same trick to open Microsoft Excel files in Preview and print them; but I do not think you can modify them in this way.
Workarounds for Microsoft Office 2004 since upgrading to Mountain Lion:
1. Upgrade to Microsoft Office 2011. This version works in Mountain Lion. However some of your legacy 2004 files may convert badly.
2. Restore the version of OS X that you were using before Mountain Lion.
3. Partition your hard drive and/or attach an external hard drive and install Snow Leopard on it and use the 'dual-boot' method of booting into Mountain Lion when you need it and booting into Snow Leopard when you need to run your PowerPC applications such as Microsoft Office 2004.
4. The method I use, which allows me to run my PowerPC applications concurrently with Lion: I installed Snow Leopard (with Rosetta) into Parallels 7 in Lion:
[click on image to enlarge]
Full Snow Leopard installation instructions here:
http://forums.macrumors.com/showthread.php?t=1365439

I downloaded the recent software update Mountain Lion and now my microsoft word, powerpoint, etc. are no longer supported. Why is this? What can I do?

I downloaded the recent software update Mountain Lion and now my microsoft word, powerpoint, etc. are no longer supported. Why is this? What can I do?

Depending upon how extensive your library of legacy Microsoft Office data files are, you may want to consider continuing to use Microsoft Office 2004.
Microsoft Office's 2011 version is compatible with Lion and presumably either works with Mountain Lion or an update will make it so. The problem with this approach is that Office 2011 will "convert" your earlier data files and there lies the rub! For example, I have the need to weekly open a chart created in Excel 2004, but Excel 2011 trashes the chart in its "conversion."
So I have approached the overall problem differently.
The reason your applications do not work in Mountain Lion is that they were written for the older PowerPC CPU that all Macs used up to 2006. When Apple made its transition to the Intel CPU, they licensed software that they included in all versions of OS X (from Tiger to Leopard and optionally, Snow Leopard) called Rosetta.
Rosetta miraculously allows PowerPC applications to work on the Intel processor transparently; you do not know it is even present.
The problem is that after 6 years of the transition, Apple's license to use the underlying software expired for OS X Lion and all version thereafter (and it is doubtful that the current owner of the software, IBM, would relicense it, even if Apple were inclined to do so).
So for those of use that need to run Lion, I have offered the option to install Snow Leopard (with Rosetta) into Parallels 7:
[click on images to enlarge]
And now Mountain Lion:
Full Snow Leopard installation instructions into Parallels 7 are here:
http://forums.macrumors.com/showthread.php?t=1365439
Snow Leopard is $29 and Parallels 7 is $79 retail (cheaper from competitive sources) and Parallels offers a 14 day free trial of Parallels 7 on their website:
http://www.parallels.com/download/desktop/

I downloaded mountain lion and then the new office suite (word, ppt, excel) but now when I try to display one of my ppt's it says 'ppt cannot open the file...the file may be corrupt, in use, not a type recognized by ppt etc.." how can I fix it?? HELP

I downloaded mountain lion and then the new office suite (word, ppt, excel) but now when I try to display one of my ppt's it says 'ppt cannot open the file...the file may be corrupt, in use, not a type recognized by ppt etc.." how can I fix it?? HELP

Did you try to open teh fle by double-clicking its icon? If the file was made with an older version of Office, you may get that message. Try opeing PP and, from its "File" menu, see if you can open the ppt. I've foundthat often gets around that message and then yo ucan save the file from the newer version.
If that doesn't work, consider asking in the Microsoft Office: Mac forums here:
Office for Mac forums
PowerPoint is not an Apple product and it seems a lot of people around here avoid Office.

Can I purchase Mountain Lion and make a flash drive bootable? I do not want to install it on my Macbook Pro. I have Snow Leopard on my Macbook Pro now, and due to my hard drive needing repair I need to boot off of another source, like my flash drive.

Can I purchase Mountain Lion and make a flash drive bootable? I do not want to install it on my Macbook Pro. I have Snow Leopard on my Macbook Pro now, and due to my hard drive needing repair, I need to boot off of another source, like my flash drive. I am in Paris and my Snow Leopard DVD is in Texas.

Mac OS X has a built-in disk diagnostic and repair program called fsck or file system consistency check. Here’s how to verify and repair your startup disk with fsck. As soon as you hear the startup tone, press and hold Command-S on the keyboard. Keep holding down those keys until you see a black screen with white lettering. This is called “booting into Single User Mode.” As the Mac boots in this mode, the screen reports each step of the process. The line should end in root#. Right after the root# prompt, enter the following: /sbin/fsck -fy
If repairing the disk in single user mode fails, it means one of two things. Either your hard drive itself is failing (a hardware failure), or the directory damage on your hard drive is beyond the capability of the built-in repair procedures in OS X.

HT1338 I updated my MacBook Pro with Mountain Lion and now it is starting slow and opening with some of the programs. How can I fix the problem?

I updated my MacBook Pro with Mountain Lion and now it is slow in starting up and loads a number of probrams. How can I fix the problem?

Have you tried starting in Safe Mode and see if the slowness still occurs?
Restart holding the "shift" key.
(Expect it to take longer to start this way because it runs a directory check first.)
If this works look in System Preferences > Users & Groups > Login items and delete any third party login items (-), you can always add them back with the (+). Also look in /Library/Startup Items. Nothing is put in that folder by default, so anything in there is yours.
Reboot normally and test.

HT3258 OS X Mountain Lion and Parallels

Similar Messages

Maybe you are looking for