![]() |
At 11:36 16.08.00 -0600, Lee Howard wrote: >At 01:15 PM 8/16/00 -0400, Jay R. Ashworth wrote: > >> Hey, I have the same problem :) The remote just doesn't understand the > >> gibberish setup the USR is sending... > >> I think those modems just aren't very compatible with the other ones. > >> IIRC, they always had that problem, also for data connections... > > > >Well, I can't speak for the Sportsters (of which I believe that > >internal is one), but the Couriers always performed flawlessly with > >data connections. > > > >I was searching the mailing list archive the other day for something > >else, and saw several postings that people were running just fine with > >USR products; it might be productive for those of you having problems > >to do some searching there and see what you find. > >I've got a 3Com-USR 56K modem internal that's working fine with HylaFAX in >Class 2.0. They do fine with faxing and they do fine with data. Their >biggest downside is the lack of error checking and reporting in the >firmware - which has been the biggest difficulty in getting Class 2.0 >modems to work with HylaFAX (because the firmware lies about its >capabilities). > >As a plus, though, I have noticed that 3Com-USR modems in general are much >more tolerant of line noise and static, and so I've rarely seen any >corrupted scan lines on any fax received by a 3Com-USR modem. We have downgraded to Class 1.0 to make it work, but still encounter problems. If you have a working configuration, it would be nice to make it available to everyone. Matthias J�nichen ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null