NefMoto

I can't seem to get WinOLS to function properly. It installs flawlessly but when I open the application, it brings up the loading screen then just shuts right down. No error, warning or notification of any kind.

I've tried the newest version demo and one of the older versions.

I am running windows XP in a VMWare Fusion virtual machine on my Mac. I've tried compatibility mode and running as admin. No go.

Last night I went as far as building a new XP VM, no go. Built a Win7 VM, no go. All do exactly the same thing.

Any one have any idea?

Looks like it has something to do with VMWare.  I opened the same VM in Parallels and WinOLS opens fine.  Looking for settings/options in VMWare to enable/disable in order to get it to work properly.  FWIW, the host doesn't matter.  The same thing happens between my work Windows 7 x64 PC running VMWare Player, my i7 MacBook Air and my i7 iMac both running VMWare Fusion 5.0.1.

I will report back.

Yes, WinOLS actively checks if it's running an VM and silently quits without warning. If you pop the following line in your VMX config file, all should be resolved.

isolation.tools.getVersion.disable = "TRUE"

Did that fix the issue? I'm having the same issue: trying to get WinOLS 2.24 to run on VMfusion. It ran well on a native win7 machine but now that I've transitioned to VM it does not. When launching from the desktop shortcut, I get an error window saying "This program can not be run under VMWare!". I get a different error message when launching ols.exe directly: "problem occurred reading config file ols.cfg. Problem code: cfg-12a".

Any words of wisdom?

This line should hide VMware pretty effectively from applications within VM's that are looking to detect it. There's a few others you can try if you need, but this line alone works well for me running WinOLS 2.24

Which vmware do you use?  I've never had any luck hiding the fact that it is running on vm.

Strange how that line would fix the issue for some people but not for me (for version 2.24). Anyway, I was able to get 1.7 to work so I should be set. I might try 2.24 again later but presently don't have anymore patience for it.

Using workstation 8 here, but this vmx parameter is known to work on anything recent including ESX.

There are other parameters you can add (listed below), but i've found them unnecessary with the getversion.disable parameter. Certainly for OLS 1.5, 1.7 and 2.24 that i've tried.

monitor_control.virtual_rdtsc = "false"
monitor_control.restrict_backdoor = "true"
isolation.tools.getPtrLocation.disable = "true"
isolation.tools.setPtrLocation.disable = "true"
isolation.tools.setVersion.disable = "true"
isolation.tools.getVersion.disable = "true"
monitor_control.disable_directexec = "true"

Much appreciated. I'll give these a try when I find the motivation. Any reason not to add them all to the end of the config file?

Nope, add away.... Just stop adding when it works ;)

Any info on virtualbox settings? Freaking Enigma protector is annoying as f.

Hi,

Have you managed to overcome the issue with VirtualBox? I've managed to solve this one only with VMware :(

Go to your virtual machine path and open VMware virtual machine configuration with text editor (ex : windows 7.vmx)
write at the bottom
monitor_control.restrict_backdoor = "True"
Enjoy :)

I know this is an old post but if anyone encounters this on VirtualBox. You have to uninstall Guest Additions and it'll work fine

I tested this with a VMWare XP Pro VM and WinOls 2.4 and it worked. Thank You!

MHHauto has a few hot threads with installers for newer cracked versions of winOLS. It costs as few bucks to join but its well worth it.