VOGONS

Common searches


First post, by Ravagin

User metadata
Rank Newbie
Rank
Newbie

Hello,
I have been trying to get Dosbox to run some older radio programming software, I am having trouble getting the serial port to read the radio.
I get the error:

Warning: tried to activate hardware handshake.
serial1: errors: Framing 1, Parity 1, Overrun RX:0 <IF0:0> TX:0, Break 0
serial1: errors: Framing 1, Parity 3, Overrun RX:0 <IF0:0> TX:0, Break 0
serial1: errors: Framing 1, Parity 1, Overrun RX:0 <IF0:0> TX:0, Break 1
serial1: errors: Framing 0, Parity 0, Overrun RX:13 <IF0:0> TX:0, Break 0

I am using the Dosbox Version 0.72, with the .DLL files from Hal's site.
Also I installed WinPcap.

Any help is appreciated!

Here is my Dosbox config file:

# This is the configurationfile for DOSBox 0.72.
# Lines starting with a # are commentlines.
# They are used to (briefly) document the effect of each option.

[sdl]
# fullscreen -- Start dosbox directly in fullscreen.
# fulldouble -- Use double buffering in fullscreen.
# fullresolution -- What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
# windowresolution -- Scale the window to this size IF the output device supports hardware scaling.
# output -- What to use for output: surface,overlay,opengl,openglnb,ddraw.
# autolock -- Mouse will automatically lock, if you click on the screen.
# sensitiviy -- Mouse sensitivity.
# waitonerror -- Wait before closing the console if dosbox has an error.
# priority -- Priority levels for dosbox: lowest,lower,normal,higher,highest,pause (when not

focussed).
# Second entry behind the comma is for when dosbox is not focused/minimized.
# mapperfile -- File used to load/save the key/event mappings from.
# usescancodes -- Avoid usage of symkeys, might not work on all operating systems.

fullscreen=false
fulldouble=false
fullresolution=original
windowresolution=original
output=surface
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper.txt
usescancodes=true

[dosbox]
# language -- Select another language file.
# memsize -- Amount of memory DOSBox has in megabytes.
# machine -- The type of machine tries to emulate:hercules,cga,tandy,pcjr,vga.
# captures -- Directory where things like wave,midi,screenshot get captured.

language=
machine=vga
captures=capture
memsize=64

[render]
# frameskip -- How many frames DOSBox skips before drawing one.
# aspect -- Do aspect correction, if your output method doesn't support scaling this can slow

things down!.
# scaler -- Scaler used to enlarge/enhance low resolution modes.
# Supported are none,normal2x,normal3x,advmame2x,advmame3x,hq2x,hq3x,
# 2xsai,super2xsai,supereagle,advinterp2x,advinterp3x,
# tv2x,tv3x,rgb2x,rgb3x,scan2x,scan3x.
# If forced is appended (like scaler=hq2x forced), the scaler will be used
# even if the result might not be desired.

frameskip=0
aspect=false
scaler=normal2x

[cpu]
# core -- CPU Core used in emulation: normal,simple,dynamic,auto.
# auto switches from normal to dynamic if appropriate.
# cycles -- Amount of instructions DOSBox tries to emulate each millisecond.
# Setting this value too high results in sound dropouts and lags.
# You can also let DOSBox guess the correct value by setting it to max.
# The default setting (auto) switches to max if appropriate.
# cycleup -- Amount of cycles to increase/decrease with keycombo.
# cycledown Setting it lower than 100 will be a percentage.

core=auto
cycles=auto
cycleup=500
cycledown=20

[mixer]
# nosound -- Enable silent mode, sound is still emulated though.
# rate -- Mixer sample rate, setting any devices higher than this will
# probably lower their sound quality.
# blocksize -- Mixer block size, larger blocks might help sound stuttering
# but sound will also be more lagged.
# prebuffer -- How many milliseconds of data to keep on top of the blocksize.

nosound=false
rate=22050
blocksize=2048
prebuffer=10

[midi]
# mpu401 -- Type of MPU-401 to emulate: none, uart or intelligent.
# device -- Device that will receive the MIDI data from MPU-401.
# This can be default,alsa,oss,win32,coreaudio,none.
# config -- Special configuration options for the device. In Windows put
# the id of the device you want to use. See README for details.

mpu401=intelligent
device=default
config=

[sblaster]
# sbtype -- Type of sblaster to emulate:none,sb1,sb2,sbpro1,sbpro2,sb16.
# sbbase,irq,dma,hdma -- The IO/IRQ/DMA/High DMA address of the soundblaster.
# mixer -- Allow the soundblaster mixer to modify the DOSBox mixer.
# oplmode -- Type of OPL emulation: auto,cms,opl2,dualopl2,opl3.
# On auto the mode is determined by sblaster type.
# All OPL modes are 'Adlib', except for CMS.
# oplrate -- Sample rate of OPL music emulation.

sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
mixer=true
oplmode=auto
oplrate=22050

[gus]
# gus -- Enable the Gravis Ultrasound emulation.
# gusbase,irq1,irq2,dma1,dma2 -- The IO/IRQ/DMA addresses of the
# Gravis Ultrasound. (Same IRQ's and DMA's are OK.)
# gusrate -- Sample rate of Ultrasound emulation.
# ultradir -- Path to Ultrasound directory. In this directory
# there should be a MIDI directory that contains
# the patch files for GUS playback. Patch sets used
# with Timidity should work fine.

gus=true
gusrate=22050
gusbase=240
irq1=5
irq2=5
dma1=3
dma2=3
ultradir=C:\ULTRASND

