RenegadeBBS.net: News

Changes Since Last Release ...

1. New RENEMAIL in testing.

2. Close Mail Box/Mail Forwarding -

A. Both of these procedures have been cleaned up with
slight verbage changes and a reduction of variables
required.

B. A user with access to the User Editor can no longer
setup a user with mail forwarding back to the same
user.

C. Mail can no longer be forwarded to a locked out user.

3. Private Message Read -

A. This procedure has been cleaned up with slight verbage
changes and a reduction of variables required.

B. The Message Listing will now display one screen at a
time vice scrolling to the prompt. Entering a "?"
will redisplay the message listing starting at the
first message. Pressing will display the
next screen of messages and or start back at the
first message. A valid message number must be entered
in order to exit to read the message.

4. Lightbar support added to File and Message Area Listings.

5. Removed "Ram Drive/MultiNode Path" from system config. This
option is where the "TEXT" file path will be for looking
for all language files. The default will be \BBSDIR\TEXT.

If your multinode path was not set to \BBSDIR\DATA then you
must move these files to that directory.

An updated RGSCFG.TXT file with the new option will be
released as well, or you can edit it yourself and recompile
the strings.

An update program will more than likely be made to make the
change quick and simple.

6. Quite a few more strings added. Added a few more MCI
codes for the new strings.

%A1 - LowFileArea
%A2 - HighFileArea
%A3 - LowMsgArea
%A4 - HighMsgArea
%FS - File New Scan On/Off
%MS - Message New Scan On/Off
%FP - User File Points

7. Batch Uploads:

1. Duplicate files can no longer be added to the batch upload queue.

2. The number of files that can be added to the batch upload queue
is now limited by the "Max Batch Uploads" setting in the System
Configuration.

3. You will now see SysOp Log entries when a user adds, removes,
clears or lists the batch upload queue.

4. Changed batch upload listing header/footers from '-' to '=' to
match header/footers in other listings.

5. The minimum/maximum batch uploads can now be between 1-255.

6. You can now force a user to batch upload all files in the
batch upload queue. This is controlled by the System Configuration
setting "Force batch uploads at login".

Now, this system has been revamped so that all files added to the
batch upload queue are stored in the external file "BATCHUL.DAT"
and "BATCHUL.EXT". These files are updated by adding, removing,
clearing or uploading batch queued files.

8. Batch Downloads:

1. The minimum/maximum batch downloads can now be between 1-255.

2. You will now see SysOp Log entries when a user lists the
batch download queue.

3. Removed a section of code that would reaccess the *.DIR file to
obtain the file information to a add a file to the batch download
queue. The file information is now passed from the download
command. Of course, numerous variables were no longer required
and were removed.

4. Removed a section of code that would reaccess the file to be
downloaded to obtain the filesize of the file for a ratio check.
The filesize is now passed from the download command. Of course,
numerous variables were no longer required and were removed.

5. Previously, files were added to the batch download queue and were
stored in memory and in the external file "BATCHDL.DAT".

9. File Points:

1. The file credit/debit system has now been changed to a standalone
file point system. As a result, a new variable was added to the
user record for awarding/removing file points. No internal change
was made to how these file points are awarded or removed. Initial
file points can be awarded thru the New User Configuration and/or
the Validation Editor. Some minor verbage changes were made
thru-out the code to accomodate this change.

10. Light Bar Support:

1. You can now toggle lightbar support on or off in the System
Configuration for the file area with the option "Use file
area lightbar" or for the message area with the option "Use
message area light bar".

2. Menu commands were also added to allow the user to toggle file or
message lightbar support on or off (Assuming these options are
available - See above).

*** File Area LightBar Support: CmdKeys = OP, Options = 31

*** Message Area LightBar Support: CmdKeys = OP, Options = 32

11. Message Bases:

1. In the message base editor, hitting X will allow you to
edit the DEFAULT base that is created in Renegade. This
will allow faster additions into the message areas by
allowing commands to changed to what you use the most.
ie: Max Messages can be defaulted to 200 instead of 100,
The tagline can be set, the path can be set, etc. etc.

