Re: Trouble finding drivers from Acer

On Sat, 3/8/2025 11:58 AM, micky wrote:
> In alt.comp.os.windows-10, on Sat, 8 Mar 2025 16:38:43 +0100, Marco
> Moock <[email protected]> wrote:
> 
>> Am 08.03.2025 10:28 Uhr schrieb micky:
>>
>>> 2) What was this about?  Why was it running me around to install a
>>> driver and then telling me no driver is installed but the yellow
>>> triangle is gone anyhow? 
>>
>> Please give the PCI id that is being shown in the device's properties.
> 
> Under Details/Properties there are a bunch of things that start with
> PCI, but no ID.   Under Hardware IDs there are
> PCI\VEN_8086&DEV_9CA2&SUBSYS_098A1025&REV_03
> PCI\VEN_8086&DEV_9CA2&SUBSYS_098A1025
> PCI\VEN_8086&DEV_9CA2&CC_0C0500
> PCI\VEN_8086&DEV_9CA2&CC_0C05
> Is it one of those? 

The chipset drivers add decorative text strings to Device Manager.

Think about it for a moment.

Would your computer boot, if it *TRUELY* did not have any chipset drivers ?

Of course not. That is evidence that the OS you installed, knows
a great deal about the care and feeding of x86 hardware.

If you still have the SMBUS driver, go have a look at it. Did it
have a .cat, a .inf, a DLL ? What ? There was no DLL ? Now look at the
.inf contents. Did the .inf contents have perky statements about
OS version, what service it was about to install, mention of a DLL,
the whole shebang ? No, it did not. It typically makes
reference to "nomachine.inf", which is a null installer, then
the "decorative text string" at the bottom of the "driver" gets installed.

    "...mention of a DLL ?"

NNNN          NNNN             OOOO
NNNNNNNN      NNNN           OOOO  OOOO
NNNN NNNN     NNNN        OOOO       OOOO
NNNN   NNNN   NNNN       OOOO         OOOO
NNNN    NNNNN  NNNN      OOOO           OOOO
MMMM      NNN   NNN      OOOO            OOOO
MMMM       NNNN NNN      OOOO            OOOO
MMMM        NNNNNNNN      OOOO          OOOO
MMMM         NNNN NN       OOO         OOO
MMMM          NNNNN          OOOOOOOOOOOOO
                                OOOOOO

At the top of this picture, is an improperly decorated Device Manager.
Paul has not had his push broom in here, cleaning up after these idiots.
The bottom picture, when Paul gets angry at bad workmanship (windows 10
actually used to install the correct chipset pack on its own), Paul
fixes it.

   [Picture]

    https://i.postimg.cc/W3w05Hv5/chipset-inf-X79-installed-example-bottom.gif

The "driver pack" in this case, was from here, checking my records. By going to
archive.org I could find the original web page for the download, and the
actual file is still on the Intel server (... if you can figure out a URL for it!).

   https://web.archive.org/web/20220120160547/https://www.intel.com/content/www/us/en/download/16356/intel-server-chipset-driver-for-windows-for-legacy-intel-server-board.html?v=t

      https://downloadmirror.intel.com/28531/eng/intel_chipset_win_10.1.17903.8106_pv.zip

Intel designed the PCH (Southbridge), assigned PNP numbers (the four digits
in the Intel-created ident string). The Microsoft decoration scheme, if it
even exists at all, doesn't show PNP because they don't care.  If I want
to, I can download the PDF file for the PCH, look for the four digit PNP
code, and find a register level definition of the logic block in question.
Trace-ability.

For Acer, the royalty OS provided with your product, is already
properly decorated (by some means, and to some level of quality).
Since a "decorative driver that loads text strings" never needs
an update, why would it be on the site ???

However, if you reinstall your OS, then get out your push broom, dude.

I do these just enough, so I can take pictures of "BEFORE" and "AFTER".

   Paul