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

[Chris Morse <chris@cosmicwolf.com>]

On Mon, 4 Aug 2003 10:24:16 -0400, "Bill Garber"
<willy46pa@comcast.net> wrote:

(SNIP)
>I sent you an email with a .DSK image that should help.
>Good Luck and let me know if you need anything further.
>
>Bill @ GarberStreet Enterprises };-)
>Web Site - http://garberstreet.netfirms.com
>Email - willy46pa@comcast.net
(SNIP)

Pray tell what software it is?

I've been writing a Windows COM program to talk on the serial port
using a null modem to my Apple //e...

If I just go into BASIC and enter "IN#2" and then CTRL-A 6B to set the
super serial card to 300 baud, my Windows COM program successfully
communicates with the Apple //e.

If I boot and run ProTERM v3.1 (latest version), it has major problems
with the connection.  My test app on Windows just sends the string
"SEND TEST" + <CR> over the line.  Like I said, under BASIC it works
fine but under ProTERM it comes out as "SDSTSSSN" in a VERY SLOW
manner.  And YES, both are set for 300 baud and 8-N-1.  The characters
are right -- the "SDSTSSSN" string all have characters from the string
being sent ("SEND TEST").. just not coming out right!  I tried using
ProTERM's "Null Modem Driver" and "Null Modem Driver (RTS/CTS)".  And
to add to the strangeness, if I hold down the space key on the Apple
//e, I get spaces but also see more of the characters being sent.. so
it looks like "S E N D  T E S T   S E D  T E T  S D T E S T".

So.. I guess I'm also looking for some other Communications software,
at least so I can compare results.

Thanks for any help you can offer!

// CHRIS