USB installation files for older version of Windows, and DLL for specialized application *note be sure to put the DLL from the relevant archive into your application folder ( overwrite any already there )
This DLL is ONLY for applications that are specifically 64-bit. It has nothing to do with running most
apps on a 64-bit system. Good examples would be Matlab, DLL access using VBA from within 64-bit Microsoft
Office, etc.
This is NOT for use by any of our applications.
More about it
here
NOTE
To download an archive, right-click link with mouse and choose "save target as" from drop-down menu.
Use a file decompression utility such as the one that is included with recent versions of Windows - WinZip® or similar software for older
versions of Windows - to extract the contents. Follow the instructions in the "ReadMe.rtf" for file usage instructions.
*Individual files require no decompression software.
This utility was created to reduce the possibility of confusion that can result from using a copy
of the DLL that does not correspond with a particular version of the driver. Such a situation could happen
if, for example, a new copy of the device driver is installed while not also installing the version
of the DLL that is typically supplied with it in an archive or distribution source. A driver/DLL
mismatch can also occur if old copies of the DLL find their way into various folders on your disk
drive which may then be found by the Windows loader prior to the location where you may have placed
a newer copy. This will cause an older copy to load with the application while you may think that the
most recent one is loading.
Utility for listing connected M30x devices
M30x device lister
This utility was created to assist in finding out which of our Model 301 and/or 302 devices are currently recognized
as being connected to your PC. It can help avoid confusion of using an app to initialize a device and having
it fail because the device isn't even being seen by the system as being connected. It will list all the devices
that are seen as being connected, whether they are Model 301s or Model 302s.
Extract archive into a folder and execute the .exe. This archive may not be updated as often as the most recent DLL. So if it fails to run, get the
most recent DLL and/or driver file(s) from one of the links at the top of this page.
In Win7 the installation of the driver is transparent when connected to the internet. When the 301 or 302 is powered up and
connected to the PC via the USB cable while the PC is connected to the internet, Win7 will automatically install our device driver
from the online Microsoft Windows driver database, onto your PC. Then just make sure you have the most recent DLL in
the application folder (either your own app or one of our sample apps downloaded from the internet) and you are ready to run.
If you are not connected to the internet then the "not connected to Internet" instructions found within the archive should be
followed. Note that the DLL in the downloadable archive may not be the most recent one but is still designed to work with the .sys file
either included in this archive or automatically installed off the Internet by the Win7 installer. go back to where you were
On a new installation of WinXP, it may be necessary to install some Windows system support files
in order for our newest DLL to be recognized by the system. An indication of this requirement would
be a notification that the application cannot find the LL_USB2k.DLL when you run the application, after
a successful installation process and with the DLL in the same folder as the application. If
you receive that notification, then download and run the following to install the required Microsoft
support files.
You can either download the file by clicking on the link and choosing to save, and then
once it's on your machine, execute it. Or with some browsers you can run it directly by choosing the option
to from the menu you'll be presented with by clicking on it.
When running LL_USB.msi you may be presented with a security warning since it's considered an unknown executable type. Ignore the warning,
if a box is checked asking if you should always be asked before opening the file, leave it checked, and then press the "Run" button. You
will see a box that says "Welcome to the LL_USB Setup Wizard. click the "Next" button. The next box will ask you to select an installation
folder with a default path for the folder being:
C:\Program Files\LL_USB\LL_USB\
Leave that path as it is (nothing will actually be installed in that folder) and keep the "everyone" option selected and click the "Next"
button. Next there will be a box to confirm installation - click the "Next" button. You'll be notified that LL_USB is being installed and
eventually that the installation is complete. Now, when you try to run the application with LL_USB2k.DLL in the same folder as the application,
you shouldn't receive an error that the DLL cannot be found.
If you run it again, for example if you couldn't remember if you alread ran it, you'll be presented with a box asking you if you want to
repair or remove it. If you get that message, just click the "Cancel" button.
The installer will have installed the required support files:
The Version Checker utility, "VerChk.exe" is designed to assist in troubleshooting
problems related to communication between various versions of our Device Driver, DLL, .INI file,
and .INF file.
Due to some of the complexities associated with unitial loading and updating of
various files when installing USB and similar devices, we've created this utility to help our
customers find problems that may be associated with incompatible copies of our files which may
either be initially placed on their system, or may accumulate as the result of numerous or
incorrect updates.
The Version Checker Utility has various modes of operation. In the simplest mode, it will scan
your system for all copies of the following files, and log it's process to a log
file, "VerLog.txt" in it's current directory.
For WinNT/2K/XP/7/8
LL_USB2k.SYS
device driver
LL_USB2k.DLL
dynamically linked library
LL_USB2k.INF
driver installation information - used by Windows installer
LL_USB.INI
configuration info - used by our DLL
For Win98/ME
LL_USB.SYS
device driver
LL_USB.DLL
dynamically linked library
LL_USB.INF
driver installation information - used by Windows installer
LL_USB.INI
configuration info - used by our DLL
Reading that log file may give you clues to problems that you may be having when trying to interract
with the device and/or software. The log file
can also be used when interracting with Lawson Labs, Inc. technical support.
A more advanced mode provides a lot of user interactivity with the ability to check your system
for any one or all of the files named above and even remove unwanted or unneeded copies.
Within the archive containing "VerChk.exe", there is brief documentation to further explain
things as well as a sample "VerLog.txt" file to show how a log file may look. Before running the utility,
be sure the DLL is in the same directory as "VerChk.exe" and that all of your Model 301/302 devices are connected.
As will be explained in the documentation for VerChk, be sure to place VerChk.exe in the same folder where you have
the DLL that you are attempting to use, since one of the main functions of the VerChk utility is to determine if the
M30x DLL that you are using is the correct one to use with the M30x device driver that you are using.