|
Windows 10, it's a wonderful thing
In article emailer.net Fritz Wuehler fritz@spamexpire- 201711.rodent.frell.theremailer.net wrote: Windows Update borks elderly printers in typical Patch https://www.theregister.co.uk//2017/...ed_my_printer/ It's not Microsoft's responsibility to compensate for improperly written drivers from Epson. |
Windows 10, it's a wonderful thing
In article emailer.net Fritz Wuehler fritz@spamexpire- 201711.rodent.frell.theremailer.net wrote: Windows Update borks elderly printers in typical Patch https://www.theregister.co.uk//2017/...ed_my_printer/ It's not Microsoft's responsibility to compensate for improperly written drivers from Epson. Interesting comment. Then why did MS apparently compensate in the past? Companies cannot second guess what MS is going to do. If MS wants to continue to be a viable OS, then they need to see to it that they don't break things with advancements. Passing a alleged 'improperly written drivers from Epson' is not a valid argument. You have no idea if it is a driver problem. Since the drivers worked for years up to now, I rather assume that it is an improperly written MS patch. |
Windows 10, it's a wonderful thing
In article
Nomen Nescio wrote: In article emailer.net Fritz Wuehler fritz@spamexpire- 201711.rodent.frell.theremailer.net wrote: Windows Update borks elderly printers in typical Patch https://www.theregister.co.uk//2017/...ed_my_printer/ It's not Microsoft's responsibility to compensate for improperly written drivers from Epson. Interesting comment. Then why did MS apparently compensate in the past? Companies cannot second guess what MS is going to do. If MS wants to continue to be a viable OS, then they need to see to it that they don't break things with advancements. point out when m$ did this. cite. Passing a alleged 'improperly written drivers from Epson' is not a valid argument. You have no idea if it is a driver problem. Since the drivers worked for years up to now, I rather assume that it is an improperly written MS patch. every printer oem, hp is blatant, historically bends the rules when writing device drivers. then you bitches complain when a security hole is discovered and m$ fixes it. |
Windows 10, it's a wonderful thing
In article
Wolf K wrote: On 2017-11-19 16:41, Nathan Hale wrote: In article [...] then you bitches complain when a security hole is discovered and m$ fixes it. I much admire the elegantly diplomatic politesse of your posts. |
Windows 10, it's a wonderful thing
On Sun, 19 Nov 2017 21:41:53 +0000 (GMT), Nathan Hale
wrote: Passing a alleged 'improperly written drivers from Epson' is not a valid argument. You have no idea if it is a driver problem. Since the drivers worked for years up to now, I rather assume that it is an improperly written MS patch. every printer oem, hp is blatant, historically bends the rules when writing device drivers. then you bitches complain when a security hole is discovered and m$ fixes it. Since Windows 3.0 there has been compatibility problems with some programs because the writer takes liberties, bends the rules, or otherwise skirted the MS intentions. My way is better. Especially true of games. Apple was strict on that sort of thing. Hard to say who it to blame unless you know for sure how the driver was written. |
Windows 10, it's a wonderful thing
In article
Ed Pawlowski wrote: On Sun, 19 Nov 2017 21:41:53 +0000 (GMT), Nathan Hale wrote: Passing a alleged 'improperly written drivers from Epson' is not a valid argument. You have no idea if it is a driver problem. Since the drivers worked for years up to now, I rather assume that it is an improperly written MS patch. every printer oem, hp is blatant, historically bends the rules when writing device drivers. then you bitches complain when a security hole is discovered and m$ fixes it. Since Windows 3.0 there has been compatibility problems with some programs because the writer takes liberties, bends the rules, or otherwise skirted the MS intentions. My way is better. Especially true of games. Apple was strict on that sort of thing. Hard to say who it to blame unless you know for sure how the driver was written. |
Windows 10, it's a wonderful thing
In article
Ed Pawlowski wrote: On Sun, 19 Nov 2017 21:41:53 +0000 (GMT), Nathan Hale wrote: Passing a alleged 'improperly written drivers from Epson' is not a valid argument. You have no idea if it is a driver problem. Since the drivers worked for years up to now, I rather assume that it is an improperly written MS patch. every printer oem, hp is blatant, historically bends the rules when writing device drivers. then you bitches complain when a security hole is discovered and m$ fixes it. Since Windows 3.0 there has been compatibility problems with some programs because the writer takes liberties, bends the rules, or otherwise skirted the MS intentions. My way is better. Especially true of games. Apple was strict on that sort of thing. Hard to say who it to blame unless you know for sure how the driver was written. Download the driver and disassemble it. Then you know. Some geniuses on BofA's IT staff ran into an issue where they had a crapload of old printers and no compatible driver for a new OS rollout. They started hacking on the .inf file for the old driver, cutting and pasting pieces from new driver inf files until it installed and appeared to work. Then they rolled it out. Next major service pack, that hack job no longer worked and they were screwed. |
Windows 10, it's a wonderful thing
In article
Ed Pawlowski wrote: On Sun, 19 Nov 2017 21:41:53 +0000 (GMT), Nathan Hale wrote: Passing a alleged 'improperly written drivers from Epson' is not a valid argument. You have no idea if it is a driver problem. Since the drivers worked for years up to now, I rather assume that it is an improperly written MS patch. every printer oem, hp is blatant, historically bends the rules when writing device drivers. then you bitches complain when a security hole is discovered and m$ fixes it. Since Windows 3.0 there has been compatibility problems with some programs because the writer takes liberties, bends the rules, or otherwise skirted the MS intentions. My way is better. Especially true of games. Apple was strict on that sort of thing. Hard to say who it to blame unless you know for sure how the driver was written. Download the driver and disassemble it. Then you know. Some geniuses on BofA's IT staff ran into an issue where they had a crapload of old printers and no compatible driver for a new OS rollout. They started hacking on the .inf file for the old driver, cutting and pasting pieces from new driver inf files until it installed and appeared to work. Then they rolled it out. Next major service pack, that hack job no longer worked and they were screwed. |
Windows 10, it's a wonderful thing
Nomen Nescio:
If MS wants to continue to be a viable OS, then they need to see to it that they don't break things with advancements. What a backwards point of view. MS cannot survive if it allowed the tail to wag the dog, such as you suggest. MS improves its OS continually, and we are safer from malware and we operate more efficiently as a consequence. Like it or not, the multitude of vendors who make peripherial programs will have to take breast of the improvements and change their wares accordingly. MS does do a great deal of testing for compatibility within the guidelines of good pedagogy. |
Windows 10, it's a wonderful thing
In article
Anonymous wrote: Nomen Nescio: If MS wants to continue to be a viable OS, then they need to see to it that they don't break things with advancements. What a backwards point of view. MS cannot survive if it allowed the tail to wag the dog, such as you suggest. MS improves its OS continually, and we are safer from malware and we operate more efficiently as a consequence. Like it or not, the multitude of vendors who make peripherial programs will have to take breast of the improvements and change their wares accordingly. MS does do a great deal of testing for compatibility within the guidelines of good pedagogy. |
All times are GMT +1. The time now is 03:48 AM. |
|
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
HardwareBanter.com