Thank you jeff. Now I understand, the array musy be completed with proper values provided when you buy the product.
Also, I suppose that you have to include a dll into the software folder. Do you have to include the .exe file in the usb?
And, by the way, are you happy with this software?.
Thank you!!!
You do need to include the DLL in the folder where your exe is.
You do not need to add anything to the usb drive, just use the make program to set it as a valid key and that's all you need to do the the usb drive.
Note: the usb drive can still be used as a regular drive, you can copy and delete files as normal.
>>Am I happy with the software<<
Antonio and I are still working out some Fivewin code setup.
What I have tested so far is very promising.
Once the final changes have been completed we will post the code here.
Thank you very much to you and Antonio for your work!!!!
Jeff, thanks for the tip. This looks interesting. I'm curious however whether softwares that are protected using this method can run on Win9x? Their webpage states among the system requirement is XP/2000/Vista etc. No mention of win 9x at all.
FUNCTION MAIN()
LOCAL oLoc := CREATEOBJECT( "wbemScripting.SwbemLocator" )
LOCAL oSrv := oLoc:ConnectServer()
LOCAL oJbs := oSrv:ExecQuery( "SELECT * FROM Win32_DiskDrive" )
LOCAL oJob
FOR EACH oJob IN oJbs
// IF SUBSTR( oJob:PnPDeviceID, 1, 7 ) = "USBSTOR" Then
? oJob:PnPDeviceID
// ENDIF
NEXT
INKEY( 0 )
RETURN NILI wonder how good is this protection system if the USB pendrive containts get cloned...
That is why I proposed to embedded id of the usb drive.
Mike,
But the usb drive id is defined by software or hardware ?
When you do a dir of it, you get its id. Will it will remain the same if we reformat it ?
To Test I checked the serial before and after format of the use drive and it returned the same.
I also tried formatting it on an ex pro station and a vista home station and it returned the same.
So I believe that it is returning the hardware id.
> So I believe that it is returning the hardware id.
In that case then its a valid tool for software protection, though no extra software should be required. Just check the usb drive ID, encrypt it and store it.
Jeff, Mike,
If we are able to locate the UDB pendrive ID then we can protect the application using standard FWH code 
#include "FiveWin.ch"
#define DRIVE_REMOVABLE 2
function Main()
local nBitDrives := GetLogicalDrives(), n, cDrive
for n = 1 to 32
if lAnd( nBitDrives, 2 ^ ( n - 1 ) )
cDrive = Chr( Asc( "A" ) - 1 + n ) + ":\"
if n != 1 .and. GetDriveType( cDrive ) == DRIVE_REMOVABLE
MsgInfo( "USB pendrive: " + CRLF + cDrive )
endif
endif
next
return nil
#pragma BEGINDUMP
#include <hbapi.h>
#include <windows.h>
HB_FUNC( GETLOGICALDRIVES )
{
hb_retnl( GetLogicalDrives() );
}
HB_FUNC( GETDRIVETYPE )
{
hb_retnl( GetDriveType( hb_parc( 1 ) ) );
}
#pragma ENDDUMPTo get the USB pendrive is as easy as (in the above code):
MsgInfo( "USB pendrive: " + CRLF + cDrive, nSerialHD( cDrive ) )
Getting closer to have our own based USB pendrive copy protection system...
Mike,
I have formated a pendrive several times here, and everytime it gets a new volume ID. A complete format, not a quick one.
Not good...