chillinn
Flashlight Enthusiast
Inkjet? They're all disposable. Ironically, any 20-30yo laser printer of any brand with an HP engine are desired because they don't quit, so there's still a used market for them.
I've got an old LaserJet 4 taking up space that won't feed paper correctly if anyone wants to try their hand at printer repair...Inkjet? They're all disposable. Ironically, any 20-30yo laser printer of any brand with an HP engine are desired because they don't quit, so there's still a used market for them.
I think it was the late 80's when I bought a HP Laser jet 2 or 3. I bought it on the recommendation that it was extremely reliable. IIRC it cost about $2000. I was only on my second toner cartridge, when it started printing a vertical line through everthing it printed. I called in a tech, who charged me $350 to tell me that the drum was scratched and needed to be replaced. Finally, HP agreed to do the repair for free, but I had to deliver it and pick it up about 40 miles away.I've got an old LaserJet 4 taking up space that won't feed paper correctly if anyone wants to try their hand at printer repair...
Nope, but the shell in W11 is crippled....I haven't tried a Windows 11 system yet. Has the file manager been improved over Windows 10?
Well, if hiding some popular items deep into menus and taking away some popular stuff like the ribbon is an improvement? Then yeah.I haven't tried a Windows 11 system yet. Has the file manager been improved over Windows 10?
As a former IT Data Center Mgr. for CalFed Bank I can attest to that regarding all software.Nice to see that Windows users, at least, have learned, perhaps through previous trials by fire, that mindlessly upgrading is a really bad idea.
I'd add end of support to that list - when your vendor will no longer support a version of their application, ancillary software, the server OS, etc.There's only a few rational reasons to upgrade any software:
- desired features
- bug fixes
- security patches
This is largely how it works in the enterprise space. Upgrades are not undertaken without purpose because they're risky, time-consuming, often halting affairs as problems are revealed then reported internally and externally awaiting resolution. Although in a good lab environment the spectrum of behaviors can be observed in days or weeks rather than months.The way to do it is to have two separate systems, a production machine where a fix is never, ever attempted if nothing is broken, and a development machine that works as a laboratory to determine what if anything breaks when any changes are made. Only after months of observing and testing changes on a development system, only when completely satisfied that production will not be broken by them, would it then be applied to production.
And although this is the long established best practice, the development/test environment can't always fully mirror production. External interfaces, unanticipated user peak volumes, undocumented programmer mods, etc., can derail even the best parallel testing. Trust me I've been there.The way to do it is to have two separate systems, a production machine where a fix is never, ever attempted if nothing is broken, and a development machine that works as a laboratory to determine what if anything breaks when any changes are made. Only after months of observing and testing changes on a development system, only when completely satisfied that production will not be broken by them, would it then be applied to production.
I'd add end of support to that list - when your vendor will no longer support a version of their application, ancillary software, the server OS, etc.
Although in a good lab environment the spectrum of behaviors can be observed in days or weeks rather than months.