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? ***latest version link added*** - Cosmetic Bugfixes New Options - Centre on resize : changes the way window is positioned when resizing - Search Only : when importing BINK if this option is checked keyset file will not be created/overwritten. Use only if you want to scan a file to find out if there is BINK data in it. Spoiler: English Version Code: File: EllipticCurveTool.exe CRC-32: 632dc5e0 MD4: 9f7bd14f04fe1b36e4d97af8b5256ee3 MD5: 3665210ab5a95d219fb367157cc2e81d SHA-1: f966d8808cd66ea7c4e28b1704715f8dbca579bf Code: File: EllipticCurveTool_250416_1605.7z CRC-32: 8c013c0e MD4: 38eaf67371490bf66b09a80c2a117c5d MD5: cbd5df623f02623dff000d713ce7163e SHA-1: 54d0778013a178b0e498d1173cf214c26e0a8571 pw: U&cvXSjutZp68s%#GS2PkVm*e$ycwpdV Spoiler: Keysets Code: File: Baseline Keysets.7z CRC-32: 68919e83 MD4: dcbc896241a51bcf729f8e8113cee893 MD5: 5c1f06475495eac97ef763b89295bd23 SHA-1: fde532216ab5bffa1fdad80994c4ec3538313f82 Spoiler: MultiLang Version Code: File: EllipticCurveTool.exe CRC-32: 383cb81a MD4: 92caa8ae183022dc673af539771a7f3b MD5: 2aaa9c981eb7555bb3428af732f613b0 SHA-1: 26f98aa9e8f3eb459e08c05f67409ba062869b62 Code: File: EllipticCurveTool_multilang_250421_0429.7z CRC-32: ec733819 MD4: 28ab4e2c1716bf3a9846e4170a7e9a07 MD5: 768db65a52a7bddfd9192c363a9e47f7 SHA-1: c03f6acd6b7e19ee5f44736ec9573184eb0af528 pw: mdl.net
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 ;-)
so here is a version of the tool written in c++ so no more .NET framework. Basically has all the same options but it does seem to be able to generate deterministic keys a hell of a lot quicker than the .NET framework version. This version also uses user readable keyset files. ****download link expired****
Updated version ***link expired*** Added checks to ensure Curve Name only contains alphanumeric values Added checks to ensure Curve Parameters only contain valid characters 0-9 and A-F the file has been compressed and apparently can be flagged as virus!!!! false-positive
Small update ***link expired*** Found an issue where keyset PID min/max values were loading out of order.
and yet one more small update ***link expired*** fixed an issue with the path to pidgen files when validating product keys in a text file.
okay hopefully this should be the last bug fix update ***link expired*** app now updates the software list when adding or deleting keysets properly.
Small update: Found an issue where Product ID displayed incorrectly when decimal values are used. ***link expired***
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.