[speaker]
# pcspeaker -- Enable PC-Speaker emulation.
# pcrate -- Sample rate of the PC-Speaker sound generation.
# tandy -- Enable Tandy Sound System emulation (off,on,auto).
# For auto Tandysound emulation is present only if machine is set to tandy.
# tandyrate -- Sample rate of the Tandy 3-Voice generation.
# disney -- Enable Disney Sound Source emulation. Covox Voice Master and Speech Thing

compatible.

pcspeaker=true
pcrate=22050
tandy=auto
tandyrate=22050
disney=true

[joystick]
# joysticktype -- Type of joystick to emulate: auto (default), none,
# 2axis (supports two joysticks,
# 4axis (supports one joystick, first joystick used),
# 4axis_2 (supports one joystick, second joystick used),
# fcs (Thrustmaster), ch (CH Flightstick).
# none disables joystick emulation.
# auto chooses emulation depending on real joystick(s).
# timed -- enable timed intervals for axis. (false is old style behaviour).
# autofire -- continuously fires as long as you keep the button pressed.
# swap34 -- swap the 3rd and the 4th axis. can be useful for certain joysticks.
# buttonwrap -- enable button wrapping at the number of emulated buttons.

joysticktype=auto
timed=true
autofire=false
swap34=false
buttonwrap=true

[serial]
# serial1-4 -- set type of device connected to com port.
# Can be disabled, dummy, modem, nullmodem, directserial.
# Additional parameters must be in the same line in the form of
# parameter:value. Parameter for all types is irq.
# for directserial: realport (required), rxdelay (optional).
# for modem: listenport (optional).
# for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
# transparent, port, inhsocket (all optional).
# Example: serial1=modem listenport:5000

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

[dos]
# xms -- Enable XMS support.
# ems -- Enable EMS support.
# umb -- Enable UMB support.
# keyboardlayout -- Language code of the keyboard layout (or none).

xms=true
ems=true
umb=true
keyboardlayout=none

[ipx]
# ipx -- Enable ipx over UDP/IP emulation.

ipx=false

[autoexec]
# Lines in this section will be run at startup.

Reply 1 of 15, by anarchist_tomato

User metadata
Rank Newbie
Rank
Newbie

I'm doing the same thing, trying to program Tait T700 radios. Using a USB serial adapter under Linux, which we've got to work under Linux itself. I'm running with the same settings as our friend above in the serial section, but get this error when starting dosbox:

Serial1: Opening /dev/com1
Serial1: Serial Port "/dev/com1" could not be opened.
The specified port does not exist.

Can anyone point me in the right direction?
cheers!

Reply 2 of 15, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

Port name is probably something like /dev/tty1, /dev/cu1, /dev/....

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 3 of 15, by anarchist_tomato

User metadata
Rank Newbie
Rank
Newbie

oh gawd, of course, i was looking right at that! must have been the tiny screen making me not notice! 😉

is there a way i can define the device name in the config file? i'm not at the computer with all the notes i had before, but someone had a line with realport(i think it was)=ttyUSB0, which didn't work. that doesn't have the entire /dev/ parts preceding it though, and the tip was kind of old.

anyway, throwing away any documentation or tips i might have seen before, if any of you were trying to define the device right now in your own, what would you enter in the config file?

cheers!

Reply 5 of 15, by larry350

User metadata
Rank Newbie
Rank
Newbie

I'm in a similar situation except I'm using an on-board serial port and am getting Framing 0, Parity 0, Overrun (various values) errors and was told that perhaps the data from CTS, RTS, DTR, DSR etc lines aren't getting through back-and-forth. Sounds to me like Moto stuff is pretty heavy on these for communication with the RIB. I've tried various RXDELAY settings as well as Windows serial port settings, very little changes besides the overrun numbers. Is there any way to go straight to the serial port via BIOS?

Reply 6 of 15, by MiniMax

User metadata
Rank Moderator
Rank
Moderator
larry350 wrote:

Is there any way to go straight to the serial port via BIOS?

Yes - if you boot MS-DOS on your PC.

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 8 of 15, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

Might depend on which version of Windows. I have heard of some small programs, DLL's or whatever called GIVEIO and ALLOWIO that will allow some extra access in Windows XP. But I really have no idea if this will work for you.

Remember, DOSBox is not the only emulator/virtual PC for Windows. Maybe Bochs, VirtualPC, VirtualBox, WMware (yeah, they proliferate like rabbits left to their own) will work?

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 9 of 15, by SumGuy

User metadata
Rank Newbie
Rank
Newbie

I'm wondering how an operating system (like XP) handles or controls the com ports when a 16-bit app is trying to perform I/O through the com port. Even with a utility like porttalk I can't seem to get "pure" access to the com port.

And I don't understand if IRQ handling is possible using porttalk (or dosbox).

Do you have to un-install the com port on XP in order to really free it up so it becomes accessible to a 16-bit app?

I'm working with powerbasic for dos (version 3.5) and just using it's standard com-port stuff (open com1:, etc etc). If two systems are started in pure DOS mode (boot from floppy) then I get great communication between 2 apps. If one of them has booted XP, and even if I use porttalk, I get crappy communication. The app running on XP is doing I/O to a custom ISA board and porttalk works great for that. But I can't get serial I/O to function properly.

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

User metadata
Rank DOSBox Author
Rank
DOSBox Author

It goes through the Win32 API in both DOSBox and NTVDM. In the latter Porttalk may only help you if your program uses the registers directly. No interrupt support though. In DOSBox it won't be used at all.

1+1=10

Reply 13 of 15, by SumGuy

User metadata
Rank Newbie
Rank
Newbie

> Porttalk doesn't give you interrupts.

That may be. But still, if I wanted more direct access to the com ports, would it be possible if I uninstalled the com port from XP or deactivated it's driver?