Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!tut.cis.ohio-state.edu!ucbvax!CIVIL.UBC.CA!twong
From: twong@CIVIL.UBC.CA (Thomas Wong)
Newsgroups: comp.sys.apple2
Subject: Conclusion: PR#2 on //c with Hayes compatible doesn't work
Message-ID: <1189*twong@civil.ubc.ca>
Date: 5 Aug 90 04:30:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 37

First of all, I must say that I'm surprise by the lack of response
on both of my questions (PR#2 using applesoft and //c's 5 pin DIN
connector pin out). Only two fellows answered the first question
and the first of those two fellows, Andy Tefft, answered the second.
Whatever happened to the Reign of the Apple Hacks? Am I getting that
old? There used to be tons of Apple gurus, local computer groups/clubs,
Apple BBSs all over, tons of Apple pirates, and we were all hacks.
We all lived by Applesoft, peek and pokes, assembly, and opening the
cover to play around with the hardware to make it do whatever we want.
Has all the Apple // hacks really all converted over to IBM/MACs?

Oh well, enough reminiscing over the good old days. Here is what
I was trying to do. Dump strings to the modem in Applesoft.
Simple enough. Here is the simple test program:

10 PRINT CHR$(4);"PR#2"
20 PRINT "ATDP1234567" : REM I have a pulse dial phone line

and variations thereof. That should work. But not for me.
Andy also has a //c and this program works for him. So we compared 
notes (system configuration). Everything is the same accept one last
variable. I have a Hayes compatible and he has an Apple modem. Note 
that the serial port of a //c is a 5 pin DIN connector, the Apple
modem has a 9 pin RS-232, and my Hayes compatible has a 25 pin
RS-232. I conclude that there could be two reasons why Hayes doesn't
work and Apple modem works. Logically, going from 9 pins to 5 pins
should have less of a consequence than from 25 pins to 5 pins.
And second, Apple products better work on Apple computers.
But alas, I guess ignoring 20 (actually 19 since 1 pin is a also
a GND) signals provided to be one too many signals to ignore
for PR#2 to work. But since communication programs can choose to 
ignore these signals, they all work fine on my //c.

Oh well, my weekend program, which turned into a half month project
is finally over with. Scrapped.

Thomas.