Escolar Documentos
Profissional Documentos
Cultura Documentos
The MMK has the unique ability to use different port lines (multiple modes) for communication making it very adaptable for
any incompatibilities with future new devices or protocols. The MMK is fully transparent to any other LPT device and passes
all port lines through unchanged. Multiple MMK's can be used on a single port for different products, and will not interfere with
other brands of hardware locks or other LPT devices (printers, scanners, drives, etc.).
The MMK does not contain a battery, but rather derives it's power parasitically from the port's TTL lines themselves. The
internal microprocessor operates over a wide range 2-5V and with a very small current demand of merely 100uA. Data is
retained using nonvolatile flash memory with a minimum retention of 40 years. The MMK utilizes multiple levels of sophisti-
cated encryption techniques along with randomized data encoding algorithms.
Problem Identification
While the robust MMK design has provided exceedingly good compatibility proven over many years of use, problems with key
access on an LPT port can never be completely eliminated. This can be caused by a wide range of circumstances beyond our
control. However in almost all cases these issues can be resolved easily once the cause of the problem is identified.
The modern personal computer environment is very diverse with unlimited options and configurations, dependent on the
operating system, computer, drivers, external devices, and the user's own configuration and setup. It is especially important to
be aware of any devices or drivers which may also be attempting to and/or do utilize the LPT port.
The most common problem associated with a hardware lock is the display of an application message: Key Not Found. The
obvious problem is of course that the key is attached to the computer. The possible reasons behind the application's lack of
ability to reach and properly communicate with the key is the subject of the following sections. Unfortunately there is no single
quick and easy answer that will fit all situations. Many different possible causes must be explored individually.
The following sections provide a catalog of causes which have occurred in the past. Some of the items may not apply to your
operating system, configuration, or product. If specific notes are made regarding operating systems or products, then that
section only applies to the restrictions cited. If no restrictions are given, then the section potentially applies in all circumstances.
Please read or ignore the sections which do or do not apply to your individual situation.
Note: In LEAP-5 the older DallasSemi keys are no longer supported, and that code does not exist in the product. This
message does not apply to LEAP-5.
Verifying the 16-Bit NT Driver is loaded properly [LEAP-4] [WinNT4, Win2K, WinXP]
To verify that the 16-bit virtual device driver is loaded, go to the Start Menu, select Run, and type in RegEdt32. Locate the
following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers. The VDD value is a
multi string value with one or more paths to driver files. DoubleClick on the VDD string and you will see each driver name
listed per row. There should be no blank rows in between drivers. The MMK driver will appear as MMK_VDM.DLL.
Verifying the 32-Bit NT Driver is loaded and running [WinNT4, Win2K, WinXP]
To verify that the 32-bit kernel driver is loaded and running, go to the Start Menu, select Run, and type in RegEdt32. Locate the
following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MMK_NTD. If you do not find the MMK_NTD
registry key, then reinstall the software. The key will have a PortCount value, and is the number of LPT ports found indicating
the driver is loaded and running. For each port there will be a pair of values such as PortBase0/PortSpan0, PortBase1/PortSpan1,
etc. depending on the number of ports. If your entries are similar than the driver is operating normally.