faq

genesis 2000 v9.1软件下载

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)