Version 2.93 - November 24th 2007
---------------------------------

WARNING: This release makes several dozen fundimental changes to the
         Echomail processor, XMAIL and the DBRIDGE.ADF database file. After
         this upgrade has been installed, 3rd-party programs which
         directly access the Echomail database will not function properly.
         However you may downgrade/rollback to 2.92 or prior if you are
         not happy with this release. A lot of hard work and careful
         consideration has been given if you are not happy and wish
         to rollback. No version-specific files are created and no
         additional steps are required if you feel a rollback is necessary.

This is a very minor release but has a lot of internal code changed to
facilitate large amounts of Echomail areas, and to resolve Error 202 and
203 problems for good. After this upgrade has been installed, Echomail
tossing may slow down somewhat; depending on the speed of your computer.
However, other problems have been solved, so its a case of trading a little
bit of performance to solve problems elsewhere. D'Bridge can now process up
to 32,000 Echomail areas, as opposed to the previous limit of around 2,000
before Error 202 and Error 203 happened. There is also a little bit more
memory available for other settings such as routing tables, Packet/Mail
control lines and so forth.

It is not necessary to upgrade to this version right away unless you are a
Fidonet Zone or Network Co-Ordinator and you process large volumes of
Echomail AND you have a large amount of downlinks or other setup information.

It would be a good idea to pay attention to the system log files and you
should check your message bases after each "tossing" cycle has completed.

- If you are running D'Bridge under OS/2 Warp, Echomail performance is
  actually improved on HPFS partitions when the size of the cache is set
  *low*. A cache size of 128k to 256k is recommended.

- The entire Areafix system may run a little slower than usual because the
  whole code for requesting areas depended heavily on the old method. It
  has been tested here to be stable and bug-free.

- The keyword "ALL" now tells Areafix to add (or remove) all available
  Echomail areas for a system. For example, an Areafix request from 2:2/0
  containing just "ALL" would connect that address to all available areas
  based on security level (or all of them if the request was forced
  using the ALT+N command). Likewise, if 1:229/2000 sent a request
  with "-ALL", all current areas would be disconnected.

- The new changes to the Echomail processor have no effect if you are using
  the QuickBBS storage system. It is impossible to have thousands of areas
  with QuickBBS or GoldBase. In fact I plan to completely get rid of
  the support for QuickBBS/GoldBase support altogether... unless someone
  out there absolutely insists on having it.

- A new version of DB2RG has been included for the Renegade BBS software
  to work properly with this release.

- The internal editor now correctly handles Echomail areas up to 32,000.

- The BADECHO area where "bad" messages get sent to, is now numbered
  as 32767, instead of 9999.

- DBUTIL has been significantly updated to handle the new code changes.

- The problem in DBUTIL DESCFILE not correctly justifying descriptions
  is fixed.

- Please double-check all your events and routing information after
  installing; since the way that memory is managed with those screens has
  also changed slightly.




Version 2.92 - November 10th 2007
---------------------------------

WARNING: This release makes a fundimental change to the Echomail processor
         including changes to XMAIL and the internal message editor, and
         fundimental changes to the Nodelist Compiler. Please backup
         accordingly and test very carefully.

This is a major release which introduces the ability to compile nodelists
designed with MAKENL amongst Fidonet along with major fixes to DBUTIL PURGE
and several other corrections.

- The Nodelist Compiler should now properly process and compile Nodelist
  segments amongst the recent switchover events in Fidonet.

- DBUTIL PURGE has been redesigned to purge-out old messages first, instead
  of just "randomly purging".

- This is a release that has a minor fix that has shown to improve the way
  Echomail is imported by 3rd-party software that tosses mail to BBS's,
  for any areas that use Fido *.MSG storage. In each Echomail directory
  that uses Fido *.MSG storage, a file is written to keep track of the last
  message read by the editor or "tossed" by the D'Bridge Echomail processor.
  This is simply known as a "last-read pointer". This pointer may also be
  used by BBS or 3rd-party software that manipulates Fido *.MSG directories.
  Since the very beginning of D'Bridge, this file is called 1.MSG. Its the
  infamous "Ignore this message; used for internal Echomail processing" text.

  For example, Searchlight by Frank LaRosa / Telegraphix uses SLMAIL to
  import Fido mail into the BBS, Renegade uses either Renemail or CDRMAIL to
  import messages. I'm sure there are others that I just don't know about.
  When you are using such software, sometimes those programs may get
  "confused" and think that 1.MSG is actually a message, when in fact its
  just there to keep track of the last message in the area. The result would
  be that the message gets imported into your BBS software anyway. So, only
  change the filename if this is the case and you're having problems.

  I understand that the fix in this release is probably many years too late
  but this issue has finally been resolved in D'Bridge thus making it
  compatible with most 3rd-party software that handles Fido *.MSG format.

- A new search/replace field for the Forward-To lines has been added
  to the GLOBAL CHANGE command in DBUTIL.

- A minor correction to DBUTIL RENUM and RENUMDATES has been done for
  stability reasons.

- A somewhat serious problem has been solved in the Web Processor (DBUTIL
  PROCESSWEB) where large messages were not being handled properly.

- The Setup Wizard has been corrected to NOT overwrite any Web templates
  for DBUTIL and Anti-SPAM configuration files for SOUPGATE.

Nick Andre
http://www.nickandre.com




Version 2.91 - November 7th 2007
--------------------------------

This is a minor release.

- The D'Bridge SCHEDULER screen has been enhanced to allow you to run any
  DOS commands for a MAIL event either after a Dialup session, or after any
  mail has been processed regardless (such as manipulating via. DBRIDGE.RSN)
  The "Allow Filesharing" question has been changed to "Execute DOS
  commands" and you have two choices - DIALUP ONLY or ALL MAIL. The default
  is DIALUP ONLY which is the normal behavior that Chris had in the DOS
  command code since 1.58. This new feature was absolutely necessary to aide
  in the proper operation of certain 3rd-party software or for those of you
  who use DBUTIL MOVE to manipulate the Queue.

- The blinking-ANSI problem in the internal message editor has been found,
  replicated here, and should be fixed now as per Roger.


Version 2.9 - October 28th 2007
-------------------------------

This is a very minor release that doesn't fix any problems at all but
contains various changes to code and other "behind the scenes" stuff.

Please back up and test very carefully - this release changes some
fundimental code in the Echomail processor, that has been unchanged
since 1.58. The code has now been changed slightly in order to accomodate
some upcoming features for a future release.




Version 2.89 - October 15th 2007
--------------------------------

This minor release should correct the 8000-crash problem in the internal
message editor when you list the messages in an area.

Please test accordingly and keep in mind that the code for the internal
editor is a real spaghetti-mess and fixing one thing usually breaks
something else. Not that I did this release at the last minute mind you;
but I'm very reluctant to change any of the code in the internal editor.




Version 2.88 - October 13th 2007
--------------------------------

This minor release corrects a very, very rare and hard-to-notice problem
with DBUTIL PURGE. I will be spending some time on the other problems
in the next week or so... please be patient.




Version 2.87 - October 12th 2007
--------------------------------

This is a very minor release of D'Bridge that adds a new feature to
the DBUTIL program: RENUMDATES.

DBUTIL RENUMDATES will date-sort an Echomail area, putting messages in order
from oldest to newest dates. You can also specify an individual area
to date-sort, ie. DBUTIL RENUMDATES FIDONEWS.

Note that the RENUM and RENUMDATES features execute an Echoscan when
the mailer fires up again...




Version 2.86 - October 2nd 2007
-------------------------------

I will be "down" in Fidonet for at least a few weeks and busy with personal
matters. If you need to reach me, call my cell at 416-567-0117 or EMAIL
me at foxmulder4055@hotmail.com.

I will try to catch up on the DBRIDGE echo as much as I can. Most likely
from Internet cafe's while on the road. Call it soul searching or a
personal journey I really need to take folks. In the meantime I may use
Docs Place BBS or whatever halfway-decent "Fido on the Web" board I
can find. Suggestions anyone?

Anyway, this is a very minor release. If there are serious bugs, please
call me or let me know via EMAIL and I'll do my best to write any fixes.

- D'Bridge now supports RAR archiver types. RAR support is configured
  in the XMAIL CONTROL screen. And yes - done so WITHOUT removing any
  existing support for PAK or ZOO. There was *just enough* codespace left
  in the XMAIL subroutines to squeeze that in...

- D'Bridge ships with RAR32 for DOS and comes with the RAR options already
  preconfigured for new installations. On upgrades, it *should* fill in
  the new settings but if not, just put the cursor in the RAR field and
  press delete or CTL+Y to erase it, and D'Bridge fills in the proper
  settings.

- The Setup Wizard will ask you if you wish to place the RSX/EMX libraries
  required by RAR, into your system path. This happens once only. If you
  need to do this manually, copy the RSX.EXE, EMX.DLL and EMX.EXE files
  to the WINDOWS\SYSTEM32 directory or OS2\APPS\DLL, respectively.

- The version of RAR that ships with D'Bridge 2.86 requires at least a 386
  processor. It may not run on a Tandy 1000 or earlier IBM PS/2 computers
  but should run okay on Tandy 2500 series.

- A plus sign (+) is required before the RAR compress/decompress
  commands in the XMAIL CONTROL SCREEN, just like the rest.

- If you are using D'Bridge under OS/2 Warp, you may need to change the
  properties for the virtual DOS session to enable DPMI (DOS Protected
  Mode Interface) if you plan to use the new RAR support under OS/2.

- NODEDIFF segments archived with RAR should unpack okay, but only if the
  extension of the segment has the letter R in the first part, for
  example, NODEDIFF.R12, NODEDIFF.R19 and so forth. For "net-wide"
  compatibility I recommend that segments only be compressed in ARC format.

- A minor bug has been corrected in the import/export functions.

- Removed the references to Squish and JAM... for now.





Version 2.85 - September 23rd 2007
----------------------------------

WARNING: Please study the release notes for 2.83 and 2.84 if you have not
         done so already. Theres a reason why we have three new releases
         in one night...

This is a very minor release which adds the ability to have a little bit
more control over systems who use no packet passwords and the SECURED MAIL
ONLY option is set to YES. This was absolutely crucial to have this feature
to aide in diagnosing/troubleshooting packet passwords between systems, and
was important enough to be coded and released immediately tonight.




Version 2.84 - September 23rd 2007
----------------------------------

WARNING: If you are upgrading from 2.82 or prior, please review the notes
         for 2.83 (included in the release file) if you have not done so
         already.

No sooner did I release 2.83, I realised one important thing was missing.
So this is a very minor release which enhances the PACKET PASSWORD feature
and the SECURED MAIL ONLY question in the PACKET/MAIL CONTROL SCREEN.

SECURED MAIL ONLY now has three choices. No, Yes and Detailed. The
feature works the same, except if you answer DETAILED, D'Bridge will
show the packet password from the remote system in the LOG window screen
(and also in the log file).

Even if you are happy with 2.83, upgrade to this release immediately and
test all mail processing again as I have made a minor correction with
the way D'Bridge handles missing packet passwords when the SECURED MAIL
ONLY option is enabled.




Version 2.83 - September 23rd 2007
----------------------------------

This is a minor release as per recent discussions in the DBRIDGE echo.
Although its a minor release, it addresses mail security. Because this
release deals with the way mail is processed, carefully test all features.
Pay attention to the system log during mail tossing and packing. A minor
correction to DBUTIL MOVE was also done as well.

WARNING: All inbound mail and pending XMAIL should be processed first before
         installing this release. DO NOT INSTALL THIS RELEASE if mail
         transactions are currently pending.

WARNING: If you are a Hub or Co-Ordinator, careful planning and precautions
         should be taken during this upgrade if you wish to use the PACKET
         PASSWORDS feature mentioned below. When using packet passwords,
         it will become impractical and time-consuming if you don't like
         this version and wish to rollback - seeing as how previous
         versions of D'Bridge did not support packet passwords. If at all
         possible, install a fresh copy of 2.83 in a new directory and
         do a "test run" with one system to ensure passwords and security
         are correct, BEFORE installing this release.

- The BINKD configuration now allows for mixed-case passwords. Note that
  when upgrading to this release, the BINKD configuration is imported as
  uppercase. This problem happens only once and is due to the import/export
  code in prior releases. It won't happen again on future releases. However
  if you rollback to a prior version, the BINKD configuration is imported
  as uppercase again.

  Some improvements are going to be made to the BINKD administration but
  probably not for a little while yet.

- PACKET PASSWORDS is located in the PACKET/MAIL CONTROL screen. You can
  now use packet passwords to secure your D'Bridge system even more, or to
  use passwords for exchanging mail with other systems that require it.

- SECURED ECHOMAIL ONLY in the PACKET/MAIL CONTROL screen has been renamed
  to SECURED MAIL ONLY.

- Some of the questions in the PACKET/MAIL CONTROL screen have been
  expanded to make things a bit easier when entering data, for those of you
  with large configurations.

- The Setup Wizard will offer to temporarily disable the SECURED ECHOMAIL
  ONLY setting if it detects mail or files in the INBOUND directory waiting
  to be processed, to allow proper testing of this particular version.

- DBUTIL MOVE now generates a unique packet name when moving NETmail and
  should solve the "lost mail" problem as reported. This unique name is
  generated every time DBUTIL MOVE is ran and does not rely on a counter
  or anything like that - So it should never overwrite any NETmail packet
  that is waiting in another directory or BINKD outbound queue. If... and
  I do mean *IF* this problem happens again, let me know ASAP and back
  to the drawing board I'll go...



Version 2.82 - September 20th 2007
----------------------------------

WARNING: This release makes a fundimental change to the DBRIDGE.ADF file,
         that stores your Echomail areas. Please back up this file first.

This is a very minor release which corrects some serious bugs in the new Web
integration module. A potential problem with the way the RENUM feature
of DBUTIL works has also been corrected. Although it doesn't look like it
on the outside, a lot of hard work went into writing this release.

In order to fix the bugs, a fundimental change in the way certain
information is stored has been revised. To avoid potential problems, I also
added various security checks to ensure that you are only using the DBUTIL
that is meant for this release... and not others. Therefore:

  ***********************************************************************
  *  DO NOT, UNDER ANY CIRCUMSTANCES, USE ANY OTHER VERSION OF THE      *
  *  DBUTIL PROGRAM WITH THIS RELEASE OR ATTEMPT TO COPY A DBRIDGE.ADF  *
  *  FILE FROM A PREVIOUS VERSION TO THIS ONE. DATA LOSS WILL HAPPEN!   *
  ***********************************************************************

- The Setup Wizard does not overwrite or update your HTML template files,
  only the SAMPHTML.ZIP file gets updated when upgrading. For this reason,
  if you have custom HTML code for the Web integration system, any changes
  that are done to the way placeholder variables work will need to be done
  manually. I don't expect this to be much of a problem if you are using
  the Web features; you should have a basic understanding of how HTML works
  anyway at that point.

- The ON WEB SERVER question in the ECHOMAIL SETUP SCREEN has been changed
  to three different choices now. You can specify NO, YES or DETAILED. The
  "detailed" setting saves the SEEN-BY, PATH and KLUDGE lines of a message
  on your Web server. The standard "Yes" option does not. The help file
  has also been updated with this change along with the import/export
  function in D'Bridge itself.

- A new feature, "Web ASCII" has been added to the ECHOMAIL SETUP SCREEN
  as well, enabling you to properly filter out high-ASCII from messages
  when posting to a Web server.

- Did some work in trying to correct the plethora of LF/CR confusion in
  HTML code generation but its not entirely fixed... so be warned. If
  anyone can suggest to me a proper way to handle the whole LF/CR mess, let
  me know via EMAIL or in the DBRIDGE support echo on Fidonet.

- The numbering of the messages shown in an HTML listing is correct now.

