README                                                 August 22, 1994

               What's New in Epi Info, Version 6.01


Epi Info, Version 6.00, was released on May 27, 1994.  Since then,
as expected, helpful users have identified a number of problems
to be fixed.  Version 6.01 was released during the week of
of August 22, and is available via ftp on the Internet and from
USD, Inc.

Some of the changes being made include:

Version 6.01 contains revisions that remove bugs discovered
in Version 6.00, as follows:
   1. Installation has been changed to allow custom installation
      for those who wish to install Epi Info in directories that
      are not directly subordinate to the root directory.
      To install Epi Info, type INSTALL as usual and then follow
      directions.

      For those who wish to use the installation program directly
      without the extra guidance of the program file INSTALL.EXE
      that precedes it, the main installation program has been
      renamed to INSTALL6.EXE.  INSTALL6 creates directories
      subordinate to the CURRENT directory of the drive you declare
      as the DESTINATION drive.  If the current directory of C: is
      C:\SOFTWARE, for example, declaring C: as the target drive
      for installation will create C:\SOFTWARE\EPI6 and C:\SOFTWARE\NETSS.
      INSTALL.EXE assures that you are logged to the desired directory
      and you do not need to worry about the details if you use INSTALL.EXE.
      If you choose to do a custom installation, with \EPI6 and \NETSS
      created as subdirectories of a directory other than the root
      directory, you must set a DOS environment variable called EIDIR
      to the name of the parent disk and directory so that Epi Info
      can find necessary text and data files.  The statement
      SET EIDIR = (Drive:\Parent directory) would be inserted in
      your AUTOEXEC.BAT file.  SET EIDIR = C:\APPS, for example,
      is necessary if Epi Info is installed in C:\APPS\EPI6.

   2. In ENTER, after a search for a record, if the user chooses not
       to edit the record found, the record was not reset to the
       end of the file, and a user might inadvertently overwrite
       the old record.  A message to users on a network informing
       them about competition for a file has been removed in 6.01,
       as the situation is resolved automatically.  Difficulties
       in automatic incrementing of <IDNUM> fields on a network
       have been resolved.

   3. EPED now imports European characters that are also in the
       IBM DOS character set from WordPerfect files.  The dialog
       box that appears with a multiple Find/Replace now moves
       out of the way to avoid occasionally hiding the item found.

   4. In ANALYSIS:
       A BUG THAT GAVE INCORRECT NUMERIC RESULTS IN TABLES OR
        FREQUENCIES WITH FILES CONTAINING MORE THAN 524,288
        RECORDS HAS BEEN CORRECTED.
       IN VERSION 6.00, ON COMPUTERS USING CERTAIN DOS CODEPAGES
        AND COUNTRY CODES, OTHER THAN THE STANDARD IBM CODEPAGE
        FOR THE U.S., MISSING VALUES AND NEGATIVE VALUES IN YES/NO
        FIELDS ARE LUMPED TOGETHER, LEADING TO INCORRECT RESULTS,
        IF SET IGNORE IS OFF.  The country codes for which this
        occurs are:
             Belgian 032
             Latin American 003
             Spanish 034
             Switzerland 041
        Country codes are set in the COUNTRY command in the CONFIG.SYS
        file, usually in the root directory of the disk from which
        DOS is loaded.  A typical COUNTRY command looks like this:
           COUNTRY=033,850
        This one specifies code 033 for France and code page 850
        (Multilingual).  Country codes for the US, United Kingdom,
        and most other countries do not cause this problem.
        THIS DOES NOT OCCUR WITH VERSION 6.01.

       The output of the FREQ command now includes the
        variable name when tables are suppressed with /N.  FREQ
        now produces correct statistics when multiple variables
        are specified.
       A runtime error when calculating Chi Square with more than 40
        degrees of freedom has been corrected.
       An error message now appears if a .PGM attempts to erase a
        current data set.
       An error message appears when there is an attempt to add a command
        (with CMD) when a command with the same name already exists.
        This error is not critical and is only displayed on the screen
        for informational purposes.
       A check has been added to prevent reading a file
        containing variables by the same name as an existing GLOBAL
        variable.  If an error message signifies that this is the
        case, the .PGM should be revised, either changing the
        name of the DEFINEd variable involved or, if appropriate,
        making it a standard or CUMULATIVE variable rather than a
        GLOBAL variable.
       A literal question mark can be included in a command by preceding
        it with a backslash (\?).  Previously any question mark was
        interpreted as part of an input command (?   ?).
        For example,   IMMEDIATE SELECT VANILLA = "\?"
        will select records in which the value "?" is in the
        record for VANILLA.  (ENTER, however, will not accept
        a "?" as the first character in an input field, so this
        is not a good code for "unknown." We recommend using
        the standard blank field provided by Epi Info as the
        unknown or missing value, or coding unknown as "9"
        or some other unused character.)

        Other escaped characters may be used in the
        "Get-Input command"  (?Message to User?) (see manual page 545).
        These escaped characters are:
        \N        insert a carriage return and line feed in the message.
        \R        insert a carriage return in the message.
        \?        insert a question mark in the message.
        \\        insert a backslash in the message.
        IMMEDIATE LET YR = ?Enter year\?\N  will print
           Enter year?
        and the cursor will be placed at the beginning of the following
        line.

   5. IMPORT no longer checks the length of lines being imported in fixed
        length, ASCII format, ignoring characters which may be in a record
        beyond the position of the record length given in the .REC file.
        This allows importing data such as:
             CORERECORD--
             CORERECORD--EXTRA DATA
             CORERECORD--
        into a .REC file that specifies the format for CORERECORD--

    6. The hypertext compiler (HYPER.EXE) and the hypertext
        viewer in the menus (EPI6.EXE), will now support topic
        names containing spaces, as in .TOPIC DeKalb County

    7. A number of changes have been made to accommodate use from a
       Local Area Network.  If tutorials or examples are run from
       the main menu while logged into an inappropriate directory
       a message now suggests using the SETUP function on the TUTORIAL
       or EXAMPLE menu. Depending upon circumstances, this either
       changes the logged directory to \EPI6 or offers to copy needed
       files from a read-only directory on the LAN so that Tutorials and
       Examples will run easily.  See INFORMATION FOR LAN ADMINISTRATORS
       below if you will be installing Epi Info for use on a LAN.

