Truly Serious Bugs Fixed in RC2?

D

DarylF2

Member
I'm seriously considering moving my work (professional Visual C++ 6) development to my 20" iMac 2.0GHz Core Duo running Parallels Desktop (pre-ordered on 4/9). I keep extremely good backups, and will be sync'ing with my old work PC on a daily basis.

Still, I don't want to make this move until Parallels Desktop is ready.

Has RC2 fixed the problems with Macs spontaneously restarting, and occasionally corrupting disks, seen with the early beta versions? I don't mind occasional application crashes or USB problems, but I don't want to move to Parallels until these more serious stability problems have been resolved.

Has ANYONE had such a problem with RC1 or RC2? If so, can you provide some details as to what you were doing that might have triggered the problem?

Thanks in advance!
 
Works for me with some caveats...

DarylF2 said:
I'm seriously considering moving my work (professional Visual C++ 6) development to my 20" iMac 2.0GHz Core Duo running Parallels Desktop (pre-ordered on 4/9). I keep extremely good backups, and will be sync'ing with my old work PC on a daily basis.
Click to expand...

I'm doing this (with daily backups as well!) for about two weeks now with a XP VM. I started with Beta6 and yesterday moved to RC2.

I had not the slightest problem with disk corruption. I'm still working with the same images I set up about 4 weeks ago (then, on Parallels for Win on a XP box, because my MBP hadn't arrived).

There are however a number of situations that crash the VM or the entire Mac, see below. These are annoying, but so far they all have a reason that can be avoided (at least for me). I just spent a day with heavy development and compiling simultneously in a XP VM and a Debian Sarge VM, both networked and heavily sharing files with each other, with Mac OS X and with external LAN servers, using CIFS/SMB. Plus Mac X11 running and communicating with the Linux in the VM. Not a single problem with all this! :)

The things that more or less repeatably cause crashes are:

1) Choosing "New Window..." in a VM which is already running (which means I need to create the needed VMs before starting them). This fully crashes the Mac immediately.

2) Changing "Network Location" when a VM is running. This does not crash immediately, but repeatably at the next sleep or wakeup of my MBP. Without location switch, sleep and wake works fine for me with running VMs.

3) Sometimes, accidentally switching to Property Page View (Cmd-G) when a VM is in full screen. This normally gets a black screen, but usually no crash - exiting full screen with Ctrl-Alt recovers the VM.
 
Its been my experience with the last beta, RC1, and now RC2 that if you stick to straight development stuff (I use Borland Delphi) then you will have no issues. Backups are a GREAT idea and have a way to recover too. But I've not had a single KP in a LONG TIME.

M
 
luz said:
1) Choosing "New Window..." in a VM which is already running (which means I need to create the needed VMs before starting them). This fully crashes the Mac immediately.

2) Changing "Network Location" when a VM is running. This does not crash immediately, but repeatably at the next sleep or wakeup of my MBP. Without location switch, sleep and wake works fine for me with running VMs.

3) Sometimes, accidentally switching to Property Page View (Cmd-G) when a VM is in full screen. This normally gets a black screen, but usually no crash - exiting full screen with Ctrl-Alt recovers the VM.
Click to expand...

1 and 3 are already fixed. 2 is a little bit more difficult - we working on it.
 
You must log in or register to reply here.
Back
Top