Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Contact Methods

Profile Information

I am also having problems with FaceTime in an El Capitan vm running in VMware Player 12. In my case, the app opens, but it doesn't accept my sign-in; the same sign-in as other OS X apps like Reminders and Notes, which work fine.

On a hunch, I uninstalled VMware Player (12) and reinstalled it from scratch. I then applied the 2.0.8 unlocker, and added the smc.version = "0" to the Yosemite VMX file. Everything worked, and I now have a working Yosemite vm on my Dell!
Might I suggest, Donk, that you add to the Readme of Unlocker 2.0.8 that if you had another version of Unlocker installed, you reinstall the VMware app, rather than uninstall the earlier version of Unlocker on the existing app.
Finally, to answer your question about the source of my installer, I re-downloaded Yosemite from the App Store one of my Macs (it was 10.10.1) and then converted it to a DMG using the CYI.tool.
Donk, I really appreciate that you took the time to answer my queries, and I hope that the bit about reinstalling Player will help someone else with a similar problem.

Unfortunately, the new unlocker didn't change anything; I can still run vms created from my Mac using the saved image, but as soon as I try rebooting them, they hang up. I also tried creating a Yosemite vm from an installer DMG file on the 2.0.8 patched version of VMware Player on my Dell, and it booted the DMG initially, but then hung up in the same place as before, as noted by the progress bar. Adding SMC.version = "0" to the VMX file had no noticable impact. Inspection of the vmware log file showed two interesting problems:
UserLocale=NULL 2015-11-30T08:58:48.571-05:00| vmx| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
and
2015-11-30T08:58:48.571-05:00| vmx| I125: DictionaryLoad: Cannot open file "/home/(username)/.vmware/config": No such file or directory.
There were other similar statements in the log, but both suggested that there should be two files that weren't present. So I went ahead and created those files, but unfortunately, it didn't seem to recognize them because I got the same errors. VMX and log files are attached.
OS X 10.10.vmx.txt
vmware-1.log.txt

Fantastic; thanks Donk! I'm anxious to try this. Question - do I need to uninstall Unlocker 2.0.7 before installing Unlocker 2.0.8? Also, if I already have a virtual machine made up from my Mac based on Unlocker 2.0.7 and the iso tools from that version. Is there something further that I would have to do to that vm if I want to transfer it to a PC running Player 12 (fixed with Unlocker 2.0.8)? Thanks!

I have had no problem creating Mac OS X virtual machines in VMware Player (12) with unlocker 2.0.7, but only when I do it on a Mac. I created Snow Leopard, Mavericks and Yosemite vm's in Ubuntu (15.10). But when I run them on a Dell 7010, they run OK from the saved state, but stall after a reboot, even after adding smc.version = "0" to the VMX file. They hang up about a minute after the Apple Menu appears. And if I try to make the vm on the Dell (again running Ubuntu 15.10), the installer starts up but freezes about 1/4 of the way. Is there something else I have to do to the VMX file to get it to pass the "Mac test" and start up on the Dell PC? Does it matter that I am using Linux on the Dell instead of Windows?

I have a similar problem as Med ben A, except that I am running my vm on Workstation Player 12 in Ubuntu 15.10 on a Dell 7010 and I don't know how to get verbose output upon startup to know where the problem is. When I create a new machine, add the smc.version = "0" to the newly created vm, and then try to install Yosemite from a DMG file, the installer starts up but freezes about 1/4 of the way. When I create a vm on my Mac mini running Ubuntu 15.10, it runs OK. When I transfer that vm to the Dell and run it from a suspended state it runs OK. But if I then try to restart it on the Dell, it hangs about a minute after the Apple menu appears. This happens even after I have edited the vmx and added smc.version = "0" to it, and it happens whether the vm is Snow Leopard, Mavericks or Yosemite (all of which run OK on my Mac mini running Ubuntu 15.10). My version of Player on both the mini and the Dell have been patched with Unlocker 2.0.7. Is there something else I have to do to the VMX file to get it to pass the "Mac test" and start up on the Dell PC?

Unfortunately, the unlocker doesn't seem to work on the latest version of VMware Fusion, version 7.0. The Terminal output indicates that it sucessfully patched vmware-vmx, -vmx-debug, and -vmx-stats, but "Patching vmwarebase is not supported on this platform."

Mate has come a long way since it was first released for Mint. It seems to work very well in Ubuntu, and it gives an experience virtually identical to gnome 2. I think it will be around for a long time simply because so many people were attached to gnome 2. And you can install it alongside gnome-shell or Unity, as its packages have been renamed so as not to cause conflicts with gnome-shell.

While I am mainly a Mac user, I like the open source idea behind Linux, and I have been using it for three years on a netbook I bought for that purpose. Ubuntu Unity was preceeded by Ubuntu Netbook Remix and then Ubuntu Netbook Edition, and both were good desktop environments for small display netbooks. I took to it instantly when UNR first came out, but didn't care so much for its standardization on all computers with the release of Unity. When 12.04 came out, I forced myself to learn it better, to prepare for a presentation I will be making to my local Linux club on Ubuntu interfaces (Unity, Gnome 3, Cinnamon, Mate). Now that I know it better, I also like it better. It lacks some of the customization options of the alternatives and requires some new ways of operating, but features like scopes and lenses make it interesting to me.