Version 6.01 was to be released August 22, 1994.
It is identified on the Internet by filenames containing EPI601_
rather than EPI600_.  It is recommended that all users upgrade to
the new version, particularly if they are having problems running
Epi Info on a network, work with files larger than 524,288
records, or use a DOS codepage or COUNTRY code other than the
ones for English characters.


                     GENERAL INFORMATION

Version 6.00 released     May 27, 1994
Version 6.01 released     August 22, 1994


Epi Info, a series of computer programs produced by CDC and the
World Health Organization provides public-domain software for
word processing, database and statistics work in public health.
Version 6 of Epi Info was released in May, 1994, and is
available from the source listed below and via the Internet.
There are more than 40,000 documented copies of Version 5 of Epi
Info in 117 countries.

Epi Info is a complete system for word processing, data entry,
database management, and public health statistics for

IBM-compatible microcomputers (DOS). Facilities are provided for
importing and exporting a variety of file types.  Although Epi
Info has its own file format, dBASE files also can be
analyzed directly.  The entire system occupies about 8.9
megabytes with all tutorials, examples, and utilities, but the
main programs occupy a total of about three megabytes.

Version 6 features a configurable pull-down menu, facilities for
producing and using hypertext (active text), additional
statistics, and many programming improvements.  Like previous
versions, it runs on IBM-compatible computers under DOS, and
requires only 640 K of memory (RAM), although a hard disk is
recommended.

The entire 600-page manual (except for one chapter of
statistical background for complex sample designs) is included
in hypertext format on the disks and is also available in printed
form.  CDC employees may obtain Epi Info and a companion program
for geographic mapping (Epi Map) from the CDC Warehouse.  Readers
outside CDC may obtain copies of these programs in English or of
Epi Info, Version 5, in Spanish from:

                 USD, Inc.
                 2075A West Park Place
                 Stone Mountain, GA  30087  U.S.A.
                     (404) 469-4098
                 FAX (404) 469-0681

