son of a gun, that did it Kurt! Nice! I was pulling what is left of my hair out!
On Sat, Jan 9, 2021 at 5:30 PM Kurt McCullum <[email protected]> wrote: > Here is what I have had to do to get Virtual-T in Windows to work properly. > 1) Start Virtual-T with no emulation for a COM port > 2) Select Use Host Port and pick your COM port > 3) Exit Virtual-T. If you don't do this, it won't work. > 4) Re-Start Virtual-T and you are good to go. > > That's the only way I have been able to use Virtual-T with a host port. If > (when) you loose connection, you have to do the following. > 1) Start virtual-t > 2) Select Select No emulation. > 3) Exit. > Go to step 1 above and repeat. > > Sounds crazy but that is what works for me. > > Kurt > > On Sat, Jan 9, 2021, at 1:15 PM, Stephen Adolph wrote: > > Update, back to the subject of this thread. Getting VirtualT to accept > input characters from serial ports. > > After all this experimentation, and success with the sniffer > configuration, I still cannot get VirtualT to receive a byte from a serial > port. > > Nothing seems to make a difference; regardless of port type, settings etc, > VirtualT cannot receive a byte from the external world. > > I would have thought I could at least run a TELCOM session over the PC > COM1 port but all I can do is send data out, I can't receive any data. > > Does anyone have any tips on how to get this working? > > thx > Steve > > On Fri, Jan 8, 2021 at 7:19 PM Stephen Adolph <[email protected]> > wrote: > > Hey Folks, > I'm having some trouble getting bi-directional serial port working on > virtualT. > > * Windows 10 > * VT 1.7 (and also tried 1.6) > * using a real serial port COM 1, or also COM2 FTDI USB serial port > * Model T connected to COM1. > > I can send out from VirtualT no problem, but nothing seems to flow in the > return direction. > > I thought this worked.. struggling to understand why it is jammed up. > > On the same physical setup, if I kill VirtualT and start TeraTerm instead, > it works bi-directionally no problem. > > I may try Linux next. > > thx > Steve > > >
