@database 075193e8-0
@master DLG_Upgrade.guide
@$VER: 1.0
@remark Created with Heddley v1.1 (c) Edd Dumbill 1994

@node "Main" "No title"
 @{b}@{bg shine} DLG Pro Progressive Upgrade Manual @{ub}@{bg back}

@{"Purpose" link "Purpose" 0}

Presenting: @{u}The Upgrades@{uu}

   Part I:     The Heady 1's

      @{"DLG 1.16" link "_DLG1.1" 0}

   Part II:    Grimmett Gets Medieval

      @{"DLG 1.23" link "_1.23" 0}
      @{"DLG 1.24" link "_1.24" 0}

   Part III:   Plaintive Cries of Woe!

      @{"DLG 1.25" link "_1.25" 0}
      @{"DLG 1.26" link "_DLG1.26" 0}
      @{"DLG 1.27" link "_DLG1.27" 0}

   Part IV:    Christ, He's At It Again!!!

      @{"DLG 2.1" link "_2.1" 0}
@endnode

@node "Purpose" "Purpose"
 The Purpose of this Document
 ============================

This document is a guide of the various things that you, as a sysop, must
complete when upgrading to various portions of DLG. As we progress beyond
version 1.0, more and more things have changed, and some of them are
critical enough to keep your system from working!

The need for this document became apparent recently when a sysop was trying
deperately to upgrade to 1.27 from V1.16, and a number of essential steps
were missed because they were not documented as part of the 1.27 upgrade
process.

This document, then, will be provided as a part of this and all subsequent
DLG upgrades to ensure that you the sysop know what all is needed, what is
not needed, and where to find what you need to run the most current
software.

Please note: only the steps required to get you to the current software will
be retained in this document. Steps that are not required will be eliminated
to (a) avoid excess work on your part, and (b) ensure that your system
doesn't get scrapped in the processes. For example, all the dead-end
conversions done as part of the 1.23 -> 1.25 releases will not be needed,
and in fact may cause more problems than you really want to deal with.
@endnode

