Thanks Ken,
That makes sense why New-Dos isn't working. I did get it to work for just a
moment using the RAM version of TS-DOS but it locked up and now the port is not
responding. I've tried turning on and off the flow control as well. I'll try to
create a sequence of events that is repeatable. As of right now I can't point
to any one thing that causes it.
One thing I do notice. Whenever the port hangs up, I can't exit Virtual-T. I
get a Windows error and then I have to kill the program.
I'll keep you posted.
Kurt
On Thursday, March 3, 2016 12:41 PM, Ken Pettit <[email protected]> wrote:
Hi Kurt,
The Virtual-T com port emulation doesn't really know or care what program is
running in the emulation, so it shouldn't matter from that perspective. What
might be going on could be a couple of things:
1. Maybe the app (TS-DOS, Sardine, etc.) is locking up because of hardware
flow control? The Virtual-T com settings page has a checkbox to force HW flow
control on.
2. Maybe timing related. If the emulation speed is set to anything other
than 2.4Mhz, then the app could be timing out before the serial port has time
to transfer the data. I know TS-DOS has timeouts that use ASM loops with a
specific number of iterations, and therefore time out much more quickly at
higher emulation speeds. New-DOS attempts to get around this by detecting it
is running in Virtual-T and using VT's un-documented real-time timer feature to
implement time outs.
Ken
On 3/3/16 10:11 AM, Kurt McCullum wrote:
Does the Virtual-T Host Com Port work with programs other than TELCOM? I ask
because I am trying to use it with a USB to rs232 adapter set to Com2 on my
Windows system. When I use TELCOM, I can send and receive data without issue.
When I try to use New-DOS, TS-DOS, Sardine or the Ultimate Rom they all lock up
or in the case of New-DOS, it reports an error. I'm sure I'm missing something
but it's baffling.
Kurt
