--------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EET00003Date: 10/22/97 From: JIM WOODWARD Time: 04:00am \/To: CALIXTO ONG II (Read 0 times) Subj: Re: Bragging about max/2 COI> What version of OS/2 are you using? I'm COI> planning to shift to OS/2.. JW> I am using warp 4, but warp 3 was just as stable. COI> Am I going to change a lot of stuffs in my current Dos Based COI> Maximus Settings If I shift to OS/2? What are the benefits COI> I'm gonna get? Thanks in advance.. It is my opinion that you will gain speed and stability. If you run a one line BBS, the gain will be small, but if you run a multi-line BBS, then it is well worth the effort. The only problems that I can forsee is learning how to get the dos-doors to run properly. I got all 50+ of my doors to run, so it can be done. Jim --- Maximus/2 3.01 * Origin: Woody's NutHouse (1:268/412) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EET00004Date: 10/23/97 From: ZORCH FREZBERG Time: 08:59pm \/To: ROBBY DITTMANN (Read 0 times) Subj: Okay... In a msg on , Robby Dittmann of 1:133/8003 writes to Zorch Frezberg: ZF>> d:\max\maxn.exe -s%b -b%B -n%n -p%h RD> I'm guessing that you are trying to use the NT version of Maximus RD> under WIN95. If so, that is your problem. Max/NT will not find RD> the fossil. No, no, no...sorry, I realize why you thought that. The above was the string provided in the Argus HELP file. My bad. RD> Try running the DOS version of Max. If this isn't RD> the case, let me know what versions and what OS and I'll see what RD> else I can think of. Will try Friday morning... A question I _do_ have...What COM port (if any) do I point Maximus to on a TCP/IP connection? Or do I need a 'virtual modem' to be at a normal COM port for it to work under this set-up? -zf- --- msgedsq 2.1 * Origin: Fido Bites It's Masters...What Next? 209-251-7529 (1:205/1701) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EET00005Date: 10/22/97 From: GARY GILMORE Time: 03:02pm \/To: TERRY CAIRNS (Read 0 times) Subj: Max4: When? TC> Ummm...Why is asking "when's the next version of Maximus coming out" in TC> the Maximus Echo, off topic??? Because it's a never ending thread, that doesn't do any good. People can ask 10 times a day, and that won't make a new version appear. The standard reply is "When it's released", so asking the question is a waste of time. TC> Is Maximus discussion off topic too??? :) Umm, I doubt it. --gary / MUFFIN/TUB/MECCA/MAXDEV moderator --- Maximus v3.01 * Origin: bloom county bbs * dearborn, mi * (313)582-0888 (1:2410/400) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EET00006Date: 10/23/97 From: GARY GILMORE Time: 12:45am \/To: ALL (Read 0 times) Subj: New in the MaxFDN New in the Maximus File Distribution Network... (MaxFDN) (Announcement made with moderator permission) --------------------------------------------------------------------------- Area : MAXUTIL - MAX: Maximus/Squish Utilities --------------------------------------------------------------------------- MMAIL21.ZIP 52,994 Maximus 3.x Mass Mail System, v2.1. Allows "mass mailings" to all users on your BBS. [Total bytes of announced files: 52,994] For Max 3.01; DOS freq "MAX", OS/2 freq "MAXP", Win32 beta freq "MAXN". These files available at 1:2410/400 (any time except ZMH), as well on other systems carrying the MaxFDN. Carry the MaxFDN on your own system! Contact your local file echo provider, or ask the sysops in your area about getting a feed. (The MaxFDN is carried on the IFDC FileGate, and distributed to the Filebone, paonline, FidoGate, Planet Connect and other sources.) Freq "MAXFDN.POL" from 1:2410/400 for MaxFDN policies. Files hatched in the MaxFDN are also available at: WWW: http://oeonline.com/~garyg/maximus/ FTP: ftp.oeonline.com/pub/Maximus/ If you have a file you'd like to share with other Max sysops, send it, with a -short- description, to 1:2410/400 (preferred method) -or- 1:2410/213. You may also send smaller files to "garyg@oeonline.com" as a file attach. Thank you. --- * Origin: bloom county * MaxFDN Headquarters * 313-582-0888 (1:2410/400) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EET00007Date: 10/23/97 From: GARY GILMORE Time: 02:26pm \/To: ALL (Read 0 times) Subj: New in the MaxFDN New in the Maximus File Distribution Network... (MaxFDN) (Announcement made with moderator permission) --------------------------------------------------------------------------- Area : MAXUTIL - MAX: Maximus/Squish Utilities --------------------------------------------------------------------------- DMEBBS10.ZIP 36,640 Damebbs v1.0 extracts DIZ files from archives in a given subdirectory and makes a listabbs.txt file in Maximus files.bbs format [Total bytes of announced files: 36,640] For Max 3.01; DOS freq "MAX", OS/2 freq "MAXP", Win32 beta freq "MAXN". These files available at 1:2410/400 (any time except ZMH), as well on other systems carrying the MaxFDN. Carry the MaxFDN on your own system! Contact your local file echo provider, or ask the sysops in your area about getting a feed. (The MaxFDN is carried on the IFDC FileGate, and distributed to the Filebone, paonline, FidoGate, Planet Connect and other sources.) Freq "MAXFDN.POL" from 1:2410/400 for MaxFDN policies. Files hatched in the MaxFDN are also available at: WWW: http://oeonline.com/~garyg/maximus/ FTP: ftp.oeonline.com/pub/Maximus/ If you have a file you'd like to share with other Max sysops, send it, with a -short- description, to 1:2410/400 (preferred method) -or- 1:2410/213. You may also send smaller files to "garyg@oeonline.com" as a file attach. Thank you. --- * Origin: bloom county * MaxFDN Headquarters * 313-582-0888 (1:2410/400) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: EET00008Date: 10/23/97 From: GERRY DANEN Time: 09:40pm \/To: SCOTT BROWN (Read 0 times) Subj: Year 2000 GD> yyyy-mm-dd (Japanese) long form GD> yyyymmdd (Scientific) long form SB> Funnily enough, those last two match the ISO standard for electronic SB> data interchage involving dates (If I remember correctly, the SB> standard's identification is ISO 8610, and ISO 8610-alt). SB> However, I should point out that Scott Dudley is correct - as long as SB> his program INTERNALLY deals with dates in a consistant manner which SB> takes into consideration the century, it doesnt matter how it's SB> stored. Your dissertation was really not needed, as Scott has already indicated that he's not about to do anything... SB> Many people have publically chastized Scott for saying that 100 = 2000 SB> because it's not 4 digits. I'm sorry, but 4 digits is only required SB> for interchange such that it is explicitely indicated giving no chance SB> of error of interpretation. You _can_ interchange data with less than SB> 4 digit years if you so desire PROVIDING you have an unabmiguous SB> representation. SB> Many (MANY) software products use the year as an offset from another SB> year, and store only 3 digits as their internal representation (dates SB> are stored as offsets from 1800), and only produce 4 digit years when SB> required for export of data. CAPS-I-L (an Insurance Adminstration SB> system quite common in Canadian Insurance carriers) uses this format, SB> and I've even found a few Canadian banks which interchange data using SB> this format. SB> Internally, consistancy and the ability to represent more than 100 SB> years of time is what is required. Externally, unambiguous date SB> interchange is what is required. The implementation of both of these SB> things is how those of us given the task of century compliance will SB> avoid problems when the century increments. SB> And finally, for anyone who tries to say "but the _INDUSTRY_ is doing SB> xxxxx", I beg to differ. As a project manager currently working on SB> upgrading mulitple millions of lines of code to ensure century SB> compliance, and dealing with external service providors, I can SB> honestly say that there is no such thing as a common representation. SB> The service providor, be it as large as a bank, or as small as the SB> outside print shop used for those special presentation brochure print SB> jobs, makes their own decision on what is best for them, and then SB> requires that you interchange data with them in their format. SB> We (in the form of my employer) can, and have pushed for the use of SB> ISO 8610-alt with many providors, and as providor to other companies, SB> we require the use of ISO 8610-alt for all electronic data interchange SB> activites... but it is not the norm, nor is it (or any other format) SB> likely to ever be the sole format for date interchange between SB> different vendor's systems. If nobody ever starts, indeed it will never happen. SB> The only way there is ever going to be a single format for date SB> representation is if we have one company producing all software for SB> all of the world... and that isnt going to happen. Sure it is. As sson as Bill is done with the DOJ... Gerry Danen (gdanen@accessweb.com) C+Net BBS @ 403-477-9545 http://www.geocities.com/SiliconValley/Way/9823 2 years, 69 days, 2 hours, 24 minutes, and 3 seconds until January 1, 2000. --- Maximus 3.01 * Origin: C+Net BBS. Programming & Networking. (1:342/1017)