1. RAP.EXE must be installed on, or available to the Station with the HASP device physically connected to LPT1.
  2. From DOS – Type ‘RAP’
  3. Select the first menu item: ‘Generate Request Codes’. This will display 8 – 3 digit codes that are unique to that HASP device. Write these down.
  4. Phone,Fax or EMail via BBS Touch Menus Sales department with your request for program authorization. Include:
        1. Request codes obtained from step #3
        2. List of programs to be authorized and the number of concurent uses for each.
  5. Upon aproval from TMI Sales, Authorization codes will be generated using the codes you submit. These will be given to you via
        1. Verbal
        2. FAX
        3. E-Mailed in a .BIN file – depending upon your request.
  6. Once again, run the RAP.EXE utility.
  7. Select the menu item: ‘Enter Authorization Codes’. Be sure that the same HASP device that was used in steps #1-3 is attached. At this time you can enter by hand the codes, or enter the name of the .BIN file  containing the codes.
  8. The HASP will now contain the requested authorizations.

Virtual Hasp (VHasp)

In some stand alone applications, it is neccesary to use a VHasp instead of a Hasp. The Hasp requires a parallel port, and some stand alone systems do not have an adequate port. For this reason, the VHasp was designed.

To use the VHasp, a system must have:

  1. a Valid C: Hard disk,
  2. DOS 6.22 Operating System. The Windows 95 Version of DOS (7.00 or greater) will not work.

To install a VHasp on a system, Rap v1.2+ must be run on the system with the command line “/InitVHasp” once. This will initialize the VHasp and make it ready for programming.

Whenever RAP is run on a VHASP system, it will first check for a regular Hasp. If one is not found it will next look for a VHasp. If this is what is found, a “-v-” (without the quotes) will appear in the upper right hand corner of the screen.

When RAP is run with a VHasp, the following items will behave differently:

  1. Request HaspID: Will return the VHasp ID with a “V” prefix.
  2. View Current Authorizations: Read only. Requires Auth codes to program. Displays VHasp instead of node number for each program Authorized.
  3. Authcode list will be shorter.

TMAP Version 2.00 is required for the core products to recognize the VHasp. The debug mode has also been improved. It will display the TMAP Version number, and the reason you are seeing this screen (Scroll lock Key) for those who don’t understand why it is showing up. And it also lists any attempts and results in finding the VHasp footprint.
Program ID Numbers
ID Program
1 Editnet(V4)
2 Manager(V4)
3 TouchNet(V4)
4 Street Database
5 Food Cost
6 Marketing Module
7 Delivery Report Modules
8 Taco Manager
9 Pizza Manager
10 Basic Inventory/QSR
11 Bread Manager
12 Blimpies Redbook
13 Jacks Manager
14 Quick Reports
15 Kenny Rogers/Tony Romas Manager
16 Cash Management
17 Accounts Receivable
18 SXLMenu/Host
21 EditPro(V5+)
22 Manager(V5+)
23 TouchPro(V5+)
24+ — Currently Unused —

Other Documents