I live in hope ...
... that I will survive long enough to see a straight 12 months with Microsoft screwing up systems by a poorly thought out or inadequately tested patch.
Microsoft has taken the increasingly normal step of releasing an out-of-band update to deal with the printer issue it introduced last week. "Microsoft identified an issue that affects Windows 10 devices which applied the March 2021 security update released March 9, 2021," explained the Windows giant, "and a resolution has been …
I've read this comment several times and can't quite make out if you missed a word or you're being sarcastic!
So, did you mean:
"You live in hope that you will survive long enough to see a straight 12 months with Microsoft screwing up systems by a poorly thought out or inadequately tested patch"
in which case, where have you been since... well, forever.
"You live in hope that you will survive long enough to see a straight 12 months with Microsoft [NOT] screwing up systems by a poorly thought out or inadequately tested patch"
In which case i think you'll probably see Satan scating to work well before that ever happens!
Come on, let's be realistic rather than simply trashing MS at the earliest opportunity. Exactly how many thousands of possible combinations of printer configurations, just to name one subsystem, does MS's OS support, exactly? And how are they *supposed* to test every reasonable system configuration in any "reasonable" amount of time? That LaserJet 3p you're still using (yes, toner is still available) have an issue? How would they know???
MS depends upon their system of beta testers to help weed out problems. But what happens when the circuit of beta testers do not have every configuration, ones that cover most of the major contingencies? You get this.
Figure out Microsoft can test every single possibility that their systems are currently used in, within a reasonable time frame for release, and then we can all stand on our high horses and complain about their incompetence.
Come on, let's be realistic rather than simply trashing MS at the earliest opportunity. Exactly how many thousands of possible combinations of printer configurations, just to name one subsystem, does MS's OS support, exactly?
Not when it's a BSOD. It's only a bloody printer driver. Sure, it needs to respond to interrupts and have some form of I/O so at the very lowest level it must run at a high privilege. But that stuff shouldn't have changed for years.
But then the need for printer drivers has never made sense to me. Given how much intelligence we can pack into a printer why does any OS need to do anything other than say 'here's the data, get on with it'?
Given how much intelligence we can pack into a printer why does any OS need to do anything other than say 'here's the data, get on with it'?
It means that the printer manufacturer can save $1 in making it and offload the hard work to a computer that has to have vast resources just to be able to run Microsoft Windows.
They need to build them cheaply in case they do not make their money back if the user does not buy their over priced ink.
Damn, I didn't think of that. Yeah it makes sense. Annoyingly.
I have two printers now. A laser printer that is almost never used (which is why I went laser for the long ink shelf life) and an inkjet that is used to print textures for my model making.
Printing to the laser opens HP eAdvantage. Printing to the Inket just goes straight to the queue. I can't be bothered to try and work out what's going on. Mind you trying to print anything with colour on the laser is a bad idea. For some reason it takes forever to prepare the document. I rarely do any printing other than the textures so for now I'm putting up with it :(
The era of daisy printers is over....
"why does any OS need to do anything other than say 'here's the data, get on with it'?"
Because the OS need to know what the printer can do, what its status is, and change the configuration as well when needed.
You can print with generic drivers - for example a PCL5 generic driver will print on a lot of printers supporting it - but any specific function of the printer won't be available.
If the printer does not support a generic printer language - a driver is still needed to generate whatever date the printer will understand. And no, you can't send a generic file format.
Come on, let's be realistic rather than simply trashing MS at the earliest opportunity.
I think the earliest opportunity was when MS moved the GDI into the kernel for NT 4.0 and it was trashed at the time. 25 years later and it's still there, you'd have thought someone at MS would have realised by now that the design is inherently flawed.
I thought Linux had done much the same thing for the same reason - performance.
Admittedly though it's been a long time since I've worried about the finer details of operating systems so I could well be misremembering. I can believe that MS moved too much of it into the Kernel though. Video is probably worth moving but printers don't need that kind of performance.
We had this issue in our office - with a Kyocera MFP driver.
It's all well and good Microsoft issuing a patch, but how in the hell are you supposed to run windows update to apply it? Our machines were crashing before login!
(Pro tip - safe mode, disable print spooler service, then run optional updates in normal mode)
>>Pro tip - safe mode
All well and good if you can get to safe mode without booting Windows 10 in the first place (I'm looking at you 'Secure Boot'). Oh wait, if you reset/power off the machine 3 times as it is doing the whirly icon it detects there is something wrong and lets you get a little further - which of course assumes you get a chance to see the whirly icon.
Once upon a time there was perfectly good way to get at safemode, which didn't rely on you spamming the power button, but it was removed as an improvement. Bring back my f8!
Windows seems predicated on the (misplaced) belief that it won't break before you can log in... shame the people who dream up these things don't actually live in the real world(tm).
Personally this is why I tend to run Linux myself. Not that things don't break, but so that I can actually reach under the hood and resolve the problems when things inevitably do break! (Even just the ability to chroot into an existing OS install from a live USB/DVD/etc session, that alone makes a huge difference in how easy it is to resolve serious issues.)
The design of Linux is such that its effectively impossible to produce the kinds of architectural SNAFUs that appear to plague Windows. Obviously anything can be programmed to fail but the kind of logical Whack-a-Mole we're used to from Redmond should never happen in a properly archtected and partitioned operating system.
Welcome to the Brave New World of software development, where uneducated managers see "agile" as an excuse not to bother with testing (because deployment delays wouldn't be "agile") and believe they can rapidly fix any problems later (because that's how "agile" works, right?).
They see agile development as a way to cut short term costs, release sooner / more often, without understanding anything about what agile really is, and without caring what repeated shitty releases does to their reputation.
Agile was never meant to be this way.
Agile has become a set of procedures not a philosophy. Agile the philosophy makes sense. All those involved have a say during the development of a product. The development is steered by a group of stake holders so issues can be addressed and caught early while everything is relatively fresh on everyone's minds. As a philosophy, you have formal and informal meetings to hammer out details so the various groups can move forward. It is not about being faster a goal but making sure the end product is suitable for the users when it is released. It may be faster because of the continuous discussions going on during development reduces rework and ensures more timely feedback as the project develops.
Agile the Procedure is more focused on following a set of procedures such as 2 week sprints, 'scrums', 'stand up meetings', etc. These procedures often do not fit the requirements of the project as you are paying more attention to a procedure than the intent of the procedures. BTW I think the idiot who decided to use the term 'scrum' deserve a special place in Hell for their complete misunderstanding what a rugby scrum is.
"MS has turned Windows into a permanent beta software which continue to use its users as testers."
Everyone here (and elsewhere) saw this coming when they announced updates would be pushed to non commercial users. It was abundantly commented here.
So, now, we are there:
- no more f***ing QA dept
- things and interface that have never changed for years break with 1 update out of 4
- then fixes are coming in full reactive mode
Except on my gaming machine, I use WIN10 in a VM, with a handful set of snapshots every time an update seem to work.
> Does the same bug/patch/KBxxxxx also cause a white band to be printed over bitmap prints from paint.net when using the "type 3" printer-drivers?
Ah, the "White Print of Death" (WPOD). Fortunately only a problem with the white-ink cartridge you put at the back of the computer desk drawer...
Sadly, folk are so used to Microsoft failing, that they accept it. There are avenues for compensation.
There is no reason why you shouldn't get a payout from business insurance, from a small claims court, or even from a more formal court environment, if this sort of thing costs you money.
A product has to be fit for purpose. MS have a history of upgrade failures. In such a context, not offering a simple, user-friendly safe mode, roll back option and selective blocking of duff updates in an OS amounts to a design flaw. No reputable OS designer would exclude such options. Whether MS behave as they do through arrogance, maliciousness, government demands, incompetence or laziness, it is difficult to say.
I thought that W10 users could at least delay updates, allowing someone else to be the crash test dummy.
If W10 cannot be used without an internet connection (which would prevent an update) - I would also consider that to be a design flaw.
Japan has a charge of 'interfering with business'. It is a catch-all multi-purpose charge used for all sorts of things. This is an obvious candidate for that. If a Japanese company lost money from a failed MS update, my Yen would be on MS being found guilty of such a charge and ordered to pay compensation.
There is a real danger in persistently allowing companies to get away with stuff like this.
Using replacement firmware in a router, it should be possible to allow W10 to authenticate with a MS server, but break any lengthy download that was not specifically user-authorised (or attenuate the download speed to 300 baud). So W10 would not be able to update until you allowed it to, having examined online reports to see if the update was likely to damage your system. Blocking MS and spoofing basic authentication may be more complicated. If W10 was fit for purpose, we would not have to consider such stuff.
Aside from that, always have a W7 machine handy as a back up. I consider W10 to be inherently worse than W7 for the control it takes away from users, to such an extent that it would be worth paying money to secure a W7 environment or just use W7 internally, with Linux used for anything requiring online activity, air-gapping the two.
I'm gonna go with arrogance and incompetence. Simply they gained what is pretty much a monopoly then stopped giving a shit, persuing ever greater profits at the cost of their reputation and of their customers' sanity.
It's not about quality products any more. It's about feeding today's users' insatiable need for new shiny things every few months, rather than focussing on a solid, reliable and robust OS.
Reliability is expensive, hard and slow. New shiny is cheap, easy and quick.
> There is no reason why you shouldn't get a payout from business insurance, from a small claims court, or even from a more formal court environment, if this sort of thing costs you money.
And Microsoft will bring up a fresh copy of their EULA, which you unknowingly agreed to when you first logged in to Windows 10/8/7, and which says that Microsoft makes no guarantees of any kind that their crap works, or that it doesn't crash, or that it doesn't make you lose money, or business, or anything else.
In other words, the EULA is a binding contract whereby you agreed to play with a bomb.
Biting the hand that feeds IT © 1998–2021