--------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1500006 Date: 01/04/98 From: JEAN PARROT Time: 09:13am \/To: GENE LOWRY (Read 9 times) Subj: Decimal ? GL> While the format above (S15.7=1) is most useful for bit mapped GL> registers and the format S02=255 is most useful for ( snip ) Gene, a large thankyou for your attention to my education. Is still have not found out in my Hayes manual, any reference to setting just a lone bit at a time. Still looking. The twin Ricks also educated me. -=- QWKRR128 V5.10 [R] --- Maximus/2 3.01 * Origin: Juxtaposition BBS. Lasalle, Quebec, Canada (1:167/133) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1500007 Date: 01/04/98 From: RUSSELL BROOKS Time: 08:29am \/To: GENE LOWRY (Read 14 times) Subj: x2 Courier .INF GL> In a message of John Piper (3:712/841) writes: JP>> Is anyone aware of a Windows 95 .INF file which supports the JP>> extra connect speeds made available by a Courier running x2 code? JP>> I've not been able to locate one on USR's Australian or US Web JP>> sites. GL>> I found one last week on USR's US FTP site in the DL05 download GL>> area, file name is MDMUSRCR.INF. Don't quote me on this but I GL>> think the actual path was ftp.usr.com/d1/pub/dl05. JP>> I'll check it out, but I suspect it's the same Courier .INF file JP>> I already use, which supports 31200 and 33600 connect rates. GL> John, all I can tell you is that the file works for my USA/Canada GL> x2 Courier and returns (for one) 48,000 when online with my ISP GL> under Windows '98 I am also using couriers with win98 and the actual Courier MDMUSRCR.inf does not mention any connect rates above 33600 (if you scan the file with a text editor) but 2 others do. The MDMUSRG.INF for Europe and then the MDMUSRK1.inf for x2 do have the numbers higher than 33600. So I don't really know which .inf file W98 is using in your case. There is also a MDMUSRCR.*Pnf* file in the inf directory... maybe this patches the original file or something. [To JOHN PIPER] _ I could email all of these to you to try is you want. BTW..The w98 Sportster inf file fixed Bill Grimsley's false reporting of the connect rate in w95 OSR2, for him. Can't hurt to try them ALL. --- Terminate 5.00/Pro * Origin: Electron Migration (3:640/305.55) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1500008 Date: 01/04/98 From: RUSSELL BROOKS Time: 08:29am \/To: JOHN PIPER (Read 14 times) Subj: x2 Courier .INF GL> In a message of John Piper (3:712/841) writes: JP>> Is anyone aware of a Windows 95 .INF file which supports the JP>> extra connect speeds made available by a Courier running x2 code? JP>> I've not been able to locate one on USR's Australian or US Web JP>> sites. GL>> I found one last week on USR's US FTP site in the DL05 download GL>> area, file name is MDMUSRCR.INF. Don't quote me on this but I GL>> think the actual path was ftp.usr.com/d1/pub/dl05. JP>> I'll check it out, but I suspect it's the same Courier .INF file JP>> I already use, which supports 31200 and 33600 connect rates. GL> John, all I can tell you is that the file works for my USA/Canada GL> x2 Courier and returns (for one) 48,000 when online with my ISP GL> under Windows '98 I am also using couriers with win98 and the actual Courier MDMUSRCR.inf does not mention any connect rates above 33600 (if you scan the file with a text editor) but 2 others do. The MDMUSRG.INF for Europe and then the MDMUSRK1.inf for x2 do have the numbers higher than 33600. So I don't really know which .inf file W98 is using in your case. There is also a MDMUSRCR.*Pnf* file in the inf directory... maybe this patches the original file or something. [To JOHN PIPER] I could email all of these to you to try is you want. BTW..The w98 Sportster inf file fixed Bill Grimsley's false reporting of the connect rate in w95 OSR2, for him. Can't hurt to try them ALL. --- Terminate 5.00/Pro * Origin: Electron Migration (3:640/305.55) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1500009 Date: 01/04/98 From: GENE LOWRY Time: 07:24pm \/To: MARIO BONELLI (Read 9 times) Subj: Latest SDL In a message of Mario Bonelli (1:273/934) writes: MB> What is the latest SDL for USR Courier 56k modems? July 97? As of last week (1/1/98), that's the latest. 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: F1500010 Date: 01/04/98 From: GENE LOWRY Time: 07:28pm \/To: JEAN PARROT (Read 9 times) Subj: Decimal ? In a message of Jean Parrot (1:167/133) writes: GL> While the format above (S15.7=1) is most useful for bit mapped GL> registers and the format S02=255 is most useful for ( snip ) JP> Gene, a large thankyou for your attention to my education. Is still JP> have not found out in my Hayes manual, any reference to setting just a JP> lone bit at a time. Still looking. Why not just try it on a register that won't cause a lot of grief and can be easily reset? S02 comes to mind... JP> The twin Ricks also educated me. A couple of good fellers in my book. 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: F1500011 Date: 01/04/98 From: DAVE BEACH Time: 10:06pm \/To: CRAIG FORD (Read 9 times) Subj: Fallback CF> indirectly on the Sportster via the &U and &N commands. Okay, then, if my Sportster is configured with &U0 and &N0, which it is, then there should be no reason why it would not fallback/forward as required, right? So, how to explain my Sportster's constant ATI6 "fallback disabled" result when the Courier with which I was just connected reports "fallback enabled"? How to explain why my Sportster, on an initially-reported 28,800 bps V.34 connect, will report, via an ATI6, final speeds of 31200/26400 and "fallback disabled" when it seems intuitively logical that fallback/forward did indeed happen on the connect (as apparently evidenced by the final speeds)? How to explain that the wording in the Courier and Sportster documentation describes the ATI6 "fallback" stat in exactly the same words, but folks seem to think it means one thing on the Courier and another on the Sportster? Any ideas? Can you at least help remove some of the ambiguity by clarifying USR's poor wording re the "fallback" stat? Does it mean: a) The modems negotiated the capability as part of the initial connection sequence, and doesn't necessarily report that fallback did indeed happen during the connection; or b) The modems actually experienced fallback during the connection. --- GoldED 2.50 UNREG * Origin: Wanna NEC? (1:163/222) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1500012 Date: 01/04/98 From: DAVE BEACH Time: 10:13pm \/To: RICK COLLINS (Read 9 times) Subj: Sportster 33.6 RC> speed, I'm not sure "fallback" refers to such a shift in speed. I think RC> I'm at the end of my "expertise" on this one, Dave. Well, you *seemed* to know what you were talking about ;-) RC> Have a look at S27, bit 4. Setting that would seem to enable RC> fallback. I tried that already, and an ATI6 still consistently reported "fallback disabled". RC> I can only re-iterate what was posted here in the past, and that is the RC> Sportster will dispaly "enabled" only if a fallback actually occurs. I'm extremely suspicious of this (not what you said above - see my question to Craig attempting to clarify USR's poor wording). I've *never* seen "fallback enabled" reported, and I make/receive enough V.34 calls that common sense, years of experience with phone lines and conditions, and years of experience with modems in general tell me that it would have happened occasionally. The presumption, from what you wrote above, is that fallback has never happened, and I find that hard to believe - not the least of which reason is the identical wording describing the reported stat in the Courier *and* Sportster docs. If the Courier reports "fallback enabled", all evidence points to the supposition that the Sportster with which it connected should darned well report "fallback enabled" also (what that actually *means*, of course, is another question entirely). --- GoldED 2.50 UNREG * Origin: Wanna NEC? (1:163/222) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1500013 Date: 01/04/98 From: RICK GRAHAM Time: 07:37pm \/To: CLAY TANNACORE (Read 9 times) Subj: Marking messages private Hello Clay, >>> Well, I got a certificate stating that -I am a moron- and not a >>> "Freq", is that good enough? . . [g] RG>> Certainly! I have one of those also, ...it all started when I RG>> bought my first computer... > Strange, that's just about the time I became certifiable . . . [g] It happened to a lot of people. Hail, I can't "interface" with another person unless they have a T-shirt with a picture of a keyboard on it! >>> Anyway, I got the file and I owe you one. Thanks a lot. Something >>> must be happening to FidoNet of late. People are starting to act >>> just like they used to, like this was REALLY a hobby. RG>> I wouldn't get real used to it Clay, it's probably just the Season, RG>> but I still like my Fido! > I was afraid of that. A one-time thing, but I'll wait and see. Heck > in the last two weeks I got help from you and (believe it or not) > from USR/3COM. I *try* to help if I think I can, but when the waters get muddy and I see I'm in over my head, I bail out. > If this stuff keeps up, I bet I'll even have someone volunteer to > explain to me why I can't connect to my ISP on the first try with the > Courier V.everything. Sounds like you need to have a talk to your ISP tech... good luck. Later... Rick rgraham@ionet.net --- PCBoard (R) v15.3/M 2 * Origin: Peyote Bud's - Dewey, OK - V.34 - 1.918.534.2124 (1:3815/123) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1500014 Date: 01/04/98 From: RICK GRAHAM Time: 08:10pm \/To: JEAN PARROT (Read 9 times) Subj: Decimal ? Hello Jean, RG>> It appears you are savy on bit mapping of S registers (snip) > Not really, Rick, just learning and the format of this S15.7=1 > got me thinking and I was mainly curious to see what to feed it . I > thouhgt that the total result of adding all the bits into a byte > value was the way to do this, even in USR's modems. > This is not the way to insert a value in a register, is it ? Say > no, please. There are a couple ways, on more technical than the other. You can add the bit values or turn on different bits by using the "1" or "on" in computereze. Q: Did you get a Quck Reference Card with your modem? Here's an example from the V34MAN.TXT file (Courier V.34 Ascii Text Manual) available on the USR bbs and website via ftp: ****************** S-REGISTER SUMMARY USAGE The default values are those users typically require. Change the settings of an S-Register with the ATSr=n command, where r is the register and n is a decimal value from 0-255: ATS13=8 The modem does not perform a value-range check. Some values you select may not work with some equipment, and you'll have to readjust the settings. Some registers (S13, S14, S15, S16, S27, S34) are bit-mapped (bits 0-7). For example, turning on bit 0 of S13 causes the modem to reset each time the computer or terminal drops its Data Terminal Ready (DTR) signal. Turning on bit 3 of S13 causes the modem, on receipt of DTR, to auto dial the number stored at position 0 in NVRAM. To turn on one or more bits in any bit-mapped register, use the total of the values shown below. For example, S13=9 turns on bits 0 (value of 1) and 3 (value of 8). Alternatively, identify the bits to be turned on with the following format: Sr.b=1, where r is the register and .b is the bit. This format does not require knowledge of the bit's value. S13.0=1 .3=1 is the equivalent of S13=9, above. To turn off a bit function, set it to zero: S13.0=0. To display the contents of a register, use ATSr? as in this example: ATS13? S13 0 Bit-mapped register. Select the bit(s) you want on and set S13 to the total of the values in the Value column. For example, ATS13=20 enables bit 2 (value = 4) and bit 4 (value = 16). Or use ATSr.b=0 (OFF) or 1 (ON). For example, ATS13.0=1 .3=1 turns on bits 0 and 3. To turn a bit off, set that bit to zero, as in ATS13.3=0. Bit Value Result 0 1 Reset when DTR drops 1 2 Reverse normal Auto Answer operation: on incoming RING, enter Originate Mode and look for Answer tone 2 4 Disable 250 msec. pause before result code display 3 8 On DTR signal, Auto Dial the number stored in NVRAM at position 0 4 16 At power on/reset, Auto Dial number stored in NVRAM at position 0 5 32 Disable HST (used for testing V.32 terbo in Dual Standard modems) 6 64 Disable MNP Level 3 (used for testing Level 2) 7 128 Custom applications <<<>>> Clear as mud now? I read Rick Collins and Gene Lowry's messages to you rgarding this - you're in good hands with Rick C. & Gene helping. Later... Rick rgraham@ionet.net --- PCBoard (R) v15.3/M 2 * Origin: Peyote Bud's - Dewey, OK - V.34 - 1.918.534.2124 (1:3815/123) --------------- FIDO MESSAGE AREA==> TOPIC: 242 USR MODEMS Ref: F1500015 Date: 01/04/98 From: RICK GRAHAM Time: 08:01pm \/To: JOHN PIPER (Read 14 times) Subj: x2 Courier .INF Hello John, [...] > I've since received the one you emailed to me. It may be newer than > the one I already have. I'll have to check, but in any event, I have > obtained a Courier driver file which does support x2. It came out of the 07/31/97 Courier SDL. Hope you get up to speed in any event. Later... Rick rgraham@ionet.net --- PCBoard (R) v15.3/M 2 * Origin: Peyote Bud's - Dewey, OK - V.34 - 1.918.534.2124 (1:3815/123)