Chkpids I use all the time - both x86 and x64 (i noticed i've become a hoarder of pigen.dll's... ) But I can not at all manage to find out how this works in this tool Could you, sort of, "hold my hand and walk me over"?
Well it basically comes down to this. It's a catch 22. To check 64 bit pidgen.dll files you need a 64 bit tool. Visual Studio 2005 can compile a 64 bit tool but the 32 bit tool will not work with legacy operating systems. Visual Studio 6 can compile a 32 bit tool that works with legacy operating systems but has not 64 bit support. To get around the messiness of having 32 bit and 64 bit versions of the tool I cheated and hacked/edited 32 bit pidgen files with the 64 bit BINK data in them so I can check product keys for 64 bit products in my 32 bit program. Basically if you have a pidgen file that you would like to check a product key against to see if it matches then you need to create a SubFolder called "PIDGEN" in the tools main folder and place the pidgen file in there. you can have as many different pidgen files in there as you want but obviously they cannot all be named "pidgen.dll" so you have to rename them using the format "PIDGEN-" followed by whatever you wish to call it so for Windows XP Pro for example rename the pidgen to "PIDGEN-Windows XP Pro.dll" then when you check a Windows XP Pro product key it should return success for that pidgen.dll. It's basically the same concept as CHKPIDS just in a GUI
https://forums.mydigitallife.net/posts/1820751 Source https://forums.mydigitallife.net/threads/c-vb-net-xp-pid-checker-conversion-help.32044/ X64 https://forums.mydigitallife.net/posts/1553700
That new one not works on my windows 7. i have to used old one. thats why i could not see maybe. I run that at my second operating system windows 10 but new gui look not good as old gui. i will check new program.
Can you run earlier versions of the tool in 7? Can't you just run it in a Windows 7 VM - English, and try to see any difference why it's not working for you? Binary is compressed with Petite far as i know, dunno if could become an issue in your case.
So here is the latest version I have. It's been a while so I'm not sure if much has changed. I remember I had an issue with pidgen files not unloading after validation. ***link removed***
Hiya @pottzman Not sure what exactly to focus on so it may not give justice but here's some of my feedback. I run the new one and previous in same folder. Spoiler 1. Validating x64 keys works not, x86 keys works perfect. No change from previous - no issues observed so far. 2. Clicking Validate on the new one with no input and tool stop working, have to restart. This is new from the previous version. 3. Import from attached pidgen gives only one of to valid resources, no change from previous. No other changes as i can find so far, and still work flawless on Win9x OS too. I'll update if I find goodies.
I have fixed issues 2 & 3. Issue 1 will remain as visual studio 6 cannot compile 64 bit binaries. I get around this by replacing the original 32 bit BINK data with 64 bit BINK data in a 32 bit pidgen.dll to get it to work.
Good morning and thank you Nice to see issue 2. and 3. fixed. I can see the challenge and solution on 1. Just thinking loud: is it possible to combine chkpids x86 and x64 binary in same folder as pidgen's and call from EllipticCurveTool.exe? Adding 2 check boxes where users are forced to select either x86 or x64? I made manually ks2 for Office 2003 Student and Teacher - bink ID 0x70 Works as expected but is that possible to do same way as we do with pidgen files? And would that be possible to validate the same way? Spoiler: BINK ID70.ks2 Code: [Settings] CurveName=BINK ID70 [Parameters] binkID=70 p=D95AF4C42B9B71E583110389F49941D26AB01F766D30C709E995D8C6209FBA573D007AAB7163B6E3585525C5F28DC0C8169052DFD14700C7EAE050DEDBF2AF51 a=1 b=0 Gx=66E78DD5F133107B497ED5CC37B08CA11CF1312332EE30E594D4F741F5678EB798492AA9F103B2A5BE1F11D126A943338E38485806CB6F057D0BFD9A08A40A89 Gy=97EA67952E4460DA87FEA5787A6D2BE7C061358627A459008770A55C244D54F76E9505FC82D7D3E820CCC458A58CA9F80D40657E8F87E158107D7BD29F2D3B87 Rx=59A7AB21BAB3546A1A478C7A2F3C316F4E93D6ED8D62C153DB549FB25201F3AF88713AB8159B423AB2749CA7A6B8233F7CA875C34DB7FA83D2BEEAF5C5D2ADC5 Ry=78F5AA72BC3B06482AE5E7E652B12AB5A281057A572443BDA936737F219EBE8CCDCEE7D72AAFD7911FB05F6FE99A87F2B2F4D6AF2BB2807A532EB1BA0881C83C n=4A1B25827D1EA955 k=05812745F1D8FFDD ValidRanges=001 ChannelIDMin001=000 ChannelIDMax001=999 PidIDMin001=000000 PidIDMax001=999999
@pottzman Small notification, if PIDGEN folder is empty tool freeze. Can not cancel. And to others - don't change filename from mso to pidgen like I did Spoiler
@Sajjo You can’t officially. The same way I manually edited 32 bit pidgen files to replace BINK data with 64 bit version, I manually replaced BINK data with BINK data found in mso.dll