VOGONS


com1 connection problems

Topic actions

First post, by doxbos

User metadata
Rank Newbie
Rank
Newbie

Hi,

we got a very old program to operate a new machine (!). It's said that win2k, which runs on the pc nearby, is unstable. It requires win98. So I took dosbox.
The machine is connected by rs232.

When I start

Serial1: Opening com1

Seems ok, but the program won't connect.

config:

serial1=directserial realport:com1
serial2=disabled
serial3=disabled
serial4=disabled

What's going wrong?

Reply 1 of 10, by doxbos

User metadata
Rank Newbie
Rank
Newbie

Is there any way to test the com1 connection?

I'm also unsure about the "Opening com1" message. Doesn't seem to be that meaningfull. It brings the same message if I configure com2 in dosconf (the pc actually has 2 ports).

Reply 2 of 10, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

"Opening com1" is fine.

A serial port log might help. There is a build with it on my homepage (web button below).

Also, explain a bit what kind of serial connection this is and what kind of ports your computer has (built-in I guess).

1+1=10

Reply 3 of 10, by doxbos

User metadata
Rank Newbie
Rank
Newbie

That looks very promising. I will try it next week when I have access to the pc.

Both, the machine and the pc are connected by rs232 and 'yes' it's a 'built in' port.
Does this answer your questions?

Reply 4 of 10, by doxbos

User metadata
Rank Newbie
Rank
Newbie

Now I have the logs!

Reply 5 of 10, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Could you try the attached improved version? Extract it into the MB5 folder and run it.

I've found three problems in the INT14 interface.

1+1=10

Reply 6 of 10, by doxbos

User metadata
Rank Newbie
Rank
Newbie

Great! Thanks!

Today I started dosbox via the new exe you offered.

Here's the console output I received:

DOSBox version 0.73MB5
Copyright 2002-2009 DOSBox Team, published under GNU GPL.
---
CVS build compiled on Oct 4 2009 - http://home.arcor.de/h-a-l-9000
featuring:
Try not to exit on unsupported fullscreen mode
\a bell support
Add the 'IMGMAKE' command (creates disk images)
Make vgaonly features availible to other graphics cards - see [render]
Add DATE and TIME commands, midnight overflow, and host time synchronization
NE2000 Ethernet passthrough
OPL chip passthrough
Parallel Port passthrough and Virtual Printer patch, logging enabled
Parallel Port data redircetion to file/device
Add restart capability, Win95 can shutdown DOSBox through APM
Serial FIFO support and logging capability enabled
Increase maximum resolution to 1600x1200, add lot's of highres VESA modes
Add back selection of video memory size - up to 8MB = 1600x1200@32bpp
EGA / SVGA_S3 compatibility, enable LDGFXROM
CGA line-by-line emulation and video memory slowdown
Fix text mode panning in vgaonly modes
DOSBox can load while the splash screen displays
FILES= adjustable by Kippesoep
CONFIG command capabilities extended - manipulate config files
Restart capability - ctrl+alt+POS1 or config -r [params] or FJMP F000:FFF0
DIR /B
---
CONFIG:Loading primary settings from config file dosbox.conf
MIDI:Opened device:win32
Capturing serlog to capture\dosbox_010.serlog.txt
Serial1: Opening com1
DOS keyboard layout loaded with main language code GR for layout gr

Network Interface List
-----------------------------------
1. rpcap://\Device\NPF_GenericDialupAdapter
(Network adapter 'Adapter for generic dialup and VPN capture' on local hos


2. rpcap://\Device\NPF_{B3C1E343-797C-4AF9-A5C8-13B804003101}
(Network adapter 'Intel(R) PRO/100 VM Network Connection' on local host)

Reply 7 of 10, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Well does it work?

1+1=10

Reply 8 of 10, by doxbos

User metadata
Rank Newbie
Rank
Newbie

Sorry, forgot to mention!
No, it does not.

Reply 9 of 10, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

This gets difficult, then. Your software sends some data and receives some in turn. From the log I don't see a problem. Maybe the software needs to be configured differently?

Try some of the general DOSBox troubleshooting tips like loadfix or different cpu type/speed.

If that doesn't help, it would require somebody with debugging skills at your place with the hardware.

1+1=10

Reply 10 of 10, by doxbos

User metadata
Rank Newbie
Rank
Newbie

Damn!

Does it make sense to install a VM with Win98 to run the prog?
If 'yes' what' you recommend? Virtualbox or VMware?