Jump to content

Status of Unlocker 2.0

Donk

By Donk,
in Multi-booting and Virtualisation

 Share
226 posts in this topic

Recommended Posts

NIXin
NIXin
Posted
Posted

1) No

2) You should have kept full backup, but I am sure you can just re-create VM as hardware 10 & just point to the disk

3) No

You are partially correct. You could try to downgrade the VM. I did it with the Tech Preview and it was as simple changing the VM version setting in the .vmx file. It's not supported though so I don't know if it will work properly.

 

@Donk many thanks for the unlocker!

Link to comment
Share on other sites
Zenith432
Zenith432
Posted
Posted

  • :thumbsup_anim:
  • Patched vmware-vmx.exe and vmwarebase.dll manually so as not to have to install python.
  • virtualhw.version = 11, smc.present = true, smc.version = 0 with FakeSMC installed in guest... works! (they coexist, unlike before.)
  • virtualhw.version = 11, smc.present = true, smc.version = 0, no FakeSMC in guest - works :)
  • virtualhw.version = 11, smc.present = true, no smc.version (i.e. 1) - vmware-vmx.exe dumps core

    2014-12-13T15:18:18.367+00:00| vcpu-0| W110: MONITOR PANIC: vcpu-0:VERIFY vmcore/vmm/main/physMem_monitor.c:1123

Now I'm not sure whether it's safe to permanently remove FakeSMC from the guest :unsure: .

Link to comment
Share on other sites
MSoK
MSoK
Posted
Posted

 

  • :thumbsup_anim:
  • Patched vmware-vmx.exe and vmwarebase.dll manually so as not to have to install python.
  • virtualhw.version = 11, smc.present = true, smc.version = 0 with FakeSMC installed in guest... works! (they coexist, unlike before.)
  • virtualhw.version = 11, smc.present = true, smc.version = 0, no FakeSMC in guest - works :)
  • virtualhw.version = 11, smc.present = true, no smc.version (i.e. 1) - vmware-vmx.exe dumps core

    2014-12-13T15:18:18.367+00:00| vcpu-0| W110: MONITOR PANIC: vcpu-0:VERIFY vmcore/vmm/main/physMem_monitor.c:1123

Now I'm not sure whether it's safe to permanently remove FakeSMC from the guest :unsure: .

 

Zenith432,

 

That is the same error as I reported to Donk when testing the new unlocker, currently smc v1 and the unlocker are not compatible, hence the need to set smc version to v0.

Link to comment
Share on other sites
snhirsch
snhirsch
Posted
Posted

1) No

2) You should have kept full backup, but I am sure you can just re-create VM as hardware 10 & just point to the disk

3) No

 

You are correct about having a backup - my bad.  Wasn't thinking clearly when I pushed the button for upgrading VMs prior to checking whether OSX 10.6 still worked.  Not the end of the world, but not one of my better moves :-).

 

Hopefully the version check will get deciphered at some point. 

Link to comment
Share on other sites
Forge64
Forge64
Posted
Posted

I'm sure I'm doing something wrong, but I don't know what.

 

[root@M4800-Arch unlocker202]# ./lnx-install.sh 
VMware Unlocker 2.0.0
===============================
Copyright: Dave Parsons 2011-14
Creating backup folder...
‘/usr/lib/vmware/bin/vmware-vmx’ -> ‘./backup/vmware-vmx’
‘/usr/lib/vmware/bin/vmware-vmx-debug’ -> ‘./backup/vmware-vmx-debug’
‘/usr/lib/vmware/bin/vmware-vmx-stats’ -> ‘./backup/vmware-vmx-stats’
‘/usr/lib/vmware/lib/libvmwarebase.so.0/libvmwarebase.so.0’ -> ‘./backup/libvmwarebase.so.0’
Patching...
  File "./vmxsmc.py", line 66
    print '+LKS Memcpy: 0x' + lks_cpy.encode('hex')
                          ^
SyntaxError: invalid syntax
Link to comment
Share on other sites
MSoK
MSoK
Posted
Posted

Tried upgrading the VM, but then I get an error.

 

vcpu:-0:Verify vmcore/vmm/main/physmem_monitor.c:1123

 

any solution for this ?

Add the following line to your VMX configuration file, it is documented in the unlocker readme:

 

smc.version = "0"

  • Like 2
Link to comment
Share on other sites
mrdutchie
mrdutchie
Posted
Posted

VMware 11.       10.9  about 50-60 seconds      10.10   about 90-120 seconds

VMware 10        10.0  about 20-30 seconds      10.10   about 40 seconds

 

VMware 11 taking forever to get from the starting black screen to the Grey VMware screen.

Link to comment
Share on other sites
11Al
11Al
Posted
Posted

VMware 11.       10.9  about 50-60 seconds      10.10   about 90-120 seconds

VMware 10        10.0  about 20-30 seconds      10.10   about 40 seconds

 

VMware 11 taking forever to get from the starting black screen to the Grey VMware screen.

I confirm with VMware 10 boot time for Mavericks and Yosemite that's.

 

Link to comment
Share on other sites
Donk
Donk
Posted
  • Author
Posted

 

I confirm with VMware 10 boot time for Mavericks and Yosemite that's.

 

 

Just so you know it is about the same on a real Macbook Pro Retina (mid-2012) with Fusion. Honestly there isn't much that can be done about this, until VMware work on improving performance.

Link to comment
Share on other sites
drblink
drblink
Posted
Posted

Drblink, I managed to get the resolution working but the only problem I have is I can't get it to show 1366 x 768. How can I get this to work?

I dont follow. Are you trying to pick a specific resolution other than the your screen's max resolution or the default res the vm starts with? If so, then it isnt possible to my knowledge.

Link to comment
Share on other sites
Donk
Donk
Posted
  • Author
Posted

I dont follow. Are you trying to pick a specific resolution other than the your screen's max resolution or the default res the vm starts with? If so, then it isnt possible to my knowledge.

 

That is correct. It does not even work on a real Mac with Fusion.

  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...