- Two new placeholders, %%%MESSAGE_NUMBER%%% and %%%MESSAGE_OF%%% have been
  added to the message body template file (MSG-B.HTM). The code looks like
  this:

  Message %%%MESSAGE_NUMBER%%% of %%%MESSAGE_OF%%%

  which translates to

  Message 1 of 102

  Please update any existing code on your web site accordingly. The new
  placeholders, like everything else in D'Bridge, are completely optional
  and your Web site doesn't need to use them if you don't want to. Note that
  the MESSAGE NUMBER placeholder in the message body template works
  differently than the one in the listing body template.

- The %%%MESSAGE_PREVIOUS%%%, %%%MESSAGE_LISTING%%% and %%%MESSAGE_NEXT%%%
  placeholders work properly now. The MESSAGE PREVIOUS placeholder will
  not be shown when viewing the first message. Likewise the MESSAGE NEXT
  placeholder is not shown on the last message.

- At the last minute, I also added two new place holders for the PREVIOUS
  and NEXT links - If you add a pound sign (#) in the above-mentioned
  placeholders, it will put the number of the referenced message in there.

  So for example: %%%MESSAGE_PREVIOUS#%%% will show "Previous Message (25)"
  as opposed to just "Previous Message", and %%%MESSAGE_NEXT#%%% will show
  "Next Message (27)" as opposed to just "Next Message".

- For icing on the cake, I updated all of the sample HTML files to show off
  all the new features... and updated my website as well.

Please note that it is not my intention to offer features such as font size,
typeface and the like - these are things you should be using your Web
publishing software to do. DBUTIL's primary task is to simply replace
placeholders with HTML code, nothing else. It is fairly straightforward to
implement whatever fonts and typeface you want in the template files.

Nick Andre
http://www.nickandre.com




Version 2.81 - September 14th 2007
----------------------------------

This is a very minor release that fixes the bug with the missing REPLY
kludge when writing messages in the internal editor. Another release
is going to be coming a little later to fix a variety of bugs with
the Web integration.




Version 2.8 - September 7th 2007 - WEB SERVER READY
---------------------------------------------------

WARNING: This release of D'Bridge now requires that any DOS events in
         D'Bridge that call DBUTIL have the plus sign (+) infront of
         the command, because DBUTIL now requires a full 640k of memory
         to function properly. Please check this BEFORE upgrading.

You can now let Internet Web users access Fido messages on your system.

This release of D'Bridge now supports Web servers such as Microsoft IIS
and Apache. I've done all the complicated hard work of making sure that this
new feature is "as easy as 1-2-3". The new feature is fully contained
in the DBUTIL program.

*** SUGGESTION *** You should view this document on your computer with
                   your web browser pointed to nickandre.com, so you can
                   fully understand how this works and how simple it is.

All is accomplished with DBUTIL PROCESSWEB followed by the directory to
generate HTML messages in. Six "template" HTML files exist in your D'Bridge
directory that you can edit and tailor to your liking. Once you're all done,
one simple command instantly transforms your D'Bridge mail to the Web:

For example: DBUTIL PROCESSWEB D:\WWWROOT\MESSAGES

This must be a directory strictly for use by DBUTIL - The contents of this
directory will be erased or updated every time DBUTIL PROCESSWEB is ran.

WARNING: Do NOT tell DBUTIL to generate messages in the root of your Web
         site for this reason. Always create a subdirectory off your site.

Any directory that can be accessible in DOS can be accessible by the Web
Server component. This means that D'Bridge can run on the same computer
as your Web Server, or on a "nanny" machine on a LAN on a networked drive.

The WEB SERVER HOME DIRECTORY question has been removed from the INTERNET
CONNECTIVITY screen in case you haven't noticed. I felt that this belonged
on the command-line with DBUTIL, so those of you who run Web servers can
offer the same Fido messages across multiple websites on the same server
(as opposed to having to install multiple copies of D'Bridge to handle
multiple websites)

When DBUTIL PROCESSWEB is ran, it scans through your Echomail database and
creates HTML messages on your Web server. First, it checks to see if
the "On Web Server?" question for each area is set to YES. For each area
it finds, it builds a list of Echomail areas on your Web server.

If you have a large number of Echomail areas that you want to set the "On
Web Server" question, just use the CHANGE feature of DBUTIL. For more help
on that, view the D'Bridge manual or consult the DBRIDGE echo on Fidonet.

WARNING: Please use due diligence. "Private" Echomail areas (such as
         net-wide, regional or co-ordinator only) should not be made
         accessible on your Web server. Web search engines such as Google
         and Yahoo could easily "crawl" these sites, thus making such
         forums available for the whole world to see. Be sure that private
         Echomail forums have the "On Web Server" question answered NO.

DBUTIL will then use the following files from your *DBRIDGE DIRECTORY* to
create the HTML files. Six HTML files are shipped with this release of
D'Bridge for you to modify as you see fit. The following files MUST exist
in your D'Bridge directory, otherwise the DBUTIL PROCESSWEB command won't
work.

If you wish to allow your website to have Fidonet areas available but NOT
allow "web robots" from Yahoo, Google or MSN.COM to index them, you should
create a ROBOTS.TXT file in the root of your website. Drop me an EMAIL
and I can explain how this is done, or just google "robots.txt structure"
if you want. In a future release of D'Bridge I plan to integrate support
for ROBOTS.TXT management.

There are three different "parts" to an HTML Fido message that DBUTIL will
work with. The Header, Body and Footer. The header should contain HTML code
that "sets up" the display of the area or message. The body contains any
code displayed along with the content of the message. And the footer is any
HTML code appended to the end of the display.

The HTML editing can be done with any HTML or text editor, or a fancy
"what you see is what you get" program like Microsoft FrontPage. If you
are totally lost, there are even Web-based editors such
as http://htmledit.squarefree.com or http://www.ewebeditor.com

There are some "placeholders" that you use when you write the HTML. When
DBUTIL processes a message, it will replace the placeholder with the
actual value.

Note that headers and footers of AREAS, LIST and MSG template files should
not contain any placeholders. DBUTIL only processes placeholders in "body"
templates.

Placeholders can be anywhere in the body, in any order, wherever you want
to use them is fine with me. If you are a web developer or programer, you
can even stick them even inside Javascript or Visual BASIC code if you want.

Heres what the six D'Bridge HTML template files are:

AREAS-H.HTM     HTML header to show before the list of available areas.
AREAS-B.HTM     HTML code containing the area listing itself.
AREAS-F.HTM     HTML footer code to append to the end of the area listing.

LIST-H.HTM      Header to show before the actual message listing.
LIST-B.HTM      The body of the message listing.
LIST-F.HTM      Footer to add to the end of the message listing.

MSG-H.HTM       Header to show before the message.
MSG-B.HTM       The actual body of the message.
MSG-F.HTM       Footer to append to the end of the message display.

AREAS.HTM       The compiled area listing code when DBUTIL PROCESSWEB ends.
                Your web site must point to this file. This file will reside
                in the base directory you define in INTERNET CONNECTIVITY.
                The user reads and views messages from here on out.

The user essentially sees AREAS.HTM, which will display the list of
available Echomail areas (generated from AREAS-H, AREAS-B and AREAS-F). The
user then clicks on an area they want. They see the list of messages in
that area (LIST-H, LIST-B and LIST-F) and clicks on a message
(MSG-H, MSG-B and MSG-F).

When DBUTIL encounters the following "placeholders" in AREAS-B.HTM, it will
substitute them with the proper information. Three percent signs (%%%)
tells DBUTIL that it should replace the code in the HTML file with what
you want.

          %%%AREA_TAG%%%  The Echomail "tag", ie. DBRIDGE or FIDONEWS
  %%%AREA_DESCRIPTION%%%  The description of the Echomail area.
%%%AREA_TOTALMESSAGES%%%  The total number of messages in the area.

When DBUTIL encounters the following placeholders in LIST-B.HTM, it will
replace with:

    %%%MESSAGE_FROM%%%    Who the message is from.
      %%%MESSAGE_TO%%%    Who the message is to.
 %%%MESSAGE_SUBJECT%%%    What the subject of the message is.
    %%%MESSAGE_DATE%%%    The date of the message.

When DBUTIL encounters the following placeholders in MSG-B.HTM, it will
replace with:

    %%%MESSAGE_FROM%%%    Who the message is from.
      %%%MESSAGE_TO%%%    Who the message is to.
 %%%MESSAGE_SUBJECT%%%    What the subject of the message is.
    %%%MESSAGE_DATE%%%    The date of the message.
 %%%MESSAGE_CONTENT%%%    The contents of the message.
%%%MESSAGE_PREVIOUS%%%    Adds a "Previous message" button to the message.
 %%%MESSAGE_LISTING%%%    Adds a "Back to Listing" button to the message.
    %%%MESSAGE_NEXT%%%    Adds a "Next message" button to the message.

DBUTIL PROCESSWEB should be ran as part of a nightly event, but for those
of you who are Hubs with busy traffic, DBUTIL PROCESSWEB should be ran as
a seperate process on your operating system, so it doesn't "tie things up".
Or, run another copy of D'Bridge on a nanny machine as described earlier.
Note that if you are tossing messages to a BBS, DBUTIL PROCESSWEB should
be called before the commands to toss the mail, and the message areas
should not be purged on a regular basis.

If you decide you don't want to use the Web support anymore, just delete
the base directory and erase the HTM files in your D'Bridge directory
(or rename them). DBUTIL is smart enough not to run if those HTM files
do not exist. So if you stored Fidonet Web mail in C:\INETPUB\WWWROOT\FIDO,
then erase the entire C:\INETPUB\WWWROOT\FIDO directory.

The method I chose to generate Web mail allows you to maintain your
existing site, whether its a real small simple one or a very elaborate
complex website. Be warned that it is still a little "crude", but I plan to
eventually add support for replies.

For an example of D'Bridge on the Web, visit my website!




Version 2.74 - August 27th 2007
-------------------------------

This is a very minor release which corrects a few outstanding issues,
including very rare bugs that may pop up from time to time.

- The obvious problem in DBUTIL has been fixed; I'm sure you know what...

- "Enhanced Areafix" options are gone; the built-in Areafix in D'Bridge
  now supports handling %LIST and %RESCAN natively. Upon studying the logic
  a bit further I felt that having %LIST and %RESCAN support as an option
  just didn't make sense...

- Along with the above mentioned cleanup, under exceptionally rare
  circumstances any Areafix requests destined for the host system were
  not being processed correctly if the previous "Enhanced Areafix" support
  was enabled.

- Areafix messages destined for SOUPGATE are no longer processed if the
  SOUPGATE address is not defined properly in the INTERNET CONNECTIVITY
  screen *and* if that address already exists as part of the AKA's.

- A problem with dialup modem support being set up by the user and then
  removed in the same instance of D'Bridge causing the "Unable to
  initialize the modem" problem has been solved.

- SQUISH and JAM support are still being worked on despite what D'Bridge
  says in the setup screens.

- Some minor things in the mailer have been cleaned up; nothing really
  worth noting here.

Nick Andre
http://www.nickandre.com



Version 2.73 - August 15th 2007
-------------------------------

This is a minor release correcting some outstanding issues with 2.72 and
adds a few features with regards to how D'Bridge handles Internet USENET
groups via. external software. This release should "tide you over" until
the upcoming version 3 series.

On the subject of USENET, if you folks need a Usenet feed (and delivered
to you as regular Echomail), I can set you up directly from my system
at 1:229/426, via BINKD, FTP or D'Bridge-Over-Telnet.

- If a TELNET connection came in and another system was running an Auto-
  Update cycle, D'Bridge would corrupt the backup configuration files. This
  problem has been fixed in this release. This was a very, very rare and
  difficult bug to track down, and only happened on multi-line setups.

- A new "placeholder", *L, has been added to the BBS CONFIGURATION screen
  as well as the EVENT SCHEDULER. When *L is encountered by D'Bridge, it
  will replace *L with the number of the current "line" running, if MULTI
  LINE SUPPORT is enabled. If you are not running a multi-line setup, then
  the line number placeholder will always be set to 1.

- The DESCFILE function in DBUTIL has been corrected to properly
  account for justification when importing descriptions from text files.

- DBUTIL has been significantly rewritten to use a more "modular" approach
  in the way it runs, please test all features and report any problems
  accordingly.

- Various minor fixes and updates have been done to the Setup Wizard.

- D'Bridge now ships with PKZIP/PKUNZIP 2.50 instead of 2.04g. When the
  Setup Wizard installs D'Bridge for the first time, it will ask if you
  would also like to copy PKZIP/PKUNZIP to your operating system's directory
  as well, ie. C:\DOS or C:\WINDOWS, etc etc.

- The Areafix system in D'Bridge has been corrected and enhanced to support
  the automatic updating of the NEWSRC file in VSOUP for Windows and OS/2,
  and other products that support the NEWSRC file standard. If an Areafix
  request comes in that is destined for your NNTP/USENET GATEWAY address
  as defined in the INTERNET CONNECTIVITY SCREEN, D'Bridge will treat that
  request as either adding or removing areas in the NEWSRC file. So for
  example, lets say my USENET gateway is 1:229/9999:

  From: Nick Andre, 1:229/426
    To: Areafix, 1:229/9999
  Subj: MyPassword
  ---------------------------------------------------------
  ALT.BBS.RENEGADE
  ALT.WORSHIP.WARD-DOSSCHE
  -COMP.SYS.UNIX
  -TALK.POLITICS

  Would make D'Bridge do the following to NEWSRC:

  alt.bbs.renegade! 0           becomes     alt.bbs.renegade:
  alt.worship.ward-dossche! 0   becomes     alt.worship.ward-dossche:
  comp.sys.unix: 12000-13000    becomes     comp.sys.unix! 12000-13000
  talk.politics: 22312-25333    becomes     talk.politics! 22312-25333

  The NEWSRC "standard" is such that a colon (:) indicates that the gateway
  software is to download the group from your NNTP server or host. An
  exclaimation point/bang character (!) tells the software not to download.

  And so forth. Note that if you did not define a NNTP/USENET GATEWAY
  address, the NEWSRC auto-updating is disabled.

- The missing files and sample configurations for SOUPGATE are now shipped
  with this release for those of you who want to setup a more advanced
  configuration for EMAIL routing in D'Bridge and SOUPGATE.



D'Bridge 2.72 / May 15 2007
---------------------------

This minor release fixes the bug where D'Bridge crashes during
the "AutoUpdate" routine if MULTI-LINE SUPPORT is enabled. A new version
of DB2RG is also included for those of you running the Renegade BBS
software.


D'Bridge 2.71 / May 12 2007
---------------------------

This is a minor release which addresses several bugs, and adds one
new feature - the ability to run D'Bridge as a shell process.

This release was programmed mostly in-flight from Halifax to Toronto at 7AM
so no doubt there will be bugs here and there... please test accordingly.

Enjoy.

- D'Bridge can now co-incide with a Telnet server or other front-end, and
  be called as a shell process. All you need to do is create a dummy/
  semaphore file called LINExxx.OTL (short for "caller on-the-line"), and
  whenever D'Bridge starts, it will check to see if theres a caller on
  the line. This can be a "human" (BBS caller) or a Fido mail session.
  This is how D'Bridge can be used to run via. Telnet on Internet setups.

  When the call is completed, D'Bridge exits. NOTE THAT THE SEMAPHORE IS
  DELETED UPON EXIT. If D'Bridge is running from within a DOS batch file,
  the batch file must explicitly create the LINExxx.OTL file before
  firing up - ie. "echo Caller On-The-Line > C:\DB\LINE1.OTL"

  You must also enable MULTI-LINE SUPPORT if you're intending on running
  D'Bridge as a "Fidonet over Telnet" server AND you intend to serve
  more than one inbound or outbound Telnet connection at a time. Run one
  copy of D'Bridge as usual; this will be the "copy" of D'Bridge that runs
  normally so it can execute events and process mail. Other "lines" would
  be what is called as a shell process by your Telnet server.

  Lets take a look at the below batch file for an example.

  This is what I actually use on my Windows Server 2003 system which runs
  my BBS and my website. I'm using the Renegade BBS software and Zoob Telnet
  Server. I can handle up to 4 telnet connections at once; or 4 "lines" if
  you want to think of it that way. Line 5 is D'Bridge 2.71 running in its
  own window, 24 hours a day to run events and process mail. It also has a
  dialup modem connection to it, so if someone wants to connect via. dialup,
  they would reach my BBS on Line 5.

  Note that NETFOSS, by PC-Micro & Associates, is required for Zoob
  Telnet Server to run with D'Bridge. When you download NETFOSS, simply
  place NETCOM and NETFOSS into your D'Bridge directory, then place
  the NETFOSS.DLL file in your Windows directory, ie. C:\WINDOWS.

  When Zoob Telnet Server fires up, the window looks something like this:

  --------------------------------------------------
  LOG                                              |
  |                                                |
  |                                                |
  |                                                |
  | * Ready to accept connections on port 23...    |
  --------------------------------------------------
  |    Command to run: D:\DB-TEST\RUNDB.BAT %N %I  |
  | Startup directory: D:\DB-TEST                  |
  |    Drop file path: (blank)                     |
  --------------------------------------------------

  The other options in Zoob, such as "Minimize new windows", "Number of
  nodes" and so forth are up to you. However, the CREATE DROPFILE should
  be UNCHECKED (blank).

  The RUNDB.BAT file simply consists of:

  (start of RUNDB.BAT)
  CD \DB-TEST
  ECHO Caller On the line semaphore > LINE%1.OTL
  NETCOM /n%1
  NETFOSS /n%1 /h%2 db.exe /%1
  DEL LINE%1.OTL
  NETCOM /u
  EXIT
  (end of file)

  Note that the "/n" and "/h" are case sensitive, and its NETFOSS that
  executes D'Bridge as a shell process.

  With this method, you can now just focus on putting all your BBS-
  related stuff in the BBS CONFIGURATION window in D'Bridge, instead of
  writing complicated batch files to handle Telnet connections.

- A serious bug in the way that D'Bridge handles inbound connections has
  been fixed; with regards to CONNECT strings. This bug was probably in
  the code since the 1.58 days. Whenever D'Bridge can't figure out what
  baudrate the incoming connection is, it would disable loading any BBS
  software. I didn't see this problem until I wrote the new code to
  handle the above-mentioned Telnet connections. I think I remember
  seeing a post in the DBRIDGE echo a long time ago about this problem.
  I really don't understand why Chris wrote the code this way, and most
  BBS software I've seen will handle such condition okay anyway.

- The unlink security code in Areafix should be fixed in this release.

- The message editor 8000+ messages problem should be fixed.

- A cosmetic bug in the XMAIL CONTROL SCREEN has been fixed; with not
  being able to cycle through the available options for each archiver.




D'Bridge 2.70 - March 30 2007
-----------------------------

This is a very minor release which fixes the QUOTE INITIALS IN REPLIES
feature. Should be working okay now.



D'Bridge 2.69 - March 26 2007
-----------------------------

This is a somewhat major release as it fixes some serious bugs and
introduces some long-overdue features.

A lot of hard work has gone into this particular release. This version also
prepares your system database files for the upcoming Version 3 release due
sometime in April. Until then, this should "hold you over" for now.

- D'Bridge now supports remote-installation using VNC and Radmin
  from Famatech Solutions Inc.

- The "No Echomail available for your security level" major bug is fixed,
  and has been tested here on a few workstations. A lot of testing has
  been done to ensure this problem is not replicated on ANY system (the
  fix was tested on various operating systems)

- There is a new option to allow QUOTE INITIALS IN REPLIES - this allows
  the internal editor to put the initials of the original poster before
  the ">" symbol. This feature is shut off by default, including on
  upgrades. The new feature is located in the EDITOR OPTIONS screen.

- A new feature, ENHANCED AREAFIX SUPPORT has been added to PACKET/MAIL
  CONTROL screen to allow the support of %LIST and %RESCAN commands in
  the Areafix system. This feature is set to OFF if you are upgrading
  to this release; you will need to turn it on manually if and when you
  are ready to test it. Note that these features currently function
  exactly like the -L and -R subject-line commands.

  What that means is that if someone sends an Areafix request with
  a line that says "%RESCAN DBRIDGE", D'Bridge will rescan ALL areas and
  not just the DBRIDGE echo. This is due to a fundimental design flaw in
  the way the Areafix system was written - it does NOT support select-
  scanning of Echomail areas. To add this feature would require a massive
  rewrite of the existing code. That is not something I'm going to do
  at this time. However, the %LIST command works okay when you put %LIST
  on one line and Echomail areas on the others.

- D'Bridge is now smart enough to understand that %LIST and %RESCAN are
  not valid Echomail areas if ENHANCED AREAFIX is enabled. But, if its
  not turned on and you get those type of requests, they won't be
  processed and instead will be noted in the system log - a possible way
  to catch "abuse" or "pinging" of the system.

- The ENHANCED AREAFIX feature also supports the %HELP command.

- Although the SCHEDULER supports File Sharing and Echofile/TIC processing
  settings, these will not be offered until the Version 3 release.

- Problems with deleting messages in the internal editor and having
  the "message leafing" system mess up should all be fixed now.

- The problem of browsing non-sequential Fido messages and having the
  display/listing mess up in the internal editor should be fixed now.

- The PROCESS XMAIL master-override question has been moved to the XMAIL
  CONTROL screen where it belongs.

- The HUB/ADMINISTRATORS screen is gone forever in this release. I decided
  that its time for it to go, and that if theres problems with D'Bridge,
  that you folks will use due diligence in reporting problems, and I have
  been releasing fixes on a somewhat regular basis...

- The RESTART AFTER NODELIST COMPILE question is gone permanently, as
  nobody has reported anything about it, so I'm assuming its not needed. If
  it is, let me know ASAP; and I'll put it back in immediately. Note that
  this feature is effectively useless anyway; if you need to restart after
  a nodelist compile, you should set the "Auto-compile Nodelists" question
  to NO (in the NODELIST settings screen), and create an event that runs
  shortly before midnight that creates a DBRIDGE.FCN (or DBRIDGE.TCN)
  dummy/semaphore file, to force (or test) the nodelist for compiling.

- Anti-SPAM features/configuration is removed permanently, a much better
  system for anti-SPAM is planned for the future.

- The DBRIDGE.MSR file should be deleted if it exists. It's obsolete.

I hope you enjoy this release of D'Bridge. Please report all problems ASAP
as usual...

Nick Andre
http://www.nickandre.com




D'Bridge 2.68 - March 7 2007
----------------------------

This is a very minor release, but significant for those of you still
running 2.64 because I screwed up the export-code.

- Problems upgrading from 2.64 should be finally resolved, but please back
  up before upgrading just in case.

- DBUTIL MOVE now creates unique filenames when moving NETmail packets.

- DBUTIL PURGE should properly save bodies of messages when archiving mail.




D'Bridge 2.67 - February 24 2007
--------------------------------

This is a very minor release, designed to address some issues with DBUTIL.
Nonetheless, please back up prior to installing.

- Some minor bugs have been corrected in the PURGE code. I'm assuming its
  stable - I've yet to hear any complaints...

- "Bleed-thru" problems with purging should be resolved.

- The total message purge count is now properly reported.

- Message renumbering is back; use DBUTIL RENUM to renumber your message
  directories. You can specify an optional area, ie. DBUTIL RENUM FIDONEWS
  if you want. Renumbering the NETmail directory is NOT supported, however.
  It is recommended that the RENUM be called immediately following a PURGE.
  Note that the renumbering code is CPU intensive and may take awhile to
  finish for those of you with large Echomail configurations.

- The OTHER56K.MCF file has been slightly corrected for new installations.


D'Bridge 2.66 - February 9 2007
-------------------------------

This is a very minor release.

- Problems with upgrading and having the Echomail database lost should be
  corrected in this release. I've tested this with both 2.64 and 2.65.

- A minor bug in the way the AFIXCTRL directory works with Areafix has
  been corrected.



D'Bridge 2.65 - January 14, 2007
--------------------------------

This is a release designed to address several issues for those of you who
are Hubs or co-ordinators of large networks.

A lot of hard work has been done, specifically to DBUTIL. Several bugs have
also been corrected for ITN/IVM flag support and Areafix not allowing a
"master override" to security (ALT+N) to process requests. Please back up
accordingly and report any problems.

- A major bug has been fixed for ITN and IVM flag support in D'Bridge. The
  bug was in relation to outgoing calls.

- The logic behind the translation has been slightly adjusted. If the
  nodelist for the network has the IP address for the system in the phone
  number field already and NO flags like ITN or IVM, D'Bridge will NOT
  attempt to "call" that system, REGARDLESS of the ITM/IVM flag setting.
  You will need to manually specify the address of the system in the
  NODELIST CONFIGURATION screen in FLAG OVERRIDES. For example, if The
  Titanic Board does not have an ITN/IVM flag with its IP address but its
  already in the phone number field, you need to add an entry
  like "25:25/0 ttb.slyip.com" in the FLAG OVERRIDE screen.

  Note that the ITN/IVM flag translation requires this feature to be turned
  ON in the INTERNET CONNECTIVITY screen. It is off by default because most
  of you don't use it.

- Problems with the Areafix system not allowing overrides or instant-
  processing and turnaround should be fixed in this release.

- Stability issues with DBUTIL should be corrected in this release, in
  regards to MOVE-ing mail to directories.

- DBUTIL's message purging code has been COMPLETELY REWRITTEN from scratch,
  to finally attempt to put an end to all the problems that currently
  exist in purging mail. It should now purge mail much faster now,
  and displays a much more graphical progress. This should make it easier
  to diagnose any problems. The purge code also should not touch the
  date/time stamp of messages.

- DBUTIL should no longer choke on any message directory, but if it does,
  it now terminates gracefully and displays a debug screen that will aide
  in diagnosis.

- DBUTIL now reports which messages have grunged date headers as per Roger.

- DBUTIL will check to see if the DBUTIL.BSY flag is over an hour old, if
  so, it will execute anyway and remove that file. This is to prevent
  automated systems from being "stuck in limbo" because of an improper
  DBUTIL shutdown and the busy flag being left over.

  If you DO NOT want DBUTIL to function this way, create a dummy text file
  called DBUTIL.DRF (short for Don't Remove Flag file). If this file exists
  then DBUTIL will not execute if DBUTIL.BSY exists, no matter what
  scenario happens.

- You may now choose to view the hidden "kludge" information of messages
  by answering yes to the VIEW KLUDGES question in the EDITOR OPTIONS screen.
  Note that this only affects the internal message editor only. It has no
  effect for those of you running another message editor or a BBS.

- The internal message editor now correctly displays messages that are
  numbered higher than 8000. It will correctly display messages numbered
  high, up to 32767.

- TAGLINE SUPPORT is no longer enabled by default. You must manually turn
  on support in the EDITOR OPTIONS screen.

- The option to specify the maximum amount of messages able to be read by
  the internal message editor has been REMOVED.




D'Bridge 2.64 - December 29th 2006
----------------------------------

To wish everyone a happy new year, I whipped up this minor release to
finally give D'Bridge support for TAGLINES! (I'm also sick in bed with a
major cold thats going around)

Taglines are just cute "words of wisdom" appended at the end of each
message before the tear line, ie:

 ... Work fascinates me.  I can sit and watch it for hours.
 ... The Big Bang is only the universe rebooting.
 ... NO MESSAGES FOUND. [H]it modem. [S]cream at fido gods. [Y]ell profanity
 ... Death before dishonor, neither before breakfast.

You get the idea.

- You can now specify in the EDITOR OPTIONS screen, if you wish to have a
  tagline attached to each message you write in the internal message editor:

            YES - Append a tagline to all messages.
  ECHOMAIL ONLY - Append a tagline to Echomail messages only.
   NETMAIL ONLY - Append a tagline to NETmail messages only.
            ASK - Ask each time if its okay to add a tagline.
       DISABLED - Shuts off the tagline support.

  The default setting is ECHOMAIL ONLY - Taglines will be added only to
  messages in Echomail areas.

- The taglines are saved in a text file called DBTAGS.TXT that is read and
  indexed by D'Bridge upon starting the internal message editor. Feel free
  to modify this file to whatever you like.




D'Bridge 2.63 - December 29th 2006
----------------------------------

- Yet another minor release that properly imports the Internet settings
  and other stuff from earlier releases. This isn't actually done by
  D'Bridge itself; but by the D'Bridge Update Component (DBUPD) that is
  part of the Setup Wizard.

  Once this release is installed, all settings should be properly imported
  and exported from now on...

- The SAVE files created during the nightly AutoUpdate should be properly
  moved into DBCONFIG.ZIP instead of building up in the directory.

- As per the last release notes (incase you didnt bother to download 2.62),
  DBUTIL only works for the version of DB its released with, and the Setup
  Wizard does a rather thorough inspection of your setup before upgrading.




D'Bridge 2.62 - December 28th 2006
----------------------------------

- This is a very minor release of D'Bridge, with a correction to DBUTIL to
  attempt to solve the issue of old Echomail being scanned out after doing
  a PURGE. DBUTIL should no longer purge the "lastread" pointer file.

- The Setup Wizard now examines your entire configuration much more in
  detail before upgrading and warns you of any potential problems. You may
  also export the warnings to a text file if you prefer.




D'Bridge 2.61 - December 22nd 2006
----------------------------------

This is a minor release done to correct some issues with 2.60. Merry
Christmas everyone, as always, report all problems to me or post in
the DBRIDGE echo on Fidonet.

- The MSGID kludge is now a unique serial number generated from both the
  system date and time. No file is necessary to store this information.
  This should solve any problems with duplicate/unprocessed messages
  resulting from a miscalculated MSGID kludge.

- The Setup Wizard will remove the DBRIDGE.MSG file when upgrading to
  this release, as its no longer necessary.

- The Setup Wizard no longer temporarily unpacks files to drive C. It will
  unpack to whatever drive has read/write access, from C to Z. And obviously
  when finished, the temporary files are removed.

- Pretty sure that the EDITOR INSERT ON/OFF value is properly saved now.

- DBUTIL should no longer "run out of memory" on large systems with
  thousands of Echomail areas. However, the interactive-mode of DBUTIL will
  not show all of the areas - Only the first thousand. All of the commands
  including the CHANGE command will work properly on all areas regardless.






D'Bridge 2.6 - December 17th 2006
---------------------------------

WARNING: The format of the DBRIDGE.ADF database has CHANGED. Any 3rd-party
         utility which makes use of DBRIDGE.ADF will no longer work upon
         installing this version. Please use only the DBUTIL that is
         included in this release. Do NOT use any older version with this
         release otherwise strange and bizarre results WILL happen.

A lot of hard work has gone into this particular release. Please test all
features and report any problems ASAP.

- A critical stability flaw has been corrected in Areafix. The AREAFIX
  ENABLED option in PACKET/MAIL CONTROL has been enhanced so you can now
  set a limit on the amount of areas D'Bridge will process at a time in
  one Areafix request. There is also a new setting, MAX REQUESTS PER
  NODE PER DAY, to prevent "abuse" of Areafix privileges. So basically,
  no one system can request thousands of areas and tie up or crash your
  system entirely. The default value has been set to 50 areas per request
  with 3 requests per day. The maximum value this can be set to is 1024 and
  1024 requests per day.

- In addition to this enhancement, I have added several new lines of code
  in the Areafix system to check for valid requests, bogus entries, and
  other garbage that may potentially crash the system. But with new code
  comes possibly new problems, please report any strange or bizarre
  behavior of the Areafix system immediately.

- Tiny database files used to keep track of the daily Areafix limits are
  stored in the AFIXCTRL (Areafix control) directory off of your QUEUE path.
  These files begin with the S- prefix. They are erased every night at
  midnight during the AutoUpdate routine.

- D'Bridge now stores the M- files in the QUEUE directory instead of
  the AFIXCTRL directory, as it used to be. The Setup Wizard program will
  automatically move any such files back into the Queue directory when you
  upgrade to this release.

- D'Bridge should now be able to handle and process messages up to 32k
  in size as opposed to 16k. IF ANYONE REPORTS A BUG DUE TO THIS CHANGE, I
  WILL CHANGE IT BACK AND RELEASE A NEW VERSION IMMEDIATELY.

- D'Bridge now supports Internet EMAIL and USENET groups, and is now fully
  integrated with VSOUP and SOUPGATE. Support can be configured in the newly
  redesigned INTERNET CONNECTIVITY screen. These tiny programs now allow
  D'Bridge to fully support Internet E-Mail and USENET groups from the
  Internet. VSOUP/SOUPGATE is configured via the INTERNET CONNECTIVITY
  screen, just like BINKD. VSOUP and SOUPGATE now ship with D'Bridge to
  get you up and running with as little work as possible.

  Note that in this release, USENET group functionality will require a little
  more configuring, in the way of scheduled events which call the VSOUP
  and SOUPGATE programs manually. This release was done to "get the ball
  rolling" and you are more than welcome to contact me for further
  assistance regarding USENET configuration.

- Although I wrote in the help system that when the VSOUP/SOUPGATE address
  is specified D'Bridge will adjust the rest of the setup accordingly, THIS
  IS NOT THE CASE IN THIS VERSION. You will need to manually add whatever
  gateway address you've decided to use to all of your ROUTING in scheduled
  events, and the Forced Priorities and Areafix information screens
  in the PACKET/MAIL CONTROL menu.

- The internal message editor now fully supports Internet E-Mail addressing
  provided that the VSOUP/SOUPGATE information screen in INTERNET
  CONNECTIVITY is properly configured. The SOUPGATE program is auto-
  matically called during a Queuescan to "pack" Internet EMAIL messages
  for further processing by VSOUP. VSOUP is also automatically called to
  send and receive Internet mail.

- In the tradition of the "keep it simple" philosophy of D'Bridge, you can
  just read and reply to Internet EMAIL as you do Fidonet NETmail.

  That means, you DO NOT "address" the SOUPGATE software; D'Bridge takes
  care of that automatically. When you compose an Internet EMAIL message,
  you just type in the EMAIL address and away you go. For example if
  you want to send a message to John Doe at his Hotmail account, just type
  in his address, johndoe@hotmail.com. Gone forever are the days of having
  to address the gate as "UUCP", put "To:" in the body of the message, and
  other extra work. And when you receive replies, D'Bridge automatically
  translates them from SOUPGATE into "non-geek jargon", to keep things as
  seamless and integrated as possible.

- BINKD support will be disabled if you specify 0 (zero) as the BINKD PORT.

- BINKD must now be ran as a "server" process (ie. running it in another
  window on your operating system). For stability reasons D'Bridge no
  longer starts BINKD to send/receive mail in "client" mode.

- DBUTIL will NOT create a log file of any activity if you create
  a semaphore/dummy file called DBUTIL.NLG. This is to avoid having the log
  file for DBUTIL grow out-of-hand when purging/processing large amounts of
  messages.

- DBUTIL should properly report now which areas have grunged message
  headers. I can't exactly duplicate this problem, but I did change one or
  two things apparently wrong in the code.

- Only one "copy" of DBUTIL can execute at a time, this is controlled by
  the DBUTIL.BSY semaphore file.

- The MAKE DBRIDGE.NQS FILE debug feature has been removed - it is now
  standard that D'Bridge creates the DBRIDGE.NQS file after unpacking mail.

- The option to begin tossing messages at 2.MSG has been removed, D'Bridge
  should now begin unpacking at 2.MSG regardless (except if its NETmail)

- XMA/XMAIL DEBUGGING in HUB/ADMINISTRATORS has been moved to the XMAIL
  CONFIGURATION screen. The long-obsolete "XMAIL ARCHIVE SIZE" feature has
  been removed, Chris never finished it and it was just simply useless code.

- The SCREEN EFFECTS DEBUG option in HUB/ADMINISTRATORS has been removed.

- The ROLLBACK/LEGACY SUPPORT feature in HUB/ADMINISTRATORS has been
  removed to save code and space. If you don't like this 2.6 release, and
  need to rollback, you will need to "edit out" the extra variables that
  the earlier releases won't understand.

- D'Bridge now supports large drives "natively", as in, it now acts
  with the LARGE DRIVE SUPPORT permanently enabled. The feature has now
  been removed from HUB/ADMINISTRATORS and is no longer necessary.

- The MAXSRINDEX debug option has been moved to the SETUP EDITOR OPTIONS
  screen.

- The Anti-SPAM and TWIT filters have been moved to the HUB/ADMINISTRATORS
  screen. There is no more seperate ANTI-SPAM setup screen. That has been
  entirely removed to reduce code and save space. The Anti-SPAM and TWIT
  filters are still NOT working, but should be for the next release.

- DEBUG QUEUE ERRORS in HUB/ADMINISTRATORS has been removed.

- The settings of REBUILD QUEUE and SCAN ECHOMAIL AREAS in the EDITOR
  OPTIONS screen are now properly saved in this upgrade... they were never
  saved in ANY release for that matter due to the way Chris wrote the code.

- The Setup Wizard can be told to install D'Bridge under a Terminal Server
  environment or Remote Administrator setup by pressing F4 when the
  installation begins.

- Dozens of other code improvements have been done, mostly minor things.




D'Bridge 2.55 - July 5th, 2006
------------------------------

- This is yet another minor release that addresses some issues in the Setup
  Wizard. There are no corrections to D'Bridge itself in this release. It is
  now possible to install D'Bridge from a CD-ROM drive or other read-only
  media. If you don't care about this feature, you don't need to install
  this release on your system.


D'Bridge 2.54 - June 26th, 2006
-------------------------------

- This is a very minor release. The tagline-fix in 2.53 was not adding the
  origin line. This should be fixed now...



D'Bridge 2.53 - June 25th, 2006
-------------------------------

- This minor release *should* correct the duplicate-tagline problem on
  messages created by 3rd-party products and then exported out by D'Bridge
  via an EchoScan.



D'Bridge 2.52 - June 24th, 2006
-------------------------------

- This is a very minor release that corrects the "BINKD extensions cannot
  be loaded" problem some of you are having.

- D'Bridge should immediately "turn around" now on completed BINKD sessions. 



D'Bridge 2.51 - June 13th, 2006
-------------------------------

- This is a minor release which adds the ability to define a "pickup-only"
  listing in the INTERNET CONNECTIVITY screen for BINKD.

  If you do not wish to connect with a remote system, but still wish to
  have the remote system pick up its mail, specify "PICKUPONLY" as its
  address. For example:

             1:229/2000 PICKUPONLY NICKS_PWD NANDRE

                        ^^^^^^^^^^

  specifies that Rob's system can call me but I should not call him.

- The help screen for the above change has been updated.

- It may be necessary to verify the BINKD ENABLED setting in INTERNET
  CONNECTIVITY once this upgrade has been applied.

- Some minor bugs in the Setup Wizard have also been corrected.

Nick Andre
ANDRE CONSULTING



D'Bridge 2.5 - June 12th, 2006
------------------------------

This is a major release of D'Bridge which now features a working BINKD
solution, in addition to a large number of bug fixes and corrections.

The auto-addressing features I'm adding are not quite finished - I'd say
about 90% done - the other 10% being minor coding. So, the auto-addressing
will be delayed until the next release of D'Bridge. Internet EMAIL and
Usenet groups are also on the works for the next release.

The Anti-SPAM features are DISABLED in this release - I'm not comfortable
with the code and feel that its too unstable after some last-minute testing.
Anti-SPAM features will be enabled in a future release.

I will NOT participate in ANY "political" discussions about the support
for Internet nodelist flags. I will leave it up to you to decide if you
wish to use that feature and if not, simply shut it off in the setup screen.

This was by far the most difficult version to design and compile. Over
several thousand new lines of code were written for this release and this
by far pushes the limit of what can be done for a DOS-based mailer.

Laura and I sincerely hope that all of you enjoy this release and as
always we look forward to your comments and suggestions.

- The D'Bridge INSTALL program has been enhanced and several dozen
  improvements were done to the way it works, especially with custom-
  installations. It is now possible to do a TYPICAL or CUSTOM installation
  and have the options configured accordingly.

- This release has fully-functional BINKP client and server capabilities,
  and has been designed and tested with fairly large amounts of Queue
  entries. That being said, I am by no means a major mail "hub" so I
  would certainly appreciate some testing and feedback with this release.

- The INTERNET CONNECTIVITY screen and all work on internal BinkP support
  has been totally redesigned and rewritten from scratch. Out of respect
  for those of you who are "hanging on" for this feature to be hard-coded,
  I have included custom copies of the public-domain BINKD program. Don't
  be fooled, however. This release of D'Bridge is designed to work hand-in-
  hand with BinkD and D'Bridge will automatically configure the setup file
  for this program. The INTERNET CONNECTIVITY screen basically matches the
  setup file of the BinkD program except that it will specifically write
  D'Bridge values and settings to the BinkD program setup file. Whenever a
  change is done to the INTERNET CONNECTIVITY screen, or a Queue entry
  exists that is defined in BINK SESSIONS, the BinkD configuration is
  automatically updated. I have included the OS/2 and Windows version of
  BinkD and there is a setting in INTERNET CONNECTIVITY to choose which
  one to run. Go check it out.

- If you already have an existing BINKD configuration and you are running
  D'Bridge under OS/2 WARP or Microsoft Windows, you can copy the BINKD
  executables to the D'Bridge directory and run BINKD with "DBRIDGE.BNK"
  as the configuration file for daemon (server) usage.

  YOU WILL NEED TO MIGRATE YOUR EXISTING BINKD CONFIGURATION MANUALLY, as
  it will take a considerable amount of code to implement an "import"
  feature... but if you already have a working BINKD setup, chances are
  you probably don't want to screw around with it until you've tested this
  one first.

- For Windows 95, you will need to install the "Winsock 2 Update" available
  from Microsoft's website. This update is NOT required if you are
  running Windows 98, ME, NT, 2000 or XP.

- EMX version 0.9D, available from ftp://hobbes.nmsu.edu/pub/os2/dev/emx,
  is required for BINKD if you are running the OS/2 WARP operating system.
  The EMXRT.ZIP file should be unzipped to C:\OS2\APPS\DLL, although it
  shouldn't be necessary to reboot the computer.

- If you already have an existing Linux BINKD configuration, and you are
  running D'Bridge using Bochs, DOSEMU or DOSBOX, you can simply point
  your existing BINKD binaries to use the DBRIDGE.BNK configuration file.
  It may be necessary to "mount" your D'Bridge directory to the
  appropriate BINKD directory on the Linux filesystem.

- BinkD works in one of two ways for D'Bridge, depending on the "server"
  setting in INTERNET CONNECTIVITY:

  If running in SERVER mode, D'Bridge will "swap out" and call DBUTIL MOVE
  to create a mail bundle specifically for BinkD to use. When BinkD detects
  the mail bundle, it will attempt to dial-out over the Internet and send
  the mail for the system. It is up to you to ensure that BinkD is running.

  EVERY TIME THE QUEUE IS RESCANNED, THE BINKD CONFIGURATION IS UPDATED.
  This may cause more disk access on your computer, but this is normal.

  When ran in CLIENT mode, D'Bridge will update the BINKD configuration
  during the QueueScan, but will immediately call the BINKD program to
  send out the mail. It may take up to a full minute for the BINKD program
  to exit back to D'Bridge. This is normal. If you're not that patient, you
  should run in SERVER mode (ie. run BINKD in another "window" on your
  operating system)

  NOTE THAT IN CLIENT MODE, INBOUND BINKD CONNECTIONS WILL NOT BE RECEIVED.

- Again, D'Bridge maintains the configuration of BINKD automatically. DO
  NOT, UNDER ANY CIRCUMSTANCES, MODIFY ANY CONFIGURATION FILES RELATED
  TO BINKD. Do NOT examine any configuration files of BINKD while D'Bridge
  is running at the same time; otherwise a sharing violation may occur.

- The DBUTIL component has been updated, redesigned and enhanced to fully
  integrate itself with the BINKD program, and has been enhanced to
  operate along with the BINKD configuration file.

- Do NOT, under ANY circumstances, specify Domains in the address questions
  in BASIC CONFIGURATION. You specify the domain matching in the INTERNET
  CONNECTIVITY screen.

- DBUTIL has been enhanced to include support for BINKD and has been
  designed to interoperate with the BINKD features. Therefore, it is
  absolutely crucial that you install both the Internet features and DBUTIL
  if you select CUSTOM INSTALL in the Setup Wizard.

- A new option in INTERNET CONNECTIVITY also allows you to translate the IVM
  and ITN flags in nodelist entries to actual IP addresses to dial for the
  VMODEM product by Ray Gwinn (or any other Virtual Modem product). You can
  choose to translate IVM or ITN or both (or none, obviously). The default
  setting is NONE. When this setting is changed, you will need to rescan the
  outbound queue. The call will be subject to the same costing as a dialup
  call as defined in COST/ACCOUNTING and the currently scheduled event.

- The D'Bridge INSTALL program now extracts/verifies files almost 300%
  faster than before.

- D'Bridge now fully supports multi-user, multi-tasking environments, by
  enabling the "MULTI-LINE" feature in the COMM/MODEM SETUP screen. When
  this feature is enabled, you MUST start D'Bridge with the appropriate line
  number, ie. DB /1, DB /16, etc etc. Otherwise, D'Bridge will default
  to line one. You can now run several "copies" of D'Bridge this way, all
  sharing the same configuration but using different modems or FOSSIL ports.

  When the MULTI-LINE feature is enabled, each line has its own unique
  configuration for the COMM/MODEM SETUP screen. The upperleft-hand corner
  of the screen will show which current line is running.

  WARNING: It is absolutely crucial that no two lines share the same port.
           If you attempt to assign the same serial port, strange and
           bizarre results will happen with your operating system. OS/2
           dies. Windows will stop with the infamous "blue screen of death".

           The only exception to this warning is the NetFOSSIL product by
           PC Micro Incorporated (www.pcmicro.com) Their virtual COM ports,
           although they show up as one address and IRQ, are safe to use
           with D'Bridge. NetFOSSIL is for Windows NT, 2000 and XP only.
           With NetFOSSIL (and possibly others like it), it is safe to use
           the same COM ports in multi-line D'Bridge.

- Note that although the multi-line features work, they all share the same
  schedule. Originally I intended to have multi-line scheduling like the
  way its done in Frontdoor and InterMail, but due to the way Chris designed
  the code, it is going to take a massive rewrite of the entire way that
  scheduling is handled in D'Bridge. Multi-schedule events produced a few
  instability problems in several critical functions during 2.5's testing
  stages. At the very last minute, much to my displeasure, I had to put the
  scheduler code back to the way it was in 2.41.

  Therefore, as a workaround, you will need to ensure that any multi-line
  DOS events do not "collide" with eachother (ie. use dummy files to check
  to see if a DOS event is already running). Feel free to post in the
  DBRIDGE echo on Fidonet for more help and explanation.

- D'Bridge should now support DigiBoard ISA and DigiBoard PCI (Intelligent
  and non-Intelligent) serial ports. The new code has been tested with an
  older DigiBoard PC/X 8-port card.

