then this tool is not what you need. its basically the whole concept of the tool thats because once you have imported a pidgen.dll or mso.dll you will have thos keysets saved in the "Keysets\Baseline" folder. then you need to enter you "n" and "k" values, then use the "save keyset" button to resave the keyset with the "n" and "k" values. Then if you find a specific software that uses the BINK ID you can alter the Product ID minimum and maximum rages to suit the specific software. Then change the "Curve Name" to something appropriate for that software. then click "save keyset". now you will have a keyset file in the "Keysets\Software" folder. Use the "Base Line" option to change between the "BaseLine" and "Software" folders to populate the dropdown list to then generate keys. again, then this tool does not fit your needs.
So I have made a few changes, the most significant being a new checkbox called "As Retail". If this is checked then a formally OEM BINK ID will produce Product IDs in Retail format. It's for exceptions like Windows POSReady 2009 that use what is normally reserved as an OEM BINK ID as a Retail version. If you select this option and save your keyset the option will be saved in new ks2 file. As such the checkbox is only available when Base Line is not selected. For Base Line BINK ID 0x0D will still be considered OEM. Spoiler: checksum Code: File: EllipticCurveTool.exe CRC-32: 2f978356 MD4: 790564843c2afb8ef49810035b228072 MD5: 6880c4661cbc01c1f7dd0d437b352b96 SHA-1: 6dd0f7c549d0f7074cc76131888e93e356d6b9c5
just adding further to @Sajjo post. yes the tool works with pre 2010 office, once you have provided all required parameters.
An observation. 00045-140-169-918 It can be interpreted as: BID 2D - CID 140 - Sequence 169918 -> Windows XP Pro OEM - 55274-OEM-0014011-69918 Finding this on a (Ebay) Windows 98 OEM COA seems odd... coincidence? The date code February 2001 (part of the Part No.) would be in the ballpark for XP i guess...
The issue with the new dates is easy to explain, the latest I've seen is from 2003 on OEM versions for some specialized devices
I saw a copy of Win95 licensed in 2001 in a Czech car factory, which was used by factory assembly robots.
So... can we interpret as OEM HW with Windows XP in Q1-2001 with downgrade opsjon to Windows 98? Where else would 00045-140-169-918 come to play?
I just do it manually after i import mso.dll resources with "Import BINK" in Elliptic curve tool, then i take (from BINK ID42) curve value "p", change endianess and search with this string in mso.dll. Copy resource to a file (as binary) and your good to go. This is resource BID_0x42 Highlighted in color: Bink ID followed by curve "p" "a" "b" "Gx" "Gy" "Rx" "Ry" ("a" and "b" is not colored btw) Code: 42 00 00 00 E4 01 00 00 09 00 00 00 90 7C DB 12 C4 7C 31 01 10 00 00 00 1F 00 00 00 3E 00 00 00 0A 00 00 00 14 00 00 00 59 3B C2 63 D0 A9 10 E9 06 79 32 84 65 DC 38 84 A5 88 E1 A2 36 BE 11 7B BB A3 84 B5 B9 F6 5F 93 F3 B2 82 CD 7F 1B BE 92 8B 7A B2 42 EF FC A7 A5 7C 6A 3E A5 08 1B 72 E0 58 40 A9 FC 7D F5 1F F7 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2D 9E A4 AF 8C E1 48 FA 8B 72 A4 C9 0C C4 A0 7F DE B6 0C 94 36 8B 60 AA BE 3F 25 79 45 FA 29 BC 83 9B 63 E7 7C 4E 15 71 D6 10 EA 07 21 6F 65 5B B4 3A 93 95 70 6A C5 07 6D ED ED 1D EB 7B 3F DE 8D 2D 39 D8 65 2B C1 19 9C E2 27 BD D5 C2 3D 55 1B 53 70 FF 0A 58 DF AB 5D BD 43 46 DA 6E 12 0E EA 5C 3F 3C 97 8E F9 25 3D 34 D3 F6 8F F3 A2 35 B8 F3 44 DC C3 69 9C 5E 71 EA 26 35 A1 DA 54 15 25 7D 4C 6C 61 15 21 DF 53 FD 1D 41 B2 93 67 FD C5 8F 49 68 4E FC C6 81 A1 1C AA B2 C9 FD 21 F1 22 21 AD 8B C9 A9 83 31 78 7C 8C 3D 6B D3 90 AC B8 E1 99 94 7A 91 85 31 39 0F AA 60 7D C0 8B B2 EA FC D4 26 46 29 8C FE 9B 83 92 BB 73 DE B9 C6 D3 52 0A 9F 25 C1 78 3B 40 CF CA 0B 52 60 F4 ED 96 87 D0 D5 C1 45 F4 27 8B FF 63 8B BE 92 69 DA 24 FB 61 AA 9E 00 87 1A D0 95 8E A4 E1 4B 0B B8 Resource starts with Bink ID and ends with curve "Ry" See resource binary, remove suffix ".txt"
It says beta1, is it same as rtm? What is k of it I need office 2007 (vlk) bink value. I deleted sagemath also need sagemath output or k value too.
No. -> #188 It's the same procedure, only difference is a different way to create the resource binary, larger curve parameters and longer computation time (depending on your hw setup) Then you need a different BINK set - I will pm you *.ks2 files for Office 2007 later. I guess you didn't need it any more then...
For completeness we are looking for missing BINK's. Green are known, red is missing. Resource files and a reference to source files are very much appreciated. 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF E0 E1 E2 E3 E4 E5 E6 E7 E8 E9 EA EB EC ED EE EF F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB FC FD FE FF