home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
PCBOARD
/
CSV256.ZIP
/
HISTORY.CSV
< prev
next >
Wrap
Text File
|
1994-01-07
|
19KB
|
418 lines
History of Changes or Fixes to CSVerify.
Entries are made in reverse order, Newest first;
NOTE: Once you receive your REGISTRATION key, Place the
Information at the TOP of your configuration file.
CSV will not go outside of the configuration file to find it.
January 7, 1994 Ver 2.56
■ If you ever want to know how screwed up the phone companies are, just
write a call back program....
I made a change to the code to accomodate SysOps who have multiple area
codes in there state with local access to those OTHER area codes.
Problem;
A BBS is in the 904 area code, and the caller is in the 813 area
code. Even though the caller is in the 813 area code, the exchange he is
calling from is a local call for the BBS.
When CSV tries to call the user back, since the number is in a different
area code, it assumes that it needs to dial the number using the
traditional 1+areacode+exchange+number, which will not work....
Solution;
In the areacode.csv file, list the areacodes that are local to YOU. In the
exchange.csv file, list the exchanges that are considered local to you from
those areacodes.
If there are exchanges in different area codes that are local, but require
you to dial the areacode with the phone number, then you need to place an
asteric "*" directly behind the exchange in the exchange.csv file.
The effect is this; When CSV set's up the dialing string, if the exchange
has an asteric next to it, CSV will automatically include the areacode as
part of the dialing string. It will not include a "1" though... If that is
to be included, then you must remove the exchange from your exchange.csv
file so CSV knows that it is a long distance call..
==================================================================================
January 4, 1994 Ver 2.55
■ I made some minor modifications to the routines that open the files that are
used by CSV.
****** -=> IMPORTANT NOTE FOR MULTI-NODE USERS : <=- *****
Even though the files used by the program are openned in SHARED mode, you must
remember to FLAG your TRASHNO.CSV file as READ|WRITE|SHARE on any network disk
in order to have this file properly updated.
=============================================================================
January 3, 1994 Ver 2.54
■ I haven't updated the code for a while, but I noticed that there is a
problem when using CSV after PCBoard has standardized the phone numbers of
the users record. The program was not tokenizing the phone number correctly
because of the leading space that PCB was inserting.
=============================================================================
October 30, 1993 Ver 2.53
■ By request, added checking for area code "000". CSV was still attempting to
dial this areacode, which would of course get the operator on the line...
sorry about that! If the user enters 000 as an area code and confirms that
the number is correct, the caller will be rudely dumped off the system with
the auto twit!
=============================================================================
October 7, 1993 Ver 2.52
■ In the never ending battle to write to the trashno.csv file, I am trying
different functions to track down the problem. This is another shot at it!
=============================================================================
September 21, 1993 Ver 2.51
■ Minor update - CSV was displaying the wrong file to users who were calling
long distance, and got verified when LOGOFF was set to YES. It was supposed
to be displaying the HANGUP.CSV file, but was showing the LONGDIST.CSV file
instead. Fixed!
=============================================================================
September 18, 1993 Ver 2.50
■ Corrected an error that was not extending the users long distance
expiration date to the proper length if you did not allow long distance call
backs.
=============================================================================
September 18, 1993 Ver 2.49
■ Added a new function to the program that allows you to restrict the program
from calling specific area codes or exchanges. This was done to accomodate
users that allow verification of long distance callers, but do not want to
make interstate long distance calls because of the higher rates.
To use this function, simply put the areacode(s) you wish to have restricted
into the areacode.csv file, and put a minus sign after the number like so;
904-
The minus sign after the number tells CSV not to call this user back because
it is a restricted area.
With this capability there are two new variables in the configuration file.
1) RESTRICTED_LEVEL=## - Put the security level here that you wish to give a
user that enters a restricted phone number.
2) RESTRICTFILE=drive:\path\filename - This is the file that is displayed to
the user explaining why they are not being verified. If this variable is
blank or does not exist the program will display a brief internal message
telling them what is happening.
If you choose not to use this new function, then just leave everything as is,
and the program will operate as it always has. The key to this function is
the hyphen after the number.
The above also holds true for the EXCHANGE.CSV file. This allows you to
accept certain areacodes, but reject certain exchanges and continuing
allowing callbacks to long distance users.
=============================================================================
September 13, 1993 Ver 2.48.4
■ Extended the length of the path names from 40 bytes long to 80 bytes long
in case they were being truncated.
■ Changed a couple more compiler options in this effort to figure out why it
wont write to the trash file.
Once you get this program, log on as a local NEW user and test the program
out. It should go through all the motions just as if the caller were on the
modem, except that it wont dial the phone.. Check the callers log, and check
the trash file to be sure the persons number was written to it when
completed.
■ Made a modification to the CVTPCBVR program that converts PCBVerify files
to the CSVerify format, and fixed an error that would give a "FILE NOT OPEN
FOR OUTPUT" error if the file you were converting to did not exist.
■ Changed CSVPURGE to show the number of purged records on the screen as well
as the number of records copied.
=============================================================================
September 11, 1993 Ver 2.48.3
■ CSV was displaying the wrong file when the user was calling long distance.
For some reason, I was showing the one for METERED Line service instead of
the longdist.csv file. Fixed...
■ Still trying to track down this nasty bug that is causing the program not
to write to the trash file on some systems. In an effort to track the problem
I have tried everything that I can think of on my end except changing the
compiler settings. I previously has the code compiled to the 386 processor
set with some optimizations turned on in the compiler. I have reverted back
to the 286 compiler settings and turned off the compiler optimizations to see
if this has any effect. Please let me know right away if theres a problem.
=============================================================================
September 9, 1993 Ver 2.48.2
■ Corrected an error that was causing an END OF FILE marker to be written to
the trash file before that data was written to the file. This would cause the
program to read only up to that point in the file, and when writing, the
program would only position itself at the point where the EOF marker was
located, seemingly just overwriting what was there previously.
All users need to check thier trashno.csv files for evidence of this EOF
marker sitting in front of an entry in the file. It should look like this
"", without the quotes, and should not be in front of any entries.
■ Corrected an error that would upgrade a user, then go right back to the
board without displaying the profile.
=============================================================================
September 7, 1993 Ver 2.48.1
■ Were back to the small step versions again. Finally, someone spoke up, and
told me that the trash file was not being updated properly.
■ I added some logging to the callers file if the program has trouble
openning the trashfile, or writing to it. I also changed the logic in calling
the addtrash() function to see if that helps!
■ There is a new file that you can download, instead of downloading the
entire program everytime theres an update. Download the file CSVPATCH.EXE,
which is an executable file that should be placed into your CSV directory,
and when run, will update your files with the current versions of the files.
=============================================================================
September 6, 1993 Ver 2.48
■ Some users brought to my attention that my wires were crossed, and the
program was logging off users after reconnect even if they were local
callers. Yup... I goofed! This was fixed.
■ I changed the routine that writes to the trash file, to standard C I/O
operations instead of using the toolkit to see if that makes any difference.
I did notice that there were times when an incorrect character was making an
END OF FILE MARKER, then writing the number after it. What happens is that
when the program next tries to read the file, it will only read up to that
point.
=============================================================================
September 4, 1993 Ver 2.47
■ I haven't heard from anyone about the program not writting to the TRASH
file, so I am assuming that the program is now working properly.
■ Added a new program to the ZIP file called CSVPURGE.EXE. This program will
purge your TRASHNO.CSV file of any users that no longer are listed in your
PCBoard Users file. To operate correctly, you must have your environment
variables set and pointing to the PCBoard.dat file where ever it might be.
The program will not modify the trashfile directly... instead, it will create
a new file called TRASHNO.NEW. After you inspect this file, you can then
delete the TRASHNO.CSV file, and rename TRASHNO.NEW to TRASHNO.CSV.
Happy now Butch! <g>
=============================================================================
September 3, 1993 Ver 2.46.5
■ Corrected an error that was causing the program to improperly check the
necessary files when the user was using the CALLBACK feature, or being
REVERIFIED. Essentially, the program was not checking the number under those
two conditions, and therefore tried dialing them as local calls, even if they
were actual long distance numbers.
=============================================================================
August 31, 1993 Ver 2.46.4
■ I am not sure why it took so long to pop up, but I corrected an error that
was causing the program the pass the phone number incorrectly to the modem on
local calls when you had allow_ld=yes, and PBX=xx. The program was also
inserting the area code on the local call, which would be invalid to the
phone company of course.
=============================================================================
August 29, 1993 Ver 2.46.3
■ Still trying to track down a bug that is not consistantly checking the
trash file, and writing the used number to the trash file. Until this is
corrected, the program will use the above style version numbering.
■ Corrected an error that was not displaying the logoff file if you were a
local call and had metered set to yes, or on long distance calls where
metered and logoff were set to yes.
■ Program was not correctly checking for the security level when entering the
door. Now the program can tell if the user's account is expired, and will
allow reverification, even with his number in the trash file, then the
program will reset his/her expiration date to whatever value you specified.
After this occurs, and his/her security level has been raised, they will not
be allowed in the door again, unless the expiration ocurrs again.
=============================================================================
August 28, 1993 Ver 2.46.2
■ Apparently, while I was changing the function calls for reading and writing
to/from the trashfile, I defined the function incorrectly, which was causing
the program never to open the file for the read, and subsequent writing of
the persons information... With the file never getting openned up to search
for a name, you would not get a hit if the person was already in the trash
file. I think this is now working properly.... I need to hear from you if it
is not...
=============================================================================
August 26, 1993 Ver 2.46.1
■ Added a Yes/No Prompt to the WELCOME screen, to allow the user to abort
the program without having to go all the way through the program. This will
write a message to the caller log that the caller aborted the program at the
welcome screen. This uses PCBoards Multi-Language support characters in what
ever the current language is that's in use.
■ Found I was incorrectly calling the checktrash and addtrash routines, which
*MAY* have been causing a problem on some systems... we shall see!
■ I learned that I was linking the FOSSIL driver in the wrong place, and it
was not taking effect after the compile... Fixed!
■ When the program initially drops carrier to call the user back, the program
will now attempt to poll the modem buffer for the words "NO CARRIER". If it
finds that string, it will begin the dialback, otherwise it will wait for 60
seconds before proceeding to give slower modems a chance to drop the carrier.
=============================================================================
August 22, 1993 Ver 2.46
■ Corrected an error that was preventing the display of error messages when
trying to write the used phone number to the trashno.csv file.
=============================================================================
August 18, 1993 Ver 2.45
■ Corrected a logic error that was causing the Callers phone number not to be
written to the trash file. It was not consistent for some reason, but it
finally happened to me, and I was able to locate the problem.
=============================================================================
August 14, 1993 Ver 2.44
■ Inadvertantly left out a line in the code that was checking for network
installation... If the PCBOARD.DAT file was set to No Network, the program
would give an error that it could not run on multi-node BBS'es.
=============================================================================
August 9, 1993 Ver 2.43
■ The Single node version was restricted to using only NODE 1, and I had a
couple of people tell me that they would like to use the program on a node
other than node 1. There is a new variable in the config file called PCBNODE.
Set this variable to the node you would like the program to run on, and you'll
be able to use the program on that node only.
■ Updated the documentation to be a bit clearer in setup. Thanks goes to Jeff
Grant of MegaSystem BBS for the assist.
BTW: It would not hurt my feelings if someone decided to work my docs over a
bit... I told you I am terrible at writing them <g>!
=============================================================================
August 7, 1993 Ver 2.42
■ Added a program to convert the trash file created from PCBVerify to the
CSVerify format. This program should be used before starting to use CSV.
To operate the program, type - "cvtpcbvr pcbvver trashno.csv", and the program
will convert the file. You can also give the second parameter a different
filename, and append it to an already existing trashno.csv file after
conversion like this Example;
cvtpcbvr pcbvver trashno.tmp
copy trashno.csv+trashno.tmp
This will cause the program to append the trashno.tmp file to the end of the
trashno.csv file, joining them together.
■ If a user was prompted by CSV to enter his phone number because it was not
entered properly during registration, CSV would allow them to not enter a
complete phone number, then it would try to dial whatever part they did enter.
This has been corrected. Now if the user only enters a partial number, then
answers that the number is correct, the program will disconnect them.
■ Added another variable to the configfile. If you have concerns about showing
a user that a phone number has already been used, and by whom, you can now set
the variable DISPLAY_NAME=NO, and the program will only display the phone
number, otherwise it will show the phone number used, the person that used it,
and the date & time.
■ Was finally able to track down a pesky bug that would not recycle the
dialing attempts if the users phone was busy on callback. Now, if the users
number is busy when called back, the program will pause 10 seconds, then
attempt to redial if they are not beyond the Sysop configured redial attempts.
■ The program will now wait five seconds after dropping carrier, to give slow
modems a chance to report "NO CARRIER" before beginning to call the user back.
=============================================================================
August 1, 1993 Ver 2.41
■ Corrected an error which was causing the Bus/Data number to be written to
the users record even if you said no.
■ Corrected an error that was causing the program not to properly check the
trash file for used phone numbers.
Note: Your Trashfile should have at least one phone number in it before you
use it.... namely your BBS number, or the program will not operate properly
when checking the trash file.
■ Added support for international characters in the prompts.
=============================================================================
June 25, 1993 Ver 2.40
■ Internal changes and recompilation with BC 3.1 to improve performance.
=================================================================================
Versions No Longer supported!
April 30, 1993 Ver 2.39
April 28, 1993 Ver 2.38
April 26, 1993 Ver 2.37
April 17, 1993 Ver 2.36
April 11, 1993 Ver 2.35
April 3, 1993 Ver 2.34 21:00
April 3, 1993 Ver 2.33 Internal Beta
April 1, 1993 Ver 2.32
March 31, 1993 Ver 2.31
March 30, 1993 Ver 2.30/M
March 25, 1993 Ver 2.29/M (* Major Changes!!! *)
March 23, 1993 Ver 2.28/M
March 19, 1993 Ver 2.27/M
March 17, 1993 Ver 2.25/M
March 16, 1993 Ver 2.24/M
March 15, 1993 Ver 2.23/M
March 11, 1993 Ver 2.22/M
March 9, 1993 Ver 2.21/M
March 6, 1993 Ver 2.20/M
March 5, 1993 Ver 2.19/M
March 2, 1993 Ver 2.18/M
February 28, 1993 Ver 2.17/M
February 26, 1993 Ver 2.16/M
February 22, 1993 Ver 2.15/M
February 21, 1993 Ver 2.14/M
February 4, 1993 Ver 2.13/M
January 20, 1993 Ver 2.12/M
January 10, 1993 Ver 2.11/M
January 7, 1993 Ver 2.10/M
July 27, 1992 Ver 2.0 *** Major Rewrite ***