INSTALLING Hurrevac2000 ON A NETWORK - SOME TIPS AND SUGGESTIONS

Step 1. -  Install on the server as you would on other machines.  

If you misplaced the Install instructions, contact support@hurrevac.com  for a resend of install instructions..

Step 2. -  Set up file access rights.

Then give all approved users full access, usually Read, Write, Share (these terms depend on the type of network) to all files in the  Hurrevac2000 installation directory and all of its sub-directories.

Reason - there are numerous scratch files written by all instances of the program during various operations, but especially when an instance of the program is closed. Also certain data files are overwritten each time an Internet download by FTP within the program is executed.

If a user running an instance of the program on a client machine does something that requires a write of a scratch file, or downloads a file from the hurrevac.com site, the user will get an access error if he does not have rights for the program to write files or overwrite files in a particular directory.

Step 3 - If your network administrator vetoes step 2 -

If security of the program files is a big concern, and you feel you must limit access to the important files, then you may try the following:

a.  Allow writes (giving full access) to all .CFG and .DAT files in the HurWin95 or Hurrevac2000 installation directory and making all other files read-only, share...   and

b.  Some of the .stm files in the  \Hurrevac2000 \data ,  \Hurrevac2000 \dataepac ,  \Hurrevac2000 \datacpac , and  \Hurrevac2000 \datawpac ,   \Hurrevac2000 \rain , and  \Hurrevac2000 \etis  subdirectories can and will be overwritten from time to time if various client machines download files from hurrevac.com so that directory should also have full access (read, write, share).   If one person with rights to these directories is chosen to download files (see below), then only he need be given full rights in this directory.

Step 4 - Check the program on client machines for a possible .DLL and .OCX file age problem -

Depending on the age of the server versus the client machines, it is probable that at least some of the client machines will have older Windows system .dll files which may cause errors in certain routines in  Hurrevac2000.  On some of the client machines one or more of these .dll or .ocx files may be missing entirely.  If this is so, these errors will most likely occur in the File |Program Setup routine and the Utilities | Raster Graphics Viewer routines, when the Hurrevac2000 program is run from the client machine. They could occur in other routines as well.

If you wish to have the program residing only on the server,  then the dll files and .ocx files  on the offending client machine(s) must be brought up to date.  Since there are many such files, and they are often interdependent,  the best solution is simply to:

1. Install the program on the client machine.

2. Use the Uninstall (Remove Program) option in Windows  Settings |Control Panel to remove the program taking care not to remove any .dlls or .ocx files when asked.   This will bring the client machine .dlls and .ocx in line with the server.

Step 5 - Network administrator - be careful if mapping the program location -

Example - If the program is located on, for example,  a server  at location   \ Applications \ EMPrograms \Hurrevac2000 and you decide to map the location so that the client side sees it as simply  in a directory at  H: \ Hurrevac2000   ,  that should work...but if you map it simply to H:\   (without a directory),  the program may fail to respond correctly with some Common Dialog boxes, such as those which pop up when saving or retrieving (loading) some files.

Step 6 - Designate one individual to download storm data files

NOTE -  There should be only one person using FTP Download to download storm data files from the hurrevac.com site in a network environment, and such a person should be designated.    If a certain person is the only one ever downloading  storm data files from hurrevac.com with the FTP downloader,  then only that person need be given rights to the  \Hurrevac2000 subdirectories noted in step 3 above.

Bottom line...unless security is a real concern, just giving full rights, in the Hurrevac2000 directory and all of its sub-directories, on the server, to all client users approved to use the program should work.