UMSKT/writeups
1
0
Fork 0
mirror of https://github.com/UMSKT/writeups.git synced 2026-07-03 20:54:20 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update BINK.md

Browse Source
This commit is contained in:
WitherOrNot 2026-05-08 01:35:40 -04:00 committed by GitHub
parent 356e14a8da
commit 5be7a9f853
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 23 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
BINK.md
View File

@ -343,14 +343,18 @@ For all NT 5 Windows versions except Server 2003 R2, this table has the followin
The license types are as follows:
| Type | Meaning |
|------|--------------------------------------------------|
| 1 | Volume (VLK) |
| 2 | Retail/OEM Certificate of Authenticity (OEM-COA) |
| 3 | Evaluation |
| 4 | Tablet |
| 5 | OEM System Locked Pre-Installation (OEM-SLP) |
| 6 | Embedded |
| Type | Meaning |
|------|---------------------------------------------------------------|
| 1 | Volume (VLK) |
| 2 | Retail/OEM Certificate of Authenticity (OEM-COA) <sup>1</sup> |
| 3 | Evaluation |
| 4 | MSDN<sup>2</sup> |
| 5 | OEM System Locked Pre-Installation (OEM-SLP) |
| 6 | Embedded |
<sup>1</sup> For even-numbered BINKs, this ID corresponds to retail. For odd-numbered BINKs, this ID corresponds to OEM-COA.
<sup>2</sup> Not 100% confirmed, but seems most likely due to all keys of this type having a 60-day activation grace period, which is consistent with [MS documentation](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-xp/bb457096(v=technet.10)).
For the Evaluation Period and Activation Grace Period values, the value `2147483647` is used to indicate `N/A`.
@ -362,6 +366,17 @@ When attempting to activate, a non-functional OOBE Activation popup will appear,
This strange behavior is most likely a bug triggered by a lack of error handling in DPCDLL's channel ID validation code.
Possibly as a result of this behavior, Microsoft added a secondary check to PIDGEN.DLL in Server 2003 RTM, making sure that keys used during setup match a more limited range of product IDs. In early versions, this check simply searches a list of product IDs, but by Server 2003 SP1, a standardized table format was created. This table is also included in Windows XP K/KN and Windows XP Professional x64.
| Offset | Value |
|----------|------------------------------------------------------|
| `0x0000` | Blocked flag |
| `0x0001` | Padding |
| `0x0002` | BINK ID |
| `0x0004` | Minimum Product ID (Channel ID + 1000000 * Sequence) |
| `0x0008` | Maximum Product ID |
| `0x000C` | Unknown, probably flags of some kind |
## Literature
I will add more decent reads into the bibliography in later releases.