Can one Key (Rockey or iButton) be used to protect more than one Product for the same Customer?

Yes, each Key can be used to protect up to 16 separate Products for the same Customer.

Each Key has a 16-byte memory area called "User-Data" which can be used as needed.  The last 2 bytes of this area consist of 16 individual bits called User-Flags.  These User-Flags are originally turned OFF (set to zero), but can be remotely turned ON (set to one) with our Renew program.

Let's assume that you have 3 Products.  You could assign the 1st Product to User-Flag #1, the 2nd Product to User-Flag #2 and the 3rd Product to User-Flag #3.  Your programs in each Product would call KECHK to read the User-Flags and test if they are authorized to run or not.  For example, your programs in the 1st Product would read the User-Flags and test if the 1st User-Flag was set ON.  If so, your programs would continue running normally.  If not, your programs would display a message indicating that the User must purchase Authorization to use that Product.

When a Customer first purchases, you send out a CD-ROM containing all your Products, but the Key that you send only has the User-Flags set for what was purchased.  Later, when the Customer purchases additional Products, all you send is a Renew Code to turn on the appropriate User-Flag(s) in the Key.

Using the above example with 3 Products, let's assume that your Customer initially purchases the 1st and 3rd Products.  You would use EVERKEY to build the Key with the 1st and 3rd User-Flags set ON.  This Key would be sent to the Customer along with a CD-ROM containing all three Products.  The second Product could not be used because it would be checking the User-Flags and "see" that the 2nd User-Flag was not set ON.

Later, when the same Customer decides to buy the 2nd Product, you would use EVERKEY to generate a Renew Code that will set the 2nd User-Flag ON.  You could email the code to the Customer who would use the Renew program to update their Key.  Now, all three Products can be used.

Can updates to a protected Product be placed on a web site for Customers to download?

Yes, there are several ways to create protected downloadable upgrades that only work for your Customers and you never need to send out a new Key (Rockey or iButton).

If you release a FREE upgrade, then you probably want to create a "generic" upgrade that works for every Customer that already possesses a Key for your Product.  In this case, you simply create the upgrade to check for your same unique Key that was required for the old version of your Product.  Once the upgrade is placed on your website, each Customer just downloads and installs the upgrade.  It works immediately because they already have the Key from the old version of your Product.  There is no need to send them a new Key (Rockey or iButton).

If you release a NON-FREE upgrade, there are at least two ways to ensure that every Customer pays for the upgrade. 

• One way is to create a separate upgrade for the Serial Number of every Customer that orders the upgrade.  Each upgrade would then require your specific Product Rockey of a specific Serial Number.  For a small number of upgrades, this may be a workable solution.
• Another way is for the Upgrade to require a User-Flag in order to run.  For example, your Upgraded software might check the User-Data to see if the 2nd User-Flag is set to ON.  If so, it would run normally, but if not, it would display a message explaining how to "purchase" a "Renew Code".  The purchased Renew Code would set the 2nd User-Flag to ON. 

Can EVERKEY be used to protect data?

EVERKEY can only be used to protect executable or pseudo-executable files such as EXE or DLL files.  EVERKEY could be used to protect a proprietary file viewer or run-time engine, but not the data files themselves.

Is EVERKEY compatible with all versions of Windows?

EVERKEY Version 6 (currently in Beta) supports all 32-bit and 64-bit versions of Windows 2000 thru Vista, including Windows Server Editions. 

EVERKEY Version 2 fully supports all 16-bit and 32-bit versions of Windows from Windows 95 thru windows XP, including Windows Server Editions.  Most brands of DOS Version 5 and later are also supported. 

If you have programs protected with Version 2 that need to be run on 32-bit and 64-bit Vista systems, please follow the instructions contained here.

Does EVERKEY support the Mac OS X or Linux operating systems?

No, not at the current time.

EVERKEY Version 6 (currently in Beta) has been rewritten in a programming framework that supports Windows, Mac OS X and Linux.  Version 6 will be first be released for Windows with Mac OS X and Linux versions to follow. 

Does EVERKEY interfere with hardware plugged into other computer ports?

No interfererence problems have been reported since 2002.

The only known interference problems were reported with Parallel or Serial Port (not USB) Keys using versions of EVERKEY prior to 2.31. 

What is UserPort and how is it used?