- The COMM/MODEM SETUP screen in D'Bridge -should- now support non-standard
  COM ports beyond COM9 (ie. COM10, COM11, etc), up to COM99.

- D'Bridge now supports the "2K" releases of Ray Gwinn's SIO serial drivers
  for OS/2 WARP, including the virtual modem (VMODEM) programs.

- D'Bridge should no longer probe the modem/serial hardware in the
  COMM/MODEM SETUP screen, in order to avoid certain problems with
  Windows NT, 2000 and XP.

- D'Bridge should no longer cause "The COM port request is already in use"
  problem in OS/2 WARP, when the newcomer installs it for the first time
  and immediately enables the MULTI-LINE support.

- D'Bridge actually should no longer cause ANY "COM port in use" errors
  in your operating system when you install for the first time, since it
  is now MANDITORY that the proper COM port address and IRQ is specified.

- D'Bridge no longer randomly crashes under Desqview.

- D'Bridge should no longer randomly freeze when running on a Tandy 1000
  system with DOS 3.3, DOS 5, DOS 6, 6.21 or 6.22.

- D'Bridge now gives up more idle-time to the CPU when its doing nothing.

- D'Bridge should now co-operate more efficiently with the TameDOS product
  written by David Thomas.

- The method that the modem/serial configuration is stored has now been
  changed. Modem information is now stored as COMM.1, COMM.2, etc etc,
  for MULTI-LINE operation.

