
               QNX Windows - Installation & Configuration


                            Copyright Notice
                                    
   
    QNX Software Systems Ltd.
    175 Terence Matthews Crescent
    Kanata, Ontario
    K2M 1W8
    Canada
    Voice: 613-591-0931
    Fax: 613-591-3579
    Email: info@qnx.com
    Web: http://www.qnx.com/
    
    (c) QNX Software Systems Ltd. 1997
        All rights reserved.
          
   No part of this publication may be reproduced, stored in a retrieval
   system, or transmitted in any form or by any means, electronic,
   mechanical, photocopying, recording, or otherwise without the prior
   written permission of QNX Software Systems Ltd.
   
   Although every precaution has been taken in the preparation of this
   book, we assume no responsibility for any errors or omissions, nor do
   we assume liability for damages resulting from the use of the
   information contained in this book.
   
   Publishing history
   May 1993 First edition
   August 1997 Second edition
   
   QNX is a registered trademark of QNX Software Systems Ltd.
   
   All other trademarks and registered trademarks belong to their
   respective owners.
   
   Printed in Canada.
   
   Part Number: 001429


                         Table of Contents

   About This Guide
   Installing QNX Windows
     System requirements
     What you were shipped
     Installation procedure
       Step 1
       Step 2
       Step 3
     Starting QNX Windows
     Exiting QNX Windows
       Shutting down QNX Windows
       Returning to text mode
         Shutting down
   Configuring QNX Windows
     Choosing an alternate graphics driver
       VGA & SVGA
       S3 graphics cards
       ATI Accelerator Series
       VESA2 graphics cards
       Testing the graphics driver
       Starting the driver automatically
     Setting up a graphics screen larger than your physical screen
       Virtual-mode options
       Examples
     Selecting custom graphics modes
       Available keys
       Basic operation
     Setting up Wterm windows
       Running many Wterm windows
       Modifying WTERMARGS
       Dev.win options
     Setting up a pointing device
       Mice
       Touchscreens
         Calibrating the touchscreen
     Other configuration options
   Where Files Are Kept
     QNX Windows files
     Application files
     Configuration files
     Readme files

   
                               About This Guide
                                       
   This Installation & Configuration guide accompanies the QNX Windows
   software and is intended primarily for system administrators and QNX
   Windows developers. It contains the information you'll need to install
   and configure a QNX Windows system.
   
   The following table may help you find information quickly:
   
   When you want to:                              Go to this chapter:
   -----------------------------------------------------------------------
   Check your system requirements                 Installing QNX Windows
   Review startup or shutdown procedures          Installing QNX Windows
   Set up graphics drivers, modes, touchscreens   Configuring QNX Windows
   Locate configuration files                     Where Files Are Kept



                            Installing QNX Windows
                                       
                              System requirements
                                       
   Before you can install QNX Windows, your system must meet the
   following minimum requirements:
   
     * QNX Operating System version 4.22 or later
     * 7M of unused disk space
     * 4M of memory
     * VGA-compatible, ATI Accelerator Series (i.e. Mach-8, Mach-32, and
       ISA-based Mach-64), most S3 (except S3 ViRGE), or VESA2-compliant
       display adapter
       
   We recommend that you also have a pointing device (e.g. mouse,
   touchscreen).
   
                             What you were shipped
                                       
   Your QNX Windows runtime package should contain the following:
   
     * Runtime System diskettes
     * QNX Windows Installation & Configuration
     * QNX Windows User's Guide
       
   On the back of the diskettes you'll find a serial number that lets you
   access the QNX online conferencing system (QUICS) to update your
   software as features are added. If you'd like to read online
   discussions about QNX Windows, you should join the
   quics.experts.qwindows newsgroup on QUICS. With the appropriate
   service plan, you can also post technical questions to the newsgroup.
   For information on using QUICS, see the QNX Operating System
   Installation & Configuration manual.
  
 
                            Installation procedure
     _________________________________________________________________
   
   Note: We assume that QNX 4 is already installed and running on your
   machine. If not, you should refer to the installation docs that came
   with your QNX OS disks.
     _________________________________________________________________
   
   The basic installation of QNX Windows consists of these main steps:
   
     * Copying the distribution files from the floppy disks to your hard
       disk.
     * Installing a pointing device driver.
     * Testing the pointing device driver.
       
   These steps are the same for all installations. Step 2, installing a
   pointing device driver, requires that you select the appropriate
   command to match your specific hardware.
   
   You'll want to add the command for Step 2 to your sysinit.node file so
   that your specific setup will remain in effect each time you boot your
   computer. For information on sysinit files, see the QNX Operating
   System Installation & Configuration manual.
     _________________________________________________________________
   
   Note: Before you install QNX Windows, you must be logged in as the
   superuser (root) and the floppy driver must be running. To check if
   the driver is running, type:

           sin ver

   If "Floppy" doesn't appear in the NAME column, type:
   
           Fsys.floppy

   We also recommend that you perform the installation procedure at the
   boot server.
     _________________________________________________________________
   
   Step 1

   Copy the QNX Windows files onto your hard disk.
   
   Insert the QNX Windows runtime install disk #1 and type:
   
           /etc/install [drive]

   where drive is the name of the floppy you're using (default is
   /dev/fd0). Then follow the instructions on your screen.
   
   The /etc/install script automatically transfers one QNX Windows
   license to the /etc/licenses directory. If you have QNX Windows
   network expansion diskettes, refer to the note "Adding Licenses to a
   QNX 4 Network" shipped with your expansion diskettes.
   
   Step 2

   Install a pointing device driver.
   
   Although a pointing device isn't absolutely required, we recommend
   that you install one to take full advantage of QNX Windows. You may
   skip this step if you've already installed a pointing device in your
   QNX 4 system.
   
   To install the:         See the:
   ------------------------------------------------------------------------
   mouse driver          section in this guide on "Setting up a pointing
                         device" as well as the Mouse utility in the QNX 4
                         Utilities Reference
   touchscreen driver    section in this guide on "Setting up a pointing
                         device" as well as the Input usage message on your 
                         system

     _________________________________________________________________
   
   Note: You should add the commands for installing a pointing device
   driver to your sysinit.node file so that your setup will remain in
   effect each time you boot your computer.
     _________________________________________________________________
   
   Step 3

   Test the pointing device driver.
   
   Once the pointing device driver has been installed, you should verify
   that it's properly configured:
   
   To test a:              Type:
   -----------------------------------
   mouse driver            Mouse test
   touchscreen driver      Touch test
   
   For more info, see the Mouse utility and the section in this guide on
   "Setting up a pointing device."
   
                             Starting QNX Windows
                                       
   To start QNX Windows, type:
   
           windows

   For info on using QNX Windows, see the QNX Windows User's Guide.
     _________________________________________________________________
   
   Note: To run QNX Windows, you'll need one virtual console to launch
   QNX Windows from and an extra, unused virtual console that will be
   used exclusively by QNX Windows. If QNX Windows won't start and prints
   a message stating that there's no console free, try logging off from
   one of your extra consoles. For more information, see Dev.con and
   tinit in the QNX 4 Utilities Reference.
     _________________________________________________________________

   
                              Exiting QNX Windows
                                       
   Shutting down QNX Windows

   To exit from QNX Windows and shut down the QNX Windows server, bring
   up the Workspace Menu (see the User's Guide) and choose the Exit item.
   
   Returning to text mode

   To exit from QNX Windows and return to text mode without shutting down
   the QNX Windows server, you should either:
   
     * click SELECT on the Workspace text button in the upper-left corner
       of the QNX Windows workspace
       OR
     * press Ctrl-PrtSc
       
   To resume your QNX Windows session, type:
   
           windows

   Shutting down
  
   To shut down the QNX Windows server while in text mode, type:
   
           windows -q


                            Configuring QNX Windows
                                       
                     Choosing an alternate graphics driver
                                       
   If you have a graphics card with capabilities greater than that of a
   standard VGA card, you may choose to configure your system to take
   advantage of those capabilities. This section describes how.
     _________________________________________________________________
   
   Note: Some graphics cards need to be configured; consult the
   installation instructions that came with your card. If your card
   includes a mouse port, this also may need to be configured.
     _________________________________________________________________
   
   At the time of printing, QNX Windows for QNX 4 supports these graphics
   cards:
   
     * VGA 640x480
     * SuperVGA 800x600
     * ATI Mach-8, Mach-32, and ISA-based Mach-64
     * most S3 (except S3 ViRGE)
     * VESA2-compliant cards that support linear frame buffer.
       
   This list of supported graphics adapters was compiled at the time of
   printing. For a current list of supported graphics adapters see the
   windows/readme/video_adapters file.
   
   VGA & SVGA

   To install the graphics driver for a VGA 640x480 16-color card
   (standard VGA), use this command:
   
           /windows/bin/gr.vga &

   To install the graphics driver for a VGA 800x600 16-color card, use
   this command:
   
           /windows/bin/gr.vga [svpmi_script_file[.pmi]] &

   where svpmi_script_file[.pmi] is one of the following:
   
   To use this card:                           Specify this script:
   ---------------------------------------------------------------------
   ATI Graphics Ultra (in VGA mode)            atiultra
   ATI XL                                      atixl (the letter "el")
   AAMAZING Technologies 560 VGA               avga2
   Tseng Labs ET4000 (e.g. Cardinal VGA732)    et4000
   Paradise 8- and 16-bit VGA cards            pvga1 (the number "one")
   Trident 8900-based VGA cards                tri8900
   Video 7 FASTWRITE                           v7ht205
   Video 7 VRAM II                             v7ht209
   Standard S3 enhanced mode                   S3enhanced
   Standard VGA adaptor*                       vga
   
   
          * Note that the vga.pmi script is executed by default for the
            VGA 640x480 16-color card and the S3 640x480 16-color card.
          
   This list of supported VGA cards was compiled at the time of printing.
   For a current list of script files, type:
   
           ls /usr/lib/svpmi

   The readme file in this directory shows you which script file to use
   for your video card.
   
   S3 graphics cards

   To install the graphics driver for an S3 640x480 16-color card, use
   this command:
   
           /windows/bin/gr.s3 &

   Note that the S3 driver can also be installed using the previously
   mentioned [svpmi_script_file[.pmi]] scripts:
   
           /windows/bin/gr.s3 [svpmi_script_file[.pmi]] &

   See the gr.s3 usage message for available options.
   
   ATI Accelerator Series

   The drivers for the ATI Accelerator Series cards are:
   
     * gr.mach (for Mach-8 and Mach-32)
     * gr.m64 (for ISA-based Mach-64, 256-color).
       
   To install the driver for a 1024x768 256-color Mach-8 or Mach-32 card,
   use this command:
   
           /windows/bin/gr.mach &

   To install the driver for a 640x480 256-color Mach-8 or Mach-32 card,
   use this command:
   
           /windows/bin/gr.mach -g640x480 &
     _________________________________________________________________
   
   Note: To support other graphics modes (e.g. 800x600, 1280x1024) for
   Mach-8 or Mach-32 cards, see the section on "Selecting custom graphics
   modes" in this chapter.
     _________________________________________________________________
   
   To install the driver for a 1280x1024 256-color ISA-based Mach-64
   card, use this command:
   
           /windows/bin/gr.m64 &

   To install the driver for a 256-color ISA-based Mach-64 card in
   graphics modes other than 1280x1024, use this command:

           /windows/bin/gr.m64 -g XxY &

   where the desired graphics mode is X by Y.
   
   See the gr.mach and gr.m64 usage messages for available options.
   
   VESA2 graphics cards

   To install the driver for a 640x480 256-color VESA2-compliant graphics
   card that supports linear frame buffer, use this command:
   
           /windows/bin/gr.vesa2 &

   To install the driver for a 800x600 256-color VESA2-compliant graphics
   card that supports linear frame buffer, use this command:
   
           /windows/bin/gr.vesa2 -g 800x600 &

   See the gr.vesa2 usage message for available options.
   
   Testing the graphics driver

   Once the graphics driver has been installed, you should verify that
   it's properly configured for your display adapter by typing:
   
           /windows/bin/gr.test

   To exit from this test utility, simply press any key.
   
   Starting the driver automatically

   Once you've tested the graphics driver, you can have QNX Windows start
   it automatically by setting the WINGRAFX environment variable:
   
           export "WINGRAFX=gr.mach"
     _________________________________________________________________
   
   Note: Remember to reboot your machine if you add this command to your
   sysinit.node file.
     _________________________________________________________________
   
         Setting up a graphics screen larger than your physical screen
                                       
   With its virtual mode, QNX Windows can use a graphics screen larger
   than your physical screen. To pan across the larger virtual screen,
   the user simply moves the pointer to the edge of the physical screen.
   
   Virtual-mode options

   -b default|none|n
          Set a panning border for the physical screen. The user can pan
          the virtual screen by moving the mouse pointer into the border.
          If you choose default, the width of the border is equal to 1/8
          the width of the physical screen. If you give a value n, the
          width of the border is equal to 1/n the screen width. If you
          choose none, the virtual screen will pan only when the pointer
          touches the very edge of the physical screen.
          
   -c
          Continuously pan the virtual screen. Moving the pointer at any
          time will pan the screen.
          
   -v default|XxY
          Set the size of the virtual screen. If you specify default, the
          size is 800x600 for gr.vga and 1024x768 for gr.mach. If you
          specify XxY, the size is X pixels wide by Y pixels high.
          
   Examples

   Start the gr.mach driver with a physical resolution of 640x480 and a
   virtual resolution of 1024x768:
   
           gr.mach -g 640x480 -v default &

   Start the gr.vga driver with a physical resolution of 800x600 and a
   virtual resolution of 832x620 in continuous pan mode:
   
           gr.vga -v 832x620 -c pvga1 &
     _________________________________________________________________
   
   Note: As the above example illustrates, virtual options must precede
   the graphics script if one is specified (in this case, pvga1).
     _________________________________________________________________
   
   Start the gr.mach driver with a physical resolution of 640x480 and a
   virtual resolution of 800x600 without a panning border:
   
           gr.mach -g 640x480 -v 800x600 -b none &

   Alternately, the panning border could be half of the screen; this
   would cause the driver to try to keep the mouse pointer centered:
   
           gr.mach -g 640x480 -v 800x600 -b 2 &
     _________________________________________________________________
   
   Note: If the virtual resolution you specify is larger than available
   video memory, the driver will automatically reduce the virtual screen
   size to fit and print a message that indicates the reduced size.
   
   Note also that QNX Windows' virtual mode won't work with all the
   graphics drivers. At the time of printing, virtual mode will work only
   with the graphics drivers for these cards:
   
     * VGA 640x480
     * SuperVGA 800x600
     * ATI Mach-8, Mach-32
     * S3.
     _________________________________________________________________

   
                        Selecting custom graphics modes
                                       
   With the setup.mach utility, you can select custom graphics modes for
   Mach-8 and Mach-32 ATI Accelerator Series cards. You need to use
   setup.mach if you wish to use a graphics mode other than 1024x768 or
   640x480 with these cards.
   
   If you have a Mach-8 card, setup.mach will let you create an 800x600
   256-color mode. If you have a Mach-32 card, setup.mach will also let
   you create a 1280x1024 256-color mode.
   
   To run this utility type:
   
           /windows/bin/setup.mach
     _________________________________________________________________
   
   Caution: If used incorrectly, this utility can permanently damage your
   monitor! Consult your monitor's manual for correct frequency
   selections. If setup.mach is running in graphics mode, and your
   monitor does any of the following:
     * goes blank
     * makes a high-pitched whistling noise
     * produces a very small or unintelligible display
       
   press the Tab key immediately to return to text mode.
     _________________________________________________________________
   
   Available keys

   In setup.mach, the following keys are always available:
   
   In order to:                                   Press:
   --------------------------------------------------------------------
   toggle between graphics mode and text mode     Tab
   switch from graphics mode to text mode         Ctrl-Tab or Shift-Tab
   switch to text mode and go to the main menu    Alt-Enter
   get help for current menu                      F1
   
   While in a setup.mach menu, you can use these keys:
   
   In order to:                Press:
   -----------------------------------
   move up one item            /\
   move down one item          \/
   select the current item     Enter
   exit the menu               Esc
   
   Basic operation

    1. When you start setup.mach, you'll see its main menu. From this
       menu, choose the Resolution Select item, which brings up a menu
       that lets you choose a resolution.
       Choose the resolution you want to add to your available modes and
       press Enter.
    2. Another menu will pop up and show the available submodes; when you
       highlight any mode, a window to the right provides detailed
       information about that mode.
       Once you've found the mode that most closely matches your
       monitor's abilities, press Enter to move the mode to the list of
       selected modes.
    3. Press Enter to access the Customize Mode window, which lets you
       position and size the mode. Once you're done customizing the mode,
       press Enter.
    4. To return to the main menu, press Alt-Enter (or press Esc until
       the main menu appears). Choose Write mode file to save your
       changes, and choose Exit to end your session.
    5. Once a mode has been created and saved, the driver must be
       restarted to use the new mode. For example, if you created an
       800x600 mode, you could start the driver with this command:

           gr.mach -g 800x600 &


                           Setting up Wterm windows
                                       
   The Wterm program lets you run QNX utilities and text-based
   applications in a window on the QNX Windows workspace.
   
   Wterm windows are devices that are managed by the Dev.win driver. When
   a QNX Windows user starts up an application that runs in a Wterm
   window, the shell script /windows/bin/wterm automatically launches the
   application on a Dev.win device.
   
   With the release of QNX 4.23, QNX defaults to 32-bit executables for
   all the OS components. Dev.win, however, continues to be 16-bit and
   requires a 16-bit Dev (i.e. Dev16). If you're running QNX 4.23 or
   later, you'll want to add to your sysinit.node file the following
   commands, which will start Dev16 and allow Dev.win to talk to it:
   
           /bin/Dev16 -N /D16 &
           /windows/apps/Wterm/Dev.win -N /D16/win -r &

   For more information on using Dev.win and Dev16 in QNX 4.23 or later,
   see the /windows/readme/Dev.win file.
     _________________________________________________________________
   
   Note: Remember to reboot your machine if you add these commands to
   your sysinit.node file.
     _________________________________________________________________
   
   Running many Wterm windows

   If you wish to run many Wterm windows concurrently, you may need to
   increase configuration limits specified to Dev, or Dev16 if you're
   running QNX 4.23 or later, in any appropriate build files to allow for
   a larger number of devices.
     _________________________________________________________________
   
   Note: Before changing any build file, read the chapter on "Building an
   OS Image" in the QNX 4 Installation & Configuration manual.
     _________________________________________________________________
   
   For example, if you specify:
   
           Dev or Dev16 [any_other_options] -n 100

   Dev/Dev16 will support 100 terminal devices (virtual consoles, serial
   terminals, and Wterm windows). For more information, see Dev in the
   QNX 4 Utilities Reference and Dev16 in the /windows/readme/Dev.win
   file.
   
   Modifying WTERMARGS
  
   If you want to use more Wterm windows than Dev.win allows by default
   (6), you should modify the WTERMARGS environment variable before you
   start QNX Windows. For example, this command:
   
           export WTERMARGS=-n16

   allows up to 16 Wterm windows.
     _________________________________________________________________
   
   Note: Remember to reboot your machine if you add this command to your
   sysinit.node file.
     _________________________________________________________________
   
   For information on using Wterm, see the QNX Windows User's Guide. For
   additional information on controlling how Wterm behaves, see the
   /windows/readme/wterm file.
   
   Dev.win options
     _________________________________________________________________
   
   Note: In most cases, you should specify these options in the WTERMARGS
   environment variable.
   
   Wterm uses several files to display its menus and dialog windows. To
   have Wterm display in a language other than English, you can copy
   these files, translate them, and then tell Wterm where to find the
   translated files with the options -h, -m, -p, and -t.
     _________________________________________________________________
   
   Dev.win [options] &

   -C number
          The size of the canonical input buffer (default is 256).
          
   -F
          Wterm windows are Force Front.
          
   -I number
          The size of the raw input buffer (default is 1024).
          
   -N name
          The prefix to register (default is win).
          
   -O number
          The size of the raw output buffer (default is 2048).
          
   -R
          Don't allows resize of Wterm windows.
          
   -S server
          The name of the server to connect with.
          
   -b
          Put up borderless Wterm windows.
          
   -h directory
          The directory for the help files used by Wterm (default is
          /windows/apps/Wterm).
          
   -m file
          The dialog file for the Wterm menu (default is
          /windows/apps/Wterm/wterm.dial).
          
   -n number
          The maximum number of Wterm windows allowed. The default is 6,
          4, 2, or 1, depending on the number of devices available.
          
   -p directory
          The directory for the .pict files used by Wterm (default is
          /windows/apps/Wterm).
          
   -r
          Stay resident after QNX Windows terminates.
          
   -s number
          The key code for switching sequentially between Wterm windows.
          The default, 0xFFAD, is PrtSc.
          
   -t file
          The text file that contains all text not found in wterm.dial or
          in the .pict files (e.g. error messages). The default is
          /windows/apps/Wterm/wterm.text.
          
   -u number
          The keycode to release input focus (no default).
          
   -w
          No window button or window menu for Wterm windows.
  
        
                         Setting up a pointing device
                                       
   QNX Windows 4.23 relies on the Input resource manager to talk to
   pointing devices. Input works with the device-specific logical
   resource managers Mouse and Touch to handle mice and touchscreens.
   
   Mice

   The simplest way to configure the input subsystem for use with a mouse
   is to type:
   
           mousetrap start

   The mousetrap (inputtrap) utility will start the Mouse manager, and
   then query the system to determine the type of mouse connected. If the
   mouse can be recognized by mousetrap, then Input will automatically
   start with the correct command line in order to connect to Mouse and
   drive the detected hardware.
   
   Sometimes mousetrap (inputtrap), can't detect the mouse installed on
   your system. In this case, you must start Input manually, specifying
   the correct command-line arguments for the mouse in question.
   
   If you've just finished running mousetrap start, then Mouse will
   already be running - you simply need to issue the following command at
   the shell prompt (assuming an MS mouse on serial 1):
   
           $ Input -d/dev/mousein msoft fd -d/dev/ser1 &
     _________________________________________________________________
   
   Note: If you haven't previously run mousetrap start, then you should
   start Mouse before starting Input.
     _________________________________________________________________
   
   For a complete list of mice supported, see the Input usage message.
   
   Once Mouse and Input are running, you can verify that the system is
   correctly configured by typing:
   
           Mouse test

   and moving the mouse.
   
   Touchscreens

   When using a touchscreen, you don't have the convenience of using
   inputtrap to automatically detect the device, since (as of this date)
   there's no good general-purpose method for detecting touchscreens.
   
   Since you can't use inputtrap, you'll have to start Touch manually:
   
           $ Touch &

   Then you must start Input with the appropriate command-line options
   for the particular device. For example, here's the command for an
   Elographics smartset protocol touchscreen on ser1:
   
           $ Input -d/dev/touchin smartset fd -d/dev/ser1 &

   For a complete list of touchscreens supported, see the Input usage
   message.
   
   Once Touch and Input are running, you can verify that the system is
   correctly configured by typing:
   
           Touch test

   and touching the screen. To exit test mode, press Ctrl-C.
   
   Calibrating the touchscreen
  
   Before it can be used with QNX Windows, the touchscreen must be
   calibrated. With the graphics driver installed, type the command:
   
           TCalib

   If a touchscreen has never been calibrated on your node, you'll
   automatically enter calibrate mode. If TCalib doesn't start in
   calibrate mode, press C.
   
   In calibrate mode, you'll be asked to point twice to a red cross hair
   in the upper-left corner. The program will pause briefly and then ask
   you to touch another red cross hair in the lower-right corner.
     _________________________________________________________________
   
   Note: While calibrating the touchscreen, try to look at the display
   from the same viewpoint as the operator; this will help avoid a
   parallax effect. Parallax is sometimes a problem with touchscreens
   since the surface that you touch can be some distance in front of the
   surface of the actual monitor.
     _________________________________________________________________
   
   Once the touchscreen is calibrated, you'll see the main menu for
   TCalib. This menu consists of a series of buttons across the top of
   the screen; the rest of the screen is gray. If you touch the screen in
   the gray area, a yellow cross hair should appear under your finger. If
   the cross hair doesn't appear under your finger, you should
   recalibrate the touchscreen by pressing C.
   
   The main menu includes these "touchable" buttons:
   
   In order to:                      Touch:          Or press:
   --------------------------------------------------------------
   exit                              TCalib          Exit Esc
   recalibrate                       Calib           C
   erase the yellow cross hairs      Clear           n/a
   try a touchscreen typewriter      TypeWriter      n/a
   try a simple paint program        Fun             n/a

     _________________________________________________________________
   
   Note: For more information on configuring pointing devices, see the
   /etc/readme/technotes/input_system.doc file.
     _________________________________________________________________

   
                          Other configuration options
                                       
   For information on other options that let you control how QNX Windows
   looks and behaves, see the chapter on Customizing QNX Windows in the
   QNX Windows User's Guide and the chapter on Configuration in the QNX
   Windows Programmer's Reference. You should also look at the files in
   the /windows/readme directory (see "Readme files" at the end of this
   guide).
   
   For information on printing files from QNX Windows see the
   /windows/readme/config_OL file.

   
                             Where Files Are Kept
                                       
                               QNX Windows files
                                       
   QNX Windows files are located in the /usr/lib/windows directory. For
   your convenience, there's a symbolic link from /windows to
   /usr/lib/windows; QNX Windows documentation refers to /usr/lib/windows
   as /windows.
   
                               Application files
                                       
   All QNX Windows application programs are located under the
   /windows/apps directory. If you're developing an application that will
   consist of multiple files, we suggest that you create a subdirectory
   within /windows/apps where all of these files may be kept, including
   the load module. For example, the OPEN LOOK File Manager's files are
   located in the /windows/apps/Olfm directory. The exception to this
   rule is when an application consists of only a load module and a
   single picture file. In this case, these files may reside directly
   under /windows/apps.
   
   The effect of this approach is to closely associate applications with
   their related files, without over-populating the /windows/apps
   directory.
   
                              Configuration files
                                       
   Application programs often need to create and use files that contain
   configuration information. Whether you're a developer or a system
   administrator, you should be aware of the guidelines regarding the
   management of these files.
   
   We recommend two levels of configuration files:
   
     * configuration files that can affect all users
     * personal configuration files that affect an individual user
       
   Configuration files that affect all users are located with the rest of
   the application's files in a subdirectory in /windows/apps. We
   recommend that the name of this subdirectory begin with a capital
   letter. Personal configuration files that affect an individual user
   are located in a windows subdirectory in that user's home directory.
   
   For example, the File Manager would search the following directories
   in this order when looking for configuration files:
   
           /windows/apps/Olfm
           $HOME/windows

   where $HOME is expanded by the Shell to the user's home directory.
   
   Note that it's up to the application to decide which location to
   search first. Also, the application decides whether the system and
   user configuration files should combine, merge, or replace each other.
   Each application's documentation should clearly state the expected
   behavior.
   
   If you're a developer, it's good practice to give your programs names
   that differ from those in the standard /bin or /usr/bin directories.
   This minimizes the potential for confusion.

   
                                 Readme files
                                       
   As a QNX Windows user, there are many optional configuration
   parameters you'll want to take advantage of. These options tend to
   evolve over time as new features are added. To keep you abreast of
   these enhancements, we've established a "readme" directory:
   
   /windows/readme
   
   Most of the files in this directory contain notices for various
   programs, informing you of any changes that might affect your QNX
   Windows installation. The installation file contains an online version
   of this installation guide.


                           - END -
