--------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F4B00031 Date: 04/06/98 From: GENE LOWRY Time: 07:27pm \/To: LUDOVIC BRAUN (Read 8 times) Subj: V.90 upgrade In a message of Ludovic Braun (2:320/409) writes: GL> Each SDL for the Courier is a complete, self contained package. No GL> SDL to date requires that any other specific SDL has been loaded GL> into the modem. LB> One exception though: Xmodem updates require code no older than LB> 02/96 in the Courier line. That's very true, thanks Gene Lowry --- msged 2.07 * Origin: Bigfoot's RBBS - Tucson,AZ - HST/V.34 - <8:902/1> or (1:300/11) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F4B00032 Date: 04/07/98 From: MARK LEWIS Time: 12:21am \/To: BRUCE WILSON (Read 6 times) Subj: Same Names BW> On 5 Apr 98 08:49pm, MARK LEWIS wrote to MARK LEWIS: ML>> errr... are we still having this "problem" of the same names?? ML>> <> BW> So it seems. It also seems it's been a long time since we had BW> a "newbie" in an echo who got all flustered on encountering BW> messages seemingly to him/her about which he/she knew nothing. :-) <<>> hopefully their sysop can/will explain it to them OB-) )\/(ark * Origin: (1:3634/12) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F4B00033 Date: 04/07/98 From: ARTHUR MARSH Time: 02:39pm \/To: CLAY TANNACORE (Read 6 times) Subj: USR arrogance On Wed 01 Apr at 20:28 Clay Tannacore (1:18/4) wrote to Jonathan Michaels: AM >> Some astute people from outside of the USA (such as AM >> Telstra's Frank Nitzsche) have noticed the USR AM >> Couriers guess the wrong kind of line conditions and AM >> fail miserably. Does 3COM/USR have processes in place AM >> to learn from such problems and incorporate fixes AM >> into their code? CT> I'd suggest that Mr. Nitzsche should flash his Courier with CT> a country specific code if he wishes to avoid problems in CT> the future, or not attempt to use a USA/Canada model in some CT> other country. Frank Nitzsche has more experience with line impairments and modem behaviour than anyone else in Australia (having worked his way up from being a linesman to a senior engineer at Telstra with over 30 years experience), and yes, he was using Australian SDL's (which have been pitifully late, few, and far between). Unless 3COM/USR takes into account a good test coverage of line types for each of the countries it sells its modems in, it is *not* providing its non-North American customers with the best possible product. --- msgedsq 2.1 * Origin: Camelot Swamp MJCNA, Hawthorndene, Sth Australia (3:800/812) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F4B00034 Date: 04/07/98 From: ARTHUR MARSH Time: 02:44pm \/To: ALL (Read 6 times) Subj: S3=043 and drop-out Hi, when I call a USR Courier which has S3=043 set and do a +++ from my non-Courier modem, I have recently experienced an immediate disconnect. Is this expected behaviour, and is there anything that can be done besides setting the S3 register to a different value to prevent a disconnection when doing +++? --- msgedsq 2.1 * Origin: Camelot Swamp MJCNA, Hawthorndene, Sth Australia (3:800/812) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F4B00035 Date: 04/07/98 From: ARTHUR MARSH Time: 02:53pm \/To: TOM RUTHERFORD (Read 6 times) Subj: Re: V90 On Wed 01 Apr at 16:14 Tom Rutherford (1:2240/320) wrote to Gene Lowry: TR> I saw a message from one of the engineers at MichNet, our TR> statewide dial-up modem provider. He said that, due to TR> interoperability problems with their GDC racks (the V.8 TR> handling caused the modems to negotiate a V.32bis TR> connect, if they connected at all; looked like he was TR> reading right off the page of release notes with the TR> 3/13/98 flash!), users were advised to disable V.90 TR> until the new GDC code was installed. The old code TR> hadn't even been installed in the Flint modem pool yet. TR> :-) But, he said that, due to the fact that modems TR> have to be taken offline to be flashed (Duuuhhh!), TR> they'd be doing the upgrades in the wee hours of the TR> morning, and it would take six weeks to do it. The GDC folks are pretty good with upgrades, but it is difficult when the various manufacturers don't provide each other with interoperability testing. --- msgedsq 2.1 * Origin: Camelot Swamp MJCNA, Hawthorndene, Sth Australia (3:800/812) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F4B00036 Date: 04/06/98 From: BARBARA MCNAY Time: 06:50am \/To: GENE LOWRY (Read 9 times) Subj: Courier vs Zoom CRCs & Disconnects > In a message of Craig Ford (1:106/2001) > writes: > GL> This may or may not be part of your problem, original NS16550A > GL> chips had problems with the implementation of the FIFO, I'd think > GL> you should be looking for an NS16550AN or later chip. > CF> It was the origianl NS16550 that had the problem (I had one in an IBM > CF> Model 60), the 16550A is quite suitable. > I stand corrected, thanks. > CF> To shed a bit more light on the subject though, _none_ of the modems > CF> that I've tried have been able to sucessfully transfer a file over > 100Kb > CF> to Bill without aborting (it doesn't appear to be a modem problem). > Curious, very curious, I wonder what the problem > really is... A limit, perhaps, on the size of the file transfer per session? <---<< Barb >>---> --- * Origin: The Barb >>---> T E X A S (1:395/48) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F4B00037 Date: 04/06/98 From: BRUCE WILSON Time: 10:34pm \/To: LEE KELLER (Read 6 times) Subj: Re: Help! On 4 Apr 98 06:58am, LEE KELLER wrote to BRUCE WILSON: > On 2 Apr 98 05:07pm, LEE KELLER wrote to GENE LOWRY: > > LK> I spoke to a representative of 3Com about a month ago in regard > LK> to the proceedure that I needed to take to upgrade my Courier > LK> v.everything modems to 56K status. I purchased one of them on > LK> the sysop program directly from USR and the other two from a > LK> local VAR. > > Which upgrade, from V.34 to x2 and V.90 or from x2 to V.90? All one > has to do is run the new SDL for the latter. The former requires a > $60 payment per modem, obtaining an x2/V.90 enable key, and calling > the USR (3Com) bbs with each modem to use the key to enable x2/V.90 > in the modem. LK> V.34 to V.90 on two of them and x2 to V.90 on the remaining unit. The x2 to V.90 upgrade's simple. Just download and the SDL, via the web, ftp, or a direct call to the bbs, and run it. The V.34 to V.90 is going to cost $60 each unless you got in on the free x2 upgrade last year (in which case it seems they'd already be x2) and your not having been given the x2 enable key's the problem or you bought them recently enough that they qualify for a free upgrade. * Silver Xpress V4.4P [Reg] --- Platinum Xpress/Win/Wildcat5! v2.0 * Origin: Get All Your Fido Here! telnet://docsplace.dynip.com (1:3603/140) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F4B00038 Date: 04/07/98 From: WILLIAM GRINOLDS Time: 06:42am \/To: NAM TRAN (Read 6 times) Subj: Line Test.. Nam Tran wrote in a message to All: NT> I hear that USR has a line test # to see if your modem is actually NT> a x2, v.90. Could someone post the #? I believe the number is 1-888-877-9248. Log in as LINE TEST. Bill Internet: wgrinolds@pobox.com --- * Origin: ST:TNG Mail System (USR Courier V.E with x2) (1:387/601.2) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F4B00039 Date: 04/07/98 From: BOB JUGE Time: 07:20am \/To: MIKE MYERS (Read 6 times) Subj: I-Modem not answering Mike Myers wrote in a message to Bob Juge: MM> 02-Apr-98 04:09:18, Bob Juge wrote to Kari Suomela MM> Subject: I-Modem not answering BJ> As I responded in the ISDN echo, the internal I-Modem does not supply BJ> ring voltage to its POTS jack MM> Hmm, not very clever? Does the External model do the same? No, the external model does supply ring voltage. That's why it's the only one offered on their sysop discount program. - Bob Internet : bob@juge.com Telnet, Vmodem, WWW or FTP to juge.com --- timEd/2 1.10+ * Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F4B00040 Date: 04/07/98 From: JIM MARRS Time: 04:21am \/To: CLAY TANNACORE (Read 6 times) Subj: Problems connecting with some modems? Clay Tannacore wrote in a message to Jim Marrs: CT> Jim, I don't know if it'll help you any, but for me it did. Try CT> entering the ATS54.6=0&W to the modem. Also do a ATY15 and see CT> what your dip switches are set at. Thanks for trying Clay but I tried and still no ARQ with this one particular system that I connect with. The dip switches are set for the factory default and I adjusted the s54 register but still get a 28800 with no ARQ with the system I am having troubles with. He is running a Cardinal 28.8k modem and says that he can connect fine with everyone else. In fact he connected fine with me as well when I was running a Hayes Optima 56k. We have only had trouble since I switched to the V.Everything modem? He is running Intermail and I am running Binkleyterm 2.60dos. We do connect at 28800 but I get no ARQ light and then instead of handshaking correctly we get flooded with ascii garbage. I switched Binkley to NOEMSI and we conencted alright a few times but it caused trouble with a PCboard system that I feed and it didn;t totally cure the problem with the intermail so I had to switch EMSI back on. Thanks again, Jim --- * Origin: Lost in the Supermarket - Peabody, MA (1:101/101)