Yeah, it was a buttload of resources popping up in that one but some are missing as well. I checked through various editions and the mso file seems to be all in one. And mso office xp seems correct as well
latest version works ok under windows 7. I replaced x64 bink resources and put inside x86 pidgen.dll file with resource hacker replace option. It not works. How to replace x64 binks and put inside x86 pidgen.dll files? Need extra pechecksum fix? win98se works to generate but win98 not. what can be reason. how to extract bink from mso.dll?
just 1 more, it can't hurt added further checks to ensure it is real BINK data. mso from office 2007 was incorrectly identifying BINK data ***link removed***
no i mean take 1 x 64 bit pidgen file and copy its BINK data into a 32 bit pidgen replacing the 32 bit BINK data. So copy the BINK data from Windows Server 2003 x64 Standard pidgen.dll and paste it into the Windows Server 2003 x86 Standard pidgen.dll. There is more to it than that i'm afraid as Windows Server 2003 version pidgen.dll files also contain a table of valid Product ID ranges aswell. these also need to be replaced with the 64 bit data otherwise the pidgen will validate/invalidate wrong product keys
Thx. I think i have found my mistake. I copied server binks into xp pidgen. Maybe should do that server x64 to server x86 pidgen. Also if combining pids work it will be awesome. Do not know how will find id ranges. Will look.
from the Windows Server 2003 R2 Standard VL pidgen. BINK data in Red. Actually the BINK data starts from the BINK ID "5A" not where the B.I.N.K is. List of blacklisted Product IDs in Blue List of Valid Product ID ranges in Green this is the data that needs to be replaced with the respective data found in a 64 bit pidgen file. you can not increase the number of BINK data from what is originally there so if the original pidgen only has 2 BINKs then you can only paste 2 64 bit BINKs.
What changed? Both works and bink resources are identical in both, 0x02 and 0x03 Same way you import from pidgen.dll
Nicely done Bink's MSO Office 2002/XP Code: 0x20 0x21 0x22 0x23 0x24 0x25 MSO Office 2003 Code: 0x6e 0x6f 0x70 0x71 0x72 0x73 0x74 0x75 MSO Office 2007 Code: 0x7c 0x7d 0x7e 0x7f 0x74 0x75 0x76 0x77 0x80 0x81 0x82 0x83 0x84 0x85 0x86 0x87 0x88 0x89 0x7c 0x7d 0x76 0x77 0x85 0x86 0x87 atm unknown Feels very stable so far
How to extract binary binks for office products with resourcehacker or hexworkshop? Need binary binks to calculate n,k values. What are .ks2 files used for? They are only used for EllipticCurveTool.exe. Not usefull for me, is it?
Yes and no, i have tested keys for: channel 620 - gave me permanent activation channel 623 - gave me evaluation notification Not tested channel 621 and 622 You want me to test these channel's?