The Epi Info, Version 6, programs and manual are $50 (U.S., $65
outside the U.S.), including shipping.  Epi Map and the Spanish
version of Epi Info 5 are each $38 (U.S., $48 outside the U.S.).
The programs and manuals may be freely reproduced, translated, or
given to others.


                      INTERNET INFORMATION

Epi Info and Epi Map are available on the worldwide Internet
using the following access information:

     Site: ftp.cdc.gov   UserID: anonymous
     Directory for Epi Info: /pub/epi/epiinfo
     Directory for Epi Map:  /pub/epi/epimap
     The compressed files occupy 3-4 megabytes for each product.

Files:
     EPI601_1.EXE  About 1.2 megabytes
     EPI601_2.EXE  About 1.4 megabytes
     EPI601_3.EXE  About 1 megabyte

These files are self-extracting archives. Obtain them via FTP in
BINARY MODE, placing them in a directory from which you will
install Epi Info (e.g.\EIINSTALL; do NOT use \EPI6). Execute all
three programs in this directory, which will produce a series of
compressed files and INSTALL.EXE.  Run INSTALL to install Epi
Info, using the (I)nstall option.  Directories called \EPI6 and
\NETSS will be created and Epi Info files will be decompressed
and installed. The installation files may be kept for further
installations (on diskettes or on a LAN) or deleted.

To create a set of diskettes of any size or density, format the
equivalent of three 1.44 megabyte diskettes, and run INSTALL
using the (C)opy option.  This will place the appropriate number
of compressed files on the diskettes and prompt you to insert
each as needed.

         DISK SPACE AND INSTALLATION OF EPI INFO 6
            (Making your own Epi Info LITE)

Version 5 of Epi Info consumed about 2.2 megabytes of disk space.
Version 6 is a much larger system, occupying 7.2 megabytes for the
main files, examples, and manual, with an additional 1.7 megabytes
for the surveillance system example that is included.

Version 6, like previous versions, is modular, and individual parts
may be loaded and used separately.  For those wishing to load parts
occupying minimal disk space, the following notes may be helpful:

   The minimal function of data entry only can be supported by
   loading only the ENTER.EXE and ENTER.OVR files -- 273 K
   with a suitable .REC and .CHK files for data entry,
   as used in door-to-door interviewing with a laptop
   computer, for example.

   EPED, ENTER, and CHECK together form a skeletal system for
   creating and editing questionnaires and setting up data
   entry, occupying 697 K. The ANALYSIS program with its .HLP
   file adds another 457 K, making a very useful core system
   in 1.2 megabytes.

   Adding EPITABLE, IMPORT, EXPORT, MERGE, VALIDATE, STATCALC,
   the EPI6 menu, and a number of examples increases the total
   size to 3.5 megabytes.

   Adding specialized functions for nutritional anthropometry,
   including EPINUT, and a demonstration program for making
   menus called EPIGLUE brings to total size to 5.1 megabytes.

   If all the .BGI drivers for printing graphs from ANALYSIS
   to different printers and file formats are loaded, they
   occupy another 654 K.

   The entire Epi Info 6 manual of 600 pages, when loaded,
   occupies 1.15 megabytes.

   The surveillance system example (NETSS) is 1.7 megabytes.

   The total size of the \EPI6 directory, if every option is
   loaded, is 7.2 megabytes.  With the \NETSS directory, the
   entire system occupies 8.9 megabytes of hard disk space.

   Remember, however, that most individual programs can still
   be run from 360 K floppy disks if necessary.


                INFORMATION FOR LAN ADMINISTRATORS

The main programs in Epi Info are LAN compatible.  ENTER allows
multiple users to enter data in the same file, using record-
locking techniques that work through DOS and are not LAN
specific.  ANALYSIS in Version 6.01 allows several users to read
the same file and give appropriate messages when trying to write
files if this is not permitted.

