FAQ for Genesis and VUV v4.4 for Windows NT
Updated 27 Jan 99

Hardware
--------
Q: What are the minimal recommended hardware requirements 
   for running Genesis on Windows NT?
A: Processor  - Pentium 200MHZ
   RAM        - 128MB DIMM
   Disk       - 4GB
   Video RAM  - 4MB
   Screen     - 19"
   mouse      - 3 button

Q: Will Genesis and VUV run on my laptop?
A: Yes, as long as Windows NT 4.0 is installed.

System
------
Q: What are the system requirements for running on Windows NT
A: Operating system: Windows NT 4.0
   File System:      NTFS
   TCP/IP networking must be installed -- with a network adapter

Q: What extra software do I need to get Genesis or VUV to run?
A: The only software required is Windows NT 4.0

Q: Do Genesis or VUV run on Windows 95?
A: No, they do not.   

Q: Will everything work the same on Unix and Windows NT?
A: The Graphic interface the same on Unix and Windows NT.
     The following minor differences may be noted:
     * Standard Windows NT File Selection dialogs are supported,
       since drive selection is required on Windows NT but not on Unix.
     * Unix X-Server displays usually use Pseudocolor displays (8 bit color)
       but Windows NT is often set to use Truecolor displays. (24 bit color)
       The drawing method used in the CAM Editor for Truecolor displays
       is different.
   Automation developed on Unix systems must be ported to Windows NT.
   (See "Scripts")

Q: How do I uninstall VUV?
A: The Pro-installer does not currently support an uninstall function.
   The uninstallation is currently manual.
   Here is an overview of the required steps:
   * $GENESIS_DIR/e41/nt/nc_rtsu.exe -stop_svcs
   * Delete the following directories: $GENESIS_DIR /bin and /usr
   * Delete variables prefixed with "VUV" and "GENESIS" from the environment
   * XVision may be removed from "Add/Remove Software"
   
Q: Do Genesis and VUV run on DEC Alphastations?
A: There is no support for Alphastations running Windows NT.

Q: The system tends to get bogged down after being left on for a few weeks,
   even though I close Genesis frequently.  What can I do?
A: Close your X applications and restart your X-Server.
   X-Servers are notorious sources of memory leaks.
   SCO XVision may be restarted by pressing the right mouse button 
   on the green "XV" on your taskbar, and choosing "Restart".

Q: How do I configure printing from Genesis or VUV?
A: To use Microsoft printing, your "$GENESIS_DIR/sys/hooks/lp_prog" hook
   would look something like this where "myserver" and "myprinter"
   are replaced by the server name and printer name respectively.

   # Avoid slashes in filename
      if (! $?TMPDIR) then
         set TMPDIR = $TMP
      endif
      cd $TMPDIR
         
      set file = pr.$$

   # Add ^M to end of line - required for some printers
   # sed 's/$//g' < $2 > $file 
      mv $2 $file

      @ i = 0
      while ($i < $1)
         # This command does not work in some installations
         # $WINDIR\\system32\\print /d:\\\\myserver\\myprinter $file
         echo 'print /d:\\\\myserver\\myprinter ' $TMPDIR\\$file > lp_tmp$$.bat
         lp_tmp$$.bat
         rm lp_tmp$$.bat
         @ i++
      end
      \rm $file

   Caveat: The "print" command works only with Microsoft print servers.
   
   Another alternative is to replace the "print" command with something like:
      /usr/local/bin/cat $file > lpt1

   The script creates a batch file and then runs it because for some
   reason, on some installations, c-shell refuses to run the "print" command.
      
   The command for TCP/IP printing is "lpr".  For information on installing
   TCP/IP printing see the Windows NT help, under the topic "lpr".

   The following script could be used for TCP/IP printing on Windows NT,
   where "myserver" and "myprinter" are replaced by the server name
   and printer name respectively.
   
   @ i = 0
   while ($i < $1)
      lpr -S myserver -P myprinter -d $2
      @ i++
   end

Q: I installed a new version Genesis/VUV but when I run
   the application from my shortcut, it still runs the old version.
A: The installation procedure creates a shortcut under: Start->Programs->Frontline.
   This shortcut will be updated.  Any other shortcuts made manually
   will not be updated automatically, and must be updated manually.

