Well thanks Kurt. I'll do some reading. What is on my mind is to make a real TPDD usable as B: in CP/M. Lp
But a tpdd2 could also work. On Friday, January 8, 2021, Kurt McCullum <ku...@fastmail.com> wrote: > TPDD1 or 2? I ask because I've done quite a bit of work with a TPDD2. The > TPDD Client software that I wrote will drive a TPDD2 in both modes. It has > the ability to read/write all the sectors on a disk to make a copy. Not > sure if that helps you or not but thought I would mention it. > > http://www.club100.org/memfiles/index.php?&direction= > 0&order=&directory=Kurt%20McCullum/TPDD%20Client > > Kurt > > On Fri, Jan 8, 2021, at 4:38 PM, Stephen Adolph wrote: > > I did see that and tried it. no luck so far but I will keep plugging > away. I seem to recall this worked for me in the past. > > What I am trying to do is drive a real TPDD in FDC mode, and use VT to > observe the transactions. > > > On Fri, Jan 8, 2021 at 7:23 PM Ken Pettit <petti...@gmail.com> wrote: > > Hardware flow control? I think VT has a checkbox to ignore CTS / RTS. > Did you try that? > > Ken > > On 1/8/21 4:19 PM, Stephen Adolph 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 > > >
