Running SPITFIRE with OS/2

Source: SF-OS2.DOCEdition: searchable Web reading editionPresentation: historical wording retained

This transcription preserves the original wording, commands, examples, and text diagrams. Only DOS end-of-file markers, form-feed breaks, and repeated printed page furniture have been removed for continuous reading.

SF-OS2.DOC
                  Running SPITFIRE v3.51 with OS/2 2.x & Warp

                              SPITFIRE - Version 3.51
                    Copyright (C) by Mike Woltz, 1987-1996
                              Buffalo Creek Software

      RUNNING SPITFIRE WITH OS/2 2.x & Warp
      -------------------------------------

          These guidelines are just that - GUIDELINES.  They are meant to
      provide a starting point for setting up SPITFIRE to run under OS/2.
      The Sysop SHOULD be somewhat comfortable with OS/2 before deciding
      to run a BBS under it.

          In order to run SPITFIRE v3.5x under OS/2 2.x & Warp, Sysops need
      to create a Progam Object.  OS/2 uses these to run all applications
      from the desktop.  A Program Object tells OS/2 the name and location
      of the DOS program or BAT file being run and describes the necessary
      memory and hardware requirements.  A unique Program Object is required
      for all nodes.

          To create a Program Object, open the Templates folder and drag
      (hold down right mouse button) the Program icon out to the OS/2
      desktop.  When the Program Object is on the desktop, the settings
      notebook will open automatically.  The settings notebook has five
      tabbed pages: Program, Session, Association, Window and General.

      Recommended settings are indicated by an '*' to the left of the
      setting description.

      Program Tab
      -----------

      This notebook page is where the Sysop would define the program
      to be run, any optional parameters and the working directory.

           Path and File Name:  The Sysop should enter the full path
                                and file name used to start SPITFIRE.

                                For example:  C:\SF\SF.BAT

          Optional Parameters:  This entry should be left blank.

            Working Directory:  This should point to the SPITFIRE home
                                directory.

                                For example:  C:\SF

      Session Tab
      -----------

      This notebook page is where the Sysop defines the type of session
      that the program will be run in.  There are 6 radio buttons but
      only 2 apply to running SPITFIRE.  The Sysop should select the
      DOS session type by clicking on the appropriate radio button.

      *   DOS full screen:  This setting will look just like a regular
                            DOS machine screen.

               DOS window:  This setting will cause the screen to be
                            displayed in a window on the desktop.
                            This may cause jerky movement when the screen
                            scrolls.

      In addition, there are 2 independent check boxes on this page.

           *   Start minimized:  If checked, the program will start and an
                                 icon will be placed near the bottom of the
                                 desktop.  If not checked, then when SPITFIRE
                                 "Waiting For Call" screen will be displayed
                                 immediately.

          Close window on exit:  This box can be left blank.

      Finally, there is a button on this page called "DOS settings...".
      When the Sysop clicks on this button, a scrollable list of custom
      DOS session settings will be presented.  From this list, the Sysop
      can alter a particular set of parameters for each DOS session.  At
      the end of this document is a list of DOS Settings and some of the
      recommended settings.

      Association Tab
      ---------------

      This notebook page allows the Sysop to create a special link between
      this Program Object and one or more Data File Objects.  This page may
      be skipped and not cause any problems.

      Window Tab
      ----------

      On this notebook page, the Sysop can define what will happen if the
      Minimize button is selected.  The Sysop may also define what will
      happen when an open object is selected.

          Minimize button behavior

                             Hide window:  This radio button makes the
                                           window invisible on desktop and
                                           puts its name in the Window List.

               Minimize window to viewer:  This radio button will remove the
                                           window from the desktop and place
                                           an icon in the Minimized Window
                                           Viewer.

          *   Minimize window to desktop:  This radio button will cause the
                                           window to be removed from the
                                           screen and an icon is placed on
                                           desktop.

          Object open behavior

          *   Display existing window:  By selecting this radio button, the
                                        the Sysop can view a started program
                                        exactly as it currently appears.

                    Create new window:  If this radio button is selected,
                                        another instance of the program will
                                        be started using the same settings
                                        as any other instance.
                                        Do NOT select this button.

      General Tab
      -----------

      This notebook page allows the Sysop to assign a meaningful name to
      to the Program Object.  This name is displayed when the object is
      minimized or listed in the Window List.  The Sysop may also assign
      an icon to the Program Object or simply let it default to the icon
      for the session type.

      Hardware Requirements
      ---------------------

          Merely running OS/2 on a machine means that there is already
      a fair amount of hardware.  The minimum OS/2 configuration would
      probably be a 386DX 33/40 with at least 8MB of RAM.  The more RAM
      installed, the better OS/2 will perform.

      ANSI.SYS can be loaded in CONFIG.SYS and be made availalbe to all
      DOS sessions or it may be specified on a per session basis on the
      settings Session notebook page.

      Additional Information
      ----------------------

          It is highly recommended that the standard OS/2 COM drivers
      be replaced with Ray Gwinn's COMM drivers.

          If running a multi-node setup, it is suggested to name the
      batch files based upon their node number (SF1.BAT, SF2.BAT, etc.).

          To bring up SPITFIRE when the machine is booted, drag the
      icon for each node Program Object to the Startup Folder located in
      the OS/2 System Folder.

      DOS Settings
      ------------

      AUDIO_ADAPTER_SHARING = OPTIONAL
      COM_DIRECT_ACCESS = OFF
      COM_HOLD = OFF
      COM_RECEIVE_BUFFER_FLUSH = NONE
      COM_SELECT = ALL
      DOS_AUTOEXEC = C:\SF\AUTOFIRE.BAT
      DOS_BACKGROUND_EXECUTION = ON
      DOS_BREAK = OFF
      DOS_DEVICE = C:\OS2\MDOS\ANSI.SYS; C:\UTILCOM\BRK.DRV; C:\SIO\VX00.SYS
      DOS_FCBS = 16
      DOS_FCBS_KEEP = 8
      DOS_FILES = 55
      DOS_HIGH = LOW
      DOS_LASTDRIVE = Z
      DOS_RMSIZE = 640
      DOS_SHELL = C:\OS2\MDOS\COMMAND.COM
      DOS_STARTUP_DRIVE =
      DOS_UMB = OFF
      DOS_VERSION =
      DPMI_DOS_API = AUTO
      DPMI_MEMORY_LIMIT = 4
      DPMI_NETWORK_BUFF_SIZE = 8
      EMS_FRAME_LOCATION = AUTO
      EMS_HIGH_OS_MAP_REGION = 32
      EMS_LOW_OS_MAP_REGION = 384
      EMS_MEMORY_LIMIT = 8192
      HW_NOSOUND = OFF
      HW_ROM_TO_RAM = OFF
      HW_TIMER = OFF
      IDLE_SECONDS = 0
      IDLE_SENSITIVITY = 100
      INT_DURING_IO = OFF
      KBD_ALTHOME_BYPASS = OFF
      KBD_BUFFER_EXTEND = ON
      KBD_CTRL_BYPASS = NONE
      KBD_RATE_LOCK = OFF
      MEM_EXCLUDE_REGIONS =
      MEM_INCLUDE_REGIONS =
      MOUSE_EXCLUSIVE_ACCESS = OFF
      NETWARE_RESOURCES = NONE
      PRINT_SEPARATE_OUTPUT = ON
      PRINT_TIMEOUT = 15
      SESSION_PRIORITY = 1
   *  SIO_ALLOW_ACCESS_COM1 = OFF
   *  SIO_ALLOW_ACCESS_COM2 = ON
   *  SIO_ALLOW_ACCESS_COM3 = OFF
   *  SIO_ALLOW_ACCESS_COM4 = OFF
   *  SIO_IDLE_SENSITIVITY = 100
   *  SIO_MODE_DTR = NO CHANGE AT OPEN OR CLOSE
   *  SIO_MODE_FIFO_LOAD_COUNT = 16
   *  SIO_MODE_IDSR = IGNODE DSR DURING RECEIVE
   *  SIO_MODE_OCTS = HANDSHAKE SIGNAL, AS IN RTS/CTS
   *  SIO_MODE_ODSR = IGNORE DURING TRANSMIT
   *  SIO_MODE_RTS = HANDSHAKE, AS IN RTS/CTS
   *  SIO_MODE_XON/XOFF = NO XON/XOFF FLOW CONTROL BY SIO
   *  SIO_SCREEN_SYNC_KLUDGE = OFF
   *  SIO_SHARE_ACCESS_WITH_OS/2 = ON
   *  SIO_VIRTUALIZE_16550A = ON
   *  SIO_VIRTUALIZE_COM_PORTS = ON
      TOUCH_EXCLUSIVE_ACCESS = OFF
      VIDEO_8514A_XGA_IOTRAP = ON
      VIDEO_FASTPASTE = OFF
      VIDEO_MODE_RESTRICTION = NONE
      VIDEO_ONDEMAND_MEMORY = ON
      VIDEO_RETRACE_EMULATION = ON
      VIDEO_ROM_EMULATION = ON
      VIDEO_SWITCH_NOTIFICATION = OFF
      VIDEO_WINDOW_REFRESH = 1
      XMS_HANDLES = 32
      XMS_MEMORY_LIMIT = 2048
      XMS_MINIMUM_HMA = 0

   *  Only available if Ray Gwinn's SIO package is installed.