Ms-dos Serial Port Configuration
First, compliments for the beautiful project.I am an Italian boy I speak a little English (sorry ahead for my English) I have the need to run a 16-bit program on my winzoz seven 64 bit.(in win xp 32 bit work perfectly) I have a usb to serial port converter to communicate from PC to a machine tool with CNC. The 16-bit program works perfectly in dosbox 0.74, but the serial port NO! I set from the configuration file: serial1=directserial realport:COM2 serial2=disabled serial3=disabled serial4=disabled But when I start dosbox appears: Serial1: Opening COM2 Serial1: Desired serial mode not supported (9600,5,n,1) Exactly this problem! How do I install this patch? In dosbox 0.74. Where do I put the file 'dosboxignore5N1.patch'?
General configuration notes for DOS, W98SE. Serial port COM2 (if present) 4: Serial port. The relevant flavors of DOS are FreeDOS and occasionally MS-DOS 7.1.
MODE (Configure Serial Port) Description Syntax. This version of the MODE command sets the parameters for a serial port (COM1, COM2, COM3, or COM4). Many USB serial ports do not support a 5 bits per byte configuration however when configuring a serial port under DOS it is fairly common practice to simply set the.
Thanks in advance to all. Guly, Using the patch requires the project be built from source. 1) You will need a build environment. Get MinGW if you do not have it. 2) Download the source of DosBox. 3) Extract the source from the archive 4) Apply the patch with the command: patch -p0. Thank you for this Thomas, I definately am still interetsted in this but I couldn't get it to work.
Ms Dos Serial Port Transfer
I am trying to get a old DOS program to talk to a hardware device using either 1200 or 2400 baud 8 N 1. Using my Dell Latitude laptop with a docking station that has a physical serial port as COM 1. I can sucessfully run the program using DOSBox and communicate to the device every time under both Windows 7 and Windows 10 using that physical COM port. However I am trying to get a USB - Serial adapter working. The adapter is setup as COM 2 and using HyperTerminal the adapter works fine. But in DOSBox it does not communicate.
I see both serial ports open on startup: Serial1: Opening COM1 Serial2: Opening COM2 I use the software with COM 1 (physical one) and it works fine. I then switch the software over to COM 2 and start getting this: Serial2: Errors: Framing 0, Parity 0, Overrun RX:6 (IF0:0), TX:0, Break 0 Serial2: Errors: Framing 3, Parity 0, Overrun RX:8 (IF0:0), TX:0, Break 3 Serial2: Errors: Framing 2, Parity 0, Overrun RX:0 (IF0:0), TX:0, Break 0 and I cannot communicate. Switch it back to COM 1 and again it works. Any ideas or things I can try?
I am sorry not being able to give advice of what might go wrong. I just took the sources from SVN, applied the patch and compiled the whole thing. I needed the modified version myself and wanted to provide the EXE as some people stated they didn't know how to compile the code. However, I was not yet able to test it myself as it turned out my USB-serial-converter ain't working properly.
So I'm not yet able to give any feedback about the success of the patch. Kind regards, Thomas - Original Message - From: Allan To: dosbox:patches Sent: Wednesday, July 12, 2017, 16:33:25 Subject: dosbox:patches #249 USB Serial work-around Thank you for this Thomas, I definately am still interetsted in this but I couldn't get it to work. I am trying to get a old DOS program to talk to a hardware device using either 1200 or 2400 baud 8 N 1.
Using my Dell Latitude laptop with a docking station that has a physical serial port as COM 1. I can sucessfully run the program using DOSBox and communicate to the device every time under both Windows 7 and Windows 10 using that physical COM port. However I am trying to get a USB - Serial adapter working. The adapter is setup as COM 2 and using HyperTerminal the adapter works fine. But in DOSBox it does not communicate. I see both serial ports open on startup: Serial1: Opening COM1 Serial2: Opening COM2 I use the software with COM 1 (physical one) and it works fine. I then switch the software over to COM 2 and start getting this: Serial2: Errors: Framing 0, Parity 0, Overrun RX:6 (IF0:0), TX:0, Break 0 Serial2: Errors: Framing 3, Parity 0, Overrun RX:8 (IF0:0), TX:0, Break 3 Serial2: Errors: Framing 2, Parity 0, Overrun RX:0 (IF0:0), TX:0, Break 0 and I cannot communicate.
Switch it back to COM 1 and again it works. Any ideas or things I can try? USB Serial work-around Status: open Group: Created: Wed Aug 03, 2011 12:45 PM UTC by Adam Connell Last Updated: Wed Jun 28, 2017 08:11 PM UTC Owner: nobody Many USB serial ports do not support a 5 bits per byte configuration however when configuring a serial port under DOS it is fairly common practice to simply set the serial ports LCR register to 0x80 to set the DLAB bit before setting the LCR to the actually desired value. This patch is a hack to work around the problem with these adapters at the cost of disabling the 9600 baud 5.N,1 configuration. Sent from sourceforge.net because you indicated interest in To unsubscribe from further messages, please visit.
Dos Serial Number Command
Ok dug down deep into all my archives to find a W2K Pro SP4 install (probably could have used XP too but 2k is far less relliant on ms. Using the free VMWare Player, W2K can be installed and runs most dos programs VMware allows adding h/w links plus has drag drop features that still work in 2k. All round solution. Took all of 30minutes of default settings to install and get xtalk mk4 back up and running with a USB serial port. There are some easy to follow youtube sessions on how to install win 2k in vmware plus if you look hard enough there are still W2K Iso files out there for download.