Custom Query (16363 matches)
Results (1492 - 1494 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #13393 | obsolete | CYMA Professional Accounting System V (PASPLUS) Crashes | ||
| Description |
I have a client who uses an ancient accounting system called CYMA Professional Accounting System V. It's a DOS based program, written when I was chugging beers in college (I'm 44, just for the sake of discussion). First off, I love VirtualBox! I was hoping this would give me an opportunity to show off how awesome it is. She's in a nursing home right now, recovering from a near fatal car crash. Her desktop computer uses Windows 7 and XP Mode to run CYMA and it works. However, her laptop has Windows 8.1. So XP Mode is kinda no go there. (Yes, I know there is a work around, but I'm not keen on it). So, I figured I'd get it working on VirtualBox and all would be well. I created a VM and installed FreeDos 1.1. Everything went smoothly. I created an ISO with her files on it, copied them into the vdi and ran it. It gave me an odd error:
CYMA Systems, Inc. Copyright (C) 1985 - 1994
CYMA Local Area Network Runtime for i80286/386 Pressing any key does nothing other than exit to a DOS prompt. Blah. I tried just loading FreeDos with nothing but Files, Buffers and nothing else in fdconfig.sys and autoexec.bat. It didn't work. So I created a new VM, using DOS 6.22. I ran it. Lo and Behold, the user name prompt came up! After celebrating, I typed in the user name and it went straight back to a dos prompt. Bummer. After fiddling around with it and contemplating drowning my sorrows in beer, I decided to play a game I had bought from Good Old Games. It uses DOSBox to emulate a DOS based system. About 2 minutes in, it hit me. "Hey stupid, try DOSBox. If it works, it's not a file corruption issue." So, what the heck. I tried it. I set it up, mounted the drive, took a deep breath and typed CYMA4L. The user prompt came up. Bah, I'm not going to get excited this quick this time. I type in her user name and hit enter. It asked for a password. I typed in the password and hit enter. It came up! Huh?!? So... This is my thing. I'd rather use VirtualBox, because of what it offers. However, pragmatism says I have to use DOSBox right now to get her up and running. I'm not a programmer, but I am a dedicated guinea pig. Tell me what I can do to help and I'll get it done. First thing I have to offer up are the requested logs. I have searched the forums and this database for similar issues and found none. Granted, the only thing I searched for was CYMA, so it's possible my search was flawed. |
|||
| #20623 | duplicate | Call to NEMR0InitVMPart2 failed | ||
| Description |
Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED). Fehlercode: E_FAIL (0x80004005) Komponente: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} After upgrading from VB 6.1.26 to 6.1.28 starting any of my Linux guests terminates with the above message. Environment (Host): Windows 10 Pro, Version 21H1 (Build 19043.1288) After downgrading back to VB 6.1.26 all guests start and run again without any problem ... |
|||
| #20681 | duplicate | Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED).Result Code: E_FAIL (0x80004005)Component: ConsoleWrapInterface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} | ||
| Description |
This was in my upgraded VB v6.1.28 from v6.1.27? in all of my updated, 64-bit and 32-bit OSes. VB kept showing this after starting a guest VM: "Failed to open a session for the virtual machine ... Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED). Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} Please help! |
|||

