as BINK ID 0x0D is decimal value 13 which is odd, then this BINK will be used for OEM product keys, hence the OEM style Product ID
@un user Good morning, hope you have a fantastic day I could'nt agree more with you. I may have tested outside of range boundaries but when I create a key with valid parameters i can still get something not valid. -> #96 The tool and it's usage in general (umskt included) is'nt that well documented so there is room for errors as well, spesific to users that never used this before. Kind regards
@pottzman Good morning Imported resource from pidgen as instructed by EllipCurveTool.exe Only added (manually) the "n" and "k" value. See attached ks2
can you explain a little how to use bink ıd's when generating keys. which id we should select and why?
you should know which bink id to use for what software when you import your pidgen.dll file. For example, if you have a Windows XP Home CD, when you use the “import” button and choose the “pidgen.dll” file from your Windows XP Home CD it will find and BINK data in the file and tell you which BINK ID is in that pidgen.dll file. that means that only those BINK IDs found will work for Windows XP Home. most product use a unique BINK ID with some exceptions
I know that. But what is the difference if there is 4 binks in same pidgen.dll? Which one need to select and why if there is 4 binks in same pidgen.dll
are u referring to server 2003? if yes. because 2 binks are for pre “R2” and 2 for post”R2” versions of server 2003
I compared rtm binks and sp2 r2 binks. Rtm has more binks then r2. Rtm has 6 binks (also vlk binks in it). Your theory is false. Also i am curios why vlk pidgen.dll has oem bink in it. Vlk pidgen will not accept oem keys. Maybe pidgen.dll file but setupp.ini has 270 in it.
Good morning. 1. What's the purpose with "Prefix" box? 2. How is Key scan suppose to work? All i get is Code: ERROR: No PIDGEN.DLL files found. Copy them to the PIDGEN folder and rename them to label what they are. eg) Rename the Windows XP "pidgen.dll" to "PIDGEN-Windows XP Pro.dll" I start to feel like Edison and his 2000 ways to not make a lightbulb.
After you wrote i discovered i. You will give a key and keyscan will find which operating system it belongs to. It is same as CHKPIDS i guess. Find and read its how too. I hope it works on x64 keys too. "Pidgen-" syntax only works on x86 keys