Renegade What Done History
Since the 2003 hand off to the Renegade Development Team
----[ Changes in v1.33/DOS ]----
============================================================================
U - Updated A - Added F - Fixed
============================================================================
F. Fixed bug where new ONELINERS would not display if a
datafile was remade from scratch and there were not a
total of 10 ONELINERS present in the original data file.
Before you would have to save 10 entries to the ONELINER
before anything would start to display. This has now
been corrected.
F. Renegade no longer sets the USERNAME as a blank field if
you were to hit ENTER when trying to change your username
on the BBS. New RGLNG.TXT entry has been added to account
for this as well.
U. Strings added to RGLNG for the "Scanning for your new
mail." and other strings related to this.
U. User Editor now uses standard prompts for editing
instead of using any pre-defined strings made in RGLNG that
were intended for the NEWUSER INFO MENU & PERSONAL MENU.
U. SysOp Window toggle back at ALT-S since SysOp Split
Screen chat is now a toggle in the system config. ALT-A
still works as well for now.
A. Added %EP (Empty Pause) MCI Code. This is for SysOps
or users that want to make their own PAUSE prompt without
using the system deinfed one. Just write your Pause Prompt
and on the next line input the MCI Code %EP. (Work in
progress.)
F. SysOp Password prompt will no longer have an input
field as part of the string.
F. Color codes right before the @ sign was not displaying for
Logon and Password strings. This has now been corrected.
F. Renegade will no longer prompt to save a blank string.
It will now revert to the string before the change was made.
A. Scrolling Text File Viewer. Work in progress, but it's
a start and it works. Right now, ASCII text only works. Will
add more complex features as we work on this.
New MENUCMD: VI - Scrolling Text File Viewer
Works the same as -F. Whatever you put in the options field
will be displayed, only with the VI CMD Key you can scroll
UP and DOWN.
F. Bug in Renemail which would cause a large swap file
to be created if a certain type of Fido stye message was
imported. This has now been corrected and checked for.
A. More Strings external. SysOp In/Out and Multinode
chat availble/unavailable.
F. Oneliners will now show [ANONYMOUS] if the person
who wrote the oneliner is deleted from the userbase.
F. Miscellaneous Cleanup and Color fixes.
----[ Changes in v1.30/DOS ]----
============================================================================
U - Updated A - Added F - Fixed
============================================================================
A. Not really a Renegade Fix, but added Lee Woodridge to the
Renegade Development Team.
A. Added internal OneLiner Program.
New Files :
ONELH.* - Oneliners Header (Optional)
ONELM.* - Oneliners Middle (Required!!)
ONELT.* - Oneliners Footer (Optional)
ONELM.* MCI Codes :
~AN (Anon - Yes/No) ~AT (Anon - True/False)
~DA (Date Added) ~OL (The Oneliner)
~RN (Record Number) ~U# (User ID with '#')
~U1 (User ID without '#') ~UN (User Name)
~UL (User Name Lowercase)
~US (First 2 Letters of Username - iNiQUiTY Style)
~UU (First 2 letters of username lowercase)
New MENUCMD Keys For OneLiners:
1L - Display Oneliner (Header/Footer & all Oneliners)
1R - Display Random line from Oneliner File
F. Local file upload bug. Before when uploading locally with
the FU command key after 1 upload it would stop and you would
have to repeat the process. It somehow become broken over
the years and no one said anything. Now it will upload all
files without stopping if a *.* is entered for the filename.
F. When a file was moved, if it was a dupe, the file wasn't moved
but the description was. This is no longer the case. If the
file is a dupe, nothing is moved. This prevents dupe file
descriptions.
F. The (~TO) MCI Code in the LASTM.ASC file would display a random
number when viewed while the user was still online. This has
now been updated to show " - " until the user logs off and
the correct time online will be shown by this MCI code.
A. New MCI Code - %XYaa;bb% (aa=01-80 Left to right) and
(bb=01-25 Top to Bottom). Allows format positioning of the
cursor without the need of having your ANSI menu file do it,
for you. Say you wanted the word "Hello!" to appear in the
middle of the screen, it would be used as such:
%XY40;12%Hello!
The above would move the cursor to space 40, line 12, and put
your text of "Hello!" starting there.
U. The Auto Message is now configurable. It is like the oneliner,
last caller, user list, etc. It has a header, main, and a
footer file in the MISC directory.
The auto message is now saved as "AUTOM.ASC" instead of
"AUTO.ASC" to make it conform to the rest of the code base.
New Files :
AUTOH.* - Auto Message Header (Optional)
AUTOM.* - (Can be made, but automagically made when a auto)
(message is created. This is your auto message.)
AUTOT.* - Auto Message Footer (Optional)
U. Disabled Forgot password response for Co-SyOp and above.
This would prevent someone from trying to logon as the SysOp
and trying the forgot password question answer and resetting
it so they can logon as the SysOp.
U. Can now scroll through the node settings without having to
load each node seperately.
A. Added System Config Menu Option (N). SysOp Macros. They were
moved from another submenu to make a more cleaner look and easier
to find.
F. Removed System Config and File Area Editors strings from
the language files to prevent unwanted access. Also removed the
MCI codes that ran these menus (which would've caused a problem
in certain instances.)
A. YES/NO LightBar Choice options added to the YES/NO Prompt MENUCMDs.
F. Split Screen Chat now auto scrolls and stays within it's
borders. Also added help commands that are listed in the center
of the chat screen.
U. When the SysOp breaks into chat via a "Chat Page" with the
SpaceBar the split screen chat will auto load. Otherwise, the
normal line chat will be used.
Chat commands are as follows:
ALT-C - Line Chat ALT-S - Split Screen Chat
U. Teleconference strings are now located within the RGLNG
text file instead of the Node setup options screen in the system
configuration section.
U. RENEGADE.EXE /? now shows what command line parameters are
available to run along with a short message of what each does.
U. All strings are now combined into RGLNG.TXT.
A. New MENUCMD *T to toggle SysOp Chat Availability without
the use of the SCROLL LOCK key. Also, new MCI Code %SA to show
if the sysop is avaliable or not.
U. Removed more strings from Renegade and added them to
RGLNG.TXT for more editing for the SysOp.
U. Redid NewUser Toggle Questions Menu to add all toggles
in one place. Remember to clear your all of your toggles after
you upgrade so the new changes will take effect. Cmd Key of *
will do this for you.
U. User #0 (Default account) can now be cleared for all user
options. Cmd Key of $ will allow you to clear out which
fields you want to be blank instead of having a "." or some
random text in the user data file. This is also a good idea to
do once you upgrade as the forgot password question more than
likely has a space in it's field and more than likely won't
work until you clear the prompt with the $ cmd key.
U. Updated OP Menu CMD options. Be sure to change these in
your NEWINFO menu and PERSONAL info menus or else what you
have listed won't match what it does. ;)
New OP Menu CMD Options:
1 Handle
2 Real Name
3 Country
4 Address
5 City, State
6 Zip Code
7 Phone Number
8 Age
9 Gender
10 SysOp Defined Question #1
11 SysOp Defined Question #2
12 SysOp Defined Question #3
13 Password
14 Forgot Password Question Answer
15 Terminal Emulation
16 ANSI Color Toggle
17 Color Scheme
18 Screen Size
19 Screen Clearing
20 Screen Pausing
21 Hotkey Input
22 Expert Mode
23 Lightbars Toggle
24 Editor Toggle
25 Mailbox Toggle
26 QWK Configuration
27 * UNUSED *
28 * UNUSED *
29 * UNUSED *
30 * UNUSED *
U. Updated SysOp LOG Output. Now shows a bit more info on
what the user was doing while online. Such as what menus
were accessed (along with menu titles & numbers) and a time
stamp on when things were accessed.
F. Finally tracked down bug that would lock up a newscan
if you had more than 255 files in a base.
U. New MCI Code %OL -- Light Bars On/Off. This replaces
the file and message light bar mci codes.
F. Fixed bug that allowed the user to Email deleted users.
Co-SysOp and higher can still email (for what reason, testing?)
deleted users. A Prompt will ask if you wish to or not.
U. Added Several Email Error strings to RGLNG
U. Top 10 Files Listing now asks if you would like to
download one of these files from the menu. If you select YES
you will be given the option to download file 1-10.
U. More strings added to RGLNG.TXT file to edit for your
pleasure. ;)
F. User Record now correctly updates stats when a user
dowloads or uploads a file.
U. Increased MAX system menus to 200 from 100.
A. Added additional Sub-Menus to System Toggles in
System Config.
----[ Changes in v1.25/DOS ]----
============================================================================
U - Updated A - Added F - Fixed
============================================================================
U. Updated Renegade Booting to now NOT show all the debug code.
U. Updated WFC Screen and removed the "total space free" option as
Pascal only reports up to 1.9 Gig. Added Errors to Today's stats
as well and moved all options down to give a beter uniform look.
U. Updated "Scan for your personal messages" colors to be easier on the
eyes than the old yellow color.
U. CTRL-HOME key combination updated to reflect options.
ALT-A is now SysOp line ON/OFF
ALT-S is the Split Screen Chat
The above CTRL-HOME options were changed in v1.22 but the Help screen
was never updated.
U. Updated some miscellaneous display files that were maybe not
listed so that they can be used. These are placed in your
RENEGADE\MISC directory.
MISC DIRECTORY FILES - These can be .ANS, .ASC, .RIP, .AVT
2MANYCAL - Prints when user logs on more than allowed.
AUTOVAL - Prints when user successfully auto validated
BATCHUL0 - Displays before a Batch Upload w/ 0 files in queue.
BATCHUL - Displays before a Batch Upload Queue.
CHATEND - Displays when SysOp Chat is started.
CHATHELP - Shows options in SysOp Chat.
CHATINIT - Displays when SysOp Chat is ended.
CHATOVR - Displays for Chat Override
DLHOURS - Prints to show Download Hours.
DLOAD - Displays before a file is downloaded.
DLMAX - Max Downloads Reached Display File
DLBTMAX - Max Downloads (Batch) Reached Display File
GOAWAY - Displayed when tried chatting too many times.
HANGUPxx - Displays on logoff. HANGUP.xxx or HANGUP1.xxx
through HANGUP99.xxx
LOGERR - Displays if user incorrectly enters name/pw.
LOGOFF - Displays on Slow Logoff.
LOGONx - Displays after user logon. LOGON, LOGON1-LOGON9
MULTILOG - Prints when user is already logged on a node.
NEWAPP - Displays before a new user sends email to sysop.
NETMHELP - Displays before a netmail is written.
NOACCESS - Prints when a user chooses a cmd they do not
have access to.
NOLEFT - Prints when user has no time left.
NONODE - Prints when user does not have access to node.
NOSYSOP - SysOp Not Here Display
ONCEONLY - Displays ONCE only to a user.
PRELOGON - Displays after copyright notice.
PROTRES - Resume Protocols Display
PROTBDL - Displays Protocols before a Batch Download
PROTBUL - Displays Protocols before a Batch Upload
PROTSDL - Displays Protocols before a Download
PROTSUL - Displays Protocols before a Upload
REQFILE - Prints when a file needs to be requested.
SPLTCHAT - Displays for Split Screen Chatting w/ SysOp.
TELECONF - Prints when user enters the BBS Teleconference
TERMINAL - Displays which terminal type to use.
TIMEOUT - Prints when user has a timeout logoff.
WELCOMEx - Displays after user logs onto system and also
allows to display WELCOME, and WELCOME1
through WELCOME9.
WRNGBDAY - Displays when user enters wrong Birthday.
UPLOAD - Prints before a user uploads a file
A. Added new MCI Codes as follows:
MCI CODES
%OF - Use File Light Bar (ON/OFF Answer)
%OM - Use Message Light Bar (ON/OFF Answer)
%ON - If Node Is Available For Chat (ON/OFF Answer)
%OZ - User's Current Archive Format (Extention - ie: ZIP, ARJ, RAR)
U. Removed/Added some line spacing after certain hard coded internal
displays and prompts. Gives things a cleaner look than being jumbled
together when they are displayed.
U. Code Cleanup on Renemail. Nothing major, tweaked the UI a little and
did a color change. Couldn't stand that Blue Background anymore.
Also updated the copyright notice.
U. New Renegade BBS WWW Home - http://www.rgbbs.info
U. Finally noticed the "New Scanning of Files" prompt was not exported
to RGLNG.TXT. Added this option, so you can now change your
"Scanning File Base Name ... " prompt to more closely match your BBS.
Will include a new RGLNG.TXT file in the update, or you can just add
the option to the end of your RGLNG.TXT file called NEW_FILE_SCANNING
$New_File_Scanning
%CLScanning ... [%FB - %HM]@
$
U. Updated RGLNG.EXE to allow for the new addition as well.
U. Tweaked Files.BBS importer in Renegade a bit for better dupe checking.
The Files.BBS importer can be run by running RENEGADE -F at the prompt.
----[ Changes in v1.22/DOS ]----
Miscellaneous internal bug fixes and full install created
Win32 Files scrapped.
----[ Changes in v1.20a/DOS ]----
DOS and Win32 files created.
----[ Changes in v1.19a/DOS ]----
========================================================================================= UPGRADE INFO ===========================
=================================================================
Unzip this upgrade package into your main Renegade
directory. Run RGUPDATE.EXE to update miscellaneous
data files and RENEGADE.DAT file. Once this is done,
the file can be erased.
This is a "HotFix" to solve the XMS not loaded problem
** that a new windows update caused. This should fix
all issues with Renegade not loading.
=================================================================
======================== UPGRADE INFO ===========================
=================================================================
Remember to add the following switches to your command
line to load Renegade properly.
Also, if using WinXP check your _DEFAULT.PIF file in
your main Windows directory. Make sure all memory
settings are set to AUTO instead of NONE, or else RG
may or may not load.
Loading "RENEGADE -D" will load Renegade with Overlays
writing to DISK until you fix the memory issue with
the .PIF file in WinXP. Do NOT run Renegade like this
all the time or the program will run very slow compared
to how it is supposed to run in memory. This is just
a quick "fix" to be able to load the BBS and make sure
everything is working if you are getting a "Memory
Error."
----[ Changes in v1.18a/DOS ]----
We have included TEXT.ZIP as defaults that are needed. Make sure
you append these to any "custom" strings you have so you will have
all strings to date. These should be the ONLY files in your TEXT
directory if you choose to create a seperate directory for these files.
Option 9. below should be changed in RGCFG.TXT to reflect the name
change from "RAM Drive/MulitNode Path" to "Strings/Text Directory".
You can keep the same path, but whatever the path is set in Option 9,
is where Renegade will look for ALL strings.
-=-=-=- RGCFG.TXT file -- System Config Bottom of Screen -=-=-=-
0. Main data files dir. : %PD
1. Miscellaneous Files dir.: %PM
2. Message file storage dir: %P1
3. Nodelist (Version 7) dir: %P2
4. Log files/trap files dir: %PL
5. Temporary directory : %PT
6. Protocols directory : %PP
7. Archivers directory : %P7
8. File attach directory : %PF
9. Strings directory : %P3
ONCE THIS IS DONE, BE SURE TO RUN -- RGLNG.EXE -- TO RECOMPILE
YOUR STRINGS OR ELSE YOU WILL HAVE ISSUES UNTIL YOU DO!!
=================================================================
======================== UPGRADE INFO ===========================
=================================================================
New MENUCMD's to turn ON/OF lightbar options. Add these
to your Personal Info Menu for user selection if you wish.
- Turn ON/OFF File Light Bars -
MENUCMD - OP
OPTION - 31
- Turn ON/OFF Message Light Bars -
MENUCMD - OP
OPTION - 32
=================================================================
======================== UPGRADE INFO ===========================
=================================================================
Remember to add the following switches to your command
line to load Renegade properly.
Also, if using WinXP check your _DEFAULT.PIF file in
your main Windows directory. Make sure all memory
settings are set to AUTO instead of NONE, or else RG
may or may not load.
Loading "RENEGADE -D" will load Renegade with Overlays
writing to DISK until you fix the memory issue with
the .PIF file in WinXP. Do NOT run Renegade like this
all the time or the program will run very slow compared
to how it is supposed to run in memory. This is just
a quick "fix" to be able to load the BBS and make sure
everything is working if you are getting a "Memory
Error."
=================================================================
======================== LOADING INFO ===========================
=================================================================
RENEGADE -T - enables Telnet connections with Net2BBS
RENEGADE -TC - enables Telnet connections when used
with NetSerial or COM/IP.
These switches also set the users baud rate in the
last callers to "TELNET".
----[ Changes in v1.10/DOS ]----
1. FIXED - Minor issue with log files. Anytime a QWK was downloaded
garbage was thrown to the log file. This has been
corrected and will now show correctly what was done.
2. FIXED - Pressing "P" for Point entry in the file validation editor
would go into a never ending loop if there were no
un-validated files in a file area.
3. FIXED - Pressing
the validation process rather then skip to the next file.
4. CHANGE - The file validation editor will now show the file areas
being scanned just like other file search commands do.
5. FIXED - The file area display header was off by one character.
6. CHANGE - In the past, the maximum number of file areas allowed
was 2048 with compression turned on and 32767 with it
turned off. Renegade will now support 32767 file areas
with compression on or off.
7. CHANGE - The file area listing will now display the file areas
one page at a time vice scrolling thru the entire list.
The '?' will now re-list the areas starting from file
area 1. Pressing
(it will also restart the listing from file area 1 when
the last file area is reached). Pressing 'Q' will exit
the file area display. Previously, this procedure opened
all 3 files associated to an area (*.DIR, *.EXT & *.SCN)
to read file area scan flag. This process sould now be
faster since it now only opens the *.SCN file.
8. CHANGE - The file area change listing will now display the file
areas one page at a time vice scrolling thru the entire
list. The '?' will now re-list the areas starting from
file area 1. Pressing
page (it will also restart the listing from file area 1
when the last file area is reached). Pressing 'Q' will
exit the file area display. Entering an invalid file
area will redisplay the current page.
9. CHANGE - The file area set scan listing will now display the file
areas one page at a time vice scrolling thru the entire
list. The '?' will now re-list the areas starting from
file area 1. Pressing
page (it will also restart the listing from file area 1
when the last file area is reached). Pressing 'Q' will
exit the file area display. Previously, this procedure
opened all 3 files associated to an area (*.DIR, *.EXT
and *.SCN) to set the area scan on or off. This process
should now be faster since it now only opens the *.SCN
file.
Also, this procedure will now only set the scan on file
areas the user has access to. The file area scan char
has been moved to the left of the file area number vice
between it and the file area description.
9. FIXED - The resolution of a GIF file was truncated by one
character when viewing these files using the Achive
View Command, fixed. Also spruced up the entire
display. GIF files that are missing will now be
displayed with a blinking red "< Missing GIF >".
GIF files that are bad will now be displayed with a
blinking red "< Bad GIF >". Bad or missing GIF files
are also now added to the SysOp Log. The first line
of the file description has been reduced to 31 chars
to allow for the maximum possible length of the GIF
resolution.
1. The File Area Editor has made modified with the following:
A. The file area listing will now display one page at a time
verses scrolling to the prompt.
B. The File Area Name can not be blank or the default of
<< New File Area >>.
C. The File Area File Name can not be blank or the default of
NEWAREA.
D. The File Area Download Path can not be blank.
E. The File Area Upload Path can not be blank.
F. The File Area Archive Type must be active.
G. The File Area Comment Type must be active.
H. Unused fields in the Insert/Modify command will now
display *None*.
I. The File Area Insert command will now display the file
Area information for editing verses just inserting the
new record and then requiring you to go to the modify
command to edit. You will not be able to save the
new file area until all of the above items are correct.
Upon completion of editing the inserted record, you will
be prompted to save or discard the new file area. The
download/upload directories and the data files will be
auto-created after the new file area is saved. The *.SCN
file will also be updated for all users to scan this file
area.
J. The File Area Delete command will no longer prompt to
delete the data files if the the file area name is being
utilized by another file area.
K. The File Area Modify command will auto-create the
download/upload path and data files after editing or
changing to another file area. The *.SCN file will
also be updated to ensure all users are toggled to
scan this file area. You will not be able to save the
file area you are editing until all of the above items
are correct. This command has also been modified
to scan the user file for deleted users and to set the
*.SCN file to allow new scan for the next user to utilize
this file area.
L. Other changes included added some missing help data for
certain commands and color changes.
2. I recommend that you access the File Area Modify command
once you have installed this update and toggle thru all
file areas and make corrections to your file areas as they
are presented to you.
1. The File Area Editor has made modified with the following:
A. The file area listing will now display one page at a time
verses scrolling to the prompt.
B. The File Area Name can not be blank or the default of
<< New File Area >>.
C. The File Area File Name can not be blank or the default of
NEWAREA.
D. The File Area Download Path can not be blank.
E. The File Area Upload Path can not be blank.
F. The File Area Archive Type must be active.
G. The File Area Comment Type must be active.
H. Unused fields in the Insert/Modify command will now
display *None*.
I. The File Area Insert command will now display the file
Area information for editing verses just inserting the
new record and then requiring you to go to the modify
command to edit. You will not be able to save the
new file area until all of the above items are correct.
Upon completion of editing the inserted record, you will
be prompted to save or discard the new file area. The
download/upload directories and the data files will be
auto-created after the new file area is saved. The *.SCN
file will also be updated for all users to scan this file
area.
J. The File Area Delete command will no longer prompt to
delete the data files if the the file area name is being
utilized by another file area.
K. The File Area Modify command will auto-create the
download/upload path and data files after editing or
changing to another file area. The *.SCN file will
also be updated to ensure all users are toggled to
scan this file area. You will not be able to save the
file area you are editing until all of the above items
are correct. This command has also been modified
to scan the user file for deleted users and to set the
*.SCN file to allow new scan for the next user to utilize
this file area.
L. Other changes included added some missing help data for
certain commands and color changes.
2. I recommend that you access the File Area Modify command
once you have installed this update and toggle thru all
file areas and make corrections to your file areas as they
are presented to you.
1. The message area display header was off by one character, fixed.
2. In the past, the maximum number of message areas allowed was 2048 with
compression turned on and 32767 with it turned off. Renegade will
now support 32767 message areas with compression on or off.
3. The message area listing will now display the message areas one page
at a time vice scrolling thru the entire list. The '?' will now
re-list the message areas starting from message area 1. Pressing
will now display the next page (it will also restart the listing from
message area 1 when the last message area is reached). Pressing 'Q'
will exit the message area display. Previously, this procedure opened
all 3 files associated to a message (*.HDR, *.DAT & *.SCN) to read
the message area scan flag. This process sould now be faster since it
now only opens the *.SCN file.
4. The message area change listing will now display the message areas
one page at a time vice scrolling thru the entire list. The '?' will
now re-list the message areas starting from message area 1. Pressing
from message area 1 when the last message area is reached). Pressing
'Q' will exit the message area display. Entering an invalid message
area will redisplay the current page.
5. The message area set scan listing will now display the message areas
one page at a time vice scrolling thru the entire list. The '?' will
now re-list the message areas starting from message area 1. Pressing
from message area 1 when the last message area is reached). Pressing
'Q' will exit the message area display. Previously, this procedure
opened all 3 files associated to a message area (*.HDR, *.DAT & *.SCN)
to set the message area scan flag on or off. This process sould now be
faster since it now only opens the *.SCN file. Also, this procedure
will now only set the scan on message areas the user has access to.
The message area scan char has been moved to the left of the message
area number vice between it and the message area description.
6. The file area delete command will now prompt to remove the download
and upload directory if they are not being utilized by another file
area.
1. You will now be prompted to set the upload path to the download
path when editing the download path in the File Area Editor. The
'D' option has been removed due to drive conflicts.
2. The File Area Delete option has been modified to prompt you to
delete the download/upload directory if they are not being utilized
by another file area.
3. The Message Area Editor has made modified with the following:
A. The message area listing will now display one page at a time
verses scrolling to the prompt.
B. The File Area Name can not be blank or the default of
<< New Message Area >>.
C. The File Area File Name can not be blank or the default of
NEWBOARD.
D. The Message Path for Echomail/Groupmail can not be blank.
E. The Message AKA Address for Echomail/Groupmail must be an
active address setup in the System Configuration.
F. The Message Origin for Echomail/Groupmail/QWKmail can not be
blank.
G. Unused fields in the Insert/Modify command will now
display *None*.
H. The Message Area Insert command will now display the Message
Area information for editing verses just inserting the
new record and then requiring you to go to the modify
command to edit. You will not be able to save the
new message area until all of the above items are correct.
Upon completion of editing the inserted record, you will
be prompted to save or discard the new message area. The
message directory and the data files will be auto-created
after the new message area is saved. The *.SCN file will
also be updated for all users to scan this file area.
I. The Message Area Delete command will no longer prompt to
delete the data files if the message area file name is being
utilized by another file area. This option has also been
modified to prompt you to delete the message directory if it
is not being utilized by another message area.
J. The Message Area Modify command will auto-create the
message directory and data files after editing or
changing to another file area. The *.SCN file will
also be updated to ensure all users are toggled to
scan this message area. You will not be able to save the
message area you are editing until all of the above items
are correct. This command has also been modified
to scan the user file for deleted users and to set the
*.SCN file to allow new scan for the next user to utilize
this message area.
K. Other changes included added some missing help data for
certain commands and color changes.
4. I recommend that you access the Message Area Modify command
once you have installed this update and toggle thru all
message areas and make corrections to your message areas as they
are presented to you.
1. The file/message area compression routines have been replaced
completely. In the previous version the following variables,
functions and procedures were utilized:
VAR - "FileCompArray = ARRAY[0..4095] OF SET OF 0..7"
VAR - "MsgCompArray = ARRAY[0..4095] OF SET OF 0..7"
Procedure - "NewCompTables:
Function - "CompFileArea(FArea: Integer): Integer"
Function - "CompMsgArea(MArea: Integer): Integer"
Function - "AFBase(FArea: Integer): Integer"
Function - "AMBase(MArea: Integer): Integer"
The FileCompArray/MsgCompArray were previously updated by the
NewCompTables Procedure. The NewCompTables Procedure would
simply read in all file/message areas and set a bit to on or off.
The CompFileArea/CompMsgArea Functions would then display the proper
File/Message area after counting from the first file/message area to
the file/message area that needed to be displayed based on the user
access and compression setting in System Configuration. The
AFBase/AMBase Functions were utilized to return the proper file/message
area after counting from the first file/message area to the
file/message area the user actually selected based on the user access
and compression settings in System Confguration.
As you can see from the above discription, this required alot of
memory to maintain the FileCompArray/MsgCompArray. It also required
four functions for area number display and access. Not to mention
that the real area number for both display and access had to be
counted up to every time an area was displayed or accessed.
The following varibales, functions and procedures are being
utilized in this release:
FILE - "FACT[Node].DAT" (Stored in the Node Temp Directory)
FILE - "MACT[Node].DAT" (Stored in the Node Temp Directory)
TYPE - "CompArrayType = ARRAY[0..1] OF INTEGER"
VAR - "LowFileArea: Integer"
VAR - "HighFileArea: Integer"
VAR - "LowMsgArea: Integer"
VAR - "HighMsgArea: Integer"
Procedure - "NewCompTables"
Function - "CompFileArea(FArea,ArrayNum: Integer): Integer"
Function - "CompMsgArea(MArea,ArrayNum: Integer): Integer"
Two new files (FACT[Node].DAT/MACT[Node].DAT have been created and
are temporarily stored in the Node temp directory. A record of type
ARRAY[0..1] OF Integer is the storage method utilized for the
individual file areas. ARRAY 0 is utilized for storage of the
file/message area to display and ARRAY 1 is utilized for the storage
of the file/message area being accessed. Each record takes up 2 bytes
of space on your harddrive and the above file will only contain
records for the actual number of message/file areas you actually have
available. Both of these files are created at user logon and updated
at other appropriate times as Renegade requires and then deleted when
the user logs off. The NewCompTables Procedure creates and updates
the actual file/message area for display (ARRAY 0) and the actual
file/message area to access (ARRAY 1). This saves on the need to
have the FileCompArray/MsgCompArray and the need for the
CompFileArea/CompMsgArea And AFBase/AMBAse to count everytime
from 1 to the file/message area displayed or accessed. The
CompFileArea/CompMsgArea Functions have been modified to access the
record contained in the FACT[Node].DAT/MACT[Node].DAT file for the
file/message area being display/accessed. This eliminated the need
for the AFBase/AMBase Functions. CompFileArea(FArea,0) or
CompMsgArea(FArea,0) is called to obtained the display area number
and CompFileArea(FArea,1) or CompMsgArea(FArea,1) is called for
the area number to access. NewCompTables will now also return the
LowFileArea, HighFile, LowMsgArea & HighMsgArea for trapping correct
or incorrect file/message area user input.
As you can see, this enhancement saved alot of memory. Display and
access to a file/message areas should now be faster. Adding the
low/high File/Messae variables will also help trap user input errors.
1. The Conference Editor has made modified with the following:
A. The Conference Name can not be blank or the default of
<< New Conference Record >>.
B. Unused fields in the Insert/Modify command will now
display *None*.
C. The Conference Insert option command will now display the
Conference information for editing verses just inserting the
new record and then requiring you to go to the modify
command to edit. You will not be able to save the
new conference until the item above is correct.
Upon completion of editing the inserted record, you will
be prompted to save or discard the new conference area.
D. The Conference Modify command will also require that the
above item is correct before saving the record being edited.
2. I recommend that you access the Conference Modify command
once you have installed this update and toggle thru all
conferences and make corrections to your conferences as they
are presented to you.
1. The 'Q' and 'q' are no longer available for Validation Keys.
2. The Validation Editor has made modified with the following:
A. The Validation Editor Listing will now display one page at
a time verses scrolling to the prompt.
B. The Validation Level Description can not be blank or the
default of << New Validation Record >>.
C. Unused fields in the Validation Editor Insert/Modify command
will now display *None*.
D. The Validation Editor Insert command will now display the
Validation Record information for editing verses just inserting
the new record and then requiring you to go to the modify
command to edit. You will not be able to save the
new validation record until all of the above items are correct.
Upon completion of editing the inserted record, you will
be prompted to save or discard the new validation record.
E. Other changes included added some missing help data for
certain commands and color changes.
3. I recommend that you access the Validation Modify command
once you have installed this update and toggle thru all
the validation records and make corrections as they are presented
to you.
1. All of the File Editor strings have been removed to the
file FAELNG.TXT. This can be compiled utilizing the updated
RGLNG.EXE Program.
2. Some work has been completed on the System Configuration Editor.
3. The Protocol Editor has made modified with the following:
A. The Protocol Records have been modified and will require
that you execute a conversion utility to upgrade to the
current version of Renegade.
B. The protocol listing will now display one page at a time
verses scrolling to the prompt.
C. The Protocol Editor Insert/Modify option will display only
the fields required for the type of protocol you are
setting up. This is controlled by the Single/Batch Flags and
the UL/DL Commands. Numerous notes and error messages have
also been added to ensure all required fields are filled in
prior to the protocol record being saved.
D. Unused fields in the Protocol Editor Insert/Modify option will
now display *None*.
E. The Protocol Insert option will now display the protocol
record information for editing verses just inserting the
new record and then requiring you to go to the modify
command to edit. You will not be able to save the
new protocol record until all of the above items are correct.
Upon completion of editing the inserted record, you will
be prompted to save or discard the new protocol record
F. Other changes included added some missing help data for
certain commands and color changes.
3. I recommend that you access the Protocol Editor Modify command
once you have installed this update and toggle thru all the
protocol records and make corrections as they are presented to you.
1. Fixed a bug that would not allowing the saving of an added voting
answer by the user.
2. The Voting Topic Editor has made modified with the following:
A. The Voting Topic Editor has been modified to have pretty much
the same look and feel of the Menu Editor.
B. The Voting Topic and Topic Choice Editor Listing will now
display one page at a time verses scrolling to the prompt.
C. The Voting Topic and Topic Choice Editor question and answer
can not be blank or the default of << New Voting Topic >> or
<< New Topic Choice >>.
D. Unused fields in the Voting Topic and Topic Choice Editor
Insert/Modify command will now display *None*.
E. The Voting Topic and Topic Choice Editor Insert command will
now display the Topic and Choice Record information for editing
verses just inserting the new record and then requiring you to
go to the modify command to edit. You will not be able to save
the new topic or choice record until all of the above items
are correct. Upon completion of editing the inserted record,
you will be prompted to save or discard the new Topic record.
F. The Reset Topic option has been moved to the Voting Topic Editor
Main screen and is accessed by pressing "R". You will then be
prompted to enter the record number of the topic you want to
reset.
G. A Recalculate Voting Topics command has also been added to the
Voting Topic Editor main screen and is accessed by pressing "S".
This option will clear all voting data from the voting topic
records. It will then access the vote array for all User Records
and update the voting topic records based on what question the
user voted on and the choice the user made. This option excludes
deleted users and will ensure that the values in the user.vote
array are set to zero. Depending on Sysop Input, locked out users
could also be excluded per above.
E. Other changes included adding some missing help data for
certain commands and color changes.
3. I recommend that you access the Voting Topic Modify Command
once you have installed this update and toggle thru all
of the voting topic records and make corrections as they are
presented to you.
1. The Archive Editor has made modified with the following:
A. The Archive Editor extension can not be blank or the default
of "AAA".
B. Unused fields in the Archive Editor Insert/Modify command
will now display *None*.
C. The Archive Editor Insert command will now display the
archive record information for editing verses just inserting
the new record and then requiring you to go to the modify
command to edit. You will not be able to save the new archive
record until all of the above items are correct. Upon completion
of editing the inserted record, you will be prompted to save
or discard the new archive record.
D. Other changes included adding some missing help data for
certain commands and color changes.
2. I recommend that you access the Archive Modify Command
once you have installed this update and toggle thru all
of the archive records and make corrections as they are
presented to you.
1. The Scheme Editor has made modified with the following:
A. The Scheme Editor description can not be blank or the default
of << New Color Scheme >>.
B. Unused fields in the Scheme Editor Insert/Modify command
will now display *None*.
C. The Scheme Editor Insert command will now display the
scheme record information for editing verses just inserting
the new record and then requiring you to go to the modify
command to edit. You will not be able to save the new scheme
record until all of the above items are correct. Upon completion
of editing the inserted record, you will be prompted to save
or discard the new scheme record.
D. Other changes included adding some missing help data for
certain commands and color changes.
2. I recommend that you access the Scheme Modify Command
once you have installed this update and toggle thru all
of the scheme records and make corrections as they are
presented to you.
----[ Changes in v1.00/DOS ]----
1. ADDED - Two new commands for the message read menu: (See Updated
MENUCMD.ASC File)
RS = Show Message Poster (User Information)
RV = Validate Message Poster (Level A-Z)
MR CMD now needs an option to read public messages
This was update last version but wasn't documented
properly.
MR = Read Messages [Options - R]
R - Read Public Message Areas
Leaving the options field blank will read E-Mail.
2. FIXED - When editing a message in the public areas, pressing E
for edit and then pressing D to display header only
displayed up to 5 lines. If the message was posted as
anonymous, you wouldn't see the 6th line for the real
name to whatever name.
3. CHANGE - Intergrating email read menus to work in the existing
public message read menus. And then in so doing the
"Back In Thread" and "Forward in Thread" now also work
when reading private messages. So, in the end, the
private mail read menus will use the same public read
menus, have the same look and feel.
4. FIXED - Cleaned up the Validate user from the ReadMail command,
this command allowed pressing a "Q" to quit, but in
doing so, you would validate the user at whatever
level "Q" was. This was removed and require just that
ENTER be pressed to avoid setting anything.
5. CHANGE - The move command to work to move messages from the
public message areas to the private (not sure when the
need might arise to do this, but maybe a flame in the
public area and the sysop wants to move it to private
if the receiver is a member of the bbs, rather then
just delete it).
6. CHANGE - The messages are now listed before selecting a message.
Before, all you got was a prompt that said what area
you were in and the range of the messages to select from.
Now, when reading all private mail or public mail, The
messages are listed (With header) up to 18 messages per
page. Pressing enter takes you to the next page or
listing of messages. Once you reached the end of the
messages (by pressing ENTER) and you press it again, it
will take you back to the first message and you can
continue to list messages that way until you select
one or quit.
7. FIXED - The creation of VDM*.TMP files in Windows XP caused by
Renegade are now fixed. These files should NO LONGER
be created because of file locking issues with Renegade.
It took a while to fix, but ... it's windows, yaknow. ;)
8. ADDED - Added a new MENUCMD Key :
RJ - Forward Public Message into Private Mail and
also Private E-Mail to another Private E-Mail
account.
This CMD Key is for the READP Menu ONLY to FORWARD a
public message to private e-mail.
9. CHANGE - The High Read Msg Pointers are no longer updated after
a new account is created. This was taking a very long
time if a BBS had a large amount of messgae areas. This
is now done the first time the user scans the msg areas.
10. FIXED - A bug where if the sysop shells inside a background input
prompt (Blue for example) the screen will no longer turn
the color of the input box in the shell. It will clear
the screen using a black background, lightgrey foreground.
11. FIXED - RG would attempt to create the entire directory (Example:
C:\rg\dls\test). If dls didn't exist before the "test",
it would fail. Now, it will create the entire directory
(if the path is valid). It now also reports errors to the
user on screen.
12. CHANGE - You can now use a "D" to make the ULPath the same as the
DLPath instead of typing in the entire path if they are
the same when creating a new file area.
13. CHANGE - New History Editor - You can now edit dates and information
inside the HISTORY.DAT file to correct any errors that
are noticed. You can now view logons by BAUD RATE via the
history editor.
14. FIXED - Numerous updates to all the door drop files (ongoing).
15. CHANGE - Updated "RENEGADE.LNG" file, and new converter "RGLNG.EXE"
which compiles the few remaining strings and removes all
strings that were moved to differnt files and locations
on previous versions.
16. CHANGE - FILE_ID.DIZ File Descriptions are now expanded to 99 lines.
All you ASCII Art Freaks should scream "Hor-ray!"
17. FIXED - Time Slice Routines - RG now actually detects if it is
running under DOS, OS2 or Win32 and act accordingly. Before
Renegade ALWAYS thought it was under DOS and thus caused
some slow down which was sort of addressed with the time
slice setting in system config. This will help even more
now that it is hardcoded to look for this.
18. OLD/NEW - MENUCMD *= This allows Renegade to display long or short
menu cmd listings. *= with options set at 1 will display
short menu cmds. *= with options set at 2 will display
long menu cmds to the screen.
19. FIXED - "FC" CMD KEY (Files.BBS Importer)
1. Optimized by removing a duplicate procedure.
2. Reports duplicate files in the Sysop.log.
3. Reports missing files in the Sysop.log.
4. The "Hatched" flag is now set for all imported files.
5. The user can now enter file points per file uploaded
when not in the waiting for caller screen (Parameter
switch -F).
6. All User/System upload statistics are checked for
variable overrun.
7. FILE_ID.DIZ will only be checked if allowed by
System Config setting.
20. FIXED - "*1" CMD KEY (Edit Files)
1. File name change will no longer allow renaming a
file if the new file names exists in the upload or
download path.
2. The Filesize limit as been increased to allow for
a maximum of 1.9 Gigs. You now also have the choice
of updating with the actual file size or entering
whatever you like up to the 1.9 Gig limit.
3. You may now interactively edit the file description.
4. Changing the user name or number now reports an error
if the user does not exist.
5. Changing the upload date of the file will not allow
entry of a date beyond the current date.
6. The number of downloads has been increased to allow
up to 2147483647.
7. The modify extended description option has been
revamped. If one exists, you will first be asked if
you would like to delete it, if one doesn't, you will
be asked if you would like to create one. If you
decide to keep the exisiting one or created one,
you will be taken to the standard full screen message
editor, the old line by line edit mode has been
removed. Existing extended descriptions will be
copied into the message editor for editing. All
message editing option are available for line edit
or full screen edit mode.
8. The file move cmd has been revamped provides clearer
error message.
9. The User Editor option will now display messages if
the user doesn't meet the access requirement and
also default to User #1 if the current owner of the
file has been deleted.
10. All User/System upload statistics are checked for
variable overrun.
- NOTE -
A. While editing the file owner name, the owner name
will be checked against the user name stored in
the user editor. If the names do not match, the
file owner name will be converted to the Sysop name
(User #1). The editor will assume that the orignal
uploader account has been deleted.
B. While updating the file size, if the file does not
exist, you will be asked if you would like to set
the file to offline or request status.
C. Use File_ID.DIZ must now be turn on in System
Config to be able to update or upload the Extended
Description (if it exists).
D. The internal archive viewer will now only attempt
to display files with the following extentions
(ZIP,ARC,PAK,ZOO,LZH,ARK,ARJ). IF the extention is
valid and the file doesn't exist, you will be
prompted to set the file to offline or to request
status.
21. CHANGE - FILE_ID.DIZ File Descriptions are now extended to 99 lines
of text per file.
NOTE:
The way extended description were handled has
been revamped. Prior to this release, every
extended description required 950 bytes of
hard drive space rather the description required
it or not and was limited to 19 lines. This
version now allows up to 99 lines of 50 chars
each and will only require space for the actual
characters utilized plus one byte for every line
in the description. For example: "This is a great
file" would only require 20 + 1 byte or 21 bytes
of harddrive space verses the old minimum of
950 bytes.
22. ADDED - "OB" CMD KEY (User Statistics)
1. Renegade now has built in User Top 10 Statistics.
I recommend that a new menu be created for these
cmds. Menu options are listed below along with
the title of the action performed.
2. Adding ;## will not allow that specific user to
be included in the stats file. Example: A;1
would not all User #1 to be posted in the current
stats screen.
Option Top 10 Result
A High Time Users
B File Kbyte Uploaders
C File Kbyte Downloaders
D Private Message Senders
E Public Message Posters
F SysOp Feedback Senders
G All Time Callers
H File Uploaders
I File Downloaders
J File Points
K Upload/Download Ratios
L Post/Call Ratios
M Top Download Files
23. ADDED - "L7" CMD KEY (File Archive View Tagging)
Used on FILEP menu to allow file tagging when
viewing internal archives. Sames some time from
having to type out the full filename. ;)
24. CHANGE - Added 2 60 character lines to voting editor. This
replaces the 1 line of 65 characters. Now you have
2 lines to ramble on about for your voting pleasure.
25. CHANGE - Moved time bank options from the timebank menu to
System Config, Option E, Cmds X, Y, and Z. This
involved Max Time, Max Withdrawl, Max Deposit.
No longer do you have to list these options in the
options field of each command as they are now hard
coded into Renegade.
26. FIXED - The Color Codes of the SYSOP.LOG file, no longer
bleed from line to line. Now each line will have
it's own apporiate color(s), if color for logfile
is turned on in System Config.
27. ADDED - Option to Messagae Base Editor to Renumber the
QWK Index. This is inplace to ensure each base
has it's own IDX # and there are no duplicates.
This should really only be used if you are
having issues with QWK, or if you don't do a
lot of QWK, to renumber the QWK # to match the
base position number in the editor.
28. ADDED - ALT-S while a user is online will now enter into a
split screen chat mode session. ALT-C still works
the same as before in a line by line text mode
chat session.
ALT-S was previously (Turn SysOp Status Bar ON/OFF),
this cmd has moved to ALT-A.
29. CHANGE - Made RGLNG to compile all strings in one easy swoop.
RENEGADE.LNG needs renamed to RGLNG.TXT for this to
work tho.
---------------------- READ BELOW FOR CHANGES!!! -------------------------
Validation System Changes:
1. In order to save memory, the validation records were moved from
the RENEGADE.DAT file to the new VALIDATE.DAT file. These records
were previously stored as an array of 1 to 26 records taking up
about 3484 bytes of memory when loaded. This array also limited
the number of available validation records to a maximum of 26.
2. Removing the validation records from the array stored in memory
also allowed for increasing the maximum allowed validation records
from 26 to 94. Of course, this changed the range of validation keys
from A-Z to !-~.
3. Since the old new user validation key was logically the letter "A"
(Or first character in the set). The '!' is now the first character
in the set and became the new user validation key. The code has been
internally modified to accept this key as such. So, if you are using
the letter "A" in your scripts or for your auto-validation command,
please change it to the "!".
4. The VALIDATE.DAT file is checked during boot-up for existance and
to ensure that it contains at least the new user validation record.
Available validation keys are also stored in memory for later use
in the validation process.
Validation Editor:
1. The Validation Editor has been completely re-written adding a record
delete, insert and position function. The modify option has also been
extensively modified.
2. The deletion function will not allow removal of the new user
validation record. It will also not allow you to remove a validation
key that is still attached as an expire to key for any users. You
must first delete the expire to key from all users prior to deleting
the effected key from the validation editor. Deleting a key also
removes it from memory and global use.
3. The insert function will allow adding any one of the possible 94
validation keys if it does not already exist. Inserting a key adds
it to memory and is also available for global use.
4. Changes to the modify option:
A. Added a header to the records list display.
B. Added the Validation key to the record. This key can not be
modified.
C. The validation key description can not be modified for the
new user validation key.
D. Added a free form field that will be sent to the user as a
short message at logon. This field should be utilized to inform
the user of the type of validation they received.
E. The SL can no longer be lower then the SL stored in the New User
Record of the USERS.DAT file (Record 0).
F. The DSL can no longer be lower then the DSL stored in the New
User Record of the USERS.DAT file (Record 0).
G. Combined the AR modification and AR upgrade option into one cmd.
H. Combined the AC modification and AC upgrade option into one cmd.
I. Added a field for file point entry (Not implimented).
J. Increased the allowable credits from 65535 to 2147483647.
K. Added menu display for the start menu option.
L. Combined the expiration days/expire to option in one command.
Before, you could actually set one and not other. Expiration
days without an expire to key wouldn't do anything more then
having an expire to key without expiration days. Setting a null
value for one forces they other to a null value as well. You can
not modify these fields for the new user validation record. Why
would you want to expire someone below your lowest value. Also,
you will only be able to attach keys that actually exists. This
Expire To key can not be the same as the validation key
associated to the record you are currently modifying.
5. The position command works the same as it would in any other editor
within renegade.
User Editor:
1. Combined the expiration days/expire to option in one command.
Before, you could actually set one and not other. Expiration
days without an expire to key wouldn't do anything more then
having an expire to key without expiration days. Setting a null
value for one forces they other to a null value as well. Also,
you will only be able to attach keys that actually exists.
NOTE: You must set both the expiration date and expire to key to
null for every user it's attached to should you ever want to
delete a validation key.
Auto-Validation Command:
1. The menu option is checked for proper syntex
2. The level is checked to ensure it actually exists or logs an error.
3. The command will exit and log an error if the expiration days and
expire to fields are not both activated or nulled.
4. This command will exit and log an error if the "Expire To Level"
does not exists.
5. This command will exit and log an error if a user attempts to
validate themselves at the same access level (Checks SL/DSL/AR/AC).
6. This command will exit and log an error if a user attempts to
validate themselves at a lower access level (Checks SL/DSL).
7. The password length is now set to a maximum of 20 characters.
8. Entry of the password is now masked.
9. Incorrect password entry exits and logs and error.
10. If it exists, the file "AUTOVAL" is displayed upon sucessfull
validation. Otherwise, the user message stored in the validation
level is displayed.
11. The sysop window message and sysop log entry has been changed to
display either "himself" or "herself" (Depending on the user gender)
and the auto-validation level.
Validation (Prompted):
1. The validation level selection prompt will only except entry of an
existing level in the validation editor.
2. The command will exit and log an error if the expiration days and
expire to fields are not both activated or nulled.
3. This command will display a message if the "Expire To Level" does
not exists.
4. This command will display a message to the user if an attempt is made
to validate a user at the same access level (Checks SL/DSL/AR/AC).
5. This command will now display both the old a new settings when a
validation key is selected and offer the user an option to continue
with validation using the current level or select another level.
6. The user is now sent the short message stored in the validation level.
Validation (Internel):
1. The level is checked to ensure it actually exists or exits and logs
an error.
2. The command will exit and log an error if the expiration days and
expire to fields are not both activated or nulled.
3. The "Expire To" level is checked to ensure it actually exists or the
option exits and logs an error.
Conference System Changes:
1. In order to save memory, the conference records were converted
from loading as an array of records to load as a single record.
These records were previously stored as an array of 1 to 27
records taking up about 1674 bytes of memory when loaded.
2. The CONFRENC.DAT file is checked during boot-up for existance and
to ensure that it contains at least the general conference record.
Available conference keys are also stored in memory for later use
in the conference system process.
Conference Editor:
1. The Conference Editor has been completely re-written adding a record
position function.
2. The deletion function will not allow removal of the general
conference record. Deleting a conference will also convert the
last conference a user was in to the general conference if it was
the same conference being deleted. Deleting a key also removes it
from memory and global use.
3. The insert function will allow adding any one of the possible 27
conference records if it does not already exist. Inserting a key
adds it to memory and is also available for global use.
4. Changes to the modify option:
A. Added the conference key to the record. This key can not be
modified.
C. The conference description can not be modified for the
general conference.
5. The position command works the same as it would in any other editor
within renegade.
Change Conference Command:
1. Will now generate an error if the menu option is not an existing
conference or '?'.
The following features have been added to RG:
1. Added an option to toggle all AR flags "*".
2. Added a clear fields function. This feature can be accessed by pressing
"$" in the user editor. Any fields that are cleared will be re-asked of the
user the next time they logon. Handy for questionable entries in the user
record.
Internal Message Editor Changes:
1. The total line counter was off by one, fixed.
2. The line editor was originally split into two separate sub menus.
The first menu allowed for general adding of text and editing
along with the importing of text files, attaching files, etc.
If you wanted to edit a line, you had to exit to the second menu.
This second menu also contained some commands that were duplicative
from of first menu. Now, these two menus have been combined
into one menu. All duplicative code has been removed.
3. A number of new user error messages have been added utilizing the
color code or Red.
4. Command changes:
Abort - Will now display an error message if the message can not
be aborted.
Clear - Will now display an error message if the message is empty.
Delete - Will now display an error message if the message is empty.
This command will also display the deleted line and give
you an option to continue or not with it's deletion.
File Attach - Will now display an error message if the user does
not have file attach access. The user is also
prompted as to rather they wish to proceed with
the file attachment or not.
Insert - Will now display an error message if the message is empty
and when the user has reached the maximum lines allowed.
The user will be prompted with the line number to insert
and asked if they want to proceed with the line insertion.
List - Will now display an error message if the message is
empty. Will now ask the user if they want to list the
entire message or allow the user to enter a starting
line number. The listing "Pause" has been changed to
the "Allow Continue" pause.
Dsiable MCI - Will now display an error message if the user does
not meet the access requirements.
Replace String - Will now display an error message if the message
is empty. The user is prompted to continue or
not with the string replacemnt after editing.
Quote - Will display an error message if the user is not
replying to a message. Will also display an error
message when the maximum lines are reached. Corrected
the line number display (it would only justify up to
2 char positions, will now adjust for 3).
Delete Last Line - Will now display an error message if the
message is empty. Will prompt the user to
continue or not with the last line deletion.
Save - Will now delete any empty lines at the end of the message.
Ever notice an empty saved message. This was due to the
fact that a user could just hit the space bar to save one
line of the message. Now, this line is checked for all
spaces and not saved. An error message is sent to a user
that can not abort the message if the message contains no
text. A message can not be saved that contains no text
(Or at least I hope I thought of everything).
Title - An error message is sent to the user if they can not change
the title. This normally applies to non-abortable
messages.
Upload - An error message is sent to the user if they have reached
the maximum line limit.
Replace Line - An error message is sent to the user if the message
is empty. The user is prompted to continue with
the line replacement or not.
will display the PRHELP.ASC file after every 5 keypresses
when the maximum lines have been reached.
? - Displays the new PRHELP.ASC file.
5. If the maximum lines have not be reached, pressing the enter key
five times will display the following messages:
"Enter "/?" on a blank line for help."
The 5 proceeding blank lines will also be removed. This is helpful
for new users.
6. Discovered a maximum character per line difference between the
Full Screen Editor and the Line Editor. This error was actually
with the char count in the Line Editor and has been corrected.
Additional Message Editor Changes:
1. Non-abortable message changes (New User, etc):
A. File attachment not allowed - Attaching a file
would change the original subject of the message.
B. Title change not allowed - The original receiver and
subject should remain the same.
Note: The user can not abort or save a message that
contains no text.
2. File attachment changes:
A. In previous releases, a user with file attachment access
was not warned if they tried to attach a file when a file
was already attached. However, this basically allowed the
user to swap out the file should they attach an incorrect
file. In this release, if a file is already attached, the
attached file will be displayed and the user will be prompted
to replace the file. I took this a step further, a user may
also want to remove the attached file all together. Presently,
there is no option for this without aborting the message.
Therefore, an option has been added for removing the attached
file. In this case, the user is also prompted to change the
message subject. If the subject contains no text, removing
the attached file is aborted.
3. Error messages:
A. I did not feel there was adequate messages to the user as to
certain editor options. So, this area has been greatly
expanded. For example: Pressing "C" to clear a message
when the message contains no text, now informs the user of
this situation rather then nothing at all.
4. Empty messages:
A. In an effort to reduce the possibilty of an empty message being
saved, the following apply:
1. All null lines at the end of a message are deleted.
2. All lines at the end of a message containing nothing
but spaces are deleted.
NOTE: Lines are reviewed in reverse order up to the first
line containing text. The user will not be able to
save the message unless it contains some kind of
text.
5. Title change:
A. In certain cases, changing the title would actually remove
the subject of the message. I believe this error has now
been corrected.
1. File Downloads -
A. If an actual protocol (Like ZModem) was the first protocol
(or record zero), the downloaded file would not have the UL/DL
ratio checked. This was do to the ratio being set to look for
protocol records from [1..200]. Also, the maximum protocols
allowed at present is 120. The above should have been [0..120]
to be correct.
B. For the ratio check, the FindFirst procedure would look for the
file on the harddrive even if the ratio didn't need to be checked.
This procedure was moved to only get the filesize if the ratio
needs to be checked.
NOTE: The FindFirst procedure would allow searching of any type
of file on the hardrive. This has been changed to not allow
searching of Directory, VolumnID, Hidden & SysFiles.
C. In the present version, duplicate files could be added to the
batch download queue. This alpha release no longer allows
duplicate files in the queue.
D. Downloading any file locally would place an entry in
the sysop.log that the DL was successfull, fixed.
E. Adding a file to the batch DL queue will no loner indicate in the
sysop.log that the file was downloaded successfully. Now, it
will either indicate that the file was added to the batch queue or
that an unlisted file was added to the batch queue. Adding a file
to the queue doesn't complete the DL.
F. The ASCII download of a file has been modified. The allow
continue prompt and a pause after the DL has been added.
File download buf fixes/enhancements:
1. The Star procedure would carry the last color to the next
line, fixed.
2. Downloading a file locally would increment various dl statistics,
fixed.
3. Downloading an unlisted file locally will now prompt the sysop
or user for a path to copy the file to (Like a regular download
currently does).
4. The copy command for local downloads, local unlisted downloads
and copy from CDRom now gives more detail as to the status of
the copy both to the user and sysop.log.
5. Viewing a text file will now indicate that it was viewed vice
downloaded both to the user and sysop.log.
6. Attemtping to view a text file that is missing will no longer
increment the DL statistics.
7. The system should no longer allow downloading or uploading of
batch files locally. It should also no longer increment DL/UL
statistics for batch transfers.
8. The user record was saved everytime a file was selected for
download even if the download was aborted or not completed,
fixed.
9. There was an error in the checking of DL codes against the
returncode when downloading files. The DL codes in the
protocol record are currently strings. This string was being
converted to a numeric value internally even if it were empty.
The string to numeric conversion routine would interpret this
empty string as a value of zero. Since the value for success
was set to a zero also, the system would assume a successful
result. Now, if the DLCode is a null string, it is not compared
against the return code. You may now have to input a zero into
one of the DLCodes in the protocol record for a proper comparison.
This also applies to the ULCodes in the protocol record.
10. Removed an extra file area initialization procedure in the DLX
procedure.
Renegade enhancements/bug fix's:
1. Removed a duplicate procedure for crediting the uploader for a
file that was downloaded by another user.
2. During a batch download, if no DL/Temp log was specified in the
protocol editor, the uploader did not receive credit for the
download. Other system/user statistics were updated though,
fixed.
3. The above credit procedure never worked anyway due to some
calculation errors in the code, fixed.
4. A message telling the user to enjoy the file was only displayed
if the user was charged file points, fixed.
5. Messages to the user and the sysop.log provide additonal
information about the Single Download.
Renegade BBS Enhancements/Bug Fix's:
1. Before the posting of a message or uploading of a file
(Batch/Single), the available drive space was checked to
ensure adequate space exists according to the system setup.
This section of the code was duplicated in 3 places. I converted
this section to a function reducing numerous lines of code and
extra variabes whenever it was utilized in the code.
2. The copy/move procedures are now combined into one function.
Variables for failure, no space and success were required
external to the procedures everytime they were called. Various
messages to the user/sysop.log were also reported external
to these procedures. I also noticed that the move procedure
called the copy procedure if renaming a file was not successfull.
Now, no variables are required externally for the function and
messages to the user/sysop.log are handled internally within
the copy/move function.
3. I noticed that a section of the code for executing file
transfer's was duplicated in 4 places. This has been moved to
a single procedure reducing numerous lines of code and
variables.
4. I noticed that a section of the code for checking the return
code on file transfer's was duplicated in 3 places. This has
been moved to a single procedure reducing numerous lines of code
and variables.
5. The FILES.BBS selected for download during a batch transfer by
the user now contains this starting entry:
"(BBS Name) Batch Download File Listing"
Previously, unlisted files were not written to the above list.
Now, they are with "[No Description Available]" as the description.
Also, files in the batch download queue with a bad path download
path will have "[Bad Download Path]" as the description. These
additions help account for files selected for Batch DL by the
user.
6. The max dos character field in the protocol editor has now been
limited to 127 characters (Was 255). I always thought it was 128,
however I couldn't type in any more then 127 characters on the
command line in DOS. Please feel free to check this out for
yoursele and change you editor accordingly.
7. Removed spaces from the file name written to the protocol file
list for batch downloads.
8. The procedure that reads the success/failure codes and file name
from the protocol temp log has been modified. The starting
position of the code and file name is specified in the protocol
editor. Assumming you set this up correctly, the success/failure
code and the filename are copied to temporary strings. The success
code is compared against the returncode from dos for single
download/upload protocols or the DLCode specified in the protocol
editor for batch downloads and the temp log. This code is not
utilized for batch uploads, the file is simply checked for existance.
The temporary file name is compared against the batch queue for
existance. Since different protocol programs like dsz, etc utilize
different log formats, it's impossible to tell the actual length of
the success code or filename read from the temp log. RG would simply
read each string from the starting position and then chop off any
trailing spaces and compared them as per above. However, with ZM
protocol, the file name ends with ",". Therefore, I changed the
comparison to look for the success code/filename to a String POS
procedure rather then String = String. In local tests (Both Single
and Batch) it seemed to work without issue, we will see? The way it
was handled before did not work with ZM protocol. Hopefully, this
solves it for all others (assuming you set things up correctly in the
protocol editor.
Here's a few things I learned about protocols while editing the
RG code:
1. If you set the option "Codes mean" in the protocol editor
to "Transfer Successfull", you must specify a return dlcode
and or ulcode for single protocols of zero. Zero is hard
coded into the procedure that executes the protocol. A
return code of zero from DOS indicates a successfull result.
Of course, you could also reverse the above and specify
"Codes mean" as "Transfer Failed" and specify all possible
DLCodes/ULCodes as something other then zero.
2. If you do not specify a temp log for batch downloads, no
error checking occurs within RG. RG assumes the files were
downloaded and increments statistics, etc. RG does not create
the temp log, you must add it to the DL/UL command line. You
must also specify the proper file name and status starting
positions within the log for RG to locate them. Please
read the protocol document for a description of the log
entries and then count out the status & filename positions
for the protocol editor.
Here's what you need for the ZM protocol:
1. Specify a Temp Log.
2. Add -lz%L to the DL/UL Command Line to create a ZM
style log.
3. Set "Codes mean" to "Transfer Successfull".
4. Set DL/UL Code 1 as Z, Set DL/UL Code 2 as z.
5. Set "File name" to 22.
6. Set "Status" to 1.
OR
1. Specify a Temp Log.
2. Add -ld%L to the DL/UL Command Line to create a DSZ
style log.
3. Set "Codes mean" to "Transfer Successfull".
4. Set DL/UL Code 1 as Z, Set DL/UL Code 2 as z.
5. Set "File name" to 51.
6. Set "Status" to 1.
3. The temp log is deleted by RG automatically, if you need
or want a permanent log please specify a UL or DL Log.
NOTE: I realize some of you may know all there is to know
about protocols and how they are handled by RG. However,
some do not. Remember, if you do not specify all the above,
your files will be transferred without error checking and
statistics will not be updated. Of course, you could forgo
the above setup and RG will assume all files tranferred
successfully.
4. Using the above setup may or may not work with currently
released versions of RG or all external protocol programs.
Ok, one minor change, only use the lower case 'z' for the batch dlcode, not
the upper case "Z". The upper case 'Z" is for batch uploads and RG doesn't
look at the ULCode for batch transfers. Again, use the lower case 'Z" only
for the batch dlcode.
Renegade Bug Fix's/Enhancements:
1. Batch uploaded files would normally be moved to the file area
selected by the user. However, if the system was setup
to utilize *.DIZ files and the uploaded file contained a *.DIZ,
the file was moved to the current file area regardless of the
area selected by the user, fixed!
2. Added a sysop.log entry to indicate that start and end of scanning
the protocol temp log for downloaded files. These entries were
also added for the start and end scanning of the BATCHDL.DAT if the
temp log is not being utilized.
3. If the protocol temp log is being utilized, an entry was made to
the sysop.log that the batch download failed. This has been
changed to indicate that the file or return code wasn't found.
Example SysOp.Log For Batch Downloaded Files:
(If protocol temp log is utilized).
Start scan of "BATCH6.LOG" for batch downloaded files.
File not found: TEST.EXE
Return code not found: FILELIST.EXE
Batch downloaded: PKZIP.EXE
End scan of "BATCH6.LOG" for batch downloaded files.
NOTE: The above changes should assist in locating errors
related to inproper protocol file name and status position
configuration.
(If protocol temp log is not utilized).
Start scan of "BATCHDL.DAT" for batch downloaded files.
Batch Downloaded: TEST.EXE
Batch downloaded: FILELIST.EXE
Batch downloaded: PKZIP.EXE
End scan of "BATCHDL.DAT" for batch downloaded files.
4. If the user does not have enough time left online to complete
a batch download they will be taken to the Batch DL Edit
options (Clear, List & Remove).
5. If the filesize of an uploaded file were zero, the file would be
awarded a file point, fixed (Example: OffLine Files).
6. If a file does not exist in the upload path during a local upload
the user is prompted to make an offline entry. Previously a message
was displayed before this question indicating that the file did
not exist in the file directory. This has been changed to indicate
that the file does not exist in the upload path. Also, there
was no previous warning to the user that the file already exist in
the file listing. A message has now been added indicating that the
file exists in the file listing. (Note: A duplicate entry will be
added to the *.DIR file if the user selects "YES");
7. If a %F is utilized to pass the file name to DOS, it is checked to
ensure it doesn't exceed the maximum DOS char length. Only files
up to this point are passed to DOS for processing, anything past
this point in the Batch queue is not. I added a sysop log entry
for the first file in the queue that exceeds this length. I did
noticed that this process is only utilized for batch download
transfers and may be required for the other transfer options.
8. Information about the name, size and download time are now
displayed to the user about the Batch Download File Listing. The
total new download time is also displayed to the user.
9. The filesize was previously stored in the *.DIR file in 128 Byte
blocks. There was also a field used to store the remainder or
bytes left over between 0-127. This remainder was not fully
implemented throughout the code to account for the total filesize.
This impacted CPS rates and info displayed to the user about the real
filesize and estimated download time. I took a real hard look at
this storage method and remembered that at one time, WWIV used this
storage method for internal protocols. Up till now, alot of extra
code was required to convert the filesize to this dual storage
method and alot was required to convert it back. I saw no reason
to continue this method. Now, the filesize of a file contained
in the *.DIR is stored as the actual filesize (LongInt Value). All
code related to this back and forth convertion has been removed.
I provided an extra informational line for the 128/1024 block size
that will be displayed when a file is selected for download.
10. The date was stored in the *.DIR file as both a longint value in
seconds and the number of days since originally uploaded. Once
again, this required alot of extra code to convert back and forth
and was only utilized in 2 places. So, the number of days' since
uploaded has been removed and is now calculated internally as
needed.
Renegade Updates/Enhancements:
1. ZM protocol will default to "/" vice "\" as directory path
separators for *.log entries. There is an option to convert
this on the command line, however some sysops don't always read
the documentation. So, I added an internal conversion routine to
look for this separator and automatically convert it.
2. The message after adding a file to the batch download queue will now
display the cumulative total of file points along with the number of
files and download time.
3. During a file download, the ratio of Uploads to Downloads is
checked. Although the ratio check of the total K bytes included
the current file being downloaded, the ratio check of the total
files did not include the current file being downloaded, fixed.
Renegade Updates/Enhancements:
1. A file can no longer be copied onto itself or moved to the same
directory it currently resides in.
2. In local mode, you must have CoSysOp access to move or copy an
attached file or file selected for download.
3. I noticed that download and upload statistics were displayed for
batch transfers even if "Log-off after file transfer was selected",
but not for single download or upload transfers, fixed.
4. Some items selected for download went thru the DLX procedure and
some went directly to the send procedure. Alot of extra code and
variables were required for the send procedures everytime it was
called. Now, all download requests go thru the DLX procedure and
then to the send procedure. With this change, file downloading
can be tracked for all downloads thru the same statistcal process.
This includes, File attach, QWK, Unlisted and user archive.
5. All regular downloads were checked to ensure the user met all
security requirements, ratio, etc prior to the download. However,
if a user was exempt from certain ratio checks, the user was
charged anyway for the download unless the file area was marked
as No-Ratio. This applied to users flagged as No UL/DL Ratio in
the User Record, No UL/DL Ratio in the System record, etc.
6. You will now be asked if the file exists on a CDROM for unlisted
downloads. This will alow for faster file transfers since the
file is copied from the CDRom to the Temp Node Directory for
download.
7. The default file name for extracting text from a message has been
changed from "MSG.TXT" to MSG
have the option of changing this to whatever you like at the
prompt.
8. For Offline mail transfers, the bbs will no longer attempt to copy
the WELCOME, NEWS or GOODBYE file if they path to the file is
blank.
Renegade updates/enhancements:
1. Fixed a bug related to the length of the dlcode/ulcode in the
protocol editor. The maximum length of this string is 6 chars.
2. No process was in place to prevent ul/dl statistical variable
overrun, fixed.
3. The color from the auto-logoff countdown procedure carried the
last color to the next line, fixed. This would only be noticed
if the user escaped or cancelled the auto-logoff.
5. The color from the scaninput procedure carried the last color to
the next line, fixed. I noticed this with the batch download file
remove command.
6. Since files added to the batch downloaded queue are listed as such
in the sysop.log, it only made since to list files removed from
the batch download queue in the sysop.log as well. An entry to
the sysop.log is also made when the batch download queue is
cleared.
8. The uploader name/date and the message to the user to continue a
resume file did not redisplay the file name when wrapped to the
next page while utlizing the file list command, fixed.
9. I think I finally have some issues corrected with the file
listing display. Every now and then an extra file area
header would display when not needed. Also, sometimes the line
counter would be off by one or two lines and push the file area
header up one or two lines or completely off the screen. I also
noticed a line feed missing when the listing was aborted or
exited normally.
Renegade bug fix's/enhancements:
1. Due to space limitations, the file listing display will utilize
bytes or kbytes depending on the file point settings in the
system configuration. To be consistant, this process is now
also being utilized for the file size displayed when a file is
selected for download.
2. When a file is selected for viewing, the user will be cautioned
that the file is not checked to ensure it is an ascii text file
and then asked if they would like to continue.
3. The file listing download and add batch prompt has been cleaned
up. It would formally allow input of '-' by itself or the '-'
proceeding or following a file number and alpha characters. The
input of an invalid file number will now display a message to the
user.
4. Adding a file to the batch queue from the file listing display
will now display all the file information related to that file.
It will also now properly check the file to ensure it is ok to
download and send it thru the proper ratio checks. I have to
admit that this was an oversite on my part when I added the
ability to select a file by number. Basically it now goes
directly thru the DLX procedure vice being added directly to
the batch download queue.
File download bug fixes/enhancements:
1. I fixed an issue with certain commands accessed from the
file listing menu. For example, the file edit command would
allow you to edit whatever file you selected, but when you
returned to the file list, it wouldn't return you to the
proper record. This appears to have been a long standing
issue and I may have additional commands to correct that might
be added to this menu.
2. I added a new command to the file listing menu. This command
allows you to flag a file to edit like the batch flag or flag
download. The command is "L8". You can select by number or
range and go back and forth thru the range like you could if
you were using the regular file edit command. You must have
File Sysop access to utilize this command.
----[ Changes in v09-30.6/DOS ]----
1. FIXED - The Auto Time Display Flag (A) in the Menu Editor
would not toggle on or off, this has been corrected.
The Menu List Number and Menu Number was right
justified to make for a better looking display and
"(C)ommand editor" was added to the Prompt.
2. CHANGE - In preparation for converting the Email System over
to have the same look and feel of the message system,
the following commands were changed in the Out Going
Mail command:
(P)revious was changed to (-)Previous
(R)e-read was changed to (A)gain
3. FIXED - The File Editor would give the option to delete
all data files associated to an area when that
area was deleted. The problem was that it would only
delete the *.DIR file and not the *.EXT or *.SCN files.
The File Editor would also give the option of copying
the data files over to the new directory when the "I"
option was toggled in the File Area Flags. The problem
was that it would only copy the *.DIR file and not the
*.EXT or *.SCN files, these have both been fixed.
4. CHANGE - All extended file descriptions were previously saved to
one file (EXTENDED.DAT). This has been changed so that
all file areas have their own individual *.EXT file.
Should the EXTENDED.DAT file ever get corrupted, you could
have possibly lost all extended description for your entire
file area. This will also help make it easier to add
code for actually deleting the extended description for
any files that you delete from a file area. Previously
extended file descriptions were not actually deleted, only
blocked out from access taking up hard drive space. That's
969 bytes for every file!
5. FIXED - The file move command still allowed moving a file to file
area 0, which doesn't exists, fixed.
6. ADDED - Internal FILES.BBS importer. New Menu CMD Key "FC" allows
the scanning of all file areas configured inside of
Renegade to import descriptions from anything that lists
a FILES.BBS such as shareware CDs. Also, instead of
loading Renegade, load Renegade via cmd line -F to start
the FILES.BBS importer without loading Renegade itself.
7. FIXED - All Menu Editor related bugs to adding/removing menus.
8. ADDED - Option to allow the use of multiple "quote headers".
With this option, you will be able to change the
quote header on each base. This will default to what
ever is in the RENEGADE.LNG file.
9. ADDED - Option to allow the use of multiple "read prompt" menus
per message area. This will allow the SysOp to make
seperate menu cmds for each base if need be. This is
mainly used if you want seperate conferences for
certain bases or certain access and cmds for certain
message areas.
10. ADDED - Option to allow the posting of a text file PER message
area each time a user posts. Yes, we know this will
get old, but it will allow say a posting of "rules" to
be displayed to the user at each posting thus washing
your hands of a matter when the user says he has no
idea he wasn't allowed to do something in a certain
message area.
11. CHANGE - Extended the length of the message posts. (ie:
email/public/private) to 500 lines max. The current
default was set to 200, but you were getting no more
than 50-60 depending on the amount of memory that was
installed into the computer.
12. UPDATE - Removed most system menus to external string files.
Also added a compiler for these new string files.
This will allow the use of the software in any
language and allow faster access to the menus than
they were before. We will shortly be pulling all
strings and messages from within the code and
making them external.
13. ADDED - New CMD Keys QQ - Random Quote Generator Display.
Compile your quote text file with RGQUOTE and
make a menu cmd and place the QUOTE file name
in the options field to display the quotes one at
a time.
14. ADDED - Toggle under system config to turn the above
feature ON or OFF at logon. This works much like
the AutoMessage feature works. Must have LGNQUOTE
compiled and in the DATA directory for this option
to work. LGNQUOTE is compiled with RGQUOTE.EXE.
15. ADDED - Option in Message Base to turn ON or OFF tagline
addition to the message you have just posted. For
this option to work TAGLINE.TXT must reside in the
DATA directory and be compiled with TAGLINE.EXE.
16. ADDED - Auto Random quoting at the end of messages. E-Mail
Local, and Echo Message areas will automatically
have a quote added at the bottom of the message.
This can be toggled ON/OFF on each message base
and now EMAIL.
17. ADDED - The E-Mail Subsystem has been added to the Message
base editor. This will be record 0, which you can
edit certain features and strings.
18. ADDED - Option to add to quote file at logon via system
config toggle. This will create a file called
*.NEW (Taking on the firstname of whichever
quotefile a quote was added to.) and then you
can then copy new quotes over into the correct
file and recompile it. Please note, you MUST
erase this file when you are done with it or it
will continue to append to the end of the file
and take up space.
18. ADDED - Option to add a quote to E-Mail or a Message is
now asked after the message is saved. This can
be toggled ON/OFF in the message base editor.
19. FIXED - Standardize the SysOp.Log File - The log file
was cutting off a user if they logged on around
midnight of that night. They were either tossed
into the night before or the current one. This
has no been corrected to be sorted into the
correct file.
----[ Changes in v06-30.6/DOS ]----
1. FIXED - /S command in teleconference not displaying the
correct information (or any actually). This has
now been corrected. Basically fixed all commands
in the teleconference to work properly. Removed
all 0-, 5-, 1- and such debugging code as well.
2. FIXED - Total Free Space Showing on the WFC Screen is now
displaying correctly up to 999.9 megs.
3. CHANGE - The Menu system is now non-existant as text files.
They have been converted over to DATA files with
a new MENU EDITOR added into Renegade. This frees
up from internal memory and speeds things up a bit.
4. ADDED - Added option under S. System Config, A. Main BBS Config,
K. System Menus. This is where it will tell Renegade
which are the main system menus and that are not allowed
to be deleted. This also plays into the effect of
all the numbered menus now instead of names. The
included Menu Converter will take care of this and
any/all menus you have.
5. FIXED - Annonying "Cannot Load NODEx.DAT file" error.
6. UPDATE - File/Message/Protocol/Event Editors to more closely
reflect the look and feel of the menu editor. Thus,
giving things a more universal look and feel.
7. FIXED - The option to edit the arctype in the File Menu.
8. FIXED - The Shell to DOS in the WFC was a "J" (Not listed) and
renamed it to "D" to conform with the WFC Screen.
9. FIXED - The option for using a "U" to determine if you were
doing anything with batch upload command or batch
download commands compared against a capital "U", the
problem was that the file editor allows lower case
entry of this "U", added and allcaps to the menu were
it compared the two. Didn't change the file editor
to still allow lower case for the options.
10. REMOVE - The option to PRINT SysOp Log files. This command
only printed to the LPT port. Really, who has a
LPT Printer anymore? Command removed.
11. CHANGE - Removed all extra spacing after internal prompts
left. ie: before "Menu Prompt :" now "Menu Prompt:"
12. CHANGE - 200 Menu commands are now allowed per each menu
set. This was defaulted to 100. 200 Should be more
than enough for any users. If you need more, you
need a life! ;)
13. FIXED - Batch Files: Any files left in the Batch Queue after
logoff would not be stored for download after the
next logon to the BBS.
14. CHANGE - Overlays are revamped and the param switch -D for
disabling EMX/XMS and -O for setting the OvrExtraSize
(Default 64K). The -D switch was added incase for
some odd reason an EMS/XMS driver is not detected
and Renegade will not load. By using -D you will
be able to load Renegade's Overlay to DISK and
still be able to access the BBS to correct the error.
14. CHANGE - TOGGLES.DAT file is removed and is added internal to
Renegade. This effects two options. The option of
the access for the laston.dat file needs to be rest
if you changed it. The toggles are all there and
must be reset as a few were added.
15. ADDED - User Editor Option '/' key. This is where you can set
all defaults for a newuser up to answering all the
newuser questions, the autoval is still there for after
these questions are answered. Prior to this update,
you couldn't change anything before a newuser was
validated since they were hard coded in the program.
Anything you do in Rec 0 (Zero) will carry over past
autoval if the autoval didn't change the option.
16. FIXED - Display issues with the protocols. The RENEGADE.LNG file
allowed entry of PROTLIST which displayed a list of
protocols in addition to the PROT*.ASC files or internal
protocols. Either delete the PROTLIST entry from
RENEGADE.LNG or delete PROT*.ASC from the MISC Directory.
You may also now hide protocols if you do not wish a
discription to be displayed to the user.
17. MISC - The internal variable for NODE which should have been
a byte variable was in fact either a word or integer
variable. Reduced file reads when listing protocols
from 3 reads down to 2 reads. This should make things
abit faster.
18. FIXED - When updating the node, a comparison of the Node
number to the Activity was made to set invisible
mode instead of being compared Node to Node. Removed
this since Invisible mode is set at Logon and
via a menu comand.
19. FIXED - The length of the path/filename string for unlisted
downloads was 78 and the length of the string in
the batchdl was 65. Changed both to a length of 52
(40=Path/12-Filename) to conform with other
path/filenames used throughout the file system. A
length of 78 would have been a waist of space since
most dl's are listed.
20. FIXED - The download time is now properly updated when
batchdl's were saved for the next logon.
21. CHANGE - The node activity would report that you were in a
door when uploading files.
22. FIXED - Certain protocols when selected were passed to the
seek/read procedures that were negative causing a
runtime error of 100. This has now been corrected so
that only numbers from zero and above are passed to
these procedures.
23. FIXED - Event Editor - If setting an event to SORT FILES,
this event would never run as the command to SORT
FILES (ie: S) was not a valid option. This has been
corrected.
24. UPDATE - The NEW bulletins displayed at logon would occasionaly
display 0's (Zero) instead of just the bulletins that
were actually updated since your last logon. This has
now been corrected. Leading zero's were added to those
bulletin numbers below 10 to make for a better looking
display when listed.
25. ADDED - Added Menu Option TD to erase BBS's from the BBS
Listing. This will be listed in the updated
MENUCMD.ASC file in the next release.
25. ADDED - Added Menu Command Option (N.) to each menu command.
This command will update the node activity for each
command. If someone is playing LORD, you can set N.
to "Playing LORD" in the same command as your batch
file is placed. No more need to use the NW command
before and after a cmd is run to update the
multinode information to Renegade's Who's Online.
********** NOTE ***********
Activity Field is now able to be a MAXIMUM of 50
charcters long.
26. ADDED - New Toggle Option. Users will now have the option
of answering a question to be able to logon the BBS
after forgetting their password. This can be
toggled ON/OFF via the toggles menu. Once the user
correctly answers the question, they then will be
able to set a new password before logging onto the
BBS. A Mininote to the SysOp will be sent as well
as a sysop log file line will be written.
27. ADDED - Sysop Logging for the User Lister and Sysop Logging
for Todays Callers. Just to show what the user
was doing while online. (Nice to know once in a
while that a command is being used.
28. FIXED - The File Sort Routine was setup to access File
Area 0 which Doesn't exist, so this was changed to
File Area 01.
29. FIXED - Logoff time was not properly being passed to the
SYSOP.LOG file. Now, the sysop.log file will show
user logon time, logon node number, what they did
while online, and logoff time of that node.
30. CHANGE - Logoff entry in Sysop.Log now indicates Node Number.
31. FIXED - The Forgot PW question will now redisplay and can
be edited without retyping the whole damn thing! ;)
32. CHANGE - The User List can now be viewed a number of different
ways. You can view the list via choosing several
different options to sort it by. Location, Sex,
State, etc. Or you still can view it as it was for
the last 1000 years. ;)
33. CHANGE - File Area Toggle Scan Flags (Command)
Removed the "Q" for quit, pressing
this command and the command no longer scrolls on the
screen like it did when the "Q" was required.
Reduced the actual toggling of the scan flags from 3
separate processes down to just one procedure.
Pressing "-" alone will now exit vice scrolling the
command.
Reduced the input string from 15 down to 9 chars
since the max range that can be entered is xxxx-xxxx.
Added an input background.
34. CHANGE - File Area New Scan Date (Command)
Removed the extra Line Feed from RENEGADE.LNG File.
Added error checking for date entered past the
current date.
Reduce the input string from 160 down to 10 chars
since the max length of the date is xx/xx/xxxx.
35. ADDED - File Tagging to the File areas. File Names can now
be downloaded or added to Batch via a simple number
instead of typing out the full filename each time.
Batch downloads can be downloaded via XX-YY cmd.
ie: 4-7, would download files numbered 4, 5, 6, 7.
36. ADDED - AR Flags - You now have the option to press ? when
editing user AR Flags. ARFLAGS.ANS/.ASC is to be put
in the MISC directory and is used by the SysOp so
they know which flag is for what and who. Just a
simple little reminder. Hope this helps some.
37. CHANGE - File Points are now ranged from 0-999 to more closely
reflect an acutal file point system. I just can't
see someone having to pay 32000 points for a file. ;)
38. CHANGE - At logon, you will be prompted to download files
in which you have left in your batch queue after
last logoff.
39. CHANGE - File Prompt Header - The File Prompt header will
redisplay at each screen. No longer will you have
to wonder which file area you are in. This gives
the file system a nice rounded out look as well.
----[ Changes in v05-19.4/DOS ]----
1. CHANGE - Updated Copyright notice to reflect the new year.
2. FIXED - Slight Memory leak in v01-10.4/DOS. This in turn would
cause Renegade to eventuatly eat up all availble memory
in a few years of use if the computer was never rebooted.
3. ADDED - /F MENUCMD to disable MCI Codes from displaying inside
of a text file. This MENUCMD compliments the -F CMD Key.
4. ADDED - Option /M when entering a message to turn on or off
using MCI Codes per message.
5. ADDED - Added option to allow the SysOp access to the amount
of time to give each timeslice. This may help some systems
in which Renegade hogs a lot of CPU (ie: Windows 2000). If
you do not have much of a problem with sluggish performance
it is suggested that you leave this option at the default
setting. (10-40 optimal setting)
[System Config -> D. System Variables -> V. Time Slices]
6. FIXED - Slight problem when displaying "NEW" bulletins to users
when they first logon. Renegade would display 22 of them
across, then start putting each new one on a new line.
7. REMOVE - Removed "Digiboard" support in the codebase. Really,
who would use one of those now-a-days anyways with a DOS
based BBS? If this is an issue for anyone, please e-mail
us and we'll take care of it for you.
8. ADDED - Added option to System Config to post the BBS's telnet
URL. This is under System Conifg, Option A Main BBS Config.
Just a cosmetic add, as before you could only type in a
telephone number for the BBS. Now you have a choice. ;)
9. ADDED - Added ~TN MCI Code to BBSME.ASC/ANS and BBSMN.ASC/ANS
to reflect the new Telnet address line to the BBS list.
10. CHANGE - Changed the follow command keys to reflect new BBS
list format change.
{ See Below for list of CMD Keys }
OB : Changed to CMD Key TV {short view of bbslist}
OA : Changed to CMD Key TA {Add to bbslist}
Added the following CMD Keys to be able to have more
control over the BBS List.
TA : BBSList Add {formally CMD Key OB}
TE : BBSList Edit
TV : BBSList Short View {formally CMD Key OV}
TX : BBSList Extended View {formally CMD Key OV}
{ Updated MENUCMD.ASC file to reflect these changes }
11. CHANGE - BBS Listing is now scriptable. This means that you
now can add just about any question for the BBS you wish.
MCI Codes reflect the different questions (1-8) to display
when a user views the BBS List.
{ Added BBSLIST.SCR file to reflect this update }
*** BBSLIST.SCR MUST BE IN THE \BBS\MISC DIRECTORY ***
12. ADDED - %xA / %xB / %xC / %xD / %xE / %xF for extra definable
sysop strings in the BBSLIST.SCR file.
x:= to the following values.
a = 8 chars / b = 30 / c = 30 / d = 40 / e = 60 / f = 60
Also added %S2 for and extra line of descrition of the
BBS. Changed the way it stores the SOFTWARE. It's all
in capital letters now. Also, added that if can't find
BBSMN.ASC it will echo back that in the sysop log and
just print out the bbslist.sysopname, etc and proceed.
13. ADDED - BBS*.ASC New MCI - ~WS (website) ~RN (Record Number)
14. CHANGE - -TG and -TS command line loaders for Renegade are
now simply just -T for all telnet connections. Unless
you are using COM/IP as your emulator which the command
line changed to -TC (ie: renegade.exe -n4 -tc).
16. UPDATE - The Official Renegade Home page is now located at URL:
http://www.renegadebbs.net
17. REMOVE - Removed the "Moving xx to xx" from writing to the
SYSOPx.LOG file. Saved some clutter there. ;)
18. FIXED - The Telnet URL will now save correctly in the
system config and not constantly erase itself.
Will have to set for each node.
19. CHANGE - Bulletins now compare Time and Date of Files vs Time
and Date of last logon to display as NEW.
20. CHANGE - NODE*.ASC instead of showning a '-' when a user isn't
on a node it will echo back the node number for ~NN, then
for ~AV it will display 'Y'. MCI Code ~AC is a 20 Chars
String and ~UN is a 36 character string.
21. CHANGE - The Caller ID switch is now -ID instead of just -I
Also -IP puts the IP (if present) into the Caller ID field
in the User Editor and anything to do with Caller ID.
22. ADDED - The String Editor is now removed from Renegade. All
strings within the editor are now EXTERNAL. We will
slowly be removing all strings from within Renegade's
code and making them external for easy editing! Also
created DUMP to "dump" the STRING.DAT file to the
editable language file. (data\renegade.lng)
----[ Changes in v01-10.4/DOS ]----
1. FIXED - Bulletins - Now will correctly display if a bulletin
is new or not to the user per call and are sorted
in numerical order. ie: (2, 7, 19, 22) instead of
(22, 2, 19, 7).
2. ADDED - (-T, /T) Toggle. This will inturn toggle all baud
rate speeds to show as "TELNET". This also disables
most comm routines relating to logoffs. With -T
added to loading Renegade, it will no longer pause
for a set number of seconds before the BBS will
hang the user up. DO NOT use this command on
dialup nodes! Use this on TELNET ONLY NODES!!!!
3. REVISED (-T, /T) (-TG, /TG) (-TS, /TS) Load Toggle.
This will inturn toggle the MCI Code ~SP in
the last caller ANSI/ASCII to show 'BAUD'.
(-T, /T) will do the hang-up procedure on a
regular log-off for COM/IP. (-TG, /TG) & (-TS, /TS)
will bypass the passing of the ATH0 hangup string
to the fossil/com port and will work with GameSrv
or Synchronet respectivly. This fix's issues of
slow hangups while doing a telnet session.
DO NOT use this command with dialup nodes!
3. FIXED - Fixed Toggles Menu and added warning screen about
the use of certain toggles and what else should be
changed or certain users may not be able to log
back on to the BBS. (ie: If you have the BBS
check for birthday's and have the toggle to ask
for the birthday at new logon set to NO, the user
will not be able to logon the BBS since he will not
have a birthday set in the user record.)
4. FIXED - Added Time Slice Routines to certain functions in
Renegade where it awaits for a user input. This
SHOULD fix some slow downs while running under
some version of Windows.
5. FIXED - Fixed Memory problems with downloads and swapping
Renegade out of memory which in turn caused some
doors not to function.
6. CHANGE - Changed all file sizes in Renegade to now show as
Kilobyte (KB), and Megabytes (MB) instead of just
bytes. (ie: 64,564 bytes NOW DISPLAYS AS 64.5 KB)
Also changes to the WFC Screen to reflect this.
7. FIXED - Fixed upload Limit of 8.1 MB. Now, will show
files with sizes up to 1.9 GB.
8. FIXED - Fixed the AR, AC Flags [- OF -] toggle command to
NOT be case sensitive.
9. ADDED - MCI Code telnet - This MCI Code shows the users speed,
ie: Telnet, Local, or Actual Baud Rate.
----[ Changes in v11-26.3/DOS ]----
(Nov 26, 2003)
01 - Made NEWUSER Questions Configurable. Only questions that are
required are the User Handle, and User Password. These toggles
will be kept in a file called TOGGLES.DAT in the DATA directory.
If this file is deleted, Renegade will remake the file with the
defaults. (System Config, N - New User Toggles)
02 - Extended FILE_ID.DIZ Description length from 10 lines to 20
lines. Read UPDATE.DOC (VERY, VERY IMPORTANT!!!)
03 - Fixed: When a user was downloading or uploading a file, Renegade
still showed the user was able to be paged to chat.
04 - Fixed: Bug in Renemail which wouldn't allow importing of netmail
from a FrontEnd Mailer.