Please note that UserPort is NOT required if you are using Rockeys or Kechk32.dll.  It is ONLY required for iButtons to be accessed from DOS (16-bit) programs. 

UserPort is a Windows 32-bit device driver written by Tomas Franzon.  It allows 16-bit programs to access iButtons when running on Windows 2000, Windows XP or Windows Server 2003.  You may redistribute this driver. 

UserPort consists of the two (2) files UserPort.exe and UserPort.sys.  If you are running the Azsetup.exe program under Windows 2000, XP or Server 2003, the UserPort.exe file will be installed to the main Windows folder and the UserPort.sys file will be installed to the "system32/drivers" folder under the main Windows folder.

The UserPort driver must be manually started once and will thereafter start automatically each time Windows is booted.  Of course, you can manually stop the driver at any time. 

To START the UserPort driver:

1. Be sure you're running on a Windows 2000, XP or Server 2003 system.
2. Be sure that the Az-Tech Device Drivers have been installed using Azsetup.exe.
3. Click "Run" on the Windows "Start" menu.
4. Enter "userport" and click "OK".
5. Click the "Start" and "Exit" buttons on the UserPort dialog.

To STOP the UserPort driver:

1. Click "Run" on the Windows "Start" menu.
2. Enter "userport" and click "OK".
3. Click the "Stop" and "Exit" buttons on the UserPort dialog.

What stops a Customer from starting the protected Product, then moving the Key (Rockey or iButton) to another computer?

You can use the KECHK function to check for the presence of your Key as often as you like.  This will make it much more difficult to move the Key while your protected program is running. 

For example, you might want to call KECHK to verify the presence of your Key every time your Product does a "Print" or "Save" function.  Or, you might want to call KECHK every 2 minutes. 

When your Product first starts, it's always a good idea to verify the presence of your Key.  This is usually done using KECHK function #1 or #2.  When this function completes, KECHK will return the unique Lasered-ID of your Key.  This will allow you to use the KECHK function #4 for all subsequent presence checks.  Function #4 is much faster than function #1 or #2. 

Each time you call KECHK, you will be verifying that your Key has not been moved to another computer. 

What prevents another EVERKEY User from making Keys (Rockeys or iButtons) for your Product?

In a word, the PIN.  The "Product Name" and "Encryption Key" Options used by the Kebuild.exe program determine the PIN for your protected Product.  And your program must specify this exact PIN when performing a KECHK function to check for the presence of your Key (Rockey or iButton). 

In order to build a Key for your Product, another EVERKEY User would have to know the "Product Name" and "Encryption Key" that you used when building your Keys.  Although the "Product Name" is easily determined by using the Keshow.exe program, the "Encryption Key" is only stored in your Options file.  This is why both the PIN and "Encryption Key" should be treated as a company SECRET.

How do I prevent 2 or more computers from using a port-sharing device to "share" a single Rockey or iButton Key?

It is quite easy to prevent this. 

When your program starts, generate a random number, store it in a Static variable and then write it to a specific offset in the User-Data. 

Throughout your program's operation, you can check the Key's User-Data to ensure that the random number is the same. 

If another computer is also running your program during this period, and using the same Key, a different random number will have been written to the User-Data. 

How do I install the EVERKEY Device Drivers?

The easiest way to install all the correct Device Drivers for the supported versions of Windows is to use the Azsetup.exe or AzRockey.exe programs.  Both of these programs perform "single-click" installation and you may redistribute them with your software Products. 

Azsetup.exe:

• Installs the Rockey4 and iButton Device Drivers for EVERKEY Version 2. 
• Although these are NOT the most current Device Drivers, they are required when using Kebuild.exe and Keshow.exe from EVERKEY Version 2. 

AzRockey.exe:

• Installs the newest Rockey4 Device Drivers. 
• Does NOT install Device Drivers for iButtons. 
• Allows Kechk32.dll and Renew32.exe to be used on all 32-bit and 64-bit Editions of Windows 2000, XP, Vista and Server. 
• Installs drivers that do NOT work with Kebuild.exe and Keshow.exe from EVERKEY Version 2. 

If you're using Kebuild.exe from EVERKEY Version 2, use Azsetup.exe to install your drivers.  Since this version of Kebuild.exe does not run on Vista, this means you'll have to use Windows XP or earlier. 