Q: I am having trouble with file permissions of job files.
   What can I do?   
A: There are a few methods for solving security problems in 
   Genesis under Windows NT.  Your system administrator
   will have to establish which solution is appropriate based on
   network configuration, security policy, and the problems you encounter.

   * Set the environment variable "NUT_SEC_ATTR_OFF" to "1".
     This causes the security on all files created by Genesis
     to be the default security provided by Windows NT,
     rather than the predefined Genesis security.
     i.e. the files inherit their parent's security descriptor.
     
     This method is most highly recommended.

   * Genesis relies on the Primary Group of the user for setting group
     permissions.  There are two ways to set the Primary Group:

     (a) Set the environment variable "NUT_PRIMARY_GROUP" to the group you want
         to enable permissions for the created files.

     (b) Use the Windows NT Server user manager for domains 
         to set the Primary Group of each user.

     This method will not work if operators on more than one workstation
     need to work on a single job and you are not using Windows NT Server
     user administration.
     
   * Use "cacls" to set file mode as part of the automation process.

     This solution is the most general, but it moves the onus of file
     security to the automation process.
   
   * Use the same Windows NT user for all operators.

     This solution will not work if operators on more than one workstation
     need to work on a single job and you are not using Windows NT Server
     user administration, unless the "Administrator" account is used.

Q: Why are all the colors messed up?
A: There are two modes of color operation which may be used.
   "TrueColor" and "PseudoColor".  To run in Pseudocolor, The Windows NT
   display must be set to 256 colors.  To run in TrueColor, The Windows NT
   display must be set to 16 million colors or Truecolor.

   The "Display visual" in the XVision configuration should also be set to:
   "Let XVision determine the appropriate visual class at startup".
   (The XVision implementation of Pseudocolor visuals under Truecolor Displays
    is incomplete.)
 
   Use of Pseudocolor mode is not recommended, because Genesis
   and VUV require using most of the 256 colors, and if places in the
   colormap are taken by previously running application or toolbars,
   application colors will not come out correctly.  This problem is solved
   on Unix systems by using a private colormap (by setting PCMAP to 1)
   this is not recommended on Windows NT systems because the Windows NT
   window manager does not change colormaps at the appropriate time.
   
   The PCMAP environment variable is ignored in Truecolor mode as is the
   "gui_color_no_mix" configuration parameter.  This is a limitation of
   the truecolor mode implementation. 

Networking
----------
Q: I want to run Genesis on two computers.  
   Do I need a dongle for each one?
A: No.  Only one dongle is needed per site network.
   Genesis licenses are floating licenses. e.g.
   If you have 100 Genesis licenses you can run on 150 computers
   as long as only 100 operators are logged-in simultaneously.

Q: How do I get Unix and NT to share files?
A: To mount a Unix disk on your NT, there are three options:
   (a) Run an SMB server on under Unix

       One such product is samba, which is available freely from 
       http://samba.anu.edu.au/samba/
       or from ftp://ftp.valor.com/pub/dnload/tools/samba
       Commercial products include 
       SCO's Vision FS            - http://www.sco.com/vision/products/visionfs
       AT&T's Advanced Server     - http://www.att.com/unix_asu
       Syntax's TAS               - http://www.syntax.com

   (b) Install an NFS client under Windows NT

       One such client is Hummingbird NFS Maestro, a commercial product.
       A December 1997 article in Network Computing Magazine tested 13
       NFS clients for Windows NT.  This article may be found at:
       http://www.techweb.com/se/directlink.cgi?NWC19971215S0028

   Neither one of the above solutions is clearly better than the other.
   The network administrator should choose the solution which best suits
   his/her network configuration.

   To mount an NT disk on Unix, there are two options:

   (a) Run an NFS server under Windows NT
       Hummingbird NFS Maestro Server is a commercial NFS server for Windows NT.
       The aforementioned Network Computing Magazine article also discusses
       different NFS servers for Windows NT.

   (b) Run an SMB client under Unix
       Sharity is an SMB client available for download from:
       ftp://ftp.valor.com/pub/dnload/tools/sharity/
       or from
       ftp://ftp.obdev.at/pub/Products/Sharity/binaries/
       A license from Objective Development is required for using Sharity.
       See http://www.obdev.at/Products/Sharity.html for more details.

       Caveat: Samba includes a program called "smbclient" that is not an SMB client.

   The third option is to share files on a multiprotocol file server.
   This is a hardware solution.  Information on two commercial products
   is available from:
       Auspex            - http://www.auspex.com/products/netservices/index.html
       Network Appliance - http://www.netapp.com
   
