--------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F2F00045 Date: 02/11/98 From: DOUG REYNOLDS Time: 01:35pm \/To: JOHN DUKE (Read 8 times) Subj: ? JD> Will the USR modems be upgradable th the new VCMP or whatever it is JD> standard???????? Actually, it is now called V.90. it was supposed to be v.pcm. the maverick # http://www.microserve.net/~mav/ # mav@microserve.net ... Moderator not found. Enter forbidden topics? [Y/n] --- Telegard v3.09.b15/mL * Origin: the rebel multiline 1X % 3.100Gs % 412/459.7290 (1:2610/38) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F2G00000 Date: 02/09/98 From: TOM RUTHERFORD Time: 06:41pm \/To: JOHN ALDRICH (Read 11 times) Subj: "New" Courier On 06 Feb 98 18:46:49, John Aldrich said this to TOM PARKER about ""New" Courier": JA> Hello TOM! JA> Wednesday February 04 1998 08:17, TOM PARKER wrote to ALL: TP> Going to http://x2.usr.com shows the S/N group to be upgradeable to TP> x2, but what does the Dual Standard mean? JA> It supports their proprietary HST (16.8kbps) connect as well as the JA> industry standard connects of 300-33600. John Nope. If 33.6K is the top end, it's a V.Everything. When I got this modem, it was called Dual Standard, and it supported HST at 16.8K and V.32bis. It also had V.32terbo, but the two "standards" they were talking about were the industry standard V.32bis and the de-facto "standard" of HST. -=> Tom Rutherford -- Team OS/2 <=- ... Nominating Data for Moderator, he has an off button. --- Blue Wave/OS2 v2.30 * Origin: Gateway To Mid-Michigan, Burton,MI(810)742-6126 (1:2240/320) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F2G00001 Date: 02/10/98 From: RICK COLLINS Time: 08:54pm \/To: JOHN DUKE (Read 8 times) Subj: ? At 13:02/09/Feb, John Duke (1:116/305) said: ==================================== JD> Will the USR modems be upgradable th the new VCMP or whatever it is JD> standard???????? V.90. Yes. Indeed, any X2 3COM/USR modem can be upgraded to V.90 _free_. There are no doubt some older USR modems that cannot be upgraded, just as there were some that could not be upgraded directly to V.34 or X2. In those cases the upgrade path may be a new modem, or it may be a "daughter card", depending on the modem. Rick --- Msged 4.00 * Origin: The Warlock's Cave, Ottawa ON (1:163/215.39) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F2G00002 Date: 02/10/98 From: RICK COLLINS Time: 08:59pm \/To: BOB WINGENDER (Read 8 times) Subj: What a load of bollox V.PCM is turning i20:59:1702/10/98 At 22:00/09/Feb, Bob Wingender (1:284/11) said: ==================================== MM>> Its about time modem manufacturers grew up and started working with each MM>> other. BW> Why? That's a bunch of 'shite' because if we didn't have competition, it BW> might get stagnate. I suppose you would want General Motors to 'work BW> together and make one car for all? That would be a crock.. On the other hand, one car does not "interface" with another car, does it? Meanwhile, isn't it nice that consumer electrical products all come with a _standard_ plug that plugs into a _standard_ socket? Rick --- Msged 4.00 * Origin: The Warlock's Cave, Ottawa ON (1:163/215.39) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F2G00003 Date: 02/11/98 From: JOHN DUKE Time: 11:53am \/To: GENE LOWRY (Read 8 times) Subj: ? GL+According to statements made here over the past few months by USR personnel, +all x2 modems will be able to upgrade to V.pcm (V.90) at no +charge when the upgrade is available. With the ink still +wet on the recommendation, I wouldn't look for the upgrade +this week though. + Gene Lowry I'm not going to be dropping mu ISDN line anytime soon... John Duke KE4TQP john.duke@nashville.com * 1st 2.00n #2317bt * Proud member of P.E.T.A. People for Eating Tasty Animals --- Maximus/2 3.01 * Origin: NUT N' MUCH BBS Madison TN (615 868-8370 ISDN/Analog) (1:116/305) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F2G00004 Date: 02/11/98 From: TECHNICAL SUPPORT Time: 01:52pm \/To: BRUCE WILSON (Read 10 times) Subj: Re: Your Courier @1:106/2000 On 02-10-98 BRUCE WILSON said: BW> TS> ... However, I also notice you are using &K3, which disables BW> TS> only one type of compression. Is there any reason you can not BW> TS> try &K1 which will allow for automatic negotiation? BW>Once again, EFMBI and with all due respect, &K3 has been recommended BW>by USR since the earliest days of the V.E. modems (notwithstanding BW>that &K1 is the default). I quote from the Courier manual: BW>&K3 Selective data compression. The modem negotiates only BW> for V.42bis compression and disables MNP Level 5 BW> (MNP5) compression. Use this setting to transfer 8-bit BW> binary files, ZIP files, and other files that are already BW> compressed. BW>This is because data throughput's reduced when MNP5 is enabled and BW>tries to compress "files that are already compressed." BW> TS> Sarah K. BW> TS> 3Com Online Support BW>--- Blue Wave v2.12 BW> * Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 BW>(1:106/2000) ---------------------------2/11/98 -------------------------- Hello Bruce, Thank you for contacting 3Com Online Support. I understand that you have a question about your modem. Before we can provide any further diagnosis or troubleshooting for the problem(s) you are experiencing, we will need more information from you, namely: The full serial and model numbers of the modem The name of your faxing software program, if any The COM/IRQ settings of the modem if on a PC Brand, type of system, operating system and processor speed Listing of other peripheral devices on your system (soundcards,video cards,scanners,printers,etc.) The specific nature of the problem(s) you are experiencing (list all error messages and where you are receiving them) Please include all previous correspondence regarding this issue both your messages and the responses received. Thank you, Mike C. 3Com Online Support Chris P. On-Line Support CMPQwk 1.42 9087 --- 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: F2G00005 Date: 02/11/98 From: TECHNICAL SUPPORT Time: 02:00pm \/To: DAVE BEACH (Read 7 times) Subj: . @1:163/222 On 02-10-98 DAVE BEACH said: DB> TS> I have made a note of this element. Please see the other DB> TS> posting for some suggestions. DB>Er, which other posting? You've posted no suggestions to me so far DB>(well, this go 'round anyway). DB> TS> **Please paste all previous correspondence in your reply.** DB>I think not. We'd quickly wind up with messages our mail tossers DB>couldn't handle due to their size. DB>--- GoldED 2.50 UNREG DB> * Origin: Wanna NEC? (1:163/222) ---------------------------2/11/98 -------------------------- Hello Dave, Thank you for contacting 3Com Online Support. I understand that you are still having trouble with your modem and that all past suggestions have not resulted in a resolution of the problems you are having. Before we can conclude that there is something wrong with the modem, the possibilities of software configuration, system problems, port address conflicts in the bios, and incorrect connection settings need to be ruled out. Once again, we need a complete description of the problems and any progress made in these areas, along with the complete modem model and serial number. The only reason I am emphasizing the importance of software configuration is that correctly configuring the software to run with the modem is absolutely vital to the modem operating properly. In addition, you mention in previous postings that the problems were only occurring with two specific connections with this modem and program. This would also be indicative of a software configuration/setup problem. Once again, if all else fails, then it is also possible that something could be wrong with the modem itself. If you have not had the modem for more than 30 days, you should be able to exchange it at the place of purchase for another modem. If you have had the modem for more than 30 days, you will need to set up an SRO (service repair order) to have the modem sent in for repair. Please direct your SRO request to our customer service department. You should address it to support@usr.com with the subject of "SRO". Please include all previous correspondence regarding this issue both your messages and the responses received. Thank you, Mike C. 3Com Online Support Chris P. On-Line Support CMPQwk 1.42 9087 --- 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: F2G00006 Date: 02/11/98 From: TECHNICAL SUPPORT Time: 02:08pm \/To: FRANCOIS ROY (Read 10 times) Subj: Your Courier @1:163/506 On 02-10-98 FRANCOIS ROY said: FR>FR>>Follow-up to message from Dave Beach: FR>FR>>DB> need, but your NVRAM settings, init, etc. would probably be FR>FR>>DB> great for a start. FR>FR>>There's really nothing out of the ordinary in my Init, except FR>FR>>resetting a few parameters that sometimes get changed by Dial FR>FR>>prefixes for stubborn nodes: FR>FR>>Init ATE0&N0S0=0S54=64S56=0#CID=1 FR>FR>>I always answer with Adaptive Fax on (+FC:ASS=2.0) but that FR>FR>>shouldn't have anything to do with it, as the problem can occur FR>FR>>on outbound as well as inbound calls. I should point out that FR>FR>>most transfers have him (Sportster) transmitting and me (Courier) FR>FR>>receiving. FR>FR>>The most frustrating part is that, sometimes, the transfer goes FR>FR>>like greased lightning, and other times, I'll see the odd FR>FR>>retransmit request from Binkley (which in itself is strange, as FR>FR>>you'd expect the modems to handle all error-correction). FR>FR>>Aborted sessions invariably die in one of two ways: with my end FR>FR>>citing "Invalid Codeword" as the reason for disconnect, or with FR>FR>>Binkley timing out while waiting for a packet (when this occurs, FR>FR>>I can clearly see the LEDs showing my Binkley asking for a FR>FR>>re-send of the packet, and his end shipping it to me - it's as if FR>FR>>the packet was consistently sent with the wrong CRC or something) FR>FR>>ati4 FR>FR>>USRobotics Courier V.Everything Settings... FR>FR>> B1 C1 E1 F1 M1 Q0 V1 X7 FR>FR>> BAUD=38400 PARITY=N WORDLEN=8 FR>FR>> DIAL=HUNT ON HOOK TIMER FR>FR>> &A3 &B1 &C1 &D2 &G0 &H1 &I0 &K3 &L0 &M4 &N0 FR>FR>> &P0 &R2 &S0 &T5 &U0 &X0 &Y1 %N6 #CID=1 FR>FR>> S00=000 S01=000 S02=006 S03=013 S04=010 S05=008 S06=002 FR>FR>> S0S07=060 8=002 S09=006 S10=007 S11=055 S12=050 S13=000 FR>FR>> S14=000 S15=000 S16=000 S17=000 S18=000 S19=030 S20=000 FR>FR>> S21=010 S22=017 S23=019 S24=150 S25=005 S26=001 S27=000 FR>FR>> S28=008 S29=020 S30=000 S31=000 S32=009 S33=000 S34=000 FR>FR>> S35=000 S36=000 S37=000 S38=000 S39=000 S40=000 S41=000 FR>FR>> S4S42=126 S43=200 S44=015 S45=000 S46=000 S47=000 8=000 FR>FR>> S49=000 S50=000 S51=000 S52=000 S53=000 S54=064 S55=000 FR>FR>> S56=000 S57=000 S58=000 S59=000 S60=000 S61=000 S62=000 FR>FR>> S63=000 S64=000 S65=000 S66=000 S67=000 S68=000 S69=000 FR>TS> S70=000 FR>FR>> FR>FR>>ati7 FR>FR>>USRobotics Courier V.Everything Configuration Profile... FR>FR>>Product type US/Canada External FR>FR>>Options HST,V32bis,Terbo,VFC,V34+,x2 FR>FR>>Fax Options Class 1,Class 2.0 FR>FR>>Clock Freq 20.16Mhz FR>FR>>Flash ROM 512k FR>FR>>Ram 64k FR>FR>>Supervisor date 07/31/97 FR>FR>>DSP date 06/06/97 FR>FR>>Supervisor rev 7.2.1 FR>FR>>DSP rev 2.2.7 FR>FR>>--- Msged 4.00 FR>FR>> * Origin: Ready & Determined (819) 772-9277 (1:163/506) FR>FR>>