For your Products that you send out to Customers, use AzRockey.exe because it supports all versions of Windows since 2000.  If you include the Keshow.exe program as a diagnostic tool, be sure to use Version 6.  It's easier to use and works with all drivers. 

If you want to include the Device Drivers as part of your custom install process, please refer to the EVERKEY User's Manual which provides all the details for how to do this. 

Azsetup.exe, AzRockey.exe and the EVERKEY User's Manual are available as a free download from here.

Can I connect my Rockeys via a USB Hub?

Rockey4NDs work fine with USB 1.1 and 2.0 Hubs. 

However, USB Hubs have become a commodity item and not all are built to quality standards.  On rare occasions the Rockey4ND may not be detected through the Hub due to inadequate output voltage or bad connections. 

To determine if the problem is with the USB Hub, check the Rockey4ND in a USB port that does not use a Hub. 

If the Hub is the problem, sometimes just plugging the Rockey4ND into a different port on the Hub is enough to solve the problem. 

Our experience is that most problems with USB 2.0 Hubs are related to inadequate power supplied from the computer port.  This problem can almost always be eliminated by connecting an AC Power Adapter directly to the Hub. 

What is the lifetime of an EVERKEY Rockey Key?

It depends on how often you update the memory in the Key.  Each bit of the memory in the Rockey can be re-written at least 100,000 times.  However, Rockeys employ "Wear Leveling" which distributes the re-written bits to the "least worn" areas of the memory.  Wear Leveling dramatically extends the life of the Rockey and also makes it substantially more reliable throughout its lifetime. 

Obviously, Rockeys can handle a lot of updates, but not an unlimited amount.  These examples will show how to predict the lifetime of your Rockeys:

• If you build a Rockey without an Execution or Date limit, and the User-Data is never changed, then your Rockey will never be updated by a KECHK call.  In this case, your application should expect to be able to read the data from the Rockey for at least 10 years. 

• If you build a Rockey with an Execution and/or Date limit, the device's memory will usually be updated each time you verify the presence of the Key.  So in this example, the lifetime of the Rockey really depends on how often your protected program performs KECHK calls. 
  
  Wear Leveling can multiply the write-cycle endurance of a Rockey by up to 64 times, but for this example, let's use a "worst case" scenario of only 2 times. 
  
  So, if your program checks for the Key 100 times per day, seven days a week, then your Rockey should last at least 5.4 years (100,000 updates times 2 for wear leveling divided by 100 updates per day divided by 365 days per year).
  
  If your program checks the Key 100 times per day, but only five days a week, then your Rockey should last at least 7.6 years (100,000 updates times 2 for wear leveling divided by 100 updates per day divided by 260 days per year).

What is the lifetime of an EVERKEY iButton Key?

At least 10 years. 

iButtons contain their own lithium power source which allows them to retain their data for at least 10 years.  Updates to the data have no effect on the life of the iButton. 

What is Error 6043?

This Error means that the requested Key (Rockey or iButton) can not be found.  Check the following items:

1. Ensure that the Rockey or iButton is plugged into the computer.  If you are using USB Rockeys, you can tell that the device is plugged in correctly when the LED is solidly illuminated.  If the LED is blinking steadily (not flickering), the Rockey4 Device Drivers have not been installed properly.
2. Verify that the Device Drivers have been installed.  If you have used the Azsetup.exe program to install the drivers, you can use the Start->Run menu from the Windows taskbar to run the Azshow.exe diagnostic program.  This program will tell if the drivers have been installed correctly.  If the program is not found, then the drivers need to be installed.  To do this, run the Azsetup.exe program. 
3. If you are using iButtons in Parallel Holders, verify that any connected printer is powered up and online. 
4. If you are trying to access iButtons from a 16-bit program running under Windows 2000 or Windows XP, be sure that UserPort is active.  To do this, first use the Start->Run menu from the Windows taskbar to run "userport".  Then, on the UserPort dialog, click "Start" and then "Exit".

When using Renew, what is Error 6075?

This Error is caused by:

1. The Renew Code was entered incorrectly.  Try again.
2. The incorrect Options File, Serial Number or Renew Use-Count was specified to the Kecodes.exe program when the Renew Code was built.  In this case, the Renew Code needs to be re-built using the correct information. 
3. A very old version of the RENEW program is being used and the code was built with a new version of the Kecodes.exe program.  To correct this problem, just email or send the latest version of the RENEW program to the Customer and try the code again.