Q: How do I get Unix and NT to work with the same database and gnd?
A: You must have file-sharing between systems to use the same gnd and database.
   (See previous question for information about file-sharing.)
   
   Using the same "gnd" requires setting the environment variable "GENESIS_DIR"
   to the directory where the application has been installed.  This path
   will be different on Unix and NT systems.
   e.g. On a Unix system, GENESIS_DIR might be "/genesis" but on the
        NT system it might be "g:/genesis"
	
   [Another alternative which may be suitable in rare cases is to use
    the environment variable GENESIS_SHAREDIR.]

   To share a database, requires having the active "dblist" file
   have the value of the path of the database as its "PATH" value.
   e.g. On a Unix system, this value might be "/genesis/fw" 
        but on an NT system it might be "f:/" or
	"//sol20/fw" (a UNC path with forward slashes)

   "dblist" files may appear in one of three places:
   
   * $GENESIS_DIR/sys/dblist
   * $GENESIS_DIR/hosts/<host name>/dblist
   * $HOME/.genesis/dblist (a.k.a. ~/.genesis/dblist)
   
   A "dblist" file in "$HOME/.genesis" takes precedence over a "dblist" file in 
   "$GENESIS_DIR/hosts/<host name>" and "$GENESIS_DIR/sys".
   
   A "dblist" file in "$GENESIS_DIR/hosts/<host name>" takes precedence over a
   "dblist" file in "$GENESIS_DIR/sys".


Q: How do I set up Genesis in a mixed Unix/NT environment?
   
A: If you want to use a mixed enviroment, I have found a way that works
   best for me.

   Configure $GENESIS_EDIR on the NT to point to a local install of the
   executables.  This is a bit tricky using Pro-Installer.  You have to install
   as a server, but not install the GND process.  After every update you have
   to remember to fix the $GENESIS_DIR variable.

   Configure $GENESIS_DIR to point over a mapped drive using SAMBA.  This will
   allow scripts, joblist, etc. to be recognized.

   Configure $GENESIS_DIR/host/"system"/dblist to correct the locations of
   the databases.  Remember SAMBA will allow you to export NFS mount points.
   So the best install of a UNIX system is to cluster all your database mount
   points into one directory.  Then have SAMBA broadcast that one directory.
   This way you only need to install SAMBA on one UNIX station and broadcast.

   Configure (This is important.) $GENESIS_TMP to be local on the NT
   system.  No need to keep broadcasting this noise back and forth over the
   network.  Not to mention there is a UNIX lock issue with our log file that
   the NT "get.exe" process has trouble with at exit.

   Max Clark (maxc@valor-us.com)

Windows NT filesystem
---------------------
Q: How are Windows NT filenames different from Unix filenames?
A: There are many differences which may cause problems:
   1. Windows NT filenames are case-preserving but case-insensitive
      e.g.
         % echo hello > aaa
         % echo good-bye > AAA
         creates one file containing "good-bye"
      e.g.
         Only one of "bbb" and "BBB" will be accessible
         through NFS
   2. Under Windows NT, full paths begin with:
      (a) "X:/" where X is any uppercase or lowercase letter.
      or 
      (b) "//computer_name/share_name" -- these are known as UNC paths.
      
   3. There is no "/dev/null" file as in Unix.  The reserved name "nul"
      may be used instead.
      
   4. Filenames of the following forms are illegal:
         con
         con.*
         prn
         prn.*
         pa.*
         nul
         nul.*
         *.
 
    5. backslashes may be used as delimiters as well as forward slashes.	 
	 
    6. Filenames with spaces inside are more commonly used in Windows NT.

    7. NTFS does not support soft (symbolic) links.

Q: How are Windows NT file permissions different from Unix filenames?
A: File permissions are completely different under Windows NT.
   "chmod, ls -l, ll, etc." cannot be relied upon to give expected
   results.  The recommended tools for viewing and changing file
   permissions are "Windows NT explorer", and the command line "cacls.exe"
   