12. File Validation:

1. Corrected a few places that utilized the SysOp or FileSysOp
access level instead of the global ULValReq System Settings
as in other instances to determine if a file should be
validated or not.

13. Files.BBS Processing:

1. Reduced the total variables required to process a hatched
file.

2. A successful upload will now show "Hatched" instead of
"Added" in the SysOp Log Entry. As before, you will
still see "Duplicate" if the file already exists or
"Missing" if the hatched file can not be found.

*IEMSI Logon:

1. At attempt to utilize the IEMSI record will no longer be made
for the shuttle logon menu or normal logon if the negotiation
failed.

2. Since the birthdate is included in the IEMSI record, it is
now utilized as part of the IEMSI logon. If the birthdate
verification is turn on in the system configuration, the
birthdate from the IEMSI record will auto populate the
birthdate verification field. If the birthdate is incorrect or
has not been completed by the user utilizing the IEMSI
logon, they will be prompted to manually enter their birthdate
as before.

Shuttle Logon:

1. A sysop log entry will now be generated if a user attempts
to logon to the shuttle menu with an invalid user name.
The "LOGERR" file will also be displayed (If it exists). The
user will also be disconnected if the maximum number of
attempts exceeds the setting in the system configuration.

2. An attempt to logon as New to the Shuttle Menu when the system
is closed to New Users will now display a note to the user that
the system is closed rather then just flashing the pre-logon
screen and re-displaying the shuttle menu.

3. The fact the user selected "No" to "Logon as New" from the
shuttle menu will now generate a sysop log entry.

4. A sysop log entry will now be generated if a user attempts to
logon to the shuttle menu when they have not been validated.

5. Selecting "HangUp" from the Shuttle Menu should now exit the
user from the system faster since it now bypasses numerous
procedures before exiting to the Waiting For Caller screen.
A sysop log entry will also be generated.

6. The "PRELOGON" file will now be displayed if the user chooses
to apply as a new user or logon to the system from the shuttle
menu. Therefore, the display of this file as a linked command
can be removed the Shuttle Menu.

Logging in User Number/Node Update:

1. Corrected an error where the user number was set to -1 instead
of 0 when the node record was updated at user logon. This -1
caused the user number to be set to 65535 in the node record.

SysOp Password:

1. Illegal attempts to utilize the SysOp Password will now
generate a short logon message to the SysOp.

Forgot Password:

1. The user will now be asked to re-enter their password and/or
phone number and/or birthdate after successfully logging in
utilizing the forgot password option. The user record will
also be saved.

Node ACS Access:

1. Illegal attempts to utilize a node without proper ACS
access will now generate a short logon message to the SysOp.

2. This check will only be made if the user is calling from a
remote location.

3. A duplicate check of the Node ACS access has been removed.

User Lock-out check:

1. Illegal attempts to access the system when locked-out will
now generate a short logon message to the SysOp.

2. This check will only be made if the user is calling from a
remote location.

3. A duplicate check of the lock-out status of the user has been
removed.

4. The lock out file must exist in the MISC path prior to locking
out a user in the User Editor.

Multi-Node Logon:

1. Illegal attempts to access more then one node at a time will now
generate a short logon message to the SysOp and a sysop log
entry.

2. This check will only be made if the user is calling from a
remote location.

Time Limits:

1. Added a check to set the user time limits to either per day or
per call in the Shuttle Menu and IEMSI Logon.

SysOp Log - Caller ID/IP Address:

1. The caller ID/IP Address has been moved from the end of the
"Logon node" sysop log entry to the next line down.

SysOp Log - User Separate Log:

1. Added the node number to this log.

Line Feeds:

1. Numerous line feed procedures were removed from the code and
were added as an MCI Code where appropriate. This should reduce
the overall size of the code and speed things up abit. This was
also accomplished to speed up the process of adding these items
to the string files at a later date.

Pause:

