--------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EEQ00010Date: 10/20/97 From: ANKUR GUPTA Time: 01:17pm \/To: TERRY CAIRNS (Read 0 times) Subj: Max4: When? TC> FS> Hi All! TC> FS> I've read of a wishlist for Maximus 4 - when will the TC> FS> new version of Max be released? TC>There is no date set for a Maximus 4...we don't even know TC>if there will be one!!! :) TC>If there is and by the looks of the Y2K debate it may be on TC>December, 1999!!! Hehehe That is the last point till date on the current wishlist ;) Ankur WishList4 ___ X SLMR 2.0 X You call that sexual harassment? Check this out... --- Maximus 3.01 * Origin: Kamas BBS -Bringing India To You- (6:606/52) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EEQ00011Date: 10/20/97 From: ANKUR GUPTA Time: 01:18pm \/To: FERMIN SANCHEZ (Read 0 times) Subj: Max4: When? Hi Gruss, FS>Speaking of that list ... what about sharing it in a place FS>where everybody can have access to it? Say - on the 'net? FS>Or defining some people to be the keepers of the list, FS>where everybody can frequest the latest version of the list FS>with an universal Alias (let's say MAX4)? Done. Ill put it up on the net soon. FS>I'll begin to ask people here in switzerland for ideas to FS>put in that list from now on. Please do! FS> AG-> X SLMR 2.0 X FERMIN SANCHEZ's so stupid he could screw up a one-car FS> AG-> funeral. FS>Hmmm ... :-) I have NO idea who Fermin Sanchez is, got it from someone! Ankur ___ X SLMR 2.0 X Save water--shower with a friend. --- Maximus 3.01 * Origin: Kamas BBS -Bringing India To You- (6:606/52) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EEQ00012Date: 10/20/97 From: ANKUR GUPTA Time: 01:21pm \/To: TARUN SINGH (Read 0 times) Subj: OS/2 BBS options TS>LE>speed, acsii must be there for those still trapped in 2400 TS> AG> Added to wishlist4 if you dont mind Larry. ;) TS> Hay Ankur and what about me yaar ? TS>--Tarun Hi Tarun, long time no see ;) Any suggestions for the list ? Ankur (linux ka haal kya hai? Mujhe khabar karo please) ! ___ X SLMR 2.0 X If you smoke after sex, you're doing it too fast. --- Maximus 3.01 * Origin: Kamas BBS -Bringing India To You- (6:606/52) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EEQ00013Date: 10/20/97 From: CRAIG FORD Time: 07:42am \/To: ALL (Read 0 times) Subj: program * Forwarded (from: HOUSYSOP) by Craig Ford using timEd/2 1.10+. * Originally from Matt Bedynek (1:106/2001) to All. * Original dated: Mon Oct 20, 02:37 I have been looking for a program that will fix the problem of converting fastecho database over to maximus 3.0 msgarea.ctl. I have been writing a utility in virtual pascal and tp 7.0 which means there will be dos and os/2 versions ! :) I learned to do tp in school but had to learn and relearn a few things in just a couple of days. if anyone runs fastecho and maximus and wants to make suggestions the please suggest. I will make it as simple as possible but very useful. . . ie. FE2MAX2.exe \fe\fastecho.cfg \max\msgarea\fidonet.ctl A includes group A It will be completely commandline driven and in the end i will make the source available but with the condition that the program and any counterparts remain FREE! with source given to promote futher devolpment. could someone post this message into the maximus support echo please! :) thanks matt ___ Maximus/2 3.01 - Origin: Dayze of Futures Past (1:106/2001) --- timEd/2 1.10+ * Origin: Dayze of Futures Past * V.Everything * 281-458-0237 * (1:106/2001) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EEQ00014Date: 10/20/97 From: DON GUY Time: 08:51am \/To: DONAT ALLAIRE (Read 0 times) Subj: Year 2000 Greetings Donat! Concerning . From . To . Dated . DA> There is an international standard for writing dates which is: DA> year-month-day. If everybody was using it, we would all be better DA> off. It all depends whose ~international standard~ you read. I've heard the same for the mm/dd/yy format. YY/MM/DD has certain advantages if you need to express dates in a sortable format (e.g. 971020, 971019, etc.). Personally though, I'm far more interested in the month and day than I am year, and prefer to see those rst. -Don ... Error 96: Dead mouse in hard drive. --- * Origin: Extreme Impossibility/2 [Kingston, Ontario, Canada] (1:249/176) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EEQ00015Date: 10/20/97 From: DON GUY Time: 08:58am \/To: GREG FOLEY (Read 0 times) Subj: treatment of Crash mail? Greetings Greg! Concerning . From . To . Dated . DG>> I've been using GoldED for over 3 years now; mail set as Crash from DG>> there is sent as soon as possible, but it adheres to the routing DG>> file's instructions. I take that back. I just tried a quickie Crash message (via GoldED) to a system who'd normally be routed to. Off it went as if I'd sent it Direct. This shoe needs tobasco sauce... :-) -Don ... Windows users would use CP/M if MS told them it was new and good --- * Origin: Extreme Impossibility/2 [Kingston, Ontario, Canada] (1:249/176) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EEQ00016Date: 10/20/97 From: JOE SCHWEIER Time: 09:19am \/To: STEVE HAYES (Read 0 times) Subj: Fossil Hello Steve! 18 Oct 97 14:52, Steve Hayes wrote to Joe Schweier: JS>> Is there a fossil that supports speeds greater than 115200?? DOS JS>> or OS2?? SH> OS/2 doesn't use fossils. SH> Keep well, Some BBSes do... Ditto Joe --- * Origin: Joe's Computer, V32b,V42b,V34,ZyX,U,Z19,ISDN,FAX (1:229/300) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EEQ00017Date: 10/19/97 From: GERRY DANEN Time: 10:35pm \/To: ROBBY DITTMANN (Read 0 times) Subj: Year 2000 GD> First, how incompatible is your BIOS? Can you set the date to Feb GD> 29/2000? If so, observe the day of the week. Now set it to Feb 28/2000 GD> and March 1/2000 respectively. Are the days of the week one earlier and GD> one later as you'd expect them to be? If so, leave the date on March GD> 1/2000, turn the PC off overnight and turn on the next day. Does it say GD> March 2/2000? If so, your BIOS is just fine. Make sure not to run any GD> programs during these tests, because some programs have expiration dates GD> for licenses, or will start doing month end or year end jobs... RD> Actually, I just checked the Year 2000 website and saw that my BIOS RD> was listed as completely incompatible and in need of upgrading. Couple of questions. Which website? And how is it incombatible? Gerry Danen (gdanen@accessweb.com) C+Net BBS @ 403-477-9545 http://www.geocities.com/SiliconValley/Way/9823 2 years, 73 days, 1 hour, 29 minutes, and 55 seconds until January 1, 2000. --- Maximus 3.01 # Origin: C+Net BBS. Programming & Networking. (111:1403/2) * Origin: Alberta Genealogy BBS (1:342/5013) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EEQ00018Date: 10/19/97 From: GERRY DANEN Time: 10:42pm \/To: MICHAEL EPLER (Read 0 times) Subj: Year 2000 ME> Not to belabor this discussion, all I thought several of these folks ME> were asking for is the following: ME> [format] specifies the format to use for file-entry date ME> stamps, and can be any of the following options: ME> mm-dd-yy (U.S.A., default) ME> dd-mm-yy (Canada/England) ME> yy-mm-dd (Japanese) ME> yymmdd (Scientific) ME> Each "yy" to become "yyyy" thus the already flexible MAX remains so ME> but with four digit year compliance the way other apps are being ME> recoded. I would not replace those 4 formats, I would *add* 4: mm-dd-yy (U.S.A.) short form dd-mm-yy (Canada/England) short form yy-mm-dd (Japanese) short form yymmdd (Scientific) short form mm-dd-yyyy (U.S.A.) long form dd-mm-yyyy (Canada/England) long form yyyy-mm-dd (Japanese) long form yyyymmdd (Scientific) long form Gerry Danen (gdanen@accessweb.com) C+Net BBS @ 403-477-9545 http://www.geocities.com/SiliconValley/Way/9823 2 years, 73 days, 1 hour, 29 minutes, and 55 seconds until January 1, 2000. --- Maximus 3.01 # Origin: C+Net BBS. Programming & Networking. (111:1403/2) * Origin: Alberta Genealogy BBS (1:342/5013) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EEQ00019Date: 10/19/97 From: STEVE READ Time: 08:29am \/To: SCOTT DUDLEY (Read 0 times) Subj: Year 2000 Hello Scott, 10 Oct 97 19:45, Scott Dudley wrote to Gerry Danen: SD > Why does compliance mean 4-digit years? If Maximus were to support SD > 2-digit years properly ("01/14/00 = January 14, 2000"), how on earth SD > could that not be compliance? I speak only for myself but prefer 2 digit years (less typing) but seeing 00 for the year will take a bit of getting used to. SD > Furthermore, suppose that Maximus does use four-digit years, but SD > assume that it uses dashes instead of slashes to separate the SD > components. I suppose that this would make it "incompliant" too? Doesn't the COUNTRY option in CONFIG.SYS specify which format to use? Living in the USA I've never worried about it since the default is that's the efault for DOS. SD > As long as date handling is internally consistent and an intuitive SD > way to do things, who cares what the rest of the industry does? We should at least listen to "the rest of the industry" because they may have a better way. SD > I agree that "01/03/103" is awkward and unintuitive, but I fail to SD > see why we *must* replace it with four-digit years in cases when a SD > properly-interpreted two-digit year is unambiguous and works just as SD > well. There is a software package I work with that is keeps all it's dates as 4 digit dates but has a configuration option called "pivot point." It's a 4 digit year (yyyy format). if you enter a date (mm/dd/yy format) where the yy portion of the entred date is >= the yy portion of the pivot point the century for the pivot point is used otherwise the century of (cc + 1) is used The pivot point only controls how dates are entered and displayed -- not the internal value of dates already entered. Example Pivot Date Entered Date Maximus Point or Displayed Uses Internally ===== ============ =============== 1920 01/01/80 01/01/1980 1920 01/01/01 01/01/2001 The only exception to this would be when a caller was entering their dob. It's a little hard to be born in the future a dob of 01/01/17 with a pivot point of 1920 would be 01/01/1917. SD > Obviously, for birthdates, a four-digit year is the way to go. On SD > the other hand, do you think there is really any point in cluttering SD > up the file area listings or the current date display with SD > four-digit dates? I think most people will be comfortable with 2 digits for year in displayed dates (including dob). Steve --- Msged/NT 4.20 beta 2 * Origin: Gulliver's Travels -- Dublin, IN (1:11/201@fidonet)