Epi Info may be installed on Local Area Networks (LAN's) in
several different configurations, depending upon the intended
use:
   1.  The compressed installable system, containing INSTALL.EXE
       and FILES1.EXE, FILES2.EXE, etc. may be placed in a LAN
       directory to allow users to install the system on their
       hard disks (using the (I)nstall option in INSTALL) or
       copy it to floppy disks (using the (C)opy option) for
       distribution to others or installation on a laptop
       computer.

   2.  The executable version of Epi Info may be installed
       in a LAN directory in a directory for which most users
       do not have write privileges.  It is important to use
       the INSTALL.BAT program to install the system.  The
       main programs and examples will be installed in a
       directory called \EPI6, which may be made read-only to
       most users.  Users should then run the system from
       another directory in which they DO have write privileges,
       either another LAN directory or their local hard
       disk drive.  If the sample surveillance system is
       chosen during installation, a directory called \NETSS
       is also created. This directory MUST BE WRITABLE for
       users, or provision must be made to copy its contents
       to another directory for individual use.

   3.  To install Epi Info in subdirectories that are not
       directly subordinate to the root directory (e.g., in
       N:\APPS\EPI6 and N:\APPS\NETSS), use the batch file
       INSTALL.BAT for instructions, or merely log into the
       parent directory (N:\APPS) and proceed with installation
       using INSTALL6.EXE.  The desired directories will be
       created subordinate to the currently logged directory
       on the DESTINATION drive.  To allow Epi Info to run
       properly with directories not directly off the root,
       a DOS ENVIRONMENT VARIABLE called EIDIR must be set
       to tell Epi Info where to find its directories.  In
       this case SET EIDIR=N:\APPS will do the job.  See
       the SAMPLE below.

   4.  It is possible for a user to install and run
       Epi Info in a writable directory on the LAN without help
       from the LAN administrator, although others having access
       to the same directory can then alter the files.

                            LAN NOTES

Some tutorials and examples require write privileges. Epi Info
programs need to write configuration files or save data files,
and this cannot be done in a directory for which the user does
not have read/write privileges. Although the system may reside in
a directory for which the user does not have write privileges,
the user must run it from a writable directory, either on the LAN

(if users are to share a single data file, for example), or on
the user's local hard disk.

If tutorials or examples are run from the main menu while DOS is
logged to an inappropriate directory a message now suggests using
the SETUP function in the TUTORIAL or EXAMPLE menu. Depending
upon circumstances, this either changes the logged directory to
\EPI6 or offers to copy needed files from a read-only directory
on the LAN so that Tutorials and Examples will run easily.

The PATH statement in AUTOEXEC.BAT must contain the location of
the Epi6 directory on the LAN.  This allows Epi Info to be run
from the LAN without being on the user's hard disk, although the
latter is also a reasonable option if there is disk space
available.

The programs should run faster if the system is copied to the
user's own hard disk and run from there (perhaps accessing a
common data file on the LAN).  Programs residing only on the LAN
must be loaded into RAM on the user's computer via the LAN, and
this can slow things down in some cases.


                SAMPLE (Novell) LAN INSTALLATION

In a Novell LAN, a batch file is placed in a directory called
M:\BATCH that is accessed when a user types EI6; the batch file
contains the following commands:

@echo off
cls
set eidir=n:\apps                 (Set an environment variable
                                   to tell Epi Info the parent
                                   directory for \EPI6 and \NETSS)
map ins s6:=sys:/apps/epi6        (Set up mappings)
map ins s7:=sys:/apps/netss
call m:home.bat                   (Be sure that the user is running
                                   system from a directory with
                                   write privileges)
call n:\apps\epi6\epi6.exe        (Run Epi Info)
map del s7:                       (Remove the mappings)
map del s6:
call m:home.bat                   (Go back to home)
set eidir=                        (Erase the environment variable)
echo on

Although other LAN's may have different configurations or
commands, perhaps this example will be helpful in setting up a
smooth system for accessing Epi Info.

To run the sample surveillance system contained in the NETSS
directory the user must be logged into the NETSS directory, and
must have write privileges.  There are several choices in setting
up NETSS on a LAN.  Here is one solution:

In the menu configuration file EPI6.MNU, in the DONETSS block,
delete 'REM' from the front of lines 5, 6, and 8, making
appropriate changes as needed; then add 'REM' to the front of
lines 3, 4, and 9. The commands are the same as for DOS batch
files.  Line numbers are for this discussion only and are not in
the file.

