Re: //c telecom programs... (was Re: no one said it was foolproof....)

[Chris Morse <chris@cosmicwolf.com>]

On Mon, 4 Aug 2003 17:33:15 -0400, "Bill Garber"
<willy46pa@comcast.net> wrote:

(Large and powerful SNIP)
>I'm not sure what that was all about but I've been fine at 9600
>all along, never had to go at 300 baud, which by the way takes
>like 45 minutes to transfer DOS 3.3. I think I used ADT once,
>and that was to get Comm.System to my only Apple IIgs back
>when I got started, last year was it? Yeah, that's it. If you need
>further help I'm always in the books and trying new things on
>these. I must have several hardware and software things going
>on all the time. I just can't stop. ;-)
>
>Bill @ GarberStreet Enterprises };-)
>Web Site - http://garberstreet.netfirms.com
>Email - willy46pa@comcast.net
(Large and powerful SNIP)

Well, my current Quest is to get a "comm" program running on my //e so
that I can see keystrokes on both ends.  On the PC I type HELLO and it
shows up on the //e, and vice-versa.

So far I have tried...

(1) ProTERM v3.1 (couldn't get anything reliable working)
(2) COMM.SYSTEM (from the modem_util.dsk on Asimov that you sent me)
(3) Z-Link (PC didn't see Apple //e keystrokes)

This morning I tried the next comm program in line (having grabbed all
that I saw from Asimov).  The program is Apple Access II v0.99B.  AND
IT WORKS FINE!

Right-out-of-the-box, Access II v0.99B worked fine.  I wonder what is
different about the various comm programs.  I used Hyperterm on the PC
and it worked fine; so I ran my test program and FINALLY started
seeing the test message being sent show up on the Apple //e screen.

I think I have one more comm program to try-- VisiTerm.. unless I dig
up some more.. But so far Access II is the only one that seems to
work.  Anyone know what gives??

My goal is to write a Windows gateway program for the Apple //e.  I
just don't understand why I can get so few communications programs
working over a direct null-modem link.

// CHRIS