--------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1H00002 Date: 01/12/98 From: RICK COLLINS Time: 08:02am \/To: STEVE WALFORD (Read 9 times) Subj: Winmodem init.string On Jan 01 20:11, 1998, Steve Walford of 2:2502/7.9 wrote: SW> Windows 3.11 and a Winmodem, recently flashed by the latest SW> software from USR's website. SW> Anyone sugest a initialisation string for internet connections. SW> Currently using AT&F1&W AT&F1 is fine, but get rid of the &W. It serves no useful purpose. SW> As this is an internal modem how do you determine what speeds SW> connections are made at, I've read lots about modem inf files but SW> they all seem to relate to Windows 95 The modem returns a "connect string" when it connects to a remote system. That string includes the speed at which the modem connected to the remote. In Win3.1, the comm program itself is responsible for all modem operations, including sending the init and interpreting the returned connect string. If the comm program doesn't display the connect speed, then it doesn't, and there's not much you can do about it. There is nothing in Win 3.1 that is equivalent to Win95's .INF files because Win 3.1 handles comms completely differently. You _can_ determine the comm status _after_ you have disconnected by issuing the command ATI6 from a terminal program, such as Windows Terminal. That will tell you far more about the communication than the connect speed. In some ways, connect speed is overrated: it is not, in itself, indicative of performance. What you're really concerned about is _throughput_, and the connect speed is only one factor that will influence that. Besides, modern modems shift up and down in speed during a connect, depending on conditions, so the initial connect speed is less useful than you might think. :-) Rick --- MsgedSQ 3.30 * Origin: The Warlock's Cave, Ottawa ON (1:163/215.39) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1H00003 Date: 01/12/98 From: FRANCOIS ROY Time: 10:25am \/To: BUD JAMISON (Read 9 times) Subj: Problem #2 BJ> I'd be willing to bet the 'DISC received' means a disconnect from the BJ> other modem was received. And I'll bet it's his setup or modem that's BJ> at fault. Errr... that would be _my_ modem being at fault. What happens is that my end times out on what seems to be endless retransmits of the acknowledgement I send to his system after receiving a bundle. After nine retries, Bink decides there is a problem and hangs up on him. The only obvious thing in this scenario is that the problems started when he installed the Sportster V34+. I've been using my v-everything for a few years now, and I have never seen these symptoms before. --- Msged 4.00 * Origin: Ready & Determined (819) 772-9277 (1:163/506) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1H00004 Date: 01/11/98 From: GENE LOWRY Time: 10:51pm \/To: CLAY TANNACORE (Read 9 times) Subj: S-Register Settings In a message of Clay Tannacore (1:372/4) writes: CT> Can someone please tell me whether or not the S54=9 or S54=2 setting on CT> the Courier V.Everything is correct? S54 is a bit mapped register that disables specific symbol rates for the Courier V.e. I would think that you would want a good reason to do that. CT> When I received this modem, there was no manual in the box. The CT> information I have to depend on comes from other SysOps in the local CT> network. Some say S54=9 and some say use the S54=2 setting. And some will say, "leave it alone and at the factory default unless you have a specific reason to change it". It's your modem, you make the choice in settings. CT> I personally can't see any difference in the operation of the modem, but CT> I don't want to cause it any damage. I wouldn't expect that you would, what those settings do is disable possible connect negotiations. Settings in S54 will not damage a functional modem, as I read the documentation, they merely disable function(s). 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: F1H00005 Date: 01/11/98 From: GENE LOWRY Time: 10:57pm \/To: ALL (Read 9 times) Subj: USR_MODEMS Rules - Read BEFORE Posting Revised: July 26, 1997 USR_MODEMS Echo Rules This echo was established for the purpose of discussing the US Robotics Family of high speed modems. This discussion includes the entire US Robotics,WorldPort and MegaHertz product lines, both past and present models. The discussion may also include compatibility concerns or problems with other Modems, but only with relation to the US Robotics, WorldPort and MegaHertz products. The following Echo Rules are expected to be followed; Failure to follow these rules may result in a request for your removal from the echo: 1. The Moderators of USR_MODEMS are: 'Gene Lowry' FidoNet address 1:300/11, (520) 579-7188, 'Rick Collins' Fidonet address 1:163/215.39. Please remember that the moderators are not employees of US Robotics, we are US Robotics customers just like the rest of the participants of the USR_MODEMS echo. Any comments or complaints about anything in the USR_MODEMS echo should be addressed to one of the moderators at the above addresses given. At no time are complaints or messages about non-technical matters to be entered into the USR_MODEMS echo. 2. The Official Language of the USR_MODEMS echo is English. Apologies to those who cannot read or write English, but the fact is, most readers cannot read or write other languages and conversations would be difficult at best. 3. Only those messages directly addressing technical issues related to the US Robotics product line should be entered into the Echo. (Including the Courier and Sportster models offering speeds of 9600 BPS or above, WorldPort and MegaHertz models.) This specifically means that the following types of messages are *** NOT *** allowed: a. Absolutely no advertising of any type. No For-Sale advertising of used modems, no advertising for modem dealerships, etc. This is a technically-oriented echo and all messages must be technical in nature. b. Absolutely no messages on banned topics. Such topics include proprietary information such as dealer pricing, discussion of any operation of a modem outside of it's published specifications, unauthorized modification of USR modems, reproduction of proprietary ROM code, etc. c. Absolutely no trivial or personal messages should be entered in USR_MODEMS. Conversations between friends, having no technical content are a violation of Echo Rules. Messages of a conversational matter, not relating to the technical subject, should be conducted via direct netmail and not via the this Echo. d. Absolutely no messages involving personal attacks, insults or other topics intending to provoke, rather than to discuss technical topics. Please let's not get into "My Modem is better than Your Modem" discussions, we don't need it. e. Absolutely no messages regarding any topic, if the messages produced are not within the generally-agreed-upon, technical standards for Echo Mail Specifications. Specifically, Multiple Tear Lines, Multiple Origins, etc. may be considered sufficient cause to request linkages to the echo be removed. In the case of Echo Topology problems (e.g. "Dupe Rings", etc.) the Moderators reserve the right to restrict access in order to correct echo topology problems. f. Absolutely no messages that could be interpreted as condoning or advocating any illegal activity including but not limited to copyright violation or theft of intellectual property. 4. No parts of a message entered should be considered in violation of one of the previous rules. For instance, no origin lines or any message component should advertise for your modem dealership, or to sell your old modem, etc. 5. No parts of the message entered should be excessive, or particularly wasteful in verbiage. Like in addressing, or BBS naming, etc. This means specifically that your signature (e.g. "-Tom-") should not include multiple lines announcing your BBS's capabilities, etc. A simple name and a simple address (if required) and perhaps Telephone Number should suffice. 6. The use of your REAL NAME is expected at all times within the USR_MODEMS echo. If for some reason you are on a BBS which forces or otherwise doesn't allow you to change your name from an Alias, then you MUST sign with your real name at the bottom of any messages you enter. People feel more comfortable when dealing with you, when they feel they know who they are talking with. If your particular system of entry doesn't allow the use of your real name, and you don't wish to sign messages with your real name, then please don't participate in the USR_MODEMS echo. 7. The gating or exporting of the USR_MODEMS echo to networks other than FidoNet is permitted under the following conditions: a. All of the USR_MODEMS Echo Rules must be followed. b. All decisions and comments issued by the Moderators must be followed, including requests to remove linkages, and/or specific user's access. c. All pertinent FidoNet rules pertaining to Echo Management must be followed. d. All messages returned back into the FidoNet EchoMail system, must indicate an address of entry and/or location to which private replies or comments regarding those messages can be addressed. e. If problems develop, and the source of the offending messages cannot be localized, then the gateway to the other network will have its access cut off. f. It is strongly suggested that you seek permission to "Gate" the USR_MODEMS Echo to other networks, before you establish the linkage to do so. In the history of the echo, we've never prohibited it yet, but by telling us ahead of time, and asking permission, we'll be better able to handle any problems that might occur, since we'll know the Gateway and person to contact in the event of trouble. 8. Known Exceptions: Sysop-Pricing and Sysop-Program information from US Robotics is considered an exception from the Advertising rule, and thus accepted in the Echo. US Robotics *does* participate in the Echo at times, and as such, any such messages posted should be done by them, or authorized by them before posting. Since we are very THANKFUL that US Robotics does participate here, they are allowed to post any information they deem useful to the readership here. They may advertise their modems, sales prices, rebates, Sysop or other discount programs or anything they wish. We allow this to ensure they continue helping us with useful information about our modems and other US Robotics products. 9. Any questions, concerns, or appeals of Echo Moderation should be addressed to the MODERATORS in private netmail. -Gene Lowry- -Rick Collins- --- 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: F1H00006 Date: 01/11/98 From: JOHN PIPER Time: 02:44am \/To: DAVE DANIEL (Read 15 times) Subj: x2 Courier .INF Hello Dave. On Saturday, Jan 03, 1998, you wrote to John Piper: JP> I'll check it out, but I suspect it's the same Courier .INF file I JP> already use, which supports 31200 and 33600 connect rates. DD> Don't forget to delete your existing modems in the control panel DD> and re-detect them so they'll use the new inf file. Thanks, but I've since obtained an x2 .INF. -- John (japp@mpx.com.au) http://www.mpx.com.au/~japp Vescere bracis meis --- FMail/Win32 1.40g+ * Origin: Lateline Mail Emporium: South Sydney, Terra Australis (3:712/841) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1H00007 Date: 01/12/98 From: RICHARD THOMPSON Time: 09:02am \/To: GENE LOWRY (Read 9 times) Subj: 56???? GL> In a message of RICHARD THOMPSON (1:123/522) writes: GL> RT> Ever since I installed X2 I always receive connects of 115,2. I've t GL> RT> everything I can think of to get it to show me the true connect spee GL> You have a common problem. Regardless of the date on your MDMUSRCR.INF f GL> in your INF directory, it is incorrect for your x2 modem. To prove or GL> disprove this theory, go to your INF directory and load the file with a t GL> editor/browser and search for the string '49333' or '58666' (both x2 conn GL> speeds), if you don't find them you have the wrong file. The file that s GL> with Windows '95 and even with beta copies of Windows '98 are incorrect. GL> a copy of the file that has the above strings from either USR or one of t GL> others offering it on the web and drop it in your INF directory. Delete GL> modem and let the system re-detect it and you should be in business. I h GL> the same problem and just dropping in the file didn't fix the problem. A GL> if there is a .PNF file, delete it. GL> Gene Lowry Hi Gene, Thanks for responding. I checked my mdmusrcr.inf file for those 2 strings. It had them both. I have no idea what a .PNF file is? I had 3: chlen-us.pnf msimn.pnf setup.pnf I'm thinking you meant a USR or modem.pnf. Setup looked promising so I renamed it. It had the word modem in it. I downloaded the latest mdmusrcr.inf from totalservice.usr.com just for grins. I deleted the Courier properties and shutdown completely. After a couple of minutes I rebooted it found the Courier and installed for it. No change! I still got a 115.2 connect. Regards, on Monday 01/12/98 at 09:12 Rick INTERNET: rthompso@netten.net * RM 1.31 0123 * At night, I am a licensed cleavage inspector. --- Platinum Xpress/Win/Wildcat5! v2.0 * Origin: The GREAT PYRAMID 901-372-4980 (1:123/522) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1H00008 Date: 01/12/98 From: STEIN-IVAR JOHNSEN Time: 08:03pm \/To: ALL (Read 9 times) Subj: I-Modem problems.. Hi there .. I've got a strange problem here with my i-modem, and if someone could help me out or give me some idea of what to look for, i'd appreciate it. Here's what happens: Most of the callers get through and my system answers their calls, but calls from some people my i-modem wount answer at all. I did a test at home, called from my voicephone and my i-modem answered. I then called from my mobilephone and my i-modem didn't answer, i only heard some "clicking" in the modem??? I need some help on this!! What shall I do, what should I look for?? I'd appreciate all help on this! =-sijo-= --- OPMED/SQ 4.00.001/NDev.01 * Origin: El Beso Fatal (2:212/8) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1H00009 Date: 01/12/98 From: GENE LOWRY Time: 05:47pm \/To: JAMES COLE (Read 9 times) Subj: Re: Latest SDL In a message of James Cole (1:115/500@fidonet.org) writes: GF> No, he was insinuating that he wasn't clear in his response (that was GF> obvious) so chill a bit. GF> George * (941)745-5677 (1:137/2) JC> Gene: Wow! Talk about syntax, etc... This sucker's getting outa hand, JC> eh? Totally. JC> One of those times when NO response would have been the best response!? JC> Interesting nonetheless, how different folks perceive the language. That was my first approach, after the second swipe at me I reacted. JC> Maybe it's the heightend tenseness induced by pending ITU agreements. More like the size of the chip on an individual's shoulder IMHO. 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: F1H00010 Date: 01/12/98 From: GENE LOWRY Time: 05:58pm \/To: RICHARD THOMPSON (Read 9 times) Subj: 56???? In a message of RICHARD THOMPSON (1:123/522) writes: RT> It had them both. I have no idea what a .PNF file is? I had 3: RT> chlen-us.pnf RT> msimn.pnf RT> setup.pnf RT> I'm thinking you meant a USR or modem.pnf. Setup looked promising so I RT> renamed it. It had the word modem in it. I downloaded the latest RT> mdmusrcr.inf from totalservice.usr.com just for grins. Here the file name was MDMUSRCR.PNF, I deleted it. RT> I deleted the Courier properties and shutdown completely. After a couple RT> of RT> minutes I rebooted it found the Courier and installed for it. No change! RT> I still got a 115.2 connect. We wish! You've still got the problem of Windows not matching to the .INF file. I'd forgotten about it, but I did one more thing to the modem before it started working right, disabled external PNP (S69.0=1). With that bit set and the proper .INF file in place Windows correctly picked up the modem and shows the true connect speed. Regards, 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: F1H00011 Date: 01/11/98 From: VERNON FRAZEE Time: 05:43am \/To: PAUL CASEY (Read 9 times) Subj: Re: Expiration Warning GL> John, please be advised that I relisted the echo in November 1997 GL> and received an acknledgement. I'm relisting tonight ... PC> Yes, I relisted mine to 1/1/201 but never got receipts, so sent PC> again a week later to, 1:153/752 and then I got receipts, for my 3 PC> echos. Quote from: ELFAQ801 ZIP 6,421 01-01-98 12:00p