Hello Paul!

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

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

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

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

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

Any ideas?

Sea Ewes are round!
Geoff.

--- FMail 0.92