XPost: alt.comp.os.windows-10
From: nospam@needed.invalid
On Fri, 1/30/2026 3:29 PM, ...w¡ñ§±¤ñ wrote:
> Paul wrote on 1/30/2026 3:20 AM:
>
>> And the hosting softwares are not always properly labeled.
>> One developer said "we leave the old OSes behind when
>> they go out of support, but we don't state anywhere whether
>> the software works or not". I think they do in fact know
>> it's a trap. (I had the same problem with this attitude,
>> around copies of Wireshark, where when you needed OS
>> version info, there was no hint which one was OK.)
>>
>> I suppose it's just human nature to torture people
>> who aren't using "The New Shiny".
>>
>> Paul
>>
>>
>
> From Wireshark documenatation
>
> User Guide
> 2. Who should read this document?
> The intended audience of this book is anyone using Wireshark.
>
> User Manual
> Chapter 1.2.1. Microsoft Windows
> Wireshark should support any version of Windows that is still within its
extended support lifetime. At the time of writing this includes Windows 11,
10, Server 2022, Server 2019, and Server 2016. It also requires the following:
>
> The Universal C Runtime. This is included with Windows 10 and Windows Server
2019 and is installed automatically on earlier versions if Microsoft Windows
Update is enabled. Otherwise you must install KB2999226 or KB3118401.
> Any modern 64-bit Intel or Arm processor.
> 500 MB available RAM. Larger capture files require more RAM.
> 500 MB available disk space. Capture files require additional disk space.
> Any modern display. 1280 × 1024 or higher resolution is recommended.
Wireshark will make use of HiDPI or Retina resolutions if available. Power
users will find multiple monitors useful.
> A supported network card for capturing
> Ethernet. Any card supported by Windows should work. See the wiki pages on
Ethernet capture and offloading for issues that may affect your environment.
> 802.11. See the Wireshark wiki page. Capturing raw 802.11 information may be
difficult without special equipment.
> Other media. See https://wiki.wireshark.org/CaptureSetup/NetworkMedia.
>
> Older versions of Windows which are outside Microsoft’s extended lifecycle
support window are no longer supported. It is often difficult or impossible to
support these systems due to circumstances beyond our control, such as third
party libraries on
which we depend or due to necessary features that are only present in newer
versions of Windows such as hardened security or memory management.
>
>
> Note the first line...
> "Wireshark should support any version of Windows that is still within its
extended support lifetime."
> - it, in the same section it also states - "Older versions of Winodows
which are Microsoft's extended support window are no longer supported."
>
> That information, most likely, pre-dates the end of extended support for
Windows 10...but to be fair, it does not state the current version or earlier
will no longer function on Windows 10.
>
Well, actually, at the time, I was on MacOSX 10.2 or 10.3 and absolutely no
"Wireshark
versus MacOSX" information existed. I had to try them manually one at a time.
Really :-/
On MacOSX, the versioning was "really sharp", and only a couple files would
work,
and later releases might only work on 10.4 or whatever.
The people who do this work, they really know what is going on, but they
just don't give a fuck. Is it fair to have 10,000 people sitting there,
downloading unnecessary copies and wasting bandwidth, and time, to find
a version of your software that works ??? It boggled the mind.
I've noticed some of the smaller developers, self-hosted, who will drop
a few lines near the download section, to warn of trouble, or to indicate
how the product was compiled/built, and that's a great help.
Paul
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
