PC Online 1997 October

home *** CD-ROM | disk | FTP | other *** search

/ PC Online 1997 October / PCO1097.ISO / FilesBBS / DOS / MCU10G13.EXE / install.exe / MCMUTIL.DOC next >

Wrap

Text File | 1997-08-18 | 26.6 KB | 573 lines

│ ─·─── ┌────┬────┌──────┌────┬────┌──┐ ┌──┌──────┌────┌────┐ │ │ │ ┌──│ │ │ │ │ └─┐ ┌│ │ │ │ │ │ │ └──│ │ │ │ └─┘ │ │ ││ │ └──┐ └──┴───┴──└──────└──┴───┴──└───────┘ └───┘└────└───────┘ Version 1.0g (C)opyright 1994-97 by Grischa Brockhaus, SkullSoft English Documentation ( not my native language, sorry! ;-) ) ───────────────────────────────────────────────────────────────────────── Introduction: A friend of mine crashed me a new mailer. He asked me to have a look at it. It was MCMAIL, a new Mailer from Germany. Because of it's Binkley outbound style it was no problem, to convert from my old mailer (Portal of Power) to MCMAIL. He promised to pay a MCMAIL key, if I would convert my POPUTiL to MCMUTiL. :-) Okay Michael and all you other sysops out there, here it comes: MCMUTiL! If you have used POPUTiL once, you will learn very fast how to handle MCMUTiL. MCMUTiL is very similair to it, but it is only supporting the RA2 as BBS-SoftWare. The reason for this is that I'm using RA2 myself and 90% of my programs are registered by RA sysops. ───────────────────────────────────────────────────────────────────────── ShareWare: I decided to release this utility not as cardware (as I did with POPUTiL) but as ShareWare. This means: You are allowed to evaluate MCMUTiL for 30 days without paying anything. If you want to use MCMUTiL after this evaluation- period, you have to pay for it, else you have to delete it. If you want to buy MCMUTiL you have to print out the registration form valid for your country, fill it out and send it to the adress named in the registration form. You can asure to have a valid Registration by checking my PGP sign with my public PGP key. You'll get my public PGP key if you request PGPKEY at my site (2:2410/1005). You may send you registration also via netmail. But please think about, that netmails may not reach the location, they were adressed to. If you don't get any reaction on yu netmail, you should try to send it again. ═════════════════════════════════════════════════════════════════════════ MCMUTiLs parameters: Usage : MCMUTIL.EXE <parameter> [/NODE<Nr>] [/C:<MCM config>] The parameter /NODE<Nr> defines the aktual nodenumber of MCMAIL, MCUTiL is working in. If you don't specify this parameter, MCMUTiL will read the environment variable %TASK% for it. If this is not set it will use the node 1 for default. Per default MCMUTiL will use the MCMAIL.CFG defined in MCUSETUP. If this entry is left empty MCMUTiL will use MCMAIL<Node>.CFG in the directory specified as maindirectory of MCMAIL. With the parameter /C: you can cause MCMUTiL to use the configuration file named after the /C: parameter. *One* of the folloing parameters have to be used: /CLEAN ────────────────────────────────────────────────────────────────── This will clean up your outbound directories. MCMUTiL will scan yur outbounds for 0 length files and will delete them. It won't delete any semaphores found in the outbounds. Empty outbounds will be removed, for example empty point-directories or normal zone outbounds. /DLC ────────────────────────────────────────────────────────────────── MCMUTiL will scan the logfile defined for the current node for sent files. If a file was sent after the last call of MCMUiL /DLC, MCMUTiL will scan the RemoteAccess 2.+ filebase, if this file is listed there. If this is the case, MCMUTiL will increase the download counter of this file. /DLC /NOEEP ──────────────────────────────────────────────────────────── If you use the /NOEEP parameter with the /DLC, then MCMUTiL won't update download counters for files left your system via a request processor. This might become handy for Request Processors (like EasyERP), that update the DLC's on their own. /DPOLL ────────────────────────────────────────────────────────────────── Usage: MCMUTiL /DPOLL=<adr1>,<adr2>,..;<dir> MCMUTiL will immitate a poll on a system having the adresses <adr1>,<adr2>,.. The files will be "transfered" to the directory <dir>. You only have to copy the files in that directory to a disk. The according system copys the files into in it's inbound. /INH ────────────────────────────────────────────────────────────────── MCMUTiL will append the last BBS caller to the inbound-history list of MCMAIL. I use MCMUTiL in the Spawnbbs.Bat: :start rem ** start BBS RA.EXE -E25 -B%3 -P%2 -T%5 rem ** React on errorlevels of RA rem ** refresh lastcaller list and inbound history C:\POP\UTILS\MCMUTIL.EXE /NODE%TASK% /INH /ANS Your inbound history window will look like that: Minutes been online ════════════════════════╕ Times called ══════════════════════╕ │ Baudrate ═════════════════╕ │ │ Marks a BBS caller ═══════════╕ │ │ │ Name ══╕ │ │ │ │ ┌Settings─────────┬In - Sessions─────────────────────────────┐ │Port : xFos COM2│04:49 Grischa Brockhaus [BBS] 14400,21,5│ │Speed: 14400│ │ │Event: @ n@,24:00│ │ │Flags: CBP│ │ └─────────────────┴──────────────────────────────────────────┘ ╒═══════════════════════════════ Marks a BBS call │ ╒════════════════════════ Baudrate of caller │ │ ╒═══════════════════ Total-Calls of caller │ │ │ ╒═════════════════ Nodenumber of RA ┌History-Info─────────────────────────────┐ │ [BBS] 14400,21,1 Berlin │ < Location │ Mc.Greg Grischa Brockhaus │ < Name ├─────────────┬─────────────┬─────────────┤ │ In 0KB │ Baud 14400 │ Start 04:49 │ < LogOn Time Downloads > │ Out 0KB │ CPS 0 │ Day 15Oct │ < LogOn Date today │ All 0KB │ Cost 0 │ Mins 20 │ < Online time ├─────────────┴─────────────┴─────────────┤ │ Press any key to continue │ └─────────────────────────────────────────┘ You can call MCMUTiL /INH as often as you want, MCMUTiL will rememner its last run and will update only with really new callers. /INH /ANS [/NS] ───────────────────────────────────────────────────────── This parameter does exactly the same, as the normal /INH parameter. But MCMUTiL will also create the lastcaller ANSi/ASCII defined in MCUSETUP. You may define yourself, how this ANSi should look like. I added some examples to the archive. You have to create 2 templates in the directory of MCMUTiL and name them LASTCALL.ANS and LASTCALL.ASC. These templates will be caculated on runtime while creating the lastcaller list. You may use the following macros inside the templates: @NUM Count of last callers listed @BBSNAME The name of your BBS as defined in RA The rest of the macros has to be used in *one* line *only*. MCMUTiL will use them to display the the last callers. If MCMUTiL finds one of the macros in a line, it will repeat the line for every last caller. (Please just have a look at the example templates, it's easier as it seems now.) @USER:<width> The line will be overwritten at this place with the name of the caller. MCMUTiL will overwrite as much letters as defined with <width> @LOCATION:<width> The same as @USER but done with the location of the caller @LOGON Logon-LogOff time. At this position 11 letters will be overwritten. for example 01:12-01:39 @BAUD Will be replaced with the connect speed. This will be 5 letters always and formated to the right margin. @BAUD@ Will be replaced with the connect speed. This will be 6 letters always and formated to the right margin. (Needed for bundled ISDN calls) @N# Will be replaced by the nodenumber the user was online. 3 Digits formated to the right margin. If you don't registered MCMUTiL, it will create an ANSi only of the last 4 callers. After registering it, you are allowed to define this count yourself. It is possible to create seperate lastcaller ANSi's for each task. Just specify a $T in the name of the lastcaller ANSi, it will be replaced at runtime with the actual task. (for example: C:\RA\TXTFILES\LAST$N.ANS) For default MCMUTiL will sort the inbound-history entries before creating the LASTCALL.ANS. If you don't want that for any reason, use the /NS parameter. The LASTCALL.ANS will be sorted in the same way, as you see it in your MCMAIL inbound-history-window. ! The lines in the TPL files MAY NOT BE LONGER than 255 bytes. If you have ! very colored TPL's, use A3E for saving them ! /MULTILC ─────────────────────────────────────────────────────────────── This is a special version of the /INH /ANS feature. /INH /ANS will create ANSi files for one single node each. In mulitiline boards normaly a lastcaller holding entries of all lines is wanted. So here is the parameter for this. /MULTILC won't patch the INH files of MCMAIL at all, it only creates a lastcaller of all nodes found by MCMUTiL. In MCUSETUP you may define, how many nodes MCU is searching maximal. MCMMUTiL is using the template MULTILC.ANS/ASC in it's own directory. Your BBS batch should look like this, if you want to use the Multiline- Lastcaller: :start rem ** start BBS RA.EXE -E25 -B%3 -P%2 -T%5 rem ** React on errorlevels of RA rem ** refresh inbound history and *don't* create ANSi's C:\POP\UTILS\MCMUTIL.EXE /NODE%TASK% /INH rem ** Now create the multiline ANSi's: C:\POP\UTILS\MCMUTIL.EXE /NODE%TASK% /MULTILC /MOVERVD [<directory>]────────────────────────────────────────────────── This option will move the netmails already read by you from your netmail folder (or the folder defined with the directory after the parameter) to a seperate directory for recieved netmails. You have to configure the directory for recieved mail in MCUSETUP. This option will keep the ammount of mails in your main netmail dir low and will speed up netmai tossing/importing. /MOVESNT [<directory>] ────────────────────────────────────────────────── This option will do the same as above but to sent netmails. You have to define a directory for sent netmails in MCUSETUP. /NOTIFY ───────────────────────────────────────────────────────────────── This option send notify netmails to all sysops in your extendet nodedatafile. You have to edit the file NOTIFY.MSG in the MCU directory for this option. You may use macros in the NOTIFY.MSG. They are the same as the commands in the extendet nodedatafile but with @ as brackets (@Sysop@, @System@, @Phone@,..). MCU will inform all sysops exept of sysops with Capability N. N is not a capability flag used by MCM at the moment only MCU will interpret it as "N - Don't write notify messages". This flag might change, if MCM starts using this flag. /PINT <text> ──────────────────────────────────────────────────────────── This option puts an information string <text> in the multiline info window of McMail. You may use it in your tosser batch for example with MCMUTiL /NODE2 /PINT Tossing incoming mail This will show "Tossing incoming mail" for node 2 in the multiline window. /POLL ────────────────────────────────────────────────────────────────── With this parameter you can force MCMUTiL to poll a node. This is the same like pressing Alt+P in MCMAIL. Usage : MCMUTiL.EXE /POLL <Adress> /RENUM [<directory>] ──────────────────────────────────────────────────── Will renumber the netmail-folder you defined for this node and updates the lastread counter depending on this. I use this in the RENUM.BAT of timEd for example. In the registered version of MCMUTiL you may specify the netmail- directory, MCMUTiL should use. If not specified via command line, MCMUTiL will renumber the netmails in the directory defined in MCMAIL.CFG. /REQ ────────────────────────────────────────────────────────────────── Usage: MCMUTiL.EXE /REQ <adress> <file> This will prepare a filerequest at <adress> of the file <file> Example : MCMUTiL /REQ 2:2410/1001.1 MCMU10G5.RAR /SEND ────────────────────────────────────────────────────────────────── Usage : MCMUTiL.EXE /SEND <adress> [^|#]<file> <flo> This will order MCMAIL to send the <file> to the <adress>. If you use a ^ before the filename, MCMAIL will truncate the file after sending, if you use a # , MCMAIL will delete it. <flo> is a char, that marks how the file should be sent: I : Immidiate D : Direct F : Normal H : Hold Example : MCMUTiL.EXE /SEND 2:2410/1001.1 #TEST.TXT I /SITE ────────────────────────────────────────────────────────────────── This will change the siteinfo and location information of MCMAIL. MCMUTiL will need a file called SITEINFO.TXT. It has to be located in the directory of MCMUTiL. This file will hold a list of possible siteinfos and locations, you want to be used by MCMUTiL. How the file SITEINFO.TXT should be build up you should look up from the example file in the archive. The siteinfo/location informations will be displayed by most mailers. Most sysops think to display only our real sitinfo and location is a little bit boaring, so this is for you. Use it to display some funny remarks. MCMUTiL will put this siteinfos / locations into the configuration of MCMAIL. Everytime you call it, it will enter a new one. The changing of the siteinfo / location only takes effect after restarting MCMAIL, so you should write this to your MCM.BAT before you start MCMAIL. Until registering of MCMUTiL will only use the first 5 siteinfos / locations. After registration, the number of siteinfos and locations are unlimited. HINT: If you want to speedup the site option copy the relating Infos from your MCMAIL.CFG to a seperate (short) configuration file and name it for example SITE.CFG. After this include SITE.CFG into your MCMAIL.CFG and call MCMUTiL /C:SITE.CFG /SITE This way MCMUTiL only have to rewrite a very short textfile. (But you have to add the Sysop command in the SITE.CFG, because else MCMUTiL won't be registered this way!) /TL=<TIMELOG.BBS> ─────────────────────────────────────────────────────── With this option you are able to add the online times of your mailer to the RA busy-per-hour graph. MCMUTiL will scan the in- and outbound history of the relating node and will add all online minutes found there into the TIMELOG.BBS named with the parameter. (TIMELOG.BBS is a RA file saving the online minutes of the BBS.) Now your users will see the busy-per-hour graph of your whole system instead of the BBS only. This option may used as often as you want, MCMUTiL will remember what was already added. Please give always the correct TIMELOG.BBS for the depending node ! In a multinode environment TIMELOG.BBS is found in the line directory of RA else in the maindirectory. Example: MCMUTiL.EXE /NODE%TASK% /TL=C:\RA%TASK\TIMELOG.BBS /TOSS ────────────────────────────────────────────────────────────────── This option will convert all the netmails with special attributes in your netmail folder to binkley style FLO files. Special attributes are those not handled by the normal Netmail-Packer (FileAttach, FileRequest, Immidiat, Crash, Direct, Hold mail). You should use this feature behind your normal Tosser. /WOH ─────────────────────────────────────────────────────────────────── MCMAIL has a "What's on hold window" since version 1.0g3. With the Parameter /WOH you can create a WOH Ansi for your BBS. The same entries as in the WOH window will be listed in the WOH ANSi. This means: MCMUTiL won't scan the outbound itself, it will read a file created by MCMAIL while scanning for the WOH window. This makes the creating of the ANSi very fast, you can use this often without loosing system performance. The name of the ANS/ASC file to be created is defined in MCUSETUP. The look of the WOH.ANS is defined free by templates created with your favorite ANSi Editor again. I have put some examples to the Archive (WOH_TPL.EXE). The following macros are valid: @BBSNAME The name of your BBS as defined in RA. @DATE Date of creating the ASNi (Width=9) @TIME Time of creating the ASNi (Width=5) @ZONE The line holding this makro will be used everytime when the Zone is changing in the WOH window. The macro will be replaced by [Zone=<Zone>] The following macros may be used in one line only (together!), because every line holding one of these macros will be used for displaying the WOH entries. @ADRESS:<width> Will be replaced with the address of the WOH entry. <Width> is the width to be used. @NAME:<Breite> Will be replaced by the name defined in MCUWOH.CTL for this node. @FL Will be replaced by the type(s) (flavours) of the pakets. The width is 7 always. @FS Will be replaced by the size of the paket. Width is 5 always. @FN Count of all files in the paket. Width=5 @FD Date of the oldest file in the paket. Width=5 ! The lines in the TPL files MAY NOT BE LONGER than 255 bytes. If you have ! very colored TPL's, use A3E for saving them ! Configuration-file MCUWOH.CTL: You can define names for Nodes, that are listed in your WOH window. This is done in the MCUWOH.CTL that has to be located in the directory of MCMUTiL. Everyline has to hold an address and a name following to it. I added a sample MCUWOH.CTL to the archive. Semaphores ────────────────────────────────────────────────────────────── If MCMUTiL is called with the parameters /POLL, /REQ, /SEND or /TOSS it will create the semaphores for rereading the outbound and for rebuilding the WOH window. All new things done by MCMUTiL will be available in MCMAIL immidiate. ═════════════════════════════════════════════════════════════════════════ Configuration of MCMUTiL ──────────────────────────────────────────────── The configuration of MCMUTiL is very simple. It will try to get all configuration from it's environment. It will read the MCMAIL.CFG file of the actual node for example and will read in the directory defined by the RA environment variable for settings of RA. But some things you have to configure. This is done with the configuration utility MCUSETUP.EXE. ╒═╡ Configuration ╞═════════════════════════════════╕ │ │ │ MCMAIL directory : C:\MCMAIL │ │ MCMAIL.CFG : C:\MCMAIL\MCMAIL.CFG │ │ Rcvd directory : C:\NETMAIL\RVD │ │ Sent directory : C:\NETMAIL\SENT │ │ │ │ ANSi Setup │ │ │ ╘═══════════════════════════════════════════════════╛ First you enter the directory, where MCMAIL is located. The second entry defines a default configuration file of MCMAIL. If this is left empty, MCU will use <MCMAIL-Dir>\MCMAIL<Node>.CFG. If the /C: partameter is used, it will overwrite this entry. Rcvd- and Sent-directory are the relating directories of the switches /MOVESNT and /MOVERVD. If you push [Enter] at the "ANSi Setup" you can configure the the creating of the LastCall and WOH ANSi (Option /INH /ANS, /MULTILC and /WOH). A new submenu will open: ╒═╡ ANSi Setup ╞════════════════════════════════════╕ │ │ │ MULTI LC ANS : C:\RA\TXTFILES\LASTCMUL.ANS │ │ MULTI LC ASC : C:\RA\TXTFILES\LASTCMUL.ASC │ │ Check nodes : 10 │ │ LASTCALL.ANS : C:\RA\TXTFILES\LASTCALL.ANS │ │ LASTCALL.ASC : C:\RA\TXTFILES\LASTCALL.ASC │ │ Use Handles : [ ] │ │ Hidden Users : [ ] │ │ Local Calls : [ ] │ │ OUTMAIL.ANS : C:\RA\TXTFILES\WOH.ANS │ │ OUTMAIL.ASC : C:\RA\TXTFILES\WOH.ASC │ │ List Dumbterm : [ ] │ │ Max Entries : 15 │ │ WOH.ANS : C:\RA\TXTFILES\WOH.ANS │ │ WOH.ASC : C:\RA\TXTFILES\WOH.ASC │ │ │ ╘═══════════════════════════════════════════════════╛ The two first lines define the name of the multiline lastcaller ANS/ASC file to be created. Check nodes defines, for how many nodes MCMUTiL should search maximal while creating the multiline lastcaller The two lines after define the name of the Lastcall ANS/ASC file to be created. With the switch "use handles" you can switch on, that MCMUTiL will use handles in the lastcaller ansi instead of realnames. Hidden users tells MCMUTiL, if it should list hidden Users in the Lastcaller ANSi. Local calls tells MCMUTiL wether it should ignore local calls or not. All these switches will configure the multiline lastcaller, too. Outmail.ans/as is the name of the file used for the /OUT option. List dumbterm tells MCMUTiL wether to list dumbterm calls in the outmail ANSi or not. With max. Entries you define the maximal ammount of lastcallers shown in the lastcaller and outmail ansi. At the WOH inputs you define the name of the WOH.ANS/ASC file to be created. If you are ready with this, press [Esc] to return to the main menu. Press F10 to open the options menu: ╒═╡ Options ╞════════════════╕ │ │ │ (R)oute Pointmail [■] │ │ (D)el Exported [ ] │ │ Del (M)ine 0-Length [ ] │ │ Del (A)ll Send [ ] │ │ Use (Z)ones [■] │ │ (S)et Send-Flag [■] │ │ (I)nform Sysop [■] │ │ │ ╘════════════════════════════╛ Route Pointmail: Normally the netmails will be exported as written. this means: No routing is possible with MCMUTiL *AT ALL*. If you swith on this option, MCMUTiL will export pointmails to their boss nodes. The bossnode must route the mail to their points then. This won't work with hold or direct flagged mails, because this would be nonsence. Del Eported: This will cause MCMUTiL to delete *ALL* mails after exporting them. Normally this swith should be disabled, MCMUTiL will delete mails with the "Kill message when sent" independent of this switch. Del mine 0-Length: This will cause MCMUTiL to delete all mails sent to your without any text in it (Mail attaches and so on) while working in /TOSS mode. Del All Sent: This is similair to the "Del Exported" swith, but it will also delete mails exported by other tools. It will delete all mails that have a SENT flag. Normally you should disable this switch ! Use Zones: Should always be enabled if you have more than one zone. Set Sent-Flag: Should normally be switched on ! This will cause MCMUTiL to set the SENT flag on all mails exported by itself. The SENT flag will tell MCMUTiL and other tools, that the mail was already exported and will prevent them from exporting the mails again. Inform Sysop: This will cause MCMUTiL to inform the sysop via Netmail about some action. This feature is not ready yet. ═════════════════════════════════════════════════════════════════════════ More tools added to the packet ────────────────────────────────────────── I have added some more tools to the archive. They will explain temself if called without parameter. Here comes a short description of them: MCUPHONE This is a converter for some terminal phonebook files into MCMAIL's BBSDATA.CFG file for the dumbterm. At the moment it can convert Terminate 1.4+, FrontDoor 2.02 and FrontDoor 2.20 phonebook files. MCUMODE With this tool you can change the actual textmode. This means Rows and collumns. [MCUVIEW] This is a "replacement" for MCMVIEW. But it has many more usefull features. You'll see online users in the watch windows with complete userdoes support, may send online messages to the nodes and receive them, call the multiline chat, watch the logfiles of your mailer and BBS of all nodes in ONE very comfortable list, view the busy-per-hour graph of the lines and much more ! MCUVIEW is the multiline tool for the sysop, who want to be informed about everything with one look. This is a tool delivered in a seperate archive, because it is too big and has too many features. Look for MCUV????.RAR. If you register MCMUTiL, you will be registered for this tool, too.