Windows HASP Installation

This document is of interest to customers installing APPX on a Windows PC or in a Windows PC network environment, who wish to register their license to a hasp rather than a CPU serial number. (Customers using the APPX Client for Windows, but running APPX on a UNIX server, do not need this document because the licensing is handled by the UNIX server.)

(If you are installing a HASP on a Unix system, see this document.)

Important Note: If you are installing a HASP on Appx 5 or greater, you must set the Windows Environment Variable APPX_USE_HASP to some non blank value.

HASP Installation:

1. Verify that you have the right HASP hardware.

   The proper HASP for the Windows version of APPX is a white or red, approximately square piece of hardware with two connectors, labeled "NetHASP" or "MemoHASP". A gray one labeled "OpenHASP" is for the UNIX-based version of APPX, and should not be used.

2. Make sure that the serial number printed on the HASP label matches the serial number on your registration document.

   These should match. If they do not, call APPX Software for a replacement serial number. If APPX is run with mismatching serial numbers, it will fail the license check and generate an error message.

3. Determine which PC will run the APPX license server.

   This answers the question "Where do I put the HASP?" because the HASP hardware is always installed on the same machine on which your APPX license server runs.

   In a networked environment, it is important to carefully choose the PC on which the APPX license server will run, because the PC you select MUST be up and running Windows (and the APPX license server) any time someone might want to get into APPX.

   Normally, the APPX license server is run on a file server machine, probably the same one on which the APPX data files are located. This is because license server process must have access to the APPX data files, and it is more efficient and reliable to access the files locally (on the same machine) than over the network. Additionally, running the license server on that machine means that it should always be available whenever the APPX data files are accessible to other users.

   This strategy is appropriate when your server operating system is Windows NT or Windows 95. However, it does not apply if your file server is Novell NetWare-based, because the APPX license server is a Windows program, and Windows programs cannot run directly on a Novell NetWare file server.

   If your APPX file server is Novell-based, and you have another reliable file server PC which runs Windows NT or Windows 95 on the same LAN, consider running the APPX license server on that other PC. If your APPX file server is Novell-based, and you do not have any non-Novell file servers on the same LAN, it is necessary to identify some other PC running Windows 95 or Windows NT which will have server-like "availability" (i.e., one that's not shut off when someone goes home for the day, and doesn't get rebooted routinely during the day while people are wanting to run APPX) on which the license server can be installed.

   ** NOTE: If you have been running APPX on a temporary registration that is not restricted to a particular HASP serial number, this may be a new requirement for your site. Under the temporary registration, the license server could usually be run on any Windows PC on the LAN, since no serial number check was being performed.

4. Install the HASP on the APPX license server PC.

   Connect the HASP to the "Printer" or "Parallel" port on the back of that PC. If a printer is already connected to that port, disconnect it, attach the HASP to that port, and then connect the printer cable to the rear connector on the HASP hardware.

5. Download NetHASP device driver software.

   Use ftp or a browser to download the hasp installation file. This file should have a size of 619643. Unzip from it the file "hinstall.exe". HINSTALL.EXE should have a size of 1,027,072, and be dated April 6, 1999. If you have an earlier version of hinstall.zip, your sizes will be smaller and your dates will probably be back in 1997. If you plan to use APPX on an NT system runnnig Service Pack 3 or higher, you must upgrade to this newer hinstall.zip file. If you continue to use the old one after installing one of the more recent service packs, you may render your system unbootable!

   --- or ---

   Find the above hinstall.exe program on a floppy disk accompanying your hasp.

6. Install NetHASP device driver software.

   These instructions are for license server PCs running Windows NT and Windows 95 only. If you are installing the device driver on a Windows NT machine, you must be logged in with Administrator privileges.

   From a DOS Command window or the Start Menu's "Run" command, execute the command:

    c:\...\hinstall.exe /I 

   (Substituting the full path name to the hinstall.exe file, for "c:\...\

   The installation program will then tell you that the driver will be activated after your next reboot.

   (Note that invoking HINSTALL with the "/I" option installs the HASP driver but not the NetHASP server. You want to install only the HASP driver. You do not want to install the NetHASP server.)

7. Reboot the machine.

   To ensure that the device driver starts up properly when the machine is rebooted, test it now by rebooting and verifying that no error messages are produced. If you are running Windows NT on that machine, you should also check the Event Log to verify proper startup of the HASP device driver.

   Run APPX and get to its registration screen. If the "CPU Serial No" in the box in the upper right hand matches the serial number on your HASP, it has been properly installed, and all is well.

   If the CPU Serial number begins with a "0-", the Registration program is looking at the Serial number of your C: drive, not the HASP. It's likely the HASP driver is not properly accessing the HASP installed on your parallel port.

Comments:

Read what other users have said about this page or add your own comments.

-- ChrisBrower - 2011-06-21