|
|
Post by ed on Dec 1, 2023 18:41:44 GMT 1
I have a program from the 1990s. Unfortunately, it was a purchased product at the time so I don't have source and the developer passed away in the early 2000's. The program works great in vDos (version 2023.05.01) until I select the print option. As soon as it tries to print an error is thrown "Device unavailable in module PRG at address 00EE:0C85". All I want is a the output in a file. I use a virtual printer (VPRINT version 5.10 by Whitman Software) to redirect lpt1 to a file, but this error occurs with and with/out using it. My config.txt has one line (LPT1=RAW) and I also tried an empty config.txt. No autoexec.txt is being used. No #LPT1.asc or #LPT1.txt is generated. I test creating one using "echo hello >lpt1" and that works as expected. From what I can tell, the instruction at 0xC85 is: MOV AX,235Ch. According to a de-compiler generated listing. I'm an experienced programmer but I don't have much experience trying to get this old stuff to run on Windows 11. Therefore, I can probably send you what you need (outside of the PRG module as it is proprietary "secrete sauce"). What more information would help diagnose? What config options may help with this?
Ed
|
|
|
|
Post by Jos on Dec 1, 2023 19:45:25 GMT 1
Seems your program attempts to access a non-existing DOS/vDos device, or validates some bit of the device information as incorrect.
You can start vDos with the log option (….\vDos.exe /log) and have a look at the generated vDos.log file. But that will only show failed open/create operations of the device. Device information isn’t logged.
Eventually send me the files needed to reproduce the error, and I’ll have a look.
The VPRINT roundabout is not needed, LPT1 = DUMMY will do. Though #LPT1.asc and #LPT1.txt will of course only be created if your program actually prints.
Jos
|
|
|
|
Post by ed on Dec 1, 2023 20:08:49 GMT 1
The same program runs under dosBOX without any issues (with or without the virtual printer). This is all that shows int the log:
vDos 2023.05.01
CodePage: 437
C: => (Local) C:\ct10newp\
4.01 C: => (Local) c:\
8.28 LOADEXEC: PRG.EXE
INT 34 => 1710:0550
INT 35 => 1710:0550
INT 36 => 1710:0550
INT 37 => 1710:0550
INT 38 => 1710:0550
INT 39 => 1710:0550
INT 3A => 1710:0550
INT 3B => 1710:0550
INT 3C => 1710:051B
INT 3D => 1710:0548
INT 00 => 1117:00CE
INT 04 => 1117:00D2
Redirect INT 24 ignored, won't be further logged
25.67 INT EF => original
INT F0 => original
INT 00 => 1057:00B5
INT 04 => original
INT 34 => original
INT 35 => original
INT 36 => original
INT 37 => original
INT 38 => original
INT 39 => original
INT 3A => original
INT 3B => original
INT 3C => original
INT 3D => original
INT 02 => original
INT 75 => original
INT 00 => original
26.91 vDos ended by EXIT (0)
|
|
|
|
Post by Jos on Dec 1, 2023 20:57:52 GMT 1
No errors, so a device information mismatch remains, the only cause that comes to mind.
Jos
|
|
|
|
Post by ed on Dec 2, 2023 14:43:53 GMT 1
I'm not sure how to proceed because it works in dosBox and it works if I don't select the print option.
|
|
|
|
Post by Jos on Dec 2, 2023 17:13:30 GMT 1
I suggest you stick with DOSBox. There’s no way to find the cause of the error without a copy of PRG.EXE.
Jos
|
|
|
|
Post by ed on Dec 4, 2023 18:30:10 GMT 1
I actually started with dosBox but some rexx code wouldn't operate properly under it so I tried vDos; but prg runs fine. I have just the opposite situation with vDos. As of yet, I haven't found a solution that runs both without issues. I'm starting to think I'm just going to have to stay with Windows Xp and hope the machine running it doesn't die.
|
|
|
|
Post by ed on Dec 11, 2023 13:50:58 GMT 1
I am a system programmer fluent in many languages from ASM to C to c++ and beyond. Any chance I can get the source for the current version of vDOS to try and correct this problem myself?
|
|
|
|
Post by emendelson on Dec 11, 2023 14:13:54 GMT 1
Have you posted the REXX issue on the DOSBox-X GitHub site? There is a large group of programmers there who may want to fix it.
|
|
|
|
Post by ed on Dec 11, 2023 14:59:56 GMT 1
I have not posted there, but I can. However, vDos is more for business and dosbox is more for gaming (at least that is they way each is portrayed. And I do like the way vdos handles command line better. Is that a "no" on the source?
|
|
|
|
Post by Jos on Dec 11, 2023 15:09:55 GMT 1
|
|
|
|
Post by ed on Dec 11, 2023 15:25:43 GMT 1
For previous version only. I'm on the current version which I presume I should be using; no? |
|
|
|
Post by ed on Dec 11, 2023 15:26:50 GMT 1
Have you posted the REXX issue on the DOSBox-X GitHub site? There is a large group of programmers there who may want to fix it. |
|
|
|
Post by Jos on Dec 11, 2023 15:40:02 GMT 1
You could get one, and check if it gives the same error. Then look for the cause, and submit the solution…
Jos
|
|
|
|
Post by ed on Dec 11, 2023 15:44:35 GMT 1
You could get one, and check if it gives the same error. Then look for the cause, and submit the solution… Jos Okay, never mind. I need to have something with some support or be able to support it myself. I purchase something else. |
|
