ADTPro woes [message #380572] |
Sun, 03 February 2019 15:19 |
dawjazz
Messages: 10 Registered: February 2013
Karma: 0
|
Junior Member |
|
|
I can't get ADTPro to work with my IIGS. I've connected the FTDI USB-serial adapter cables to the IIGS modem port and USB jack on the PC. I start up ADTPro 2.01, ensure the serial configuration is to COM5, reboot the IIGS, enter ctrl-reset.
When I enter IN#2 on the IIGS, spurious characters appear. Apparently, data is being sent and I can't stop it. I've tried the Ctrl-A 14B commands to no avail. The IIGS keeps beeping and displaying characters.
Any suggestions?
I've tried this on a windows 10 64-bit and windows XP 32-bit with same results
Thanks,
Dale Wilkins
|
|
|
Re: ADTPro woes [message #380593 is a reply to message #380572] |
Sun, 03 February 2019 19:19 |
|
Originally posted by: J. Random Hacker
On 2019-02-03 20:19:34 +0000, dawjazz said:
> [...]
> Any suggestions?
> I've tried this on a windows 10 64-bit and windows XP 32-bit with same results
I have had great results using this tool to transfer images between an
old MacBook and an Apple 2 Plus. It transfers via audio cable:
https://github.com/datajerk/c2t
Don't know about 2gs compatibility though...
|
|
|
Re: ADTPro woes [message #380594 is a reply to message #380572] |
Sun, 03 February 2019 19:57 |
David Schmidt
Messages: 993 Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On 2/3/19 3:19 PM, dawjazz wrote:
> [...]
> When I enter IN#2 on the IIGS, spurious characters appear. Apparently, data is being sent and I can't stop it. I've tried the Ctrl-A 14B commands to no avail. The IIGS keeps beeping and displaying characters.
Sounds like your serial port (on the GS) might be bad. Have you done
tests with various cables plugged in and not to figure out where the
problem is? It would be interesting to know what element is presenting
the bytes to the SCC chip in the GS.
|
|
|
Re: ADTPro woes [message #380597 is a reply to message #380594] |
Sun, 03 February 2019 20:50 |
|
Originally posted by: Anthony Adverse
There's always the good ol' standby of loopback testing. Short the TX/RX pins and you should get an echo response out of anything you type. You can test each element along your cabling to find which piece isn't behaving.
A
|
|
|
Re: ADTPro woes [message #380599 is a reply to message #380593] |
Sun, 03 February 2019 20:55 |
|
Originally posted by: Anthony Adverse
On Monday, February 4, 2019 at 11:19:43 AM UTC+11, J. Random Hacker wrote:
> On 2019-02-03 20:19:34 +0000, dawjazz said:
>> [...]
>> Any suggestions?
>> I've tried this on a windows 10 64-bit and windows XP 32-bit with same results
>
> I have had great results using this tool to transfer images between an
> old MacBook and an Apple 2 Plus. It transfers via audio cable:
>
> https://github.com/datajerk/c2t
>
> Don't know about 2gs compatibility though...
Sounds like its using the cassette interface, a GS doesn't have one.
|
|
|
Re: ADTPro woes [message #380604 is a reply to message #380572] |
Mon, 04 February 2019 00:41 |
dawjazz
Messages: 10 Registered: February 2013
Karma: 0
|
Junior Member |
|
|
On Sunday, February 3, 2019 at 12:19:35 PM UTC-8, dawjazz wrote:
> I can't get ADTPro to work with my IIGS. I've connected the FTDI USB-serial adapter cables to the IIGS modem port and USB jack on the PC. I start up ADTPro 2.01, ensure the serial configuration is to COM5, reboot the IIGS, enter ctrl-reset.
>
> When I enter IN#2 on the IIGS, spurious characters appear. Apparently, data is being sent and I can't stop it. I've tried the Ctrl-A 14B commands to no avail. The IIGS keeps beeping and displaying characters.
>
> Any suggestions?
> I've tried this on a windows 10 64-bit and windows XP 32-bit with same results
>
> Thanks,
>
> Dale Wilkins
Success!
I removed the USB to RS-232 adapter and connected the IIGS directly to the PC's 9-pin serial port using the null modem cable and was able to transfer ADTPro. No spurious characters. These are new cables--apparently there is noise when using a USB serial connection so I'll stick with the RS-232 connection from now on. Unfortunately, my Windows 10 PC doesn't have an RS-232 port.
Thanks for all the suggestions.
Dale
|
|
|
Re: ADTPro woes [message #380607 is a reply to message #380572] |
Mon, 04 February 2019 02:55 |
|
Originally posted by: groink_hi
It is reasons like this why I still hang onto a 15-year old Dell Latitude laptop running XP Pro and a real serial port. This is what I use for ADT Pro.
|
|
|
Re: ADTPro woes [message #380636 is a reply to message #380604] |
Mon, 04 February 2019 10:08 |
David Schmidt
Messages: 993 Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On 2/4/19 12:41 AM, dawjazz wrote:
> On Sunday, February 3, 2019 at 12:19:35 PM UTC-8, dawjazz wrote:
>> I can't get ADTPro to work with my IIGS. I've connected the FTDI USB-serial adapter cables to the IIGS modem port and USB jack on the PC. I start up ADTPro 2.01, ensure the serial configuration is to COM5, reboot the IIGS, enter ctrl-reset.
>>
>> When I enter IN#2 on the IIGS, spurious characters appear. Apparently, data is being sent and I can't stop it. I've tried the Ctrl-A 14B commands to no avail. The IIGS keeps beeping and displaying characters.
>>
>> Any suggestions?
>> I've tried this on a windows 10 64-bit and windows XP 32-bit with same results
>>
>> Thanks,
>>
>> Dale Wilkins
>
> Success!
>
> I removed the USB to RS-232 adapter and connected the IIGS directly to the PC's 9-pin serial port using the null modem cable and was able to transfer ADTPro. No spurious characters. These are new cables--apparently there is noise when using a USB serial connection so I'll stick with the RS-232 connection from now on. Unfortunately, my Windows 10 PC doesn't have an RS-232 port.
FTDI is my go-to chipset - where did the USB cable come from?
|
|
|
Re: ADTPro woes [message #380642 is a reply to message #380636] |
Mon, 04 February 2019 11:19 |
dawjazz
Messages: 10 Registered: February 2013
Karma: 0
|
Junior Member |
|
|
On Monday, February 4, 2019 at 7:08:14 AM UTC-8, schmidtd wrote:
> On 2/4/19 12:41 AM, dawjazz wrote:
>> On Sunday, February 3, 2019 at 12:19:35 PM UTC-8, dawjazz wrote:
>>> I can't get ADTPro to work with my IIGS. I've connected the FTDI USB-serial adapter cables to the IIGS modem port and USB jack on the PC. I start up ADTPro 2.01, ensure the serial configuration is to COM5, reboot the IIGS, enter ctrl-reset.
>>>
>>> When I enter IN#2 on the IIGS, spurious characters appear. Apparently, data is being sent and I can't stop it. I've tried the Ctrl-A 14B commands to no avail. The IIGS keeps beeping and displaying characters.
>>>
>>> Any suggestions?
>>> I've tried this on a windows 10 64-bit and windows XP 32-bit with same results
>>>
>>> Thanks,
>>>
>>> Dale Wilkins
>>
>> Success!
>>
>> I removed the USB to RS-232 adapter and connected the IIGS directly to the PC's 9-pin serial port using the null modem cable and was able to transfer ADTPro. No spurious characters. These are new cables--apparently there is noise when using a USB serial connection so I'll stick with the RS-232 connection from now on. Unfortunately, my Windows 10 PC doesn't have an RS-232 port.
>
> FTDI is my go-to chipset - where did the USB cable come from?
The Apple2Online Store. It included the FTDi USB-Com232-DB-9 cables and adapter, and amini CD-ROM containing drivers
|
|
|
Re: ADTPro woes [message #380646 is a reply to message #380642] |
Mon, 04 February 2019 12:55 |
David Schmidt
Messages: 993 Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On 2/4/19 11:19 AM, dawjazz wrote:
> On Monday, February 4, 2019 at 7:08:14 AM UTC-8, schmidtd wrote:
>> On 2/4/19 12:41 AM, dawjazz wrote:
>>> On Sunday, February 3, 2019 at 12:19:35 PM UTC-8, dawjazz wrote:
>>>> I can't get ADTPro to work with my IIGS. I've connected the FTDI USB-serial adapter cables to the IIGS modem port and USB jack on the PC. I start up ADTPro 2.01, ensure the serial configuration is to COM5, reboot the IIGS, enter ctrl-reset.
>>>>
>>>> When I enter IN#2 on the IIGS, spurious characters appear. Apparently, data is being sent and I can't stop it. I've tried the Ctrl-A 14B commands to no avail. The IIGS keeps beeping and displaying characters.
>>>>
>>>> Any suggestions?
>>>> I've tried this on a windows 10 64-bit and windows XP 32-bit with same results
>>>>
>>>> Thanks,
>>>>
>>>> Dale Wilkins
>>>
>>> Success!
>>>
>>> I removed the USB to RS-232 adapter and connected the IIGS directly to the PC's 9-pin serial port using the null modem cable and was able to transfer ADTPro. No spurious characters. These are new cables--apparently there is noise when using a USB serial connection so I'll stick with the RS-232 connection from now on. Unfortunately, my Windows 10 PC doesn't have an RS-232 port.
>>
>> FTDI is my go-to chipset - where did the USB cable come from?
>
> The Apple2Online Store. It included the FTDi USB-Com232-DB-9 cables and adapter, and amini CD-ROM containing drivers
Gotcha. That's the second report of bad cables coming from there:
https://github.com/ADTPro/adtpro/issues/13
|
|
|
Re: ADTPro woes [message #380725 is a reply to message #380604] |
Tue, 05 February 2019 18:04 |
|
Originally posted by: James Davis
On Sunday, February 3, 2019 at 9:41:29 PM UTC-8, dawjazz wrote:
> On Sunday, February 3, 2019 at 12:19:35 PM UTC-8, dawjazz wrote:
>> I can't get ADTPro to work with my IIGS. I've connected the FTDI USB-serial adapter cables to the IIGS modem port and USB jack on the PC. I start up ADTPro 2.01, ensure the serial configuration is to COM5, reboot the IIGS, enter ctrl-reset.
>>
>> When I enter IN#2 on the IIGS, spurious characters appear. Apparently, data is being sent and I can't stop it. I've tried the Ctrl-A 14B commands to no avail. The IIGS keeps beeping and displaying characters.
>>
>> Any suggestions?
>> I've tried this on a windows 10 64-bit and windows XP 32-bit with same results
>>
>> Thanks,
>>
>> Dale Wilkins
>
> Success!
>
> I removed the USB to RS-232 adapter and connected the IIGS directly to the PC's 9-pin serial port using the null modem cable and was able to transfer ADTPro. No spurious characters. These are new cables--apparently there is noise when using a USB serial connection so I'll stick with the RS-232 connection from now on. Unfortunately, my Windows 10 PC doesn't have an RS-232 port.
>
> Thanks for all the suggestions.
>
> Dale
Did you try putting the adapter (attached directly) on the W10 computer and using a null-modem cable from it to your GS?
|
|
|
Re: ADTPro woes [message #380729 is a reply to message #380725] |
Tue, 05 February 2019 19:41 |
dawjazz
Messages: 10 Registered: February 2013
Karma: 0
|
Junior Member |
|
|
On Tuesday, February 5, 2019 at 3:04:52 PM UTC-8, James Davis wrote:
> On Sunday, February 3, 2019 at 9:41:29 PM UTC-8, dawjazz wrote:
>> On Sunday, February 3, 2019 at 12:19:35 PM UTC-8, dawjazz wrote:
>>> I can't get ADTPro to work with my IIGS. I've connected the FTDI USB-serial adapter cables to the IIGS modem port and USB jack on the PC. I start up ADTPro 2.01, ensure the serial configuration is to COM5, reboot the IIGS, enter ctrl-reset.
>>>
>>> When I enter IN#2 on the IIGS, spurious characters appear. Apparently, data is being sent and I can't stop it. I've tried the Ctrl-A 14B commands to no avail. The IIGS keeps beeping and displaying characters.
>>>
>>> Any suggestions?
>>> I've tried this on a windows 10 64-bit and windows XP 32-bit with same results
>>>
>>> Thanks,
>>>
>>> Dale Wilkins
>>
>> Success!
>>
>> I removed the USB to RS-232 adapter and connected the IIGS directly to the PC's 9-pin serial port using the null modem cable and was able to transfer ADTPro. No spurious characters. These are new cables--apparently there is noise when using a USB serial connection so I'll stick with the RS-232 connection from now on. Unfortunately, my Windows 10 PC doesn't have an RS-232 port.
>>
>> Thanks for all the suggestions.
>>
>> Dale
>
> Did you try putting the adapter (attached directly) on the W10 computer and using a null-modem cable from it to your GS?
The null-modem cable that attaches to the IIGS is a mini-din--the other end is a 9-pin serial cable. There is NO 9-pin serial connector on the Windows 10 PC, so I tried using the USB to RS-232 adapter without success. Here's the cable link:
https://www.ebluejay.com/ads/item/5058024
|
|
|
Re: ADTPro woes [message #380785 is a reply to message #380729] |
Wed, 06 February 2019 17:21 |
|
Originally posted by: James Davis
On Tuesday, February 5, 2019 at 4:41:45 PM UTC-8, dawjazz wrote:
> On Tuesday, February 5, 2019 at 3:04:52 PM UTC-8, James Davis wrote:
>> On Sunday, February 3, 2019 at 9:41:29 PM UTC-8, dawjazz wrote:
>>> On Sunday, February 3, 2019 at 12:19:35 PM UTC-8, dawjazz wrote:
>>>> I can't get ADTPro to work with my IIGS. I've connected the FTDI USB-serial adapter cables to the IIGS modem port and USB jack on the PC. I start up ADTPro 2.01, ensure the serial configuration is to COM5, reboot the IIGS, enter ctrl-reset.
>>>>
>>>> When I enter IN#2 on the IIGS, spurious characters appear. Apparently, data is being sent and I can't stop it. I've tried the Ctrl-A 14B commands to no avail. The IIGS keeps beeping and displaying characters.
>>>>
>>>> Any suggestions?
>>>> I've tried this on a windows 10 64-bit and windows XP 32-bit with same results
>>>>
>>>> Thanks,
>>>>
>>>> Dale Wilkins
>>>
>>> Success!
>>>
>>> I removed the USB to RS-232 adapter and connected the IIGS directly to the PC's 9-pin serial port using the null modem cable and was able to transfer ADTPro. No spurious characters. These are new cables--apparently there is noise when using a USB serial connection so I'll stick with the RS-232 connection from now on. Unfortunately, my Windows 10 PC doesn't have an RS-232 port.
>>>
>>> Thanks for all the suggestions.
>>>
>>> Dale
>>
>> Did you try putting the adapter (attached directly) on the W10 computer and using a null-modem cable from it to your GS?
>
> The null-modem cable that attaches to the IIGS is a mini-din--the other end is a 9-pin serial cable. There is NO 9-pin serial connector on the Windows 10 PC, so I tried using the USB to RS-232 adapter without success. Here's the cable link:
>
> https://www.ebluejay.com/ads/item/5058024
Gotcha. I was thinking the adapter was an all in one (USB to RS232) without a cable.
|
|
|