rc> You _do_ know that command tells the modem "connect at this
rc> speed, and if you can't, don't connect at all"?
AL> Umm.. no, I just started reading this area a couple of days ago.
RC> That's why I mentioned it. :-)
RC> "Forcing" the modem doesn't cause it to connect at a speed higher
RC> than it normally would. The idea of "forcing" is this: I have a
RC> large file to send. I don't want to accept a connection less than
RC> 28,800 (for example) because the transfer would take too long, so
RC> I'll tell the modem "if you can't connect at 28,800, don't connect,
RC> you'll be wasting my money". You'd normally do this sort of thing
RC> with "unattended" operation where the program will try later if it
RC> fails to connect the first time at the given speed.
Good thing the bill here is just flat rate/month.
RC> The modem determines the maximum speed it can connect at, depending
RC> on line conditions. None of the available commands will affect this,
RC> but they can be used to prevent an unwanted connection at a lower
RC> speed.
RC> Some modems also provide a "floor" command. You can then tell the
RC> modem "don't connect unless you can negotiate a speed between (floor)
RC> and (ceiling)". You could then configure the modem to accept between
RC> 14,000 and 28,800, for example.
Can you give me an example init string (your modem's)?
--- Maximus/2 3.01
---------------
* Origin: MACH2/VULCAN OS/2 SYSTEMS 1-403-489-4250 (1:342/61)
|