virtualbox.org

I get this message "SYSTEM ERROR: Attempt to unlock memory that is not locked" I am running Windows XP 32 bit on my virtual box to run a program that won't run on 64 bit platforms. It runs fine on 3 machines but not on one other. All machines are running Windows 8 with VB 4.2.6r82870. How do I fix this?
Roy

Is this happening in the host or in the guest?

After opening the Virtual Box running XP It happens when I open a program on the XP Machine. The program is Quickverse for Windows. It has three portions to the program. The atlas and dictionary portions will run just fine. It is the Bible portion that gives the Error message when opening it. It then stays on the screen and can only be closed through Task Manger.

If this is an application error, and it works on other Virtualbox VM, it is not a Virtualbox issue, but an application issue.
Something in the config of the guest OS for that specific machine is not good for the application.
I suggest you seek support at the application's publisher directly.

Why does it work on three other machines with the same Windows 8 operating system running Windows XP on the same version of Virtual Box?

Perhaps you should ask that of the QuickVerse developers? I would suggest however that your test environments cannot be identical, otherwise they would behave the same. Only you are in a position to see what the main differences are, e.g. perhaps one has significantly less memory and you haven't changed the VM config to take account of that.

If you want to continue this conversation I suggest you post the VM log file as a zipped attachment.

roy

Did you find a solution? I encountered the same problem today. I have kept virtual drives for my Windows 2000 and Windows NT4 vm's around for some time and have installed them on various 32bit Intel platforms under OpenSolaris, Windows XP, and FreeBSD hosts. I connect to them with rdp or vnc from a 1995 Compaq 486 laptop. This way I keep the Bible software going I purchased in the 90's. (Longest lasting laptop I ever had.)

Today I set up Windows 2000 and NT4 vm's on an Athlon XP 2700, FreeBSD 9 host, running VirtualBox-OSE 4.2.6 r82870, compiled yesterday, and got the error you did when attempting to open a Bible in Quickverse in either vm. I experimented with different settings via modifyvm but to no avail. I re-installed Quickverse, but to no avail. Other apps in the vm's appear to be working.

Update: I installed FreeBSD 9-STABLE on an intel machine, built VirtualBox-OSE 4.2.6 r82870, and I get the same error as on the Athlon build. Whether I run the app in a NT4 or Windows 2000 guest the application fails with the error noted above with or without guest additions installed. Other applications appear fine. This app, Quickverse, did support Microsoft's DDE (Dynamic Data Exchange).

I'm a newbie to FreeBSD but have been using it for several months now. I wanted to upgrade to VirtualBox-OSE 4.2.6 to get around another bug (https://www.virtualbox.org/ticket/10493) only to run into this. I need the VNC support of VBoxHeadless. Since I did not, some time ago, know how to build I used the PC-BSD pbi to get the VNC support. Now that I'm building, and was tracking 9-STABLE, I was able to build with guest additions and vnc support. My current effort is to revert to 9.1 release and use a mix of prebuilt packages and build VirtualBox-OSE again. I suppose I'll have the slow boot problem again of Window 2000, but the app in question should work.

Any ideas?

Thank You

UPDATE: Finally able to verify that the app, Quickverse, fails regardless of Intel or AMD platform. Building VirtualBox 4.0.16, legacy, fixes this bug and the slow Windows 2000 boot.

Did anyone ever find an answer to the "Attempt to unlock memory that is not locked." system error?

Created my first Virtual Box and can't get QuickVerse to launch completely.

In my case I have to have the virtualization extensions enabled else Quickverse will not run in an XP virtual machine running in Virtualbox 4.2 and above. Hence, if I am not mistaken, you need hardware with the VT-x virtual extensions and the virtual machine configured to use them. I was, however, able to run Quickverse on versions of Virtualbox previous to 4.2 on 32bit Intel processors without the extensions available.