Parallels 3.0 Not Working in Leopard 10.5

I'm running Leopard on my MacBook Pro and MacPro 8-core using the beta Parallels to run WinXP SP2. It seems to work fine. On my MacBook Pro, I run WinXP in order to use IE 7.0 for financial web sites that don't work with any other browsers and ACT! 2008 Premium for Workgroups as my CRM to run my business. I use Office 2007 for the usual stuff. It all works very well. I'm very happy with my Macs using Parallels to run WinXP and avoid having to buy another Dell PC.

My 2 cents.

Bud James
 
Bud, I must say I envy you. I certainly wish that Parallels had worked out for me. Are you using a Boot Camp partition as your virtual machine, or did you create it within Parallels. From what I've read on both Parallels and VMware forums, support for Boot Camp is much trickier and easier to break.

If you're running a Boot Camp VM, well then I'd be very impressed. This morning, all I tried to do was plug in my Spyder3Elite to calibrate my monitor with Leopard and the computer crashed and Windows XP was completely and utterly corrupt.
 
The thing that's got me furious at this situation is that as oceans777 pointed out, Parallels is still actively promoting Leopard support from it's homepage. Check out this quote from a PCWorld article that's linked on the Parallels homepage:

Ben Rudolph, director of SWsoft (owners of the Parallels brand) said: "We're confident that Parallels Desktop is compatible with Leopard. Performance is great, and core functionality works smoothly. You'll be able to safely upgrade to Leopard when it goes live without worrying that Parallels will work.

"That being said, it's entirely possible that Apple will make some last minute changes in the final 'gold master' build of Leopard that may cause some minor bugs to pop up in Parallels. If that happens, we'll release a free, automatic update to account for them very soon after Leopard's launch."
Click to expand...

That article in full is here.

Well, I followed this recommendation from Parallels, and as a result, I've rebuilt my computer twice. Build 5160 is NOT Leopard-compatible, especially with Boot Camp, and I really think that Parallels should come clean. Just because folks that are crashing and burning is a minority doesn't mean that they're compatible. Parallels is not being honest, and it's costing their customers, time, frustration, and data loss.
 
I am on a direct first name basis with customer support of my never ending XP unexpected quit problems on my MacBook Pro! I have sent crash longs, reviewed installed apps, etc.
Click to expand...
I'm in the same situation. Question: Do you run multiple VMs at the same time? For example, are you running two versions of XP simultaneously, or one version of XP and one version of Windows 2000? Or XP and Vista at the same time? My experience is that the sudden "lightning crash" problems always happen when more than one VM is open. The same applies to the spontaneous blue screen crashes in Vista while Vista is just sitting there doing nothing, with no programs running -- this too only happens when I have another VM open at the same time (usually XP). It never happens when the Vista VM is running on its own.

I'm still on Tiger by the way -- I wouldn't even consider switching to Leopard before the Parallels issues on it are officially solved.
 
