222
this post was submitted on 22 Jan 2024
222 points (100.0% liked)
Technology
37757 readers
572 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
As somebody that's been working on computer hardware since the early-to-mid 90s, installing the drivers before connecting the printer was the norm. It was actually the norm for most peripherals. Just be glad you didn't have to do manual irq assignment. Hell, that is probabaly the issue, is that the driver installer borked the irq assignment when the device already had a handshake agreement with the hardware.
I digress though, this shouldn't have been the pattern for a modern printer in 2007, when PnP had been standard for several years at that point.
I still have a early 2000s (I think that's the era anyway) LaserJet 2200dn and it's done nothing of that sort, even on my spare actual Windows XP laptop. Insanity that their more consumer brand printers had those problems by '07