Monday, March 17, 2008

MacBook/DVD Player/Leopard/Kernel Panic

Ok, I've been doing some troubleshooting of sorts on this DVD Player kernel panic problem. Along with the crucial RAM, I've also been wondering if Parallels could be causing this problem. Here is what I've done so far:

1. I mounted a DVD image and then started DVD Player, and it played with no problem.
2. I then started Parallels without booting the Vista VM, mounted a DVD image and then started the DVD player, and it played with no problem.
3. I then started Parallels and booted the Vista VM, mounted a DVD image and then started the DVD player -- KERNEL PANIC.
4. Rebooted and mounted DVD image and then started DVD player, and it played fine.
5. Started Parallels, booted Vista VM, then shut down Vista VM, then exited Parallels. I then mounted a DVD image, started up DVD player, and it played fine.
6. Started Parallels, disabled the CD/DVD Drive in Parallels. Next, I booted the Vista VM, then I mounted a DVD image, started DVD player -- KERNEL PANIC.
7. Rebooted and mounted DVD image and then started DVD player, and it played fine.

CONCLUSION: At least on my system, this has to a problem with Parallels, but only if the virtual machine is booted up. Even if I have had the virtual machine booted, if I shut it down and exit Parallels, then the DVD player works as expected. In my opinion, this is a Parallels problem.

My new MacBook

I got a new MacBook one day last week. It was a stock model black one. Has 2GB RAM, 250 GB hard drive and 2.4GHz core 2 duo. I bought a 4GB RAM kit from crucial.com and have successfully added that in. I have also installed a trial version of parallels, and am running MS Vista Business in a virtual machine. I'm trying to decide if it is even worth my while to try out VMWare fusion after this parallels trial is over. If anyone has any suggestions, please let me know.

One problem I'm having is that if I start up DVD player and the disk or image is already mounted, it crashes the computer. I'm wondering if this is a result of the Crucial RAM or if this is some sort of bug.