Hi, first of all I would like to say this is a great guide =D
Unfortunately, I'm not a cabler but a mapler instead, and had tried to use the same tactic as well, 1 for my hb mule and the other for my main to train. Sadly, as you can see from my com's spec:
Processor: Intel(R) Pentium(R) 4 CPU 2.80GHz
Memory: 2550MB RAM
Display Memory: Integrated 128.0 MB
... could be sent to the trash. Furthermore, I've encountered the errors faced by other users here. However, after troubleshooting, I managed to fix all errors and everything is running as smoothly now. As my com could not support 2 maplestory in vmware (No Core2duo for me =(), I had to open 1 on my host instead. The first error I got after 1 min was:
*** VMware Workstation internal monitor error ***
I then tried another method. After loading maple in the guest, I click on the close button and had it run in the background instead. I then used DXwnd... and to my surprise, the error was gone. Unfortunately, the guest could only last for a maximum of 15 mins before producing another error, the one everyone have.
I managed to fix it by adding the following lines:
Default Location in:
C:\Documents and Settings\All Users\Application Data\VMware\VMware Server\config.ini
prefvmx.useRecommendedLockedMemSize = "TRUE"
prefvmx.minVmMemPct = "100"
Default Location in: Your ".vmx" file
sched.mem.pshare.enable = "FALSE"
mainMem.useNamedFile = "FALSE"
MemTrimRate = "0"
I have also disabled Vmware's debugging, which is enabled by default by doing the following.
Default location in C:\Program Files\VMware\VMware Workstation
Rename vmware-vmx-debug.exe to vmware-vmx-debug-orig.exe
Make a copy of vmware-vmx.exe and rename the copy to vmware-vmx-debug.exe
Which speeds up vmware quite alot =) Now I have maple running in the background, controlled wirelessly by my psp and doing all the things that's needed of it.
Hope this helped. =)