you really want to go down this path?

months to build a reply on the internet from fear....really?

seems you learned some new words...

now, before you reply...take a deep breath, collect your thoughts and perhaps think hard...really hard

I think this was a joke but I don't think it was a good one...

By the way, if you want to see software that is updated really rarely then see mine; sometimes it takes me not one year but several years to come up with a new major release. So, TippeX, you need to work on your release delays to overtake me. ;)

actually, its a bit more serious..cdkilller seems offline / uncontactable... last code commit from him was over 2 months ago and his activity on a lot of forums seems to have stopped too... i hope he is ok and i hope he touches base soon... its true there hasnt been a public release in a long time but there have been quite a few internal betas and tests... i might (time permitting) do a public beta in a few weeks, with the usual xmas final following after that the project will be on pause

I always get this error (Win 7 x64) what can I do?

you can wait for the next release (soon), that bug is fixed (and also reported previously), quite some time ago actually

The GetProductInfo-value PRODUCT_PROFESSIONAL isn't implemented and thus the function which joins the OS-string returns "<Unknown>". However, it's incorrectly passed via the ebx- instead of via the eax-register, leading to a memory access violation:
Here's a fix:

its fixed already, same with win7 issues..
i also deleted your attachment as you have no rights to adjust the code or make a public distribution, so fuck you very much for that, if you want to help then pm me or email, what you did was plain shitty

haha, wtf is wrong with you?
As for the crash happening when starting your tool, your last response, stating it's already fixed 'n stuff, was 4 months ago.
And though, there still isn't a new version on your homepage which is why I figured it might be helpful if I post a quick fix so those experiencing the same crash, who are therefore unable to use your tool at all, could at least use the fixed version I posted temporarily until one comes out officially.
So fuck you very much.

my point is that you have no right to publically alter the code and release the 'fix' publically... you really think that was the right thing to do?.. as for release, cdkiller has not been online in a long time.. hence no releases, i mentioned this also

you want to help in release? then work with me, what you did was not on at all.. and you should know that...

the *correct* course of action would have been to contact with info on how to reproduce the issue and a fix.. not being a dick and posting an altered exe and thinking that was fine

I actually didn't think it'd upset you this much.
And why would I want to contact you? You already said it's all fixed 'n shit.
Though, there is no update yet. So I thought I might help if I post a temporary fix for those who can't use Protection ID atm.

well it seems you really dont understand...

you really think altering the exe and posting publically was the right thing to do?
i mentioned it was fixed AFTER you made your post... not before, so the point of taking the correct path (ie: contact) still stands

and then the point of were you think you get the right to make and ditribute the patch is also raised... are you on the beta team, or the coding team (i know you are not), or in the development... ? nope...


point made? if you want to help thats fine, doing what you did is not the way to go about it

k, I get it, you may lessen your rage now..

Though, you're wrong in the following point:
The small bug I'm talking about is the same one 5moufl was quoting whom you've answered that it was already fixed.
Telling him that and that he should wait for the next release isn't really helping, though, as he probably couldn't use ProtectionID for the last 4 months and still can't.

running in compatabibility mode solves it too...
trying to excuse your action just makes it worse... i offered you a chance to help, you didnt comment...
and now trying to justify it by making it out that it helps another user doesnt exactly help now does it... what you did was wrong.. just get the point and we can move on

call to arms
 

as some of you are probably aware, cdkiller has disappeared and seems uncontactable, he emailed me once saying he would be in touch, but that was over a year ago :(...

so...

im trying to keep the project going, but now its really just a 'one man show' and i have a lot of real life stuff to deal with, so if anyone would like to help by giving files, detection info, code (asm preferred but i can port it if necessary), detection methods etc please contact me at the *new* email address -> protectionidteam at outlook.com (edited to avoid spammers), you should know how to piece it together :)

also, that means i have no information on the beta testers, so as a result i am opening that up again, simply contact me on the email saying what you can bring to the project (testing, code etc) and i'll respond as soon as i can

i plan to keep the project open as im sure thats what cdkiller would have wanted, hopefully he might see this (and/or some of the other things i did to reach out to him) and get in touch, but continue we must..

i've updated the code a lot, mostly on the build system, some code fixes and bugs fixed (including the windows 7 one), detections are at 540 at the moment and i plan to release a public beta very soon (maybe at the weekend if time permits), so if you want to beta test, or even help out, please do contact me

yeah, he's probably dead or in jail.

with disc based drm about dead, so is such a tool. anyway, it was dead years ago what with yearly or longer releases.