Category : BBS Programs+Doors
Archive   : TONSMOD.ZIP
Filename : UPDATE50.DOC

 
Output of file : UPDATE50.DOC contained in archive : TONSMOD.ZIP
ASR 1.50:
Totally redid the user interface. Configuration, work screen, everything
is now full screen. Much better than the command line interface, in my
opinion.

ASR 1.40:
Fixed problems with the wildcard support, sometimes a file would be
"de-string'ed" more than once. New scheme has been implemented, and this
is now not a problem. Also, the "?" wildcard character was not supported.
Now it is.
Cleaned up a problem with ASR not working properly when you tried to
use a strings.txt file or source files that were not in the same directory
as ASR with wildcards (and some other occasions). Fixed.
Generally cleaned up the code. ASR should run considerably faster now
when you are running it on multiple files with wildcards.

ASR 1.32:
Added WildCard support for source code files (some known bugs in this,
none really significant).

ASR 1.31:
After fixing the slash bug, decided that we saw the occurrence of this
slash command:

"\x1b"

or the escape character enough to warrant conversion to a form that ESM can
understand when STRINGS.TXT is converted to STRINGS.DAT. If you turn the
"\x1b" conversion on in the configuration, then all occurences of "\x1b" in
strings will be converted to the ESCAPE character, "" or ^[. This does
exactly the same thing as "\x1b" does in WWIV source code. This option will
take effect even with SLASH checking on, so if you want to convert this
particular code but not mess with other parts of the string, feel free to
leave this on.

ASR 1.30:
added Slash checking. Refer to ASR.DOC for more information under
configuration.

ASR 1.21beta:
When you start up ASR, a data integrity check will be performed on the
ASR.EXE file. If the file has been tampered with in any way, a message saying
that the data integrity check failed will be displayed, but the program will
still execute. If the check fails, it could be due to one of several things.
The most common reason that the check might fail would be that the
ASR.EXE file has been compressed in some form or another by a Executable File
Compressor such as PKLITE (tm) or LZEXE (tm). If this is the case, then you
can choose to ignore the error. If you have not compressed the file, then
it is also a possibility that someone has compressed it somewhere along the
way before you got it. If you can, try and see if it is compressed by using
a utility such as CHK4LITE (tm) that comes with PKLITE to see if it has been
compressed. Otherwise, your best bet is to assume that the file has been
tampered with, be it benign or not, and you are advised not to use the file.
It could contain a virus, trojan horse, or just have been modified by a person
who is handy with messing with HEX editors. You can obtain a qualified and
updated version from my BBS, which is listed in the main documentation, or one
of numerous other BBSs.

Good luck!

Ellrond, #3 @9987 WWIVnet


  3 Responses to “Category : BBS Programs+Doors
Archive   : TONSMOD.ZIP
Filename : UPDATE50.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/