[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Super Serial trouble.
- Subject: Re: Super Serial trouble.
- From: Linards Ticmanis <ticmanis@coli.uni-sb.de>
- Date: Tue, 26 Jun 2001 00:55:48 +0200
- Newsgroups: comp.sys.apple2
- Organization: University of Saarland, Computing Center, Germany.
- References: <3B375772.8BBE4638@coli.uni-sb.de> <8mMZ6.125533$DG1.20737149@news1.rdc1.mi.home.com>
- Xref: archiver1.google.com comp.sys.apple2:9483
william strutts wrote:
>
> I haven't figured out the PR#1 command. I was trying
> to do a similar thing with an HP Deskjet printer and nothing
> would happen.
According to the printer manual, after PR#1 everything that usually
appears on the screen is supposed to go to the printer. By inference,
I assume that the same is true if there is a terminal program on the
other end.
However in fact neither a printer (Apple ImageWriter) nor a terminal
program receive anything.
> In terminal mode on the PC, do you see anything being
> typed? It should be showing some characters. Have you
No, and that's the problem. I only see stuff typed on the PC appearing
Apple side of things, not the other way around.
> tried running a terminal program on both ends to see if
> you can type characters back and forth between the two
> systems? This would help you debug the speed and
Not yet, but as I said the Apple can receive with no trouble, which in
my admittedly limited understanding of these things would suggest that
the speed and parameters are right. I did write a short QBasic program
on the PC to experiment with speed settings and everything went as
expected, only it was a rather one sided experience, so to speak ;-)
> parameter settings. If they are correct, you would get
> ASCII characters on the screen and if not, you would
> get garbage characters on the screen.
I'm getting neither.
>
> Are you using Windows version of ADT if you're
> in Windows? I could never get DOS ADT to work for
> me in Windows because it wouldn't recognize my com
> ports correctly.
I've tried DOS ADT in both DOS and Windows, and also Unix ADT in
Linux. None of them worked and
the failure was always at the same point: The PC doesn't ever get any
commands from the Apple.
I also tried the APTEST disk from CALL-A.P.P.L.E. and all it had to
offer was "THE CARD TEST GOOD"
I also tried various null-modem and straight-through cables while
flipping back and force the jumper block as needed.
I also tried different slots and tried removing all other cards. I
tried Integer BASIC and Applesoft BASIC, the latter with or without
DOS loaded. I tried ProDOS. I tried setting different speeds with the
DIP switches and then followed suit in my little QBasic program. The
card always receives but it never sends.
I looked at the traces and joints again and I also checked the
ribbon-cable connector and the DB25 socket that came with the card.
Everything looks just fine.
The bottom line: I'm running out of ideas just what to check.
> "Linards Ticmanis" <ticmanis@coli.uni-sb.de> wrote in message
> 3B375772.8BBE4638@coli.uni-sb.de">news:3B375772.8BBE4638@coli.uni-sb.de...
> > Hi Group,
> >
> > I'm having trouble with the (original) Super Serial Card I just got.
> > No matter what I do, it seems that I can only receive data *to* the
> > (clone) Apple II+, but cannot send anything *from* the Apple. I have
> > tried 2 different PCs and different comm programs as well. Among
> > others I put a laptop right on top of the Apple and I attached the
> > little dangly bit from the SSC directly to the laptop COMM input (with
> > the jumper block on the SSC set to TERMINAL), so the cable is out.
> >
> > Receiving works just fine at any speed, setting, etc., I can type IN#1
> > on the apple and then remote-control it from the PC. However after I
> > do PR#1 the Apple output never shows up on the PC (or anywhere else
> > for that matter).
> >
> > Playing around with setting Hardware Flow-Control on and off, parity
> > settings, different slots, etc. just didn't work either. Also I
> > haven't found any broken solder joint etc. by inspection.
> > Unfortunately my multimeter is currently with my parents, and I don't
> > have an osci.
> >
> > ADT didn't work either so I'm pretty sure the fault is somewhere in
> > the Hardware. Do you have any ideas on what to check beyond broken
> > wires, oxidised contacts and bad solder joints?
--
Linards Ticmanis
The Master said, "The business of laying on the colors follows the
preparation of the plain ground."