• Windows 10 is randomly removing programs without telling me

    From John C.@21:1/5 to All on Thu Apr 25 03:57:07 2024
    I have been attempting to get used to Windows 10, but now it had
    developed a problem that, if it ever happens again, will force me to
    either go back to Windows 7 *OR* finally make the move to Linux.

    What is happening is that I'm seeing programs which I was able to use
    without issue in Windows 7 and which I have installed in Windows 10
    suddenly, and completely, disappear.

    Here's an example:

    I installed WizMouse (https://antibody-software.com/wizmouse) and
    configured it to work as it usually does. The program "allows you to
    scroll the window under the mouse with your mouse wheel even if the that
    window doesn't have input focus.
    Windows 10 already has this functionality built in so WizMouse is most
    useful if you're using earlier versions of Windows (Windows 2000, XP,
    Vista, 7, 8)."

    Yesterday, I noticed that the program completely disappeared. In other
    words, it was uninstalled without me doing anything.

    However, perhaps the most frustrating thing is that I was able to
    install the drivers for my beloved Canon Canoscan 8400F scanner and it
    was working perfectly. In fact, it was working better than it ever has
    before. The drivers were for Windows 7, but they installed in Windows 10 without any issues and the scanner has been working for a couple of
    weeks now.

    Then this morning, when I attempted to use the scanner, the twain driver
    was no longer available in Adobe Photoshop Elements or any other
    graphics editing program I have installed, all of which used to list the
    twain driver. The scanner is still listed in the Device Manager and it
    says "This device is working properly."

    I noticed that there was a new system notification, so I checked it out
    and it said something to the effect that "Finish installing software for
    a device." When I attempted to get more information about the
    notification, it simply disappeared!

    when I go into the Device Manager with the scanner turned on,
    right-click on the listing, select "Properties" and click on the
    "Events" tab, I see the following "events" listed: __________________________________________________________________________ Events
    Timestamp Description
    2024-03-25 8:46:23 PM Device configured (null)
    evice USB\VID_04A9&PID_221E\5&2c2ab93d&0&5 was configured.
    Driver Name: null
    Class Guid: {00000000-0000-0000-0000-000000000000}
    Driver Date:
    Driver Version:
    Driver Provider:
    Driver Section:
    Driver Rank: 0x0
    Matching Device Id:
    Outranked Drivers:
    Device Updated: false
    Parent Device: USB\ROOT_HUB20\4&33ca6639&0

    2024-04-10 7:48:47 AM Device deleted
    Device USB\VID_04A9&PID_221E\5&2C2AB93D&0&5 was deleted.
    Class Guid: {00000000-0000-0000-0000-000000000000}

    2024-04-10 7:55:03 AM Device install requested
    Device USB\VID_04A9&PID_221E\5&2c2ab93d&0&5 requires further installation.

    2024-04-10 7:55:04 AM Driver sen/ice added (usbscan)
    Driver Management has concluded the process to add Service usbscan for
    Device Instance ID USB\VID_04A9&PID_221E\5&2C2AB93D&0&5 with the
    following status: 0. __________________________________________________________________________

    I *KNOW* that the drivers I installed will work with Windows 10 because
    they were doing so. To me, it simply appears that the OS deliberately
    fucked things up so that they wouldn't work. I have read various places
    on the internet that other people who owned the same model scanner were
    able to make it work when W10 first came out, but that after one of the
    W10 updates it suddenly quit working.

    This smacks of collusion between Microsoft and Canon in order to get
    people to purchase new scanners from Canon.

    As for software randomly disappearing from Windows 10 without any
    notice, I am far from the only person to see this kind of thing happening:

    https://www.google.com/search?hl=en&as_q=windows+10+programs+get+randomly+uninstalled&as_epq=&as_oq=&as_eq=&as_nlo=&as_nhi=&lr=lang_en&cr=&as_qdr=all&as_sitesearch=&as_occt=any&as_filetype=&tbs=

    Especially this discussion:

    https://www.tenforums.com/software-apps/201227-windows-deletes-software-automatically.html

    Has anybody else experienced this problem (programs being uninstalled
    without permission) and if so, have any of you found a solution or at
    least a reason why it's happening? This is completely unacceptable.

    As for the scanner, if I can't find a way to make it work again, then
    that's it for Windows 10. I won't tolerate this kind of bullshit.

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Newyana2@21:1/5 to John C. on Thu Apr 25 08:27:55 2024
    On 4/25/2024 6:57 AM, John C. wrote:

    As for the scanner, if I can't find a way to make it work again, then
    that's it for Windows 10. I won't tolerate this kind of bullshit.


    Usually scanners/printers will install their own applet with
    the driver. That's not in the start menu? I don't know if
    this will help, but after installing drivers for my HP Envy I've
    found the TWAIN driver doesn't work. But WIA works fine.
    The only downside is that the WIA applet is a "for dummies"
    thing and the printer doesn't implement it properly. HP doesn't
    respond to my WIA script witth full information about properties.
    For example, the WIA applet only gives me a choice of PDF or
    JPG scan output. Yet with my own WIA script I can also
    choose BMP and probably other formats. (With JPG being lossy
    it's a rather dumb primary output format for a scanner.)

    If you're not familiar with this... TWAIN was the standard for
    a long time. WIA is Windows Image Acquisition. It provides
    a COM interface to talk to the scanner, get its capabilities,
    and set scan options. Your problem may be entirely different,
    but you can also look in PS elements or look for a Canon applet.
    My PSP5 offers to scan via TWAIN and sees the scanner, but
    for whatever reason the TWAIN isn't working. However, the
    HP applet and my script both work via WIA.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Johnson@21:1/5 to All on Thu Apr 25 14:46:56 2024
    On Thu, 25 Apr 2024 03:57:07 -0700, "John C." <r9jmg0@yahoo.com>
    wrote:



    As for the scanner, if I can't find a way to make it work again, then
    that's it for Windows 10. I won't tolerate this kind of bullshit.

    It's a long time since I had to install a TWAIN driver for a scanner,
    though I see if I look at the import options for PaintShop Pro it
    lists the TWAIN drivers that it can use. What printer is it? Does it
    have an app for running the scanner? Usually, in my experience,
    installing the scanner app installs the drivers. If you have one, try reinstalling the scanner app. Sounds an odd scenario that you
    describe.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to John C. on Thu Apr 25 14:30:57 2024
    John C. <r9jmg0@yahoo.com> wrote:
    I have been attempting to get used to Windows 10, but now it had
    developed a problem that, if it ever happens again, will force me to
    either go back to Windows 7 *OR* finally make the move to Linux.

    What is happening is that I'm seeing programs which I was able to use
    without issue in Windows 7 and which I have installed in Windows 10
    suddenly, and completely, disappear.

    Here's an example:

    I installed WizMouse (https://antibody-software.com/wizmouse) and
    configured it to work as it usually does. The program "allows you to
    scroll the window under the mouse with your mouse wheel even if the that window doesn't have input focus.
    Windows 10 already has this functionality built in so WizMouse is most
    useful if you're using earlier versions of Windows (Windows 2000, XP,
    Vista, 7, 8)."

    Yesterday, I noticed that the program completely disappeared. In other
    words, it was uninstalled without me doing anything.

    How do you *know* the program was "removed" (uninstalled)? Was it
    listed in Control Panel (-> Programs -> Programs and Features) and is it
    no longer listed there?

    That the program does not work anymore, doesn't mean is was removed.

    However, perhaps the most frustrating thing is that I was able to
    install the drivers for my beloved Canon Canoscan 8400F scanner and it
    was working perfectly. In fact, it was working better than it ever has before. The drivers were for Windows 7, but they installed in Windows 10 without any issues and the scanner has been working for a couple of
    weeks now.

    Then this morning, when I attempted to use the scanner, the twain driver
    was no longer available in Adobe Photoshop Elements or any other
    graphics editing program I have installed, all of which used to list the twain driver. The scanner is still listed in the Device Manager and it
    says "This device is working properly."

    I noticed that there was a new system notification, so I checked it out
    and it said something to the effect that "Finish installing software for
    a device." When I attempted to get more information about the
    notification, it simply disappeared!

    when I go into the Device Manager with the scanner turned on,
    right-click on the listing, select "Properties" and click on the
    "Events" tab, I see the following "events" listed: __________________________________________________________________________ Events
    Timestamp Description
    2024-03-25 8:46:23 PM Device con?gured (null)
    evice USB\VID_04A9&PID_221E\5&2c2ab93d&0&5 was configured.
    Driver Name: null
    Class Guid: {00000000-0000-0000-0000-000000000000}
    Driver Date:
    Driver Version:
    Driver Provider:
    Driver Section:
    Driver Rank: 0x0
    Matching Device Id:
    Outranked Drivers:
    Device Updated: false
    Parent Device: USB\ROOT_HUB20\4&33ca6639&0

    2024-04-10 7:48:47 AM Device deleted
    Device USB\VID_04A9&PID_221E\5&2C2AB93D&0&5 was deleted.
    Class Guid: {00000000-0000-0000-0000-000000000000}

    2024-04-10 7:55:03 AM Device install requested
    Device USB\VID_04A9&PID_221E\5&2c2ab93d&0&5 requires further installation.

    2024-04-10 7:55:04 AM Driver sen/ice added (usbscan)
    Driver Management has concluded the process to add Service usbscan for
    Device Instance ID USB\VID_04A9&PID_221E\5&2C2AB93D&0&5 with the
    following status: 0. __________________________________________________________________________

    I *KNOW* that the drivers I installed will work with Windows 10 because
    they were doing so. To me, it simply appears that the OS deliberately
    fucked things up so that they wouldn't work. I have read various places
    on the internet that other people who owned the same model scanner were
    able to make it work when W10 first came out, but that after one of the
    W10 updates it suddenly quit working.

    April 10 is the Wednesday after the last 'patch Tuesday' (second
    Tuesday of the month), so it looks that Windows Update downloaded and
    installed new drivers which it thought (FSVSVO 'think') were newer/
    better than the 'old'/installed ones.

    For Windows 10 (I mainly use Windows 11) there's still a setting which
    you can set to prevent this from happening (again). (For Windows 11 it's
    less easy, but still possible (with third-party software).)

    I don't have the Windows 10 setting handy, but others/Paul can point
    you to it.

    Question: Besides the scanner driver, did you install any other
    scanner/Canon software? If so, was that listed in 'Programs and
    Features' and now gone?

    This smacks of collusion between Microsoft and Canon in order to get
    people to purchase new scanners from Canon.

    Some comment about stupidity versus malice?

    As for software randomly disappearing from Windows 10 without any
    notice, I am far from the only person to see this kind of thing happening:

    https://www.google.com/search?hl=en&as_q=windows+10+programs+get+randomly+uninstalled&as_epq=&as_oq=&as_eq=&as_nlo=&as_nhi=&lr=lang_en&cr=&as_qdr=all&as_sitesearch=&as_occt=any&as_filetype=&tbs=

    Especially this discussion:

    https://www.tenforums.com/software-apps/201227-windows-deletes-software-automatically.html

    Has anybody else experienced this problem (programs being uninstalled
    without permission) and if so, have any of you found a solution or at
    least a reason why it's happening? This is completely unacceptable.

    My wife's system is Windows 10 and there were no programs removed from
    that system. But she's no tinkerer and I tinker with that system as
    little as possible.

    As for the scanner, if I can't find a way to make it work again, then
    that's it for Windows 10. I won't tolerate this kind of bullshit.

    See above as to what probably happened with the scanner driver and how
    to prevent it in the future. And FWIW, as I mentioned before, my 'stone
    age' (2010) Epson scanner software happily moved from Vista to 8.1 and
    now 11 without it being removed.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stan Brown@21:1/5 to Frank Slootweg on Thu Apr 25 08:51:42 2024
    On 25 Apr 2024 14:30:57 GMT, Frank Slootweg wrote:
    How do you *know* the program was "removed" (uninstalled)? Was it
    listed in Control Panel (-> Programs -> Programs and Features) and is it
    no longer listed there?

    That the program does not work anymore, doesn't mean is was removed.

    True dat.

    Another possibility: Windows Security (formerly Windows Defender) or
    the Malicious Software Removal Tool might have decided those programs
    were dangerous and quarantined them.

    To check that in Windows Security, open Settings; select
    Update & Security
    Windows Security
    Virus & Threat Protection
    Protection History
    If there are any "This app has been blocked" notations, click on each
    one in turn.

    The MSRT runs as a Windows update, and I don't know how to check its
    logs.

    --
    Stan Brown, Tehachapi, California, USA https://BrownMath.com/
    Shikata ga nai...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Hall@21:1/5 to All on Thu Apr 25 16:56:03 2024
    In message <v0dcu6$2v9ts$1@dont-email.me>, John C. <r9jmg0@yahoo.com>
    writes
    <big snip>
    Has anybody else experienced this problem (programs being uninstalled
    without permission)

    I've been using 10 for about five years and, to the best of my
    knowledge, have never had that happen. Could your anti-virus have
    quarantined the program as suspicious without your being aware of it? It
    might be worth checking.
    --
    John Hall
    "Acting is merely the art of keeping a large group of people
    from coughing."
    Sir Ralph Richardson (1902-83)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to John C. on Thu Apr 25 12:44:11 2024
    John C. <r9jmg0@yahoo.com> wrote:

    I installed WizMouse (https://antibody-software.com/wizmouse) and
    configured it to work as it usually does. The program "allows you to
    scroll the window under the mouse with your mouse wheel even if the
    that window doesn't have input focus. Windows 10 already has this functionality built in so WizMouse is most useful if you're using
    earlier versions of Windows (Windows 2000, XP, Vista, 7, 8).

    Yesterday, I noticed that the program completely disappeared. In other
    words, it was uninstalled without me doing anything.

    Did you check the install folder to see if it still existed, and, if so,
    if the program's files are still there?

    However, perhaps the most frustrating thing is that I was able to
    install the drivers for my beloved Canon Canoscan 8400F scanner and
    it was working perfectly. In fact, it was working better than it ever
    has before. The drivers were for Windows 7, but they installed in
    Windows 10 without any issues and the scanner has been working for a
    couple of weeks now.

    Then this morning, when I attempted to use the scanner, the twain
    driver was no longer available in Adobe Photoshop Elements or any
    other graphics editing program I have installed, all of which used to
    list the twain driver. The scanner is still listed in the Device
    Manager and it says "This device is working properly."

    __________________________________________________________________________ Events
    Timestamp Description
    2024-03-25 8:46:23 PM Device configured (null)
    evice USB\VID_04A9&PID_221E\5&2c2ab93d&0&5 was configured.
    Driver Name: null
    Class Guid: {00000000-0000-0000-0000-000000000000}
    Driver Date:
    Driver Version:
    Driver Provider:
    Driver Section:
    Driver Rank: 0x0
    Matching Device Id:
    Outranked Drivers:
    Device Updated: false
    Parent Device: USB\ROOT_HUB20\4&33ca6639&0

    2024-04-10 7:48:47 AM Device deleted
    Device USB\VID_04A9&PID_221E\5&2C2AB93D&0&5 was deleted.
    Class Guid: {00000000-0000-0000-0000-000000000000}

    2024-04-10 7:55:03 AM Device install requested
    Device USB\VID_04A9&PID_221E\5&2c2ab93d&0&5 requires further installation.

    2024-04-10 7:55:04 AM Driver sen/ice added (usbscan)
    Driver Management has concluded the process to add Service usbscan for
    Device Instance ID USB\VID_04A9&PID_221E\5&2C2AB93D&0&5 with the
    following status: 0. __________________________________________________________________________

    Since the scanner is still listed in Device Manager, that device was NOT uninstalled. Didn't the scanner come bundled with some software either
    with the scanner, or you were given a URL of where to download it?

    Not many drivers are dynamic (can be loaded after Windows has loaded,
    and loaded by the user). Many require they load while Windows is
    loading. That means you have to reboot when you install a new driver.
    Did you yet restart Windows?

    Also, do NOT let Microsoft update drivers. It does an unreliable job.
    A device in a family line all under the same model number may have
    different versions, and that versioning could be due to changes in
    hardware, and you need to get the driver that matches on the hardware.
    The same model number doesn't mean the same hardware. However,
    Microsoft can only detect the product and model, not when version
    numbering reflects a major change in the hardware. So, the WU client
    picks a driver for a model, but for the wrong version of the hardware.
    *YOU* should be the only one doing driver updates.

    Just because there is a new driver version does not mean you want it or
    need it. Newer is NOT always better. For example, many video drivers
    get updates to be compatible with newer games (that you may not have,
    and may never have), but you suffer loss of compatibility with older
    games (that you do have). Compatibility code is added to support the
    newer games, but then old compatibility code with old games is lost.
    When reviewing a driver update, you need to decide if you need it. Does
    it address a security issue? Does it fix an issue you are actually experiencing with the current driver? Will it work with your new
    software or hardware AND your old software and hardware? Read the
    release notes for all versions to the newest one, and all those after
    the version you have, to determine if there really is a need for the new
    driver version.

    Disable hardware (driver) updates in Windows, and relegate that
    responsibility to yourself. Rather than describe the registry hack to
    disable driver updating, I use WinAero Tweaker. Most tweaks are have
    links to description pages on how they work, like:

    https://winaero.com/how-to-turn-off-driver-updates-in-windows-update-in-windows-10/

    Search on "update", and use it to disable hardware updates. You can
    even use it to disable Windows updates; however, some features in
    Windows won't work if WU is disabled, like you won't be able to review
    the update history, or use the Windows Store app to find apps that way
    (but you can still use their Store web site). I permanently disable
    hardware updates. I make the choice if the current driver is broken,
    has flaws, or if a new version actually gives me anything. If no bang
    for the buck, I pass on the new driver version. I disable WU for a
    month, or two, maybe longer, until *I* am ready and prepared, like
    saving an image backup (providing a means to escape backwards rather
    than burn the bridge), before allowing those updates.

    Another problem with hardware or WU updates is the time to reflect new
    driver versions in the WU catalog (an MS site). Takes times for a
    vendor to get their new version validated and appear in the catalog. In
    that time, they may find (or users report to them) there are problems
    with a new version, so the vendor has to go through the complete
    submission process again. In the meantime, the catalog is pushing out
    the bad version. There is no yanking of a bad version to immediate
    retrograde to a prior version (that process takes time, too). In the
    meantime, users are getting afflicting with the bad version. Could be a
    couple months before the vendor gets a new -- and fixed new -- version
    put into the catalog, and everyone that got stuck with the bad version
    can finally get the new and fixed version.

    I never allow hardware updates. I make those choices. I disable
    Windows updates until I hear of some that are really important, but even
    then I decide if and when to apply the update (just because there is a
    security update means you might be vulnerable, not that you will be
    hit). Besides scheduled backups, I save an image backup before every
    update whether hardware or software, and the same before I install any
    software (far more accurate to restore from an image backup to get back
    the exact state of my drive rather than rely on uninstallers, and more
    accurate than using System Restore). Pause all updates, you decide when
    to apply any, and prepare by saving an image backup and allocate the
    time (including the outage of your computer during the backup and any
    needed reboots).

    Also, just because an update doesn't declare that a reboot is not needed (you're not told a reboot is required) doesn't mean you shouldn't
    reboot. File versions can get out of sync: old files may still be left
    around, especially if they were in use, with a mix of new files, and
    failures can occur when trying to use the old files with new ones. Do a
    reboot after an update to ensure the file set is in sync.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to All on Thu Apr 25 17:47:57 2024
    Earlier today, I wrote:
    [...]

    April 10 is the Wednesday after the last 'patch Tuesday' (second
    Tuesday of the month), so it looks that Windows Update downloaded and installed new drivers which it thought (FSVSVO 'think') were newer/
    better than the 'old'/installed ones.

    For Windows 10 (I mainly use Windows 11) there's still a setting which
    you can set to prevent this from happening (again). (For Windows 11 it's
    less easy, but still possible (with third-party software).)

    I don't have the Windows 10 setting handy, but others/Paul can point
    you to it.

    I checked my notes and found my notes on how to stop automatic driver updates.

    It's apparently the same setting for Windows 10 and 11. Credits go to
    Paul [1] for mentioning the basic method (method 1. in the article) and
    for pointing to the MakeUseOf article:

    'How to Stop Automatic Driver Updates on Windows' <https://www.makeuseof.com/windows-stop-automatic-driver-updates>

    FWIW, I checked with method 3. (Registry Editor) on my Windows 11
    system and the SearchOrderConfig key is indeed set to the default value
    1 (Automatic Driver Updates are enabled).

    Hope this helps.

    [...]

    [1] Paul's post:
    From: Paul <nospam@needed.invalid>
    Newsgroups: alt.comp.os.windows-10
    Subject: Re: Windows 10 updating drivers
    Date: Mon, 26 Dec 2022 18:09:02 -0500
    Message-ID: <tod9if$3dbha$1@dont-email.me>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to Stan Brown on Thu Apr 25 13:32:11 2024
    Stan Brown <the_stan_brown@fastmail.fm> wrote:

    Frank Slootweg wrote:

    How do you *know* the program was "removed" (uninstalled)? Was it
    listed in Control Panel (-> Programs -> Programs and Features) and
    is it no longer listed there?

    That the program does not work anymore, doesn't mean is was removed.

    Another possibility: Windows Security (formerly Windows Defender) or
    the Malicious Software Removal Tool might have decided those programs
    were dangerous and quarantined them.

    To check that in Windows Security, open Settings; select
    Update & Security
    Windows Security
    Virus & Threat Protection
    Protection History
    If there are any "This app has been blocked" notations, click on each
    one in turn.

    The MSRT runs as a Windows update, and I don't know how to check its
    logs.

    I downloaded the portable version of WizMouse (so I could see the files
    instead of the installer executable). I submitted wizmouse.exe and wizmouse.dll to VirusTotal. The .exe had a couple hits on obscure AVs,
    but those are insignificant. The .dll had no hits. I don't think
    Defender saw wizmouse as malware, but only looking it its logs might
    show it decided it was a PUP (Probably Unwanted Program) or PUA
    (Potentially Unwanted Application).

    Not sure why the OP still wants to use WizMouse under Windows 10 where
    the program seems superfluous. WizMouse isn't even listed at the
    author's home page (https://antibody-software.com/). The .exe and .dll
    haven't been updated since Sept 2013. It's ancient. It's long dead.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From micky@21:1/5 to this@ddress.is.invalid on Fri Apr 26 02:09:27 2024
    In alt.comp.os.windows-10, on 25 Apr 2024 14:30:57 GMT, Frank Slootweg <this@ddress.is.invalid> wrote:


    This smacks of collusion between Microsoft and Canon in order to get
    people to purchase new scanners from Canon.

    Some comment about stupidity versus malice?

    Not even stupidity. It's awfully hard to test updates with every device
    out there to make sure it's still compatible. That's why Apple doesn't
    let every Tom, Dick and Harry write software, etc for their products,
    but it's also why there are far fewer programs to run.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From micky@21:1/5 to r9jmg0@yahoo.com on Fri Apr 26 02:13:00 2024
    In alt.comp.os.windows-10, on Thu, 25 Apr 2024 03:57:07 -0700, "John C." <r9jmg0@yahoo.com> wrote:



    I installed WizMouse (https://antibody-software.com/wizmouse) and
    configured it to work as it usually does. The program "allows you to
    scroll the window under the mouse with your mouse wheel even if the that >window doesn't have input focus.
    Windows 10 already has this functionality built in so WizMouse is most
    useful if you're using earlier versions of Windows (Windows 2000, XP,
    Vista, 7, 8)."

    Yesterday, I noticed that the program completely disappeared. In other
    words, it was uninstalled without me doing anything.

    Why not just install it again? I see two possibilities. It only got uninstalled because something related got installed on the 2nd Tuesday
    update, OR a check is made every 2nd Tuesday and it will get uninstalled
    in a month , every month. I think it's the first and you won't have
    more problems for years, but I'm guessing. Others here might know how
    that actually works.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to Peter Johnson on Sun Apr 28 07:26:18 2024
    Peter Johnson wrote:
    John C. wrote:

    As for the scanner, if I can't find a way to make it work again, then
    that's it for Windows 10. I won't tolerate this kind of bullshit.

    It's a long time since I had to install a TWAIN driver for a scanner,
    though I see if I look at the import options for PaintShop Pro it
    lists the TWAIN drivers that it can use. What printer is it?

    Printer? What are you talking about? I'm talking about a scanner. A
    stand-alone scanner. As I said in the OP, "my beloved Canon Canoscan
    8400F scanner."

    Does it have an app

    I'm not running my scanner from a "smart" phone, I'm running it from my
    desktop computer. The software it uses is referred to correctly as an "application".

    for running the scanner? Usually, in my experience,
    installing the scanner app

    Again, you mean "application". Or program. Yes, I did try installing it
    but it was a separate install from the drivers and did not include the
    drivers. The scanner remained inoperative.

    installs the drivers. If you have one, try
    reinstalling the scanner app. Sounds an odd scenario that you
    describe.

    No, there's nothing odd about it at all. This is the way things were
    done when I first purchased the scanner.

    Regardless, since I posted the first message to this thread, I've found
    a freeware program that's able to access the twain driver I installed
    for my scanner.

    --
    John C. No ad, CD, cripple, demo, nag, pay, pirated, share, spy,
    time-limited, trial or web wares for me please.

    So that I don't see them, I filter out crossposts (messages sent to
    multiple newsgroups at a time) and from various trolls (like "al" AKA
    "Bill Bennett".)
    If you do the same, the group will be easier for you to read.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to VanguardLH on Sun Apr 28 07:34:53 2024
    VanguardLH wrote:
    Stan Brown <the_stan_brown@fastmail.fm> wrote:

    Frank Slootweg wrote:

    How do you *know* the program was "removed" (uninstalled)? Was it
    listed in Control Panel (-> Programs -> Programs and Features) and
    is it no longer listed there?

    I know because I just installed the program. It runs in the background
    with an icon on the Tray. I noticed when I started up the system a
    couple of days ago that the icon was missing. When I tried to find the
    program in my Start Menu, it wasn't there. When I looked in "Programs
    and Features", it was no longer listed as an installed program.

    I did NOT uninstall the program myself. Period.

    That the program does not work anymore, doesn't mean is was removed.

    In this case, yes, it did mean that.

    Another possibility: Windows Security (formerly Windows Defender) or
    the Malicious Software Removal Tool might have decided those programs
    were dangerous and quarantined them.

    There was no notification and not mention of it being uninstalled that I
    was able to find anywhere.

    To check that in Windows Security, open Settings; select
    Update & Security »
    Windows Security »
    Virus & Threat Protection »
    Protection History
    If there are any "This app has been blocked" notations, click on each
    one in turn.

    The MSRT runs as a Windows update, and I don't know how to check its
    logs.

    I downloaded the portable version of WizMouse (so I could see the files instead of the installer executable). I submitted wizmouse.exe and wizmouse.dll to VirusTotal. The .exe had a couple hits on obscure AVs,
    but those are insignificant. The .dll had no hits. I don't think
    Defender saw wizmouse as malware, but only looking it its logs might
    show it decided it was a PUP (Probably Unwanted Program) or PUA
    (Potentially Unwanted Application).

    Not sure why the OP still wants to use WizMouse under Windows 10 where
    the program seems superfluous. WizMouse isn't even listed at the
    author's home page (https://antibody-software.com/). The .exe and .dll haven't been updated since Sept 2013. It's ancient. It's long dead.

    Although the program "allows you to scroll the window under the mouse
    with your mouse wheel even if the that window doesn't have input focus.
    Windows 10 already has this functionality built in...", I was going to
    explore whether or not MS's implementation of the feature did things
    like automatically move the background window to the foreground when I
    scrolled it. I do not want this to happen. However, before I was able to determine if this was the case or not, the program disappeared.

    --
    John C. No ad, CD, cripple, demo, nag, pay, pirated, share, spy,
    time-limited, trial or web wares for me please.

    So that I don't see them, I filter out crossposts (messages sent to
    multiple newsgroups at a time) and from various trolls (like "al" AKA
    "Bill Bennett".)
    If you do the same, the group will be easier for you to read.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to micky on Sun Apr 28 07:49:23 2024
    micky wrote:
    In alt.comp.os.windows-10, on 25 Apr 2024 14:30:57 GMT, Frank Slootweg <this@ddress.is.invalid> wrote:


    This smacks of collusion between Microsoft and Canon in order to get
    people to purchase new scanners from Canon.

    Some comment about stupidity versus malice?

    Not even stupidity. It's awfully hard to test updates with every device
    out there to make sure it's still compatible. That's why Apple doesn't
    let every Tom, Dick and Harry write software, etc for their products,
    but it's also why there are far fewer programs to run.

    The scanner not only worked for me for a while in Windows 10, but many
    other Canoscan 8400F users experienced the same thing for a few years
    before a Microsoft updated rendered their scanners non-functional as well.

    Am I supposed to be happy about this kind of thing? My scanner still
    works physically and if I were to set up one of my older computers
    (something I don't have the room for in my house), I could easily attach
    the scanner to it and prove that it works.

    Would YOU be happy about being forced to purchase a new scanner? The
    only scanners being made these days that combine negative and slide
    scanning capability are very, very expensive. >80(>

    --
    John C. No ad, CD, cripple, demo, nag, pay, pirated, share, spy,
    time-limited, trial or web wares for me please.

    So that I don't see them, I filter out crossposts (messages sent to
    multiple newsgroups at a time) and from various trolls (like "al" AKA
    "Bill Bennett".)
    If you do the same, the group will be easier for you to read.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to Frank Slootweg on Sun Apr 28 07:42:38 2024
    Frank Slootweg wrote:
    Earlier today, I wrote:
    [...]

    April 10 is the Wednesday after the last 'patch Tuesday' (second
    Tuesday of the month), so it looks that Windows Update downloaded and
    installed new drivers which it thought (FSVSVO 'think') were newer/
    better than the 'old'/installed ones.

    For Windows 10 (I mainly use Windows 11) there's still a setting which
    you can set to prevent this from happening (again). (For Windows 11 it's
    less easy, but still possible (with third-party software).)

    I don't have the Windows 10 setting handy, but others/Paul can point
    you to it.

    I checked my notes and found my notes on how to stop automatic driver updates.

    It's apparently the same setting for Windows 10 and 11. Credits go to
    Paul [1] for mentioning the basic method (method 1. in the article) and
    for pointing to the MakeUseOf article:

    'How to Stop Automatic Driver Updates on Windows' <https://www.makeuseof.com/windows-stop-automatic-driver-updates>

    FWIW, I checked with method 3. (Registry Editor) on my Windows 11
    system and the SearchOrderConfig key is indeed set to the default value
    1 (Automatic Driver Updates are enabled).

    Hope this helps.

    [...]

    [1] Paul's post:
    From: Paul <nospam@needed.invalid>
    Newsgroups: alt.comp.os.windows-10
    Subject: Re: Windows 10 updating drivers
    Date: Mon, 26 Dec 2022 18:09:02 -0500
    Message-ID: <tod9if$3dbha$1@dont-email.me>

    Thanks, Frank. The info in the article was slightly different from what
    I found in the Group Policy Editor, but I still found the setting and
    enabled it.

    --
    John C. No ad, CD, cripple, demo, nag, pay, pirated, share, spy,
    time-limited, trial or web wares for me please.

    So that I don't see them, I filter out crossposts (messages sent to
    multiple newsgroups at a time) and from various trolls (like "al" AKA
    "Bill Bennett".)
    If you do the same, the group will be easier for you to read.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to John Hall on Sun Apr 28 07:50:00 2024
    John Hall wrote:
    In message <v0dcu6$2v9ts$1@dont-email.me>, John C. <r9jmg0@yahoo.com>
    writes
    <big snip>
    Has anybody else experienced this problem (programs being uninstalled
    without permission)

    I've been using 10 for about five years and, to the best of my
    knowledge, have never had that happen. Could your anti-virus have
    quarantined the program as suspicious without your being aware of it? It might be worth checking.

    That was about the first thing I checked. Nope, the program just
    disappeared.

    --
    John C. No ad, CD, cripple, demo, nag, pay, pirated, share, spy,
    time-limited, trial or web wares for me please.

    So that I don't see them, I filter out crossposts (messages sent to
    multiple newsgroups at a time) and from various trolls (like "al" AKA
    "Bill Bennett".)
    If you do the same, the group will be easier for you to read.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to VanguardLH on Sun Apr 28 07:56:25 2024
    VanguardLH wrote:
    John C. <r9jmg0@yahoo.com> wrote:

    I installed WizMouse (https://antibody-software.com/wizmouse) and
    configured it to work as it usually does. The program "allows you to
    scroll the window under the mouse with your mouse wheel even if the
    that window doesn't have input focus. Windows 10 already has this
    functionality built in so WizMouse is most useful if you're using
    earlier versions of Windows (Windows 2000, XP, Vista, 7, 8).

    Yesterday, I noticed that the program completely disappeared. In other
    words, it was uninstalled without me doing anything.

    Did you check the install folder to see if it still existed, and, if so,
    if the program's files are still there?

    Yes, and it wasn't.

    However, perhaps the most frustrating thing is that I was able to
    install the drivers for my beloved Canon Canoscan 8400F scanner and
    it was working perfectly. In fact, it was working better than it ever
    has before. The drivers were for Windows 7, but they installed in
    Windows 10 without any issues and the scanner has been working for a
    couple of weeks now.

    Then this morning, when I attempted to use the scanner, the twain
    driver was no longer available in Adobe Photoshop Elements or any
    other graphics editing program I have installed, all of which used to
    list the twain driver. The scanner is still listed in the Device
    Manager and it says "This device is working properly."

    __________________________________________________________________________ >> Events
    Timestamp Description
    2024-03-25 8:46:23 PM Device configured (null)
    evice USB\VID_04A9&PID_221E\5&2c2ab93d&0&5 was configured.
    Driver Name: null
    Class Guid: {00000000-0000-0000-0000-000000000000}
    Driver Date:
    Driver Version:
    Driver Provider:
    Driver Section:
    Driver Rank: 0x0
    Matching Device Id:
    Outranked Drivers:
    Device Updated: false
    Parent Device: USB\ROOT_HUB20\4&33ca6639&0

    2024-04-10 7:48:47 AM Device deleted
    Device USB\VID_04A9&PID_221E\5&2C2AB93D&0&5 was deleted.
    Class Guid: {00000000-0000-0000-0000-000000000000}

    2024-04-10 7:55:03 AM Device install requested
    Device USB\VID_04A9&PID_221E\5&2c2ab93d&0&5 requires further installation. >>
    2024-04-10 7:55:04 AM Driver sen/ice added (usbscan)
    Driver Management has concluded the process to add Service usbscan for
    Device Instance ID USB\VID_04A9&PID_221E\5&2C2AB93D&0&5 with the
    following status: 0.
    __________________________________________________________________________

    Since the scanner is still listed in Device Manager, that device was NOT uninstalled. Didn't the scanner come bundled with some software either
    with the scanner, or you were given a URL of where to download it?

    Yes, it was installed. I was able to use the scanner for a couple of
    weeks before the twain driver was no longer available in any of my image editing programs.

    Not many drivers are dynamic (can be loaded after Windows has loaded,
    and loaded by the user). Many require they load while Windows is
    loading. That means you have to reboot when you install a new driver.
    Did you yet restart Windows?

    Yes, and I tried this but it didn't change anything.

    Also, do NOT let Microsoft update drivers. It does an unreliable job.

    Totally agree. And I've since disabled driver updates.

    A device in a family line all under the same model number may have
    different versions, and that versioning could be due to changes in
    hardware, and you need to get the driver that matches on the hardware.
    The same model number doesn't mean the same hardware. However,
    Microsoft can only detect the product and model, not when version
    numbering reflects a major change in the hardware. So, the WU client
    picks a driver for a model, but for the wrong version of the hardware.
    *YOU* should be the only one doing driver updates.

    Agreed, but the driver is still installed and if the twain driver can be accessed, it functions. I determined this by installing this freeware
    program:

    https://www.naps2.com/

    My scanner problem is now solved.

    I'll keep your reply archived in case the problem arises again. Thanks
    for your effort, VanguardLH. I really appreciate your help.

    --
    John C. No ad, CD, cripple, demo, nag, pay, pirated, share, spy,
    time-limited, trial or web wares for me please.

    So that I don't see them, I filter out crossposts (messages sent to
    multiple newsgroups at a time) and from various trolls (like "al" AKA
    "Bill Bennett".)
    If you do the same, the group will be easier for you to read.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to micky on Sun Apr 28 07:58:05 2024
    micky wrote:
    John C. wrote:

    I installed WizMouse (https://antibody-software.com/wizmouse) and
    configured it to work as it usually does. The program "allows you to
    scroll the window under the mouse with your mouse wheel even if the that
    window doesn't have input focus.
    Windows 10 already has this functionality built in so WizMouse is most
    useful if you're using earlier versions of Windows (Windows 2000, XP,
    Vista, 7, 8)."

    Yesterday, I noticed that the program completely disappeared. In other
    words, it was uninstalled without me doing anything.

    Why not just install it again? I see two possibilities. It only got uninstalled because something related got installed on the 2nd Tuesday update, OR a check is made every 2nd Tuesday and it will get uninstalled
    in a month , every month. I think it's the first and you won't have
    more problems for years, but I'm guessing. Others here might know how
    that actually works.

    Thanks, but I did that already. Seems to be working. I read online that
    other people who were experiencing the same problem as me were able to
    get programs to stay installed by reinstalling them two or three times.

    --
    John C. No ad, CD, cripple, demo, nag, pay, pirated, share, spy,
    time-limited, trial or web wares for me please.

    So that I don't see them, I filter out crossposts (messages sent to
    multiple newsgroups at a time) and from various trolls (like "al" AKA
    "Bill Bennett".)
    If you do the same, the group will be easier for you to read.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From micky@21:1/5 to r9jmg0@yahoo.com on Sun Apr 28 13:59:07 2024
    In alt.comp.os.windows-10, on Sun, 28 Apr 2024 07:49:23 -0700, "John C." <r9jmg0@yahoo.com> wrote:

    micky wrote:
    In alt.comp.os.windows-10, on 25 Apr 2024 14:30:57 GMT, Frank Slootweg
    <this@ddress.is.invalid> wrote:


    This smacks of collusion between Microsoft and Canon in order to get
    people to purchase new scanners from Canon.

    Some comment about stupidity versus malice?

    Not even stupidity. It's awfully hard to test updates with every device
    out there to make sure it's still compatible. That's why Apple doesn't
    let every Tom, Dick and Harry write software, etc for their products,
    but it's also why there are far fewer programs to run.

    The scanner not only worked for me for a while in Windows 10, but many
    other Canoscan 8400F users experienced the same thing for a few years
    before a Microsoft updated rendered their scanners non-functional as well.

    Am I supposed to be happy about this kind of thing? My scanner still
    works physically and if I were to set up one of my older computers
    (something I don't have the room for in my house), I could easily attach
    the scanner to it and prove that it works.

    Would YOU be happy about being forced to purchase a new scanner? The

    I never said you should be happy. I said it's hard to test every OS modification to see if it works with every piece of software written by
    1000's, tens of 1000's, of software companies.


    only scanners being made these days that combine negative and slide
    scanning capability are very, very expensive. >80(>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to John C. on Sun Apr 28 13:58:55 2024
    John C. <r9jmg0@yahoo.com> wrote:

    I'm not running my scanner from a "smart" phone, I'm running it from my desktop computer. The software it uses is referred to correctly as an "application".

    Microsoft confused and conflated the terminology. Programs and
    applications meant the same thing (Win32 programs), so application was
    often abbreviated to "app". Then Microsoft came out with UWP (Universal Windows Platform) apps. They didn't call them applications, or UWPs, or newapps, but just apps. This confused the new UWP apps with the old
    Win32 apps. So, now "app" means a UWP application, and application or
    program means a Win32 application. Which terminology you lean towards
    depends on how long you've been using PCs.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to John C. on Sun Apr 28 14:14:19 2024
    "John C." <r9jmg0@yahoo.com> wrote:

    John Hall wrote:

    John C. <r9jmg0@yahoo.com> WROTE:

    Has anybody else experienced this problem (programs being uninstalled
    without permission)

    I've been using 10 for about five years and, to the best of my
    knowledge, have never had that happen. Could your anti-virus have
    quarantined the program as suspicious without your being aware of it? It
    might be worth checking.

    That was about the first thing I checked. Nope, the program just
    disappeared.

    With mention of anti-virus comes to mind possible other-actor malicious
    action whether deliberate or accidental.

    Have you enabled RDP to allow remote access to your computer? Is Remote Assistance disabled? See:

    https://winaero.com/disable-remote-assistance-windows-10/

    I disabled that long ago. Don't need it, won't allow it, and disabled
    it should there be any vulnerabilities.

    Running any other remoting software (e.g., VNC, TeamViewer)? I have
    used both in the past, but never left them running (as a server to
    accept new outside connects).

    What you described I've not seen happen: suddenly installed programs disappearing. So, I'd make sure no one can remote into your computer to perform accidental or malicious actions.

    There is one condition where I've seen programs disappear: a corrupted
    Windows profile. There are online articles on how to mend, but I
    usually don't bother, create a new Windows profile, and start again. In
    fact, you can backup your Windows profile: run sysdm.cpl, Advanced tab,
    User Profiles, Copy To.

    However, I resort to using an image backup to restore the drives back to
    the exact state as before. The backups are scheduled. Relying on the
    user to perform a backup means unreliable backups. Do you have image
    backups to which you could restore your computer to when you saw the now missing programs? You could try using System Restore, but that does not
    revert the drive(s) back to their exact state as before. Restoring from
    image backups does. If you don't do backups then nothing on your
    computer is important.

    If you already did a restore from backup, could be the backup from which
    you restored was created before you installed the software or drivers.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to John C. on Sun Apr 28 13:53:02 2024
    John C. <r9jmg0@yahoo.com> wrote:

    VanguardLH wrote:

    Stan Brown <the_stan_brown@fastmail.fm> wrote:

    Frank Slootweg wrote:

    How do you *know* the program was "removed" (uninstalled)? Was it
    listed in Control Panel (-> Programs -> Programs and Features) and
    is it no longer listed there?

    I know because I just installed the program. It runs in the background
    with an icon on the Tray. I noticed when I started up the system a
    couple of days ago that the icon was missing. When I tried to find the program in my Start Menu, it wasn't there. When I looked in "Programs
    and Features", it was no longer listed as an installed program.

    I did NOT uninstall the program myself. Period.

    There are installable and portable versions of WizMouse. The installer
    likely adds the Start menu and desktop shortcuts, and probably defaults
    to showing a systray icon. For the portable version, you merely copy
    the files (no shortcuts unless you create them). Could be there is an
    option of whether or not to show a systray icon, especially for the
    portable version (but then it really isn't portable if it gets added as
    a startup program since affects the registry for startup proggies).

    Seems you moved from Windows 7 to 10. Was that an upgrade from 7 to 10?
    Or did you do a fresh install of Win10, and then install (not copy the
    portable version of) WizMouse?

    Do you run any cleanup tools (e.g., CCleaner, Bleachbit, etc)? Where
    was the install folder for WizMouse? Is that folder, or its parent, a
    target for a cleanup tool?

    Another possibility: Windows Security (formerly Windows Defender) or
    the Malicious Software Removal Tool might have decided those programs
    were dangerous and quarantined them.

    There was no notification and not mention of it being uninstalled that
    I was able to find anywhere.

    To check that in Windows Security, open Settings; select
    Update & Security
    Windows Security
    Virus & Threat Protection
    Protection History
    If there are any "This app has been blocked" notations, click on each
    one in turn.

    To verify, did you check where Slootweg mentioned in Defender's history?

    I downloaded the portable version of WizMouse (so I could see the files
    instead of the installer executable). I submitted wizmouse.exe and
    wizmouse.dll to VirusTotal. The .exe had a couple hits on obscure AVs,
    but those are insignificant. The .dll had no hits. I don't think
    Defender saw wizmouse as malware, but only looking it its logs might
    show it decided it was a PUP (Probably Unwanted Program) or PUA
    (Potentially Unwanted Application).

    I was going to explore whether or not MS's implementation of the
    feature did things like automatically move the background window to
    the foreground when I scrolled it. I do not want this to happen.
    However, before I was able to determine if this was the case or not,
    the program disappeared.

    In Win10 settings, go to Mouse, and check if the option "Scroll inactive windows when I hover over them" is enabled. Scrolling the inactive
    window does not change focus (the inactive window does rise to the top).

    For what you do not want for now (make the scrolled inactive window rise
    to the top), another option might look at is to make a window rise to
    the top just by hovering the mouse over it. This is called the X-mouse function. See:

    https://winaero.com/enable-xmouse-window-tracking-windows-10/

    Scrolling an inactive window means part of that window could be
    partially obliterated by another window. The x-mouse function lets you
    pop the target window to the top that you could then scroll. Hover the
    mouse over the prior window to have it get focus again. However, if I
    need the scrolled window to be completely visible, I just click on it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Steve Hayes@21:1/5 to VanguardLH on Mon Apr 29 05:17:43 2024
    XPost: alt.usage.english, alt.english.usage

    On Sun, 28 Apr 2024 13:58:55 -0500, VanguardLH <V@nguard.LH> wrote:

    John C. <r9jmg0@yahoo.com> wrote:

    I'm not running my scanner from a "smart" phone, I'm running it from my
    desktop computer. The software it uses is referred to correctly as an
    "application".

    Microsoft confused and conflated the terminology. Programs and
    applications meant the same thing (Win32 programs), so application was
    often abbreviated to "app". Then Microsoft came out with UWP (Universal >Windows Platform) apps. They didn't call them applications, or UWPs, or >newapps, but just apps. This confused the new UWP apps with the old
    Win32 apps. So, now "app" means a UWP application, and application or >program means a Win32 application. Which terminology you lean towards >depends on how long you've been using PCs.

    In my understanding and usage "app" is short for "application program"
    and is distingushed from other programs by what it is used for. There
    are programs like "utilities" that are for maintaining the computer's
    running, or system programs that are not apps.



    --
    Steve Hayes from Tshwane, South Africa
    Web: http://www.khanya.org.za/stevesig.htm
    Blog: http://khanya.wordpress.com
    E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bertel Lund Hansen@21:1/5 to Anton Shepelev on Mon Apr 29 12:50:09 2024
    XPost: alt.usage.english, alt.english.usage

    Anton Shepelev wrote:

    In my understanding and usage "app" is short for
    "application program" and is distingushed from other
    programs by what it is used for. There are programs like
    "utilities" that are for maintaining the computer's
    running, or system programs that are not apps.

    You are correct. I find `app' exceedingly vulgar, and
    prefer the normal terms `program' and `application'.

    To me they are all programs. I only use "app" about programs on my
    mobile when talking with other people.

    --
    Bertel
    Kolt, Denmark

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anton Shepelev@21:1/5 to All on Mon Apr 29 13:36:21 2024
    XPost: alt.usage.english, alt.english.usage

    Steve Hayes:

    In my understanding and usage "app" is short for
    "application program" and is distingushed from other
    programs by what it is used for. There are programs like
    "utilities" that are for maintaining the computer's
    running, or system programs that are not apps.

    You are correct. I find `app' exceedingly vulgar, and
    prefer the normal terms `program' and `application'.

    --
    () ascii ribbon campaign -- against html e-mail
    /\ www.asciiribbon.org -- against proprietary attachments

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bertel Lund Hansen@21:1/5 to J. J. Lodder on Mon Apr 29 13:47:35 2024
    XPost: alt.usage.english, alt.english.usage

    J. J. Lodder wrote:

    In my understanding and usage "app" is short for "application program"
    and is distingushed from other programs by what it is used for. There
    are programs like "utilities" that are for maintaining the computer's
    running, or system programs that are not apps.

    It is anything with the extension .app

    A text file?

    --
    Bertel
    Kolt, Denmark

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From J. J. Lodder@21:1/5 to Steve Hayes on Mon Apr 29 13:45:15 2024
    XPost: alt.usage.english, alt.english.usage

    Steve Hayes <hayesstw@telkomsa.net> wrote:

    On Sun, 28 Apr 2024 13:58:55 -0500, VanguardLH <V@nguard.LH> wrote:

    John C. <r9jmg0@yahoo.com> wrote:

    I'm not running my scanner from a "smart" phone, I'm running it from my
    desktop computer. The software it uses is referred to correctly as an
    "application".

    Microsoft confused and conflated the terminology. Programs and >applications meant the same thing (Win32 programs), so application was >often abbreviated to "app". Then Microsoft came out with UWP (Universal >Windows Platform) apps. They didn't call them applications, or UWPs, or >newapps, but just apps. This confused the new UWP apps with the old
    Win32 apps. So, now "app" means a UWP application, and application or >program means a Win32 application. Which terminology you lean towards >depends on how long you've been using PCs.

    In my understanding and usage "app" is short for "application program"
    and is distingushed from other programs by what it is used for. There
    are programs like "utilities" that are for maintaining the computer's running, or system programs that are not apps.

    It is anything with the extension .app

    Jan
    (avoiding the Evil Empire)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to VanguardLH on Mon Apr 29 05:53:06 2024
    VanguardLH wrote:
    John C. wrote:

    I'm not running my scanner from a "smart" phone, I'm running it from my
    desktop computer. The software it uses is referred to correctly as an
    "application".

    Microsoft confused and conflated the terminology. Programs and
    applications meant the same thing (Win32 programs), so application was
    often abbreviated to "app". Then Microsoft came out with UWP (Universal Windows Platform) apps. They didn't call them applications, or UWPs, or newapps, but just apps. This confused the new UWP apps with the old
    Win32 apps. So, now "app" means a UWP application, and application or program means a Win32 application. Which terminology you lean towards depends on how long you've been using PCs.

    Totally agree. And my understanding of the term "app" as it applies to
    smart phones is that it can mean either something installed on the phone
    or else a web service.

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Newyana2@21:1/5 to Steve Hayes on Mon Apr 29 08:59:10 2024
    XPost: alt.usage.english, alt.english.usage

    On 4/28/2024 11:17 PM, Steve Hayes wrote:


    In my understanding and usage "app" is short for "application program"
    and is distingushed from other programs by what it is used for. There
    are programs like "utilities" that are for maintaining the computer's running, or system programs that are not apps.


    Whether we like it or not, I think V's explanation is entirely
    accurate. App started with Steve Jobs and became a word
    that meant cellphone applet. It was typical of Apple, creating
    a cutesy, child-like environment that would placate and
    entertain people afraid of tech, with icons that look like
    they're designed by a 12 year old girl who dots her i's with
    little hearts.

    On Windows it's always been "programs". Only some
    programmers say "application". (It could be worse. For
    awhile people were talking about their programming
    projects as "solutions".)

    Having established that app means cellphone applet, MS
    have made things more clear. They've gone from Metro to
    RT to UWP to name essentially the same crippled, interpreted
    applet software. Who knows those terms? No one outside of
    Windows programming. With the Start Menu separating Programs
    from Apps it becomes still more clear. These Metro applets are,
    and are meant to be, more like cellphone applets than Windows
    software. They're a completely different animal, closer to
    dyanmic webpages than to complied executables. (Though,
    frankly, I've never found a clear explanation of exactly how
    they work. I've seen lists of restricted APIs. I've seen lists
    of all the ways one can write a Metro applet -- from HTML to
    C++. But I've never seen a technical explanation of exactly how
    they operate and get interpreted.)

    I often call them Metro apps because that's the first name
    MS came up with and it's the only name with flavor. RT and UWP
    are terms only geeks can like. Metro carries a connotation of
    urban fashion. As though Bill Gates had decided to buy an iPhone,
    get a haircut that costs more than $10, and invite some intelligentsia
    over for winetasting. MS probably hoped that the flat, ugly,
    borderless monotone of Metro apps, with the Apple-style slide
    controls, would seem hip and artfully sparse.

    That's an interesting pattern with fashions. For example, with
    the use of color, rare and intense colors were prized for millennia.
    Then we came up with "day-glo" fluorescent colors. All colors were
    possible and cheap. So what were gourmands to do? Subtle variations
    of beige became all the rage. Computers have been similar. We had
    3-D. We had walnut burl windows. We had boombox windows. With
    Win7 we had clever translucency and grass growing on window
    frames. Garish and complicated had reached their limit. Where was
    there to go? Hues of beige. That's basically what the Metro theme is.
    The fashion sophisticate now goes for minimalist, ever since excess
    became effortless. Though I'm not sure how much of the computing
    public gets that particular joke.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to VanguardLH on Mon Apr 29 06:15:05 2024
    VanguardLH wrote:
    John C. wrote:
    VanguardLH wrote:
    Stan Brown wrote:
    Frank Slootweg wrote:

    How do you *know* the program was "removed" (uninstalled)? Was it
    listed in Control Panel (-> Programs -> Programs and Features) and
    is it no longer listed there?

    I know because I just installed the program. It runs in the background
    with an icon on the Tray. I noticed when I started up the system a
    couple of days ago that the icon was missing. When I tried to find the
    program in my Start Menu, it wasn't there. When I looked in "Programs
    and Features", it was no longer listed as an installed program.

    I did NOT uninstall the program myself. Period.

    There are installable and portable versions of WizMouse. The installer likely adds the Start menu and desktop shortcuts, and probably defaults
    to showing a systray icon. For the portable version, you merely copy
    the files (no shortcuts unless you create them). Could be there is an
    option of whether or not to show a systray icon, especially for the
    portable version (but then it really isn't portable if it gets added as
    a startup program since affects the registry for startup proggies).

    Seems you moved from Windows 7 to 10. Was that an upgrade from 7 to 10?

    No, the option I chose during the move was to do a fresh install from
    scratch rather than an upgrade. For some reason though, the process did
    create a folder named "Windows.old" which contained the old $Recycle.bin
    and complete "Users" folders. Glad it did so, too. And since I had my
    data backed up, I was able to preserve that.

    Or did you do a fresh install of Win10, and then install (not copy the portable version of) WizMouse?

    I did a fresh install.

    Do you run any cleanup tools (e.g., CCleaner, Bleachbit, etc)?

    No. I didn't do that. Still haven't done that yet. Still checking out a
    few things before I do.

    Where was the install folder for WizMouse?

    "C:\Program Files (x86)\WizMouse\WizMouse.exe"

    Is that folder, or its parent, a target for a cleanup tool?

    No, it is not.

    Another possibility: Windows Security (formerly Windows Defender) or
    the Malicious Software Removal Tool might have decided those programs
    were dangerous and quarantined them.

    There was no notification and no mention of it being uninstalled that
    I was able to find anywhere.

    To check that in Windows Security, open Settings; select
    Update & Security
    Windows Security
    Virus & Threat Protection
    Protection History
    If there are any "This app has been blocked" notations, click on each
    one in turn.

    To verify, did you check where Slootweg mentioned in Defender's history?

    Yes, I did. There was no mention of the program being removed. In fact,
    no mention of it at all.

    What I *did* see was a repeated mention of:

    "PUABundler:Win32/PhotoScapeBundler

    which presumably was installed with PhotoScapeSetup V3.7, despite my
    having refused the offer of third party crap during installation.

    I downloaded the portable version of WizMouse (so I could see the files
    instead of the installer executable). I submitted wizmouse.exe and
    wizmouse.dll to VirusTotal. The .exe had a couple hits on obscure AVs,
    but those are insignificant. The .dll had no hits. I don't think
    Defender saw wizmouse as malware, but only looking it its logs might
    show it decided it was a PUP (Probably Unwanted Program) or PUA
    (Potentially Unwanted Application).

    I was going to explore whether or not MS's implementation of the
    feature did things like automatically move the background window to
    the foreground when I scrolled it. I do not want this to happen.
    However, before I was able to determine if this was the case or not,
    the program disappeared.

    In Win10 settings, go to Mouse, and check if the option "Scroll inactive windows when I hover over them" is enabled. Scrolling the inactive
    window does not change focus (the inactive window does rise to the top).

    Thanks for that. I did that just now and there was a checkmark there.
    Doesn't seem to hurt anything to leave Wizmouse installed though, but if
    it disappears again I probably won't reinstall it.

    For what you do not want for now (make the scrolled inactive window rise
    to the top), another option might look at is to make a window rise to
    the top just by hovering the mouse over it. This is called the X-mouse function. See:

    https://winaero.com/enable-xmouse-window-tracking-windows-10/

    Scrolling an inactive window means part of that window could be
    partially obliterated by another window. The x-mouse function lets you
    pop the target window to the top that you could then scroll. Hover the
    mouse over the prior window to have it get focus again. However, if I
    need the scrolled window to be completely visible, I just click on it.

    That's also how I prefer to do things.

    Thanks again for your help, VanguardLH.

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to VanguardLH on Mon Apr 29 06:23:18 2024
    VanguardLH wrote:
    John C. wrote:
    John Hall wrote:
    John C. wrote:

    Has anybody else experienced this problem (programs being uninstalled
    without permission)

    I've been using 10 for about five years and, to the best of my
    knowledge, have never had that happen. Could your anti-virus have
    quarantined the program as suspicious without your being aware of it? It >>> might be worth checking.

    That was about the first thing I checked. Nope, the program just
    disappeared.

    With mention of anti-virus comes to mind possible other-actor malicious action whether deliberate or accidental.

    Have you enabled RDP to allow remote access to your computer? Is Remote Assistance disabled? See:

    https://winaero.com/disable-remote-assistance-windows-10/

    I disabled that long ago. Don't need it, won't allow it, and disabled
    it should there be any vulnerabilities.

    Yes, along with file indexing, that's always the first thing I disable
    when moving to a new version of Windows or doing a fresh install of the
    version I'm using.

    Running any other remoting software (e.g., VNC, TeamViewer)? I have
    used both in the past, but never left them running (as a server to
    accept new outside connects).

    No, I've never used anything like that.

    What you described I've not seen happen: suddenly installed programs disappearing. So, I'd make sure no one can remote into your computer to perform accidental or malicious actions.

    There is one condition where I've seen programs disappear: a corrupted Windows profile. There are online articles on how to mend, but I
    usually don't bother, create a new Windows profile, and start again. In fact, you can backup your Windows profile: run sysdm.cpl, Advanced tab,
    User Profiles, Copy To.

    I always try to install programs for all users.

    However, I resort to using an image backup to restore the drives back to
    the exact state as before. The backups are scheduled. Relying on the
    user to perform a backup means unreliable backups. Do you have image
    backups to which you could restore your computer to when you saw the now missing programs? You could try using System Restore, but that does not revert the drive(s) back to their exact state as before. Restoring from image backups does. If you don't do backups then nothing on your
    computer is important.

    If you already did a restore from backup, could be the backup from which
    you restored was created before you installed the software or drivers.

    There's been a lot of things going on in my life at this point. I guess
    I should consider the possibility that I may have seen the notice on the Wizmouse homepage:

    https://antibody-software.com/wizmouse

    that "Windows 10 already has this functionality built in so WizMouse is
    most useful if you're using earlier versions of Windows..." and not
    bothered to install it.

    My memory of installing it is probably when I did so on another computer
    I'm currently working on for somebody else. Since it's running W7, I did install the program on that system.

    If that was the case, then my apologies to everybody for the error.

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to All on Mon Apr 29 06:33:38 2024
    XPost: alt.usage.english, alt.english.usage

    Newyana2 wrote:
    Steve Hayes wrote:

    In my understanding and usage "app" is short for "application program"
    and is distingushed from other programs by what it is used for. There
    are programs like "utilities" that are for maintaining the computer's
    running, or system programs that are not apps.

      Whether we like it or not, I think V's explanation is entirely
    accurate. App started with Steve Jobs and became a word
    that meant cellphone applet. It was typical of Apple, creating
    a cutesy, child-like environment that would placate and
    entertain people afraid of tech, with icons that look like
    they're designed by a 12 year old girl who dots her i's with
    little hearts.

       On Windows it's always been "programs". Only some
    programmers say "application". (It could be worse. For
    awhile people were talking about their programming
    projects as "solutions".)

    Yes, that wouldn't have been a good thing.

       Having established that app means cellphone applet, MS
    have made things more clear. They've gone from Metro to
    RT to UWP to name essentially the same crippled, interpreted
    applet software. Who knows those terms? No one outside of
    Windows programming. With the Start Menu separating Programs
    from Apps it becomes still more clear. These Metro applets are,
    and are meant to be, more like cellphone applets than Windows
    software. They're a completely different animal, closer to
    dyanmic webpages than to complied executables. (Though,
    frankly, I've never found a clear explanation of exactly how
    they work. I've seen lists of restricted APIs. I've seen lists
    of all the ways one can write a Metro applet -- from HTML to
    C++. But I've never seen a technical explanation of exactly how
    they operate and get interpreted.)

    My understanding of them is that they're more or less like a portable
    app that uses callouts to modules which are standard in every Windows
    version since W8. The "apps" are hidden in a folder named "C:/Program Files/WindowsApps". You may think you can "uninstall" them, but all that
    does is to (usually) turn them off if they normally run in the
    background AND to eliminate access to them. The program files actually
    remain in the WindowsApps folder. Steps to access to that folder are
    easily found on the internet so that you can delete the program files,
    but doing so can be risky if the files you delete are for "apps" that
    come by default with Windows.

      I often call them Metro apps because that's the first name
    MS came up with and it's the only name with flavor. RT and UWP
    are terms only geeks can like. Metro carries a connotation of
    urban fashion. As though Bill Gates had decided to buy an iPhone,
    get a haircut that costs more than $10, and invite some intelligentsia
    over for winetasting. MS probably hoped that the flat, ugly,
    borderless monotone of Metro apps, with the Apple-style slide
    controls, would seem hip and artfully sparse.

    It made me gag.

      That's an interesting pattern with fashions. For example, with
    the use of color, rare and intense colors were prized for millennia.
    Then we came up with "day-glo" fluorescent colors. All colors were
    possible and cheap. So what were gourmands to do? Subtle variations
    of beige became all the rage. Computers have been similar. We had
    3-D. We had walnut burl windows. We had boombox windows. With
    Win7 we had clever translucency and grass growing on window
    frames. Garish and complicated had reached their limit. Where was
    there to go? Hues of beige. That's basically what the Metro theme is.
    The fashion sophisticate now goes for minimalist, ever since excess
    became effortless. Though I'm not sure how much of the computing
    public gets that particular joke.

    For me, one of the most frustrating things about W10 is the massively
    reduced UI configurability.

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Brian Gregory@21:1/5 to John C. on Mon Apr 29 15:12:19 2024
    On 25/04/2024 11:57, John C. wrote:
    I have been attempting to get used to Windows 10, but now it had
    developed a problem that, if it ever happens again, will force me to
    either go back to Windows 7 *OR* finally make the move to Linux.

    What is happening is that I'm seeing programs which I was able to use
    without issue in Windows 7 and which I have installed in Windows 10
    suddenly, and completely, disappear.

    Old programs are sometimes falsely recognized as malware by Defender and deleted or quarantined. Go to setings / Windows security and see if
    anything shows under Virus and Threat protection / protection history.
    If that is what happened you can go to Virus and Threat protection /
    Manage settings / Add or remove exclusions and add the effected file or directory as excluded from virus / malware scans.

    --
    Brian Gregory (in England).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to VanguardLH on Mon Apr 29 12:00:39 2024
    VanguardLH <V@nguard.LH> wrote:

    In Win10 settings, go to Mouse, and check if the option "Scroll inactive windows when I hover over them" is enabled. Scrolling the inactive
    window does not change focus (the inactive window does rise to the top).
    not ___/
    Sometimes my brain
    outpaces my fingers.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Newyana2@21:1/5 to John C. on Mon Apr 29 13:38:42 2024
    XPost: alt.usage.english, alt.english.usage

    On 4/29/2024 9:33 AM, John C. wrote:
    Newyana2 wrote:
    Steve Hayes wrote:

    In my understanding and usage "app" is short for "application program"
    and is distingushed from other programs by what it is used for. There
    are programs like "utilities" that are for maintaining the computer's
    running, or system programs that are not apps.

    Whether we like it or not, I think V's explanation is entirely
    accurate. App started with Steve Jobs and became a word
    that meant cellphone applet. It was typical of Apple, creating
    a cutesy, child-like environment that would placate and
    entertain people afraid of tech, with icons that look like
    they're designed by a 12 year old girl who dots her i's with
    little hearts.

    On Windows it's always been "programs". Only some
    programmers say "application". (It could be worse. For
    awhile people were talking about their programming
    projects as "solutions".)

    Yes, that wouldn't have been a good thing.

    Having established that app means cellphone applet, MS
    have made things more clear. They've gone from Metro to
    RT to UWP to name essentially the same crippled, interpreted
    applet software. Who knows those terms? No one outside of
    Windows programming. With the Start Menu separating Programs
    from Apps it becomes still more clear. These Metro applets are,
    and are meant to be, more like cellphone applets than Windows
    software. They're a completely different animal, closer to
    dyanmic webpages than to complied executables. (Though,
    frankly, I've never found a clear explanation of exactly how
    they work. I've seen lists of restricted APIs. I've seen lists
    of all the ways one can write a Metro applet -- from HTML to
    C++. But I've never seen a technical explanation of exactly how
    they operate and get interpreted.)

    My understanding of them is that they're more or less like a portable
    app that uses callouts to modules which are standard in every Windows
    version since W8. The "apps" are hidden in a folder named "C:/Program Files/WindowsApps". You may think you can "uninstall" them, but all that
    does is to (usually) turn them off if they normally run in the
    background AND to eliminate access to them. The program files actually
    remain in the WindowsApps folder. Steps to access to that folder are
    easily found on the internet so that you can delete the program files,
    but doing so can be risky if the files you delete are for "apps" that
    come by default with Windows.

    They can be uninnstalled to some extent, but it's a tedious
    process involving PowerShell, designed to make sure that virtually
    no one tries it. Microsoft are clearly trying to force this crap
    on people, getting everyone used to thinking of Windows as
    a giant Metro cellphone, with plenty of ads and no control.

    https://www.askvg.com/guide-how-to-remove-all-built-in-apps-in-windows-10/

    I've uninstalled pretty much everything on my system. When I
    set it up I wanted to get to a base starting point of max-clean,
    min-size, no junk.

    The WindowsApps
    folder mostly just has .Net runtimes in it. I also left applets for display, sounds and sound recorder. The rest is gone. The SystemApps folder
    is similar. It seems to only have basic OS functionality. I tried to
    remove SearchApp but id didn't work. I was able to shut it off, though,
    by renaming the folder with a bat file.

    Crazy nonsense. When I look at Sound Recorder I find a lot of crap
    that looks like redundant config files, and an EXE that seems to be
    a normal, compiled PE file.

    For me, one of the most frustrating things about W10 is the massively
    reduced UI configurability.


    Yes. Odd, isn't it? I've found that with Classic Shell and
    WinAero Tweaker I can get back some control. But it turned
    out that I can't get window frames without Aero. And there's
    no going back to a menu from the "ribbon". Fortunately I
    don't use that very much. I've got it looking pretty much
    like XP/7 with Classic style, for the most part. And actually,
    some things are better. For example, I was able to change
    most icons without too much trouble. I now have my own folder
    icons and was aable to bring my red oak wasttebasket over
    from XP. (Though Win10 often doesn't update the display
    when I empty it.)

    One annoyance still unsolved is folder windows. I tried runing
    a Win7 script to make all windows the same size. It seems to
    have worked. But then if I do something like maximize one window,
    Win10 starts maxing all of them and I have to retrain it. That's
    especially irritating because it's been broken since Win98.

    On XP, every folder was set to remember its size and type, but
    it didn't work because Explorer had a bug that made it record the
    specs wrong. It was fixable with a Registry edit, but rather involved.

    With Vista/7 MS broke the system again, swapping around the
    Registry settings as though to deliberately thwart any effort to
    make it work properly. Win7 has a way to remove all settings and then
    create one setting for all folders, which is fine with me. I'm still not certain whether it still works on Win10.

    It involves deleting the keys
    HKEY_CURRENT_USER\SOFTWARE\Classes\Local Settings\Software\Microsoft\Windows\Shell\BagMRU and Bags, which store
    settings for each opened folder
    but are undependable.

    Then those two keys are recreated and the desired settings are
    created in Bags\AllFolders\Shell ...It's not a project for the faint of
    heart. :)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Steve Hayes on Mon Apr 29 17:05:40 2024
    XPost: alt.usage.english, alt.english.usage

    On 4/28/2024 11:17 PM, Steve Hayes wrote:
    On Sun, 28 Apr 2024 13:58:55 -0500, VanguardLH <V@nguard.LH> wrote:

    John C. <r9jmg0@yahoo.com> wrote:

    I'm not running my scanner from a "smart" phone, I'm running it from my
    desktop computer. The software it uses is referred to correctly as an
    "application".

    Microsoft confused and conflated the terminology. Programs and
    applications meant the same thing (Win32 programs), so application was
    often abbreviated to "app". Then Microsoft came out with UWP (Universal
    Windows Platform) apps. They didn't call them applications, or UWPs, or
    newapps, but just apps. This confused the new UWP apps with the old
    Win32 apps. So, now "app" means a UWP application, and application or
    program means a Win32 application. Which terminology you lean towards
    depends on how long you've been using PCs.

    In my understanding and usage "app" is short for "application program"
    and is distingushed from other programs by what it is used for. There
    are programs like "utilities" that are for maintaining the computer's running, or system programs that are not apps.

    On Windows, a Metro.App is not command line. It does not
    "launch" in an ordinary way. No attempt was made to
    integrate it into the Win32 infrastructure. You can't
    chain Metro.App together in a script and "make something useful".

    There is even trouble making "shortcuts". A shortcut, you cannot
    pass parameters to a Metro.App via the shortcut.

    It is purposefully "in-sensate" design.

    "Apps" are different, and a special place in hell is reserved for their characteristic.

    More than one ecosystem right now, is headed towards a "non-technical" "un-debuggable"
    state. You have been warned.

    Always keep tools so you can write your own applications. A day may come,
    where you are the developer -- that will be because of how bad the
    environment has become.

    Ubuntu for example, is trying to replace everything with Snaps, which is
    a way of dumbing down how Linux works. There is nothing "noteworthy"
    about this commercial activity, except that it is "headed in the wrong direction".
    The multiple packaging activities (Snap, Flatpak, AppImage) on Linux, have
    no technical merit, but they're great for splitting customers into groups,
    for harvest.

    "Apps", unfortunately, are not a joke. They're a serious matter.

    Here is a picture of the Groove Music Player (Groove.App).
    Now, what is noteworthy about this ? It's licensed content. You
    could click it and... it could stop playing and it would no
    longer start. In other words, while it has a Manifest, and while
    it will download a fresh copy if the files are adulterated, it
    is also centrally controlled, and can be removed from your
    desktop in the blink of an eye.

    https://filestore.community.support.microsoft.com/api/images/cc39e98c-fef7-4404-bedd-aa8a3d4aa624?upload=true

    Windows Media Player, is an item in transition. Only older versions
    are fairly benign.

    https://en.wikipedia.org/wiki/Windows_Media_Player

    Whereas something like WinAmp, has an entirely different history.
    This is not an App. Will they ruin it ? No. Not if they
    want $10 a copy.

    https://www.popularmechanics.com/technology/audio/a23797304/winamp-is-coming-back-in-2019/

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Moylan@21:1/5 to All on Tue Apr 30 10:48:26 2024
    XPost: alt.usage.english, alt.english.usage

    On 29/04/24 22:59, Newyana2 wrote:
    On 4/28/2024 11:17 PM, Steve Hayes wrote:

    In my understanding and usage "app" is short for "application
    program" and is distingushed from other programs by what it is used
    for. There are programs like "utilities" that are for maintaining
    the computer's running, or system programs that are not apps.


    Whether we like it or not, I think V's explanation is entirely
    accurate. App started with Steve Jobs and became a word that meant
    cellphone applet. It was typical of Apple, creating a cutesy,
    child-like environment that would placate and entertain people afraid
    of tech, with icons that look like they're designed by a 12 year old
    girl who dots her i's with little hearts.

    It's for that reason that my definition of "app" is "like a program, but
    not as well written".

    --
    Peter Moylan http://www.pmoylan.org
    Newcastle, NSW

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Moylan@21:1/5 to All on Tue Apr 30 10:47:07 2024
    XPost: alt.usage.english, alt.english.usage

    On 30/04/24 03:38, Newyana2 wrote:

    One annoyance still unsolved is folder windows. I tried runing a Win7
    script to make all windows the same size. It seems to have worked.
    But then if I do something like maximize one window, Win10 starts
    maxing all of them and I have to retrain it. That's especially
    irritating because it's been broken since Win98.

    I dislike the Windows implementation of folder windows for several
    reasons, but a major one is that they take up massive amounts of screen
    real estate. Why do they have to be so big, and filled with a lot of
    useless detail?

    On my desktop (I run OS/2), each folder has separately specified display attributes, such as whether in icon view the icons are located as
    placed, or put in multiple columns, etc. (There's also a tree view and a details view, and the details view does take a lot of space.) In the
    case of a folder whose files are all of the same kind, e.g. all source
    files, I usually choose to display only the names (no icons shown) in a
    simple multi-column list, so that the folder window is very small. That
    matters to me. During program development, in particular, I'll have a
    number of folder windows open and a number of other windows (e.g.
    command shells) open. I want to be able to get at those easily. Windows
    seems to have been designed for people who only run one program at a time.

    --
    Peter Moylan http://www.pmoylan.org
    Newcastle, NSW

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Peter Moylan on Mon Apr 29 22:21:02 2024
    XPost: alt.usage.english, alt.english.usage

    On 4/29/2024 8:47 PM, Peter Moylan wrote:
    On 30/04/24 03:38, Newyana2 wrote:

    One annoyance still unsolved is folder windows. I tried runing a Win7
    script to make all windows the same size. It seems to have worked.
    But then if I do something like maximize one window, Win10 starts
    maxing all of them and I have to retrain it. That's especially
    irritating because it's been broken since Win98.

    I dislike the Windows implementation of folder windows for several
    reasons, but a major one is that they take up massive amounts of screen
    real estate. Why do they have to be so big, and filled with a lot of
    useless detail?

    On my desktop (I run OS/2), each folder has separately specified display attributes, such as whether in icon view the icons are located as
    placed, or put in multiple columns, etc. (There's also a tree view and a details view, and the details view does take a lot of space.) In the
    case of a folder whose files are all of the same kind, e.g. all source
    files, I usually choose to display only the names (no icons shown) in a simple multi-column list, so that the folder window is very small. That matters to me. During program development, in particular, I'll have a
    number of folder windows open and a number of other windows (e.g.
    command shells) open. I want to be able to get at those easily. Windows
    seems to have been designed for people who only run one program at a time.


    You can adjust the columns, de-select some of them, and put whatever information you want in the window. Just because the default sucks,
    don't give up.

    [Picture] [The scale was doubled, to make it easier to read]

    https://i.postimg.cc/K4XGLY9b/folder-W11.gif

    If the built-in is not good enough, third party tools also exist.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Newyana2@21:1/5 to Peter Moylan on Mon Apr 29 22:48:21 2024
    XPost: alt.usage.english, alt.english.usage

    On 4/29/2024 8:47 PM, Peter Moylan wrote:

    On my desktop (I run OS/2), each folder has separately specified display attributes, such as whether in icon view the icons are located as
    placed, or put in multiple columns, etc.

    That's what Windows is supposed to do, dating back to Win9x.
    It's been broken with every rendition. Yet the settings are still
    there -- thousands of keys in the Registry meant to spec the size
    and orientation of each individual window. It's like building a
    skyscraper and neglecting to put stairs... for 30 years... How do
    they do that? Maybe it's an interesting story.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Moylan@21:1/5 to Peter Moylan on Tue Apr 30 14:31:52 2024
    XPost: alt.usage.english, alt.english.usage

    On 30/04/24 14:18, Peter Moylan wrote:

    Here's another view of the same folder, showing all details. http://www.pmoylan.org/ftp/DetailsView.png (So more comparable to the
    Windows default view.) The window is now a lot larger, of course, but
    you could still fit plenty of other things on the screen. And in
    practice it wouldn't be as wide because I don't normally choose to
    display three separate timestamps for each file.

    Admission: the folder windows might get bigger in future. As my eyesight weakens, I might end up using a larger font size for my most-used folders.

    --
    Peter Moylan http://www.pmoylan.org
    Newcastle, NSW

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Moylan@21:1/5 to Paul on Tue Apr 30 14:18:30 2024
    XPost: alt.usage.english, alt.english.usage

    On 30/04/24 12:21, Paul wrote:
    On 4/29/2024 8:47 PM, Peter Moylan wrote:

    I dislike the Windows implementation of folder windows for several
    reasons, but a major one is that they take up massive amounts of
    screen real estate. Why do they have to be so big, and filled with
    a lot of useless detail?

    [...]

    You can adjust the columns, de-select some of them, and put whatever
    information you want in the window. Just because the default sucks,
    don't give up.

    [Picture] [The scale was doubled, to make it easier to read]

    https://i.postimg.cc/K4XGLY9b/folder-W11.gif

    If the built-in is not good enough, third party tools also exist.

    True, it's possible to do that much, but notice how much of your window
    is taken up with things that aren't file names.

    Here's a similar example on my computer
    http://www.pmoylan.org/ftp/FolderView.png
    (This is full-size, but even if doubled it wouldn't look large.) The
    overhead (things that aren't file names) in this example consists of the
    title bar, the menu bar, the scroll bar, and a summary at the bottom.
    The decision not to display icons means that the titles are closer
    together. If I do display icons, I can choose between normal icons and
    small icons.

    I could have made this smaller, by turning off the options to view the
    menu bar and the status bar, but I usually leave those visible.

    Microsoft could have chosen to do a similar thing, but they chose to
    focus on bells and whistles.

    Here's another view of the same folder, showing all details.
    http://www.pmoylan.org/ftp/DetailsView.png
    (So more comparable to the Windows default view.) The window is now a
    lot larger, of course, but you could still fit plenty of other things on
    the screen. And in practice it wouldn't be as wide because I don't
    normally choose to display three separate timestamps for each file.

    --
    Peter Moylan http://www.pmoylan.org
    Newcastle, NSW

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bertel Lund Hansen@21:1/5 to All on Tue Apr 30 09:32:29 2024
    XPost: alt.usage.english, alt.english.usage

    Newyana2 wrote:

    That's what Windows is supposed to do, dating back to Win9x.
    It's been broken with every rendition. Yet the settings are still
    there -- thousands of keys in the Registry meant to spec the size
    and orientation of each individual window. It's like building a
    skyscraper and neglecting to put stairs... for 30 years... How do
    they do that? Maybe it's an interesting story.

    Thanks. That explains what I wondered about for a long time. Up till XP
    the windows had individual settings. Suddenly with version 7 that was
    gone.

    --
    Bertel
    Kolt, Denmark

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bertel Lund Hansen@21:1/5 to Peter Moylan on Tue Apr 30 09:27:59 2024
    XPost: alt.usage.english, alt.english.usage

    Peter Moylan wrote:

    case of a folder whose files are all of the same kind, e.g. all source
    files, I usually choose to display only the names (no icons shown) in a simple multi-column list, so that the folder window is very small. That matters to me. During program development, in particular, I'll have a
    number of folder windows open and a number of other windows (e.g.
    command shells) open. I want to be able to get at those easily. Windows
    seems to have been designed for people who only run one program at a time.

    I've always chosen a minimal display of the folders. Now with Linux I
    have pretty much the same view as I had with Windows up to 10 (first
    version). I have a small icon and the file name for each file in a
    flowing display. In Linux (Mint) there is a one click access to the
    detailed view where also the size, the time and the file time are
    displayed. This choice is remembered though I'd prefer if it weren't.

    --
    Bertel
    Kolt, Denmark

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bertel Lund Hansen@21:1/5 to Paul on Tue Apr 30 09:35:48 2024
    XPost: alt.usage.english, alt.english.usage

    Paul wrote:

    Windows Media Player, is an item in transition. Only older versions
    are fairly benign.

    Thanks for VLC which I used under Windows and use now under Linux.

    --
    Bertel
    Kolt, Denmark

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bertel Lund Hansen@21:1/5 to Bertel Lund Hansen on Tue Apr 30 11:06:45 2024
    XPost: alt.usage.english, alt.english.usage

    Bertel Lund Hansen wrote:

    detailed view where also the size, the time and the file time are

    Second item should be "type".

    --
    Bertel
    Kolt, Denmark

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Newyana2@21:1/5 to Peter Moylan on Tue Apr 30 08:45:25 2024
    XPost: alt.usage.english, alt.english.usage

    On 4/30/2024 12:18 AM, Peter Moylan wrote:

    True, it's possible to do that much, but notice how much of your window
    is taken up with things that aren't file names.

    Here's a similar example on my computer
    http://www.pmoylan.org/ftp/FolderView.png

    That's something I hadn't thought of. I dislike the ribbon bar
    as unnecessary rejumbling of defaults. But it's also, as you say,
    a massive space waster. It's basically spreading each submenu
    out under the menu bar, without being able to close them.

    You can, of course, remove what they call the Navigation Pane,
    what used to be called the Explorer Bar or Explorer Treeview.
    Though I use that. In XP I had made my own Explorer Bar with
    links to commonly accessed folders and expanded file previews,
    but I wrote it in VB6, which is 32-bit only, so I can't use it in
    Win10-64 because it's an in-process shell extension. Bitness has
    to match.

    It's a big missed opportunity that MS don't provide some kind
    of building block kit for people to arrange folders in whatever way
    is most useful, without need for technical expertise. Though in my
    most recent explorations of Linux, that seems to be even less flexible.
    You can choose from all sorts of "window managers". Most are ugly
    and minimal. KDE is a beautiful piece of work, but focused mainly
    on looks, not functionality.

    In the meantime I find that I've collected a row of folder shortcuts
    on my Win10 Desktop, to make up for the convenience of my old Explorer
    Bar. AppData, System32, Coding folder, etc. The original inspiration
    for those links was actually Active Desktop. It wasn't my idea. It
    was MS's idea to make all folder windows into webpages in IE. The
    file view was a listbox on a webpage. So anything one could do with a
    webpage could be done with folder windows. It was great. And any folder
    could be custom, as well. But MS never made that functionality useful.
    They only made Active Desktop to show that they were "webby", to
    introduce ads on the Desktop, and to "cut off Netscape's air supply".
    So they had this brilliant invention and only plopped a half-assed image-preview control onto the left side.

    I suppose part of the problem has always been the issue of architects
    vs engineers. The architect designs a liveable space but is unconcerned
    with technical issues like holding up the roof. The engineer designs
    roof support, but ignores aesthetics. We have computer UIs designed
    primarily by engineers. Those engineers assume that anyone not techy
    is simpleminded, so they confuse usability with childishness, creating
    silly icons and "my" everything. Apple takes that to an extreme. The
    screen appearance looks like a daycare center, while access to control
    and customization is almost entirely cut off... Never trust a techie who
    gives you Looney Tunes for a GUI. :)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Newyana2@21:1/5 to Bertel Lund Hansen on Tue Apr 30 09:28:59 2024
    XPost: alt.usage.english, alt.english.usage

    On 4/30/2024 3:32 AM, Bertel Lund Hansen wrote:
    Newyana2 wrote:

    That's what Windows is supposed to do, dating back to Win9x.
    It's been broken with every rendition. Yet the settings are still
    there -- thousands of keys in the Registry meant to spec the size
    and orientation of each individual window. It's like building a
    skyscraper and neglecting to put stairs... for 30 years... How do
    they do that? Maybe it's an interesting story.

    Thanks. That explains what I wondered about for a long time. Up till XP
    the windows had individual settings. Suddenly with version 7 that was
    gone.


    XP had them, but they often didn't take. If you look at HKCU\SOFTWARE\Classes\Local Settings\Software\Microsoft\
    Windows\Shell\Bags
    in Win10 you'll see that the settings are still there. But still,
    Windows seems to be not saving them properly and thus forgets
    them. On Win7 I found that I could fix it by properly configuring Bags\AllFolders\Shell and deleting the rest of the Bags subkeys.
    I'm still not sure whether that works on Win10. It seems that a
    sample Shell key once again lacks the necessary settings.

    It's complicated because this is all undocumented and MS
    switch it up frivolously with every release. But there is a system.
    Explorer is supposed to record the specs when a window closes.
    If you look in those keys you may see values with names drawn
    from Shell API parameters for displaying windows. WFlags specs
    min/max/normal size. FFlags, ShowCmd, Vid (which specs display
    options, not as 1-5 but as GUIDs!), etc.

    Windows size and position are specced like so:
    "WinPos" is followed by screen dimensions and API-style specs.
    For example, I have WinPos1920x1080x96(1).top, with corresponding
    bottom, left and right. All of these have to be redone if screen
    resolution is changed. But Win10 Explorer is not propagating those
    specs to Bags keys, so it doesn't know how a window should appear.
    And of course, Win10 adds a few new values, willy nilly, which may
    or may not actually be relevant... And a new wrinkle has been added
    since Win7: The broken folder settings are now saved to a further
    subkey -- Bags\[number]\Shell\{5C4F28B5-F869-4E84-8E60-F11DB97C5CC7}

    That GUID signifies a generic folder type. Ther Softies just
    can't seem to resist throwing in GUIDs to make things look
    more official. Now there are folder types. 20-30 of them. (Generic, communications, library....)

    Sometimes I think half the time of MS developers must be spent
    in the lunch room, competing to have the best secret decode ring
    from some video game box.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From micky@21:1/5 to r9jmg0@yahoo.com on Wed May 1 16:23:23 2024
    In alt.comp.os.windows-10, on Sun, 28 Apr 2024 07:50:00 -0700, "John C." <r9jmg0@yahoo.com> wrote:

    John Hall wrote:
    In message <v0dcu6$2v9ts$1@dont-email.me>, John C. <r9jmg0@yahoo.com>
    writes
    <big snip>
    Has anybody else experienced this problem (programs being uninstalled
    without permission)

    I've been using 10 for about five years and, to the best of my
    knowledge, have never had that happen. Could your anti-virus have
    quarantined the program as suspicious without your being aware of it? It
    might be worth checking.

    That was about the first thing I checked. Nope, the program just
    disappeared.

    Do you have more than one malware program?

    Somehow I ended up with two.

    Despite the warnings, they worked fine together for years.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Steve Hayes on Sat May 4 02:11:51 2024
    XPost: alt.usage.english, alt.english.usage

    On 5/4/2024 1:01 AM, Steve Hayes wrote:
    On Mon, 29 Apr 2024 06:33:38 -0700, "John C." <r9jmg0@yahoo.com>
    wrote:

    Newyana2 wrote:

       On Windows it's always been "programs". Only some
    programmers say "application". (It could be worse. For
    awhile people were talking about their programming
    projects as "solutions".)

    Yes, that wouldn't have been a good thing.

    I have seen advertisements for "solutions", but they never tell you
    what problem they are claiming to be able to solve.

    Yes, they're all programs, but some are applications, like word
    processors, spreadsheets, databases etc.

    But I have a program called "Glary Utilities", which is not an
    application. It just helps the computer to run better. Likewise, the operating system is a program, but not an application.

    The operating system is not a program. It is an executive.

    It loads applications in Ring3.

    There is a scheduler giving "execution time slices" to the application.

    In Ring 0, lives a kernel and hardware drivers. Applications are
    not allowed to access hardware directly, and go through kernel calls.

    There is a task scheduler, that allows items to be loaded/executed at
    fixed time points. That's similar to CRON in Linux or Unix.

    And to further complicate matters, even though the OS is an executive,
    it is virtualized via an inverted hypervisor. The diagram of how
    an executive works, no longer looks the same as it did in Windows XP.
    Windows 10 would be the root partition. The Linux partition would
    really exist, if you had installed WSL plus the Linux distro of your
    choice. If you had VirtualBox, it would have a position in this diagram
    too (not shown of course). VirtualBox is not nested, that I can detect.
    Nested has never worked on my computers here. I tried.

    https://web.archive.org/web/20111205072921/https://msdn.microsoft.com/en-us/library/cc768520%28v=bts.10%29.aspx

    Task Manager was not modified in any way, to make details about this
    apparent to the machine operator. This is why I use a *Power Meter*
    on the AC line cord, to detect foreign activity (even if it is windows
    doing it, and does not show in the list). In Task Manager for example,
    try and find "Memory Compressor". Now, use Process Explorer, you will
    find Memory Compressor is listed as a process.

    [What Task Manager should have been - percent CPU with two digits after decimal, nice!!! ]

    https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer

    One of the observations you can make, is via the "ruggedness" of Task Manager. The modern Task Manager can freeze. In an emergency, it is the patron
    saint of "Useless". Can't do a thing with it. You will notice the Task
    Manager in Windows XP was not like that. Via statically provided resources,
    it always seemed to have resources, and when the OS had gone to hell in
    a hand basket, you could still "attempt to do stuff" in Task Manager.
    That's all changed. In WinXP you could alt-tab, even when the OS was in
    serious trouble. W10/W11 just die instantly, when even a tiny bit of
    smothering is applied :-) One of my favorite examples, was using
    ImageMagick one day, and OpenMP happened to be enabled (use multiple
    cores to open an image for display on the screen). OS froze... instantly.
    As instantly as you can envisage "instantly" means. One frame time. Dead.
    Oh, the electrons are flying around in there, but "nobody is home".
    It's not a crash. It's a deadlock, a form of software deadly embrace.

    When an OS has no observational capability, we can only dream as
    sheep dream, about what is the matter. Gone are the days of having
    dual CRT tubes with critical information recorded on the screen.
    In uni, when one of the students did a DOS attack on the mainframe,
    he stood by the window and watched the "free disk" counter decrement
    over a matter of 30 seconds or so, killing the mainframe. On a timeshare system, jobs are rotated in and out via that particular disk. Our student
    had used a primitive fork bomb, and the system operator (a "stable genius")
    had forgotten to enable a policy to prevent that :-) It was kinda a
    splash of cold water for the gentleman, to discover he had competition.
    The operator used to play chess on one of those CRTs.

    https://archive.computerhistory.org/resources/still-image/LLNL%20Computer%20Museum/102675044.03.01.lg.jpg

    The power meter on my computer, is the last vestige of observability.
    I may not know what is going on, but I know "something, is inside the machine".

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Hall@21:1/5 to All on Sat May 4 10:28:00 2024
    XPost: alt.usage.english, alt.english.usage

    In message <v14jj8$12jqr$1@dont-email.me>, Paul <nospam@needed.invalid>
    writes
    <big snip>
    The operating system is not a program. It is an executive.

    That brings back memories. The computer I used back in the 1970s, an ICL
    1900, actually called the core part of its OS "Executive" with a capital
    E.
    --
    John Hall
    "Acting is merely the art of keeping a large group of people
    from coughing."
    Sir Ralph Richardson (1902-83)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to John Hall on Sat May 4 14:51:31 2024
    XPost: alt.usage.english, alt.english.usage

    John Hall <john_nospam@jhall.co.uk> wrote:
    In message <v14jj8$12jqr$1@dont-email.me>, Paul <nospam@needed.invalid> writes
    <big snip>
    The operating system is not a program. It is an executive.

    That brings back memories. The computer I used back in the 1970s, an ICL 1900, actually called the core part of its OS "Executive" with a capital
    E.

    Yep, in the early 70s, I was using/supporting HP's 'mini' computers,
    running RTE, Real Time Executive.

    Later, the business side of HP had MPE, Multi Programming Excecutive.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to John Hall on Sat May 4 10:43:02 2024
    XPost: alt.usage.english, alt.english.usage

    On 5/4/2024 5:28 AM, John Hall wrote:
    In message <v14jj8$12jqr$1@dont-email.me>, Paul <nospam@needed.invalid> writes
    <big snip>
    The operating system is not a program. It is an executive.

    That brings back memories. The computer I used back in the 1970s,
    an ICL 1900, actually called the core part of its OS "Executive" with a capital E.

    There are some differences.

    Mainframes were "ball jugglers". They could support 500 users at once,
    by keeping 490 sessions "asleep". A limited number of users would be
    in "near orbit" and have access to CPU cycles. Perhaps one drive, or
    even, an entire Storage Director, took care of paging of jobs.

    This was managed with disk drives (and occasionally, if you were lucky,
    with a drum storage device).

    The difference on a personal computer, is there is no juggling of processes
    in the same way. The processes are stored in memory, and are "ready to run". The scheduler gives them slices. Some of the things in Task Manager, use
    zero cycles, they use nothing at all. They are "mostly silent". Only a few
    of the SVCHOSTs are busy little beavers. Some things related to security,
    might always have a busy stance.

    Modern Windows has taken to "suspending" some items, but it's unclear whether that ever pans out (actually helps a user). Some of the same states as were always there, are still present. The "zombie" state for example. A "zombie"
    is a process that did not get harvested properly, and might disappear on a reboot.

    And while early Windows had pagefile.sys for paging out of virtual memory, that's hardly ever used on machines potentially using SSD drives for storage. We really are reliant now, on gobs of main memory, embarrassing excess,
    for how the machine works. That's how my browser a few minutes ago, could
    be using 7GB of memory, while a web site recorded every line I read on a
    web page. They measured my "interest" in each article, my dwell time,
    whether I saw the adverts or not. They even interfere with my scroll
    bar, until I get annoyed and close the session.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 0rby@21:1/5 to Steve Hayes on Sat May 4 18:34:36 2024
    On 04/05/2024 06:01, Steve Hayes wrote:
    On Mon, 29 Apr 2024 06:33:38 -0700, "John C." <r9jmg0@yahoo.com>
    wrote:
    But I have a program called "Glary Utilities", which is not an
    application. It just helps the computer to run better.


    Adding more software to Windows often makes it run slower. Especially if
    said software adds yet another background task that runs al the time
    regardless of if you are using the software or not.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 0rby@21:1/5 to All on Sat May 4 18:46:22 2024
    I have seen advertisements for "solutions", but they never tell you
    what problem they are claiming to be able to solve.


    You have just reminded me of this...

    Terence McKenna: "Technologies do not always increase peoples options! Sometimes they decrease peoples options. One may not want a car, with
    that sort of equipment, but one has no choice.

    The next point is, technology does not always solve important problems.
    We like to think that technological innovation will almost always lead
    to an enriched and enhanced life. But very often, technological progress
    does not progress it’s self to important problems, but rather to be
    worse. And yet we proceed anyway, in spite of the fact that in solving a trivial problem, we may be creating a greater problem than the problem
    we solve.

    For example, we now have in America the issue of weather or not we
    should spend billions of dollars for something called a super
    information highway.

    Well, if we ask our authorities on this, the same question I put to the cartels, we get some curious answers! What is the problem to which this
    super information highway will be a solution?

    One of the answers you’ll get is ”well, we now have available only 60 television channels. With the super information highway we will have to
    have 500, maybe even a 1000”.

    Is this a problem that really needs a solution?

    We have to ask this question and several others, about technological change.

    Because technological change is almost always what I call a faustian
    bargain “it giveth, and it taketh away."

    Good old Terence...

    https://www.sheldrake.org/audios/the-sheldrake-mckenna-abraham-trialogues

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Steve Hayes on Sat May 4 19:25:17 2024
    XPost: alt.usage.english, alt.english.usage

    On 5/4/2024 12:56 PM, Steve Hayes wrote:
    On Sat, 4 May 2024 02:11:51 -0400, Paul <nospam@needed.invalid> wrote:

    On 5/4/2024 1:01 AM, Steve Hayes wrote:
    Yes, they're all programs, but some are applications, like word
    processors, spreadsheets, databases etc.

    But I have a program called "Glary Utilities", which is not an
    application. It just helps the computer to run better. Likewise, the
    operating system is a program, but not an application.

    The operating system is not a program. It is an executive.

    In MyEnglish the definition of a program is "a set of instructions to
    operate a computer". Is this "Executive" not that?

    My first computer had an OS in ROM, with built-in BASIC, with which
    you could write other programs and save them and their data on tape,
    but all were programs. With a couple of add-ons you could have a DOS
    (CP/M), and save stuff on floppy disks, but that by-passed the BASIC
    in ROM, so you had to get programming languages that ran under CP/M,
    but whether they loaded from ROM, tape or disks, all there sets of instructions tomake the computer do different things.

    If you boot a memtest floppy, that is a single program that
    runs 100% of the time. Nobody tells it to do anything.
    It is the boss. All machine resources are available.

    If it wanted to erase your hard drive, nothing would stop it.

    The frame buffer for the graphics are at a fixed address. It
    takes fixed font pixmaps of characters and writes them to the
    frame buffer. That makes the character display.

    The memory is linear mapped. The virtual address equals the physical address. It could be using "Giant Pages", a 1GB mapping, as you might notice the
    program has a fixation with 1GB and 2GB chunks as it runs. Loading the
    mapper, is an executive-type function.

    You can see then, that it is running the restaurant all by itself.
    It's taking the orders (from the keyboard), it's running into the
    back of the restaurant to the kitchen, it is putting steaks and
    veggies on the table and cooking the steak, it's doing all the jobs.
    That means, when the guy wrote the program, he had to "think of
    all the details", not just "some of the details". Well, that's what
    happens when you have No Executive.

    *******

    When a program runs in an OS, a lot of details have been worked out.
    The program "just sits down and eats". It worries not about the
    grill, about the dish washer person, about the staff to carry the
    orders to the tables and so on. The memory mapper is set defensively
    by the executive, to prevent "shenanigans" (self-modifying code is
    not allowed, and has not been allowed for a lot of years). This
    means the code segment is read only, and after the loader has
    loaded it (written to it), the mapping the program sees for its
    code is read-only.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Moylan@21:1/5 to Steve Hayes on Sun May 5 13:59:57 2024
    XPost: alt.usage.english, alt.english.usage

    On 05/05/24 02:56, Steve Hayes wrote:
    On Sat, 4 May 2024 02:11:51 -0400, Paul <nospam@needed.invalid>
    wrote:

    On 5/4/2024 1:01 AM, Steve Hayes wrote:
    Yes, they're all programs, but some are applications, like word
    processors, spreadsheets, databases etc.

    But I have a program called "Glary Utilities", which is not an
    application. It just helps the computer to run better. Likewise,
    the operating system is a program, but not an application.

    The operating system is not a program. It is an executive.

    In MyEnglish the definition of a program is "a set of instructions to
    operate a computer". Is this "Executive" not that?

    It's all software, of course, but a person writing operating systems
    code has to be aware of hardware features that the average applications programmer never comes into contact with. For certain functions, e.g.
    thread switching, it might be necessary to descend into assembly language.

    There's another distinction that occurs to me. An application program
    has a beginning, a middle, and an end. It does it job and then
    terminates. The operating system never terminates until the whole
    computer is shut down.

    The distinction is becoming fuzzier now that some operating systems are
    built in layers. The bottom-level operating system is probably small and
    does only some basic things. (Typically thread switching and memory management.) Then another operating system is built on top of that. And
    maybe even another on top of that.

    --
    Peter Moylan http://www.pmoylan.org
    Newcastle, NSW

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From lar3ryca@21:1/5 to Steve Hayes on Sat May 4 23:40:14 2024
    XPost: alt.usage.english, alt.english.usage

    On 2024-05-04 10:56, Steve Hayes wrote:
    On Sat, 4 May 2024 02:11:51 -0400, Paul <nospam@needed.invalid> wrote:

    On 5/4/2024 1:01 AM, Steve Hayes wrote:
    Yes, they're all programs, but some are applications, like word
    processors, spreadsheets, databases etc.

    But I have a program called "Glary Utilities", which is not an
    application. It just helps the computer to run better. Likewise, the
    operating system is a program, but not an application.

    The operating system is not a program. It is an executive.

    In MyEnglish the definition of a program is "a set of instructions to
    operate a computer". Is this "Executive" not that?

    I agree with you on that one, Steve.

    My first computer had an OS in ROM, with built-in BASIC, with which
    you could write other programs and save them and their data on tape,
    but all were programs.

    The first computer I worked on, though it was not called a computer, but
    rather an 'Electronic Accounting Machine'. I 'wrote' programs on it by
    plugging wires into a board that made contact with relays.

    It was definitely a computer, though, stepping through programs, doing
    math, branching on tested conditions, and reading and writing to and
    from I/O devices.

    I worked on that for about two years, at which time I started working on
    a different set of machines, and found out that a program could actually
    be stored in a memory.

    With a couple of add-ons you could have a DOS
    (CP/M), and save stuff on floppy disks, but that by-passed the BASIC
    in ROM, so you had to get programming languages that ran under CP/M,
    but whether they loaded from ROM, tape or disks, all there sets of instructions tomake the computer do different things.



    --
    A computer won't stop you being an idiot,
    but it'll make you a faster, better idiot

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Moylan@21:1/5 to All on Sun May 5 18:15:28 2024
    XPost: alt.usage.english, alt.english.usage

    On 05/05/24 15:40, lar3ryca wrote:

    The first computer I worked on, though it was not called a computer,
    but rather an 'Electronic Accounting Machine'. I 'wrote' programs on
    it by plugging wires into a board that made contact with relays.

    It was definitely a computer, though, stepping through programs,
    doing math, branching on tested conditions, and reading and writing
    to and from I/O devices.

    I worked on that for about two years, at which time I started
    working on a different set of machines, and found out that a program
    could actually be stored in a memory.

    We take memory for granted now, but it took a while to get it right.
    Looking back, the ideas of having main memory on a rotating drum or in
    columns of mercury sound incredible crude.

    To make computer memory practical, the electronics people had to learn
    how to put transistors on semiconductor chips. You can also build
    flip-flops with vacuum tubes, but vacuum tubes already become awkward
    once you have a few hundred of them.

    In my student days, and for some time afterwards, I used the plugboard approach, but that was with analogue computers. Those were very good at
    solving differential equations, but they died out through not being sufficiently scalable.

    --
    Peter Moylan http://www.pmoylan.org
    Newcastle, NSW

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bertel Lund Hansen@21:1/5 to Steve Hayes on Sun May 5 11:28:19 2024
    XPost: alt.usage.english, alt.english.usage

    Steve Hayes wrote:

    In MyEnglish the definition of a program is "a set of instructions to
    operate a computer". Is this "Executive" not that?

    It's mine too. If you operate with a class called "executives" (or
    OS's), it's just a subset of the programs.

    --
    Bertel
    Kolt, Denmark

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Lloyd@21:1/5 to All on Sun May 5 14:02:30 2024
    XPost: alt.usage.english, alt.english.usage

    [snip]


    If you boot a memtest floppy, that is a single program that
    runs 100% of the time. Nobody tells it to do anything.
    It is the boss. All machine resources are available.

    If it wanted to erase your hard drive, nothing would stop it.

    There would be something if you had a real write-protect switch (not one
    of those lying ones that software can just ignore).

    [snip]


    --
    Mark Lloyd
    http://notstupid.us/

    "If there is a supreme being, he's crazy." -- Marlene Dietrich
    (1901-1992), quoted in Rave magazine, November 1986

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Carmody@21:1/5 to mayayana@invalid.nospam on Sun May 5 23:40:10 2024
    XPost: alt.usage.english, alt.english.usage

    Newyana2 <mayayana@invalid.nospam> writes:
    On Windows it's always been "programs". Only some
    programmers say "application". (It could be worse. For
    awhile people were talking about their programming
    projects as "solutions".)

    So Windows 3.0 never had UAEs - Unexpected Application Errors? (And of
    course, none of the ".exe" files were ever called "executables" either?)
    "Apps" is quite well established in Windows, the oft derided "Hungarian Notation" had an "Apps Hungarian" flavour used in the Apps Division,
    in contrast to "System Hungarian" used in the Systems Division.

    Phil
    --
    We are no longer hunters and nomads. No longer awed and frightened, as we have gained some understanding of the world in which we live. As such, we can cast aside childish remnants from the dawn of our civilization.
    -- NotSanguine on SoylentNews, after Eugen Weber in /The Western Tradition/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Steve Hayes@21:1/5 to gadekryds@lundhansen.dk on Mon May 6 06:02:19 2024
    XPost: alt.usage.english, alt.english.usage

    On Sun, 5 May 2024 11:28:19 +0200, Bertel Lund Hansen
    <gadekryds@lundhansen.dk> wrote:

    Steve Hayes wrote:

    In MyEnglish the definition of a program is "a set of instructions to
    operate a computer". Is this "Executive" not that?

    It's mine too. If you operate with a class called "executives" (or
    OS's), it's just a subset of the programs.

    And all programs execute instructions (and then, of course, there are
    the executioners in another thread on aue).

    In low-level operating systems, the instructions are given by the
    programmer, rather than the user. From the point of view of the user,
    the most common instruction given by a user to the OS is to run an
    app, and to exit the app when the user has finished with it.



    --
    Steve Hayes from Tshwane, South Africa
    Web: http://www.khanya.org.za/stevesig.htm
    Blog: http://khanya.wordpress.com
    E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Steve Hayes@21:1/5 to peter@pmoylan.org.invalid on Mon May 6 05:56:10 2024
    XPost: alt.usage.english, alt.english.usage

    On Sun, 5 May 2024 13:59:57 +1000, Peter Moylan
    <peter@pmoylan.org.invalid> wrote:

    On 05/05/24 02:56, Steve Hayes wrote:
    On Sat, 4 May 2024 02:11:51 -0400, Paul <nospam@needed.invalid>
    wrote:

    On 5/4/2024 1:01 AM, Steve Hayes wrote:
    Yes, they're all programs, but some are applications, like word
    processors, spreadsheets, databases etc.

    But I have a program called "Glary Utilities", which is not an
    application. It just helps the computer to run better. Likewise,
    the operating system is a program, but not an application.

    The operating system is not a program. It is an executive.

    In MyEnglish the definition of a program is "a set of instructions to
    operate a computer". Is this "Executive" not that?

    It's all software, of course, but a person writing operating systems
    code has to be aware of hardware features that the average applications >programmer never comes into contact with. For certain functions, e.g.
    thread switching, it might be necessary to descend into assembly language.

    There's another distinction that occurs to me. An application program
    has a beginning, a middle, and an end. It does it job and then
    terminates. The operating system never terminates until the whole
    computer is shut down.

    The distinction is becoming fuzzier now that some operating systems are
    built in layers. The bottom-level operating system is probably small and
    does only some basic things. (Typically thread switching and memory >management.) Then another operating system is built on top of that. And
    maybe even another on top of that.

    Yes, that supports the distinction I am trying to make: an operating
    system, whether it is built on top of another one or not, and an app
    are both programs, but not all programs are apps. And yes, both are
    software as well.

    US English is somewhat at a disadvantage here, be cause they use
    "program" in a wider sense, so they often have to add "software" to
    it, to distinguish a "software program" from other kinds of what the
    rest of us would call "programmes", like TV programmes, sports events programmes etc.



    --
    Steve Hayes from Tshwane, South Africa
    Web: http://www.khanya.org.za/stevesig.htm
    Blog: http://khanya.wordpress.com
    E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bertel Lund Hansen@21:1/5 to Steve Hayes on Mon May 6 07:37:11 2024
    XPost: alt.usage.english, alt.english.usage

    Steve Hayes wrote:

    US English is somewhat at a disadvantage here, be cause they use
    "program" in a wider sense, so they often have to add "software" to
    it, to distinguish a "software program" from other kinds of what the
    rest of us would call "programmes", like TV programmes, sports events programmes etc.

    Danish has the exact same 'problem' - which isn't really a problem since context usually makes the meaning clear.


    --
    Bertel
    Kolt, Denmark

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From lar3ryca@21:1/5 to Peter Moylan on Sun May 5 23:18:09 2024
    XPost: alt.usage.english, alt.english.usage

    On 2024-05-05 02:15, Peter Moylan wrote:
    On 05/05/24 15:40, lar3ryca wrote:

    The first computer I worked on, though it was not called a computer,
    but rather an 'Electronic Accounting Machine'. I 'wrote' programs on
    it by plugging wires into a board that made contact with relays.

    It was definitely a computer, though, stepping through programs,
    doing math, branching on tested conditions, and reading and writing
    to and from I/O devices.

    I worked on that for about two years, at which time I started
    working on a different set of machines, and found out that a program
    could actually be stored in a memory.

    We take memory for granted now, but it took a while to get it right.
    Looking back, the ideas of having main memory on a rotating drum or in columns of mercury sound incredible crude.

    How about memory on acoustic delay lines?
    When I worked for CDC, I sometimes got called to Allstate (the insurance folks), to repair the terminals.

    The memory on those consisted of modules containing spirals of what
    might best be described as 'piano wire'. Bits were input by giving the
    wire a quick twist (twist, then reset back to idle). That generated
    something like a shock wave that travelled around the spiral to a
    transducer on the other end, I can't remember if it twisted one
    direction for a '1' and the other direction for a '0', or if it only
    used one direction of twist, relying on framing pulses and time between
    bit to differentiate between them.

    Nor do I remember the amount of data it could hold, probably in the
    order of a few hundred bytes.

    Of course, once the data got to the end and was read, it had to be
    re-sent again, unless that particular packet had to be changed, at which
    time it was not re-sent, and a new packet was sent in its place.

    To make computer memory practical, the electronics people had to learn
    how to put transistors on semiconductor chips. You can also build
    flip-flops with vacuum tubes, but vacuum tubes already become awkward
    once you have a few hundred of them.

    In my student days, and for some time afterwards, I used the plugboard approach, but that was with analogue computers. Those were very good at solving differential equations, but they died out through not being sufficiently scalable.

    The plugboards I spoke of were for programming a digital computer, When
    a plugboard was mounted, pressing "Start" sent a 48V pulse out of the
    'start hub', and into a 'program step' hub (almost always 'program step
    1'. This would pick up a relay, which would cause voltage to be applied
    to hubs called 'operation, 'in word 1', 'inword 2', and 'out word'.

    That would, in turn, call on the electronics (SMS cards) to perform the operation.

    As for analog computers, my step-brother and I bought one, but it was
    pretty simple, consisting og circuits to do math, input via dials (potentiometers), and output on a voltmeter.


    When a step was active,

    --
    Whose idea was it to put an "S" in the word "lisp"?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From J. J. Lodder@21:1/5 to larry@invalid.ca on Mon May 6 13:52:52 2024
    XPost: alt.usage.english, alt.english.usage

    lar3ryca <larry@invalid.ca> wrote:

    On 2024-05-05 02:15, Peter Moylan wrote:
    On 05/05/24 15:40, lar3ryca wrote:

    The first computer I worked on, though it was not called a computer,
    but rather an 'Electronic Accounting Machine'. I 'wrote' programs on
    it by plugging wires into a board that made contact with relays.

    It was definitely a computer, though, stepping through programs,
    doing math, branching on tested conditions, and reading and writing
    to and from I/O devices.

    I worked on that for about two years, at which time I started
    working on a different set of machines, and found out that a program
    could actually be stored in a memory.

    We take memory for granted now, but it took a while to get it right. Looking back, the ideas of having main memory on a rotating drum or in columns of mercury sound incredible crude.

    How about memory on acoustic delay lines?
    When I worked for CDC, I sometimes got called to Allstate (the insurance folks), to repair the terminals.

    The memory on those consisted of modules containing spirals of what
    might best be described as 'piano wire'. Bits were input by giving the
    wire a quick twist (twist, then reset back to idle). That generated
    something like a shock wave that travelled around the spiral to a
    transducer on the other end, I can't remember if it twisted one
    direction for a '1' and the other direction for a '0', or if it only
    used one direction of twist, relying on framing pulses and time between
    bit to differentiate between them.

    That's a bit primitive.
    One of the first bulk computer memories,
    used by Alan Turing himself, was a mercury delay line.
    Bits were stored as sound pulses in a column of mercury.

    Just as with a hard drive the computer had to wait
    for the right part of the bit string to pass by.
    I would have to look up how long its bit string could be,

    Jan

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ken Blake@21:1/5 to hayesstw@telkomsa.net on Mon May 6 07:15:07 2024
    XPost: alt.usage.english, alt.english.usage

    On Mon, 06 May 2024 05:56:10 +0200, Steve Hayes
    <hayesstw@telkomsa.net> wrote:

    US English is somewhat at a disadvantage here, be cause they use
    "program" in a wider sense, so they often have to add "software" to
    it, to distinguish a "software program" from other kinds of what the
    rest of us would call "programmes", like TV programmes, sports events >programmes etc.



    That used to be true, but not so much anymore. It was in 1962, when I
    was out of work, and I answered an ad for "Programmer Trainee --
    College Graduate, Any Major" for a higher salary than I had ever had.
    I didn't know what a programmer was, but I thought it referred to TV
    or Radio programming.

    I didn't get the job, but I soon started a computer programming course
    and got a programming job soon afterward.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to J. J. Lodder on Mon May 6 14:47:14 2024
    XPost: alt.usage.english, alt.english.usage

    On 5/6/2024 7:52 AM, J. J. Lodder wrote:
    lar3ryca <larry@invalid.ca> wrote:

    On 2024-05-05 02:15, Peter Moylan wrote:
    On 05/05/24 15:40, lar3ryca wrote:

    The first computer I worked on, though it was not called a computer,
    but rather an 'Electronic Accounting Machine'. I 'wrote' programs on
    it by plugging wires into a board that made contact with relays.

    It was definitely a computer, though, stepping through programs,
    doing math, branching on tested conditions, and reading and writing
    to and from I/O devices.

    I worked on that for about two years, at which time I started
    working on a different set of machines, and found out that a program
    could actually be stored in a memory.

    We take memory for granted now, but it took a while to get it right.
    Looking back, the ideas of having main memory on a rotating drum or in
    columns of mercury sound incredible crude.

    How about memory on acoustic delay lines?
    When I worked for CDC, I sometimes got called to Allstate (the insurance
    folks), to repair the terminals.

    The memory on those consisted of modules containing spirals of what
    might best be described as 'piano wire'. Bits were input by giving the
    wire a quick twist (twist, then reset back to idle). That generated
    something like a shock wave that travelled around the spiral to a
    transducer on the other end, I can't remember if it twisted one
    direction for a '1' and the other direction for a '0', or if it only
    used one direction of twist, relying on framing pulses and time between
    bit to differentiate between them.

    That's a bit primitive.
    One of the first bulk computer memories,
    used by Alan Turing himself, was a mercury delay line.
    Bits were stored as sound pulses in a column of mercury.

    Just as with a hard drive the computer had to wait
    for the right part of the bit string to pass by.
    I would have to look up how long its bit string could be,

    Jan


    https://www.oxfordreference.com/display/10.1093/oi/authority.20110803095708310

    "quartz crystals were used as transducers and the ultrasonic pulses were
    passed along a tube of mercury about 5 feet (1.5 meters) in length.
    The delay was approximately 1 millisecond but it enabled nearly 1000 pulses
    to be stored. Later acoustic memory used magnetostrictive transducers and
    nickel-iron wire, with the electrical signals converted into stress waves."

    A thousand bits, isn't a lot.

    Some of the first SRAM (suitable for home computer projects)
    were 256x4 bits and 1024x1 bit static RAM running at 5 volts.
    "Beautiful stuff". Compared to the dreadful DRAM of the day.
    And just one of those chips, stores the same stuff as a delay
    line, and also offers "random" access, so is a lot faster.

    My breadboarded home computer used (4) 256x4 chips. As a 256x16 array (16 bit CPU).

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Moylan@21:1/5 to Paul on Tue May 7 10:09:03 2024
    XPost: alt.usage.english, alt.english.usage

    On 07/05/24 04:47, Paul wrote:

    Some of the first SRAM (suitable for home computer projects) were
    256x4 bits and 1024x1 bit static RAM running at 5 volts. "Beautiful
    stuff". Compared to the dreadful DRAM of the day. And just one of
    those chips, stores the same stuff as a delay line, and also offers
    "random" access, so is a lot faster.

    My breadboarded home computer used (4) 256x4 chips. As a 256x16
    array (16 bit CPU).

    My first computer had an 8080A processor (very new at the time) and 1k
    bytes of RAM. The "motherboard" was a whole lot of wire-wrap sockets,
    which took ages to wire up. I was very proud of the metal chassis that I
    built as well, with eight switches for input[1] and eight LED lights, plus
    a couple of pushbuttons. The switches were mainly for loading a program
    into memory, although I later wrote a loader that took the data from an
    audio cassette tape. Then, with the aid of a few resistors, I turned the
    front panel leds into a D/A converter. With the analogue output
    connected to an amplifier, I got the computer to play 3-part music.

    [1] Or possibly 24 switches. I've now forgotten whether I had separate
    address and data switches.

    The front panel bore the logo "IDSFA-80". If anyone asked what IDSFA
    stood for, I could tell them it doesn't stand for anything.

    --
    Peter Moylan http://www.pmoylan.org
    Newcastle, NSW

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to All on Mon May 6 22:14:42 2024
    XPost: alt.usage.english, alt.english.usage

    On 5/6/2024 9:18 PM, lar3ryca wrote:
    On 2024-05-06 12:47, Paul wrote:
    On 5/6/2024 7:52 AM, J. J. Lodder wrote:
    lar3ryca <larry@invalid.ca> wrote:

    On 2024-05-05 02:15, Peter Moylan wrote:
    On 05/05/24 15:40, lar3ryca wrote:

    The first computer I worked on, though it was not called a computer, >>>>>> but rather an 'Electronic Accounting Machine'. I 'wrote' programs on >>>>>> it by plugging wires into a board that made contact with relays.

    It was definitely a computer, though, stepping through programs,
    doing math, branching on tested conditions, and reading and writing >>>>>> to and from I/O devices.

    I worked on that for about two years, at which time I started
    working on a different set of machines, and found out that a program >>>>>> could actually be stored in a memory.

    We take memory for granted now, but it took a while to get it right. >>>>> Looking back, the ideas of having main memory on a rotating drum or in >>>>> columns of mercury sound incredible crude.

    How about memory on acoustic delay lines?
    When I worked for CDC, I sometimes got called to Allstate (the insurance >>>> folks), to repair the terminals.

    The memory on those consisted of modules containing spirals of what
    might best be described as 'piano wire'. Bits were input by giving the >>>> wire a quick twist (twist, then reset back to idle). That generated
    something like a shock wave that travelled around the spiral to a
    transducer on the other end, I can't remember if it twisted one
    direction for a '1' and the other direction for a '0', or if it only
    used one direction of twist, relying on framing pulses and time between >>>> bit to differentiate between them.

    That's a bit primitive.
    One of the first bulk computer memories,
    used by Alan Turing himself, was a mercury delay line.
    Bits were stored as sound pulses in a column of mercury.

    Just as with a hard drive the computer had to wait
    for the right part of the bit string to pass by.
    I would have to look up how long its bit string could be,

    Jan


    https://www.oxfordreference.com/display/10.1093/oi/authority.20110803095708310

        "quartz crystals were used as transducers and the ultrasonic pulses were
         passed along a tube of mercury about 5 feet (1.5 meters) in length. >>      The delay was approximately 1 millisecond but it enabled nearly 1000 pulses
         to be stored. Later acoustic memory used magnetostrictive transducers and
         nickel-iron wire, with the electrical signals converted into stress waves."

    A thousand bits, isn't a lot.

    Some of the first SRAM (suitable for home computer projects)
    were 256x4 bits and 1024x1 bit static RAM running at 5 volts.
    "Beautiful stuff". Compared to the dreadful DRAM of the day.
    And just one of those chips, stores the same stuff as a delay
    line, and also offers "random" access, so is a lot faster.

    My breadboarded home computer used (4) 256x4 chips. As a 256x16 array (16 bit CPU).

    And my breadboard computer used 8 1024x1 chips (2501?), and that was also my first computer. The memory cost me $85.00 CAD at the time, about 1975 if I remember correctly).


    That stuff was a lot easier to work with, than the DRAM of the day.
    The little SRAM chips meant that anybody could build a computer. You
    didn't need Einstein on the team, to do the DRAM. I think my SRAM were
    between $2 and $3, but when you had 64 of those on a memory card,
    the money adds up quickly. I only needed a few of the chips to get the prototype running.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From lar3ryca@21:1/5 to Paul on Mon May 6 19:18:25 2024
    XPost: alt.usage.english, alt.english.usage

    On 2024-05-06 12:47, Paul wrote:
    On 5/6/2024 7:52 AM, J. J. Lodder wrote:
    lar3ryca <larry@invalid.ca> wrote:

    On 2024-05-05 02:15, Peter Moylan wrote:
    On 05/05/24 15:40, lar3ryca wrote:

    The first computer I worked on, though it was not called a computer, >>>>> but rather an 'Electronic Accounting Machine'. I 'wrote' programs on >>>>> it by plugging wires into a board that made contact with relays.

    It was definitely a computer, though, stepping through programs,
    doing math, branching on tested conditions, and reading and writing
    to and from I/O devices.

    I worked on that for about two years, at which time I started
    working on a different set of machines, and found out that a program >>>>> could actually be stored in a memory.

    We take memory for granted now, but it took a while to get it right.
    Looking back, the ideas of having main memory on a rotating drum or in >>>> columns of mercury sound incredible crude.

    How about memory on acoustic delay lines?
    When I worked for CDC, I sometimes got called to Allstate (the insurance >>> folks), to repair the terminals.

    The memory on those consisted of modules containing spirals of what
    might best be described as 'piano wire'. Bits were input by giving the
    wire a quick twist (twist, then reset back to idle). That generated
    something like a shock wave that travelled around the spiral to a
    transducer on the other end, I can't remember if it twisted one
    direction for a '1' and the other direction for a '0', or if it only
    used one direction of twist, relying on framing pulses and time between
    bit to differentiate between them.

    That's a bit primitive.
    One of the first bulk computer memories,
    used by Alan Turing himself, was a mercury delay line.
    Bits were stored as sound pulses in a column of mercury.

    Just as with a hard drive the computer had to wait
    for the right part of the bit string to pass by.
    I would have to look up how long its bit string could be,

    Jan


    https://www.oxfordreference.com/display/10.1093/oi/authority.20110803095708310

    "quartz crystals were used as transducers and the ultrasonic pulses were
    passed along a tube of mercury about 5 feet (1.5 meters) in length.
    The delay was approximately 1 millisecond but it enabled nearly 1000 pulses
    to be stored. Later acoustic memory used magnetostrictive transducers and
    nickel-iron wire, with the electrical signals converted into stress waves."

    A thousand bits, isn't a lot.

    Some of the first SRAM (suitable for home computer projects)
    were 256x4 bits and 1024x1 bit static RAM running at 5 volts.
    "Beautiful stuff". Compared to the dreadful DRAM of the day.
    And just one of those chips, stores the same stuff as a delay
    line, and also offers "random" access, so is a lot faster.

    My breadboarded home computer used (4) 256x4 chips. As a 256x16 array (16 bit CPU).

    And my breadboard computer used 8 1024x1 chips (2501?), and that was
    also my first computer. The memory cost me $85.00 CAD at the time, about
    1975 if I remember correctly).

    --
    Whose idea was it to put an "S" in the word "lisp"?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From J. J. Lodder@21:1/5 to Paul on Tue May 7 10:41:44 2024
    XPost: alt.usage.english, alt.english.usage

    Paul <nospam@needed.invalid> wrote:

    On 5/6/2024 7:52 AM, J. J. Lodder wrote:
    lar3ryca <larry@invalid.ca> wrote:

    On 2024-05-05 02:15, Peter Moylan wrote:
    [-]
    We take memory for granted now, but it took a while to get it right.
    Looking back, the ideas of having main memory on a rotating drum or in >>> columns of mercury sound incredible crude.

    How about memory on acoustic delay lines?
    When I worked for CDC, I sometimes got called to Allstate (the insurance >> folks), to repair the terminals.

    The memory on those consisted of modules containing spirals of what
    might best be described as 'piano wire'. Bits were input by giving the
    wire a quick twist (twist, then reset back to idle). That generated
    something like a shock wave that travelled around the spiral to a
    transducer on the other end, I can't remember if it twisted one
    direction for a '1' and the other direction for a '0', or if it only
    used one direction of twist, relying on framing pulses and time between
    bit to differentiate between them.

    That's a bit primitive.
    One of the first bulk computer memories,
    used by Alan Turing himself, was a mercury delay line.
    Bits were stored as sound pulses in a column of mercury.

    Just as with a hard drive the computer had to wait
    for the right part of the bit string to pass by.
    I would have to look up how long its bit string could be,

    Jan


    https://www.oxfordreference.com/display/10.1093/oi/authority.20110803095708310

    "quartz crystals were used as transducers and the ultrasonic pulses were
    passed along a tube of mercury about 5 feet (1.5 meters) in length.
    The delay was approximately 1 millisecond but it enabled nearly 1000
    pulses to be stored. Later acoustic memory used magnetostrictive
    transducers and nickel-iron wire, with the electrical signals
    converted into stress waves."

    A thousand bits, isn't a lot.

    Maybe it was, in 1949. [1]
    Trivia: I happened to remember this particular tidbit of information
    from the witty chapter title in Hodges' biography of Alan Turing:
    "Mercury Delayed,

    Jan

    [1] Mercury delay lines had the great advantage
    that they were already available, from radar applications

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Char Jackson@21:1/5 to All on Tue May 14 15:31:14 2024
    XPost: alt.usage.english, alt.english.usage

    On Tue, 7 May 2024 10:09:03 +1000, Peter Moylan <peter@pmoylan.org.invalid> wrote:

    My first computer had an 8080A processor (very new at the time) and 1k
    bytes of RAM.
    <snip>

    The front panel bore the logo "IDSFA-80". If anyone asked what IDSFA
    stood for, I could tell them it doesn't stand for anything.

    Nice. I see what you did there, although it took a second.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From lar3ryca@21:1/5 to Char Jackson on Tue May 14 22:40:50 2024
    XPost: alt.usage.english, alt.english.usage

    On 2024-05-14 14:31, Char Jackson wrote:
    On Tue, 7 May 2024 10:09:03 +1000, Peter Moylan <peter@pmoylan.org.invalid> wrote:

    My first computer had an 8080A processor (very new at the time) and 1k
    bytes of RAM.
    <snip>

    The front panel bore the logo "IDSFA-80". If anyone asked what IDSFA
    stood for, I could tell them it doesn't stand for anything.

    Nice. I see what you did there, although it took a second.

    Many years ago, the company I worked for played a softball game. For the occasion, the manager bought us all T-shirts with the company name on
    them. We all had the choice of what name to put on the back.

    I chose 'ITYNA'.

    About halfway through the game, one of the players on the opponents team approached me and asked "Isn't your name 'Phillips'?"
    I answered "Yes", and she asked "So why does your shirt have "ITYNA" on
    it (she pronounced it out, "Iteena"), and I said "I thought You'd Never
    Ask".

    After a few rounds of "But I am asking", and " I thought you'd never
    ask", she suddenly got it.

    --
    The day after tomorrow is the third day of the rest of your life.
    ~ George Carlin

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)