Hello CDKiller,

i would say i found a bug in PID5.0b3.
When i click on "Multi Scan" and find a protection in a file, i can click on OK and then the "gimme a file to scan :P" dialog don't open again.

I cant reproduce this 'bug' :confused:

must be your computer :p

Greetings to cdkiller ;) nice job m8

@ GLH

for me it´s working fine... i don´t know whats wrong.
but i´ll see if i find a possible bug. maybe only after a certain protection was found, the bug appears.

@ R!Co

thx m8 i´ll do my best to keep it up to date.
nice to see your scanner comming along quite fine too.

Now i'm going confuse :confused: :confused: :confused:

I tested it again. Test game is "X2 - Die Bedrohung".
When i scan the original X2.EXE yesterday it was telling me "Securom 5.00.03".
When i scan it now, it tells me "Starforce" and "Scan the protect.dll". Then i turn to dll-files and scan the protect.dll and it found Starforce 3.0 . After that the open file dialog don't open again in MultiScanMode.

And then it going really mad. I click again on MultiScan and scan once again the X2.EXE and the PROTECT.DLL and nothing is found !!! Only after EXIT the PID5.0b3 and restart it i will find Starforce again.

I'm really confused .............


EDIT:
OK. The problem that i found SECUROM yesterday is "solved". Yesterday i was thinking the X2.DEV (from DEViANCE Crack) is a renamed original exe (for redirecting file checks). When i rename X2.DEV to X2.DEV.EXE and scan it, SECUROM5.00.03 is found. Scanning the real original exe (after reinstalling the game) brings me STARFORCE3.0 .

I am sure cdkiller will fix it :)

yep already fixed.
the multiscan option had a bug wich closed the fileopen dialog after scanning a securom file.

dear cd killer, i was looking at your credits for protection id and i noticed that there was noone with a capital i (I) in thier name, not even your i in protection "iD" why is this??

hmm i dunno. i think it looks smarter with i.e.
'PROTECTiON iD' instead of 'Protection ID' ;)

small bug:

scanned game.exe: SecuROM 4.83.52

scan for cd-checks -> Couldn't.... protected with safedisc only

thx EMPiRE for reporting the bug.
anyway it´s fixed now and my next release v5.0 FiNAL
was improved and tweaked in a heavy way.
so expect a nice surprise ;)

Hi cdkiller,

I have found bug in PiD. Because if I scan a compiled Delphi source, then I get the following message:

Even if I copiled an empty source this message also appears, anyway which Delphi-Version I use.

If I should send you an example, say it.


Bye Uncle cracker

yeah i know, it´s funny because my old v5.0 Beta 3 will detect
'Air ExeLock' in every Delphi compiled exe.

of course this bug is fixed in my v5.0 FiNAL ;)

i uploaded 3 preview screenies of my current *private* version.
check my site http://www.protectionid.owns.it/.

hope u´ll like it ;)

now that looks cool!