Along these lines, my ISP also just upgraded their modems to all V.90.
During this period there were numerous connect problems, such as
disconnects, busy signals and slow connect speeds. I just recieved a letter
from them explaining that they had to get software written for whatever
their modems are from 3Com. A friend who has the misfortune of having only a
14.4 modem still has problems. We tried numerous AT strings at their
sugguestion, nonw of which helped. Whereas my USR v.90 fax modem, non
winmodem, connects consistantly at either 46.6 or 49.3. So I believe that
older hardware may have compatibility problems with the newer standards.
Brad Loomis

Will wrote:
> I work for an ISP that recently tried (and tried and tried) to upgrade to
> the v.90 protocol. I have never heard of WFW being unable to connect with
> the v.90 standard simply because the operating system has little
> to do with
> the actual connection. What I mean by this is that the ISP's modems don't
> care what OS you have, merely what modem you have - more specifically the
> language the modem speaks. I believe that modem protocols are not OS
> specific.
>
> One of our problems in the v.90 fiasco was that USR modems often failed to
> make a connection, which is why we downgraded to kflex. You might
> have your
> sister ask her ISP to research a modem init string that would allow her to
> connect.
>
> Here are some possibilities to try:
>         AT&F1S32=98
>         ATS27=32
>         ATS28=115
>
> These may not work, but it's worth a shot. Good luck!
>
> Will Stephenson
> [log in to unmask]
>
>
> Has anyone heard of an ISP's upgrading to V.90 causing customers
> running Windows for Workgroups to lose their ability to connect?

                                  -----
                PCBUILD mailing list -  http://nospin.com
         Bob Wright:[log in to unmask] - Drew Dunn:[log in to unmask]