- Modem/serial information is no longer stored in DBRIDGE.PRM or in
  exported configuration files. If you need this feature, please let me
  know ASAP.

- A new menu option MODEM RESULT CODES in BASIC CONFIGURATION allows you
  to specify the result codes that your modem reports back to the computer.

- The way D'Bridge stores ".DSI" (Daily Schedule Information) files has
  changed to facilitate the new MULTI-LINE support. Instead of storing
  the DSI in DBRIDGE.DSI, it stores in LINE1.DSI, LINE2.DSI, and so forth.
  Please adjust any events and/or 3rd-party utilities that may use the file.

- D'Bridge now stores Unevent Event History (DBRIDGE.UEH) and Mail Event
  History (DBRIDGE.MEH) differently now for MULTI-LINE operation, such
  as LINE1.UEH, LINE2.MEH, etc etc. The MEH and UEH files are used during
  creation and maintenance of a QueueScan. 3rd-party utilities should not
  be affected by this change.

- Note that for testing purposes, deleting a DSI file for the appropriate
  line will cause D'Bridge to run as if it were being run for the first
  time... ie. all events that ran that day will be ran again.

- The way the "AutoUpdate" routine works has been rewritten and updated to
  facilitate multi-line operation. Instead of having files like
  SAVE-FRI.DSI, SAVE-SAT.DSI, SAVE-SUN.DSI, and so forth, the filename is
  now the same except that the .DSI extension is replaced by the number
  of the line. So, if AutoUpdate exported the DSI on line 3 for Saturday,
  the result would be SAVE-SAT.3.

