Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / WHO28.ZIP / WHO.DOC < prev next >

Wrap

Text File | 1995-04-24 | 19.3 KB | 481 lines

■ WHO 2.8 Manual ■ Author... DaCoTa Sysop of Insanity Systems +31-85-636369 ■ Disclaimer... I only guarantee it will use 13961 bytes of your precious diskspace and that it works perfectly at my place. ■ What's it supposed to do?.. It checks all of the supported programms on callers and if someone has made an inbound call, the history file of the mailer will be updated with that info. This way you can track all incoming calls from your mailer and you don't have to gaze through kilos of logfiles. WHO supports eigth programms: ■ Mailers FrontDoor 2.x InterMail ■ Bulletin Board Systems RemoteAccess 2.x ProBoard 2.x SuperBBS 1.x ■ Rear-End FAX Receivers BGFAX 1.x ZxXEL FAX 2.x and 3.x ■ Voice Mailboxes (VMBs) ZyXEL FAX 3.x If you have another BBS system or a different mailer, give me a sign and I will see what I can do for you. If you have complete structure files of a BBS system, I could add it in 15 minutes if you supply the info to me. ■ How does it work?.. Just put it in your batchfile, just start it every time after something or someone called. A good position is right before the mailer is started or right after the BBS, FAX and/or VMB software. ■ What do all those things mean?.. ■ With FrontDoor 2.x... The environment setting FD should be set to point to the directory where SETUP.FD is located, e.g.: SET FD=C:\BBS\FD It reads SETUP.FD and writes to INBOUND.HIS, LASTCALL.FD and FD.LOG or their mL equivalents. ■ With InterMail... The environment setting IM should be set to point to the directory where CONFIG.FD is located, e.g.: SET IM=C:\BBS\IM It reads SETUP.FD and writes INBOUND.HIS, LASTCALL.IM and IM.LOG or their mL equivalents. ■ With a MultiLine system... >>> IMPORTANT <<< If you're running a multiline system, WHO looks at the TASK environment setting for the line. This is no standard but it's being used almost everywhere. If you use WHO with a multiline system, the filenames which are used for FrontDoor, InterMail and BGfax are changed. If you haven't set up a TASK setting or if you're using an environment setting with another name, you can pass the line number with a command line switch. Just start WHO with: WHO /TASK=[n] Lets say it is line nr. 3, you can start WHO with: WHO /TASK=3 If you've set an environment setting with another name, e.g. you've set up a LINE environment setting with the line number, you can start WHO from within a batchfile (won't work from the DOS prompt!) with: WHO /TASK=%LINE% If you want to force WHO to store all data in one mailer's history, you can add /FORCE to the command line. So if you have a dual line system where line one is the mailer and line two is the BBS, run WHO with WHO /TASK=1 /FORCE This way all the data from the second line will be logged to the mailer on the first line. Only use this in combination with the /TASK= parameter or strange things will happen. I'm not shure what exactly, but it won't be much good. If you want to default WHO to a single line system, start WHO with WHO /TASK=0 /FORCE and all the data will then be put into the normal single line history files. The command line switch overrules the TASK environment setting, even if it is invalid! ■ Other options... /LOCAL Log local calls too. Only works with the three BBS systems. Behind the name there is a Local flag so you can pick them out easily. /ALIAS Use the users alias in stead of his/her real name. Only works with Remote Access and SuperBBS. /NOLOG Don't log things to the mailer's logfile. Saves you some diskspace. (Not much though :) /NORA /NOPB /NOSBBS /NOBGFAX /NOZFAX Disable the processing of one or more systems. Especially for ProBoard sysops who have a RA environment setting. /? /HELP Display a little help screen. ■ With RemoteAccess 2.x... If RemoteAccess is installed it checks LASTCALL.BBS and compares this to the last caller in the inbound history of the mailer. The node nummer is made out of three numbers. The net number is the line, the zone number is the baudrate and the node number is the number of times the user called this system. So if the node number is: 2:14400/9 the user called in on line two at 14400 baud and it was his or her ninth call. On single line systems there is no net number. The environment setting RA should be set to point to the directory where LASTCALL.BBS is located, e.g.: SET RA=C:\BBS\RA It reads LASTCALL.BBS and CONFIG.RA. RemoteAccess 1.1x isn't supported. If you're still working with it, please, change to 2.x! All that development isn't done for nothing! ■ With ProBoard 2.x... It reads ProBoards BINLOG.PB and compares this to the last caller in the inbound history of the mailer. The node nummer is made out of two numbers. The net number is the line and the zone number is the baudrate on which the user called. So if the node number is: 1:14400/0 the user called in on line one at 14400 baud. On single line systems there is no net number. The environment setting PROBOARD should be set to point to the directory where BINLOG.PB is located, e.g.: SET PROBOARD=C:\BBS\PB It only reads BINLOG.PB. ■ With SuperBBS 1.x... It reads SuperBBS's CALLERS.BBS and compares this to the last caller in the inbound history of the mailer. The node nummer is made out of two numbers. The net number is the line and the zone number is the baudrate on which the user called. So if the node number is: 3:14400/0 the user called in on line three at 14400 baud. On single line systems there is no net number. After the user's location there are seven flags which represent the following things: D if the user downloaded something; U if the user uploaded something; R if the user read some messages; W if the user wrote some messages; P if the user paged the sysop; N if the user was a new user; Q if the user used the QWK system. The environment setting SBBS should be set to point to the directory where CALLERS.BBS is located, e.g.: SET SBBS=C:\BBS\SBBS It only reads CALLERS.BBS. ■ With BGFAX 1.x... It reads the ASCII logfile FAXIN.LOG and compares the last entry to the last entry in the mailer's history. If you use the PID feature of BGFAX, you should pass it on to WHO with the TASK variable or with the /TASK= command line switch. Now, the node nummer is made out of two numbers. The zone number is the baudrate of the call and the node number is the number of received pages. So if the node number is: 14400/3 the fax was at 14400 baud and BGFAX received three pages. The location field is the filename of the received fax file. After the filename is the status report. If the fax wasn't completely received (e.g. if there should be more pages.) it reports Not Done. Else it reports Finished. After the status report is the resolution and compression status. It can report 1D or 2D compression and HR (High Resolution) or NR (Normal resolution) faxes. If you use BGFAX 1.36, please don't use the /ED switch with it. WHO expects the USA date format (mm-dd-yy) in the logfile so if you'll change it to European date format (dd-mm-yy) WHO will mess things up. If you have a ML system with BGfax, WHO will report a fax on every task. This due to a limitation in the logging of BGfax. You can work around this to include /NOBGFAX in every node and put WHO /TASK=1 in the batchfile where the faxes are received. This way all the faxes are reported to task nr. 1. The environment setting BGFAX should be set to point to the directory where FAXIN.LOG is located, the same directory as where the faxes are received, e.g.: SET BGFAX=C:\BBS\BGFAX\INBOUND It only reads FAXIN.LOG. ■ With ZyXEL FAX 2.x... It reads the logfile ZFAX.LOG and compares the last entry to the last entry in the mailer's history. Now, the node nummer is made out of the baudrate of the call. So if the node number is: 14400/0 the fax was at 14400 baud. The system name is the received fax ID and the location is the filename in which the fax was received. Behind the filename is the result code and the compression (1D or 2D) and resolution (NR or HR) status. The environment setting ZFAX should be set to point to the directory where ZFAX.LOG is located, e.g.: SET ZFAX=C:\BBS\ZFAX It only reads ZFAX.LOG. ■ With ZyXEL FAX 3.x... It reads the logfiles ZFAXIN.LOG and ZFAXVM.LOG and compares the last entries to the last entry in the mailer's history. Now, the node nummer is made out of the baudrate of the call. So if the node number is: 14400/2 the fax was at 14400 baud and contained two pages. The system name is the received fax ID and the location is the filename in which the fax was received. Behind the filename is the result code and the compression (1D or 2D) and resolution (NR or HR) status. For the Voice Manager the resolution and compression flags won't be set and the number of pages will be zero. (Guess why :) The environment setting ZFAX should be set to point to the directory where ZFAXIN.LOG and ZFAXVM.LOG are located, e.g.: SET ZFAX=C:\BBS\ZFAX It reads ZFAXIN.LOG and ZFAXVM.LOG. ■ Why did I make it?.. I didn't want to gaze througt the logfile to see who had called my BBS, so I thought... Let's put it in the INBOUND.HIS of FrontDoor! (Not a really new idea, but what the heck.) Worked on it for maybe two or three hours, and did what I wanted at my place... After a while some people came up to me with requests for BGFAX, ZFAX and InterMail. So after a big struggle for time and peace between my final exams I created this. (BTW, I passed those exams! :) When I finished that, other requests for MultiLine systems and ProBoard were coming in. Also found the structures of SuperBBS somewhere (or better, the structures found me, thanx to Thomas Raehalme :) and put those in too. ■ What errors can be reported?.. All the errors WHO can return are self-explaining. If a fatal error occurs you will hear two beeps. When you hear only one beep, you should register :) If you find a bug, please report it to me. (How? Look at the end of this DOC) This program is very, very heavily tested, but some things just aren't showing on a small, single line humdrum system. Errors in this doc aren't very dangerous, but you can report them to me if you want to. :-) ■ Credits... The following copyrighted programs are mentioned in this file and other files supplied with this software package: (in alphabetical order) BGFAX B.J. Guillot FrontDoor Joaquim H. Homrighausen InterMail Peter Steward Portal of Power The Portal Team ProBoard Philippe Leybaert RemoteAccess Andrew Milner SuperBBS SuperBBS group ZyXEL FAX ZyXEL Communication Corp. Special thanks to the following persons for: (in alphabetical order) Tommy Arveborg Bugs JeRoen van Baarsel InterMail, Bugs, ß Jeroen Beekhof Bugs Terry Belton My bad English ;-) Marcel Jansen ZyXEL FAX 3.x, Bugs Martijn Janssen Bugs, ß Paul Kolenbrander FrontDoor, Bugs Karlo Leenhouts ProBoard, ß Peter Lindeman InterMail, Bugs, ß Terence Milbourn FrontDoor, Bugs Hans Niewenhuis Suggestions, Bugs Frank Schots Bugs Sikko Stienstra ZyXEL FAX 3.x, Bugs Thomas Raehalme Structures Richard R. Sands Sound routine Rini Schaap Portal of Power, Bugs ■ Registration... Register and support the Shareware system (and get rid of the little not-so-annoying beep :). Just send me the little amount of HFL 10 (Approx. US$ 7) to Postbank account 6492481 to Claudio Tagliola in Holland. If you'll send me your registration form I'll put your key on your board asap. Read REGISTER.DOC for more details. The unregistered version isn't crippled in any way, it only makes a little beeping sound. WHO takes note of the audio times in the mailer config, so you won't wake up in the middle of the night and delete this program in pure rage. (That would be a shame, not? :) ■ Bug reports... Ideas... Flames... Registrations... If you have found a bug, have a suggestion, are unhappy with something or just want to register this fine piece of software, contact me: ■ BBS Insanity Systems +31-85-636369 Open 25 hours a day and 8 days a week From 1k2 to 28k8 ■ Netmail 2:283/607@FidoNet 79:1100/106@HOLLANDnet 85:100/309@085net 115:3137/0@PascalNet 135:1040/102@DutchSceneConnection 202:900/101@SupportNet 206:3106/0@DisasterNetwork ■ VNSP I'm registered as a member of @VNSP under the registrationcode VNSP/941222/01/M.