> Hi,
>
> I would like to know if someone have problem whit this
>
> US Robotic WinModem model usr2090, usr568302 and usr2974
first, WinModems are crap, get a decent one? ;)
Okay, not an option.
Then search through the archives of portmaster-modem and portmaster-users.
This once, I'll paste something I saved for the init strings:
From: "Jamin A. Brown" <jamin@gwi.net>
Subject: Re: (PM) USR modems not connecting with ComOS3.8.2 - need init
string?
USR 56K modems tend to work well with our system *except* for the
Winmodems. Even so, we often have to put in an init string on all of them
to get them to connect more reliably.
S32=34 Disables X2 (Which helps for some reason)
S32=66 Disables v.90
S32=98 Disables Both X2 and v.90
S13=64 Disables Fast Retrain (helps prevent disconnections)
&N## Sets a maximum speed, replace ## with 30 for 45333, 29 for
44000... etc.
> They all have problem connecting.
>
> The 2974 allways connect at V.34 driver date 02/03/99 the most recent i
was able to found
> The 2090 always connect at less then 39933, driver date 28/07/97 the
most recent i was able to found
> The 568302 connect 20% of the time at v.34 and when he connect at v.90
( 37333, 42666, 44000) but if i connect at this speed when donwloading if
i got 0.5 K/s i'm lucky, driver date 05/12/98
Check out those driver dates and think.. all pre-v.90 ratification date,
except for the 2974.
> If someone have a solution that can help resolve this problem, or if
you have idea to correct the problem.
You need to learn to use the archives first 8)
and which ComOS in particular 3.8 or 3.9? well, actually not much
difference in the modem code...
-- Aloha from Paradise,Sherwood Got Clue? If so: ISPF! The Forum for ISPs by ISPs, <http://www.ispf.com>
- To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-modems' in the body of the message.