Subversion Repositories Brabant Water.oosterhout

       
                    RELEASE NOTES FOR MODSOFT REV. 2.4
        
       If you have problems using this software, call your local 
       distributor.
      
       The third disk labelled "Compact Drivers and Other Loadables"
       contains Compact Drivers, Quantum Drivers and Quantum DX loadables.
       This file set is not compressed.  You simply copy files you need 
       to where you know you can access them by Modsoft.

       Note 1: Modsoft and Modsoft Lite now require a minimum CPU of a 
       286 with 4MB total RAM. Better performance can be obtained
       on systems with a 486 or Pentium CPU, more extended RAM, and disk 
       space greater than 10 MB.

       Modsoft can no longer be supported on XT and AT systems. 
       CPU 286 systems without at least 4 MB total RAM will not be 
       supported as well.

       Note 2: Due to the requirement for greater than 30 files open
       simultaneously in Modsoft, MSDOS version 5.0 or greater is
       required. 

       Note 3: Do not use Doublespace in the TMP directory of
       Modsoft without disk caching or Modsoft performance will be 
       slower than normal.

       Note 4: Modsoft 2.1-2.4 contain a new file format scheme. 
       The Symbol and Comment files are now DBase IV compatible. 
       The configuration file format has changed. Modsoft 2.4 has an 
       added bit selection in the RDE

       If you have older Modsoft files, these files will be converted 
       into the new formats. After loading them into Modsoft via New 
       Program or Select Program, do a Save All Files to save the files
       in the new format. 
       
       This should also be done for all macros which may have been 
       created. Using the Macro editor, load the macro and then save 
       to the same name.
       
       A program which you have saved in Modsoft 2.1-2.4, will not 
       be able to load into a previous version of Modsoft. It is advisable 
       to save all program and macro files created from the previous 
       release onto a backup disk.

       Note 5: Reference symbols are now 32 characters.  Reference 
       descriptors are now 199 characters.  Reference Tags no longer exists.
       When Modsoft reads a 2.0 file, it has to decide what to do with the
       Tag information.  Unless instructed otherwise, Modsoft puts the Tag
       in front of the Descriptor when converting from Modsoft 2.0 to 
       Modsoft 2.1-2.4.  You can instruct Modsoft to place the Tag 
       immediately after the Symbol, by either running Modsoft /i or by 
       turning off (0) the iec_standard flag in the UPF or the UPF editor.  
       These flags allow any character to be placed in the symbol field (even
       spaces), as long as one character is a letter.

       For example, if in Modsoft 2.0/2.01 you have

       REF    SYMBOL     TAG          DESCRIPTOR
       00001  valve1     Drop 3       This controls intake into tank 1

       This will convert to Modsoft 2.1-2.4 as (default):
       REF   BIT    SYMBOL                           DESCRIPTOR
       00001        valve1                           Drop 3
                                                    This controls intake into 
                                                    tank 1

       However, if you type MODSOFT /i or set iec_standard=0 in MODSOFT.UPF,
       the symbols and tags will convert as:
       REF    SYMBOL                           DESCRIPTOR
       00001  valve1 Drop 3                    This controls intake into tank 1


       Note 5: Modsoft 1.1->Modsoft 2.4 requires that the MAP 3.0 
       communications can only be used with version 2.3 or greater of 
       the ISOcomm software.
       
       Note 6: The Configuration Extension, S980 Address, is not utilized
       by all versions of the S980. If the S980 User's manual does not have
       information about the S980 personality mismatch detection, do not 
       use this feature.
        
       Note 7: The 984-685E, 785L, 785E, and Quantum controllers must use DX 
       Loadables with a revision level of 192 or greater. 
       
       Note 8: When using the Loadable function in the Configuration,
       the User's Manual mentions that the loadable DX files will be placed 
       in the Macros Directory. The Macros directory is selected via Program 
       File Settings and is usually the same directory as is used by the 
       rest of the program.

       Note 9: The Modsoft Print Utility attempts to open and use three 
       different font styles: (1) The network graphics are selected to be 
       constant pitch; (2) The comments and symbols are in a scaleable font 
       for information to be placed above a node; (3) The text for the 
       configuration information is fixed pitch for tabular alignment, 
       but smaller type size (minimum 8 points).
       
       Most older printers will not support all three type faces. 
       
       Selecting the minimum font size will have different effects on the 
       three potential fonts.  1) there is no effect on the fixed pitch 
       graphics font.  2) The general text font may not have the ability to 
       be set to the exact font size requested, and may end up smaller.  
       3) The comments and symbols font may be scaleable and show up as the 
       only thing that appears to be obeying the minimum font size rule.
          
       It is advisable to try an experimental printout of a single network
       to see the effects of your font size selection.  

       If you do not set a minimum font size in the UPF editor, the 
       minimum font size is implied to be 6 points, and is guaranteed to 
       apply only to the scaleable font used for comments and symbols in the 
       network listing.

       Note 10: Not all the 4X registers are being marked in the Used
       Reference Table. This is due to functions, such as XMRD and XMWT
       which use indirect addressing for the destination of data. Due to the
       fact that the values in these pointers can change control of the
       application, there is no way any programming package would be able
       to automatically build a 4X used table that would include these 
       registers.

       The recommended work around is to use other functions such as BLKM
       in the logic so that the 4X registers will be found as used and placed
       in the Ref Used Table. These functions can be placed either in the
       same network as the functions that are indirectly using them, so that
       the cross reference can generate the correct network for the
       reference usage. Or, if scan time is an issue, the BLKM functions
       can be placed in a segment that is not being used and has been
       removed from the segment scheduler so they will not be scanned.

       Note 11:
       RTU protocol: This protocol was designed for optimal speed and as a
       result has very strict timing restrictions. The protocol requires
       that a message be transmitted with less than a 3.5 character time
       gap between each character transmitted. A gap in excess of the
       3.5 characters is seen as the end of the message. On dedicated
       machines such as a PLC, this is not a problem, but on a multipurpose
       machines such as a PC, this is difficult. Interrupts from the
       system clock, a Modbus Plus card, the keyboard, or a network card
       can all take the CPU several milliseconds. This can delay the
       transmission of characters when the baud rate is 9600 baud beyond
       the 3.5 character limit, thus terminating the message. The PLC
       sees this message as being incomplete and ignores the message.
       Modsoft must then time-out and try again.

       The problem is more severe on systems such as Windows, Windows 95,
       and Windows NT, where there are other tasks executing at the 
       same time. This can cause delays that render RTU mode unusable.

       There is no one solution to the above problem. The following three
       suggestions are given as possible workarounds.

       a) If RTU is a problem on a system with network cards, remove the 
          drivers when running RTU. In older versions of Modsoft, the
          Modbus Plus driver was turned off when RTU was to be used,
          however, customers that were using Modbus Plus for another
          application simultaneously could not run. Since Modsoft no longer
          turns the Modbus Plus driver off, the user must turn off the
          driver manually.

       b) Another suggestion involves the use of PC systems with 16550
          UARTs. These systems have a transmission queue of 16 characters,
          so the PC has the transmission time for 16 characters to do other
          things before a message in incorrectly terminated. A faster CPU
          also lessens the impact by processing other tasks more quickly.

       c) The final suggestion involves avoiding use of RTU mode on systems
          where it is a problem. The ASCII protocol will handle RS-232
          communications with the PLC with little degradation in performance.
          Modbus Plus is also an option where the PLC can handle the protocol.

       Note 12: The Modsoft Reference Symbol File is stored in dBase IV format.  
       This allows the customers to use non-Modsoft tools to view or change the 
       file. Although we encourage looking at the file from other office systems 
       (such as Microsoft Excel or Access), we discourage making changes to this 
       file through any method other external to Modsoft.  Using other products 
       to change these files may damage the relationship between the data base 
       and the index file, or it may introduce illegal reference numbers or 
       symbol names.  If you want to make changes to these files outside Modsoft, 
       write a routine to create a Symbol import/export file, and then import the 
       symbols through the Symbol Editor.
 
       The Symbol file is stored as <programname>.RFS and its index file is stored 
       as <programname>.RFI.  Before viewing these files with a dBase IV reader, 
       rename them to GRSF1TMP.DBF and GRSF1TMP.MDX. 

       Likewise, the Modsoft Program Comment Files are stored in dBase IV format. 
       These, though, are even more difficult to view and manipulate outside of 
       Modsoft, because they user dBase memo fields. The Comment file is stored 
       as <programname>.PCM, its index file is stored as <programname>.PCI, and 
       the memo file is stored as <programname>.PCT.  Before viewing these files 
       with a dBase IV reader, rename them to PCMTMP.DBF, PCMTMP.MDX, and 
       PCMTMP.DBT, respectively..
      
       Note 13: On PCs which utilize Network software; there exists the 
       possibility that the Modsoft Install and Update disks may not be able 
       to install/update. If this happens, please disable the Network TSRs, 
       reboot the PC to release memory resources and attempt re-install of 
       Modsoft.

       Note 14: MSDOS 5.0 and EMM386. It has been noticed that Modsoft
       will not run while using MSDOS 5.0 and EMM386 with the NOEMS switch
       while Modsoft using MSDOS 6.0 with EMM386 with the NOEMS will run.

       If you are running MS-DOS version 5.0, using EMM386 with the NOEMS
       option, this is not recommended. The NOEMS option causes EMM386 to 
       switch into Virtual 8086 mode without activating the EMS or VCPI
       interface. As a result, only a very limited amount of memory is available
       to 286|DOS-Extender.

       Regardless of which version of DOS you are using, you must be careful
       when selecting EMM386 options. Some of these options conflict with
       one another, and choosing them can cause EMM386 to become unstable with
       respect to 286|DOS-Extender. One such set of conflicting switches is
       the NOEMS/FRAME=xxxx/RAM/mX group. Each of these EMM386 switches affects
       the creation of an EMS page frame and should not be used together. If
       you must use any of these switches, please ensure that only one is selected.
       Specifying FRAME=NONE is satisfactory for most users.

       EMM386 Switch Setting for CONFIG.SYS:

                  DEVICE=c:\dos\emm386.exe frame=none

       QEMM Switch Setting for CONFIG.SYS:

                  DEVICE=c:\qemm.sys frame=none

       386MAX Switch Setting for CONFIG.SYS

                  DEVICE=c:\386max\386max.exe pro=c:\386max\386max.pro            

       NOTE 15: Installing or Updating Modsoft may require you to register
       your name and company name. The use of the apostrophe in the Your Name
       and Company Name fields will corrupt the fields such that when
       Modsoft is invoked the user will be placed in Trial Modsoft. DO NOT
       USE APOSTROPHES in these fields. If this happens call your Customer 
       Support for a new "text2.sys" file and re-install the software as 
       instructed.

       NOTE 16: There are situations where Modsoft communications could be
       unreliable due to limitation of the capabilities of the hardware.
       If the user has a slower PC and was trying to use Modsoft at 19200
       baud under Windows, the failure appears to be a receive overrun. 
       This means that the 984 PLC sent characters to the PC faster than the
       PC software could process them. With Windows running, Windows itself
       and other operating software can be taking CPU time away from Modsoft.
       At 19200, the CPU only needs to be away from Modsoft for 2-3 ms for
       an overrun to occur.

       There are several solutions that should be looked at. First, the mix
       of executing Windows applications should be examined, and the priorities
       set so that Modsoft has enough time to run. A slower baud rate will 
       also help. Running on a faster PC is another solution. A final solution
       is to use a PC with 16550 UART. This UART was designed to help Windows 
       with this situation by increasing the hardware receive buffer from 3 
       to 16 characters (increasing the time before an overrun occurs from 2
       milliseconds to 8 milliseconds at 19200 baud).

       NOTE 17: The new Quantum controllers have additional function built-in
       function blocks. This may cause collisions with loadable functions
       using the opcodes now assigned to builtin functions. If this happens,
       go to Offline->Config->Loadables and change the opcodes to unused ones.
 
       NOTE 18: Sy/Max implementation in Quantum is controlled by the UPF editor.
       Selecting "Yes" to the Sy/Max S908 IO Drops field grants the user, permission
       to configure Sy/Max S908 Drops and Sy/Max Ethernet Config Extension.
       Turning off ("NO") the Sy/Max flag does not cause the programmer to loose
       the Sy/Max drops or the Ethernet Config Ext if already created.

       NOTE 19: When using Modsoft Lite and setting the Modsoft driver via the UPF 
       editor, please be certain that the file created is named 'lmodsoft.upf'.
       If not, the editor assumes 'modosft.upf' and Modsoft Lite will ignore this
       name and the MB+ setting. 

       NOTES ON MODSOFT 2.4 VERSION:

       NOTE 20: Via TCP/IP, it is not possible to get the hardware ID., the
       executive ID., or the executive rev. on a per slot basis through
       the Quantum Backplane. The only per slot information that is displayed
       is personality and module description.

       NOTE 21: If you see this message "TCP/IP can not assign requested 
       format" ensure that a TCP directory exists. The TCP directory should 
       contain a SERVICES, PROTOCOL, HOST and RESOLV.CFG file.  See the 
       READ.ME in the \modsoft\vsl directory for further information on the 
       contents and placement of the TCP directory.

       NOTE 22: If you see this message "Timeout without a PLC response" using
       TCP/IP, check the communications_timeout in the UPF and increase it, if
       necessary.  A value of 30 seconds should generally suffice for TCP/IP.

       NOTE 23: If you see this message "The selected Communications Mode is
       not available when using TCP/IP, ensure that you can "ping" the node
       in question.  Ensure that the TCP/IP and the Network Module drivers
       are loaded. Ensure that the VSLDOS.INI file correctly reflects the 
       Network Module (netmod) corresponding to your TCP/IP stack.  See the
       READ.ME file in \modsoft\vsl directory for further information on
       loading the communications drivers and configuring the VSLDOS.INI
       file.

       NOTE 24: TCP/IP communications reports Rtcp (Running controller via
       TCP) or Stcp (Stoppped controller via TCP) in upper right corner of 
       the screen while online to a controller.  Usually this field 
       reports the status of the controller as well as the slave address. For 
       TCP/IP, the slave address does not exist.

       NOTE 25:Users unfamiliar with the TCP/IP protocol may not realize
       what constitutes a broadcast address. See Documentation for NOE 211
       module.

       If the user enters an IP address that is a broadcast address, or enters an IP
       address that is illegal, the cursor will be placed at the beginning of the
       IP address field and Modsoft will wait for a correct address to be entered.

       NOTE 26:Loadables that have an extension of .exe produce different library
       files for 16 bit controllers( e.g. Quantum 186, Compact, Micro, 984 slot
       mount controllers) and 32 bit controllers (Quantum 424, VME 424). The loadable 
       files are only common in the original distributed file (relocatable
       format). Due to this, it is not possible to load and run library loadable
       file for the 186 on a 486 controller and vice versa.  It is therefore 
       STRONGLY recommended that you segregate your project programs for 32 bit
       controllers from all other 16 bit project files.

       NOTE 27:Projects List: If there are over 116 project names in your projects 
       subdirectory, the screen cannot show them all at the same time.  A border 
       for the projects selection list will contain  --<<----- project ----->>--
       to indicate that more names in the list by pressing either the right 
       arrow cursor key or the left arrow cursor key.
       
       The maximum number of projects that can be shown in this expanded 
       window is 252.
       
       It is recommended that you do not have so many projects in a single 
       projects directory. A grouping of your projects by geographical or 
       functional categories is recommended to keep the number well below 
       116 in a sub-directory.
       
       Known bug:There is at least one place where this extended projects 
                 list is not yet implemented.  This is in the LIBRARY prg 
                 file list.
       
       NOTE 28: Config size adjustments from prior releases:
       Modsoft 2.4 corrects several places that the config size was incorrect 
       in the past.  You may find that attempts to go on-line in combo mode 
       from Modsoft 2.4 without first transferring the program to the PLC 
       from Modsoft 2.4 can prevent access to the configuration section. If 
       this happens, transfer the project to the PLC later at a convenient 
       time.
       
       NOTE 29: Printer databases compatibility:
       It may be possible that your new printers.pdb contains changes, from 
       the previous release. Such changes are not automatically reflected in 
       YOUR Modsoft.pdb. This will not affect your current printing with 
       Modsoft.pdb.  However, if you edit your printer preferences using the 
       UPF editor, you may encounter compatibility issues between the 
       databases.   If this happens,  and you need to change the definitions 
       or your device, you will have to re-define the printing device that 
       has the conflict, after removing it from the Modsoft.pdb database.
       
       NOTE 30: .EXE Loadables Library files:
       When a project is transferred from the controller to a set of files, 
       any .EXE loadables that are transferred are saved within the project 
       files for subsequent downloading.  These transferred loadables are 
       in absolute addressing format, and are now applicable only to the 
       project and to the PLC type.  Any attempt to change PLC type on 
       the program will potentially make the loadable un-usable.  If this 
       happens, it will be necessary to delete the project's .msl file in 
       your programs directory and configure the loadable once again. 
       
       NOTE 31: LIBRARY operations:
       When copying and pasting from Library prg files, it is wise not 
       to do too many networks at a time.  As in many other editing operations 
       in your PC, it is recommended that you exit and/or save the changes 
       made frequently.  It is recommended that you limit your repeat 
       operations of entering the library to five or six, before exiting the 
       ladder editor and saving the changed files.
       
       NOTE 32: Correct PC date is important;
       Modsoft will prevent you from using a PC date prior to 1994. This 
       can happen accidentally if your PC's clock battery needs replacing. 
       
       NOTE 33: Pasting networks with comments:
       Pasting Networks can take a long time to perform if a large number of 
       networks are selected at the same time.  Times of over 10 minutes have 
       been experienced.  

       Recommendation:  Do ten or so at a time, and then exit the editor, and 
       then save the program. 


       The following problems, discrepancies, and workarounds have been found 
       in MODSOFT 2.21->2.4:
       
       ***Problem 1***
       If you push to DOS and try to PRINT or invoke a new TSR, you may hang 
       DOS, if memory is low. 
       
       ***Problem 2***
       CTRL F7 will not function in the CfgExt, Segment, Loadable screens.

       ***Problem 3***
       If Modsoft crashes while you are editing ladder logic in the Macro
       editor, Modsoft /s will not restore the macro edited.

       ***Problem 4***
       The Micro 311/411 and the A120 controllers do not have a second 
       Modbus Port, however, a second port is displayed and can be edited. 
       If the second port is edited, it will be ignored.

       ***Problem 5***
       If you create a loadable with 3 character names, Modsoft will change 
       them to four characters. The fourth character is an underscore(_).

       ***Problem 6***
       If you are in the CfgExt screen, setting the Words Reserved to a 
       value above what the controller has for memory, causes the
       Size of Full Logic Area to set to zero. You will get an error 
       message "Specified registers/references do not fit in controller
       state RAM".

       ***Problem 7***
       The RDE plus (+) key does not work with the Range function.

       ***Problem 8***
       Search Previous/Next in Online/Combo mode will search relative to 
       the last search location. Offline Search Previous/Next searches
       relative to the current cursor position.

       ***Problem 9***
       The Ports screen will scroll if you press page up/down.

       ***Problem 10***
       Peer Copped references are not noted in the used reference table.

       ***Problem 11***
       Create a IO Map online and start the PLC while still in the IO Map
       editor. Type ALT-N to goto next drop, you will see the warning
       message "PLC in Optimize Mode". Modsoft is trying to write the drop 
       again to the PLC. This is only an error message and does not
       impair usage of Modsoft.

       ***Problem 12***
       If you use Reference Zoom on a register and change the value Offline,
       with the RDE and register on the screen; you will notice that the 
       register did not change value. PageUp or PageDown keys can be used
       to refresh the screen.

       ***Problem 13***
       When changing between 800 and 200 series I/O controllers, remember to
       change the number of drops/channels from 1 to an even number. 200 
       Series I/O requires 2 channels per drop. If the channels are not even 
       numbered, upon controller startup, an error 0800 (Invalid Segment 
       Scheduler) will appear.

       ***Problem 14***
       When using the Offset feature in Netlist, both start and end 
       references must be of the same reference type (0X, 1X, 3X, or 4X).

       ***Problem 15***
       Due to the fact that the M984 iomap is organized inside the PLC
       differently from other 984's, the cross reference list building
       operation does not find references in the iomap of this plc.
       Network references are found and reported, however.

       ***Problem 16***
       On E785 Quantums, drop 1 is local. You can not use "GOTO drop 1".
       You will get an error message. The work around is to use the Previous 
       or Next Drop command to get to Drop 1.

       ***Problem 17***
       Modsoft erroneously allows Peercop global input of 64 nodes, 
       8 subfields, 1 word over the 500 words maximum. The results in the 
       PLC are indeterminate.

       ***Problem 18***
       If you insert a three node function block over a one node or two
       node function block, you may see the new three node function block 
       one set of ????? missing in either the middle or bottom node. Type in
       the missing reference or constant value, to fix the problem.      

       ***Problem 19***
       Modsoft 2.21/2.3/2.4 allows configurations larger than 32K words. Most 
       controllers, except Quantum 424 and the VME-424, will disallow this.
       When an attempt is made to download a configuration greater that 32K
       an error message "Illegal Config" will be issued from the controller.
             
       ***Problem 20***
       Modsoft incorrectly write the constant sweep register numbers when 
       in Online/Combined modes. This only happens if registers above
       9999 are attempted to be used for constant sweep. Example: 419998-
       419999 becomes 409998-409999. The work around is to use only 
       registers below 9999 for constant sweep.

       ***Problem 21***
       More than 14243 words of IOMap area in 785E Quantum will cause an 
       "Illegal Config" at download.

       ***Problem 22***
       You can not use reserved system words for filenames, such as
       CON, PRT, PRINT, etc.

       ***Problem 23***
       If one or more *.tmp files are either write protected , locked or
       hidden in your \modsoft\tmp directory  Modsoft may incorrectly store 
       the <program>/prg file after transfer from the PLC to File.  This should
       be an unusual occurrence, requiring an outside influence or intentional
       action within the operating system.  The only method to correct this
       is to un-protect or free the file(s) and repeat the transfer from the 
       PLC to File.

       ***Problem 24***
       Conversion of files with macros to flat files may experience database
       errors. If this happens, it is necessary to temporarily rename the
       macro comments file names so they will not attempt to convert. After
       the conversion, the macro comment file names may be re-instated.

       Example:    Original Name              Temp rename
                  --------------------------------------------------
                    <macro>.mcr    ----->   <macro>.mcr  (no change)
                    <macro>.dbf    ----->   <macro>.fdb
                    <macro>.mcm    ----->   <macro>.mmc
                    <macro>.dbt    ----->   <macro>.tdb

                     Temp Name            Rename back to Original
      --------------------------------------------------
        <macro>.mcr    ----->   <macro>.mcr  (no change)
        <macro>.fdb    ----->   <macro>.dbf
        <macro>.mmc    ----->   <macro>.mcm
        <macro>.tdb    ----->   <macro>.dbt
       

       ***Problem 25***      
       Modsoft does not test the validity of nodes being pasted. In offline mode
       this is not a problem as the download process will test the nodes for
       validity. In online or combined mode, the controller tests the nodes
       and rejects illegal nodes.  Modsoft does not guard for this rejection
       in the paste operation and can result in a General Protection Fault. This
       is possibly can happen when copying and pasting from a library program
       since the library may have loadables that are not in the current PLC.

       
       ***Nuance 1***
       Pressing the Print Screen Key (or CTRL-P) may cause "Checksum Errors" 
       if the user is logged into the controller.
       
       ***Nuance 2***
       If an attempt is made to process a large group of references using 
       the Offset feature in the Symbol Table, expect the process to
       take a long period of time to finish. 
       
       ***Nuance 3***
       If you set your Location of Program Names to a drive other than C:,
       CTRL C out of Modsoft, then utilize Modsoft /s, the pathname
       will now default to c:\modsoft\programs. To prevent this from 
       happening, type the full pathname with the /s switch on the DOS 
       command line (i.e. modsoft /s d:\test).
  
       ***Nuance 4***
       To prevent splitting of networks across page boundaries you must
       limit the number of rows (lines) of comments and symbols that will 
       be printed. (This is very dependent on the capabilities of the printer.
       Use landscape mode wherever possible.) 
       
       To do this, use the UPF editor in the printer options, to
       set the maximum rows of comments and symbols. Generally limiting
       it to 2 rows of comments and 2 rows of symbols is adequate to keep
       7 nodes of network graphics on a page. Also invoke the single network
       per page parameter.

       ***Nuance 5***
       To get the best out of using laser printers: Since some of the older
       laser printers do not have so many fonts available, and the nicer
       IBM-2 character sets only come in one size, it is recommended that 
       you always use the laser printer in landscape mode when that mode is 
       available from the printer. This will also provide more efficient
       use of the paper.

       ***Nuance 6***
       If you are using Modsoft and a mouse in a Windows environment, make 
       sure you are using the full screen display. If you use partial
       window mode, the mouse movement will appear to have lost 
       synchronization with the window.

       
                     
                     NEW FEATURES IN MODSOFT 2.4

       1) Configuration Overview
       
                  Reusable Coils  :  ( ) Yes  ( ) No
       
       This new option allows reuse of coils in the Quantum and the "E" 
       controllers. This option is identical to the /d (duplicate-coil) 
       startup switch, and the Modsoft.upf file entry  "duplicate_coils = 1".
       ALLOWING DUPLICATE COILS or RE-USABLE COILS IS A POTENTIALLY DANGEROUS 
       OPERATION. The user must be aware that this function should only be 
       used in places which do not present a danger in ladder logic if a 
       coil is energized inadvertently.  A warning is issued each time you 
       enter the LADDER screen, Reuseable Coils has be set to Yes. When 
       Reusable coils are selected "Yes", you place the starting coil 
       address you wish the coils to be re-usable.  Modsoft will continue 
       to monitor and warn you when downloading duplicate coils.  Find the 
       Reusable coils range selection in the Configuration overview screen.
       
       2) UPF editor GENERAL KEYS
       
                 Safety Y N Defaults: ( ) Convenient  (.) Safe
       
       There are several places in the Modsoft operations which are hazardous 
       if the user selects the default YES or NO answer to a warning message, 
       by pressing the ENTER key.  It is generally considered "convenient" to
       accept the default answer.  When safety is at stake, this option will 
       require the user to change the answer to cause the action to completed.
       Most frequently the "convenient" answer is Yes, and the "Safety" 
       answer is No.  In some cases the opposite will be the case. In any case, 
       if the "Safe" option is selected here, Modsoft will provide as the 
       default that answer that will NOT complete the action if the user 
       simply presses the ENTER key.
       
       3) UPF editor GENERAL KEYS    
       
        Disable Mouse:  (.) Yes  ( ) No
       
       Modsoft's use of the mouse is a carry over from older DOS applications, 
       and is not consistent with the most modern uses of the mouse as a pointing 
       and selecting device.  For this reason, you are allowed to disable its 
       use in.
       
       This does not disable use of the mouse in the UPF editor or in any 
       other application or Windows, only in Modsoft.
       
       When the mouse is disabled, none of the other mouse related vertical 
       and horizontal speed numbers have any meaning.
       
       4) Clearing the RDE Template
       
       When you change project names offline for any reason the current
       RDE template (temporary copy) will be cleared.  You will no longer
       see the RDE template carried from one project to another or from 
       one online controller to another.   
       
       When leaving online, and going back online to the same controller, 
       it is not possible to know if you are switching  between controllers
       or back to the same one.  Thus in such a case, the RDE template is
       also cleared.
       
       If you wish to keep the RDE template, save it as a file and reload
       it when back on-line.
       
       
       5) Project name on Screens
       
       The project name is now displayed on screens after selecting a project 
       from the selection list.  The name is seen between the F1 and F3 
       positions on the function bar at the top of the screen.  This is the 
       "Project" name, that is the name of the .env file.  The "State" 
       display has moved to the right.

       The project name can only appear if the project is "opened".  The 
       project is not opened when in the ONLINE mode, even if you selected 
       the controller project from a project list.  
       
       6) PLC/IO Status Table Index
       
       You are now able to get an index of the STATUS table by pressing 
       page UP in the PLC/IO Status Screen.  The Table Index is actually 
       the last one two pages of the table.  Press page up a second time 
       to get to the first page of the index.  From the index find the 
       desired page and use the Goto menu item to move directly to the page 
       you enter.
       
       7) Import TOS, non-overwrite option:
       
       When importing symbols and descriptions, it is possible that the
       import operation could potentially overwrite an existing record with
       different information.  Since the records are keyed by the reference
       number and by the symbol, either of these fields matching an existing
       record would be potential overwritten.  In the event that such an
       overwrite occurs with at least something different in the record,
       you will be warned of the overwrite.  You have then several choices;
        
               "No", to skip the overwrite, 
              "Yes", to cause the overwrite,
             "None", to skip all overwrites, but process non-overwrites.
              "All", to cause all overwrites.
              <ESC>, to cancel the job at this point.  
       
       In the case of ESC, Any overwrites that have been allowed already, are
       in the database.  The only way to preserve the old database is to exit
       from Modsoft without saving the changes.
       
       You will not be informed of any records that are identical.  Identical
       records are not updated in the database.
       
       8) New Setting of Config Extension Area Size:
       
       In the Config Overview screen, you will see new info at the Config Ext.
       Size field.  Also you will see how many words have been used;
        
           Cfg. Extension  Used/Size  150/ 1000    for example.  
       
       In addition, when you wish to change the size of the ext area the 
       current value is the default, such that hitting ENTER will keep the 
       value the same.  Previously, it would have changed to zero if 
       accidentally accessed.
       
       If you attempt to reduce the size below that required for the 
       current used extensions, you will receive a warning and an opportunity
       to change your mind about the new size.  If you allow the smaller size,
       all current config extensions will be deleted.
       
       If you wish to delete only a selected config extension, do so via the
       config extension's individual delete feature.
       
       9) Allow deleting a peer cop node
       
       A new menu item in the Peer Cop is to delete the current node on the 
       screen.  A warning is given and the node is deleted if answered 
       "YES".  If the last node is deleted, a window opens to allow entry of 
       a node. This is identical to the initial screen of an empty Peer Cop.
       
       10) A new feature in Modsoft is the deletion of the temporary RDE 
       template when you change programs or go between offline and online direct.
       This prevents inadvertent attempts to access out of range or otherwise
       nonsense reference. 


                               FIXES AND CHANGES
              
       The following changes and fixes were made to Modsoft from version 
       2.33->2.4
       
       1) Modsoft 2.4 now allows more project names (xxx.env) and potentially
       more Quantum modules than can be seen in the window at the same time.
       The user must cursor to the right or left to shift the hidden part 
       of the list into view.
       
       When this condition exists, the user will see  <<  and/or >> arrows
       in the list's top border.  When the list is smaller, these arrows
       do not appear.  (It may also be noticed that the color of the list
       window title is different.)
       
       There are a maximum of 252 project names that can be included in the
       list. This limit is due to memory allocation issues.  Users must 
       be aware of this limit.  It is far better to segregate projects into
       smaller groups in sub-directories of their own and to fall far short
       of this limit.
       
       If the user exceeds 252 project names, some will be missing from the
       list. It is difficult to know which ones are missing, since the list
       is sorted before viewing.  The actual ones that will be missing are
       those that would come sequentially after the 252nd .env file in the
       programs directory in use.

       If you notice that a newly entered program is not in the .env file 
       list, and all projects list is wider than the screen, it is very 
       likely due to this limit.  Remedy,  move some project elsewhere.
       
       2) The Printers.pdb database has been modified to add new printer
       types in the selection -Special Printer Types.  The name of the 
       generic printer types and flat file types was modified.  If your 
       existing Modsoft.pdb has used these types, it will be necessary to 
       delete them from your Modsoft.pdb file using the UPF editor, and 
       re-enter them.  
       
       When you bring up a printer in the UPF editor to "setup", and see
       a yellow stripe that tells you to cancel immediately, this indicates 
       that  the printers.pdb file has changed for the printer type that was 
       selected.  It is necessary to follow directions; cancel the setup, 
       delete the printer device that has this problem, and "add" it to the 
       list again.

       3) A problem with printing extended ASCII characters from foreign key-
       boards on certain ASCII printers, e.g. Printronix P300 and P600; and on 
       flat file ASCII has been fixed. A new font has been created that is 
       attached to the flat file and the Printronix drivers.
       
       The new font does not have overstrike characters.  It is impossible 
       to print umlaut and accent characters.  Such extended ASCII characters 
       are replaced by their simple ASCII character equivalent.  For example, 
       "a umlaut" is simply "a".
       
       If you already have a printers database "Modsoft.pdb" and do not wish 
       to replace it with the distribution copy from "Update".  It may be 
       necessary to use the UPF editor to delete flat file print devices you 
       already have, and re-enter them to get the new font installed from the 
       printers.pdb file. 

       Be sure you "update" Printers.pdb file even if you don't update the 
       Modsoft.pdb.
       
       If you have printronix P300 or P600 devices in your modsoft.pdb file,
       it is necessary for you to delete them via the UPF editor and to 
       re-enter them.

       4) The purpose of the select string is to add setup information to 
       the printer immediately prior to the start of printing.   This setup 
       must be of sort that does not get "reset" by a general Reset command 
       ESC-E for example. The Printer driver from the database frequently 
       sends a RESET command after processing the selection.  Laser printers 
       are handled in this way.  An example of losing your setup occurs with 
       a duplex laser printer being driven with a simplex driver, and a 
       select string to set the duplex feature.  This will not work.