Thanks Daryl. Until your post I didn't know the chip was in the cable. I'd thought it was part of the Dell m/board.
Funny - when I inserted the usb/serial cable (the one with the Prolific chip) into my Win10 laptop, the laptop immediately recognized it, installed a driver, added it to Device Manager ports, and said "ready for use". When I tried a different usb/serial cable, the laptop didn't recognize it - didn't show up in Device Manager at all, even after I had uninstalled the Prolific one. (Imagine how much simpler this would have been if I'd used the 25 pin serial instead of the 9 pin connector. I'd completely forgotten that the 102 came with a barcode scanner port. That port is the *only* unlabeled port on the 102.) I am chomping at the bit now, waiting for the gender changer to arrive, so I can finally test and use the 102 Telcom to Win10 TeraTerm connection. Thanks. Tom M. On Fri, Apr 5, 2019 at 9:56 PM Daryl Tester < [email protected]> wrote: > On 6/4/19 5:48 am, Thomas Morehouse wrote: > > > To help my overloaded brain ... when folks refer to "the Prolific > > problem" ... is that a reference to the usb/serial cable? or > > to a chip on the Windows machine? > > Hi Thomas. > > I'm not sure this got specifically answered for you. The "Prolific > problem" refers to the brand of chip inside your USB cable > (specifically, located inside the DB9 connector), and is the USB > to serial converter. FTDI is the other manufacturer, whose drivers > and chips tend to "work better". There are a variety of manufacturers, > but FTDI tend to be less problematic (note the lack of absolutes in > this description). > > (And good to see you got the potential issue diagnosed). > > Cheers, > Daryl. >
