GA> Could you please look in you binkley.log and see what's happening
GA> with my packet xmission? When my system sends its outgoing packet
GA> (usually small ie less than 4k) it gets all manner of zmodem retries
GA> due to CRC errors. The larger files I get from you process without
GA> any CRC errors. So most likely it is in my ZModem send.

The usual cause of that symptom, uploads awful, downloads fine, is that
you dont have the handshaking between the modem and the comms prog
right. On an upload that means that the modem cant tell the comms prog
to pause and so data gets lost, giving a visible symptom of a Zmodem
error, CRC errors. Doesnt affect downloads coz the modem doesnt need to
tell the comms prog to pause, so it doesnt matter if it cant.

You want hardware handshaking in the modem and the comms prog.

GA> Sometimes the session is aborted due to excessive retries, which
GA> means I need to try again manually. A real pain.

Thats just a secondary level problem, the fundamental problem is just
dropped chars, and so CRC errors. If its bad enough it gives up instead
of retrying.

GA> Also, sometimes after an attempted session (due to BUSY returned or
GA> something) my modems "Originate" light is out, indicating that the
GA> modem is set to "Answer" mode. Also when this happens, the modem is
GA> continuously trying to lock on, scanning up and down. I can hear the
GA> busy tone of the unsuccessful call over the top (underneath?). The
GA> modem won't then retry to dial, it just leaves the line looped until
GA> manual intervention.

Sounds like just a brain dead modem. Didnt you say you were using those
Exicom specials ?

GA> I have a PCTools for Windows timed event set up to fire off Front
GA> Door at time "x", and I set the event in FD to fire up and talk to
GA> you one minute past "x". I have "Exit with ErrorLevel
32" set in the
GA> event, so in theory FD is only running for the event duration + 1
GA> minute. I can then use a terminal program without worrying about port
GA> conflict, which I always ran into with FD running 24hrs/day. I kept
GA> forgetting to close it down before I ran the term prog.

GA> I wonder if somethinh in this arrangement is stuffing up the port,
GA> and thus the initial connect and the initial ZModem xfer (which is
GA> always TO you)?

Its possibly some subtle interaction with the Windows comm port config.
Try with plain old DOS, not a Win DOS box, and see if that changes the
symptoms.

--- PQWK200