- If you run batch files that "clean up" the SAVE-*.DSI files, you should
  modify them as per the above notice.

- The INSTALL program will properly upgrade and make adjustments to
  the D'Bridge directory as per the above multi-line filename changes.

  *HOWEVER*, if you are ROLLING BACK ("downgrading") to a prior release, you
  will need to perform the following MANUALLY.

  If these precautions are NOT followed, then when you install the prior
  release, you will either experience difficulty in migrating your setup
  back to the prior release, or the prior release will execute all mail
  events as if they haven't been ran already.

         - Delete any *.DSI files in your D'Bridge directory.
         - Delete any "LINE*.*" files in your D'Bridge DATA directory.
         - Export a ROLLBACK configuration file (explained below)
         - Install a version of D'Bridge prior to 2.5.
         - Manually recompile the nodelist.
         - Ensure the Queue is rescanned.

- A new option in HUB/ADMINISTRATORS allows you to automatically restart
  D'Bridge after a nodelist compile. This option was once hard-coded and
  solved some problems for people, but created problems for others. So its
  back again as an option, and its left as NO (disabled) by default. Do not
  enable this setting unless restarting-after-compiling solves problems.

- A new option in HUB/ADMINISTRATORS enables you to shut off the unnecessary
  "Unable to write UEH/MEH" messages that may pop up from time to time,
  by changing the DEBUG QUEUE ERRORS settings. Its not so much an error as
  it is a limitation with the way the code works under OS/2 or Microsoft
  Windows environments. D'Bridge eventually recovers from such a condition.

- For Ward, you may now specify the maximum number of Fido *.MSG files able
  to be handled by the internal message editor by changing the new "EDITOR
  LIMITS" variable in HUB/ADMINISTRATORS. The default is 8000. The maximum
  that may be specified is 32,766.

  WARNING: Changing this variable also changes the amount of free memory...

- D'Bridge now features ANTI-SPAM features, and those can be configured in
  the ADVANCED CONFIGURATION screen. You may choose to filter by FROM
  or SUBJECT. The SPAM filter is very primitive and only checks for
  the presence of the keywords you specify. When such a keyword is
  encountered, D'Bridge will NOT toss (process) that message, NETmail
  or Echomail - ***AND ANY DOWNLINKS WILL NOT RECEIVE THOSE MESSAGES***

  When reading a message in the internal editor, you may now press the S
  key to indicate that the FROM and SUBJ of the message is SPAM. Then
  D'Bridge will no longer process messages matching that criteria in
  the future.

     **** NOTE **** ANTI-SPAM FEATURES ARE DISABLED IN THIS RELEASE

- The internal editor now supports a TWIT FILTER. When this option is
  enabled in the ADVANCED CONFIGURATION screen, messages will NOT be
  displayed in the internal editor that match the criteria you specify.
  Note that the TWIT filter does not affect any messages sent to other
  systems, so a message that arrives from someone on your TWIT list will
  still be sent to any downlinks.

  When reading a message in the internal editor, you may press the T key
  to indicate that the person sending the message (the FROM field)
  should be marked as TWIT.

     **** NOTE **** TWIT FILTERING IS DISABLED IN THIS RELEASE

- Removing SPAM or TWIT filter criteria is as easy as removing them from
  the ANTI-SPAM screen.

- The ANTI-SPAM and TWIT FILTER options are DISABLED by default.

- You may now specify packet files (*.PKT) of unlimited size by changing
  the XMAIL PACKET SIZE option to zero (0) in the XMAIL CONTROL screen.
  For those of you that "toss" large amounts of mail, this will cause
  the D'Bridge XMAIL processor to create one huge .PKT file for a system
  instead of multiple PKT files. This may improve efficiency, and is a
  feature found in other "tosser" programs so I'm including it here as well.
  The help screen for this feature has also been updated. One such use for
  this feature would be for local LAN use or in situations where it is
  necessary to decompress the XMAIL bundle in a DOS batch file.

  WARNING: Under normal use, the XMAIL PACKET SIZE option should NOT be
           changed unless you are a Hub or administrator whoes setup would
           benefit from having packets with no "limits".

- A stability bug in the way that D'Bridge checks and analyses the Carrier
  Detect (CD) signal from the serial port/FOSSIL driver has been corrected
  and totally rewritten. The carrier-detection code is now 100% compatible
  with both "real" serial ports, and virtual ports such as FOSSIL ports
  under the OS/2 WARP operating system, or NetModem ports under Windows.

  WARNING: Ray Gwinn's VMODEM product does NOT report a carrier signal
           to D'Bridge until the result code has been sent back, and there
           may be a slight delay (a few milliseconds) between the presence
           of the carrier signal and the result code. But that few
           milliseconds is an eternity to D'Bridge. It may result in lost
           calls when a user connects via. Telnet, because during those
           few milliseconds delay, VMODEM is allocating memory and system
           resources to operate the modem port. For this reason I
           strongly recommend that you use VMODEM on a high-speed Internet
           connection such as cable or DSL (ie. Bell Sympatico), and make
           sure your D'Bridge system is running on a Pentium-2 or faster
           computer. 

- A minor bug has been fixed in the D'Bridge EMSI code for dialup sessions,
  and now makes it possible to do EMSI over Telnet, using virtual-modem.
  Gone forever are the warnings about high-ascii and other such nonsense.

- A minor cosmetic bug has been fixed in the SESSION INFORMATION screen
  during an EMSI session, and D'Bridge now displays "OTHER" instead
  of "DATA" so newcomers won't be confused what "DATA" means: OTHER means
  any other file attachments besides NETmail and XMAIL.

- A minor cosmetic bug has been fixed in the SYSTEM LOG screen for the
  EMSI fix mentioned above.

- Problems with importing configuration files should now be a thing of
  the past. Unknown keywords and variables are simply ignored.

- You can now export a configuration file that should be 100% backwards
  compatible with prior releases (including the legacy 1.xx series), by
  enabling the "ROLLBACK FILE SUPPORT" option in HUB/ADMINISTRATORS. This
  will tell D'Bridge NOT to export any Internet and multi-line settings.

- A new command-line option in the mailer, ROLLBACK, does the same thing
  as the EXPORT command except it won't export the settings for the new
  features, same as the feature explained above. ie. DB ROLLBACK DB.CFG will
  export a compatible CFG file for older releases. It will perform this
  function no matter if the ROLLBACK FILE SUPPORT option is enabled or not.

- The NEW ECHOMAIL LINK and REQUEST ECHOMAIL LINK screens have been slightly
  enhanced to allow specifying conferences with large Echomail tags, such
  as Internet Usenet groups... a feature I plan to integrate into D'Bridge
  in the next release or so.

- NETmail messages addressed to SYSOP will now trigger the YOU'VE GOT MAIL
  option if enabled.

- DBUTIL now automatically deletes the message bases in the Renegade BBS
  software when DBUTIL DELETEDOS is used. It doesn't matter what version
  of the Renegade BBS software you're using.

- Due to a fundimental design flaw in the ECHOMAIL AREA EDITOR, you should
  NOT delete the very last area from the database, if you plan to later
  "clean up" your message directories with DBUTIL DELETEDOS. If the last
  area must be deleted, you should first create a "dummy" area after that
  record so the first one can be deleted properly. Failure to do so will
  result in directories not being cleaned up properly in DBUTIL DELETEDOS
  because the last record is not marked for deletion - its nuked altogether.

- Various help screens have been updated, corrected, and in some cases
  rewritten altogether to keep the help for 2.5 as up to date as possible.

- You may now specify the ADDRESS/AKA of an Echomail area to change globally
  in DBUTIL. This allows DBUTIL to manage multiple Fido-networks properly
  when used with the GROUP SORT and GROUP ACCESS functions. The ADDRESS/AKA
  feature only works in the "GUI" portion of DBUTIL only - it will NOT work
  with the AUTOASSIGN parameter, ie. DBUTIL AUTOASSIGN.

Nick Andre
ANDRE CONSULTING




D'Bridge 2.41 - April 1st 2006
------------------------------

This is a very minor release, but now includes the entire source code
to the DBUTIL program along with the technician's manual for those of you
who are interested in my work. DBUTIL is written in Visual BASIC so it
should be easy to understand how things work. The source code and
technicians manual is now installed by clicking on the "Source code"
button in the INSTALL program.

- An issue with DBUTIL MOVE not computing the FTSC-name-control file
  has been corrected.

- When more than 36 XMAIL bundles are moved in one day for one node address
  using DBUTIL MOVE, the archive number is reset back to zero and the
  counter starts over.



D'Bridge 2.4 - March 29th, 2006
-------------------------------

This major release of D'Bridge now bring things "up to snuff" with running
DB on more modern computers such as Pentium 3's, 4's, celerons, dual-core
chips and on computers with extremely large hard drives. D'Bridge should now
function 100% when running under "emulator" environments (such as DosEmu,
Bochs or DOSBOX). It also adds support for debugging the system timer. A
minor bug in DBUTIL has also been fixed.

WARNING: It is absolutely imperative that the "AFIXCTRL" directory exists
         off of your Queue directory (ie. C:\DBRIDGE\QUEUE\AFIXCTRL). The
         DBUTIL program makes extensive use of this directory for the MOVE
         command. If the directory doesn't exist, the MOVE command will FAIL.

- D'Bridge will now properly toss mail on partitions larger than 2 gigabyte,
  by enabling the "Large drive support" option in HUB/ADMINISTRATOR. This
  option is OFF by default.

  This option will allow D'Bridge to process mail on hard drive partitions
  larger than 2 gigabytes. Basically, all disk-space checking is DISABLED
  regardless of what is defined in DISK SPACE PARAMETERS, but some internal
  safeguards are turned off as well.

  Please do not enable this option unless you are running D'Bridge on a
  computer that has a hard drive partition larger than 2 gigabytes in size,
  or you are running D'Bridge under an "emulator" such as DosEmu, Bochs
  or DOSBOX.

- It is now possible to disable all the "animations" and other fancy timer
  stuff in D'Bridge, by disabling the "Screen effects" option in HUB/
  ADMINISTRATORS. Its turned on by default. Shutting it off will stop
  all the animated zooming, screen fades and other screen-related effects,
  except of course the built-in screen saver. This should solve problems
  with running D'Bridge under OS/2 WARP or on extremely-fast CPU's, or any
  DOS environment where the screen effects are obviously causing a problem.

- It is now possible to debug the system timer in D'Bridge. D'Bridge
  computes its own "delay" timer from calculating the number of BIOS ticks
  per second. By default, this is set to zero, telling D'Bridge to
  automatically compute the BIOS ticks. But changing this value to anything
  but zero will manually set the BIOS ticks. Setting the ticks manually may
  be necessary to correct problems with D'Bridge running on more modern
  computers such as Pentium 3's, 4's, Celerons, Dual-Core, etc.

  This option should NOT be changed unless you are an experienced system
  administrator and you know your hardware "inside-out". Strange
  and bizarre results may happen if the system timer is incorrectly set.

- Under rare circumstances, DBUTIL MOVE would not "move" the mail properly.
  This has been fixed for good this time. Instead of DBUTIL.DAT, the system
  will create individual data files in the QUEUE\AFIXCTRL directory that
  control the FTSC-compliant filenames generated by DBUTIL.

- DBUTIL now creates the semaphore (dummy) files DBRIDGE.RSN whenever the
  MOVE command is used, so that D'Bridge is "forced" to rescan the Queue
  when completed.

- For those of you that use the shareware client/server program Internet
  Rex, you should be aware that it may be UNSTABLE reading the D'Bridge
  Queue directly. I highly recommend that you use DBUTIL MOVE to move your
  mail to individual directories for your nodes.




D'Bridge 2.3 - March 25th, 2006
-------------------------------

This is a huge release that fixes a variety of problems, including one
major security flaw. Although it doesn't look like it on the outside,
there is plenty of new code in this release. This release was one I've
wanted to do for weeks, but just haven't had the time to work on it until
now. Please upgrade your installation to this release as soon as possible.

YOU MUST RUN "DB EXPORT DBRIDGE.AUT" BEFORE RUNNING THE INSTALL PROGRAM.
Failure to do so will cause problems. The change was done to ensure that
all of you are taking proper precautions and steps to upgrade your systems.

WARNING: Rolling back to a prior version once this release is installed is
         NOT recommended. However, if you must rollback, please move the M-
         style queue entries from the AFIXCTRL directory back to the QUEUE
         directory. For example:

                   CD \DBRIDGE\QUEUE\AFIXCTRL
                   COPY *.* ..
                   DEL *.*
                   CD ..
                   RD AFIXCTRL

         If C:\DBRIDGE\QUEUE is not the directory your Queue files are
         located in, substitute it for the correct directory.

