[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ADT 1.22 finally working on IIC - Thanks --> Phoenyx / Rubywand / Delfs!!
My problem in getting null-modem communications to happen between my IIC and
PC-setup is finally resolved.
ADT is now running currently at 9600 bps, and I'm producing new disks on the
fly! Really awesome!!
---> I would especially thank alias 'Phoneyx', 'Rubywand' and 'Delfs.' for
their kind support during my 'ordeal' of constructing a working cable, which
for the 'novice' is indeed not an easy task, but definitely worth the
effort!
Here is a summary of the work done:
--->Rubywand supplied a French URL 'Apple IIc. dsk Site' where the correct
pin-assignment is given for the IIc DIN-5 and the necessary DSBUB 9F or 25M:
Rubywand wrote:
> http://www.multimania.com/apple2c/tech/Transfert.htm
>
> The Apple IIc .dsk Archive site seems to be using this numbering on the
> DIN-5 connector.
>
> 1 3
> 4 5
> 2
--> I then constructed a new shielded five-lead cable with the given PIN
assignment setup, for a Dsub25 plug with the correct shorting of pins. This
cable design basically correspond to the wiring for a standard
serial-printer cable (type: Imagewriter-I).
'The shorting of the pins is required to let the PC-side think there is a
modem on the other side responding (thus a null-modem function.)
> DIN-5M Dsub9 or Dsub25
> (Apple) 9 pins 25 pins
>
> 4 (2) TXD --> 2 RXD 3 RXD
> 5 (4) RXD <-- 3 TXD 2 TXD
> 2 (3) GND --- 5 GND 7 GND
> 1 (1) DTR --> 6 DSR --,* 6 DSR --,*
> 1 DCD --' 8 DCD --'
> 3 (5) DSR/DCD <-- 4 DTR 20 DTR
>
>* pins connected by a jumper
After making sure the cable was according to the specification I connected
it to the Dsub9M-connector using a gender-changer and a Dsub 25-->9 pin
converter
I then entered the Apple II ''adt.dump' source with the Win98
'Hyperterminal' software acc. to the 'readme.txt'-file, and checked the
transfer with the ADTCK checksum programme on the IIc wich reported the
correct values.
But the software failed to get communications to start when trying both in
Win98 DOS mode and in the recommended MSDOS-mode (in my case MS-DOS 6.22)!
Typical errors were when issuing 'Directory'-command within ADT, the A2
screen went black indicating no response from the PC-side. Also for the
'Receive'-command the programme reported "Awaiting signal from PC'
During troubleshooting I found out that there obviously was a working
two-way connection by forcing text-file transfer using 'Hyperterminal' to
the ADT "Receive" or "Directory" wait-state and by sending sample-files the
opposite way from the IIC around issuing a 'send' command from ADT to the
'Hyperterminal.
This confirmed that the cable was OK, but something was wrong on the
COM-port setup:
I discovered that I had different numbering of the onboard COM-ports in DOS
vs. Win98, that is, in DOS COM #1,#2 corresponds to the WIN98 COM #3,4.
I removed the ports in Win98 Setup, turned off the PC, installed a second
Hewlett-Packard serial-card and jumpered it to work as "COM1" and in PC
XT-mode.
When rebooting the system the new COM1- port operated in both
OS-environments with the same designation.
I hope my case-description may be useful for others in trying to get their
ADT -working!
Best regards
This seemed to crack the case, and let the ADT communicate over the cable as
supposed.