VOGONS


Problem with COM port.

Topic actions

First post, by rafii

User metadata
Rank Newbie
Rank
Newbie

I have few programs wich use COM port to comunicate with other devices. Programs by it self works but don't comunicate over that port.
The same programs work properly when i run them from win98 start disc.
Maybe someone can help me.

Thanks. 😁

Reply 2 of 30, by rafii

User metadata
Rank Newbie
Rank
Newbie

I try it becuase i use this programs to programing Motorolla Radios, and it will be more comfortable to open that programs from windows.
Once i drive to a client with my notebook and i forgot win98 start disc (i have winXP). Thats why i start digging.
Maybe someone knows how to do this in Dos Box?

Reply 4 of 30, by rafii

User metadata
Rank Newbie
Rank
Newbie

I've change it for something like that:
serial1=directserial realport:com1
But when i try to comunicate:
Serial port at 3f8:Opening COM1
Serial port at 3f8:RX Overrun!
It seems that XP is blocking that port.

Maybe i do somethin wrong? 😀

Reply 7 of 30, by rynocs

User metadata
Rank Newbie
Rank
Newbie

hi i am attempting the same thing, had the original error with the serial port but with the patch i am getting a new set of errors:
Serial1: Opening com1
Serial1: Errors occured: Framing 0, Parity 0, Overrun 6, Break 0
Serial1: Errors occured: Framing 0, Parity 0, Overrun 9, Break 0

Reply 9 of 30, by rafii

User metadata
Rank Newbie
Rank
Newbie

I try it with your patch and it the same:
Serial1: Opening com1
Serial1: Errors occured: Framing 0, Parity 0, Overrun 10, Break 0
Serial1: Errors occured: Framing 0, Parity 0, Overrun 10, Break 0
I increase and decrease framing and cycles and it the same.
I even change value of com1 in cmd and still nothing.

I'm just stupid 🙁

Reply 14 of 30, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Try this

http://home.arcor.de/h-a-l-9000/dosbox_files/ … d_async_int.zip

Maybe also try
serial1 directserial realport:comx rxdelay:100
if it doesn't work on its own.

1+1=10

Reply 17 of 30, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Well I don't have the thing and thus can't debug it. You could try the latest CVS as it has my latest serial port code. And try to boot DOS in DOSBox maybe it helps. Could also be that it's not the serial port that causes problems but some INT call that should set the interrupt flag but doesn't.

Reply 18 of 30, by _ivan_

User metadata
Rank Newbie
Rank
Newbie

Hi hal, i have almost the same problem, i am using a software for an interface that needs to run on a CPU max 200 Mhz. I have downloaded the latest dosbox 0.65, edited the conf. file. to
serial1=directserial directport:com2
serial2=dummy
...
....

the program runs over com2.

i only have com1 on my laptop so i redirected the com1 to com2 in win XP.

runnin with core=normal and cycles=3000 (standard)

what more can i try?

The software says "connect the cable......"

Any suggestions?

Reply 19 of 30, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

I don't know much about this redirection of serial ports in WinXP, so I could be wrong, but ....

Drop the redirection in WinXP and let DOSBox do the redirection:

serial1=dummy
serial2=directserial directport:COM1

When the program inside DOSBox tries to talk to COM2 (serial2) DOSBox will redirect it to the real COM1 (I think).

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