- The Areafix "M-" style Queue entries have been modified to correct a
  security issue when using D'Bridge with Internet Rex, a shareware
  Internet client/server program.

  The security issue affects ALL versions of D'Bridge prior to this one,
  including the legacy 1.xx series (ie. 1.58, 1.60, 1.70, etc)

  Internet Rex has the capability of interfacing with the D'Bridge queue.
  Any entries in this directory will be converted to proper FTSC packet/
  archive names for transfer via the Internet. However, if Internet Rex
  finds any M- style entries, it will also send them out. M- style entries
  are an essential portion of the Areafix system in D'Bridge. By carefully
  manipulating Internet Rex, it may be possible to download a list of
  another system's connected areas.

  To correct the flaw, the "M-" style Queue entries are now stored in a
  subdirectory called "AFIXCTRL" off of your Queue directory. So if your
  Queue directory is C:\DBRIDGE\QUEUE, you will now find a new directory
  called C:\DBRIDGE\QUEUE\AFIXCTRL where all of the M- stuff is located.

- Because this is a fundimental change to the way the Queue system works
  in D'Bridge, this may render some 3rd-party utilities useless. Please let
  me know if this is the case and an alternate solution will be designed.

- The DEBUG/SUPPORT menu is now called HUB/ADMINISTRATOR OPTIONS, and the
  previous XMAIL debugging options from the 2.2 release have been moved
  into this menu screen.

- The INSTALL program has been vastly improved, and will scan your Queue
  directory for any M- style Queue entries and move them to the above-
  mentioned AFIXCTRL directory accordingly. I'm pretty sure that all of
  the bugs in the install program are gone now. If theres any, let me know.

- Work has begun on support for Return Receipt Requests (RRQ's), although
  the option is there now in SETUP -> EDITOR OPTIONS, this feature will not
  be completed until the next release of D'Bridge.

  A Return Receipt Request (RRQ) kludge is a flag on a NETmail message to
  trigger D'Bridge to send the sender of the message a "receipt"
  acknowledging that the message has been read by the receiver.

  When a RRQ kludge is encountered, D'Bridge will write a "receipt" NETmail
  to the sending system indicating that the original message has been read
  for the first time by the receiver. The receipt that gets sent back is a
  simple NETmail message indicating the time and date that the message was
  read, along with a copy of the original message. The receipt is sent back
  to the receiver during the next QueueScan, and is subject to the routing
  defined in the SCHEDULER.

  Note that the RRQ kludge feature only works for the built-in internal
  message editor. It will NOT work with GoldED or any external editors.

  The RRQ kludge feature has three options:

  RRQ KLUDGE: Yes, Ask, No

  YES - The editor will acknowledge RRQ's automatically without your consent.

  ASK (Default) - The editor will display a pop-up window when it encounters
  a message with the RRQ kludge and ask you if you wish to acknowledge
  receipt.

  NO - The editor will not acknowledge RRQ's.

  The internal editor's "Add Return Receipt" option will only show up in
  the menu when you are writing a NETmail message only. It will not be shown
  when writing Echomail messages or if the RRQ kludge feature is turned off
  altogether in EDITOR OPTIONS. The help screen for the RRQ kludge and the
  internal editor menu commands have been updated accordingly.

- D'Bridge now creates a new semaphore file called DBRIDGE.NQS whenever a
  new QueueScan has just been performed (manually or automatically). This
  new semaphore file can be used by 3rd-party Internet clients (like
  Internet Rexx) to indicate that D'Bridge has finished scanning the
  outbound Queue. This feature is triggered ON or OFF (ON by default) in
  the HUB/ADMINISTRATOR menu.

- D'Bridge no longer unpacks Echomail starting at message 1 if there are no
  messages in the directory. It will now start at message 2. This change was
  done, again, to allow 3rd-party programs to properly import mail from
  D'Bridge. This feature is triggered ON or OFF (Off by default) in
  the HUB/ADMINISTRATOR menu.

- D'Bridge does not fill in "201:ALL" for Automatic Session Passwords in
  the SECURITY screen for newcomers.

- DBUTIL PURGE no longer renumbers messages. Nobody likes this feature so
  I got rid of it. Delete the DBRIDGE.NRN or DBUTIL.NRN files if they exist.

- And the MOVE command in DBUTIL has been rewritten from scratch. There
  should be no more issues with moving any mail whatsoever.

- DBUTIL MOVE now works with files up to 2 gigabytes in size.

- The unpack/upgrade/copying process in the INSTALL program has been
  rewritten from scratch. Again, you MUST export your configuration BEFORE
  upgrading to this release. This is MANDITORY.

I hope you enjoy this version and look forward to your feedback.


Version 2.2 - March 5th, 2006
-----------------------------

This minor release adds two new features for XMAIL: "Process XMAIL Yes/No"
and "Debug XMAIL Yes/No" to the DEBUG/SUPPORT screen.

PROCESS XMAIL - If this is set to YES, any Netmail that contains the XMA/
(default: YES)  XMAIL flag will be packed out as an XMAIL bundle; otherwise
                if the option is set to NO, it gets treated as a
                normal "Queue" entry, subject to the routing conditions set
                up in the SCHEDULER.

  DEBUG XMAIL - Any Netmail messages with the XMA/XMAIL flag that are
(default: NO)   processed by your D'Bridge system, will now display the
                current message number, from/to/subj/address as well as the
                archive name in the system log if this set to YES. Note that
                this WILL cause the system log to grow quite a bit in size.

Note that these two new features are only provided for those of you who
wish to diagnose/troubleshoot in-transit NETmail that is processed. DO NOT
change these parameters unless you are an experienced D'Bridge administrator.

- The help screens for these two features has also been updated accordingly.

- Cleaned up some code in the internal editor, please test all functions.


Version 2.1 - February 27th, 2006
---------------------------------

This interim release corrects some minor issues with stability and security.
As usual, please back up your D'Bridge directory before installing.

- Pretty sure I figured out the large-message crash problem.

- Dozens of minor corrections have been done to the mailer source code.

- Rewrote the entire routine for handling modem hangup/constant carrier
  signal errors (when the system starts up or is idle) The CD mask can no
  longer be set or changed via. a DOS variable; this was a debugging
  feature that Chris left in from the non-FOSSIl days and I thought it was
  utterly useless. Several "+++" escape sequences, along with DTR dropping
  and ATZ'ing are now done to help eliminate the rare CD error problem.

- Fixed a problem where under rare circumstances, the "You've Got Mail"
  feature may randomly crash D'Bridge if you receive a large amount
  of personal mail.

- D'Bridge no longer performs a timesync on startup if the system date is
  earlier than the release date - didn't want to scare newcomers. :-)

- You can now force a system restart/recycle every time the nodelist is
  compiled by creating a semaphore (dummy) file called DBRIDGE.RNC in
  your directory. D'Bridge will always restart after a nodelist compile
  if that dummy text file is there.

- DBIS developement is currently on hold due to lack of personal time.

- A newer DBNET file has been included in this release.




Version 2.00 Beta Release #9 - January 24th, 2006
-------------------------------------------------

This is a MINOR release, containing the same code as Beta Release #8 but
recompiled using a slightly different method of initializing TCP/IP sockets
and stacks. The web server is enabled but BinkP, FTP, Telnet and DynDNS are
still disabled. It may not be necessary for you to install this update.

PLEASE NOTE: My work schedule is busy again, folks. Updates after BR#9 will
be few and far between. Expect a 2.1 release sometime next month which
will have all Internet features enabled.

We're moving to a new apartment on the first of the month. I will not be
able to answer home telephone calls about D'Bridge for the first week or so.

- DBIS has been recompiled to NOT require Winsock-2 specific code while
  running under Windows 95 (A, B and C). It is no longer necessary to have
  a Winsock-2 compliant update from Microsoft if you are running Windows 95.
  Note that Windows 98 and higher already have the Winsock-2 extensions.

- With the above update, it may be possible to run DBIS under Windows
  For WorkGroups 3.11 with Microsoft TCP/IP Services installed. And if that
  works, then it is possible to run DBIS under OS/2 Warp Connect or Warp 4.

- This is the first release that Laura compiled herself.....(with Nick's
  step by step directions)



Version 2.00 Beta Release #8 - January 18th, 2006
-------------------------------------------------

A lot of hard work has gone into Beta Release #8. Please test thoroughly.
This beta tests the web server function of DBIS only. BinkP, FTP, Telnet
and the DynDNS client are presently disabled.

To test the web server code of DBIS, do the following:

- Ensure your operating system is capable of running DBIS (see notes)

- Confirm proper configuration of DBIS via INTERNET CONNECTIVITY.

- Create a text file called INDEX.HTM in the WWWROOT directory with just
  one word - "test".

- Start DBIS in another window on your operating system.

- When the DBIS program says its ready, make note of the IP address.

- Type "http://[that IP address]" into your browser. So for example
  if your computer's address is 192.168.2.101, type http://192.168.2.101
  into your web browser.

- The word "test" should now appear in your browser.

- You should now disable the web server feature, unless you wish to keep
  on testing it with more elaborate HTML files.

Note that the web server does NOT support LFN's (long file names). You must
limit your files to standard DOS 8.3 format... for now.

- The help system and configuration screen has been updated for the DBIS
  component. However, in order to make space for all of the new features,
  some sections in the help system had to be REMOVED:

     - References to setting up different BBS types. (obsolete)
     - The detailed discussions on time zones and the US Naval Observatory.

- DBIS has been rewritten (yet again) to pipe output to STDIO so you can
  redirect the output of DBIS to anything you want. Note that DBIS creates
  a log file called DBIS.LOG in the directory.

- Note that DBIS will require Windows 95/98/ME, or NT4 with Service Pack
  6, 2000 with Service Pack 4, or XP with Service Pack 1A or higher. Testing
  the DBIS component under Linux/FreeBSD WINE is encouraged; please let me
  know how it works out.

- Note that the upcoming Telnet server feature of DBIS requires that you be
  running either Windows NT4, 2000 or XP. The Telnet server WILL NOT
  FUNCTION properly on any other platform.

- If you are running Windows NT4, 2000 or 2003 Server, and are using
  the Microsoft Internet Information Server (IIS), you will need to DISABLE
  the server BEFORE testing DBIS, otherwise the code will not work.

- The "Modem required for dialup" bug in D'Bridge is gone forever.

- A brand new setup screen has been added to D'Bridge - DEBUG & SUPPORT.
  Look for it underneith the ADVANCED menu. The purpose of this screen is
  to allow you to change certain internal variables used by D'Bridge. DO NOT
  under ANY circumstances, change any of these. This screen is provided
  in the event that technical support is needed. If you request support and
  we deem that its necessary to change an internal variable, we will tell
  you to do it. If the change in the variable fixes the problem or at least
  makes D'Bridge more stable for you, we will note the change and then
  permanently change that variable in the next release of D'Bridge.

- Several outstanding bugs have been corrected in the way D'Bridge imports
  and exports configuration files (*.CFG or DBRIDGE.AUT).

  It should be noted that although this version is 100% backwards compatible
  with older versions (minus the Internet support obviously), you should
  only "rollback" to 2.xx releases, THEN rollback to 1.xx releases if so
  desired. Rolling back from 2.1 to lets say, 1.58, 1.60 or 1.70 is NOT
  recommended.

- A bug where the INSTALL program may crash when upgrading an installation
  on another drive has been corrected.

- Other miscellaneous bugs have been corrected in the mailer and tosser,
  again none worth noting or even trying to explain.

- The INSTALL program now performs several stability checks before even
  starting; to avoid "problems" for newcomers.




Version 2 - Beta Release 7 (BR7) - 13 December 2005
---------------------------------------------------

- This release corrects various minor issues with my new INSTALL program.

- Screenshots will be made available this week of the new Internet subsystem.



Version 2 - Beta Release 6 (BR6) - 10 December 2005
---------------------------------------------------

WARNING: This release contains major code updates. Use with caution.

- The entire code for installing/upgrading D'Bridge has been rewritten
  from scratch. D'Bridge is now installed using INSTALL.EXE.

- D'Bridge no longer gives cryptic error messages. All error messages in
  the program should now display a more detailed explanation of what went
  wrong as well as ways to fix the problem, sortof like what I did
  for error 202 and 203.

- Although I can't exactly replicate the large-Areafix request problem
  that Ward was having, I did go through the Areafix code and cleaned up
  some things that may of caused problems...

- This should be the final Beta release. Assuming no serious problems with
  this one, the next will be 2.1 with BinkP features enabled, in a multi-
  user, multi-tasking Internet subsystem that will handle BinkP, FTP and
  simple Web/HTTP connections.

Version 2 - Beta Release 5 (BR5) - 1 December 2005
--------------------------------------------------

This is only a minor release designed to correct some issues in Beta
Release #4. It is NOT necessary to upgrade unless the following concerns you:

- This release was compiled on an HP NetServer E45 platform. If you
  decide to upgrade to this release, please test all features, etc etc.

  This new server I have now, compiled BR5 in less than 15 *seconds*. My
  notebook can take up to a full minute to compile the code. I could never
  understand why SCSI never caught on...

- This release corrects "frozen" sessions under Windows NT Workstation
  and Windows NT Server running the TAMEDOS product by David G. Thomas. If
  you are running Windows 2000 or Windows XP Home/Professional/Server
  or .NET Enterprise, this *may* cause problems if you run D'Bridge inside
  of a batch file. You MUST include the line "TAME-MON /UNINSTALL" right
  before D'Bridge is loaded up.

- D'Bridge should now support DigiBoard multi-port serial boards such
  as the PC/X, MC/X, and most newer PCI boards.

- D'Bridge should now detect and adjust its timeslicing for Linux/BSD
  operating systems (Tested with NetBSD, OpenBSD and FreeBSD 5.1 and 6.0
  with Linux binaries and the Boches virtual computer system) The code
  really just checks for Boches version info but you get the idea. :-)

- In case you didn't get it, DBUTIL 1.9G is included in this release.

- BinkP is still DISABLED in this release. Please be patient.



Version 2 - Beta Release 4 (BR4) - 24 November 2005
---------------------------------------------------

- This is a minor release that corrects another one of my screwups. Try to
  guess where it was, I think you'll be pleasantly surprised!

- Another programmer is looking at the assembly-language code to help me
  get this BinkP feature underway. Its a problem that I can't solve myself.
  Therefore, this may be the last release for a little while until then...

- This release includes the updated DBUTIL (1.9d) that corrects the "access
  error" when using the DELETEDOS command to purge old Fido directories.

- BinkP is still DISABLED in this release. Please be patient.



Version 2 - Beta Release 3 (BR3) - 21 November 2005
---------------------------------------------------

- This is a minor beta that features an improved "You've Got Mail" system,
  that now notifies you which Echomail areas have personal mail for you.

- The LOG window now displays any new personal mail to you.

- Some minor corrections done to DBUTIL; the current version is now 1.9c.

- Problems with "corrupt DBRIDGE.PRM" files should now be fixed.

- BinkP is still DISABLED in this release. Please be patient.



Version 2 - Beta Release 2 (BR2) - 20 November 2005
---------------------------------------------------

WARNING: Beta Release 2 contains major code updates to your D'Bridge
         system. PLEASE READ THIS ENTIRE DOCUMENT before proceeding.
         Please BACK UP your D'Bridge directory before installing. 

A lot of hard work has gone into Beta Release 2. Please test all
features of D'Bridge upon installing. Any problems or bugs, please
report ASAP.

- BinkP is still DISABLED in this release.

- Compiled while watching "Freddy Versus Jason", yes, we like to have
  our horror-movie-marathons here at the house.

- Special thanks to Bjorn Felten for his help with object code compiling
  and some assembly stuff that was a little over my head. Thanks a lot!
  Without his help and direction, this beta would have never been finished.

