Good point, this appears to be the crux of my issue.
Any suggestions/ideas as how to do this? Based on your reply, one would expect
that a TSR or similar is required to handle this if the UEFI cannot be
configured directly to do so.
I did configure the HP PC's UEFI's com1 & com2 interrupts to the standard DOS
interrupt values which still didn't work.
Tim
From: Ralf Quint [mailto:freedos...@gmail.com]
Sent: Thursday, June 21, 2018 5:53 PM
To: freedos-user@lists.sourceforge.net
Subject: Re: [Freedos-user] Difficulty with serial communications
On 6/21/2018 2:04 PM, Schoenfelder, Tim M wrote:
I am having difficulty getting serial communications to work on FreeDOS 1.2
using new style PCs such as HPs, Dells, etc. The software fails to
communicate. To test, I have attempted to use:
">echo hello > com1"
to verify that serial communications is working as described in this HP post
without any success:
https://h30434.www3.hp.com/t5/Desktop-Operating-Systems-and-Recovery/RS232-Serial-Communications-via-FreeDOS-is-not-working/td-p/6585759
If I try writing something to the port, it fails as follows:
>echo hello > com1
>error reading from device com1 write fault
>(A)bort (I)gnore (R)etry (F)ail
I can then hit the 'A' key twice to exit out of it.
My protocol analyzer is setup for 9600, 8, n, 1 on the other end of the serial
cable. It should see any bits coming across the serial connection (this
scenario worked for the cmd window in win10 but not with FreeDOS as primary OS
or with VMWare in Win10). However, this same command works fine in a cmd
window under Windows 10 on the same computer...its just that windows won't run
my 16bit software program.
My goal is to get HP495x.exe to communicate serially to HP Protocol Analyzers
on newer hardware that can be maintained. HP495x.exe was designed to work with
MS-DOS (I forget which version off-hand). I believe that the software was
developed to use the actual interrupts.
Any ideas as to what to do to make FreeDOS serial communications work?
There isn't really anything in FreeDOS "to make serial communications work".
FreeDOS relies on the BIOS setting up any serial device properly and is
communicating through the BIOS with any properly initialized serial port. And a
lot of software is bypassing DOS/BIOS in the first place and is accessing the
serial ports directly...
What have you done to verify that the serial port(s) are being properly
initialized by the BIOS in the first place?
Ralf
[https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif]<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon>
Virus-free.
www.avast.com<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
