2Dariusz
Good Evening, Sir!
Hi Mark!
...I will try what you suggested above. After migrating to libcx 0.6.2-1 I have not had a successful start of either VM, but that may be because of the current configuration...
The key here is to include the 'SET LIBCX_HIGHMEM=2' in either your CONFIG.SYS or in the vbox.cmd file (like the one I attached to my previous post) which you use to start virtualbox with. That will allow you to run vbox with the new experimental libcx. If you do not have the variable set it is a known fact that virtualbox will not run, at least that's with the standard OS2 or AOS kernels, the result may be different with OS4 kernels.
...I was curious about one other thing.
Is VirtualBox and your VM's installed on the same partition?...
Here is the configuration I have:
1) 'G:\' is my boot drive
2) VBox is installed on G:\
3) virtual machine definitions are stored on G:\, but in a different directly as defined by 'SET VBOX_USER_HOME=G:\HOME\VirtualBox'
4) the VM disk images are stored on another HD (and another parittion), idea there being to avoid disk contention if the main boot drive is being accessed by the program while at the same time the vm is trying to access it's virtual disk (basically a poor man's HD load-balancing if you will, same idea as yours)
I will give the version Valery is talking about a try next as that appears to be a slightly upgraded (newer) version, so if I'm going to experiment why not work with the one that is being actively worked on?
Thanks for all the information - looking at your CONFIG.SYS it was very well organized, annotated and easy to follow. I assume you do a lot of changes regularly, probably for development and testing.
I was interested in seeing most specifically if all your files (VBOX, VM's, etc.) were all on the same partition, or scattered across partitions like mine, as I thought that might be part of the problem, getting the VM's to start.
But I think I found a workaround last night, using VBOX 5.0.51 that allows for consistent start-up of the VM's, which I have used successfully multiple times today. It has also been tested with both LIBCX 0.6.0-1 and LIBCX 0.6.2-1 (with SET LIBCX_HIGHMEM=2 set in config.sys).
1) Startup the VirtualBox window.
2) Wait 15 seconds, then click on the VM you want to open or press the start button. The VM you requested should start up normally.
3) If you get the 1018 error box, press the "Abort" button, then when the second window appears, the "Okay" button. Wait 15 seconds, then again start the VM, and it should start up normally
4) If neither works, and you have a program open that takes up a lot of memory (in my case Seamonkey 2.35), shut that down first, then attempt 1) to 3) above. You should get a normal VM start.
I tried the above waiting 10 seconds, which did not work for me, but waiting 15 seconds seemed to do it.
With limited testing I believe, as Valery has mentioned, that the problem is related to a shared memory or memory conflict problem. Once the Windows XP VM I've been using for test purposes started I was able to then start Seamonkey 2.35 again and use both successfully at the same time. However, at one point I had to shutdown Seamonkey, while I was still running VBOX, and attempting to restart SeaMonkey, it would not start a second time, with VBOX open
That did not occur again but i suspect YMMV based on how much memory was being used at any specific time
Anyway now at least here I plan to focus on the testing mostly on the VBOX program as opposed to getting the VM to start
You might want to try the above Dariusz or others and see if the same workaround works for you and Best
Mark