***
3.72
***
FINALLY!  Figured out the LINE25 problem!  Now the SysOp screens are
AWESOME!

Added a new file called TESTTIME.  Same configuration as the others.
This screen is shown to the user once they have been re-connected to the
BBS.  Changed a few little things.

        Anyone running this in OS/2 yet?  Does it give up the time
slices properly?  It does in DV I have no idea about 'the doze' or OS/2.


***
3.69
***
Re-did the SysOp's display.  More informative as to what's going on with
the modem and such.  Modified how I watch a carrier a little bit.  Give
the modem a second chance to make sure carrier is dropped before
reporting it.  Some modems don't seem keep carrier high all the darn
time, so I pause 1 second before verifying that carrier is indeed
dropped!

***
3.60
***
Now I've REALLY done it!  Added support for other BBS's besides RBBS!  I
now write out a DOOR.SYS if a BBS.Type=2 is indicated in the x.SWI file.
Also, BETA testing WildCat! 3.0 stuff as well!  Changed the screens a
little.  Just minor clean up.

***
3.53
***
Some more enhancements.  MYCALBK will now remind the user what to type
when the phone rings, instead of just clearing the screen.

Added a WHOLE bunch of options in the .SWI file for you!  To control how
MYCALBK handles certain situations that I normally consider failures.

***
3.49
***
Now, we are ever closer to the BEST release ever!

