Can one Key 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.

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.

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 Editions of Windows 2000, XP, Vista, Windows 7 and Server. 

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. 

Programs protected by EVERKEY Version 2 can be run on any 16-bit, 32-bit or 64-bit version of Windows including Windows Server Editions. 

For running your EVERKEY protected programs on Vista or Windows 7, the step-by-step instructions are here.

Is EVERKEY compatible with the new Microsoft Windows 7?

EVERKEY Programs That Are Distributed to the End User
The Good News is that all EVERKEY programs that are distributed to the End User work fine with the 32-bit and 64-bit Editions of Windows 7.  This means you can distribute your protected applications the same way you do with Windows Vista.  Here is a summary of our testing:

• AzRockey.exe works fine installing the Device Drivers for Rockey4s. 
• Kechk32.dll v2.31.005 and later works fine for verifying the presence of your Rockey4. 
• Renew32.exe v2.31.006 works fine for renewing your Rockey4s.  Be sure to use this version because earlier versions do not work with Windows 7. 
• Keshow.exe Version 6 works fine showing Rockey4 devices. 

EVERKEY Programs Used to Protect Your Application
These are the programs that are only used by the Software Developer.  They are not distributed to the End User. 

• Kebuild.exe v2.31.005 does not work in the Native mode of Windows 7.  However, we were pleasantly surprised to find that it works perfectly in the Virtual Windows XP mode.  (Here is how it's done.) Kebuild is being completely rewritten for EVERKEY Version 6 which supports Windows 2000, XP, Vista and Windows 7 (all Editions, all Modes).  So, until Version 6 is released, you'll have to use Virtual Windows XP mode to run Kebuild.exe.
• Kecodes.exe v2.31.005 runs fine in the 32-bit versions of Windows 7.  However, just like the Kebuild program, you'll need to use the Virtual Windows XP mode to run Kecodes in the 64-bit Editions of Windows 7. 

Rockey4 devices work fine in all Editions of Windows 7.  Our timing tests showed no differences in speed of access between Windows XP, Vista and Windows 7. 

How do I run Version 2 Kebuild and Kecodes on Windows 7?

Your End Users don't have to do anything special to run your EVERKEY protected applications under Windows 7. 

However, in order for you to program Rockey4 devices with Kebuild running under Windows 7, you will need to use Virtual Windows XP mode. 

Virtual Windows XP requires that your computer support hardware virtualization.  Although OEMs have been shipping hardware virtualization in PCs since 2006, not all new PCs have it.  Also, some PCs with hardware virtualization have it turned off by default, so you will need to turn it on.  Microsoft.com/Windows/Virtual-PC  has excellent documentation on this subject. 

One final note: Microsoft chose to not support Virtual Windows XP in Windows 7 Starter, Home Basic and Home Premium.  This means it can only be used with the Windows 7 Professional, Ultimate and Enterprise Editions. 

So, if your PC supports it, here is how to set up Virtual Windows XP.  This procedure works with both the 32-bit and 64-bit Editions of Windows 7:

• Be sure you're logged-in as an Administrator. 
• Download Windows Virtual PC RC and Windows XP Mode RC from Microsoft.com/Windows/Virtual-PC . 
• Double-click WindowsXPMode_nn-NN.exe (where nn-NN is the locale, for example: WindowsXPMode_en-us.exe).  Follow the instructions in the wizard to extract and install the application. 
• Double-click Windows6.1-KB958559-x86.msu or Windows6.1-KB958559-x64.msu (depending on your architecture).  Follow the instructions in the wizard to install the update.  After installation, click Restart Now to reboot.
• After Windows has restarted, login as an Administrator and click Windows XP Mode from the Start menu. 
• If you accept the license terms, check the box and click Next. 
• Enter a Password for the XPMUser User and record it in a safe place. 
• Select a preference for Automatic Updates and click Start Setup. 
• The setup will take a few minutes and then Windows XP will startup in a Virtual PC window. 
• From the Virtual PC window, install Kesetup.exe.  This will install EVERKEY Version 2.31 and the older version of the Rockey4 Device Drivers. 
• Plug in a Rockey4.  From the Menu bar, click USB and select FeiTian Attach. 
• In the Found New Hardware Wizard dialog, select "No, not this time" and click Next.  Then, click Next again. 
• When the Hardware Installation warning message appears, click "Continue Anyway".  Then, click Finish. 

You now can use all EVERKEY Version 2 programs just like you were using a real Windows XP system! 

Just a couple of things worth mentioning: 

• In the Real Windows XP, the Found New Hardware Wizard dialog appears each time you insert a Rockey4 into a different USB port or USB Hub port.  Using Virtual Windows XP mode, the dialog only appears the first time you insert and attach a Rockey4.  This is a big improvement. 
• In this version of the Windows 7 Virtual Windows XP mode, you have to click Attach every time you plug in a Rockey4.  If the Rockey4 is blinking slowing, then you know you forgot to Attach it.  Hopefully, Microsoft will provide a way to attach automatically in a future release. 

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 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 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. 

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 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 setup my protected programs to run on Vista or Windows 7?

Here's how to make sure that your Customers have NO PROBLEMS installing and running your protected programs on Vista and Windows 7. 

A typical Product protected by EVERKEY contains the programs Kechk32.dll and Renew32.exe.  You might also include the Keshow.exe program because it's an easy-to-use Diagnostic tool.  The latest versions of these programs are fully compatible with all 32-bit and 64-bit Editions of Vista and Windows 7. 

Step-by-Step Instructions

Here are the step-by-step instructions for setting up your protected programs to run on Vista or Windows 7:

1. Copy the latest version of AzRockey.exe to your Product CD.  This program will do the installation of the Rockey4 Device Drivers.  Do not use Azsetup.exe - It installs the old version of the Rockey4 drivers.  Here's where you get the latest version of AzRockey.zip.  This Zip file contains the AzRockey.exe program and works with all 32-bit and 64-bit Editions of Windows 2000, XP, Vista, Windows 7 and Server. 
2. Be sure that your Product CD contains the latest versions of the following EVERKEY programs:
   • AzRockey.exe v6.2.4 or later (see previous step). 
   • Kechk32.dll v2.31.005 or later.  This is the module that verifies the presence of your Rockey.  Get the latest version here. 
   • Renew32.exe v2.31.006 or later.  This program allows you to remotely change the Date Limit, Execution Limit and Feature-Flags stored in your Customer's Rockeys.  Be sure to use this version (or later) because earlier versions do not work with Windows 7.  Get the latest version here. 
   • Keshow.exe v6.2.4 or later.  This utility program allows your Customer to display basic information about any Rockeys that are plugged into their computer.  Most Developers include this program as an easy-to-use Diagnostic tool.  Get the latest version here. 
   • Ibfs32.dll (any version).  This is a library DLL that is required by Kechk32.dll and Renew32.exe.  You can ensure that this DLL is always available by copying it into the same folder with the Kechk32.dll and Renew32.exe programs.  Get the latest version here. 
3. Have your Customer install your protected Product FIRST and run AzRockey.exe LAST.  Be sure to have your Customer install in this order because AzRockey.exe will overwrite any older drivers with the newest Rockey4 drivers.
4. Your Customer can now begin using your protected programs. 

Step-by-Step Instructions Notes

1. Vista and Windows 7 requires Administrator rights to install Device Drivers.  This means that your Customer will have to be logged-in as an Administrator or enter the Adminisrator Password when running AzRockey.exe. 
2. For most Editions of Vista and Windows 7, it is still necessary to unplug any Rockey4 devices first before running AzRockey.exe to install the Device Drivers.  If you don't want your Customer to unplug the devices, restarting Windows will have the same effect. 
3. If Azsetup.exe has already been used to install the old version of the Rockey4 Device Drivers, there is no need to uninstall it first.

How do I install the EVERKEY Device Drivers?

In order for the EVERKEY programs to be able to access Rockey4 Keys, you must first install the Rockey4 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. 

If you use one of these programs to install the Device Drivers while the Rockey4 is plugged into a USB port, the Rockey4 may not be accessable until 1) it's re-inserted, or 2) Windows has been restarted. 

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, Windows 7 and Server. 
• Installs Device 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 2000, XP or Windows 7 Virtual XP Mode.

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 no matter which Device Drivers are installed. 

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 can not be found.  Check the following items:

