The World of Computer Software/World_Of_Computer_Software-02-387-Vol-3of3.iso/c/csver222.zip/HISTORY.CSV

Text File | 1993-03-11 | 14KB | 301 lines

History of Changes or Fixes to CSVerify.
Entries are made in reverse order, Newest first;


March 11, 1993 Ver 2.22/M

■ I hate to keep changing things on you all, but I have redone the
configuration file format to be in the same format as the rest of my CS*
software. I have changed the configuration file to a KEYWORD type format, so
that I can continue to expand CSVerify without having to worry about screwing
up the configuration file. It was already starting to get out of order, with
the addition of the TimeTables and was at times confusing to some users. This
should make a little more sense.

Please refer to the configuration file enclosed in the zip for the changes.

March 9, 1993 Ver 2.21/M

■ Minor modification made to the user that gets long distance access.
Previously, the user was just sent back to the board.... now they make a stop
along the way to see their current settings.

■ I had previously changed the callback only mode to have the user enter the
phone number they wanted to be called back at, and removed reading the number
from the Users file. Carol wants the Users Record read first, then give the
caller the opportunity to change the number.... Okay Carol... you got it <G>!

■ Little by little, updating the docs... <g>

March 6, 1993 Ver 2.20/M

■ Made a minor change to the log entries. The users phone number will now be
put into the callers log, so you can view it quickly through PCBoard.

■ A couple of minor cosmetic changes were made... i.e. typo's.

March 5, 1993 Ver 2.19/M

■ Added a Callback time function. Using the matrix file included in this ZIP
called TIMETAB.CSV, place an 'x' in the appropriate column corresponding to
the day of the week, and time you would allow long distance callbacks. If the
column is blank, but you allow long distance callbacks, the user will be shown
the CALLTIME.CSV file explaining when to call back. You may modify this file
as you see fit. Double check the positions of each 'x' you place into a
column, and double check the appropriate day of the week, There is no checking
made by the program other than what you have in the matrix, so please follow
the example closely, and you wont have any trouble.

I cannot be responsible if the program dials a long distance number either by
configuration error, or incorrect placement of the time slot marks!

March 2, 1993 Ver 2.18/M

■ I noticed that some new users were getting expiration dates of 00-00-00
after callback. Checking the code I found I was grabbing the wrong data off
the line from the configuration file variable EXPIRED= .

■ Changed the options displayed to the user before call back to be a little
more specific.. They just don't get it <g>!

February 28, 1993 Ver 2.17/M

■ After the last modification, I noticed that everything was working fine,
until the user exited the door.. Seems I forgot to update the users file, so
PCBoard never saw the updated information... Fixed!

■ Inadvertantly left off the Fossil drive when I compiled the program... sorry
folks!

February 26, 1993 Ver 2.16/M

■ Minor modification that now adds the users name to the trashno.csv file on
successful verification. If a user calls, and the number they enter has been
used by someone else, and is found in the trashno.csv file, it will display
the users name that used that number. Handy for SysOps to look back also to
see who used what number.

February 22, 1993 Ver 2.15/M

■ I was in the process of adding another function to the program to check for
valid callback times on long distance, which I have not yet finished... but I
have some code in there already to check the table, which I forgot about.
Anyway, the change I made yesterday to correct the callback only mode was not
working correctly because of it... For the time being I commented out that
part of the code, until I get finished with it..

■ Added a notification that CALLBACK ONLY mode was enabled.

■ Corrected an error that was causing CSV not to properly check the security
level on entry into the door on security callbacks.

■ CSV was allowing a blank BusData phone entry on callback.. If for some
reason this field is blank when CSV starts up, you are now prompted to enter
the number manually.

February 21, 1993 Ver 2.14/M

■ Made a change to the program when in CALLBACK ONLY mode. The program will
now prompt the user for the callback number instead of getting the number from
the users record. The number must still meet the criteria for callback as
usual, but the program will now have the user enter the number instead of
assuming the users record entry.

February 4, 1993 Ver 2.13/M

■ Corrected an error on the Expiration Date routine, where if you selected
Zero (0) it would set the users expiration date to the current date. It will
now place 00-00-00 in the expiration date field of the users record if Zero is
specified.

January 20, 1993 Ver 2.12/M

■ Corrected the procedure for allowing International telephone numbers. In the
configuration file, a new keyword "INTERNATIONAL" was added to tell the
program that a different set of telephone numbers is acceptable. If you do not
use INTERNATIONAL phone numbers then just leave the line out. Maybe I got it
right this time!

January 10, 1993 Ver 2.11/M

■ Added support for International phone numbers... I dont know if I did
this right, so i'll count on you International SysOps to help me with
that.

January 7, 1993 Ver 2.10/M

■ Added an option in the configuration to allow you to specify the
expiration period of the user. You can leave it blank, or you can
specify any number of days. The default is 365 days (1 year). Putting
730 would equal 2 years and so on.

■ CSV can now be used for CALLBACKS only. If you have a subscription
service that uses callback security, you set the logon security to this
level. When the user logs on, he is immediately taken to CSV, where the
callback phone number is verified. The program will then disconnect the
user, and call him back. After correct password entry, the user is
returned to PCBoard. See the revised DOCS for using this feature.

December 16, 1992 Ver 2.9

■ Corrected a couple of minor details that were being displayed on the
screen.

■ Added support for Fossil Drivers, to maintain compatibility with the
new PCboard 14.5a/M version.

November 12, 1992 Ver 2.8

■ In the interest of protecting the SysOp from doing callbacks that were
long distance that were not mean to be, I tried to use too much logic in
identify a long distance user. I reworked a section of code to make it
much simpler. If you do not allow long distance callbacks, you need to
make sure that the areacode and exchanges for the calling area are
correct in your file. If the program does not find a match from what the
caller enters, the program will flag the caller as long distance, no
matter what he answers to the prompt.