1  DoNETSS
2  BEGIN
3    cd %EIDIR%\NETSS
4    IF NOT EXIST NETSS.MNU GOTO NONETSS
5  REM   n:
6  REM  cd \apps\netss
7    NETSS
8  REM  call home
9    cd %EIDIR%\EPI6
10    GOTO END
11    :NONETSS
12     ECHO Could not locate %EIDIR%\NETSS\NETSS.MNU menu file for NETSS.
13     ECHO Was it installed?
14     ECHO If you are running on a LAN see README.EI6
15     ECHO NETSS must be run from NETSS directory
16     PAUSE
17    :END
18 End



               PRINTING THE ELECTRONIC MANUAL

The entire 600-page manual is accessible in electronic form
through the MANUAL portion of the menu.  If you do not have a
printed copy (highly recommended for convenience and bedtime
reading), it is possible to send the electronic manual either to
a printer or to a disk file in text format, using the facilities
on the menu.

You will find that the manual is divided into three files, each
of which must be printed separately.  The three files contain the
following sections:

        A. Title Page (p. 1) - Chapter 15;
        B. Chapter 16 (p. 191) - Chapter 32; and
        C. Chapter 33 (p. 415) - Alphabetic Index.

To print any file, do the following:

        1. Choose MANUAL and then CONTENTS from the EPI6 main menu;
        2. Choose any chapter in A - C above; press <Enter>;
        3. Press <Esc> ("Software Binder" should be at top of screen);
        4. Press <F5> to print this section (A, B, or C) of the manual;
        5. Be patient!  The printing will take some time.

When printing, be sure to give the correct initial page number for the
section you are printing so that the numbers printed at the bottom of
each page will correspond to those for the printed and electronic manuals.
Page numbers are available by choosing MANUAL and then CONTENTS from
the EPI6 main menu.

The printed manual contains figures showing major screens and is
well formatted.  It can be obtained from:

            USD, Inc.
            2075A West Park Place
            Stone Mountain, GA  30087  USA
            (404) 469-4098
            FAX   469-0681

or by photocopying a printed version.


             UPDATES FOR VERSION 6.00  July 7, 1994

MOVING AROUND IN A HYPERTEXT VIEWER

  The following keys are used:

   <Up>, <Down>, <Tab>, or <Shift-Tab> to move cursor to keywords
   <Page Up>, <Page Down> to scroll vertically one line at a time
   <Ctrl-Page up>, <Ctrl-Page down>, to scroll vertically one screen