If you're running a Boot Camp VM, well then I'd be very impressed. This morning, all I tried to do was plug in my Spyder3Elite to calibrate my monitor with Leopard and the computer crashed and Windows XP was completely and utterly corrupt.
Click to expand...
So would I. In my experience there is effectively no support for running Boot Camp partitions in a Parallels VM. A function that does not work is not there and should really be ignored. Parallels has completely trashed three Boot Camp partitions for me and now I no longer have one. Also, even when the Boot Camp VM worked it was unusably slow, even on a Mac Pro with 5GB of memory. Apparently (I can't confirm this but I have seen it claimed several times) at least part of the problem is that Parallels actually changes the Windows code on the Boot Camp partition to "play nice" with Parallels, and some users have suggested that this then causes problems in Windows
 
Hello all,

Please, pay attention to this official announcement from Parallels published on the 31 of October.

Khoji, please reduce your Mac RAM to 4 GB. Maximize manually the amount of memory for Parallels (Parallels Desktop -> Preferences -> Memory) and put check at Enable virtual memory preallocation. Reduce RAM for your VMs (Configuration Editor -> Memory). The total amount of RAM of opened VMs must not exceed the RAM allocated to Parallels.

Could you give more information on the way your Boot Camp partitions trashed?

Best regards,
Xenos
 
Xenos said:
Please, pay attention to this official announcement from Parallels published on the 31 of October.
Click to expand...

I read that before upgrading to Leopard. You recommended Build 5160, which just doesn't cut it with Leopard (at least when using Boot Camp). I followed every bit of advice in that posting. What brought by Boot Camp install to its knees was not any of those "known issues".

Xenos said:
Could you give more information on the way your Boot Camp partitions trashed?
Click to expand...

This one should be easy to produce. MacBook Pro running Windows XP SP2 Boot Camp partition as the VM. I installed the calibration software for the Spyder3Elite monitor calibration system. I calibrated my monitor for Leopard first, then unplugged the tool via USB. I then booted Parallels and my VM and installed the Spyder software in Windows. I restarted Windows (as instructed by the software) and then plugged in the Sypder3Elite. BOOM! Instant crash and corruption (the hal.dll issue as stated earlier in this thread). Looks like your test dept. better invest in a Spyder3Elite. They're $279, which is a bargain considering reinstalling Windows on my MacBook cost me more than that in my time.
 
jrotondo, please try the following:
In Configuration Editor go to Hard Disk 1, Advanced tab and click Clear.
Waiting for the feedback.

Best regards,
Xenos
 
Sorry Xenos. I no longer have Parallels loaded on the machine. I've rebuilt too many times. I'm running a very stable VMware now.

Good luck obtaining Leopard compatibility. I'm sorry your product did not fit my needs.
 
Tired of waiting. Dumping parallels for VMWare. Still can't use multi-monitor and no one has provided any timeline on when this will be resolved. We're now in December running a (very buggy) Sept release.
 
reinstalled parallels a few days ago and reverted to the 5160 build; working pretty well, froze only once in about 15 tries.
 
Has this multi-monitor/graphic card issue been fixed? I have installed the latest build 5584 and it crashes.
 
So, What is the fix?

rempe00 said:
I just installed Leopard today and now Parallels quits unexpectedly whenever I try to launch it. I have restarted my computer and so far have been unable to launch Parallels since I upgraded to Leopard.
Click to expand...


I have had the same problem start last night with Leopard and Parallels. I have tried the Parallels FAQ regarding the repair disk permission, uninstalling and reinstalling. This did not work. What is the fix to this problem between Leopard and Parallels?
 
Hello all,

Moas, the multi-monitor/graphic card issue is not fixed yet. However this problem is of high priority for Parallels developers and the fix is going to be included in the next build. We bring our apologies for the inconvenience caused.

Kmc7e, what build are you using? Please check. If it is 5584, could you describe the issue in details?

Best regards,
Xenos
 
Parallels Often Doesn't Alunch

I'm having the same problems as others. New MacBook Pro, Leopard, Parallels Build 5584 (latest) reinstalled after original 3.0 disk uninstall. Sometimes Parallels launches and works fine. Later on launch I get an immediate:

The application Parallels Desktop quit unexpectedly.

Relaunch, Reset & Relaunch, and Restart do nothing. Usually Shut Down and reboot will let it work again. But once I close down Parallels, it won't work again that session.
 
Hello Pdodd,

This is the first report we get on 5584 unexpected quit. Could you please provide us with the following information:

1. Open Console (Applications -> Utilities), Clear the display (Clear button on the top);
2. Launch Parallels.

We would like to see the output of the Console after Parallels unexpected quit. Please copy all the data you will get in the display and paste it in you next post.

Best regards,
Xenos
 
Console Output on Unexpected Quit

2/4/08 10:45:26 AM com.apple.launchd[1] (com.apple.launchd.peruser.423) Throttling respawn: Will start in 10 seconds
2/4/08 10:45:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2628]) getpwuid("423") failed
2/4/08 10:45:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2628]) PID 154 "lsregister" has no account to back it! Real/effective/saved UIDs: 423/423/423
2/4/08 10:45:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2628]) PID 138 "OpenBase" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:45:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2628]) PID 78 "openinfo" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:45:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2628]) PID 77 "openexec" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:45:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2628]) PID 53 "openmonitor" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:45:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2628]) Exited with exit code: 1
2/4/08 10:45:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423) Throttling respawn: Will start in 10 seconds
2/4/08 10:45:36 AM [0x0-0x476476].com.parallels.desktop[2629] QFSFileEngine::open: No file name specified
2/4/08 10:45:38 AM [0x0-0x476476].com.parallels.desktop[2629] Parallels Desktop 3.0 critical error! Send log file ( /Library/Parallels/bugreports/parallels-fault-104538.040108.2629.log ) to [email protected]
2/4/08 10:45:43 AM com.apple.launchd[71] ([0x0-0x476476].com.parallels.desktop[2629]) Exited abnormally: Bus error
2/4/08 10:45:46 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2635]) getpwuid("423") failed
2/4/08 10:45:46 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2635]) PID 154 "lsregister" has no account to back it! Real/effective/saved UIDs: 423/423/423
2/4/08 10:45:46 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2635]) PID 138 "OpenBase" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:45:46 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2635]) PID 78 "openinfo" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:45:46 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2635]) PID 77 "openexec" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:45:46 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2635]) PID 53 "openmonitor" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:45:46 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2635]) Exited with exit code: 1
2/4/08 10:45:46 AM com.apple.launchd[1] (com.apple.launchd.peruser.423) Throttling respawn: Will start in 10 seconds
2/4/08 10:45:56 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2639]) getpwuid("423") failed
2/4/08 10:45:56 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2639]) PID 154 "lsregister" has no account to back it! Real/effective/saved UIDs: 423/423/423
2/4/08 10:45:56 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2639]) PID 138 "OpenBase" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:45:56 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2639]) PID 78 "openinfo" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:45:56 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2639]) PID 77 "openexec" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:45:56 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2639]) PID 53 "openmonitor" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:45:56 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2639]) Exited with exit code: 1
2/4/08 10:45:56 AM com.apple.launchd[1] (com.apple.launchd.peruser.423) Throttling respawn: Will start in 10 seconds
2/4/08 10:46:06 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2641]) getpwuid("423") failed
2/4/08 10:46:06 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2641]) PID 154 "lsregister" has no account to back it! Real/effective/saved UIDs: 423/423/423
2/4/08 10:46:06 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2641]) PID 138 "OpenBase" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:06 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2641]) PID 78 "openinfo" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:06 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2641]) PID 77 "openexec" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:06 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2641]) PID 53 "openmonitor" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:06 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2641]) Exited with exit code: 1
2/4/08 10:46:06 AM com.apple.launchd[1] (com.apple.launchd.peruser.423) Throttling respawn: Will start in 10 seconds
2/4/08 10:46:16 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2644]) getpwuid("423") failed
2/4/08 10:46:16 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2644]) PID 154 "lsregister" has no account to back it! Real/effective/saved UIDs: 423/423/423
2/4/08 10:46:16 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2644]) PID 138 "OpenBase" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:16 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2644]) PID 78 "openinfo" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:16 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2644]) PID 77 "openexec" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:16 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2644]) PID 53 "openmonitor" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:16 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2644]) Exited with exit code: 1
2/4/08 10:46:16 AM com.apple.launchd[1] (com.apple.launchd.peruser.423) Throttling respawn: Will start in 10 seconds
2/4/08 10:46:26 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2646]) getpwuid("423") failed
2/4/08 10:46:26 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2646]) PID 154 "lsregister" has no account to back it! Real/effective/saved UIDs: 423/423/423
2/4/08 10:46:26 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2646]) PID 138 "OpenBase" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:26 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2646]) PID 78 "openinfo" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:26 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2646]) PID 77 "openexec" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:26 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2646]) PID 53 "openmonitor" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:26 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2646]) Exited with exit code: 1
2/4/08 10:46:26 AM com.apple.launchd[1] (com.apple.launchd.peruser.423) Throttling respawn: Will start in 10 seconds
2/4/08 10:46:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2648]) getpwuid("423") failed
2/4/08 10:46:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2648]) PID 154 "lsregister" has no account to back it! Real/effective/saved UIDs: 423/423/423
2/4/08 10:46:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2648]) PID 138 "OpenBase" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2648]) PID 78 "openinfo" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2648]) PID 77 "openexec" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2648]) PID 53 "openmonitor" has no account to back it! Real/effective/saved UIDs: 0/423/423
2/4/08 10:46:36 AM com.apple.launchd[1] (com.apple.launchd.peruser.423[2648]) Exited with exit code: 1
 
Hello Pdodd,

Thank you very much for the information. I am sorry for the answer delay.

Please, could you provide more data for analysis?

Go to /Library/Parallels/bugreports, make a zip file including all the files from that folder and send it to me.

Thank you in advance!

Best regards,
Xenos
 
Similar issue but no crash

I have a user who has a Mac Book with 10.5 on it, running Parallels. Anytime the user starts the vm, the screen where the Windows XP should be running is just a blank screen, no error, no nothing. In the Console messages, all I see is "QDSFileEngine::Open: No file name specified" when the program starts. I have installed MacFuse, but that has not helped, the version of PD is 3.0 build 5584.

Thank you
 
You must log in or register to reply here.
Back
Top