- D'Bridge now requires at least a 386 processor in order to function.

- The Internet features in D'Bridge will not run under Windows 95 unless
  Microsoft Winsock 2 Update has been installed. Windows 98 and ME already
  have the Winsock 2 update; therefore disregard this warning if you
  are running Windows 98 or ME.

- The Internet features in D'Bridge will not run under Windows NT
  unless Service Pack 6A (standard or high encryption) has been installed.

- For Windows 2000, you should have Service Pack 4 installed.

- For Windows XP, Service Pack 2 should be installed.

- If you're going to use the Internet features of D'Bridge under IBM OS/2,
  please make sure you have applied the latest MPTS update (for Warp Connect
  systems), and/or the latest TCP/IP Stack Update, both of which can be
  obtained from ftp://hobbs.nmsu.edu (New Mexico State University). It may
  also be necessary to apply Fixpaks to your operating system as well.

- This beta may cause problems with ProtectorPlus 2000 7.2.G06 (an anti-
  virus program). The "real-time scanner" may cause significant "slowdowns"
  during mail tossing and reading messages in the editor. You may need
  to temporarily disable Protector Plus's real-time scanner in order to
  correct "slowdown" issues. (Tested on a Dell Pentium 133 system)

- This beta may cause problems with DialUp Networking in Windows 95/98/ME
  when Windows first boots, if "Connect Automatically" has been enabled
  in your network settings and you've put D'Bridge in your Startup folder.

- In order for this beta to work, some of Chris Irwin's original assembly
  language routines had to either be rewritten, re-arranged, and in some
  cases, deleted altogether. The code in question deals with "swapping
  to DOS", also referred to in the help file as "PUSH" and "DROP" (ALT+Y,Z)

  PLEASE RUN A FULL TEST OF THE FOLLOWING:

             - DOS EVENTS
             - FUNCTION KEYS THAT CALL DOS PROGRAMS
             - EXTERNAL RECEIVERS
             - FUNCTION REQUESTS
             - XMAIL COMPRESS/DECOMPRESS COMMANDS
             - "DOS COMMANDS TO RUN" IN ALL MAIL EVENTS.
             - Anything else that D'Bridge may have to "swap out" for.

  IF ALL TESTS PASS, CONDUCT THE FOLLOWING TEST:

       - Start D'Bridge and Shell to DOS from the mailer (ALT+Z)
       - Do something to "crash" D'Bridge (or close the DOS window)
       - Restart D'Bridge.
       - Shell to DOS again (ALT+Z)
       - Type DIR /A:H *.DRO and verify that there are no *.DRO files.
       - Start D'Bridge and fire up the editor (or type DB EDIT)
       - Shell to DOS by typing ALT+Z.
       - Do something to "crash" D'Bridge (or close the DOS window)
       - Restart D'Bridge.
       - Shell to DOS again (ALT+Z)
       - Type DIR /A:H *.DRO and verify that there are no *.DRO files.

  IF THAT TEST PASSES, RUN THE FOLLOWING TEST:

      - Start D'Bridge and Shell to DOS from the mailer (ALT+Z)
      - At the DOS prompt, try starting D'Bridge by typing "DB".
      - If the computer says "D'Bridge is already loaded", you have
        successfully completed the tests.

- More modifications will be done to the underlining assembly language
  code in the next few releases to accomodate the Internet features.

New "goodies" added:

- You can now specify your own "tear line" in outgoing Echomail, by
  going into SETUP -> EDITOR OPTIONS. Do not include the "---" part
  in your custom tearline. The help system (F1) will tell you more about it.

- By the way, D'Bridge no longer reports the license key on tear lines, and
  this was actually corrected in Beta Release 1. Beta Release 3, already
  in the works, should finally do away with the license key files
  altogether.

- Beta Release 3 will have an option to include "cookies", or "taglines"
  in outgoing mail.

- D'Bridge can now notify you if it's tossed Netmail or Echomail addressed
  to you! This is a handy feature, one that Laura requested I add in there.
  Go into SETUP -> EDITOR OPTIONS and answer Yes or No to the "You've Got
  Mail" option. And the help system (F1) will tell you more about it.
  See, when she nags me enough, I get it done. :-)

- The "You've got Mail" system works on both Fido and QuickBBS systems.

- Beta Release 3 will have a more elaborate and detailed "You've Got Mail"
  system. Please be patient - I'm working on it.

- This beta also corrects a minor security issue, and all of the license-
  key checking code should finally be gone now.


Version 2 - Beta 1 - 14 November 2005, 10:00pm EST
--------------------------------------------------

Welcome to version 2 of D'Bridge!

A lot of hard work has gone into this release to prepare D'Bridge for the
addition of BinkP support. Please be patient. Its coming.

WARNING: Do NOT run the WSLOADER.EXE program, as mentioned in the help file.
         It is not necessary to run that program in this Beta release.
         
- This release of D'Bridge now has an INTERNET CONNECTIVITY menu, please
  configure your BinkP settings there, verify the help file system, etc etc.

  BinkP connectivity is DISABLED in this beta, due to a problem with one
  of the libraries I'm using. But again, you may go ahead and configure
  the sites you need to communicate with.

  Again, do NOT run the WSLOADER application... at this time.

- You no longer need a modem to use D'Bridge. If you want to use D'Bridge
  in an "Internet-only" environment, just go into the COMM/MODEM setup
  screen and erase your settings there. However, if D'Bridge is configured
  for BinkP "Receive only", outbound calls will still require a modem.

- Confirm the installation of the following files: WSLOADER.EXE, NTWSOCK.DLL,
  and WSOCKXS.VXD.

- This release should corrects a security issue; any mail and file
  attachments that come in from unknown systems will be renamed BAD-MAIL
  and BAD-FILES respectively, provided that RENAME UNAUTHORIZED FILES
  is set to YES.

- The installation problem of always defaulting to C:\DBRIDGE should be
  corrected.

- The installation program should now automatically remove any old copies
  of the DBNET nodelist. DBNET.005 is included in this release.

- Because this is a Beta release, please report problems ASAP.


1.96 / 12 November 2005
-----------------------

WARNING: This release contains major updates. Please backup before upgrading.

WARNING 2: Backup the following files to a temporary directory:

                        - DBRIDGE.PRM
                        - DBRIDGE.ADF
                        - DBRIDGE.DSI
                        - Contents of your Netmail directory.
                        - All of your queue and packets.

WARNING 3: Do NOT use DBUTIL DELETEDOS unless your system has been backed up
           and you are prepared to restore/rollback in the event of problems.


- A very serious problem with EMSI has been corrected in this version. Under
  rare circumstances, the *lack* of the anti-piracy code in DB would cause
  a system crash. The problem has been corrected by rewriting part of
  the EMSI code so it does not report (and compare) certain statistics
  of the report system.
                       
  *** YOU MUST UPGRADE TO THIS VERSION TO ENSURE A STABLE EMSI SYSTEM ***

- A serious problem with DBUTIL SORT AREAS has been fixed. Please check your
  Echomail database for any duplicate areas. If any exist, please follow
  these instructions, "to the tee":

        - Backup the DBRIDGE.ADF and BACKUP.ADF file (if it exists)
        - Run DB SETUP and manually remove the duplicate areas.
        - Make a second backup of DBRIDGE.ADF.
        - Run DBUTIL SORT.
        - Run DB SETUP again and confirm the Echomail database is accurate.

- A serious bug in DBUTIL DELETEDOS has been fixed, however, please do NOT
  use the DELETEDOS command in DBUTIL unless you have backed up your system
  first.

  DBUTIL DELETEDOS should only be used if you want to run a "system-wide"
  cleanup of your message directories. It should NOT be ran as part of any
  regular maintainence, due to the fact that if something happens to
  your Echomail database (DBRIDGE.ADF), you can really mess things up. Again,
  you should NOT run DBUTIL DELETEDOS unless you have backed up your
  entire DB directory first.

- This release also includes a new command for DBUTIL: MOVE.

     MOVE will take any address you specify, and "move" it to a directory
     of your choice. It should replace Khile Klock's entire DBQ2FTP utility,
     and requires no external configuration at all. MOVE should obviously
     be used *after* any queue-manipulating commands such as POLL
     and SEND. It also works on point systems, something DBQ2FTP wasn't
     able to do properly. MOVE creates a tiny database called DBUTIL.DAT
     that contains the current day-of-the-week increment that FTSC calls
     for, ie. Tu1, We2, Sa7. It also takes NETmail queue entries and
     converts them to PKT files, including XMA-marked messages. And
     obviously, any queue/packet moving is recorded to DBUTIL.LOG for
     your inspection.

     *NOTE* DBUTIL MOVE will NOT move Packets, only Queue entries. This will
     be corrected in the next release of DBUTIL. If you wish to use
     the MOVE command in this release, please "pack out" your Netmail
     into Queue bundles by adding the XMAIL flag to each of your Netmails;
     and enable the "Xmail" option in EDITOR -> EDITOR OPTIONS.

     Note that MOVE is NOT present in the "interface" portion of DBUTIL. It
     must be called from the command-line.

     MOVE [address] [directory]

     ie.

     C:\DB> DBUTIL MOVE 1:229/426.1 F:\LAN\LAURA
     C:\DB> DBUTIL MOVE 1:229/2000 C:\IREX\ROBERT
     C:\DB> DBUTIL MOVE 201:3000/1 C:\IREX\WARD

- Because of the above feature, Khile Klock's DBQ2FTP utility is no longer
  included in this release, or any future versions for that matter.

- The DB help system has been updated accordingly for the new MOVE command.

- DBUTIL now has "startup screen", and performs a small check on critical
  system files before executing any commands. Nothing is modified or
  changed during the startup sequence. If the check fails, DBUTIL now halts
  back to DOS, as a safeguard against commands running only to have it fail.

- Also, some last minute changes have been made to DBUTIL to NOT purge any
  areas without criteria, and some other minor bugs have been corrected.

     *** YOU MUST SPECIFY PURGE CRITERIA FOR AN AREA TO BE PURGED! ***

- Internal code that calls PKZIP to create configuration and history
  archives (ie. DBCONFIG.ZIP), now creates them with maximum compression.
  Not really a big deal; just something that I felt needed updating.

- On new installations, several corrections have been made to the default
  compress/decompress options in the XMAIL CONFIGURATION screen. The most
  bizarre (yet important) change was adding ".EXE" to the ends of all
  the compress/decompress commands. For some reason, new installations
  don't have this problem when installing in "pure DOS". But on Windows
  95/98/ME systems, the .EXE must be added. Anyways, thats all fixed now
  so the new user doesn't have to worry about that.

  If you are upgrading your installation, the above compress/decompress
  corrections will NOT be applied. Check your configuration just in case.

- The same fix has been applied to the COMM/MODEM SETUP screen to ensure
  that PKUNZIP.EXE (*not* just "pkunzip") is called if D'Bridge needs to
  extract any MCF or PCF files. Theres only one in there... for now.

- Its now possible to change the dialup number of the United States Naval
  Observatory Atomic Clock by creating a text file called DBRIDGE.CLK
  with the proper phone number. If D'Bridge encounters this file, it will
  dial whatever number is in there. I didn't change it in the code itself
  for two reasons: (1) I don't even know what the new number is,
  and (2) Just in case it changes again in the future.

- ENVVARS.TXT has been renamed to TECHSPEC.TXT and now contains a history
  of ongoing work to D'Bridge from 1.80 up to now. TECHSPEC.TXT also
  contains the D'Bridge technician's manual if someone out there wants to
  start writing 3rd-party stuff for D'Bridge.

- HISTORY.TXT contains a history of D'Bridge developement since 1.80, and I
  will go back to the CD-R archives to find older stuff that Chris wrote.

- Some corrections were done to the OTHER56K.MCF INIT and DELAY strings to
  speed things up a little bit.

- Some minor things were fixed up in the source code; no big deal.

- Newcomers are warned against installing DB into the current directory
  as well as making sure they have read/write access if D'Bridge is being
  installed onto a LAN server, such as Windows 2003 Advanced Server.

- DBUTIL's version level as of this release, is 1.9a.


1.95 / 10 November 2005
-----------------------

WARNING: Due to major code updates, please BACKUP your existing installation.

- This release of D'Bridge has been recompiled in Borland Pascal 5.5.


1.94 / 7 November 2005
----------------------

- Minor corrections done to post-startup operations.

- Removed an EMSI limitation that affects "Freeware" keys, was supposed to
  be fixed back in Alpha5000-4 (A4) but apparently I didn't fix all of it...

- Help for DBUTIL has been updated in D'Bridge. (Refer to Section 7.00)

- DBUTIL is brought up to 1.9, and so far runs stable with no apparent bugs.

- Got Laura running her own copy of D'Bridge (1:229/426.1 & 201:1000/3)

- Nick Mackechnie runs DBNET Aust/NZ (201:2000/1)


1.93 / 7 November 2005
----------------------

- This release corrects a minor memory leak.

- This release brings DBUTIL to version 1.6. In case you didn't know, there
  have been several fixes and updates to DBUTIL in the past week alone. I
  may design and include "history" files for D'Bridge and DBUTIL just to
  keep everyone up to par on whats going on.

- A text file called DB193ENV.TXT is included, explains all the environment
  settings used by D'Bridge. 

- Release notes are going to have a TXT extension from now on, to keep Ward
  happy... (or as happy as Ward can be!)


1.92 / 2 November 2005
----------------------

WARNING: This is yet another release that contains major updates or source
         code changes. Install with caution.

- First of all, I would like to take a moment to thank all of you for your
  continued help and support. D'Bridge has come a long way, and dozens of
  problems have been corrected since 1.58. With your continued help, we can
  finally have ourselves a mailer that is rock-solid stable and reliable.

- The old code from Alpha5000-3 (A3) has been recycled and put back into
  place, to correct the issue of not being able to have multiple "DB EDIT"
  windows running at once, or over a local network. Because this change
  affects the underlining database routines, please run the following tests.

  This checklist should be ran on *ALL* of my new releases:

        (1) Recompile the nodelist.
        (2) Recompile the nodelist, then perform a queuescan.
        (3) Perform a queuescan, then poll a system.
        (4) Poll a system immediately on startup.
        (5) Run DB EDIT first, then poll system via. UTILITIES menu.
        (6) Create a "dummy" Netmail message with the XMAIL flag.
        (7) Take that dummy Netmail and then perform a queuescan.
        (8) On a queue entry, "view" it's details.
        (9) Display "details" on any nodelist entry. Confirm accuracy.

  If *ANY* of those database tests fail, either with error 202 or 203 or
  messages such as "COSTBASE", do the following:

        (1) "Export" your configuration or backup your entire DB directory. 
        (2) Erase the contents of the DATA directory.
        (3) Begin the checklist again.

  If the system still fails at this point, drop Laura a line indicating which
  checklist number it fails on. For example, if the system fails to generate
  a proper poll request when selected immediately on startup, indicate
  problem #4 in an email. Also be sure to tell Laura the following:

             - The last 5 or 6 lines of your system log.
             - The contents of your Queue directory. (ie. the QUEUE window)
             - The list of files in the Queue directory.

