  |
  |
|
 |
||||
 |
Hardware Unique ID Extractor
-DLL and source code available-
|
|
||
TOC
Programming languages supported Example application (compiled)
MANUAL
How to call it from your language How to import the DLL - Code snippets
|
|
The Hardware ID Extractor is a library for programmers (both Microsoft Windows and Linux). It offers functions that extract data about your computer's hardware (CPU, HDD, RAM, main board, video BIOS), including unique hardware identification numbers. Source code & compiled DLL available.
This library can be used to:
|
||
The functions offered by this library can read the following hardware information:
Hard disk
CPU
Physical memory
BIOS (NEW!)
Detailed list off exported functions is available here.
You can download the DLL right now. It is FULLY functional and requires no installation. Some of the functions exported are free, others will display an ad. Get a key to unlock all functions (to stop it from displaying the ad).
If you have multiple applications delivered in your product's package, you can deliver our DLL along with your product. You don't need to install the DLL in Windows folder. Just leave it in your application's folder. If you want you can rename the DLL to anything you want. Using the source code, you can also chose to compile your own DLL or to integrate the functionality directly into your application.
Programming languages supported The DLL provided was compiled using the standard calling convention (StdCall). Therefore, it is compatible with ALL programming languages that support this calling convention. C Builder, Visual C (basically all strains of C/C++), Visual Basic, Liberty Basic, Visual Fox Pro, Delphi, Lazarus, Free Pascal, PowerBuilder, Clarion, Visual Studio (C#, VB), etc are all able to use the DLL. If your programming language does not support this calling convention (it must be a really old programming language), use the source code to compile your own DLL or to integrate the functionality directly into your application. The DLL also supports Microsoft VBA powered languages such as Word, PowerPoint 2000, 2003, 2007, Excel, Access, etc.
Why any programmer MUST use hardware-signed keys?
Using hardware-signed keys you will increase your profit. There is a chain of three events that leads to increased revenue:
There are several good reasons to choose our library:
HDD For example when they read the HDD they get the volume ID. This number is indeed unique but it changes every time the user formats the drive to reinstall its operating system. We also offer a function to read this number. However, we offer the real deal: a function that reads the device ID written by manufacturer in hard drive's IDE chip. This number is absolutely unique on the planet (no other hard drive has this ID) and it is 100% unchangeable.
CPU The same for CPU. They offer a function to read the unique serial number of the CPU. While this worked perfectly with single core CPUs, none of the libraries we have tested works properly with multi core CPUs. This is because the application can have access only to the core in which it currently runs. Unfortunately, Windows can start the application in any core, therefore you will probably see four different ID's for a quad-core CPU. Our library is the only one that works properly and extracts the correct CPU ID number. Note:
NIC Other libraries offer you a function to read the MAC of the network card. We just decided not to bother offering such a functions since the MAC can be so easily changed.
PRICE There is also the "small" issue called PRICE. Similar libraries force you to pay the big buck to purchase them. Usually the prices are around $100 for DLL and many hundredths of dollars for source code.
FLEXIBILITY Other DLLs does not allow you low level access to the functions that extract the hardware identification numbers (maybe they try to hide that their library don't extract the true serial numbers). Instead the offer you access to a single function that extracts some the numbers hashes (MD5) these numbers and finally returns to you the hash. Our DLL gives you access to all its inner working! You can decide which hardware to read and which not and to implement the protection system exactly the way you want/need!
Overall, most concurrent products around do not offer you the true hardware ID, are really expensive, don't show you what happens under the hood, don't provide the code, are unreliable or difficult to use.
Source code/Exported functions
The Hardware ID Extractor library was written in Delphi. The source code also contains Windows API calls and assembler code. Most of these functions are also available via our DLL; other functions are used internally and are not exported by the DLL. To see all functions available in this library please see this document: Delphi programmers, C (and other) programmers.
How to call the functions exported by the DLL from your programming language
In this page you will find examples of how to use the functions exported by the DLL from your preferred programming language. After you load the DLL you can access read the hardware information as simple as calling the appropriate function.
Example application (compiled)
Here you can find the source code and complied EXE of a demonstration application called Hardware ID Extractor that reads the hardware information and displays it on screen. This demonstration application is 100% freeware. See screenshot.
Hardware Programming tutorials
Related programs
Related key words: Get disk serial, real hard drive serial number, hardware ID number, programming code, DLL library, extract hardware info, get CPU producer frequency and produce |
||||
 |
||||
Hard drive ID (unique hardware serial number written in drive's 