MOVING THE CURSOR WITHOUT A MOUSE IN PROGRAMS THAT USE A MOUSE

  Several programs (IMPORT, EXPORT, CSAMPLE, VALIDATE, MERGE, and
the menus, are able to use a mouse.  If you do not have a mouse,
the <TAB> and (SHIFT-TAB> keys are used to move the cursor from
field to field.  This feature was not used in Version 5 of Epi
Info, but is consistent with modern conventions for Windows and
(should you ever use a Mac without a mouse) the Macintosh.  If
you have trouble moving around, therefore, try <Tab> or
<Shift-Tab>.


MATCH COMMAND

The MATCHED external command mentioned in the manual has been
integrated into ANALYSIS.  The MATCH command will provide all the
output that was formerly provided by the two commands, MATCH and
MATCHED.  The syntax for MATCH as given in the reference section
of the manual is incorrect with regards to the order of parameters.
The order MUST be

    MATCH <ID> <OUTCOME> <EXPOSURE>

for meaningful results to be produced.

In order to obtain the correct results the fields should be
specified in this order, as reversing the Outcome and Exposure
fields will give incorrect results.

EXCLUDING FIELDS FROM A GENERAL COMMAND ("NOT")

The word NOT may be used in a LIST command, as described in the
manual, to specify fields that should NOT be listed.  For
example, LIST * NOT AGE SEX will list all fields EXCEPT AGE and
SEX.  What is not documented in the manual, however, is that NOT
can also be used with the WRITE command.
  READ OSWEGO
  ROUTE OSWEGO2.REC
  WRITE RECFILE NOT TIMESUPP

will create a new .REC file containing all the fields from OSWEGO
except AGE.  This avoids having to name many fields specifically
if nearly all are to be included.


USER INPUT WITH THE ?  ? STATEMENT

When making an assignment to a variable with the ?  ? statement,
the word IMMEDIATE must be included for the assignment to take
place when the input is made.  For example:

   DEFINE YEAR #### GLOBAL
   IMMEDIATE YEAR = ? Year to process: ?

will work as expected, setting YEAR to the user's entry.  Without
the IMMEDIATE, however, the assignment will not take place until
a record of a file is read, even though the ?    ?  happens only
once, when the statement occurs in the program.  The IMMEDIATE
designation makes the assignment occur only once, at the time the
user input is obtained.


NEW FEATURES IN THE EPI6/EPIGLUE MENU SYSTEM

The following features were developed recently and are not
documented in the Epi6 manual.

þ SAVEAS

     The save as command can now be accessed from the <Ctrl-F9> key
     combination. This is particularly useful when MENUEDIT is not
     included in a menu definition.

þ MACRO FILE

     A set of commands for opening text files or hypertext files can be
     listed in a file with the same name as the .MNU file, and a .CMD
     extension. If such a file exists, the indicated commands will be
     executed when starting the program. The syntax for the commands is as
     follows:

     HELPFILE=<Name of help file>
     TEXTFILE=<Name of text file>
     COMMAND=<Value>

     <Value> can be: CASCADE, TILE, or a number corresponding to the rank
     of the menu options in the .MNU file. In EPI6.MNU, a value of 1 would
     launch Eped for instance.

     This can be use to display a welcome message, or a warning after
     installation, as in the NETSS example.

     There may be several commands of each type in the macro file.
     They will be executed in sequential order.

þ ROUTEFILE {<Filename>}

     A ROUTEFILE statement added in a function definition carries out
     the following:
       - does not erase the screen when swapping out
       - displays a message "running the program ..."
       - captures any DOS output and displays it in the built-in editor
         upon completion
       - default file name is $$OUT unless specified otherwise in the
         command. If a filename is specified, it erases any existing
         filenames with the same name.
       - see COMPILE THE SYSTEM menu choice in the EPIGLUE example

     Example:

     DoFileList
     BEGIN
       ROUTEFILE
       DIR *.REC
     END
     * Outputs in $$OUT

     DoFileList
     BEGIN
       ROUTEFILE DIRLIST.TXT
       DIR *.REC
     END
     * Outputs in DIRLIST.TXT

þ Background colors

     Ten colors can be defined for the background of a file, by using a #x
     statement at the beginning of a given line. The title will alternate
     the default and the alternate color for each line. Examine the EPI6.SCR
     file for an example. The colors are as follows:

        #1        Default Blue on gray background
        #2        Black on Gray
        #3        Red on gray
        #4        White on gray
        #5        Green on grey
        #6        Yellow on gray
        #7        Dark gray on gray
        #8        Dark green on gray
        #9        Reverse gray on blue
        #0        Blinking on a red background

þ Switch to specify the name of the configuration file

  /CFG=<Configuration file and path>

      EPI6.EXE looks for the presence of the following directories
      (in order):

              C:\EPI6
              C:\
              D:\ .. Z:\

      The first valid directory is assumed to host the configuration file.
      If this file does not exists, it is created with default values

   EPI6 /CFG=C:\SOMEWHER\MYNAME.CFG

  will result in EPI6 attempting to locate the configuration file indicated.
  If this file does not exist, the above algorithm is used. This switch is
  useful when designing a system calling several menus working together. It
  allows using one configuration file for all sub menus.

þ IDPRINT

  An IDPRINT standard function was added. When specified in a MENUITEM
  statement, it displays the printer setup dialog box.

  Example:
  MENUITEM "Setup printer",IDPRINT

New Features in the Hypertext Compiler, HYPER

þ Hyper compiler switches

    Two switches have been added to the hypertext compiler:

    /L: creates a file with the same name as the text file that is
        compiled and a .LST extension. This file holds a list of topics
        and their corresponding values. This is useful when using BRANCH
        topics, for activating a topic by default.

    /N: prevents the screen from redrawing when HYPER is called from an
        application. It is used mainly in conjunction with a ROUTEFILE
        statement in a function block (see above).

þ Predefined constants for TOPICs

  .TOPIC <Topicname>{=<x>}         {/NOWRAP}
                    {=DEFAULT}
                    {=MENU}
                    {=GENERAL}
                    {=MESSAGE}
                    {=BATCH}
                    {=BRANCH}

   <Topicname> is a name of your choice, used to define the block of the
   text that will be displayed when a call is made to this <Topicname>.
   In version 6.01, it may contain spaces to separate words.
   The < and > here mean "Substitute your own topic name," and
   are not included in the .TOPIC line.

   <x> is the optional Context number for context sensitive help.  This
   should be a unique number <10000. The DEFAULT, MENU, GENERAL, MESSAGE,
   BRANCH and BATCH are predefined values corresponding to the following:

   DEFAULT  Value=0. This corresponds to the default screen
            appearing when no active option is highlighted.
            There should be only one DEFAULT topic
            in a file. Range 1-1999 is reserved for built-in options of
            EPIGLUE, such as CUT and COPY.

   MENU     Value=2000, defining the lower bound of the range 2000-
            4999. Indicates that subsequent topics will refer to user
            defined menu options.  MENU should appear for the first menu
            option. There should be only one MENU topic in a file. All
            subsequent topics will be numbered incrementally, until a GENERAL
            instruction is encountered.
            .TOPIC MENU1=MENU is equivalent to .TOPIC menu1=2000

   GENERAL  Value=5000, defining the lower bound of the range
            5000-9999. Indicates the beginning of context free help
            screens in a context sensitive help file.  It will usually
            follow a group of topics relating to user defined menu.
            Only one GENERAL instruction is allowed in a help file.

            .TOPIC THE_REST=GENERAL is equivalent to .TOPIC THE_REST=5000

   BRANCH   Defining a value in the range 10000-11999.
            A TOPIC DO_THIS=BRANCH will call the specified help file,
            at the specified block. Each BRANCH topic should be given
            the instruction. Up to 2000 BRANCH topics are allowed in a file.

            Example:  .TOPIC CALLCASEDEF=BRANCH
                      CASEDEF.HLP,1100

            The file CASEDEF.HLP is loaded with the topic 1100 active.
            You need must have attributed a specific number to this topic
            by a .TOPIC CASE=1100. See topic HYPER in the EPIGLUE help
            file for explanation on how to generate a list of these values
            for a file.

   BATCH    Defining a value in the range 12000-13999.
            A TOPIC DO_THIS=BATCH will treat the commands in the topic
            definition as DOS batch commands.  It is possible to execute
            an external application from a hypertext file, such as
            displaying a graphic. Each BATCH topic should be given the
            instruction. 2000 BATCH topics are allowed in a file.

            Example:  .TOPIC SHOWGRAPH=BATCH
                      CD\HG
                      HG SLIDESHOW.SHW

            Reference can be made to the %P parameters in a batch block.
            Refer to the EPIGLUE.HLP file for explanations concerning
            the %P parameters.

   MESSAGE  Defining a value in the range 14000-15999. This is a
            reserved topic definition that will display a line of text
            in a popup box, at the cursor location, without erasing the
            screen.  It can appear anywhere in a help file, and can be
            multiple. Each MESSAGE topic should be given the instruction.
            2000 MESSAGE topics are allowed in a file.

            Example:  .TOPIC WARNING=MESSAGE
                      You have selected the warning topic . . .

    {/NOWRAP}

    When /NOWRAP is specified, text wrapping is disabled for the entire
    topic.

    Not more than 16000 topics can appear in a single help file. Each
    topic should be less than 30 Kb in size. No error message appears if an
    attempt is made to load a block larger than this, but the computer will
    hang... The size of the file is virtually limited only by disk storage.

þ Highlighted passive text

     The tilde ~ was added as an additional character for displaying
     highlighted text in hypertext mode. This character does not occupy
     space after compilation, and should be preferred to the
     combination ASCII 169 et 170 mentioned in the manual. However, ASCII
     169 and 170 are still supported.

þ Hypertext troubleshooting

     The previous limitation of a maximum of 130 characters per lines in
     a topic was extended to 255 characters. The maximum size maximum
     of a topic was decreased from 40 Kb to 30 Kb.

þ Microsoft Windows users

     A WINDOWS application can be called from a menu option or a hypertext
     keyword in an EPIGLUE application. However there seems to be a memory
     conflict when EMM386.EXE is used to set some of the extended memory
     as expanded memory. In such case, a EMM386 error message flashes when
     attempting to run the WINDOWS application. To get around this
     limitation, you can either comment out the EMM386 driver in the
     CONFIG.SYS file, or add a NOEEMS switch. This will prevent the
     computer from mapping extended memory as expanded memory.

     Example:
     DEVICE=C:\DOS\EMM386.EXE NOEMS

þ Graphic file viewer PICEM.EXE

     EPIGLUE example is provided with a public domain graphic viewer. For
     more information about this program, read the file PICEM.DOC in the
     EPI6 directory

CHANGES IN NETSS

þ MAPTITLE.EXE

     MAPTITLE is a utility program that updates the titles of maps created
     in EPIMAP. It is used by the NETSS application for automated updating
     of the MAP titles from within a .PGM. Refer to the PLACE.PGM file.
     The syntax is as follows:

     MAPTITLE <Map file> <Text file>

     <Map file> should be a standard file created by EPIMAP when saving a
     map. These files have a .MAP extension. If multiple maps are saved in
     the .MAP file, only the title of the first map will be updated.

     <Text file> is an ASCII text file corresponding to the four lines
     of the title that can be updated. In this text file, the following
     syntax can be used:
        - A blank line is not modified
        - A line with a single . is erased
        - A line with anything else replaces the existing one

     Example (the text in parenthesis is for comment only):
     This text would replace line 1 of the original file
     . (this would reset line 2 to a blank line)
       (nothing here would keep line 3 as it is in the original .MAP file)
     This text would replace line 4 of the original file.

             _________________________________________

     Details on the Huge-File Bug in ANALYSIS, Version 6.00

There is a bug in ANALYSIS for Version 6.00 that can give
incorrect results for files with more than HALF a MILLION
(524,288) RECORDS.  Most users do not work with files that big,
and should not encounter the problem. We have corrected this bug
and several others (data entry problems on networks being the
most troublesome) and will be placing version 6.01 on the
Internet within a few days.

For those interested in the mechanism of the large-file FREQ
problem, it concerns a mechanism in ANALYSIS to make selection of
records faster and more efficient when a file is processed more
than once.  In ANALYSIS, a bit map is maintained, with one bit
representing each record.  When a record is evaluated and found
to meet the criteria in a SELECT command, the bit for that record
is set to indicate that the record should be processed. On
subsequent passes through the file (with the same SELECTion
criteria) only the bit map needs to be consulted to decide
whether a record is processed or not, speeding up the processing
of the file if only a small number of records is selected.

The bit map is maintained in RAM, and is limited to 64 K (or
524,288 bits) in size.  Although a mechanism was provided to turn
off this feature with files having more than 524,288 records, the
mechanism was faulty and bits continued to be written outside of
the allotted 64 K area, leading to the erratic results with FREQ
that were observed.  Let me emphasize that, as far as we can
tell, the problem was LIMITED TO FILES OF MORE THAN 524,288
RECORDS, and is not a concern for smaller files.  There was also
a glitch in FREQ when the command was followed by several field
names, and this has also been corrected, but this one gave zero
results that were obviously incorrect for some of the ancillary
statistics, and would be considered inconvenient but not
dangerous.  Doing the FREQ with a single field name gave the
correct and complete results.

Many users will not be interested in so much detail, but
sometimes details are better than a vague feeling of mistrust for
all the statistics in Epi Info.  Although we can never guarantee
that all results for all data sets are correct, the problem
discovered with large files appears to be quite circumscribed and
predictable, and is not present in Version 6.01.


             ______________ End of News_______________