Groups > alt.comp.os.windows-10 > #182809

Re: Today's "Windows 10 concern"

From	Newyana2 <newyana@invalid.nospam>
Newsgroups	alt.comp.os.windows-10
Subject	Re: Today's "Windows 10 concern"
Date	2025-03-07 08:31 -0500
Organization	A noiseless patient Spider
Message-ID	<vqesdl$3iaic$1@dont-email.me> (permalink)
References	<vq9imi$2e7gt$1@dont-email.me> <vqabig$2ioi8$1@dont-email.me> <vqdipm$377vf$2@dont-email.me>

Show all headers | View raw

On 3/6/2025 8:40 PM, John C. wrote:

>>>
>>> I went into the Task Scheduler and disabled the piece of shit:
>>>
>>> Open Task Scheduler
>>>    Click on the carat next to "Task Scheduler Library"
>>>      Same on "Microsoft"
>>>        Same on "Windows"
>>>          Left click on "Device Information"
>>>            Right click on "Device" in the right hand upper pane
>>>              Select "Disable".
>>> If there's another task named "Device User" under "Device" do the same
>>> to it as well.
>>>

   Thanks for that. Mine was disabled but there was a Device User
entry. I have most things in TS disabled. Though I also use
Simplewall to block callinghome. There are numerous processes
that try to call out.

> You're right, Paul. And they did the same thing to the popular Twain
> driver for most scanners built within the last 20 years or so. The
> disabled support for Twain drivers in W10 and for scanner and digital
> camera in-box drivers, Microsoft accepts only WIA drivers.
> 

   To be fair, WIA works in XP, with a supporting printer.
Printer makers have been slow to add support, but MS
came out with WIA a long time ago. My somewhat old
HP Envy supports both TWAIN and WIA. It supported
WIA on XP. Though it was a bit spotty. For example,
there's no way to ask whether it supports a given file
extension. PNG? "Sure, bring it on." It gives me a PNG file,
but it's actually a JPG. That wasn't WIA's fault. HP just
hadn't done the whole job of supporting WIA. I don't know
whether that's HP's fault for being half-assed or Microsoft's
fault for designing a buggy interface.

   We get spoiled on Windows. Up until a year ago I was
still running XP. A lot of software developers were still
supporting it, 23 years after it came out. What if you
were on a Mac? You'd have support only for the current and
one earlier version. "Don't be a cheapskate. People stand
in line for our toys. You should, too." Linux? Don't even try
to imagine it. In 2001 you would have been lucky to get
a program on Linux that could produce something to print.
On current Linux they have no time for the past. Backward
compatibility is an oxymoron. They worship at the alter of
The Future. Hardware support is generally
pretty good, but any kind of commitment to support is
missing. Linux OS support? I think it's typically 6-18 months.
I had to replace the OS on my Raspberry Pi 4 because it
wouldn't support newer Chromium. Luckily I was able to
install the latest Raspbian on the hardware. Of course,
most people wouldn't be able to do that. But the OS was
only 3 years old to begin with.

Thread

Today's "Windows 10 concern" "John C." <r9jmg0@yahoo.com> - 2025-03-05 05:13 -0800
  Re: Today's "Windows 10 concern" Mr Xi Ji Ping <ping@china.cn> - 2025-03-05 18:00 +0000
  Re: Today's "Windows 10 concern" Paul <nospam@needed.invalid> - 2025-03-05 15:18 -0500
    Re: Today's "Windows 10 concern" Frank Slootweg <this@ddress.is.invalid> - 2025-03-06 10:33 +0000
    Re: Today's "Windows 10 concern" "John C." <r9jmg0@yahoo.com> - 2025-03-06 17:40 -0800
      Re: Today's "Windows 10 concern" Newyana2 <newyana@invalid.nospam> - 2025-03-07 08:31 -0500
        Re: Today's "Windows 10 concern" Paul <nospam@needed.invalid> - 2025-03-07 19:04 -0500
        Re: Today's "Windows 10 concern" The Car <arriving@dawn.com> - 2025-03-08 10:39 -0800
          Re: Today's "Windows 10 concern" Paul <nospam@needed.invalid> - 2025-03-08 14:36 -0500
  Re: Today's "Windows 10 concern" micky <NONONOmisc07@fmguy.com> - 2025-03-06 18:45 -0500
    Re: Today's "Windows 10 concern" Paul <nospam@needed.invalid> - 2025-03-06 20:15 -0500
    Re: Today's "Windows 10 concern" ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-03-07 01:02 -0700
      Re: Today's "Windows 10 concern" micky <NONONOmisc07@fmguy.com> - 2025-03-08 00:11 -0500

csiph-web