Ok, I know where the problem is. The Hardware Key generator module takes the HD and MAC ids, converts each to int and then back to string before appending one to the end of the other. This results in a huge int which much bigger than SM can handle. We use 32 bit ints and these only go up to 2147483647. If you go inside the Hash(x) module then inside the Hash1(x) module you'll see that when this String containing the huge int is converted to an int the best SM can do is give it a value of 2147483647. This is why you get the same Hardware key as Darren.
It's only by way of luck that I don't get the same key as you too. The De-Inverser module seems to add a little differentiation in my case. I'm not sure why though.
Might be worth going back to the author to let him know.
AngularMomentum wrote:I rather have this system working then yet another discussion on copy protection.
TomC wrote:AngularMomentum wrote:I rather have this system working then yet another discussion on copy protection.
Right. I'm a bit buried in work right now, but this Thursday is a public holiday here in Germanyland,
so I'll have a look.
Of course malc is right, there IS a integer overflow. No biggie to solve.
Thanks for the feedback.
PS: if we'd have a green code module this whole mess of a schematic would be about 10 lines
of code. Maybe 11...
2.) If you have more than one (even virtual) Network card in your PC the Mac mod component outputs them with a comma separated (I hope the 1st Hardware one is also always the first in the output-string) ...please confirm!
(So if the user add or remove/replace one of his NW-Cards virtual or not U have 2 generate a new serial 4 him again)
AngularMomentum wrote:What holiday is that then? I love Germany. I am in Aachen on Friday, we visit Germany regularly since we have a car...at least once every two weeks.
Users browsing this forum: No registered users and 0 guests