Re: SSC Failure - odd symptoms

[Polymorph <polymorph69@hotmail.com>]

On Aug 20, 11:52 am, Zero dB <n...@email.com> wrote:
> Greetings all,
>
> I have been transferring all of my old favorites to some fresh NOS
> polaroid floppies I scored en masse from ebay. having a blast with
> sneakers, death in the caribbean, aztec, etc. :)
>
> I left it alone for a few days, then came back to it. Just for kicks,
> I took out the mainboard and all the peripherals to blow out the
> system with my snazzy new air compressor.
>
> Re-assemble everything, and now I can't transfer images to or from ADT
> on my PC with a known-good cable/pc config.
>
> I can get an SSC: prompt via "IN#2, ctrl-a" i think it was. It
> responds to commands. But, no transfers. ADT just sits there "Awaiting
> response from PC".
>
> I tried other slots for the SSC (which is usually in slot 2), same
> thing. The disk controller, the motherboard and everything that i can
> sense is working just fine, except for transfer initiation on the SSC.
> ADT "sees" the card to the point that it knows there is a card there
> (that is to say, it doesn't give the 'empty slot' error), but still
> just sits there "awaiting answer from PC"
>
> I have verified the cable and serial port in question on another term
> server and all is well.
>
> It it possible for the SSC to fail in such a way that transfers won't
> work, but the logic still does ?  I can "session" into the card and
> get a responsive prompt, but can't transfer.
>
> To re-iterate, this was a prior working config. I verified the PC
> serial port and cable are still good with another term server (and
> concurrent 'wiggle test' to verify not positional)
>
> Thanks for any insight!
>
> Jayson
>
> jayson dot anderson AT removethis gmail com

Sounds like a classic case of "if it ain't broke, don't fix it!".  ;-)

Having said that, it is unusual for such a scenario to happen, so
let's make sure it is a hardware problem first up, or if its just a
configuration issue.

Some things to check/try:
* Are the commuincation parameters (baud rate, etc) set the same on
both host & client?
* Have you tried connecting to the Apple II via a terminal program? -
i.e. typing IN#2 and then trying to connect via a terminal program on
the host (e.g. HyperTerm in Windows) using the correct communication
parameters as specified by the switches on the SSC. You should be able
to type stuff on the host and see it appear on the Apple II if things
are working.
* Did you accidentally switch the jumper with the arrow on it the
wrong way during cleaning?
* Is the cable you're using a null modem cable or straight through?
Double check the jumper with the arrow to ensure its sets correctly
(check the docs if you need to).

Let us know what you the results of the above checks show up.

Cheers,
Mike