On Jul 01 13:29, 1997, Jay Fuller of 1:3607/22 wrote:
RC>>Flow control, almost without a doubt.  What is your init string? 
RC>>What setting do you have for flow control in your comm program?  If
RC>>your modem is external, it's _possible_ the cable between the modem
RC>>and the PC doesn't have a full complement of wires.  RTS/CTS requires
RC>>the modem and PC to assert lines, and if the cable doesn't have those
RC>>lines, then the RTS/CTS flow control simply won't work.
JF> I use ATZ normally, except I changed the init string after reading a
JF> reply you fellas made to someone else....I changed it to AT&K3. (using
ATZ is meaningless if you don't know what was first stored in the profile.  
If your init was ATZ, it's just not possible to say with any confidence how 
the modem is configured.  Same with adding &K3 - though that command is 
probably a good idea, the only thing you can say with any assurance is that 
the modem is configured to use &K3 - the other settings are still a mystery.
When configuring a modem, it's always wise to _start_ with a factory default, 
like AT&F1 for the Sportster.  That command sets the modem to a "known" 
state, and from there you modify the remaining settings as necessary.  So, 
the initial configuration command (issued in Terminal mode) might look like 
this:
AT&F1 &K3 
That will configure the modem to the default settings for hardware flow 
control (the &F1) and then modify those defaults to change the &Kn setting to 
&K3, to allow only V.42bis data compression.  Once that's done, _save_ the 
configuration to a profile (you can do it in the same command string, so the 
string would actually look like this):
AT&F1 &K3 &W 
That saves the configuration to Profile 0.  Then, in you comm program, you 
would define the init to load that saved profile:
ATZ1^M
(I'm referrring to the Sportster, here, where ATZ1 loads Profile 0).  You 
could, if you liked, simply use the AT&F1 &K3 ^M as your init string in the 
comm program - it's your choice.  _Don't_ add the &W if you do this, though.
JF> Incidently...I've "solved" the problem by using DSZ.COM - here's how. 
JF> (I'm the SysOp of Deep Space Nine, so I have a little knowledge of DSZ)
JF> I use dsz port 2 speed 28800 sz (filename) -- that will send whatever
JF> file just fine, and I see XOFF appear from time to time. 
JF> In my qmodem setup, Xon/Xoff is OFF, CTS / RTS is on. I've actually
JF> aided people with modem setup before, so I know what "should" work and
JF> what "shouldn't" -- so therefore, I'd REALLY appreciate getting this
JF> worked out. 
You shouldn't be seeing that XOff at all.  Use the string I've mentioned 
above and ensure the comm program is configured for RTS/CTS flow control and 
all should work well.
Rick
--- MsgedSQ 3.30
---------------