@node "_DLG1.1" "DLG 1.1"
 Upgrading to DLG 1.16 from 1.0 or earlier
 =========================================

 o You must have AmigaDOS 2.04 or later installed.

 o Update language files -- copy to DLGConfig:Languages/, CD to that
   directory, then run DLG:CompileLang

 o Ensure FILE:TempDownLoads exists. Create it if it's not there.

 o If you wish to use the new module FILESEARCH from your file menus, you
   will need to create an entry for it using the sysop's Menu Editor.
   Create an entry as normal and give it the following options:

      File Path:  DLG:FileSearch
      Type     :  Executable
      Load Type:  Overlay
      Pend Msgs:  Yes
      CLI Mode :  No

 o You can now filter new users so as to lock out undesireable users. The
   file that does this is DLGConfig:Misc/BadNames.BBS. The format of the
   file is simple: one name per line. ? and * wildcard matching is
   implemented.

 o You can now filter new users so as to lock out undesireable aliases. The
   file that does this is DLGConfig:Misc/BadAlias.BBS. The format of the
   file is simple: one name per line. ? and * wildcard matching is
   implemented.

 o If you are using DLG:RemovePort in any of your batch files, you will
   need to change it to "DLG:TKill -p <port> -f". RemovePort is gone.

 o You no longer need an assign for every UseNet newsgroup you import.
   Simply make one -- UUNEWS: -- and DLG will find the newsgroups. This
   assumes, of course, that you are using UUCP 1.17 or equivelent with
   hierarchial directory structure.

 o UNet2DLG now deletes news articles as it imports them. However, you can
   override this feature by specifying the -k option when calling it.

 o TPTFreq is gone, history. Enter DLGFreq, a lot faster. However, this
   speed is a result of using a precompiled index file. You create this
   index file using DLG:MakeIndex.  Please note that this filename
   collides with SkyFreq's MakeIndex program, so if you had it living in
   the DLG: directory (a bad idea), it has been overwritten. Well, we told
   you to make backups.

   You must run MakeIndex periodically to keep your file index fresh. We
   recommend running it nightly from your maintenance batch file (you DO
   have a maintenance batch file, right?)

   See accompanying documentation for DLGFreq for usage, etc. You will
   have to change a few things to make it work in place of TPTFreq.

 o Introducing DLGCP, the DLG Control Panel. This nifty little program
   replaces "Yahoo" and then some. Please read the accompanying
   documentation for usage.

 o When DLG was moved from Manx C to SAS C, one thing that was lost was
   the nifty overlay ability that the compiler had for its code. The
   overlay ability allowed DLG:Door to spawn the various BBS processes
   while a user was logged in, yet still stay loaded. To get around this,
   a program called "OM" now lives in DLG:. You have to set it up in all
   of your DLGConfig:Batch/*.startup files.  Here is a sample:

      ; sample startup file

      ChangeTaskPri pri 2

      FailAt 100

      Stack 16000

      OM DLG:Door    ; <-- there's the change!!

      DLG:Hangup
      DLG:FreePort >NIL: -p TR0 -k "BBS"
      EndCLI

   As stated, all your startup files, e.g. TL0.startup, TR0.startup, need
   to be changed to reflect this.

   If this change is not made, then the user will be dropped offline as
   soon as he logs in.

   Note also that the RemovePort CronE vent is gone. Door does this for
   you now.

 o Some programs may have irrational problems when dealing with users or
   groups, such as unable to find users you know exist. If so, contact
   Digerati Dreams for a program called "FixCaseBug".


 o A blanket statement: rename all PDQ*.* config files in FIDO: to DLG*.*.
   All PDQMail stuff should go away, and be replaced with DLGMail
   executables.  e.g. PDQMail.ARE becomes DLGMail.ARE, PDQMail.TIC becomes
   DLGMail.TIC, and so on.

   @{"On to 1.23!" link "_1.23" 0}
@endnode

@node "_1.23" "On to 1.23!"
 Upgrading to DLG 1.23
 =====================

DLG 1.23 started a departure from the old file structures to new file
structures that were designed to make DLG more powerful and flexible.
Unfortunately, these changes proved unpopular so they were removed in a
later version.

First of all:

  DO NOT RUN THE CONVERSION ROUTINES!!!! THEY WILL ONLY CAUSE YOU GRIEF!

 o FILE now has two new commands, subscribe and unsubscribe. You will need
   to copy the contents of DLGConfig:Menu from the archive to get these
   commands. Configure them as any built-in command.  Subscribe gives you
   the ability to add an area to your newscan list while viewing it,
   unsubscribe of course is the opposite.

 o Likewise, MESS has the same new commands.

 o ScreenEdit has changed. It is now a revamped EmacsDLG, courtesy of Alan
   Bland. You will need to edit your editor config files to use this new
   editor, plus run the config program. Read the ScreenEdit 2.0 docs for
   more details.

   On the web site, you will find ConvertEmacs, a handy program that will
   convert any EmacsDLG config files over to use by ScreenEdit.

 o Create a new directory: DLGConfig:Rexx.  You may put Arexx scripts here
   and DLGRX will search here FIRST for the script if no path name is
   specified.

 o You need a file called DLGConfig:Batch/Bulletin.DLGBatch. It must
   contain at least one line:

      DLG:Bulletin

   -- or, if you want to run another bulletin program, replace DLG's
   default bulletin program here.

 o Any program that tries to look at TPTRM directly will get a big suprise
   -- it's been renamed to ResMan. You shouldn't have anything doing this,
   but better to warn you than learn the hard way.

 o Additionally, the message port for ResMan has changed from
   tptrm.control to dlgrm.control. However, some programs, such as
   TrapDoor, will never be changed to accomodate this, so a dummy
   tptrm.control port is still there -- it just doesn't do anything.

 o The old MakeFList is gone. In its place, we have FileList and
   FileGuide. The former creates text files, the latter creates AmigaGuide
   files that the remote user can click on to generate FREQ files. Both of
   these programs require the index generated by MakeIndex.

 o The Lex Check flag is no longer honored. More bother than it was worth.

 o Jive, Kraut, and ValSpeak are gone.

 o FileMaint has a new menu option, FILEM_AmiNet. This option allows you
   to import AmiNet files that have accompanying .readme files. The file
   gets imported, and the .readme gets imported into the file description.
   Aside from the function name, it is configured exactly as Turbo Upload.


   @{"On to 1.24!" link "_1.24" 0}
@endnode

@node "_1.24" "On to 1.24!"
 Upgrading to DLG 1.24
 =====================

No changes required.

   @{"On to 1.25!" link "_1.25" 0}
@endnode

@node "_1.25" "On to 1.25!"
 Upgrading to DLG 1.25
 =====================

No changes required. This was more or less a maintenance update to un-do the
damage done by 1.23 and 1.24's new config file structures. The intent was to
bring the new features in, but not the incompatabilities. Ain't that nice.

   @{"On to 1.26!" link "_DLG1.26" 0}
@endnode

@node "_DLG1.26" "On to 1.26!"
 Upgrading to DLG 1.26
 =====================

   No changes required.

   @{"On to 1.27!" link "_DLG1.27" 0}
@endnode

@node "_DLG1.27" "On to 1.27!"
 Upgrading to DLG 1.27
 =====================

 o New modules, AreaEd and AreaTemplete. AreaEd replaces DLG:MsgAreas and
   DLG:FileAreas. You will need the menu files for these two programs, and
   you will need to set up AreaEd as a replacement for both.

 o You will need to create a directory called DLG:Fido. Evenally, ALL
   fidonet config files will live here.

 o Create a file called DLGConfig:Domains. This file tells DLG's fido
   modules how to handle different fido-style domains. For example, zones
   1 through 7 are in the FidoNet domain, zones 39 through 41 are in the
   AmigaNet domain. Here is an example:

      ; Sample DOMAINS file. Comments are OK.

      ; DEFAULT defines the fallback address your system will
      ; use if all else fails.

      DEFAULT 1:202/720.0 ; your default fido-style address here

      DOMAIN   fido  ; what you call it is irrelevant. Just be consistent.
                     ; This starts a DOMAIN block. All following entries
                     ; belong to the fido domain.

         Address 1:202/720 ; This is YOUR address in the fido domain.
         Zone 1            ; This and the following define what zones
                           ; are in this domain
         Zone 2
         Zone 3
         Zone 4
         Zone 5
         Zone 6
         Zone 7
      @DOMAIN        ; Marks the end of a DOMAIN block. We are no longer
                     ; in the Fido domain.

      DOMAIN   amiganet ; start the AmigaNet domain
         Address 40:405/101.0
         Zone 39
         Zone 40
         Zone 41
      @DOMAIN

   Note: you only need a default address. The rest is only needed if you
   are in multiple domains.

 o DLGTick now accepts a USEADDRESS command in a TICK area block. If this
   key word is encountered within an area block, that address will be
   substituted for your default address.


   @{"On to 2.1!" link "_2.1" 0}
@endnode

@node "_2.1" "On to 2.1!"
 Upgrading to DLG 2.1
 ====================

 o The format for DLGConfig:Misc/DLGSerial has changed significantly. Be
   sure to read up on that in the 2.1 upgrade docs. You don't really need
   to know what that format is, but you WILL need to convert to the new
   format for 2.1 or later. If you are not at this moment upgrading to
   2.1, you will need to get the keyfile converter archive from the DLG
   web site. If you are upgrading to 2.1 right now, it's part of the
   install routine.


 o If you have users on your system that for some reason you cannot edit
   or delete, they may have a corrupted level > 255. A program that
   shipped with 2.1 called RepairLevels will cure this. If you are not
   upgrading to 2.1 right now, you will need to get it from the DLG web
   site.

 o Although you probably are not running a demo, a file called
   DLGConfig:Text/TooManyUsers.txt is now available for DLG:Door to use if
   too many users are online when another user tries to log in. Right now,
   this only affects people running the demo -- it's limited to 2 users at
   a time - but later on, it will be quite useful for telnetted BBSs, as
   they may wish to limit how many users are on via the telnet pipe.

   @{"On to 2.2!" link "_2.2" 0}
@endnode

@node "_2.2" "On to 2.2!"
 Upgrading to DLG 2.2
 ====================

   Watch this space for further details.
@endnode

