At 12:56/15/May, Bill Grimsley (3:640/305.9) said:
====================================
BG> David, at 06:28 on May 14 1998, you wrote to Bill Grimsley...
JK>>> In the case of USR modems, &F0 initiates software flow control.  
BG>> My Sportster's on-line help screen (AT&$) suggests otherwise... 
BG>> &F0 = *NO* flow control
BG>> &F1 = Hardware flow control
BG>> &F2 = Software flow control
BG>> Are the Couriers' &Fn templates not the same?
DD>> Mine says:
DD>> n=0  Load Factory Configuration
DD>> n=1  Hardware Flow Control Cnfg.
DD>> n=2  Software Flow Control Cnfg.
DD>> n=3  HST/Cellular w/ HW FC Cnfg.
BG> I can understand the Sportster not supporting an HST template, but I'm 
very 
BG> surprised that &F0 is obviously different between Sportsters and 
Couriers.  
I don't see "obviously different" at all.  What does "Factory Configuration" 
mean, after all?
The &F0 for the Sportster is defined as "Generic template" and it affects 
lots more than just flow control.
BG> I wonder what genius threw in that little gotcha, especially given that 
BG> even the Windows *.inf files for all USR modems has the init string 
listed 
BG> as AT&F, which presumably defaults to &F0 in the absence of a qualifier 
(or 
BG> is it &F1 - I can't for the life of me remember now?).
Not in any .INF I've seen.  Here's mine (snipped from MODEMLOG.TXT):
   ----- MODEMLOG.TXT begins -----
05-09-1998 19:28:28.95 - U.S. Robotics 56K FAX EXT #2 in use.
05-09-1998 19:28:29.15 - Modem type: U.S. Robotics 56K FAX EXT
05-09-1998 19:28:29.15 - Modem inf path: 3COMCO~1.INF
05-09-1998 19:28:29.15 - Modem inf section: ModemPCMex
05-09-1998 19:28:29.42 - 115200,N,8,1
05-09-1998 19:28:30.31 - 115200,N,8,1
05-09-1998 19:28:30.34 - Initializing modem.
05-09-1998 19:28:30.34 - Send: AT
05-09-1998 19:28:30.48 - Recv: OK
05-09-1998 19:28:30.48 - Interpreted response: Ok
05-09-1998 19:28:30.48 - Send: AT&F1E0Q0V1&C1&D2S0=0
05-09-1998 19:28:30.62 - Recv: OK
   ----- MODEMLOG.TXT ends -----
Quite often provided init strings _did_ start with AT&F, but then went on to 
add the necessary flow control settings.  This was true with Compuserve's 
CIM, which originally _didn't_ support hardware flow control at all.  So the 
init provided configured for software flow control.
Rick
--- Msged 4.00
---------------