Checking V.90/V.92 Dropout Problems

The Problem, with Solution.

V.92 modems are suffering similar problems with an extra twist. Very few ISPs have upgraded their V.90 host-modems to V.92. This means that a V.92 client-modem usually has to connect with a V.90 host-modem. It should, of course, gracefully drop back to V.90... Instead, strange V.92/V.90-hybrid connections are being made (sometimes with call-waiting notifications). In addition, some modems (the AMR/CNR Smartlink modems are a particular example) are having AOL-connect problems, probably for the same reason.

The fix for both V.90 & V.92 is easy - get an updated driver - but a bit difficult if the modem will not connect (catch 22). The fix for both is also easy - slow the modem with an init string to V34, which will give a reliable (if slow) connection, then get the updated driver, then remove the init string. This is probably best even for the V.92 modems, by the way - V34 will avoid all problems.

• Use the table below to find the init string. On win95/98/Me/XP systems this goes into the Extra Settings box.

  Note: Windows^® is supposed to prepend the string in the Extra Settings box with an "AT" (in other words, you don't add it because Windows^® does it for you). From experience with different models, this is not always the case. If unsure, leave the AT out - if the modem then locks up, go back & add it (the modem will be unharmed).

• Get an updated driver:
  • If you know the manufacturer use this index
  • If you know the model use this index
  • If the modem's unknown try What's My Modem?
• Remove the init string after updating.