--------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: F1^00001 Date: 01/25/98 From: JACK STEIN Time: 01:23pm \/To: ALL (Read 0 times) Subj: Disk Space Alert Does anyone know why OPUS would give me a disk space alert in partition with less than 2 gig free? I had my File area and Msg area in a 3.5 Gig partition, and OPUS worked fine for tossing mail and so on. Users were unable to U/L files though, so I moved the u/l directory to a smaller partition. OFAM then would not let me move files from the upload dir. to the files area, so I reduced the big partition to have less than 2 gigs free space. OFAM then worked, but users still can't leave a message directly (Xpress works fine). My files/msg partition is still over 2 gigs, but less than 2 gigs are free, which I thought would enable users to write a message. Everything else seems to work well in the large partition, even a 3.5 GIG one with 3.1 GIG free. I expected more problems from things such as my renumbering, OMMM software and so on, but seems only the message area is the problem now. Looked through 179 docs and didn't see any mention of this either, hoping Trev would have changed the int size to double or unsigned long or whatever was needed to correctly read large drives. Anyone have any tips on this, other than the obvious make another small partition? Jack --- timEd/2-B11 * Origin: Jack's Free Lunch 4OS2 USR16.8 Pgh Pa (412)492-0822 (1:129/171) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: F2200000 Date: 02/01/98 From: CHRISTOPHER BAKER Time: 07:37am \/To: ALL (Read 0 times) Subj: MEADOW Echo Guidelines - regular repost This is the MEADOW Echo. It exists to offer assistance to Sysops who run or want to run Opus CBCS. It is called the MEADOW due to an unintentional confusion with a cartoon hero named Opus who often frolicked in a meadow. [See: Cartoon history; Berke Breathed] The current version of Opus is 1.79. That is the version most often dealt with in this Echo. However, we have plenty of oldtimers who might remember a thing or two about the previous versions if you happen to be starting from one of them. Questions and answers refer to the current version unless otherwise noted by the message authors. Unreleased or beta/gamma versions are off-topic here unless updates are given by the Opus authors. The standard reply applies to questions about WHEN any new versions might be released - "When it is ready." This Echo is for OPUS Sysops and would-be OPUS Sysops only! If you are considering becoming an Opus Sysop or are just starting to organize an Opus operation on your system, you might also want a link into the NEWOPUS Echo where newbies and wannabees can get more attention. [grin] Anything related to starting, running and maintaining an Opus based system is on-topic here. If you want to ask questions about other BBS programs you'll need to find a specific Echo for those elsewhere. You can get limited answers to front-end mailer [like BinkleyTerm, and others] questions depending on who is reading here at any given time. Those questions that deal with interfacing with an Opus setup will be considered on-topic as well but if you need detailed information on front-end mailers, check the ELIST [master list of Echos] or ask your NEC [Net Echo Coordinator] about specific Echos for your particular mailer. The following list of specific Echo rules are lifted directly from an original post by Bev Freed and then churned by Jimmy Winson [thanks, Bev and Jimmy!]. RULES: In addition to general rules for any conference, Meadow rules are simple, standard, and may be bent a little, but not trashed. The Meadow "spirit" is one of cooperation. And remember: Guido is watching. [you'll find out about him if you stray to far off topic ] 1. Keep your messages on-topic -- On occasion, the Moderators may get the feeling that message content is inappropriate or has the potential to attract a barrage of inappropriate messages. In such instances, the Moderators will post a reminder of the rules or send netmail. It's not personal. If you post an off-topic message, let it be for comic relief and the fostering of friendships. 2. Be excellent to one another and keep your sense of humor -- Personal attacks (thinly disguised or not) are prohibited. The useful exchange of information requires you to accept that people have opinions or experiences which contrast yours. The object of this conference is to learn from others, not argue with them. 3. Be helpful -- If you can help someone with a technical problem, PLEASE do, but avoid blind guesses. You'd be doing a disservice. If you're not certain of a proper response, wait a few days to see if someone out there has the definitive answer. Then everyone learns something. 4. Never use Meadow to reply to inappropriate messages -- If you feel a message is inappropriate, simply take a deep breath and ignore it. It'll go away. And if it doesn't, LET THE MODERATORS HANDLE THE PROBLEM. If you feel particularly strong about a specific posting, send the Moderators private netmail, or take your beef off-echo and flame the person directly. Leave the others out of it. The Moderators have probably already addressed the problem via netmail. 5. Keep your quotes to a minimum -- People read Meadow regularly; you don't need to quote and explain the obvious. If you get a bad case of quotitis, the Moderator will come over to administer something you hated as a kid. 6. Keep your messages public and without nuisances such as encryption, encoding, or rotation -- If you have a driving need to send a private or fancy message, there's something intriguing out there called Netmail. Use it. 7. Keep to a minimum BBS ads and notices on new conferences or toys -- Such advertisements and so on should be restricted to no more than ONCE per month. We hear ya, already. 8. Running a barefoot Opus is not the same as running Opus bare. HANDLES: While not encouraged, "handles" or anonymous names are permitted provided they are not used with the intent to conceal the identity of a person posting malicious, annoying, or illegal messages. Please include your proper name someplace on every message. NONCOMPLIANCE: If you cannot abide by and comply with the rules, you are requested to forego posting messages to this conference. Anyone who posts inappropriate messages will be warned of the infraction. If such postings continue, you will be asked to drop the conference. If you do not drop the conference voluntarily, the system(s) uproute will be asked to disconnect your feed. This method of keeping Meadow interesting and productive is not preferred. It is preferable that participants simply abide by the rules and "spirit" of the conference, and that they serve one another. That's it. Remember that as an Opus Sysop, you pledge to avoid becoming serious [you did read the docs, yes?]. You can be serious about Opus so long as you don't become serious. [grin] Take the WOC pledge and welcome. Above all, enjoy your adventures with a continually evolving software legend! The global community of Opus Sysops is eternally and infinitely grateful to the countless hours of work donated [as well as the attendant abuse suffered enroute with great patience] by Wynn Wagner III, Doug Boone, the late John Valentyn, Trev Roydhouse, Bev Freed, Tom Kashuba, and MANY others who have made this the largest cooperative BBS project on the planet! OPUS is NOW in the process of resurrecting the BBS project! Stay tuned to this Echo for bulletins and details! Christopher Baker jim barchuk Michael Whitlatch MEADOW Echo Moderators Addendum: From: Christopher Baker To: All Date: 15 Dec 95 00:23:14 Subj: AMFAR request I have been requested to post this notice in all the Opus-related echo conferences: If you wish to show your appreciation for Opus-CBCS, please send a contribution to: AmFAR 5900 Wilshire Blvd. Second floor East Satellite Los Angeles CA 90036-5032 U.S.A Don't forget to write "Opus-CBCS" on your check or money order. Thanks! For all the Opus Development Team. Origin: Rights_On!-F/R OPUSFILE for 1.7+ List-Edgewater_FL_USA (1:18/14) -30- --- DB B2300sl/001027 * Origin: Rights_On!-F/R OPUSFILE for 1.7+ List-Edgewater_FL_USA (1:18/14) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: F2200001 Date: 01/31/98 From: GEORGE FLIGER Time: 12:04pm \/To: JAN MURPHY (Read 0 times) Subj: Y2K issues On 29 Jan 98 09:43am, Jan Murphy wrote to all: JM> Howdy guys, JM> Since nothing much is going on in here, I thought I'd stir up JM> some trouble. JM> Over in Z1_Election, people have started to make noise about JM> the Year 2000 problem, better known as "Will we even have a JM> Fidonet on January 1, 2000?" JM> I've been wanting something to do in my copious spare time JM> , so I thought it might be a good idea to start working JM> now to see what software is robust and what will choke when the JM> big day comes. I know we've touched on this before, but I JM> wasn't really paying attention then. This time, I will. JM> Now, *one* thing I know for sure, because I screwed up this way JM> myself: if you want to set your system clock ahead in order to JM> play with this, be sure to make a backup of your schedule file JM> before you start messing around. If not, your Opus will not JM> like you when you go back to 1998. JM> How much have y'all experimented? What's going to break? What JM> are we going to do about it? Is it true what somebody said, JM> that the *.pkt structre itself is faulty? JM> I confess I don't have much of a clue as to which part is JM> controlled by hardware, which by software, and so on, so I JM> figure it's time to start paying attention and learning this JM> stuff. And I wanted an excuse to learn C anyhow. JM> So I'd appreciate it if you could post or re-post your findings JM> here, and I'll try and assemble some kind of Y2K/Opus FAQ file JM> from the lot. Good questions, all of them. I, myself, have not experimented with my "bird" to find out the ramifications. I'll be one of those who will be scrambling for some type of alternative to Opus if it breaks on 1/1/2000. :) I just can't give the old bird up! George ... At 34 nobody will feel the heat more than him. --- Via Silver Xpress V4.4P [Reg] * Origin: Chipper Clipper * WOC'in' on the water * (1:137/2) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: F2500000 Date: 02/04/98 From: MEL PHEASANT Time: 07:26pm \/To: JAN MURPHY (Read 0 times) Subj: Y2K issues Ugh. Make sure if you try testing for y2k compliance, that you remember to set the date back to normal time before entering messages. I just got about 50 messages bounced back, from the last few days, from our NEC. He runs GMD, and it bounces messages that are too far out of date. So alot of my writing has gone to the bit bucket. Oh well... On another note, most old bios's have a date bug, but if you leave the computer running, the bug is squashed. And even more happily, my homebrew mailer chugs along fine, and even runs schedules properly (as I suspected). --- msged 1.99S ZTC * Origin: Bug? What bug?! Ottawa, Canada (613) 733-5820 (1:163/207) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: F2500001 Date: 02/03/98 From: JACK STEIN Time: 09:07pm \/To: GEORGE FLIGER (Read 0 times) Subj: Y2K issues George Fliger wrote in a message to Jan Murphy: JM> So I'd appreciate it if you could post or re-post your findings JM> here, and I'll try and assemble some kind of Y2K/Opus FAQ file JM> from the lot. GF> Good questions, all of them. I, myself, have not GF> experimented with my "bird" to find out the ramifications. GF> I'll be one of those who will be scrambling for some type of GF> alternative to Opus if it breaks on 1/1/2000. :) I can't even think of anything that would be affected. OPUS messages store a 2 digit date, so it should just list them as 01/01/00 as far as I know. DOS should convert any date in the BIOS correctly for years 00 to 79 since DOS should know nothing existed in DOS before 1980. Renumbering based on age might be an issue depending on how dates are calculated. I imagine if someone manually subtracts a two digit year then problems will show up for sure, but I don't have a clue how compiler date functions work. In other words, I don't have a clue either. Jack --- timEd/2-B11 * Origin: Jack's Free Lunch 4OS2 USR16.8 Pgh Pa (412)492-0822 (1:129/171) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: F2A00000 Date: 02/04/98 From: JOHN NEMMER Time: 02:53pm \/To: JACK STEIN (Read 0 times) Subj: Re: Y2K issues hmmmm excuse my technical talk here ..... :-))) but a few things in opus access the date.... I think one was something todo with dupe detection and or the time/ date stamp since opus was born??? also I remember someone saying it affected their sched.dat how how this happened I don't know... not sure but remembering bits and pieces of long past conversations John --- Opus 1.73 GEcho1.11+ * Origin: Scouter's Haven (412) 488-8960 (1:129/186.0) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: F2A00001 Date: 02/05/98 From: JAN MURPHY Time: 08:59am \/To: MEL PHEASANT (Read 0 times) Subj: Re: Y2K issues > Ugh. > > Make sure if you try testing for y2k compliance, that you > remember to set the date back to normal time before entering > messages. I just got about 50 messages bounced back, from > the last few days, from our NEC. He runs GMD, and it bounces > messages that are too far out of date. So alot of my writing > has gone to the bit bucket. Oh well... What kind of messages did you get from GMD? Did it complain that the messages are too old, too new, or just out of range? ;-) --- Opus-CBCS 1.73a * Origin: Sci-Fido II, World's Oldest SF BBS, Berkeley, CA (1:161/84.0) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: F2A00002 Date: 02/05/98 From: JAN MURPHY Time: 09:01am \/To: ALL (Read 0 times) Subj: Y2K web sites Hi guys, One of our local computer magazines, _Computer Currents_, has a quick run-down on Y2K problems in the current issue. I'll post all the web sites here so that those of you who have web access (I don't at the moment) can check them out. On replacing clock chips, try Resource 800: www.resource800.com/ho01006.html BIOS upgrades: Micro Firmware: 1-800-767-5465 www.firmware.com Unicore Software: 1-800-800-2467 www.unicore.com Tom Becker offers a small memory-resident program, Year2000.com, which intercepts the dates from the BIOS and clock chips at the 2000 rollover and corrects the information. www.rightime.com There's also a commmercial version Y2KPCPro available from Year2000 Consultants (1-617-242-9091). In the UK, The Computer Experts have a demo of their Millenium Bug Toolkit: www.computerexperts.co.uk/pc2000 Commercial version of same is at: www.4xinc.com A fix for Windows 3.x's file manager (WINFILE.EXE) which has a display bug: support.microsoft.com/support/kb/articles/q85/5/57.asp Novell patches: www.novel.com/p2000/patches.html Test programs: Test2000.zip from Tom Becker: www.rightime.com Y2000.exe from National Software Testing Labs: www.nstl.com/html/ymark_2000.html F2000.exe from Fernlink 2000 at www.implement.co.uk/bios.htm SURVIVE.EXE from www.survive-2000.com The Computer Currents article can be found at www.currents.net/cover (this is from the February 3rd issue). There's also a huge sidebar for web pages for various hardware and software vendors. Hope this helps. --- Opus-CBCS 1.73a * Origin: Sci-Fido II, World's Oldest SF BBS, Berkeley, CA (1:161/84.0) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: F2B00000 Date: 02/06/98 From: JOE ROWEHL Time: 09:18pm \/To: JAN MURPHY (Read 0 times) Subj: Re: Y2K issues >> messages. I just got about 50 messages bounced back, > from >> the last few days, from our NEC. He runs GMD, and it > bounces >> messages that are too far out of date. So alot of my > writing >> has gone to the bit bucket. Oh well... > > What kind of messages did you get from GMD? Did it complain > that the messages are too old, too new, or just out of range? > ;-) Hehehe... "This message is being returned because it hasn't been written yet"... ];-> Joe --- Opus-CBCS 1.79.x * Origin: Flashpoint Opus: (757)479-5408, Va Beach, VA (1:275/52.0) --------------- FIDO MESSAGE AREA==> TOPIC: 195 MEADOW Ref: F2M00000 Date: 02/17/98 From: JOHN NEMMER Time: 03:10pm \/To: ALL? (Read 0 times) Subj: hello?? HELLOOOOOOOO ????????????????????/ --- Opus 1.73 GEcho1.11+ * Origin: Scouter's Haven (412) 488-8960 (1:129/186.0)