home *** CD-ROM | disk | FTP | other *** search
- Version 3.2
-
- - Added some more utils.
- WhosOn UserOn alike utility for dos
- UOFix Fix damaged records in the useron.bbs
- - Some internal changes
-
- Version 3.1
-
- - UserOn was still looking in the RA directory (System dir) for SYSDOES
- files.. Should be the SemDir, like the USERDOES files...
-
- - Removed the extra spaces between the <*> and the username if he had the
- quietflag set... Though I already removed thatone.. Oh well..
-
- - Added some utils:
- Wipe110 Builds a clean UserOn.bbs
- MakeDoes To make SysDoes and UserDoes files from within batch files.
-
- Version 3.0
-
- - RELEASE
-
- Version 3.0b2
-
- - Some little internal changes
- - Added the -AKA parameter. When used, useron show's the handle instead
- of the name.
- - Hidden users are no longer shown.
-
- - If you use a seperate semafore directory, useron probably can't find
- the userdoes files of older doors anymore.. Sorry..
-
- Version 3.0B1
-
- - The multilanguage version off useron! See the *.DEF files in the
- USONLANG.ZIP file for details..
-
- - Prepared useron for RA 1.10
-
- - Removed a bug which ruined the memory sometimes when a user aborted a
- message.
-
- - UserOn now uses the SEMAFORE direcory for its UserDoes and message
- files!!
-
-
- Version 2.6
-
- * Fixed a bug which did hang the BBS if a user dropped the carrier while
- writing an online message.
-
- * Renamed the [S]ave option in the editor to [S]end
- (and in the dutch version from [B]ewaar to [Z]end
-
- Version 2.5
-
- Changed 2 things:
-
- * UserOn now checkes for online mail again.. It didn't do that in the 2.4
- update.
-
- * It's also possible to make SYSDOES.<NodeNr> files now. they work the same
- way as the USERDOES.<NodeNr>, but they are only checked for when there's
- no user online on a node. You can use it to tell the other lines
- that a line is maintaining the system, you are playing games on that
- node, and.. If you're not using the shell to mailer option, you can
- make a SYSDOES to tell the world when a user is logging in, just put
- a copy command (see above) in the fall through part of the batchfile.
-
- Oh well, just a gadget..;-)
-
- Version 2.4b2
-
- * Argh.. Lot's of problems with memory managment.. Somehow it would go right
- producing exeption #13's here etc. So I kicked all the heap stuff out!
-
- * Made a dutch version
- * Shuffeled the lines in the useron.dat once again
- * Added a line which is shown when a user is writing a message to an
- other line. f.e. Two users are looking in useron, one is writing a
- message to the other, the line of the writer shows:
- Is typing a message to <Name of addressee>
-
- * Removed some little bugs and cleaned the code a little.
-
- Version 2.4b1
-
- - Rewrote the useron door from scratch. The code was messed up and it seemed
- like a nice occasion for some cleaning up.
- - Used the new RAdoor 3.0 (not released yet, the docu's.....)
- This means: More sysop control and a lot of structural changes
- It also means a new editor. I didn't implement the EDIT and DELETE
- lines as I did implement those though.. Anyhow, I'm not sure, but
- I think they are seldom used in this door anyhow.
- - Added an extra line to the useron.dat
-
- - A nice new feature for curiose people.. As long as the door waits for
- userinput (and is showing the Usersonline info) the screen is updated
- every 10 second... You can realy see what the users on the other line
- are doing now..;)
-
-
- Version 2.3
-
- - Reduced the minimal time needed to enter the door to 1 minute..
- - Added the file UserOn.Dat. You can define your own messages now!
- See the demofile for details. The file UserOn.Dat is expected in
- the same directory as the UserOn.Exe. As usual with my door though
- you can overrule this with the environment variable USERON. Just put
- SET USERON=<Path to datfile> in your autoexec and it will be found.
- This is ONLY needed when the file isn't in the same directory as the
- UserOn.exe main program!!
-
- ==============================================================================
-
- Version 2.1 & 2.2
-
- - Got rit of some typo's
- - Removed a bug that showed QUIET on lines where noone was on..
- - Removed a little bug which did put the Press enter line directly after
- an errormsg..
-
- ==============================================================================
- Version 2.0
-
- Added the option to send an online message too.. This isn't my way of
- providing a real multiline chatter, but it makes things more decent as
- the user get's only one UserOn list. Further I provided an editor to
- write longer on-line messages.. (up to 20 lines) which can be edited.
- As simple line-editor (but it looks great ansi/avatar too...;-)
-
- If you want to give the users the possibility to send online messages
- add the parameter -LINES:<NoLines> to the commandline.
- If NoLines is 0, NO messages van be send (same as not putting the parameter
- on the commandline) if NoLines is greater than 20 the maximal msglength of
- 20 lines can be used.. Every number in between puts a maximum on the msglength.
- If here's already a NODE??.RA found, the text is appended.
-
- ==============================================================================
- Version 1.2
-
- Found that useron didn't work ok under DV. Found a bug in one of my libraries,
- and the problem is solved.
-
- Also added a SysOp override, as I don't want to show up in the 'Users today'
- list. (Certainly not while testing..) But have no problems with users seeing
- me online.. Just add a -SYSOP:ON to the commandline and you're on the list
- whatever the 'ExcludeSysopFromList' field is saying..
-
- ==============================================================================
- Version 1.1
-
- Removed the LiveSystems commercial on top of the screen and tried to make it
- look as much as possible as the RA UsersOn command..
- Also fiddled around with the colors a little..
-