It's as simple as this;   If you allow long distance callbacks, set the
parameter in your configuration file, along with the other options for
logging off the user after callback (if desired), and the program will
call the user back. If you say NOTALLOW LD, and the users areacode and
exchange are not in the list, it will consider it long distance, and
deal with it as you have configured. This step shortened the code size,
and makes a lot more sense in program flow.

■ To fall in line with the other doors and the new PCBOARD node numbers
then $$$DUMMY.$$x filename is now $$$DUMMY.node , node being what ever
node created the file. It would look like this;

$$$DUMMY.10   for a file created by node 10.

November 9, 1992 Ver 2.7

■ A slip of the fingers caused this one! In checking a variable to see
if the program was in LOCAL mode, I forgot an equals sign, which caused
the program to switch to local mode, even if it was not really. This
effected the caller, in that once the program switched to local mode,
the caller no longer saw anything sent to the screen. Fixed... Sorry!

November 7, 1992 Ver 2.6

■ A user reported that the program was having trouble opening the
various data files described in configuration file. Turns out that I
specified a length of only 29 characters for each file and pathname for
the trashno.csv file, exchanges.csv etc, and for some that was not
nearly long enough. I increased the length to 40 characters, which
should hopefully clear that problem.

November 2, 1992 Ver 2.5

■ A couple of other minor bugs were reported;
1) - Incorrect number was being placed into the TRASHNO.CSV file if the
user modified it after registration... Fixed!

2) - After a user was updated, and the information screen was displayed,
the incorrect security level and time was being show... Fixed!

3) - The program will sense LOCAL operation now, so if you want to test
the door to see what it does to a record, you can do so. Just a
reminder, if you call the program and pass it a parameter of TEST it
will go through the verification process, but not write any records.

4) - Some cosmetic clean up.

5) - Corrected an error that would cause the areacode to be dialed on a
     local number if you were calling out through a PBX system...Fixed!

October 26, 1992 Ver 2.4 **** Change to Configuration File ****

■ Correct a problem that caused every number entered by a user to be
invalid. I was using the wrong variables to see if the areacode or
exchange was a 911, 411, 800, etc. Fixed...

■ Corrected the problem (I think!) with the program not starting the
dialing string with a 1 if the callback was long distance. The program
should now place a 1 and the areacode into the dialing string on all
long distance calls.

■ For users of local metered systems, I added a new line to the
configuration file where you can put the word "METERED". If this is
encountered, as soon as the user has been called back and verified, the
program will display a new file called hangup.csv (which should contain
an explanation on why they have to call the board back), then
disconnect the user. This file will also be displayed if the user is
being called back long distance since they are related.

Pay attention to the changes made in the configuration file so your
program will run properly.

October 19, 1992 Ver 2.3

■ Corrected a bug that was not allowing the program to properly dial
long distance numbers. The program was not getting a switch turned on on
certain cases that would tell it to add the dialing prefix as defined in
your csverify.cnf file. The dialing prefix would include the needed 1
for dialing long distance. On my system I do not have a long distance
carrier assigned to my line, so I can use any carrier by including the
10288 as an example to use AT&T then appending a 1 to that to complete
the dialing prefix. Your dialing string would look something like this;

ATE0M1DT10288-1(555)555-1212.

■ Hardcoded some checks to be sure that some idiot hacker doesn't send
your program dial strings for dialing 900, 800, 911, 411. I put that in
as hardcode for the time being till I think about how the sysOp can have
control over this.... It will check this information just before dialing
and kick them off if the areacode or exchange contains any of these
numbers.

September 8, 1992 Ver 2.2a **** Change to Configuration File ****

■ Made a minor modification to the program to allow the SysOp to
override the newuser security level found in pcboard.dat. This value was
being used by CSVERIFY to determine if a users security level was too
high to use the door. In the configuration file, add line 19, and
SECURITY=## (whatever security level you choose) to override it, or
PCBSECURITY to use the value in pcboard.dat. This allows you to use
other doors to gradually upgrade a user through other doors before the
actual callback verification.

August 15, 1992 Ver 2.2

■ Corrected an logic error which did not take into account incorrectly
entered phone numbers. The program will now look at the phone number
entered, and try to divide it into 3 parts (Areacode, Exchange, and
Number) when the user first enters the door. If unable to split the
number properly, it will then take the user to a screen to enter each
portion of the number separately for proper operation. Since you have
the option of controlling the callback area, the number entered has to
be parsed into its separate sections to be checked.

■ Added a note to the user that the number entered will be the number
called back, so they have an opportunity to change it before the program
does the callback.

August 12, 1992 Ver 2.1

■ Corrected an error which did not write the number to the trash can
file upon successful verification.

■ Working on a parsing routine for the phone numbers to separate them
into area code, exchange, and number when a user enters the phone number
all together without spaces or dashes. Encourage your users to enter the
phone number properly during registration, perhaps displaying a guide
for them by modifying the prompt in PCBTEXT like this;

Business/Data Number XXX XXX-XXXX (800 555-1212)

July 27, 1992 Ver 2.0 *** Major Rewrite ***

■ Version 2 in beta testing... completely rewritten in Turbo C++ 3.0 using
the new PCBoard Door Toolkit from Clark Development.

Setup is not much different than the previous versions. The Phones.dat
file is not longer required, and the config file has changed. Please
refer to the sample config file included in the ZIP for changes.

Please report any problems or suggestions to me on my board. These beta
versions are not for distribution... please do not post them... I will
release the program as FREEWARE as soon as the testing is completed.