home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
bbs
/
adlog225.zip
/
ADLOGO.NEW
< prev
next >
Wrap
Text File
|
1992-04-11
|
26KB
|
558 lines
AdLogo - History File
In reverse order.....
04/10/92 10:58
--------
AdLogo v2.25
-- ADLOGO now has the ability to insert into a GIF an OverLay
image. This OverLay can be an added advertisement for your
system. This feature was added due to there are only selected
GIF viewers that allow viewing of the GIF Comment. For Details
on this new feature, download ADGIFSET.ZIP from our support
BBS. (This file is only available for REGISTERED Sysops)
-- Coming in the next release: ADLOGO as it stands now WILL allow
support for Multi-Node Systems running with a CD-Changer.
The next public version of ADLOGO will have enhancements
added for sysops running with this kind of setup to better
support a multi-disk changer across multi-nodes!
-- Publicly Released as ADLG225.ZIP
04/04/92 15:23
--------
AdLogo v2.24ßeta
-- Ever since v2.10ßeta, my Support/ßeta site has reported
numerous times that ADLOGO would fail to process properly.
When executed, ADLOGO would simply 'FLY THRU' and the down-
load was aborted, DSZ stated 'File not found'. At first, we
thought the problem may have been caused from his machine.
This was not the problem! Also, we we're unable to EVER
duplicate the problem, no matter what we tried, ADLOGO would
ALWAYS work when WE tested it! Told my ßeta site to go back
to using v2.01 and see what happen. No problems reported.
Ever since the code was added to ADLOGO for Xmodem transfers,
this is when the problem started. Was able to locate the
'Bug' and cure the problem!
-- Version not released to the public
04/03/92 22:52
--------
AdLogo v2.23ßeta
-- Added code for better error-trapping. Hopefully will be able
to locate a bug that has been reported since v2.10ßeta
-- Version not released to the public
03/30/92 23:30
--------
AdLogo v2.22ßeta
-- Change the max. command line for DSZ under a Xmodem transfer
from a total of 90 chars to 120.
-- When ADLOGO is in the XModem transfer mode, just before ADLOGO
passes control over to DSZ, ADLOGO will display to the local
screen.. ADLOGO: Xmodem Transfer Mode.
-- I know, only 45 minutes since the last complied time, but I
was bored! <grin> We are now very near to the final release
of ADLOGO v2.xx. Should have the docs in order by April 5th.
for the public release of ADLOGO with the XModem transfer mode
installed.
-- Edited the code for ADLSETUP.EXE for the new .CFG file format
for the addition of Xmodem Mode to ADLOGO. ADLSETUP will create
this new DSZ partcial command line automatically which is a
general default for almost all systems.
-- Not released to the public
03/30/92 22:45
--------
AdLogo v2.21ßeta
-- Bug reported that none of the Xmodem protocols would work
when sending files to the user. DSZ displays 'Directory or
File not found' when both the file and directory WERE there!
Fixed!
Thanks Glenn Holk
-- Not released to the public
03/30/92 15:15
--------
AdLogo v2.20ßeta
-- Change the User output display on reigstered versions.
Now, if running a registered version, the ADLOGO Title lines
are no longer sent to the user. Instead, the line:
'One moment please, porcessing your transfer request...'
is displayed. Now, ADLOGO will look as if it's a part of
PCBoard!
Thanks Ed Maroon
-- Not released to the public
03/27/92 23:55
--------
AdLogo v2.10ßeta
(Change in the .CFG file is required!)
-- Added code to ADLOGO for the support of Xmodem transfers.
This includes XModem, 1K-Xmodem (Old YModem), & 1K-Xmodem/G.
Instead of ADLOGO creating the ADLOGO.LST, exiting and the
PCBSX.BAT (or PCBSO.BAT, PCBSF.BAT) calling on DSZ, ADLOGO
now calls on DSZ internally for the XModem protocols ONLY.
Six (6) batch files for PCBoard are now included in the ADLOGO
archive:
PCBSC.BAT & PCBRC.BAT for Xmodem CRC/CheckSum
PCBSO.BAT & PCBRO.BAT for 1K-Xmodem
PCBSF.BAT & PCBRF.BAT foe 1K-Xmodem/G
To install, first edit the three (3) PCBS?.BAT files. The
changes necessary are the PATH to the ADLOGO.CFG file and
the TEMP directory on the DELF command line. No changes to the
PCBR?.BAT file are needed. Next, go into PCBSetUp and
make XModem(CRC), 1K-Xmodem, & 1K-Xmodem/G as a TYPE 'D'.
Also, make sure that for all external protocols using ADLOGO,
LOCK LINES and PORT OPEN are both set to 'N'. Completely delete
the XModem(CheckSum) line as DSZ will AutoSelect CRC or
CheckSum error checking when using the standard XModem
protocol.
Now insert before the last line of the .CFG file, the
following:
handshake both pB4096 estimate 0 SPEED
This is the DSZ command line for ADLOGO. ADLOGO will add to
this line the 'port #' and the transfer mode ('sx', sx -k', or
'sx -g -k'). In this new line, you may change the pB4096 to
a figure that you may have changed in the PCBSZ.BAT file to
fit your system. Also, the same is true for the 'handshake'
parameter. HOWEVER, you MUST have the 'estimate 0 SPEED' at
the end and 'SPEED' *MUST* be in CAPS.
This feature of ADLOGO is NOT crippled on UNREGISTERED
versions.
-- Not released to the pulbic
03/26/92 15:55
--------
AdLogo v2.01
-- Some of the ADLG200.ZIP archives did not have the DELF11.ZIP
file included. Unzip DELF11.ZIP for the DELF.COM file which
is need to delete ALL files from the TEMP directory.
-- Sysop reported a bug where ADLOGO would go into 'La-La Land'
when trying to process certain .GIFs. Found that these .GIFs
that would make ADLOGO go into an endless loop, were "poorly"
made, and contain about 1k of extra padding at the end of the
GIF. Fixed!
Thanks Glenn Holk
-- Released as ADLG201.ZIP
03/22/92 17:15
--------
AdLogo v2.00
(Change in the .CFG file is required!)
-- Complete Re-writing of the code from scratch! Some of the
new enhancements include:
» Much faster processing!
» BIOS or DIRECT Screen Writes Toggle
* » Added .ARJ file format Support
* » Added .GIF file format Support !!!
* » Added ablility to insert an AD file into an ARJ or ZIP
* » CallersLog Logging can be toggled ON/OFF
* » Added toggle to copy ANY file format from MATHCED DRIVE
to TEMP directory for less Network traffic and faster
transfer rates
» Writes to CallersLog the total amount of time it took
8 AdLogo to process the transfer request
» ANSI output thru the com ports has been added
» And more!!!
(* = Registered versions only)
-- Complete Re-Write of ADLSETUP.EXE to follow the new format of
the ADLOGO.CFG file. Also now includes help screens!
-- Complete Re-Write of the AdLogo Manual! (Thanks Brian!!)
(I hate writing docs!)
-- DELF11.ZIP is included in the ADLGxxx.ZIP archive.
The DELF.COM file is now required to remove all files from
the TEMP directory. DELF.COM was written by the author of
ZipLab Plus. DELF11.ZIP is only included as a convenience.
-- Released as ADLG200.ZIP
03/19/92
--------
Adlogo v2.00ß-v2.22ß
-- These versions were the proto-types for the final release
of v2.xx of AdLogo and were never released to the public.
03/01/92
--------
AdLogo v1.00 - Official Release!
-- Edited the code for final release of version 1.00:
-- Removed the 20-file Batch File Limit from AdLogo. Now,
AdLogo has NO limits as too how many files can be processed.
-- ADLSETUP.EXE will now create all the TEMP directories. After
entering in all the required info, AdlSetUp will prompt if
you wish to create all the TEMP directories now. This feature
can be very handy for those running large, multi-node systems!
-- Complete Re-Write of the docs (ADLOGO.DOC)! (I know, it needed
it!)
-- Released as ADLG100.ZIP
02/22/92 - 01:11
--------
AdLogo v1.8ß Enhanced Version
-- Went thru the docs and updated them as best as possible.
(Think I would rather spend 10 hours programming than I
would 2 hours of doing the docs!).
-- Finally added COM PORT output to the code. AdLogo now displays
to the user online what AdLogo is doing (Sort of..) The info
that is sent out to the com port displays what file is being
processed and the status of that file.. Either 'Working...'
or 'Processed'. I felt that this is the only info that is
needed to be sent out, there is no need to send to the user
that the file(s) are being copied, and a logo is being added,
etc.. This way, you may not get as many ANGRY users complaining
about the time delay. As far as they can tell, the board is
simply processing each file into a packet (or whatever), and
then is will start the transfer. At the end of all file
processing, AdLogo will display START YOUR DOWNLOAD NOW and
(CTRL-X) Aborts RIGHT before AdLogo terminates and passes
control over to the protocol driver. With this addition your
users should not be getting time-out errors, or aborted
transfers. The info that is sent out to the user is NOT
displayed on the local screen. The ONLY way for you to view it
is to log into your system from remote (Another modem, NULL
modem cable, etc..) Below is an example of what the user will
see.
(CTRL-X) To abort transfer <--LAST string that PCBoards sends
AdLogo v1.8ß Compiled 02/22/92
Registered to: The "Port of Call" BBS
[Serial #: 00001]
Filename Status
------------ ----------------
123W20.ZIP Processed <-- This is on a MATCHED drive
LINDA.GIF Processed <-- Bypassed, not .ZIP
159KEYS.ZIP Working... <-- After completed, Processed
is displayed.
START YOUR DOWNLOAD NOW
(CTRL-X) Aborts
AdLogo will automatically detect if there is a 16550 UART
installed and enable the FIFO buffer.
-- Added a 2 second delay just before AdLogo closes the COM port
so that any characters that are waiting to be sent, will get
sent before closing the port.
-- A change to the ADLOGO command line in each of the PCBS?.BAT
files is required for the above added feature. Simply add
%1 to the end of the line.
(ie: ADLOGO C:\PCB\ADLOGO.CFG %3 %1)
This is the COM PORT number that PCBoard passes to the .BAT
file.
NOTE: ADLOGO IS ONLY COMPATABLE WITH COM1 & COM2!!!
If you are using Non-Standard COM ports, please
contact me as I will have to add a lot more code
to ADLOGO for this addition. I will only do this
if someone calls and requests this.
-- If you registered your copy of AdLogo, and installed the batch
files for XModem protocols there is something you
should be aware of:
IT WILL NOT WORK!! AdLogo creates a text file that
is then passed over to DSZ. DSZ then reads that text
file to get the path and filename(s) of the file(s)
to be transfered. However, when DSZ is invoked in the
XModem mode, DSZ will NOT allow itself to open and
read the text file (ADLOGO.LST) that AdLogo creates.
Under YModem and Zmodem, this is not a problem.
It does not state this in the DSZ.DOCs, but I'm
assuming that since XModem is a SINGLE file transfer
protocol, and that USUALLY when a text file is passed
to DSZ it means that a multi-file transfer is to take
place, that DSZ is rejecting the request. DSZ will NOT
allow a text file to be passed to it when invoked
using XModem! So, this means I have to figure out
someway of passing a SINGLE file path and filename
to DSZ when XModem is the selected protocol.
Thanks Bart & Glenda
The Year 2000 Network BBS
-- Released as ADLG18B.ZIP
02/17/92 - 20:24
--------
AdLogo v1.7ß Enhanced Version
-- Complaint of 'File not found' error with version 1.6ß when
running under COMPAQ DOS v3.x where PKZip was trying to add
the Logo to the ZIP file located in the TEMP directory--FIXED
-- Released as ADLG17B.ZIP
02/17/92 - 01-23
--------
AdLogo v1.6ß Enhanced Version
-- Changed the format of the Batch File Status window to a more
formatted display.
-- Added 'Total Files Processed - n' to the Batch Transfer Status
window.
-- Fixed bug when a Single File Transfer was taking place and
the file to be downloaded was NOT in a ZIP format the cursor
positioning was incorrect and would add linefeeds thus making
the Status Window un-readable.
-- On some systems it has been reported that the screen writes
get all messed up. This is not a problem in AdLogo, but the
way DOS handles it's info when output is redirected to NUL.
To fix this problem, simply change the LOCK LINES settings
in PCBSetup, File Locatations #2, Protocol Data File for all
the external protocol that you have AdLogo installed in to
'N'.
-- Added a file to the archive called BATCH.PMT. This is a file
that you can have echoed to the user online right before
PCBoard shell's out to the external protocol. This file
contains PCBoard's @X color codes that simply states that the
batch mode file transfer may take upto 1 minute before
starting. To add this in to PCBoard, change to your directory
that contains the file PCBTEXT (usually C:\PCB\GEN) and
execute MKTXT145 as follows:
C:\PCB\GEN\> MKTXT145 PCBTEXT <enter>
Press <F3> and then enter the number 496 <enter>
Change that line to %<DRIVE><PATH>BATCH.PMT
Where <DRIVE> is the drive letter where you had
placed the file BATCH.PMT and <PATH> is the DOS
path to the file.
(ie: You placed the file BATCH.PMT into you C:\PCB\GEN
directory, the line would look like this:
%C:\PCB\GEN\BATCH.PMT
Press <ESC> to save the changes made.
NOTE: If you have PCBoard load the PCBTEXT file (set via
PCBSetup, Options #1), you will need to cycle PCBoard one
time before the changes will take effect.
-- Well, we're gonna let this version fly for a while.. Want to
get working on the code that will echo to user online what
you as the Sysop will see in the File Status Window so that
the user will know what is going on and why the transfer
hasn't started within 5 seconds.
-- Just to keep you up-to-date on what our future additions list
is adding support for .ARJ format, and for those boards that
are big into .GIFs, adding support for adding your ad to a
.GIF file(s) before sending! Please report any bugs, problems
or incompatablilty problems that you incountering. Would like
to set March 1st, 1992 as the release date of the official
release of AdLogo v1.0.
-- Also in the process of adding code to ADLSETUP that will
automatically create the TEMP directories for all nodes.
This may not be a problem to most Sysops, having to manually
create a TEMP directory for each node, however for those that
are running systems bigger than 10 nodes, this could really
be hard on the 'ol fingers! <grin>
-- Released as ADLG16B.ZIP
02/16/92 - 04:51
--------
AdLogo v1.5ß Enhanced Version
-- Fixed bug that would incorrectly read the passcode from the
ADLOGO.CFG file.
-- Changed format of ADLOGO.CFG file. Line 3 USED to be the
PassCode line. PassCode line is NOW LINE 8 and all others
move up one. (ie Line 4 is now Line 3, etc...)
-- Now packaged in the archive file is a utility called
ADLSETUP.EXE. This simple util will create the ADLOGO.CFG
file automatically. Simply run this util in the directory
you want your ADLOGO.CFG file to be placed in. ADLOGO.CFG
can still be edited with a text editor, but created ADLSETUP
to follow the new .CFG file format stated above.
-- Enahanced Version! Completely re-wrote the code for the screen
output. All screen writes are done via the Video BIOS. No
DIRECT screen writes are in the code. Using the BIOS, there
should be no problems with 'bleed-through' for those running
under multi-tasking enviroments such as DESQview, DoubleDOS,
etc...
-- Just for your information, AdLogo is currently being tested on
a 386sx-16mhz running under DESQview v2.41 with QEMM v6.01
(stealth enabled, mapping mode) for a 3 node PCBoard v14.5a/E3
system and a 386-16mhz running under LANtastic with PCBoard
14.5a/E3 for a two node system (Node 2 is an 8088).
-- Released as ADLG15B.ZIP
02/13/92 - 01:55
--------
AdLogo v1.4ß
-- AdLogo now reads the permenent parameters from a configuration
file. New Syntax for AdLogo is:
AdLogo <CFGFILE> %NODE% %3
<CFGFILE> is the full pathlist and name of AdLogo's
configuration file. (ie: C:\PCB\ADLOGO.CFG)
(%NODE% & %3 are still the same)
A sample .CFG file is included in the archive. The file format
is as follows:
Line 1 - Your Name (32 chars max)
Line 2 - Serial # (00000 if UNREGISTERED)
Line 3 - PassCode (0000000000 if UNREGISTERED)
Line 4 - CD-ROM (or Hard Drive) Drive Letters
Line 5 - TEMP directory
Line 6 - FULL Path & Filename of ZipComment (BBS LOGO)
Line 7 - FULL PAth and Filename of Callers Log file
(Do NOT Place a node number here if running
MultiNode!)
Line 8 - Y or N (Y=MultiNode System, N=Single Node)
The .CFG file is a simple TEXT file that can be created/edited
with a normal text editor such as QEdit.
-- More code removed to make screen display more clear and easier
to read.
-- Changed the filename of the registration form from
REGISTER.TXT to REGISTER.FRM
-- Posted as ADLG14B.ZIP
02/12/92 - 16:31
--------
AdLogo v1.3ß
-- Boy did I really mess v1.2ßeta up!! All is fixed with
the fixes listed below.. Think I'll take a few days off
to get my eyes straight again! Sorry for any problems!
-- Bug fix. AdLogo was not correctly writing the new path
of a file processed during a Single File Transfer.
-- Fixed CR/LF on the opening screen
-- Posted as ADLG13B.ZIP
02/12/92 - 12:30
--------
AdLogo v1.2ß
-- Edited documentations to reflect added SET variable
Problem encountered when running under certain enviroments
DSZ was unable to locate ADLOGO.LST by the setup stated
in the docs. Must add a SET DRIVE=n in each BOARD.BAT file
where 'n' is the drive for that node. (ie: SET DRIVE=C:)
-- TMC Software Development and OTS Development Corp. are
working together to bring you AdLogo and future creations by
TMS Software Development. All files in ADLG???.ZIP will now
have the -AV Authenticity Verified code next to them, and
OTS Development Authenticity Verified statement at end of
the .ZIP file. If ANY file(s) do not have the -AV next to them,
DO NOT use any of the files in the archive and please report
such cases to any of the Support Boards listed in the manual
or call voice support between the hours of 8:00am-7:00pm,
Monday thru Friday Central Time.
-- Posted as ADLG12B.ZIP
02/12/92 - 01:23
--------
AdLogo v1.1ß
-- Removed all code that displayed every detail that AdLogo
was performing. This will help on systems with slow
screen writes and shorten the time it takes AdLogo to
execute.
-- Added logging to PCBoard's Callers Log. Two more commands
must now be passed on the AdLogo command line in the
PCBS?.BAT files. New format is:
AdLogo <CDROM> <TEMP> %NODE% <ZipComment> %3 <CALLERSLOG> <MULTINODE>
<CALLER> is the Full Path of your CALLERS log file
(ie: C:\PCB\MAIN\CALLER)
NOTE: To not add a node number to this!
<MULTINODE> is either the letter Y or N.
Y = Yes, you are running a multinode system
N = No, you are not running a multinode system
-- Added support for SHARE under Networks and Multitasking Systems
-- Released as ADLG11B.ZIP
02/09/92 - 23:19
--------
AdLogo v1.0ß
-- Initial Public release
-- Added code for .ZIP file checking. If a NON .ZIP file is
detected, AdLogo will not move the file(s) over to the temp
directory. Instead, will simply copy the ORIGINAL path of
the file over to ADLOGO.LST
-- Added Serial No.
-- Edited docs. Incorrectly stated the wrong syntax for DEL.
now stated properly as DEL N:\TEMP%PCBNODE%\.
^
(Was missing)
-- Released as ADLG10B.ZIP
02/09/92 - 19:31
--------
AdLogo v1.0ß2
-- Removed code not is use. (Code that was inserted for initial
testing purposes.) Not released.
02/08/92 - 17:38
--------
AdLogo v1.0ß1
-- Initial ßeta release. Fully functional for both single and
batch file transfers.