- Joined
- Oct 9, 2007
- Messages
- 47,166 (7.56/day)
- Location
- Hyderabad, India
System Name | RBMK-1000 |
---|---|
Processor | AMD Ryzen 7 5700G |
Motherboard | ASUS ROG Strix B450-E Gaming |
Cooling | DeepCool Gammax L240 V2 |
Memory | 2x 8GB G.Skill Sniper X |
Video Card(s) | Palit GeForce RTX 2080 SUPER GameRock |
Storage | Western Digital Black NVMe 512GB |
Display(s) | BenQ 1440p 60 Hz 27-inch |
Case | Corsair Carbide 100R |
Audio Device(s) | ASUS SupremeFX S1220A |
Power Supply | Cooler Master MWE Gold 650W |
Mouse | ASUS ROG Strix Impact |
Keyboard | Gamdias Hermes E2 |
Software | Windows 11 Pro |
A legal storm is brewing for HP, one of the world's largest manufacturers of inkjet printers. Users around the world are adding to empirical evidence that HP programmed its printers to not play well with third-party ink cartridges. Apparently, HP Inkjet printers and PSCs (AIOs) are programmed to malfunction when a non-HP made ink cartridge is used, on an arbitrary date of 13/09.
The printers are programmed to recognize that a non-HP cartridge is installed, and tell the driver to report a "damaged cartridge" error to the end user. HP has been responding to individual support calls from end-users so far, that the problem is caused by using third-party cartridges. The company recently redacted this statement, replying that a firmware bug is causing this error. Users on online boards were quick to retort that printers with no Internet connection, and no scope for OTA firmware updates, too are exhibiting this behavior. The only explanation that make sense is that HP programmed this date to deliberately make third-party cartridges malfunction, and drive up sales of its own brand cartridges.
View at TechPowerUp Main Site
The printers are programmed to recognize that a non-HP cartridge is installed, and tell the driver to report a "damaged cartridge" error to the end user. HP has been responding to individual support calls from end-users so far, that the problem is caused by using third-party cartridges. The company recently redacted this statement, replying that a firmware bug is causing this error. Users on online boards were quick to retort that printers with no Internet connection, and no scope for OTA firmware updates, too are exhibiting this behavior. The only explanation that make sense is that HP programmed this date to deliberately make third-party cartridges malfunction, and drive up sales of its own brand cartridges.
View at TechPowerUp Main Site