--------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: DEC00006 Date: 10/06/96 From: STU TURK Time: 10:17pm \/To: JOE FOSSATI (Read 1 times) Subj: What Does This Mean?? Joe Fossati wrote in a message to All: JF> I've been getting this message in the log if I upload an JF> Xpress Packet with a LARGE message. Does anyone know what JF> it means, or how to correct the problem?? JF> : 04 Oct 17:23:57 OPUS Scanning BEER to 129/11 JF> + 04 Oct 17:23:58 OPUS Can't scan `260.MSG' (12729) [10240] JF> <---------- # 04 Oct 17:23:58 OPUS OOMP A=BEER M=3 C=3 D=0 S=0 The message is too large and Opus won't scan it. Willie's board scanned it (I assume that is the msg you mention in our local Echo) because he is using a external scan program. --- timEd/386 1.10+ * Origin: SoundProof Point, Pittsburgh PA (1:129/26.2) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: DEF00000 Date: 10/09/96 From: MICHELE MARIE DALENE Time: 08:10am \/To: WALTER TIETJEN (Read 1 times) Subj: Re: _LARGE_ message - part 2 > > Note that the _SIZE_ problem is encountered on _EXPORT_SCAN_ > - _NOT_ import toss. External toss/scan _REQUIRED_ - PSRT_14 > will _NOT_ help. Sounds like the sysop might want to set a message limit of less than 10K per message. Thats a possible problem if the sysop allows xmodem upload of messages. but setting maximum lines at something that wont go over 10K is the next step. As far as message exporting. I use Squish 1.11 so I cannot help reguarding an internal opus export problem. Michele Marie Dalene --- Opus-CBCS 1.73a * Origin: The Pink Rose 860-423-2782, 300-14400bps (1:327/6338.0) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: DEH00000 Date: 10/11/96 From: JOE ROWEHL Time: 08:00pm \/To: PETER BROWNWATER (Read 1 times) Subj: Re: Problem - X00 > PROBLEM: I upgraded again, from the 486-50DX to a > Cyrus 6x86 and > To an INTEL 1430 VX CHIPSET PENTIUM System Board and > now notice > a significant delay reseting the comm port. It simply > will sit and > wait sometimes for 3 or 4 seconds, othertimes for 20 > seconds or more > > Anyone have an idea why? I spoke to a field engineer at work today about your problem. It seems the Cyrix 686's run at a significantly higher speed than other processors, and will also accept non-sequential instructions. This seems to drive FOSSIL's crazy. His recommendation is to try either DigiFoss or BNU, as X00 and the Cyrix 686's seem to not like each other a whole bunch. BNU is fairly common, but I've never heard of DigiFoss. Hope this helps! Joe --- Opus-CBCS 1.73a * Origin: Flashpoint Opus: (757)479-5408, Va Beach, VA (1:275/52.0) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: DEI00000 Date: 10/13/96 From: BOB JUGE Time: 08:05am \/To: JOE ROWEHL (Read 1 times) Subj: Problem - X00 Joe Rowehl wrote in a message to Peter Brownwater: > PROBLEM: I upgraded again, from the 486-50DX to a Cyrus 6x86 and > To an INTEL 1430 VX CHIPSET PENTIUM System Board and now > notice a significant delay reseting the comm port. It > simply will sit and wait sometimes for 3 or 4 seconds, > othertimes for 20 seconds or more > > Anyone have an idea why? JR> I spoke to a field engineer at work today about your problem. JR> It seems the Cyrix 686's run at a significantly higher speed than JR> other processors, and will also accept non-sequential instructions. JR> This seems to drive FOSSIL's crazy. His recommendation is to try JR> either DigiFoss or BNU, as X00 and the Cyrix 686's seem to not like JR> each other a whole bunch. I have run X00 v1.53a successfully on a P6-200 at home and a P-166 at work, so I don't think your field engineer's thinking regarding the Cyrix 686's speed is on target here, Joe. - 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 (713) 980-9671 (1:106/2000) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: DEI00001 Date: 10/11/96 From: JIM BARCHUK Time: 05:55pm \/To: WALTER TIETJEN (Read 1 times) Subj: _LARGE_ message - part 2 Hello, Walter Tietjen, I'd like you to meet my friend, Dr. Lao... JF>> I've been getting this message in the log if I upload an Xpress JF>> Packet with a LARGE message. WT> Note that the _SIZE_ problem is encountered on _EXPORT_SCAN_ - _NOT_ WT> import toss. External toss/scan _REQUIRED_ - PSRT_14 will _NOT_ help. You are absolutely correct, I missed the above completely. :-) jB-) --- * Origin: :nigirO * (1:141/355) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: DEI00002 Date: 10/12/96 From: IVAN SZE Time: 04:52pm \/To: COWGIRL (Read 1 times) Subj: DROP DROP ___ Blue Wave/386 v2.30 [NR] --- Silver Xpress Mail System 5.4H1 * Origin: Cowgirl's Rodeo *Fido* ->Hub400<- (1:250/401) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: DEJ00000 Date: 10/14/96 From: JOE ROWEHL Time: 10:19am \/To: BOB JUGE (Read 1 times) Subj: Re: Problem - X00 >> Anyone have an idea why? > > JR> I spoke to a field engineer at work today about > your problem. > JR> It seems the Cyrix 686's run at a significantly higher > speed than > JR> other processors, and will also accept non-sequential > instructions. > JR> This seems to drive FOSSIL's crazy. His recommendation > is to try > JR> either DigiFoss or BNU, as X00 and the Cyrix 686's > seem to not like > JR> each other a whole bunch. > > I have run X00 v1.53a successfully on a P6-200 at home and > a P-166 at work, so I don't think your field engineer's > thinking regarding the Cyrix 686's speed is on target here, > Joe. There's two items mentioned there - speed, and non-sequential instructions. There are quite a few differences bwteeen a Pentium and a Cyrix 686. In any case, trying a different FOSSIL should be relatively simple, no? :-) Joe --- Opus-CBCS 1.73a * Origin: Flashpoint Opus: (757)479-5408, Va Beach, VA (1:275/52.0) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: DEJ00001 Date: 10/14/96 From: BOB JUGE Time: 09:42pm \/To: JOE ROWEHL (Read 1 times) Subj: Problem - X00 Joe Rowehl wrote in a message to Bob Juge: > JR> I spoke to a field engineer at work today about your problem. > JR> It seems the Cyrix 686's run at a significantly higher speed > JR> than other processors, and will also accept non-sequential > JR> instructions. This seems to drive FOSSIL's crazy. His > JR> recommendation is to try either DigiFoss or BNU, as X00 and the > JR> Cyrix 686's seem to not like each other a whole bunch. > I have run X00 v1.53a successfully on a P6-200 at home and a P-166 > at work, so I don't think your field engineer's thinking regarding > the Cyrix 686's speed is on target here, Joe. JR> There's two items mentioned there - speed, and non-sequential JR> instructions. There are quite a few differences bwteeen a Pentium JR> and a Cyrix 686. In any case, trying a different FOSSIL should be JR> relatively simple, no? :-) The Pentium Pro also accepts non-sequential instructions, I believe. X00 is industrial-strength (as FOSSILs go), and should not be affected by hardware at all. - 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 (713) 980-9671 (1:106/2000) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: DEJ00002 Date: 10/14/96 From: PETER BROWNWATER Time: 08:46pm \/To: JOE ROWEHL (Read 1 times) Subj: Re: Problem - X00 Joe Rowehl wrote to Peter Brownwater: JR> as X00 and the Cyrix 686's seem to not like each other a JR> whole bunch. Thanks a lot for the note... and for remembering to ask about my problem. I don't think I'll get a fix, given the date of X00 and the future coming blazing through. I guess I'll just have to be patient waiting for the resets on exits. Heck, at least it works, not properly maybe, but I have not had any freezeups or crashes. Thanks again Peter --- timEd/B8 * Origin: Pete's Place: 1-905-471-5229 (1:2424/204) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: DEJ00003 Date: 10/14/96 From: PETER BROWNWATER Time: 08:51pm \/To: BOB JUGE (Read 1 times) Subj: Problem - X00 Bob Juge wrote to Joe Rowehl: BJ> I have run X00 v1.53a successfully on a P6-200 at home and a BJ> P-166 at work, so I don't think your field engineer's BJ> thinking regarding the Cyrix 686's speed is on target here, BJ> Joe. Sorry to butt in here BOb, but if you have a version of X00 that works well with the Cyrix, then I'd like to know where I can get it. Available on the INTERNET? The version I have is X00 1.50 and is described as the last version using the original source code. Thanks for answering Joe, and maybe you can lead me to the X00 1.53a version you use. Regards, --- timEd/B8 * Origin: Pete's Place: 1-905-471-5229 (1:2424/204)