We have exactly the same problem since the upgrade to 3.5.1b20. Long
standing members can no longer get on.
Contacted Livingston Support, they advised there is a know problem with the
current ComOs and HSP style modems manufactured/developed by PC TEL.
PCTEL developed these modems chipsets (technology) and then sells them off
to other manufacturers such as Zoltrix. They are most common as OEM's in
the Brand Name Boxes such as AST and Packard Bell (AST uses the Modem
Master 2000 based on PC TEL's HSP chipset)
These have got to be the cheapest modem yet, they no longer have their own
DSP chip and actually rely completely on the CPU's within the box. As a
result far more conflicts with other onboard peripherals. The most recent
bug reported was with HSP modems and S3 based video cards were you could
not get the modem to connect if you had the resolution set to higher than
256 colours.
Livingstons solution was to go to the respective HSP manufacturers website
and DL the latest drivers. We tried this several times with no success.
These HSP things just don't work especially with 3.5.1.b20!!!
PC TEL site at: http://www.pctel.com does acknowledge the flakeness of the
product and has released a driver patch (V2.16) that IMHO just don't fix
the problems... Although they make you go to the actually maker of the
modem to get the patch. They do list most of the manufacturers currently
buildling modems based on the HSP technology, ZOLTRIX being one of them.
I am surprised by Livingstons position of telling us to go get the newer
drivers (again that don't seem to work) when the modems did work prior to
beta20, seems to me the only difference is the new ComOs and therefore the
underlying cause of the problem. But that is just one mans opinion ;-)
And that is all I know about that!
--Bruce Burley
--Brand Communications Inc.
At 11:34 PM 8/10/97 -0500, Larry Vaden wrote:
>Here's the final report this evening from the field regarding 3.5.1b20:
>
>>Here is the rundown, first of all, when we say "lock up" the whole system
>>completely locks up with no response from the mouse, keyboard, etc.. Only
>>action was to hit the "reset" button. Dialing with the 2 commas resulted in
>>the same lockup. Dialing with 3 and 4 commas yielded results of where the
>>tones took twice as long but eventually returned a message "The computer
>>you are dialing is not answering". Dialing with 5 commas, however, results
>>in a successful connection but the first 3 sets of tones take about 3 times
>>as long and it restarts going straight through all the tones and
>>connecting. Any thing else, as you notice I am connected right now. My IP
>>address is: 206.65.116.107 .. best of luck.
>>
>>David W. Odom --|-- Co Manager, Customer Service
>>Internet Texoma --|-- http://www.texoma.net/
>>(903)813-4500 --|-- (972)542-4020 (972)484-3434
>>Sherman/Denison --|-- McKinney Dallas
>
>We'll fall back to b17 at 04:00.
>
>ldv
>
>