Would there be any interest in a program that can use the BINK data in pidgen files to calculate product keys? the program on its own will not do anything. the user would need to "calculate" certain values that are missing before the program can function?
YES. Also, if some "certain" values can be stored in *.txt/*.xml in order to test "calculated" values obtained from multiple BINK would be awesome. I mean, to store p, gx, gy, pubx, puby and priv for each BINK, in order to calculate for that particular case.
yes that is how the program works. each set of BINK values are stored in its own file that is selectable from a drop down menu.
I have seen your software and it looks great! I would like to have some keyset for testing. Please PM ;-)
It's nice to see an product key generator for Windows XP. But there're two things: 1. When I import a pidgen.dll file, it doesn't extract or load the n and k values which is a problem. When I open the .ks2 files, then these two values are empty. This won't let me generate a key. 2. You should add a feature. This feature is to importing setupp.ini files. With that feature we can see if the generated product key is Retail or Volume Licensing. This program already has OEM key option. Retail or Volume Licensing option would be nice too.
1. The pidgen.dll file does not contain the values for "n" and "k". you need to calculate these values yourself and then paste the values into program and re-save the "ks2" file. It will now save the values for "n" and "k" and be able to generate a key. 2. If you know where your pidgen.dll file originated from then you already know whether it is Retail, OEM or Volume licensing. Just make sure to have one of those in your "curve name" eg) Windows ME Retail and it will make it very simple.
1. The problem is, I don't know how to calculate them. And I tried to find values for "n" and "k". While, I found the "n" value on the internet, "k" still remains empty. Also, I have looked into other generator's source code, there was no mention to "k" there too. 2. Wait, Isn't OEM, Retail or Volume Licensing determined by last three digits of pid value in setupp.ini? Well, it's impossible know that from pidgen.dll. Because pidgen.dll files from both Retail and Volume ISOs are identical. OEM - OEM 270 - Volume 335 (And maybe possibly 000) - Retail.