faq

genesis 2000 v9.1软件下载

   "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 ([e-mail])

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
--------------------------