--------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F5G00138Date: 04/30/98 From: CHRIS ALBERTSEN Time: 02:07pm \/To: TOMMI PITKANEN (Read 0 times) Subj: Max/2 & pipes Hey Tommi, Software? Why not let Maximus send the messages? I do it like this: [apb]%!%n just logged into Node %k I put that in a mec file. If the other users online are not downloading or in a external program, they will see the above message, without the tokens of course. Chris --- Maximus/2 3.01 * Origin: Plastic Tower/2 CBCS - Okinawa Japan - (6:733/1) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F5G00139Date: 04/30/98 From: CHRIS ALBERTSEN Time: 02:08pm \/To: DAVID CHORD (Read 0 times) Subj: File splitter? Hey David, DC> Terry Hollis wrote in a message to David Chord: DC> That's pretty much along the lines of what I am thinking DC> of, a door which they enter (Max passes the current file DC> area path), which splits the file into enough pieces so the TH> SplitIt avoids all that hassel by using one directory. DC> Sounds like it creates hassle in the process. Does it DC> in any way track what the user has already downloaded? DC> What if the user moves the sections they've already DC> recieved to a new directory? before, when I had a timelimit, and slow modems were the norm, I used splitit. I has very low overhead, and the users that used it had no complaints with it. It was very easy to use. It used one file area to put the split files. So the users couldn't move the files. Now if they move them on thier own computer, no program running on the BBS will be able to do anything about that. DC> I'm looking at a program that will : DC> Allow users to split specific files Splitit will. DC> Keep a datebase of which users have files split, and DC> what sections have been sent Splitit leaves that to the user. That way, you don't have to maintain a database on the BBS. If the database gets nuked, what then? DC> Have a 'resend' function for a section, or allow the DC> users to kill sections after recieving them There is only one file split, and the file sizes of the split files are always the same. I never had the need to worry about if the users left the files sections there or not. The next split user would split his file over the old files there. If another user came back to get the rest of his file, he could re-split right no top of the other split files. DC> [possibly] update the users download limits for the day DC> (maybe make it optional) Maximus handled this part. Splitit put the file parts on a Maximus controlled file area I had me for the split files. You may find something else to do this for you, but Splitit is easy to setup, and maintain, with almost no overhead. Chris --- Maximus/2 3.01 * Origin: Plastic Tower/2 CBCS - Okinawa Japan - (6:733/1) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F5G00140Date: 04/30/98 From: CHRIS ALBERTSEN Time: 02:05pm \/To: DAVID CHORD (Read 0 times) Subj: File Split util Hey David, DC> I'm starting writing a file-split util for users to DC> split files that are larger than their download/time DC> limits will allow them to download (I have one 12Mb exe DC> file recently uploaded which I want to allow users to DC> get, without tying the system up for long periods or DC> being limited to those few with enough access to DC> download it). Keep one thing in mind. And that is, the method used my the users to unsplit the files. Chris --- Maximus/2 3.01 * Origin: Plastic Tower/2 CBCS - Okinawa Japan - (6:733/1) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F5G00141Date: 04/29/98 From: ROY J. TELLASON Time: 11:29pm \/To: DAVID CHORD (Read 0 times) Subj: Local File Attaches David Chord wrote in a message to Victor Loberger: DC> Victor Loberger wrote in a message to All: VL> I just discovered that my local file attaches is NOT working. DC> [..] Hm, I've been wondering about that myself. DC> Are you remembering to press A while the cursor is on the DC> attributes field? :-) VL> Here's the stuff from the MSGAREA.CTL file: VL> Attach Base Att VL> Attach Path Attaches VL> Attach Archiver ZIP VL> Kill Attach Ask Normal Why would this stuff be needed in msgarea.ctl? It's supposed to be able to be put in there (someplace? Where?) if you want to override what's in max.ctl, if I read the docs correctly. VL> Is there any other place that I should check? DC> I think this is what you may be missing : DC> In MAX.CTL : DC> Message Edit Ask LocalAttach Normal I just went in and checked, and that was in there. What I was missing was having it in msgarea.ctl like so: Style Squish Local Pvt RealName Attach ...which is in there now. I just tried it, and it works okay now. email: roy.j.tellason%tanstaaf@frackit.com --- * Origin: TANSTAAFL BBS 717-432-0764 (1:270/615) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F5G00142Date: 04/29/98 From: ROY J. TELLASON Time: 11:31pm \/To: DAVID CHORD (Read 0 times) Subj: 31 filetag limit David Chord wrote in a message to Michael Epler: DC> Michael Epler wrote in a message to Minh Van: MV> but WHY ?? did the author impose such a nuisance limiting factor ? ME> For 99.9% of mere mortals this is not a problem or a nuisance ME> factor. As they say, "your mileage may vary." DC> Maybe there's many of us who are annoyed by it, but don't DC> speak up about it? :-) I'll say this: One of the reasons I picked Max in the first place was because it had so _few_ arbitrary limits of that sort built into it compared to a lot of what else was out there at the time. Still, I think that if this one went away too it wouldn't bother me a bit. :-) email: roy.j.tellason%tanstaaf@frackit.com --- * Origin: TANSTAAFL BBS 717-432-0764 (1:270/615) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F5G00143Date: 04/30/98 From: TERRY HOLLIS Time: 03:43pm \/To: DAVID CHORD (Read 0 times) Subj: File splitter? Hello David On 04-29-98 10:09 David Chord wrote to Terry Hollis about "File splitter?" (edited)... TH> SplitIt avoids all that hassel by using one directory. DC> Sounds like it creates hassle in the process. I have been using SplitIt on Whakapapa for several years, I can assure you that there is no maintenance required. It is up to you what you do but it seems to me that you are just making work. DC> Does it in any way track what the user has already DC> downloaded? No! this is not necessary, the MAXIMUS log file keeps track if the sysop wants to know. DC> What if the user moves the sections they've DC> already recieved to a new directory? Only the sysop can move the sections on the BBS, the user can move the sections, on his own computer, anywhere he likes, they will re-assemble provided that they all share the same directory. DC> I'm looking at a program that will : DC> Allow users to split specific files Yes. DC> Keep a datebase of which users have files split, and what sections DC> have been sent No! it isn't necessary, but you could create one from the MAXIMUS logfile, I use FGREP for that sort of job. DC> Have a 'resend' function for a section, or allow the users DC> to kill sections after recieving them No! it is not necessary because each new split kills the previous split. DC> Delete whatever is there after x days (probably make it DC> default to 14, but otherwise be SysOp configurable) This is not only unnecessary, it will cause problems because some users have difficulty following instructions, eg I have seen a confused user split the same file six times before he got the message, your system would have six copies of the same thing. DC> [possibly] update the users download limits for the day DC> (maybe make it optional) This is taken care of by MAXIMUS. DC> (almost)Anything else anyone would like to see in such a program DC> Naturally it'll observe the remaining time for the user, DC> and make the sections fit that limit. The only thing the that I have found wrong with SplitIt, is it's age, the default makes the splits too small. DC> SplitIt doesn't look like it'll be quite what I am after, DC> somethere where the split is done once unless the user DC> doesn't call back in the set time. You should at least try it, your problems are mostly non-existant. Regards - Terry Hollis ... Email Netmail, Terry Hollis <3:772/190> ___ Blue Wave/DOS v2.30 --- Maximus 2.02 * Origin: Whakapapa Genealogy, +64-9-626 5199, Auckland NZ (3:772/190) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F5G00144Date: 05/01/98 From: CHRIS ALBERTSEN Time: 01:12am \/To: ALL (Read 0 times) Subj: Newsgroups into Squish Hey Anyone out there that ports Newsgroups into Max, How you doing it. And if you are using Gigo, could you drop me a line at albertsc@sunnynet.or.jp Thanks in advance. Chris --- Maximus/2 3.01 * Origin: Plastic Tower/2 CBCS - Okinawa Japan - (6:733/1) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F5G00145Date: 05/01/98 From: GARY GILMORE Time: 12:02am \/To: ALL (Read 0 times) Subj: MUFFIN Echo - Rules Posting MUFFIN - The Maximus Support Echo Moderator - Gary Gilmore, 1:2410/400 (garyg@oeonline.com) Asst. Moderator: Kevin Bentz, 1:2410/213 Last updated: 9/25/97 1 - This echo is for MAXIMUS support. Messages posted here should pertain to Maximus and related utilities. Discussions that start to lean more toward Squish, MEX/MECCA scripts or 3rd party software should be continued in one of these echoes: - TUB, the Squish echo. - MECCA, the MEX/MECCA scripts echo. - MAXDEV, development of/support for 3rd party Max/Squish utils. English is the official language of this echo. 2 - When someone posts a message requesting help, please try to be as helpful and accurate as possible. 3 - This echo is restricted to sysops (or soon to be sysops) only. It may not be made generally available to your users. 4 - Aliases are not allowed. Please post using your real name. If you aren't sure, check your birth certificate. 5 - Avoid creating unneeded traffic. Here's a list of basic "No-no's": No: BBS ads, 'test' messages, "where are you from" chains, multiple tearlines, replies to off-topic messages, encrypted messages, PGP sigs, multiline sigs or taglines, playing moderator (unless you -are- the moderator), additional headers/footers in messages, hi-ascii/ascii "artwork" (we really -don't- care to see it), uuencoded files, or huge amounts of over-quoting. ("high-bit" ASCII characters are permitted ONLY in the context of demonstrating something directly related to Maximus or a related util. Other uses are not allowed. ANSI is -never- allowed.) If a program (reader, tagline mgr, etc.) is adding a lot of extra junk to messages, please don't use it here. (The moderator will decide what's "extra junk", and let you know.) "Internet-style" signatures are -greatly- unwelcome, as well as listing every email account or FTN-type address you have. Leave it out, please. One -short- line is an "acceptable" signature. Please, do not use a "shotgun" approach to posting, cc'ing a message to all Maximus-related echoes. Pick the one echo that applies to your topic, and post the message only in that one. 6 - Please, limit quoting in your replies. (If you're quoting more than a couple lines, you're probably quoting too much.) Never quote tag/ tear/origin lines. 7 - ANY "OS Bashing" will be strongly frowned upon. Don't do it. Period. This also means, leave your cutesy "OS put-down" tag/origin lines out of this echo. (Grow up, ok?) 8 - Rules of Common Courtesy apply at -all- times. If you want to argue with, or complain to someone, do it in netmail. 9 - No file announcements are allowed, unless done via the moderator(s). You may, however, help others find programs. When doing so, please include filenames, and what (if any) restrictions you have on file requests. In the case of files via ftp, *try* to include the site & directory location of the file as well. Ads for any *directly* Maximus-related utilities may be posted once, and only by the program author. Please, keep them -short-. (One screenful should be plenty.) 10 - This echo may not be gated (in or out) to any other FTN-style network, or the internet, without without prior permission of the moderator. Authorized gates will be published in the ELIST*.* listing for this echo. Changes will be made to this list, as needed. Input is welcome, but via netmail only, please! (Arguing about moderator decisions/rules is NOT welcome in the echo... use netmail.) Those breaking the rules will usually be warned via netmail. Failure to follow the simple rules of this echo could get you (or the BBS you post from) banned from the echo. Hopefully, we won't have to go that far. Thank you for using the MUFFIN echo, --gary, MUFFIN/TUB/MECCA/MAXDEV moderator http://oeonline.com/~garyg/maximus/ --- NetMgr 1.00+ * Origin: bloom county bbs * dearborn, mi * (313)582-0888 (1:2410/400) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F5G00146Date: 04/30/98 From: VICTOR LOBERGER Time: 07:53pm \/To: JAIME DOMENECH (Read 0 times) Subj: JFREQ and Maximus Hi Jaime, JD> I use jfreq since one year without problems, with JD> FrontDoor 2.12 and Maximus 3.01. I can send my setup JD> file to your Internet address, if you are interested. Sounds good! I suspect that my problems is with JFREQ because Argus *does* do it's thing. On the other hand, JFREQ *does* send all the files BUT those that are on the CD-ROMs. I wonder if I have the access fouled up somewhere? I sure have something fouled up! 8-) Thanks! Victor --- Maximus/NT 3.01b1 * Origin: Aarrgghh! BBS-West Bend, WI USA (414) 334-7041 (1:154/731) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F5G00147Date: 04/30/98 From: VICTOR LOBERGER Time: 07:53pm \/To: DAVID CHORD (Read 0 times) Subj: MECCA and file-browsing Hi Dave, VL> The FDOMORE.MEX file should be available on the Maximus Home Page DC> Would you mind e-mailing it to me? No problem and it's on it's way to you. Victor --- Maximus/NT 3.01b1 * Origin: Aarrgghh! BBS-West Bend, WI USA (414) 334-7041 (1:154/731)