![]() |
![]() ![]() 626 - 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.)
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.
Make sure that the serial number printed on the HASP label matches the serial number on your registration document.
Determine which PC will run the APPX license server. 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.
Install the HASP on the APPX license server PC.
Download NetHASP device driver software.
Find the above hinstall.exe program on a floppy disk accompanying your hasp.
Install NetHASP device driver software. 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.)
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.
Note: An older document concerning installation of NetHASPs is provided here. Note that its contents are considered obsolete, but may be of interest to customers running older versions of APPX.
| |
[Append to This Answer] | |
2010-May-20 12:29am |
Previous: |
![]() |
Next: |
![]() |
|