          Open!EDIT v0.99h                Installation Documentation
          



          Introduction
          

          This documentation  explains how to quickly and easily get
          Open!EDIT up and running.  It  provides explicit  instruc-
          tions for installing Open!EDIT with RemoteAccess, Concord,
          QuickBBS, EzyCom,  and Synchronet BBS,  as well as generic
          instructions for other BBS systems.

          This documentation does not explain how to setup Open!EDIT
          with multinode  BBS'.  In short,  simply refer  to section
          6.1 of OEDIT.DOC (Command-Line Parameters) for information
          on how to setup for use on a multinode system.

          This  installation assumes that the main  BBS directory is
          "C:\BBS", and that Open!EDIT resides  in a directory named
          "C:\BBS\OEDIT".  If this is not correct, just change it on
          the way.



          Uncompressing Open!EDIT
          

          This section contains step-by-step unpacking instructions.
          From the DOS prompt, type:

            MD\BBS\OEDIT <enter>
            COPY OE099A.EXE C:\BBS\OEDIT <enter>
            CD\BBS\OEDIT <enter>
            OE099K <enter>
            <enter>                    (at the "Press ENTER" prompt)
            DEL OE099K.EXE <enter>
            OESETUP <enter>

          Once inside Open!EDIT Setup, Open!EDIT should be configur-
          ed as  desired.  For more  information  on  using CESetup,
          please refer to section 7.1 of OEDIT.DOC.



          Configuring BBS software
          

          After configuring Open!EDIT,  the BBS software  being used
          to run Open!EDIT must be setup to call Open!EDIT  when the
          user tries to post a message.

          Generally,  the BBS program should  be instructed  to call
          the  batch file  C:\BBS\OEDIT\OEDIT.BAT  when a user  posts a
          message.

          If a RemoteAccess, Concord, QuickBBS, EzyCom or Synchronet
          BBS system  is being used,  detailed installation instruc-
          tions have been given further on in this documentation.

          If a  BBS system  other than those  listed above  is being
          used, the following guidelines may be of assistance:

             Run your BBS' setup program and try to locate a con-
              figuration area for External Message Editors.

             In the  "execution path" or  "commandline"  section,
              type:  C:\BBS\OEDIT\CEPATH.BAT C:\BBS\OEDIT -PC:\BBS

             If your BBS program  requires a large amount of mem-
              ory, you may need to enable swapping to Disk/XMS/EMS
              in your BBS' setup.

             If your BBS has an option such as "Old style MSGTMP"
              or "QuickBBS style MSGTMP", this must be enabled.



          Configuring RemoteAccess for use with Open!EDIT
          

          This section outlines how we  at Cheepware  have installed
          Open!EDIT  with RemoteAccess.  As  far as we know, this is
          the most  effective  way to setup  Open!EDIT for use  with
          RemoteAccess.

           Unpack the  Open!EDIT archive  into a directory of  your
            choice.  We used C:\RA\OEDIT,  so this is the  directory
            we'll be  using for  our  examples.  If  yours  differs,
            adjust your setup accordingly.

           Next, run CESETUP.EXE.  Open!EDIT Setup will ask  you if
            you would like it to perform an auto-install.  Selecting
            YES will make CESETUP  automatically search for and read
            from your RA  configuration files,  and setup as many of
            Open!EDIT's features as it can without interaction.

            CESETUP can  even edit  your RA  configuration  files to
            make  Open!EDIT  your default  editor.  If you use  this
            feature,  your original  CONFIG.RA will be  backed up as
            CONFIG.TE before ANY modifications are made.

           Finish configuring Open!EDIT, then exit CESETUP.

           If you did not use the auto-install feature in Open!EDIT
            Setup, load RAConfig.

            In RAConfig under  Options | Messages | External editor,
            type the following:

            *C /C C:\RA\OEDIT\CE.BAT *M

            Then save your settings and exit.

           The CE.BAT which is included in the archive assumes that
            your BBS path is C:\RA.  If your path is  different, you
            must edit CE.BAT and enter the correct path.

           Open!EDIT should now  be loaded automatically whenever a
            user posts a message.



          Configuring Concord for use with Open!EDIT
          

          This section outlines how we  at Cheepware  have installed
          Open!EDIT with  Concord.  As  far as we know,  this is the
          most  effective  way  to  setup  Open!EDIT  for  use  with
          Concord.

           Unpack the  Open!EDIT archive  into a directory of  your
            choice.  We used C:\CONCORD\OEDIT,  so this is the  dir-
            ectory we'll be using for  our examples.  If yours  dif-
            fers, adjust your setup accordingly.

           Next,  run CESETUP.EXE and  configure Open!EDIT  to your
            preferences.  Then exit CESETUP.

           In  CSetup select  Setup | General | FS Message Editors,
            & press Alt+A to add a new editor.  Enter the following:

    Ŀ
                                                               
      Active?       : Yes                                      
      Description   : Open!EDIT                                
      Selection key : T                                        
      Command line  : C:\CONCORD\OEDIT\OEDIT.EXE -PC:\CONCORD  
                                                               
    

           The CE.BAT which is included with Open!EDIT  is not req-
            uired for use with Concord.  It may be deleted.

           Open!EDIT should now  be loaded automatically whenever a
            user posts a message.



          Configuring EzyCom for use with Open!EDIT
          