Changed the logic of the program slightly.  MYCALBK will not search for
names in the begining UNLESS /DIALBACK is used.  It is a rather lengthy
process but in order to leave VERIFIED.LOG alone so you can edit it with
a text editor, it HAS to be done.  If I make it random access and HASH
the user name, it will speed things up imensly, however, I would also have
to write an editor for you! :( :( :(

Changed the prompts a little bit when the user is verified or when they
are dialed back.  If I have any input on if they need to be different,
my netmail address is on the REGISTER.FRM file or in the docs!

Changed some of the logging procedures...  I now tell you what security
the user entered with and what security number you are passing to RBBS.
***Please note
 What RBBS does with this number is up to RBBS.  It appears that if your
user has a negative security and you pass a positive number to RBBS,
RBBS ADDS this number to the security.  If, I am a level -7 and I pass
14 to RBBS I now become a 7!  If I am a 5 and I pass 20 to RBBS, I am
now a 20!  Go figger!

Still have no code to detect (much less give up time slices) for 'the
doze' and OS/2.  If anyone would like to contribute to this cause,
please do so.  I need what Interrupt and what Registers to use, etc...

Took out some of the LINE25 display code as it was mainly debugging code
for me anyways.  Made a noticable difference in speed!

It now looks like this...
Node 4  5003.61 178               5000 STEVE STEVENS DARLINGTON,SC
^^^^^^  ^^^^^^^ ^^^               ^^^^ ^^^^^^^^^^^^^ ^^^^^^^^^^^^^
 |       |       |                 |         |          |
 |       |       |                 |         |          ---- Address
 |       |       |                 |         --------------- User Name
 |       |       |                 ------------------------- Security Level
 |       |       ------------------------------------------- Sleep Timer
 |       --------------------------------------------------- Time Remaining
 ----------------------------------------------------------- Node #


***
3.42
***
Fixed a bug that could have caused a problem at the midnight rollover.

        I now have the /DIALBACK command line switch!

How this works...
        There are situations where a your BBS is long distance to a
        caller but they are a local call to you.  So... Tell them about
        the REDIAL door!  They enter the door, the door hangs up, then
        calls them back. Viola!  They now enjoy your BBS without being a
        long distance call to them.  And it's a local call for you so...
        no LD charges for either party! (It will NOT call a caller that
        is LD to you!)


***
3.34
***
Upgraded to POWER BASIC 3.0!

.EXE's are now smaller & faster!

Now detects DV and if it's there, will give up time slices while
delaying or waiting for keyboard input.  Seemed to make the program a
bit "snappier" as well.

Checks parallel port to see if it can print and doesn't if it can't!

MYCALBK now uses ###.SWI files instead of those gangly command line
switches.  You MUST supply a node # on the command line but that is it!

All normal comm routines have been re-written.  Now supports,
COM1 - COM4, 0 - 115000 BAUD, IRQ2-15 (See .SWI file).


***
2.23
***
Fixed the bug introduced when I fixed the drop carrier bug!  This one
now properly logs the call and does not report dropped carrier when
there isn't one!

***
2.17
***
Finally!  Fixed a bug when a user drops carrier while a screen is being
displayed.  Was in a tight WHILE WEND loop and NOT checking carrier
inside the loop.  If there are any more suggestions, please let me know.

***
2.14
****
        Fixed bug in time calculations where it would not call out
from 11:30PM until 12:05AM (Must have been one of those nights I guess).

Added more responses in the log file.

Re-did the Dropped Carrier routine.  Now when carrier is dropped, the
door no longer tries to write DROPPED CARRIER to the modem!

        Added a line explaining how to type your name back in when the
door asks you. Some people either forgot what thier name was or
are using control characters when they type thier name back in or
something.  I cannot figure out what these people were doing!


***
2.13
***
        Added on ON ERROR routine to record the errors to the LOG file.
Now it will be easier to determine the kind of errors it is picking up!

***
2.12
***
More smoothness and program flow from my point of view.  Probably fixed
a couple of things by straightening out some logic in the code.

***
2.06
***

Added a feature where if a user has already been verified, and they
enter the door again (some people want to see it work), it will NOT call
them back again.  Also, for some reason if thier security was dropped
low enough for RBBS to send them thru (the door) again, it will upgrade them
without calling.

Two things must happen for this...
        1).  Thier name is the same. Exactly the same.
        2).  They have to enter thier phone number again.  It MUST
             match!

If a user drops carrier, it resets thier security to that of a failed
callback attempt (hopefully you've got it where they'll go thru and try
being called again).

Changed the order in which the DATE & TIME are listed in the
VERIFIED.LOG

Put LOCAL or LONG DISTANCE after DATE & TIME in VERIFIED.LOG to let you
know if it (the door) dialed LD or local.

***
2.05
***

Fixed a nasty little double spacing bug that totally screwed up the
display for the SysOp and the user!

***
2.03
***

Put time remaing for door and time remaing between key strokes on LINE 25.

***
2.02
***

In setting up the /RETRIES= switch, I did not put a default number of
retries so the door NEVER called!

***
2.01
***

Minor BUG in new routines!  Would NOT send a CR/LF to user if they did not
select color.  My version of RBBS selects color at startup and does not
ask the user if they want it or not (even for a new user!), so I never
saw that!

Added command line switch /RETRIES=  to let you set the number of times
MYCALBK calls out (In case you have alot of incoming calls, etc...)

Fixed where a user with 0000 as the last four wouldn't be able to be
called back.  I now check each number to make sure they do not enter a
letter by mistake (or on purpose).

I may need to write a new switch /WIERDRBBS if more reports of a problem
appear.  It seems some versions of RBBS read the DOUTx.DEF file and ADD
the number there to the users' existing security, whereas my version of
RBBS sets thier security to that number.
I.E.  If your user enters the door at a -7 security and you tell MYCALBK
to set thier security to 14 if they are validated and RBBS sets thier
security to 7, that means that RBBS is ADDING that number instead of
changing it directly.  OR say my security is 5000 and if I fail I want a
security of 20, if your version of RBBS sets my security to 5020 then
RBBS is adding the DOUTx.DEF value instead of changing the security to
20.

A simple workaround is this...

5,15,-2

If they enter as a 5 and get validated, ADD 15 to thier security to give
them a 20 OR subtract 2 to give them a 3 of they fail.  I hope this
clears this up.

***
2.00
***
        The major thing new in this version is it's FASTER!  I have
re-written some of the display routines in preperation for a rather
large door project I will be developing towards the end of this year.  I
mainly wanted to make the displays faster and still experimenting with
calling interrupts from BASIC.  I will release another version at the
end of the summer with a much better error handling facility.  Other
than that, I have received a good response (12 or so registrations) from
this program and will continue to support it as long as there is interest
in it.

Steve Stevens
The Neutral Zone
(803)-395-6286
8:927/2