- I've added several new commands to DBUTIL, as follows:

       AUTOASSIGN [option] A-[matching address] OR T-[matching area]

       The AUTOASSIGN keyword, will automatically change/update your
       Echomail database whenever a new area is added by D'Bridge that
       has an uplink address (the A- parameter), or that has a matching
       area name (the T- paramter). Multiple entries are okay, seperated
       by commas. The following options are available:

             ALERTFLAG [value] - The "Alert" status flag. 0-9, A-Z.
           GROUPACCESS [value] - The group access character. 0-9, A-Z
             GROUPSORT [value] - The group sort character, usually 0-9.
         GROUPSECURITY [value] - The security level. 0 to 5000.
                 PURGE [value] - Purge except OR purge after days. If you
                                 are purging in days, specify a negative
                                 value, ie. 7 days should be "-7"
              PRESERVE [value] - Messages to preserve.

       Examples:

       AUTOASSIGN ALERTFLAG A A-1:229/2000
       Assigns alert-flag "A" to new areas from my 1:229/2000 uplink.

       AUTOASSIGN GROUPACCESS B A-2:2/0,2:282/153,4:500/13
       Assigns group access "B" from the specified addresses.

       AUTOASSIGN PURGE -14 T-ALT.*,REC.*
       New areas from the "ALT" and "REC" Usenet groups will be purged
       after 14 days.

       AUTOASSIGN GROUPACCESS A-1:229/2000
       AUTOASSIGN GROUPSECURITY 5000 A-1:229/2000
       AUTOASSIGN PRESERVE 200 A-1:229/2000
       Assigns group A, security level 5000 and a preserve of 200 messages
       to everything auto-added from my 1:229/2000 uplink.


       CHANGE [option] [newvalue]

       The CHANGE command tells DBUTIL to make mass-changes to your
       Echomail setup, based on the option you select:

             ALERTFLAG [value] - The "Alert" status flag. 0-9, A-Z.
           GROUPACCESS [value] - The group access character. 0-9, A-Z.
             GROUPSORT [value] - The group sort character, usually 0-9.
         GROUPSECURITY [value] - The security level. 0 to 5000.
                 PURGE [value] - Purge except OR purge after days. If you
                                 are purging in days, specify a negative
                                 value, ie. 7 days should be "-7"
              PRESERVE [value] - Messages to preserve.

       Examples:

       CHANGE ALERTFLAG A ALERTFLAG B
       Changes all areas with alert flag "A" to alert flag "B"

       CHANGE GROUPACCESS A GROUPACCESS Z
       Changes all areas in group "A" to group "Z"

       CHANGE PURGE -14 PRESERVE 50
       Changes all areas with a 14 day purge value to also have a preserve
       value of 50.


       DELETE [option]

       Deletes areas from your Echomail database based on your criteria. Use
       with caution. If you make a mistake, use the UNDELETE command
       mentioned later.

             ALERTFLAG [value] - The "Alert" status flag. 0-9, A-Z.
           GROUPACCESS [value] - The group access character. 0-9, A-Z.
             GROUPSORT [value] - The group sort character, usually 0-9.
         GROUPSECURITY [value] - The security level. 0 to 5000.
                 PURGE [value] - Purge except OR purge after days. If you
                                 are purging in days, specify a negative
                                 value, ie. 7 days should be "-7"
              PRESERVE [value] - Messages to preserve.

       Examples:

       DELETE ALERTFLAG A
       Deletes all Echomail areas that have alert flag "A"

       DELETE GROUPSECURITY 5000
       Deletes all Echomail areas that have a group security of 5000.


       DESCFILE [file]

       The DESCFILE command tells DBUTIL to change all the descriptions of
       the Echomail database to match those found in a text file. The text
       file should be in ".NA" format, meaning the area tag, at least one
       space, and then the description.

       Example: DESCFILE C:\DBRIDGE\FIDONET.NA


       DELETEDOS (No options)

       If the DELETEDOS command is executed, then whenever
       a DBUTIL PURGE is ran and DBUTIL encounteres a "deleted" area (either
       from another script operation or from DB SETUP), if the area is
       a Fido *.MSG area, the directory is also deleted. So if you
       deleted FN_SYSOP, and DBUTIL PURGE is ran again, whatever you
       specified as your FN_SYSOP message directory, will be erased. Note
       that if you plan to use the UNDELETE feature mentioned below, you
       should not use the DELETEDOS command.


       UNDELETE

       If UNDELETE is ran, any previous DELETE operations will
       be "rolled back". Any deleted records in your Echomail database
       will be restored.

- The GUI (full-screen mode) of DBUTIL has been updated accordingly.


1.91 / 31 October 2005
----------------------
           v^v
                 v^v
         
               v^v
    
    
.....woooooOOOOOOOOOOOooooooo..... This is the Halloween edition of D'Bridge.
And for your "treats", the following issues have been resolved:

- Internet code has been temporarily removed, was causing a problem with
  memory allocation under certain "rare" conditions under Windows 95.

- DBUTIL has been enhanced with a full-screen GUI to access its features,
  if you don't use any parameters. And the current issues should be resolved
  with purging and whatnot. The GUI's mini-windows can be played around with
  your mouse, and the keyboard shortcuts should work as well. Try it out!

- Renumbering messages during DBUTIL purge is disabled in this release.

- DBUTIL can also be ran in another window on multi-tasking operating systems
  if you want to purge/archive mail without "tying up" your DB session. It
  uses file-sharing and record-locking code to ensure safe operations.

- DB2RG is no longer included; support for BBS types is planned for a future
  release in addition to other message formats.

- Laura will continue to handle technical support for now. We are in the
  process of moving so it may take us some time to reply to your emails...



1.90 / 17 October 2005
----------------------

Warning: This release contains major updates; please BACK UP your system in
         the event you need to rollback to 1.89sl.

- The maximum amount of Netmails able to be processed in a Queuescan has
  been REDUCED from 2048 down to 1024, to allow the Xmail-on-Netmail packing
  to function properly. The help system has been updated for "Xmail" in
  the SETUP EDITOR OPTIONS screen accordingly.

- D'Bridge now adds the "PID", "TID" and "CHRS" kludges to all messages
  created in the internal editor, in the event that someone needs to debug
  a message from your system (although yes, its obvious from the tear line
  what generated the message) PID and TID are product identification data
  kludges, which simply state DB-version-whatever. CHRS is a character set
  kludge, which defaults to "IBMPC 2", I plan to add support later on for
  custom kludges and possibly move all kludging to some sort of script
  language, so you guys can add whatever you want to outgoing mail.

- DBUTIL has been completely rewritten from scratch. All of the purging
  problems should now finally be solved. It was tested with several
  thousand *.MSG files, both Netmail and Echomail. It also gives detailed
  reports about its activities, and logs everything to DBUTIL.LOG
  for your inspection. This log file can be deleted whenever you want.

- DBUTIL automatically "renumbers" Fido MSG files during purge processing.

- DBUTIL PURGE called on its own will process all areas EXCLUDING Netmail.
  You must specifically run DBUTIL PURGE NETMAIL to purge/archive Netmail.
  This was done as a precaution/failsafe.

- DBUTIL SORT AREAS now scans your Echomail configuration for deleted areas.
  If it finds any, and if they are of the Fido *.MSG type, DBUTIL will
  now automatically remove any old files as well as the old directory.

- "DBUTIL.OLD" is Chris Irwin's DBUTIL program, in case you need to rollback
  or you need both mine and his for some reason.

- Preparations are also under way for Internet connectivity, in fact, this
  version already contains menu and help code for the "big event", if you
  browse the help system you'll see what I mean.


1.89 / 15 October 2005
----------------------

- Look at the Help file, and go through the first few sections. I think
  you'll like it. I wrote some very thorough, detailed information about
  running D'Bridge under Windows. Mostly geared towards newcomers. I felt
  that the Help system was due for some updating. I had some free time to
  spare, and that doesn't happen often!

  The following help topics have been added:

  NOTE FROM THE AUTHOR
  NOTE FROM NICK ANDRE
  HARDWARE / SOFTWARE REQUIREMENTS
  RUNNING DBRIDGE UNDER MICROSOFT WINDOWS
  RUNNING DBRIDGE UNDER IBM OS/2 WARP
  RUNNING DBRIDGE UNDER LINUX
  THE INTERNET AND DBRIDGE

- Thanks to Ward, and a few Russians, I think this MSGID/REPLY nonsense
  should finally be solved. What I've done was change the code so the entire
  message is scanned for a MSGID kludge. And obviously a REPLY kludge is
  added if one exists. Before, my code was only checking the first line of
  a message. The other problem of only getting REPLY kludges when you reply
  after the first message should also be solved. Leave it to me to really
  screw up the way I open/close files. :-)


1.88 / 14 October 2005
----------------------

- In this version, in-transit Areafix messages are IGNORED and treated as
  regular Netmail, and subject to the routing specified in the current
  running event. Areafix requests will NOT be processed unless it has been
  specifically addressed to your system's primary address or AKA's.

  Even if you use the FOR keyword in the ALIAS ADDRESSES screen in
  the BASIC CONFIGURATION menu, you *MUST* specify the alias addresses for
  the Areafix system to work properly. So if you have a "2:2/1000 for 2:ALL"
  as an alias entry, "2:2/1000" must be specified again for Areafix to work.

- The Help system has been updated accordingly for the above Areafix change.

- Problems with no REPLY: kludge being added should be fixed now, hopefully.

- My work schedule with IBM is hectic, but please continue to inform me
  of any bugs or problems.


1.87 / 10 October 2005
----------------------

I recommend BACKING UP your current installation, or at least installing
this version in a new directory... just in case.

- "REPLY:" kludges are now added to all replies done in D'Bridge, and that
  includes BOTH Netmail and Echomail, as well as "Normal" and "Quoted"
  replies. The REPLY: kludge immediately follows the MSGID: kludge.

  A tiny text file, DBRIDGE.MSR (in addition to DBRIDGE.MSG) is now
  created during a message edit, containing the MSGID: kludge from the
  original message. DBRIDGE.MSR gets erased when D'Bridge saves the reply.

  Please double-check your DOS events that nothing touches these two files.

  NOTE: If a MSGID kludge didn't exist in the original message, the REPLY
  kludge is NOT added.


1.86 / 10 October 2005
---------------------

I recommend BACKING UP your current installation, or at least installing
this version in a new directory... just in case.

- MSGID apparently calls for a colon, so now it gets one!



1.85 / 9 October 2005
---------------------

I recommend BACKING UP your current installation, or at least installing
this version in a new directory... just in case.

- A slight correction in the new MSGID code was done for Echomail.



1.84 / 8 October 2005
---------------------

I recommend BACKING UP your current installation, or at least installing
this version in a new directory... just in case.

(1) The MSGID kludge is now added to all messages originating from D'Bridge
    according to the FTS-0009 standard by Jim Nutt, and FSP-1029 by Michiel
    van der Vlist. This kludge is added to all "new" messages, "edited" ones,
    and copying/forwarding mail in the internal editor.

    Please be aware of a new, tiny database file called DBRIDGE.MSG, this
    file keeps track of the next serial number to be used in adding a MSGID.

(2) Newcomers can now specify the color scheme they want on installation.



1.83 / 2 October 2005
---------------------

I recommend BACKING UP your current installation, or at least installing
this version in a new directory... just in case.

(1) This release should start to address the error 202 and 203 bugs that have
    plagued DB for years.

    Some code has been rewritten, changed, moved around, and in some cases
    removed altogether to address the 202/203 problems.

(2) In the event of a 202 or 203 error, D'Bridge now politely explains what
    went wrong and suggests ways to solve the problem before reporting the
    matter to myself... so 202/203 won't scare away newcomers. :-)

(3) DBNET is back... the inclusion of the DBNET nodelist has been done to
    facilitate hassle-free installations for newcomers. If you have an
    address in DBNET already, please let me know so I can update the list.

(4) The OTHER56K.MCF file has been slightly corrected.

(5) Miscellaneous code has been cleaned up for stability reasons.


1.82 / 24 September 2005
------------------------

I recommend BACKING UP your current installation, or at least installing
this version in a new directory... just in case.

(1) Khile Klock's DBQ2FTP utility is included (and installed) in this
    release. This utility translates and moves Queue packets in D'Bridge
    into standard FTSC files that can be uploaded to FTP servers or
    local LAN server directories, or whatever you want. Look for DB2FTP94.ZIP
    installed in your DB directory.

(2) Minor miscellaneous code has been cleaned up; nothing overtly special.

(3) The next version of DB will address the Error 203 problems
    with the COMM/MODEM setup screen... I just didn't have time for that
    right now. Its going to take some work to get that one figured out.

(4) I screwed up the release number; this was not supposed to come out
    until October, but I figured I'd do this one a little early.


1.81 / 1 October 2005
---------------------

I recommend BACKING UP your current installation, or at least installing
this version in a new directory... just in case.

(1) A free license key is included (and installed) in this release. However,
    if D'Bridge complains of multiple license keys (it shouldn't), you can
    delete the file DB100000.KEE and use your old one.

(2) Gone are the 200-some-odd MCF files forever, most of them were for
    anchient 2400 baud modems and the like... the 56k generic MCF file is
    now the only selection. Its easy to edit and most modems shouldn't have
    any trouble running it... even if they aren't 56k.

    Note that the COM port locks at 57600 in this MCF file. Under RARE,
    and I *do* mean *RARE* circumstances, running D'Bridge with TAME
    under Windows NT/2000/XP environments may cause a COM port "baud error"
    (yet another fantastic feature by Microsoft), that the port can't be
    opened higher than 38400 baud. If this happens, simply change the rate
    in the MCF file.

(3) If you decide to change the MCF (Modem Control File) in the COMM/MODEM
    setup screen and DB crashes with an Error 203, you will need to manually
    edit the DBRIDGE.PRM file and change the MCF name in Line 30.

    I still can't figure out why it crashes here, its got something to do
    with memory allocation. This will be addressed in a future release.

    This bug only seems to appear on Windows 95/98/ME systems... doesn't
    happen on my Windows 2000 workstation; I can change the MCF just fine.

(4) XMAIL packet statistics are always shown now during mail processing.
    Please let me know if this isn't what you want... I like it because I
    can see real-time stats for any outbound mail created during tossing.

(5) Pretty sure I nailed queuescan bugs for large Echomail systems that hub
    thousands of areas (ie. Usenet groups from the Internet)

(6) X00 version 1.53a, the last stable release from Ray Gwinn, is included.

(7) D'Bridge now adds the "DV" (Desqview Timeslice) command if it needs
    to execute the X00 driver. The DV command causes X00 to relenquish
    timeslicing back to the operating system. In theory, this should work
    on operating systems other than Desqview... if you run TAME, please let
    me know what your CPU statistics are when DB is running.

(8) D'Bridge now "restarts" itself (does an IPL) after any nodelist
    compiling, to completely flush out any open arrays or variables in
    the code. I simply don't have the time right now to address the issues
    with the memory allocation, probably for a future release.

    This originally was removed in the 1.80 release, but now its back,
    for stability reasons.

(9) Various internal code has been cleaned up, for the next release which
    will start to address some performance issues, timeslicing, etc etc.

(10) D'Bridge no longer checks for disk space or integrity on archives on
     new installations... really; who can't afford 2 megabytes of space?

(11) The integrity check was removed in order to some some rare bugs when
     installing D'Bridge under Windows 95/98/ME.

(12) This release was CC'd to Chris Irwin, hopefully he can play around
     with it and tell me if I missed anything...

I hope you enjoy this long-awaited release and any suggestions or feedback
is welcome, either on the DBRIDGE echo on Fido (preferrably), or email
to foxmulder4055@hotmail.com


1.80 / 20 September 2005
------------------------

I recommend BACKING UP your current installation, or at least installing
this version in a new directory... just in case.

(1) This version is a "rollback" to the old 1.70 code, with one exception -
    the low-level SHARE code detection is changed to always report that
    the SHARE portion of DOS is present... so in other words, this release
    should function exactly like the 1.70 code.

    The license key checking is removed but please place your key files in
    your directory anyway... just incase.

(2) The latest version of DB2RG is included for those of you running D'Bridge
    with the Renegade BBS software. It takes your Echomail database in DB
    and "mirrors" it with your message base configuration in Renegade.

(3) All of the fixes that worked in the Alpha5000 series are now consolidated
    into this version.

