🚀 go-pugleaf

does the diskid32 support windows xp?

"Vladimir Stefanovic" <spam@not.needed> wrote in message
news:41565a41@newsgroups.borland.com...
> zhan wei ming wrote in message
> > [...] Currently the protect mechanism is: when the user
> > first run the program, it read the disk id [...]
>
> Do you read the Volume disk id ( GetVolumeInformation() ) or
> you are reading hardware hd serial number?
>
> If you are using GetVolumeInformation() then there are many tools
> to change the ID like 'volumeid.exe'. So this is no reliable at all.
> Also when the user re-formats the disk your mechanism of licensing
> is down.
>
> If you want to learn how to read the hardware hd serial then look at
> www.winsim.com/diskid32/diskid32.html
>
> This is much more reliable but when the user changes the HD which is
> common nowadays your mechanism of licensing is down again.
>
> > Question is that I am afraid the program can be cracked. for example
> > heard hat there is a tool to make the ID of two disks the same. then
> > the protect machanism will be no use.
>
> Yes, read above. Be sure that crackers will generally not dig of
> what you are checking. It's much easier for them to find code
> constructions like this...
>
> if ( IsSerialNumberValidForThisMachine() == false )
>    Terminate();
>
> ... and to reverse the logic ( false -> true ).
>
>
> > Anyone knows a better way?
>
> You can also check for Network card IDs. There are couple of articles
> on Borland developers network of how to read this. Network cards
> generaly never removes or replaces from machine so it's also a
> solution.
> The bad information is that I heared (but not checked) that there are
> some
> NIC cards (Chinesse made) whose NIC ID can be changed from code ;(
>
> Hardlocks are the best solution among those two I mentioned.
>
> There are also some other solutions which some companies can do for
> you,
> but that's another story.
>
>
>
> Best regards,
> Vladimir Stefanovic
>
>
>