[ketan]

safekey hardlock emulator details explained...

safekey have developed dumper for parallel as well as usb dongles,
fastread.com is for parallel type and usbsaferead.exe is for usb.

>> fastread.com (ie. parallel port dumper )

it dumps hardlock dongle data into <modid>.log file,
the log file format...

typedef struct {
BYTE algodump[ 0x2000 ];
BYTE datadump[ 0x80 ];
BYTE a,b,c; // n/a
WORD algo2; // highword of base address maybe
BYTE d,e,f,g,h; // n/a
} log_t;

>> usbfastread.exe (ie. usb hardlock dumper )

this is revised solution from safekey to dump/process usb hardlocks
on examination i found that it contain vxd/sys files into resource section which is dynamically loaded,
and they perform main dumping and etc... but usbfastread.exe is just frontend which process other things
surprise is it produce .fst file which is infect extension used for solved files !!!
the fst file format...

typedef struct {
WORD dunno1; // ModID
BYTE algodump[ 0x2000 ];
WORD dunno3; // n/a
WORD dunno4; // ModID
BYTE datadump[ 0x80 ];
BYTE dunno6[ 0x8 ]; // ?
} fst_t;

>> safekey *.fst file ( ie. files used by emulator )

typedef struct {
DWORD BaseAddress;
WORD ModID;
BYTE datadump[ 0x80 ];
BYTE InitVectorNibble0;
BYTE InitVectorNibble1;
BYTE InitVectorNibble2;
BYTE InitVectorNibble3;
} fst_t_solved;

observations
============
- there exist some more dumpers which have same content as far as algodump is concerned