Q: How do I make a soft link (symbolic link) on Windows NT
A: You cannot.  Windows NT has three features which give a very little bit
   of the functionality of soft links.
   1. The Windows NT graphic interface supports "shortcut" files.
      These are a kind of "soft link" to other files, but these are only
      useful when using the Windows NT graphic interface.
   2. A directory may be "shared as" some name.
      e.g. If on my computer "//cpq22" I share the directory
           "/genesis/help_files" as "help"
	   then the directory will be accessible as "//cpq22/help"
	   over the network (as well as locally.)
   3. If a directory is "shared as", it may be mounted as a filesystem
      with a drive letter on any other NT system.

Q: Unix path elements are delimited with forward slashes (/) while
   Windows NT paths are delimited with backslashes (\).
   How do Genesis and VUV handle this?
A: Win32, the Windows NT API, supports both forward slashes and
   backslashes. Though the DOS shell (Command Prompt) supports only backslashes.
   A path may be entered in Genesis and VUV in either form,
   or even mixed.

Scripts
-------
Q: How will my Unix scripts run on Windows NT?
   Do I have to rewrite all my Unix scripts for Windows NT?
A: Genesis and VUV are distributed with a set of GNU tools
   which include csh, grep, cat, etc.
   Scripts will have to be modified to take into account the following:
   1. Filesystem differences (See section entitled "Windows NT filesystem")
   2. The version of "awk" in the release is named "gawk" and has a slightly
      different syntax.
   3. Process id's (accessed in c-shell using $$) are reused at an alarming
      pace by Windows NT.
   4. The GENESIS_EDIR environment variable is normally defined as a 
      full path on Windows NT but is normally a relative path on Unix. 
      (relative to /genesis or GENESIS_DIR)

Q: Why do my "sort" commands fail?
   Why do my "find" commands fail?
A: There is a "sort" and "and" command built into Windows NT.  
   It is in /winnt/system32.
   Possible solutions:
   (a) Put /usr/local/bin in your path before /winnt/system32
   (b) alias "sort" to "/usr/local/bin/sort" in startup scripts.
       alias "find" to "/usr/local/bin/find" in startup scripts.
   
Q: Where is "awk"?
A: The version of "awk" supplied is named "gawk".  It probably has a 
   slightly different syntax from the "awk" you are used to.
   
   * You may have to protect double quotes with backslashes.
   * Use "exit" at the end of your program to prevent 
        "abnormal program termination"

   As of Genesis v6.1, a version of awk released by Brian Kernighan
   is available at /bin/awk95.exe
   
Q: My GENESIS_DIR and GENESIS_EDIR values are incorrect inside scripts.
   How do I fix this?

