Could it be that your FT232R adapter is using a counterfeit chip? FTDI changed their drivers some time back so that they refuse to work with chips that are not manufactured by FTDI.

The cable is branded "Ugreen." I've had difficulties with USB to RS232 adapters in the past, which is why I bought it from the ADTPro website. I figured that it would be more likely to work straight away.

On a venture to the grocery store today, I stopped in at a Radioshack which was having a liquidation sale. I bought their "Gigaware" USB to serial cable for a decent discount at $20. As I understand it, this one uses a Prolific chipset which can occasionally be troublesome.. Thankfully, there appear to be drivers for it specifically for Windows 7.

Okay, it's working the ugreen one. I did a stupid and dropped the RXTXComm file in the wrong place. Well, since all sales are final at Radioshack these days, I've got an extra cable... Thanks again. If I didn't look into the things suggested, I probably wouldn't have found my screw-up! Joe Giliberti On Sat, Mar 11, 2017 at 5:24 PM, Adrian Graham <witchy at binarydinosaurs.co.uk> wrote: some

Not great news :( The computer recognized the serial port on COM5 and ADTPro says that it is connected. I am using the null modem cable from RetroFloppy for the //c and the Radioshack cable with the Prolific chipset (I switched over to this one because I thought this problem was caused by the other cable.) I set the working directory in ADT where the DSK files are and set the baud rate in Windows, ADT on the PC and ADT on the //c all to 19200. When I boot up the //c, I select (R)ecieve, punch in the filename, hit enter and...Host Timeout. Any idea what might not be working now? I really appreciate everyone's help Joe Giliberti On Sat, Mar 11, 2017 at 7:13 PM, Mike Whalen <mikew at thecomputervalet.com> wrote: cctalk at classiccmp.org> RS232 away. latest Windows others.

Any attempt to connect to view, send or receive results in a host timeout On Mar 11, 2017 9:15 PM, "Mike Whalen" <mikew at thecomputervalet.com> wrote: > > Are you getting host timeout when you attempt to list a directory? > > > On Sat, Mar 11, 2017 at 7:53 PM Joe Giliberti <starbase89 at gmail.com> > wrote: >> >> Not great news :( >> The computer recognized the serial port on COM5 and ADTPro says that >> it is connected. I am using the null modem cable from RetroFloppy for >> the //c and the Radioshack cable with the Prolific chipset (I switched >> over to this one because I thought this problem was caused by the >> other cable.) I set the working directory in ADT where the DSK files >> are and set the baud rate in Windows, ADT on the PC and ADT on the //c >> all to 19200. When I boot up the //c, I select (R)ecieve, punch in the >> filename, hit enter and...Host Timeout. >> Any idea what might not be working now? >> >> I really appreciate everyone's help >> >> Joe Giliberti >> >> On Sat, Mar 11, 2017 at 7:13 PM, Mike Whalen <mikew at thecomputervalet.com> >> wrote: >> > Great news! >> > >> > >> > On Sat, Mar 11, 2017 at 4:49 PM Joe Giliberti via cctalk >> > <cctalk at classiccmp.org> wrote: >> >> >> >> Okay, it's working the ugreen one. I did a stupid and dropped the >> >> RXTXComm file in the wrong place. >> >> Well, since all sales are final at Radioshack these days, I've got an >> >> extra cable... >> >> >> >> Thanks again. If I didn't look into the things suggested, I probably >> >> wouldn't have found my screw-up! >> >> >> >> Joe Giliberti >> >> >> >> On Sat, Mar 11, 2017 at 5:24 PM, Adrian Graham >> >> <witchy at binarydinosaurs.co.uk> wrote: >> >> > On 11/03/2017 21:52, "Joe Giliberti via cctalk" >> >> > <cctalk at classiccmp.org> >> >> > wrote: >> >> > >> >> >> The cable is branded "Ugreen." I've had difficulties with USB to >> >> >> RS232 >> >> >> adapters in the past, which is why I bought it from the ADTPro >> >> >> website. I figured that it would be more likely to work straight >> >> >> away. >> >> > >> >> > I've had difficulties with everything I've used from ugreen, the >> >> > latest >> >> > being an HDMI-DVA adapter which just didn't work 100%. Trouble is >> >> > with >> >> > some >> >> > of these ebay buys you don't know who made it until it lands on your >> >> > mat. >> >> > >> >> >> On a venture to the grocery store today, I stopped in at a >> >> >> Radioshack >> >> >> which was having a liquidation sale. I bought their "Gigaware" USB >> >> >> to >> >> >> serial cable for a decent discount at $20. As I understand it, this >> >> >> one uses a Prolific chipset which can occasionally be troublesome.. >> >> >> Thankfully, there appear to be drivers for it specifically for >> >> >> Windows >> >> >> 7. >> >> > >> >> > Prolific! That's the chipset name I was trying to remember earlier. >> >> > Seems >> >> > that most ADTPro folks have more success with that one than the >> >> > others. >> >> > >> >> > -- >> >> > Adrian/Witchy >> >> > Binary Dinosaurs creator/curator >> >> > Www.binarydinosaurs.co.uk - the UK's biggest private home computer >> >> > collection? >> >> > >> >> >

On 12/03/2017 01:52, "Joe Giliberti via cctalk" <cctalk at classiccmp.org> wrote: You can check if the PC is talking to the //c by doing a bare metal speediboot - this will check the comms are working: http://adtpro.sourceforge.net/bootstrap.html Can you do a lookback test on the USB adapter by looping pins 2&3 then using PuTTY to talk to itself? -- Adrian/Witchy Binary Dinosaurs creator/curator Www.binarydinosaurs.co.uk - the UK's biggest private home computer collection?

On 12/03/2017 20:57, "Joe Giliberti via cctalk" <cctalk at classiccmp.org> wrote: I've replied on FB but for completeness and historical recording I'll put it here too. Granted the PC currently in use is a 32bit XP machine so I could make sure everything was working on a real 16550 UART before going over to the USB adapter but I'll try a win 7 64bit machine when I get the chance. My adapter is a clone one with the CH340 chipset used and abused on arduino clones so I already had the driver package, it was discovered as COM4. Fire up ADTPro via the .bat file, go to serial setup to make sure COM4 is selected along with '//c with imagewriter cable' then plug in the //c and boot to the ] prompt followed by: IN#2 <CTRL-A>14B On the PC go to 'bootstrapping -> ProDOS -> speediboot' and hit OK...up she comes. I've just seen a message from David Schmidt, if anyone knows why yours doesn't work he will given that he wrote ADTPro in the first place :) Cheers -- Adrian/Witchy Binary Dinosaurs creator/curator Www.binarydinosaurs.co.uk - the UK's biggest private home computer collection?