1. A line feed was added to the pause procedure so that the pause
does not appear directly under the verbage being displayed.

NEWUSER.INF File:

1. This file must be located in the MISC Directory (If utilized).

VT-100:

1. Corrected an issue where VT-100 would not display if selected
under preferences in the User Editor.

2. Corrected an issue where the Full Screen editor would be available
if the user selected VT-100.

NetMail/Internet Mail:

1. Corrected an issue where the Fee was not initialized to zero when
looking up a netmail or internet address. This would cause
the User Debit to be increased by a random number.

2. Corrected an issue where the user could select a netmail or
internet address that was not valid or setup in the System
Configuration. If an invalid selection is made, the AKA will
default to zero (Which means that the first address must be setup
in the System Configuration).

Private/Public Message Posting Credit:

1. Corrected an issue where a user that was exempt from public or
private message credits requirements would still receive posting
credit in some cases.

Node Listing (Who's Online):

1. Corrected an issue where the "Who's Online" listing would go into
an endless loop if all 255 nodes where configured.

Mass-Mail:

1. Corrected an issue where the message area was not re-initalized to
the previous message area after sending mass-mail.

2. Corrected an issue where the SysOp Window was not updated after
a user sent mass-mail.

ALT-F5 (SysOp Window):

1. Corrected an issue where the History.Dat file was not read in
when ALT-F5 was selected. This caused random numbers to be
displayed in the SysOp Window.

Other:

1. Numerous cosmetic and color changes were also made thru-out
the code.

Deleted Users (File/Message Area New Scan/Last Read Records):

1. Previously, the File/Message Area New Scan/Last Read Records were
not updated when a user was deleted. This caused the new user of
the deleted user record to default to whatever New Scan/Last Read
settings the previous deleted user had configured prior to deletion.
The New Scan/Last Read Records are now updated at the time a user
is deleted from the User Editor. Short Messages, User Votes and
Private mail are also deleted at this time. The time required
to delete a user record will now depend on how many File/Message
areas require update in addition to updating the Short Messages,
User Votes and Private Messages.

2. Non-accessible variables in the User Editor - New User Configuration
are now intialized at the time a new user logs on.

User Editor (New User Configuration):

1. The New User Configuration Record in the User Editor (Record 0)
can no longer be deleted! This would cause major issues
(Believe me, I know)

2. Fields can no longer be cleared in the New User Configuration
Record in the User Editor (Record 0).

User Editor (User Time Left):

1. The variable utilized to hold the User Time Left Online had to be
changed from an integer to longint value due to variable overrun.
This would cause the sysop window time left to be in error. The
maximum time limit for this variable has been set to 1440 minutes
per day thru-out the code. This was accomplished by swapping the
current integer value to an existing unused longint variable in the
user record so that a convertion was not required. Once upgraded
to this new version you will notice that this field in the user
record will probably indicate a random number and or 65535. Not
to worry, this will be corrected when the user logs on to their
normal SL time allowed. However, please change the New User
Configuration record back to it's original value.

User Editor (Option 1-5 Records):

1. All integer value fields that are changeable via the Call Record
options now have a minimum/maximum value associated to them. It will
no longer be possible to set any of these values to a negative
number or higher then allowed by the maximum limitations of the
assigned variable. After upgrade, please go thru your user records
to ensure that each of these fields falls within these allowances.
Please inform me if you notice any of these items to be outside these
limitations after you have completed the above.

Menu Editor (Fallback Menu):

1. The fallback menu number must be different then the menu number or
set to 0 (Zero).

System Flagged Functions (New User Application Sent To):

1. The "New User Application Sent To" can no longer be a deleted or
locked-out user. If this value points to a deleted or locked out
user upon entry or exit from this option it will default to User #1.

File Area Configuration (To-SysOp File Area):

1. If this value points to an invalid file area upon entry to this
option it will default to 0 (None).

[Submitted by admin]

Posted by adminonThursday 01 July 2010 - 16:51:00 | Read/Post Comment: 0 |