A: One option is to use double slashes instead of single slashes in the
   definitions of GENESIS_DIR and GENESIS_EDIR (e.g. Change GENESIS_DIR
   from C:/genesis to C://genesis) under 
   Control Panel -> System -> Environment

   The other alternative, is to set the environment variable 
   NUT_ENV_LITERAL to GENESIS_DIR,GENESIS_EDIR,GENESIS_TMP i.e. a
   comma separated list of environment variables you do not want to be 
   touched. Note: This is done during the installation process starting
   in version 6.0.
   
Genesis daemons (servers)
-------------------------
Q: Where is the /etc/rc for Windows NT
A: Windows NT does not have an equivalent startup script.
   (a) Global environment variables may be set from:
       Control Panel -> System -> Environment
   (b) gnd, cns, and ems are installed as Windows NT services
       and may be controlled from:  Control Panel -> Services

Q: How do I start or stop gnd?
A: Gnd is normally run as a Windows NT service.
   When installing Genesis as a server
   "gnd" is added to the services which are run upon startup.
   It may be controlled from:
      Control Panel -> Services
      
Q: How do I run cns or ems?
A: These servers are normally run as Windows NT services.
   To install these as services, enter the following at a c-shell prompt:
      $GENESIS_EDIR/ems/ems -install
      $GENESIS_EDIR/cns/cns -install
   
Q: How do I unistall the cns, ems and gnd services?
A: To remove these services enter the following at a c-shell prompt:
      $GENESIS_EDIR/gnd/gnd -remove
      $GENESIS_EDIR/ems/ems -remove
      $GENESIS_EDIR/cns/cns -remove
    
Q: How do I run cns, ems or gnd from a c-shell prompt?
A: To run these servers as normal processes 
      $GENESIS_EDIR/gnd/gnd -debug
      $GENESIS_EDIR/ems/ems -debug
      $GENESIS_EDIR/cns/cns -debug

Q: The "gnd" server fails running from services with an "Access Denied"
   error, but starts fine when run directly [not from "services".]  
   What is the problem?
A: If the "gnd" is on a drive which is a mapped drive letter rather
   than a regular drive, it can cause this problem.  The easiest solution
   is to set GENESIS_DIR and GENESIS_EDIR to directories on normal [non-mapped]
   drives.  Another [more complicated] solution involves setting up networking
   which is not connected to user login.
   
Q: My gnd server does not come up;   
   I get, "Error 0002: The system cannot find the file specified"
   Why?
A: The path name which is registered for "gnd" is no longer valid.
   To fix, run from c-shell
      $GENESIS_EDIR/gnd/gnd -remove
   Reboot
   Run from c-shell 
      $GENESIS_EDIR/gnd/gnd -install
   Then run "Frontline gnd server" manually from Control Panel -> Services

Q: My gnd server does not come up -- I get, "Process ended unexpectedly"
   What can I do?
A: First check $GENESIS_DIR/gnd.log.  If you find messages in "gnd.log"
   that are dated at the time the process was started, they may give you
   an indication of why the process terminated.  If there are no current
   messages in "gnd.log", run from c-shell
      $GENESIS_EDIR/gnd/gnd -remove
   Reboot
   Run from c-shell 
      $GENESIS_EDIR/gnd/gnd -install
   Then run "Frontline gnd server" manually from Control Panel -> Services

Installation troubleshooting
----------------------------
Q: What can I do if the Dallas Instruments Dongle driver does not install
A: Check that the Parallel device driver is running.
      (Start -> Settings -> Control Panel -> Devices)
   If the device driver is not running, start it.  If it does not start,
   check in the "Event Viewer" why it failed.
      (Start -> Programs -> Administrative Tools -> Event Viewer)
   
Q: I entered an invalid Frontline NT registration number.  Now when I install,
   there is no request for the registration number.  What can I do?
A: Delete the following key from the Windows NT Registry:
     HKEY_LOCAL_MACHINE/SOFTWARE/Datafocus/NuTCRACKER/LicenseNumber
  (Start -> Run -> regedt32 -> OK -> HKEY_LOCAL_MACHINE -> ...)
  and rerun the stage.
  
Q: The software works if I'm logged on as Administrator, but crashes
   when I run as a different user.   What can I do?
A: The current installation program assumes that the HOMEDRIVE of the installer
   (Administrator) is the same as the HOMEDRIVE of the operator.
  
   If this is not the case, there are two ways to overcome this problem:
   (A) From the User Manager (Start -> Programs -> Administrative Tools)
       Set the Home Directory of the operator to a directory which is on
       the desired drive.
   (B) Copy the "/usr" and "/bin" directories to the top level directory
       of the operator's Home Directory.
   
   Note: This problem has been solved in Genesis v4.2

   
Standalone Troubleshooting
--------------------------
Q: I am running a computer standalone -- I do not need TCP/IP --
   but nothing is working.
A: Genesis and VUV require that TCP/IP be installed even on
   standalone computers.
   
   Make sure that TCP/IP networking is installed, and that there is a
   network adapter for TCP/IP.
   
   How to check:
     Start -> Settings -> Control Panel -> Network
     * Check that "TCP/IP" appears under the "Protocols" tab
        If TCP/IP is not installed, install it.
     * Check that there is an entry in the "Adapters" window
        If no network adapter is installed, install one.
	If the computer has no network card, install MS Loopback adapter

Q: I am running my computer standalone.
   Genesis takes a long time (about three minutes) to
   between "STARTING CONNECTION" and "ENDING CONNECTION" after logging in.
   What can I do?
A: There are two options:

  (a) The following solution is feasible if your network card is removable
      (e.g. PCMCIA)
    1. Turn off your computer
    2. Take out your network card.
    3. Turn on your computer
    On some laptop computers the PCMCIA card does not have to be removed,
    and on others, the modem card must be removed also.
    
    
  (b) The following solution is feasible for a computer which never participates
    in a network. (It requires using your Windows NT Installation CD.)
    1. Remove TCP/IP from your network protocol list
    2. Remove your network card from your network adapter list
    3. Reboot
    4. Install TCP/IP
    5. Install MS loopback adapter as your network adapter.
    6. Give 200.200.200.200 as your IP Address and Default Gateway.
       (Any legal address will do.)
    7. Reboot
   
Q: Yesterday everything worked but now "gnd" does not come up
   and neither does the Login Screen.  What can I do?
A: This phenomenon has been observed in two cases:
   1. The computer was jostled during shipping and the
      network card came loose.
   2. The computer was using an IP address obtained by a DHCP
      server when the computer was connected to the network.
      The IP address ran out because the computer could not
      contact the DHCP server to renew the IP address, and
      TCP/IP services stopped working.  To alleviate, use:
         Start -> Settings -> Control Panel -> Network ->
            Protocols -> TCP/IP Protocol -> Properties ... ->
            IP Address -> Specify an IP Address.    
      and set the IP Address to a legal IP Address.

Miscellaneous Troubleshooting
-----------------------------
Q: Whenever I drag a window, the window I drag over becomes white until
   I stop dragging.  How can I stop this?
A: Uncheck the box labeled "Show window contents while dragging" in
   Start -> Settings -> Control Panel -> Display -> Plus!

Q: When I try to login to Genesis, nothing happens for a few
   minutes and then I get an error that the application cannot connect
   to gnd.  What should I do?
A: 1. Check that the environment variable GENESIS_DIR is set correctly.
      Check that "GENESIS_DIR" points to the same directory on the server
      and the client.
      (Control Panel -> System -> Environment)
   2. Check that gnd is running on the server.
      (Control Panel -> Services)
      If not, examine $GENESIS_DIR/logs/gnd.log for explanations.
   3. Check network configuration.
      For example, A bad address in the "DNS Service Search Order"
      can cause this.
   
Q: When I use XPaint, the image looks fine, but when I put the image in
   a form, it looks awful.  What is the problem?
A: XPaint uses the default X visual to choose image depth.
   Genesis recognize only 8 bit images.  
   
   To cause XPaint to generate 8 bit images (rather than 24 bit images):
   
      Start -> Settings -> Control Panel -> Display -> Settings
      Set "Color Palette" to 256 colors
      Restart Xvision
      Run XPaint.
      Note: On some systems, the tab "Settings" is named differently
   
   When you are finished using XPaint, you will probably want to
   set the number of display colors back to 16 Million (or Truecolor.)
   
Q: Opening the Form Builder or Flow Builder from within the clipboard
   fails, but otherwise, they open fine.  What is the problem?
A: This problem has been observed when the "GENESIS_DIR" variable
   is set to "X:", where X is any letter.  Setting GENESIS_DIR to
   "X:/" solves the problem.  The source of the problem is that
   in Unix environment variables, colons are used to separate
   between paths, and a trailing colon is not identified as a
   path of a directory name by the Windows NT c-shell interpreter.
   A second alternative is to use the UNC path of GENESIS_DIR.
   
Q: The Genesis shortcuts do not appear in my menu. Why?
A: Genesis installation sets up shortcuts to Genesis.
   This works assuming the operating system is English Windows NT.
   Files are created in following subdirectory :
      Winnt\Profiles\All Users\Start Menu\Programs

   In cases where the NT version is NOT English, 
   the customer may have to move
   these shortcuts into the correct directory.

   E.g. for French users might this be:

      Winnt\Profiles\All Users\Menu démarrer\Programmes


X-Server questions
------------------
Q: I already have an X-Server installed on my computer, do I need to
   install XVision too?
A: SCO XVision is the X Server provided with the Windows NT version
   of Genesis and VUV under a special licensing agreement.
   
   There are a plethora of X-servers available on the market.  As of now,
   we have not found any that are bug-free.  You may use any X-Server you
   wish and customers have reported success with Hummingbird Exceed 
   and PC XWare.  However, Frontline's primary X-server is SCO XVision.

   There are no known problems with installing two X-Servers on one computer.
   A problem will only arise if two X-Servers are running simultaneously
   and are set to the same display number. (Usually zero)
   
Q: What can I do when I get an error message that the application cannot 
   open a display?
A: Check that Xvision is running.
   A green "XV" should appear at the bottom right of your screen.
   If it is not running:
      Start -> Programs -> Vision -> Xvision Server
    
Q: What can I do if the green "XV" appears but the application refuses
   to open a display?
A: Make sure that TCP/IP networking is installed, and that there is a
   network adapter for TCP/IP.
   How to check:
     Start -> Settings -> Control Panel -> Network
     * Check that "TCP/IP" appears under the "Protocols" tab
        If TCP/IP is not installed, install it.
     * Check that there is an entry in the "Adapters" window
        If no network adapter is installed, install one.
	If the computer has no network card, install MS Loopback adapter

Q: TCP/IP is installed.  I see the green "XV", but the application _still_
   refuses to open a display?
A: Make sure that the Vision transport "TCP-Unix" is available
   Start -> Settings -> Control Panel -> Vision Communications -> Transports
   If the status of "TCP-Unix" is "Unknown" or "Unavailable"
   Double Click on TCP-Unix -> Enable this transport -> OK -> Apply

Q: What can I do if my application comes out all black? (Genesis v4.1x only)
A: Set number of display colors to 256
   Start -> Settings -> Control Panel -> Display -> Settings
   Set "Color Palette" to 256 colors
   Restart Xvision
   Note: On some systems, the tab "Settings" may be named differently
   
Q: I would like to use my own X-Server.  What settings should I use:
A: (a) All the fonts supplied should be installed (except Oriental fonts.)
   (b) The X-Server should be configured to support Backing-Store whenever a
       window is mapped.
       In Exceed, set: tools -> configuration -> performance
                       Default backing store: [When Mapped]
   (c) When using a two button mouse, the X-Server should be configured to 
       support three button simulation.
   (d) Configured the X-Server to provide a PseudoColor colormap. (v4.1x only)
        
Q: When installing XVision, the setup program aborts stating that enough 
   disk space is not available in the target installation directory,
   even though there is plenty of space available.
A: The problem is caused by the Install Shield Wizard being unable to access
   certain data it needs in the Registry.  UHFIX.EXE solves this
   problem. It must be extracted and then the resulting executable "UHFF.EXE"
   is run.  You will get a message indicating success.  Then, attempt 
   installing XVision7 again. 

   UHFIX.EXE may be found in your $GENESIS_EDIR/nt directory.

Q: I am using a European keyboard, and my keys don't work in Genesis.  Why?
A: The Xserver uses his own keyboard setting that can be different to the
   general Windows setting.
   You can change this default setting doing the following:

	- go with your mouse to the right bottom corner of your screen
	- click with the right button on the green Xserver icon
	- select 'Properties'
	- select tap 'Devices'
	- chose the correct keyboard map
	- select 'OK' on the bottom line


Foreign Language Support
------------------------
Q: Is there support for far-eastern languages?
A: Genesis for Windows NT version 4.3 
   have support for Japanese only.

Q: What is required for Japanese support?
A: Japanese Windows NT 4.0 must be used.
   A special X-Server, distributed by our Japan distributers is required.
   Also, special care must be taken that the number format under
      Control Panel -> Regional Settings -> Number 
      has the decimal symbol defined as a point. 

Unclassified Questions
----------------------
Q: What style files do Genesis and VUV use on Windows NT?
   DOS style (CR-LF) or Unix style (LF)
A: Genesis and VUV work with both.  The c-shell has
   some problem with DOS style files.  A utility /bin/remove_cr has been
   provided to convert files from DOS to Unix.

Q: What is "launch.exe"?
A: Normally when a console process is run in a new console,
   when the process dies, the console closes.

   The role of "launch.exe" is to launch "get".  Thus if the "get" program
   ends for any reason, the console window containing the log remains open 
   rather than disappearing immediately, and the operator has an opportunity
   to read what is written in the window.

Customer Service
----------------
Q: I'm interested in upgrading or extending my VUV licence.
   Who should I contact?  I've read through this FAQ, and
   I've tried everything, but I'm still stuck.  Who can I contact?

A: North America   - 
      
   Europe          - 

   Far East        -
       
   Japan           -
       
   Israel and Rest of the world: - Frontline PCB Solutions L.P.
   
   Web Site: http://www.frontline-pcb.com   
   FTP Site: ftp://ftp.frontline-pcb.com
