Serial Port [USB dongel]

[wa2gug]

I have been unable to get my serial port to be recognized by Vdos in my GE programing software. I'm trying to program radio systems. I have tried all that I could find in the forum.

I need a KISS remedy since I know enough to be dangerous.

[Jos]

You have to add this line to config.txt:

COMx = "COMx":

Where x is the port number. So probably COM1 = "COM1":.

Documented in Printing.pdf:
Essentially not meant for printing: Communicate with the specified device/file interactively (the data is not collected as a print job). The colon at the end is mandatory.
Basic support for serial devices, such port has to be setup correctly before vDos is started. In the device manager, or by MODE COM… at the Windows(!) command prompt.

Jos

[wa2gug]

That was the first thing I did. Is there something else I missed. I guys in the shop waiting on me to get it to work.

Thanks for reply.

[Jos]

If you’re sure the COM port is setup correctly, but the program doesn’t communicate with the serial device, it probably uses interrupt driven routines to exchange data.

Those are however not supported by vDos.
You can check the usage by starting vDos with the log option (….vDos.exe /log).
The generated vDos.log file will then contain an entry like "INT 0B => XXXX:XXXX" (COM2) or "INT 0C => XXXX:XXXX" (COM1).

If your program has no option to use polling instead (the UART cache is large enough to accommodate that), it ends for vDos.

Jos

[wa2gug]

Jos,

Did as you requester. Here is the log:

vDos-Base
0.06 C: => (Local) C:\vdos\
16.20 vDos ended by EXIT (-1)

When I do Mode the configuration dos not match Device Management. Could this be the problem.

Thanks

[Jos]

I miss your program being started, so no information is shown to for instance what interrupt routines are implemented by the program.

If MODE shows incorrect settings for the serial port, do MODE with the correct parameters before vDos is started.

Jos

[wa2gug]

Finally got it right. here is what the log shows:

vDos-Base
0.06 C: => (Local) C:\vdos\
10.84
Execute: mastr.exe
Int 0 => 1d66:00e1
Int 2 => 227d:26d2
Int 23 => 227d:26ba
Int 34 => 227d:0833
Int 35 => 227d:0833
Int 36 => 227d:0833
Int 37 => 227d:0833
Int 38 => 227d:0833
Int 39 => 227d:0833
Int 3A => 227d:0833
Int 3B => 227d:0833
Int 3C => 227d:07fe
Int 3D => 227d:082b
Int 22 => f000:0003 (Delayed logging w/o DOS call)
46.43 Int 34 => f000:0000
Int 35 => f000:0000
Int 36 => f000:0000
Int 37 => f000:0000
Int 38 => f000:0000
Int 39 => f000:0000
Int 3A => f000:0000
Int 3B => f000:0000
Int 3C => f000:0000
Int 3D => f000:0000
Int 2 => f000:0000
Int 0 => f000:0000
Int 23 => 118:0000 (Delayed logging w/o DOS call)
53.06 vDos ended by EXIT (1)

Sorry I didn't get it right the first time. Not that good with command line in Windows. Hope this is what you needed.

Thanks for your patience.

[Jos]

No INT 0B or 0C mentioned, so serial I/O is supposed to work.
You might try the latest 2023.05.01 version.

Jos

[wa2gug]

Just down loaded exe file. Win 11 reported : Error occurred while loading the archive .

[Jos]

You get this error installing or running vDos?

You downloaded the installation program from the vDos site?

Jos

[wa2gug]

jos

I forgot I was in Ubuntu. Software looded ok. I still get same error. Here is log:

vDos 2023.05.01
CodePage: 437
C: => (Local) C:\vdos\

6.45 LOADEXEC: mastr.exe
INT 34 => 21D2:0833
INT 35 => 21D2:0833
INT 36 => 21D2:0833
INT 37 => 21D2:0833
INT 38 => 21D2:0833
INT 39 => 21D2:0833
INT 3A => 21D2:0833
INT 3B => 21D2:0833
INT 3C => 21D2:07FE
INT 3D => 21D2:082B
6.90 FINDFIRST failed: C:\MA-COM\M2E\*.M2E(18)

don't know what else to do. I checked with the powers to be and suggested sending you the software since there techs are having the same problem
34.15 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 00 => original
34.29 Delayed, directly set:
INT 23 => original
66.86 vDos ended by EXIT (0)

[Jos]

If the same error is "Error occurred while loading the archive" you could inspect if that would be some .M2E file missing from the M2E directory (FINDFIRST failed: C:\MA-COM\M2E\*.M2E(18)).

Eventually replace in config.txt the line COM1 = "COM1": by COM1 = "TEST.TXT":. And see if something gets written to the TEST.TXT file.

Jos