I just about learned something here.
So the makers of better installation ISOs are not enigma code-breakers; or slic inserters. They merely acquired installation DVDs of every OEM brand, copied the "xxxxx.xrm-ms" files and incorporated them into their installation media, then modified the installation process to read the code in the BIOS, then see if there is a corresponding xxxxx.xrm-ms file, then proceed with the installation as if the installation .ISO came from that particular OEM.
(since there is no "gateway.xrm-ms" such DVD would not install pre-activated Win 7 on a Gateway laptop)
Perhaps a real enigma code-breaker could tell what the long alpha-numeric lines mean.
?xml version="1.0" encoding="utf-8"?>
<r:license xmlns:r="urn:mpeg:mpeg21:2003:01-REL-R-NS" licenseId="{36bb40b7-1790-4137-937d-6fdcab4f0608}" xmlns:sx="urn:mpeg:mpeg21:2003:01-REL-SX-NS"
xmlns:mx="urn:mpeg:mpeg21:2003:01-REL-MX-NS" xmlns:sl="http://www.microsoft.com/DRM/XrML2/SL/v2" xmlns:tm="http://www.microsoft.com/DRM/XrML2/TM/v2">
<r:title>OEM Certificate</r:title>
<r:grant>
<sl:binding>
<sl:data Algorithm="msft:rm/algorithm/bios/4.0">
kgAAAAAAAgBMRU5PVk8BAAEAaRZKn7FLOvuAIKqvxPk+wYBJ7mplJnIezb9fL5bWwAqS9Qa1ALI7KQLiTI3C8rxBd5xw8PMbCdJjWtyog/heyRWV+fr93AW3TWd/LbOEMyDh0Xk
qp2p30bYgKnZCxdXptkNAVUTDyTeZX0GXcPPR9gfsexopocHxkf1Ihm4+zss=
</sl:data>
</sl:binding>
<r:possessProperty/>
<sx:propertyUri definition="trustedOem"/>
</r:grant>
<r:issuer>
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
<SignedInfo>
<CanonicalizationMethod Algorithm="http://www.microsoft.com/xrml/lwc14n"/>
<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<Reference>
<Transforms>
<Transform Algorithm="urn:mpeg:mpeg21:2003:01-REL-R-NS:licenseTransform"/>
<Transform Algorithm="http://www.microsoft.com/xrml/lwc14n"/></Transforms>
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<DigestValue>/A8xsgOKXrGblQhnUX2SSdRgNy4=</DigestValue>
</Reference>
</SignedInfo>
<SignatureValue>
kuLkCnKyqITqBlnU61GvfScsbnvg/A6NI/OTQYJZla++WLQhCj9ogu+Pn4YYGAB3gfUy/bQmFKAS86n0SylBHPNNvFoXbn8k3ak3ndOaFaT+d+vs1vdTU6WWaOsZ6rD9xXSWoFDMj
DyueNJ6mUoTWGWYSVJZYOpk8UWnMaz4yH9UsjrQ5ifdvosgLmlKvoJc4mEntDfl56rluCsyP3t2WUp69OREDAuhXqE8mD6Ib3v4boMTrLZmHt2ldCZ3rZK/amtNjTItPPoXrFk6fNU9F0
W2qNX19yXpzrwpaKwKcQ7QKy0kUjRkyg7j7gTgfAdR/aHh/eunoDFuJIltETZG4A==
</SignatureValue>
<KeyInfo>
<KeyValue>
<RSAKeyValue>
<Modulus>
sotZn+w9juKPf7bMO9rNFriB+10v/t9bo/XWG+rzoDbw/uF4INZ5rGRIitiITY/bI4rANkv4Z5hG/8VxGMbqvqcaXJqnRFda7XAjgm1z9wkgX1R/d2tXLUUUQP0J1XuSbgzR89T/lpnc5q2C
dvy7Gv2pZvAzSeLOponXc8J3zOFr0IUXBGprXKnemVk1iJBFnyQGlWG3UoSpdlF0ichBQwPx/PgoTbcZsA7Gg62BGwPx/uDA3ZgwowrPlRwfLVAO6qE9xPJqRZdRFfPHbdQjp1YAq27
wc6cTz5sPSTB1pJ4L9MD+NpvHj2OMZV5+LJ+bxZbTqhPcrzCp7ckkyD7Hzw==
</Modulus>
<Exponent>AQAB</Exponent>
</RSAKeyValue>
</KeyValue>
</KeyInfo>
</Signature>
<r:details>
<r:timeOfIssue>2006-06-17T18:22:30Z</r:timeOfIssue>
</r:details>
</r:issuer>
<r:otherInfo xmlns:r="urn:mpeg:mpeg21:2003:01-REL-R-NS">
<tm:infoTables xmlns:tm="http://www.microsoft.com/DRM/XrML2/TM/v2">
<tm:infoList tag="#global">
<tm:infoStr name="applicationId">{55c92734-d682-4d71-983e-d6ec3f16059f}</tm:infoStr>
<tm:infoStr name="licenseCategory">msft:sl/PPD</tm:infoStr>
<tm:infoStr name="licenseType">msft:sl/OEMCERT</tm:infoStr>
<tm:infoStr name="licenseVersion">2.0</tm:infoStr>
<tm:infoStr name="licensorUrl">http://licensing.microsoft.com</tm:infoStr>
</tm:infoList>
</tm:infoTables>
</r:otherInfo>
</r:license>
This doesn't bring me any closer to finding out how and why a volume license Win 2003 .iso doesn't require activation.