PR>> there? -------------------------------------------------------- CT> You need the latest .INF file so that WIN 95 can report the correct CT> speed. CT> You'll actually have to re-install the modem and direct the "Have CT> Disk" function so that the .INF file is used. A whopping two CT> minutes of your time . . . [g] Got the latest file,or one that works anyway! It only took 90 seconds as well . Thanks for your input Clay! Later preilly@logicallink.com ... Halleluja! Put your HANDS on the MODEM! --- GEcho/32 1.20/Pro * Origin: *TimeLine* USR Courier V.Everything (1:140/89) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: EGS00005 Date: 12/22/97 From: BOB SEABORN Time: 08:20am \/To: GEORGE FLIGER (Read 8 times) Subj: Connect Rates? >BS> A Sportster is NOT a Courier (or vice versa), and I'd >BS> suggest the windoze .inf files aren't all that up-to-date >BS> when it comes to a Courier. > > Wasn't there a thread earlier mentioning that an updated .INF file was > available from USR's website that corrected this problem? I think so. > > I didn't keep copies of the thread but I'm sure that there are others > out here that can confirm something along these lines. As I run OS/2 here, I didn't really pay attention. :) .....Bob --- GEcho/32 & IM 2.50 * Origin: Canadian RegSite for AllFix & Gecho (1:140/12.1) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: EGS00006 Date: 12/22/97 From: MICHAEL EPLER Time: 04:42am \/To: JEFF MCCLAIN (Read 8 times) Subj: Update Wizard works in OS -> Uh, hhmm...... that's nice if you have allocated space to include Win -> 3.x If not, still a problem without native support. JM> Could not find a work around for this. But you must agree that this will JM> fix most users without a dual boot machine. JM> Jeff McClain JM> 3Com Online Support I'm not trying to be argumentative, but this answer blindly misses the whole target. Why would a Warp or Merlin user care about win 3.x?? You still need to offer native support in OS/2. The OS is still more functional in various respects than either W95 or NT (which is why it still -HAS- a user base of onwers more likely than not to also own one of your modems), and the european market has a large installed base of OS/2 users. Or has 3Com conceded that market to Hayes? --- Maximus 2.02 * Origin: DelaMarPenn MicroNet -+- Newark, Delaware (1:150/115) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: EGS00007 Date: 12/22/97 From: RUNER NATIVIDAD Time: 10:16pm \/To: CRAIG FORD (Read 8 times) Subj: Fax @ 9600 CF>Did you receive the response I sent you in COMM? Yes. Thank you. I replied to it. Regards, Runer --- * QMPro 1.53 * "Engage"? But Captain, I haven't even dated her yet! --- InterEcho 1.19 * Origin: Fidonet (2:542/100) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: EGS00008 Date: 12/22/97 From: RUNER NATIVIDAD Time: 10:16pm \/To: CRAIG FORD (Read 8 times) Subj: Speed limit Season's Greetings Craig... CF>* Forwarded (from: COMM) by Craig Ford using timEd/2 1.10+. CF>* Originally from Craig Ford (1:106/2001) to Runer Natividad. CF>* Original dated: Wed Dec 17, 23:57 Thank you! I really appreciate your effort a lot! :) CF>Runer Natividad wrote the following to All, and I quote (in part): CF> RN> Can anyone kindly tell me the *Init strings* to LIMIT my modem's CF> RN> FAX (MODE) speed to a MAXimum of only 9600 with fallback enabled CF> RN> when it receives a fax. CF>AT+FDCC=1,3,0,2,0,0,0,0 Now my question, (If you woulnd't mind)... I tried to type it in my terminal window, it returned an error. :( Shall I only enter this strings from the INIT Field of my FAX program? MERRY CHRISTMAS to you and the family circle! Best wishes, Runer --- * QMPro 1.53 * Bo knows Taglines! --- InterEcho 1.19 * Origin: Fidonet (2:542/100) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: EGS00009 Date: 12/22/97 From: JEFF MCCLAIN Time: 07:17am \/To: LEE LAWSON (Read 8 times) Subj: Update Wizard works in OS -> Just a quick question, if you don't mind..... Is the update Wizard -> going to be needed in the future for update to the Courier line? I -> wouldn't think so, but it never hurts to ask. No, the Courier team will still build the SDL program and the X-Modem versions of the updates. Although,the wizard will soon be able to support Couriers again. Jeff McClain 3Com Online Support --- FidoPCB v1.5 beta-'j' * Origin: U.S.Robotics Support-USA 847-982-5092 (1:115/500) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: EGS00010 Date: 12/21/97 From: FRANCOIS ROY Time: 11:39pm \/To: MARK LOOFBURROW (Read 9 times) Subj: Maxwell Smart calling Control ! ML> This sounds like a classic flow control problem to me. Make sure that ML> you are using Hardware flow control with your Courier (AT&f1) and your ML> Comdriver is using hardware flow control as well. I don't think so. Everything has been working fine for years; the problems started with my one uplink when he switched to a Sportster 33.6k. It's almost like the Sportster is sending some weird code sequence and the Courier firmware goes into a CPU loop trying to figure it out. --- Msged 4.00 * Origin: Ready & Determined (819) 772-9277 (1:163/506) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: EGS00011 Date: 12/19/97 From: EDWARD HOBSON Time: 10:12am \/To: MIKE MYERS (Read 9 times) Subj: fresh UK code? Mike Myers wrote in a message to Edward Hobson: MM> Erm? Thats not entirely true.. I know for a fact that I don't MM> bother posting in there BECAUSE there is no USR representative Then it's a vicious circle. USR representatives would certainly be more involved in Fido discussion groups if there was sufficient call for it. There just isn't! EH> equipment in order to support both standards. Their Ascend K56flex lines EH> are flailing misrably MM> Hmm, strange that. Demon Internets Ascend modems seem to be Yeh, Ascend's V.34 seems to be pretty solid with them now, as they've fixed the usual Rockwell related symbol rate faults. No complaints there, rtainly. MM> Hmmm, well to be honest Edward its the same old thing again, us MM> commoners on the street see nothing of what USR UK or Europe are MM> doing. You may be getting Beta code left right and centre, we see The x2 release code from earlier this year is a good solid release. The work that has been done since then largely concerns evaluating feedback on its performance and testing changes to tweak performance. There's not a lot that could have been released. There will be further releases, but they will be issued when they will actually be of some benefit, rather than just to demonstrate that work is ongoing. MM> nothing for months on end. Its always been like this within the UK MM> and no doubt it always will be. Most people's ideal hardware solution is one that you can plug in and forget about. I personally would not find it agreeable for USR to release new code for each different hardware platform every couple of months. It would be a nightmare to support, and people would be constantly nagged with the usual "try the latest revision before complaining" excuse. Edward --- * Origin: Informe // 01606-836633 (2:250/701) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: EGS00012 Date: 12/22/97 From: DAVE BEACH Time: 09:35pm \/To: ALL (Read 9 times) Subj: Sportster 33.6 Can anyone advise how to enable/disable online fallback/fallforward for a Sportster 33.6 data/fax modem? ATI6 link diagnostics consistently report "Fallback disabled", and if I'm interpreting that correctly it means that the modem is not negotiating the fallback feature during handshake, which is annoying considering that most of the other modems I connect to (Couriers, et al.) report "Fallback enabled" in *their* link diags. --- GoldED 2.50 UNREG * Origin: Wanna NEC? (1:163/222) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: EGS00013 Date: 12/22/97 From: GENE LOWRY Time: 05:45pm \/To: FRANCOIS ROY (Read 9 times) Subj: Maxwell Smart calling Control ! In a message of Francois Roy (1:163/506) writes: FR> Which, I found out today, is a Sportster 33.6k. It appears to always FR> happen after the Sportster gets 12 Link Timeouts and gets p*ssed off FR> with me. Any idea what constitutes a "Link Timeout"? It's in the area of protocol detection (and problems with same). Things like communications momentarily interrupted. Beyond that I"d be quoting the manual to you again and you can read as well as I can. FR> Are they reading this echo? If not, what's the procedure (preferably FR> one that won't cost me a half-hour of LD charges being on hold). You'd FR> expect that the problem would affect not just me, as it is part of the FR> behaviour of our latest firmware. They seem to be, although somewhat infrequently. Try addressing the message to Technical Support and give them what details you can. Happy Holidays, Gene Lowry --- msged 2.07 * Origin: Bigfoot's RBBS - Tucson,AZ - HST/V.34 - <8:902/1> or (1:300/11) In a message of Rick Graham (1:3815/123) writes: RG> No pain at all, set one echo area up and when you want to add another RG> you simply clone the one that's setup. Or use the FIDOUTIL to add RG> message areas right out of the Backbone.Na file. You too, Rick. This is too far afield, let's get back to USR/3Com modems shall we? Gene Lowry --- msged 2.07 * Origin: Bigfoot's RBBS - Tucson,AZ - HST/V.34 - <8:902/1> or (1:300/11)