VOGONS


Serial Port question

Topic actions

First post, by derrickwhitt

User metadata
Rank Newbie
Rank
Newbie

I am using dosbox to run some software that programs old Kenwood radios. I have to connect the radio using a serial port, I have it using com1. I enabled com1 in dosbox, in the status I see opening com1. I start the software and when I try to read from the radio this message appears in the status box:
bios int14: Unhandled call AH=81 DX= 0

What does this exactly mean?

I appreciate your input.

Reply 1 of 23, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

The INT14/AH81 function is not documented as a PC's serial port function. I haven't figured out yet what it is supposed to do.
Some thoughts of what it could be:
- Maybe your program comes with an own serial port driver that fails to load in DOSBox
- 81H works on the real PC because of some side effect
- 81H is an unocumented but working function on a real PC

1+1=10

Reply 2 of 23, by derrickwhitt

User metadata
Rank Newbie
Rank
Newbie

The program doesnt have its own serial port drivers. I cannot get the radio and PC to communicate in Windows due to the speed of the PC. These radios are 15 years old it doesnt like the 3.0ghz PC 😀
I have the serial turned on in the BIOS, it shows up in the device manager as well. I've slowed the speed of the COM port as well. Any other suggestions to check?

Reply 3 of 23, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

This is a code problem, nothing that could be fixed by tinkering with settings.

1+1=10

Reply 4 of 23, by derrickwhitt

User metadata
Rank Newbie
Rank
Newbie

ok

Reply 5 of 23, by jal

User metadata
Rank Oldbie
Rank
Oldbie
derrickwhitt wrote:

The program doesnt have its own serial port drivers.

However, it may very well rely on external 3rd party drivers. See here for example. It mentions COURIERS.COM, COMM-DRV and VIDEO FOSSIL as possible candidates.

JAL

Reply 6 of 23, by dh4rm4

User metadata
Rank Oldbie
Rank
Oldbie

FOSSIL was a serial port driver for BBS software wasn't it?

Reply 7 of 23, by valnar

User metadata
Rank Oldbie
Rank
Oldbie
derrickwhitt wrote:

The program doesnt have its own serial port drivers. I cannot get the radio and PC to communicate in Windows due to the speed of the PC. These radios are 15 years old it doesnt like the 3.0ghz PC 😀
I have the serial turned on in the BIOS, it shows up in the device manager as well. I've slowed the speed of the COM port as well. Any other suggestions to check?

Do you have a copy of DOS laying around? Or can you download a freeDOS ISO image to test? Maybe it's Windows and not the speed of your CPU.

The last alternative of course is to buy an older PC. Even crappy slow laptops can be had on eBay for cheap. Or try MS VirtualPC with DOS. It supports serial ports too.

Reply 8 of 23, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Or try MS VirtualPC with DOS. It supports serial ports too.

That won't get around the problem that you need some tsr/driver for it to work.

Reply 9 of 23, by valnar

User metadata
Rank Oldbie
Rank
Oldbie
wd wrote:

Or try MS VirtualPC with DOS. It supports serial ports too.

That won't get around the problem that you need some tsr/driver for it to work.

Perhaps I don't understand the OP's original application, but I believe VPC just presents the mapped serial port like it was on the "box". I have run Qmodem from a DOS VirtualPC without problems.

Reply 10 of 23, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

As hal already said the standard serial interface doesn't provide the functions needed for this app.

Reply 12 of 23, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Ok i'll try to check if some bios can provide this, maybe even dos does that
(iirc dos only adds the hw stack stuff for those irqs though).

Reply 13 of 23, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

There is even an example program availible...

DirectSerial patch

1+1=10

Reply 14 of 23, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

I've yet to check some stuff, but it seems like

- 81H works on the real PC because of some side effect
- 81H is an unocumented but working function on a real PC

can be excluded.

Reply 15 of 23, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

After the unsupported INT 14/AH=81 call, the program goes on to do an AH=00 (initialize port) and AH=01 (write character to port) before displaying its error message. Perhaps it is looking for a driver or some such with function 81, but its behavior suggests that it does not rely upon finding something.

Reply 16 of 23, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Now it depends if the app here behaves similar...

derrickwhitt: There has been a fix to the INT14 interface since 0.72, maybe try a DOSBox CVS build.

1+1=10

Reply 17 of 23, by Brian1234

User metadata
Rank Newbie
Rank
Newbie

h-a-l-9000: I've just found DOSbox and want to use it for serial stuff, and would like to get the CVS build but can't find it. Can you give me a pointer?

Do you know what the changes to INT14 are since .72?

Thanks!

Reply 18 of 23, by MiniMax

User metadata
Rank Moderator
Rank
Moderator
Brian1234 wrote:

h-a-l-9000: I've just found DOSbox and want to use it for serial stuff, and would like to get the CVS build but can't find it. Can you give me a pointer?

http://tinyurl.com/7f2nuj

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 19 of 23, by jal

User metadata
Rank Oldbie
Rank
Oldbie
MiniMax wrote:

lol :)

JAL