1. Ensure that the Key is FIRMLY plugged into the computer port. 
2. If you are using a USB Rockey4, there is a green LED just under the case near the rounded end of the device. 
   • If the LED is not illuminated at all, try plugging the Rockey4 in again or move it to a different USB port.  If it still doesn't light up, the Rockey4 is probably defective and needs to be replaced.  Here's how to request an RMA.
   • If the LED is blinking steadily (not flickering), the Rockey4 Device Drivers have not been installed properly.  Please see the FAQ entry on How to Install the EVERKEY Device Drivers. 
   • If the LED is solidly illuminated, this means that the Rockey4 Device Drivers have been installed, so there must be something else causing the 6043 Error. 

     If you have just installed (or re-installed) the Device Drivers while the Rockey4 was plugged in, the 6043 Error can be fixed just by unplugging and re-inserting the Rockey4. 

     Check to see if there is a "USB Filter Driver" installed.  Some "Entertainment" PCs, such as the HP Pavilion dv7-3000 Notebook might use a "USB Filter Driver" to improve the performance of USB Speakers or a USB TV Tuner.  Unfortunately, some early versions of these drivers interfere with normal USB access for non-Entertainment devices.  Visit the Manufacturer's website to see if there's a newer version of the driver.  The website should also provide instructions how to uninstall the driver so you can see if this is causing the 6043 Error. 

     If none of the above has fixed the 6043 Error, try restarting Windows.  If that doesn't work, submit an Email Form to Product Support. 

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.