Best Answer, Major breakthrough! I have it up and running on his Mac now:-) I created a 'raw' 10.5 virtual machine from the original retail DVD as previously explained.

UpdateStar is compatible with Windows platforms. UpdateStar has been tested to meet all of the technical requirements to be compatible with Windows 10, 8.1, Windows 8.

I then migrated his user (documents, applications etc.) to the VM, and was able to login. Everything worked. Made a VMware snapshot. I then started a cyclic process of updating Mac OS, testing and creating a VMware snapshot. I went from 10.5 to 10. Business Knowledge For It In Trading And Exchanges Pdf Printer. 5.1, 10.5.2, 10.5.3, 10.5.4, 10.5.5 10.5.6 - and then it crashed with the above mentioned (kernel) panic. I restored to the 10.5.5 snapshot, and tested that everything worked. And I'm gonna leave it there.

I'm not quite sure exactly what happened from 10. Manipuri Thabal Music Track. 5.5 to 10.5.6 that would cause this error - except that the darwin kernel was upgraded from 9.5 to 9.6. The generel Mac OS X 10.5.6 update description doesn't ring a bell.

Anyway - thank you for the time you spent here. It's a great website! Take care:-). I have a problem that is driving me crazy: My retired uncle had a Macbook Pro (early 2008), which started failing and eventually died. He was running: Mac OS X 10.5.8 (Leopard) – the reason for this being, that he was still using a lot of PowerPC applications, and 10.5.8 was the last version supporting that VMware Fusion 1.1.3 – in order to run Windows XP I managed to rescue his old (also failing) harddisk, and created a 200GB diskimage file.

We then bought a new Macbook Pro (late 2013) – 15 inch with Retina display. And of course: OS X 10.9.1 (Mavericks).

I installed VMware Fusion 6.0.2 on this and transferred his Windows XP without any problems. The task would then be to virtualize his old Mac on the new one! And this is where the challenges began! I have a Macbook Pro myself (early 2011) – 17 inch with OS X 10.9.1 and VMware Fusion 6.0.2. So I thought I would just create the VM on my Mac and then transfer it to his new Mac. I tried different solutions until I finally found the unlocker 1.2.0 here – thank God for that!

So I got his old Mac up and running as a VM. Simple task now: Run the unlocker 1.2.0 on his Mac, transfer the VM files - peace of cake. During boot it ended up with this error. It didn’t help to restart, and I haven’t been able to locate the cause of this. I compared vmware.log on his and my system to find where it started differing. Being different hardware there would be difference, of course, but up until the two lines below it was basically the same: 2014-01-08T19:59:45.492+01:00 vcpu-0 I120: UHCI: HCReset 2014-01-08T19:59:45.708+01:00 vcpu-0 I120: APIC THERMLVT write: 0xdc The following lines are from his system, where it appears to begin shutting down: 2014-01-08T19:59:49.336+01:00 vmx I120: VNET: MACVNetLinkStateTimerHandler: ethernet0: state from 1 to 5 2014-01-08T19:59:57.726+01:00 vmx I120: VMXVmdbCbVmVmxExecState: Exec state change requested to state poweredOff without reset, soft, softOptionTimeout: 0. 2014-01-08T19:59:57.726+01:00 vmx I120: Stopping VCPU threads.

2014-01-08T19:59:57.727+01:00 svga I120: SVGA thread is exiting 2014-01-08T19:59:57.732+01:00 mks I120: MKS-SWB: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 1. 2014-01-08T19:59:57.732+01:00 mks I120: GL-Backend: stopped by HWinMux to do window composition. 2014-01-08T19:59:57.732+01:00 mks I120: MKS-SWB: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 0. 2014-01-08T19:59:57.741+01:00 mks I120: GL-Backend: stopped by renderMux to do screen composition. 2014-01-08T19:59:57.741+01:00 vmx I120: USB: Disconnecting device 0xa00000000e0f0008 2014-01-08T19:59:57.741+01:00 vmx I120: USB: Disconnecting device 0xac020b 2014-01-08T19:59:57.741+01:00 vmx I120: USB: Disconnecting device 0x400000050e0f0003 2014-01-08T19:59:57.741+01:00 vmx I120: 2014-01-08T19:59:57.741+01:00 vmx I120+ OvhdMem: Final (Power Off) Overheads I then decided, that it might be necessary to build it from scratch on his Mac instead of transferring it from mine. I furthermore decided to make a test first, where I would install a raw OS X 10.5.8 VM on his system – but alas, I ended up with the exact same error when it booted from the install media (being an ISO file mounted on the virtual DVD drive).