|
Post by will on Jul 13, 2021 15:57:50 GMT 1
Hi, I'm using vDOS to keep a legacy invoicing software ticking. The issue I'm having is the a key feature, logging charges, is causing a [Device unavailable in module FJOBCOST at address 1002:1F51quiry & modification] error when I try and use it. I think this is due to lacking some physical component that is part of the physical machine, but am unsure.
Could I please get some advice on how to start solving this issue? I've tried dumping the entire original PC's HD into the virtual environment, but that hasn't solved the issue.
|
|
|
Post by Jos on Jul 13, 2021 16:15:38 GMT 1
Hard to tell. Could it be the program:
Tries to access some serial device, and expects a specific response of that, or Requires (is protected by) a dongle to operate.
The original physical machine is a PC and still functioning?
Eventually you can start vDos with the log option (....vDos.exe /log). But I doubt that "[Device unavailable...] will be trapped in the generated vDos.log will
Jos
|
|
|
Post by will on Jul 13, 2021 16:39:10 GMT 1
Yeah, the original is still running fine, we are just in the middle of moving offices, so trying to get it onto a more portable format. The PC has nothing but a mouse and keyboard plugged in, but I can open it up to check if there's anything inside it might be trying to ping.
Where does the log generate? I'll give that a go.
|
|
|
Post by Jos on Jul 13, 2021 18:05:00 GMT 1
vDos.log is stored in the directory of vDos.exe.
Jos
|
|