UHB-IF: Difference between revisions

From EMF Badge
Jump to navigation Jump to search
(Created page with "The Unnecessary Hexpansion Bureaucracy Implementers Forum (UHB-IF) exists to implement unnecessary hexpansion bureaucracy. The only way to obtain a Vendor ID to use with hexp...")
 
No edit summary
Line 3: Line 3:
The only way to obtain a Vendor ID to use with hexpansion EEPROMs is via the UHB-IF. You will need a vendor ID to make a valid hexpansion EEPROM header.
The only way to obtain a Vendor ID to use with hexpansion EEPROMs is via the UHB-IF. You will need a vendor ID to make a valid hexpansion EEPROM header.
UHB-IF makes sure that Vendor IDs used by hexpansions are inconvenient to obtain.
UHB-IF makes sure that Vendor IDs used by hexpansions are inconvenient to obtain.
[[UHB-IF/Issued IDs]]


In defiance of the UHB-IF, rebel hackers have homesteaded on some vendor IDs. They are linked below:
In defiance of the UHB-IF, rebel hackers have homesteaded on some vendor IDs. They are linked below:

Revision as of 19:01, 25 May 2024

The Unnecessary Hexpansion Bureaucracy Implementers Forum (UHB-IF) exists to implement unnecessary hexpansion bureaucracy.

The only way to obtain a Vendor ID to use with hexpansion EEPROMs is via the UHB-IF. You will need a vendor ID to make a valid hexpansion EEPROM header. UHB-IF makes sure that Vendor IDs used by hexpansions are inconvenient to obtain.

UHB-IF/Issued IDs


In defiance of the UHB-IF, rebel hackers have homesteaded on some vendor IDs. They are linked below:

UHB-IF/Uncontrolled IDs

The UHB-IF does not approve of unbureaucratic mechanisms like this, but is powerless to do anything about them.