1) Create node directories under your Open!EDIT path ie: if Open!EDIT is 
installed in c:/OEDIT you will create c:\OEDIT\node1, c:/OEDIT/node2, etc
for each node you run.

2) Copy openezy.exe to your main ezycom directory ie: c:\ezy

3) copy OEDIT.bat to your main ezycom directory ie: c:\ezy

4) Edit OEDIT.bat to reflect your system:
C:						- Change drive letter
cd\ezy						- Change to ezy directory
Openezy.exe -N%1 				- Run Openezy.exe with the current node number.
cd\ezy\OEDIT					- Change to Open!EDIT dir
copy c:\ezy\msgtmp.%1 c:\ezy\OEDIT\node%1\msgtmp - Copy the temp file to the node directory in case you run a busy BBS
copy c:\ezy\node%1\door.sys c:\ezy\OEDIT\node%1  - copy the dropfile 
OEDIT.exe -N%1 -Pc:\ezy\OEDIT\node%1 -!          - Run Open!EDIT telling it where to find the files, the node your on, and suspend user's time limit
copy c:\ezy\OEDIT\node%1\msgtmp c:\ezy\msgtmp.%1 - After editing we are placing the file back where ezy wants it.
del c:\ezy\OEDIT\node%1\msgtmp			- Cleaning up.
del c:\ezy\OEDIT\node%1\msginf
del c:\ezy\OEDIT\node%1\door.sys

5)  Run oesetup.exe and configure as per the docs - Use generic BBS type for Ezy
 
6) Setup Ezycom to launch OEDIT.bat with the paramaters as per the docs.
ie: Ezycfg > Mail Areas > Misc
External Editor: c:\ezy\OEDIT.bat *N *D5 *M *!
(*N = Node number
 *D5 = Create a door.sys dropfile
 *M = Swap ezy out of memory
 *! = Suspend user's time while in Open!EDIT
)
Old Style MSGTmp: No




          Configuring Synchronet for use with Open!EDIT
          

          This section outlines one way Open!EDIT has  been success-
          fully installed with Synchronet.  It may or may not be the
          best way, but it does work.

          Thanks  to   Chris   Chastain  (formerly   1:3636/16)  for
          providing these sample instructions.

          Here's the information Chris sent us:

           Unpack the  Open!EDIT archive  into a directory of  your
            choice.  We used C:\SBBS\EXEC\OEDIT, so this is the dir-
            ectory  we'll be using for our  examples.  If yours dif-
            fers, adjust your setup accordingly.

           Next,  run CESETUP.EXE and  configure Open!EDIT  to your
            preferences.  Then exit CESETUP.

           In Synchronet  Config under External Programs | External
            Editors, insert a new item.  Chris used "EDIT",  so that
            is the name we'll be using.  Enter the following:

    ͻ
                              Open!EDIT Editor                         
    ͹
     Name                            Open!EDIT                        
     Internal Code                   OEDIT                            
     Local Command Line              %!OEDIT\OEDIT -P%N -N%#          
     Remote Command Line             %!OEDIT\OEDIT -P%N -N%#          
     Access Requirements             --------                         
     Intercept I/O Interrupts        No                               
     QuickBBS Style (MSGTMP)         Yes                              
     Expand Line Feeds to CRLF       No                               
     BBS Drop File Type              RBBS/QuickBBS   DORINFO#.DEF     
    ͼ

            %!   expands to your exec directory  (in Chris' case, it
                 was  C:\SBBS\EXEC\).  MAKE  SURE  that you  specify
                 YOUR OWN path if it differs from the one he used.
            -P   is Open!EDIT's path parameter and the %N expands to
                 your NODE directories (in Chris' case C:\SBBS\NODE1
                 or C:\SBBS\NODE).
            -N%# specifies which node the user is on

           Last but not  least, put OEDIT in your  GLOBAL SWAP LIST
            if you lack the memory to run it without swaping the BBS
            out.  Chris says he didn't need to swap,  and that OEDIT
            loads faster without swapping.  When  upading the GLOBAL
            SWAP LIST, just put in OEDIT, not OEDIT.EXE.

           The CE.BAT which is included  with Open!EDIT is not req-
            uired for use with Synchronet.  It may be deleted.

           Open!EDIT should now  be loaded automatically whenever a
            user posts a message.

          

          End of INSTALL.TXT
          
