View Single Post
  #3  
Old May 22nd 14, 03:09 AM posted to microsoft.public.windowsxp.hardware
Mike Rumble
external usenet poster
 
Posts: 2
Default "Haswell" and Windows XP

Lots of good information you've posted.

Originally there seemed little hope that XP would continue on new hardware,
but it now looks like that may not be the case. With the latest security
updates being ported over from POS 2009, we XP users could be around for
another 10 years or more.

Thank you.


"Paul" wrote in message
...
Drivers are typically for the chipset.

The processor itself, uses "standard looking" logic blocks,
for which the OS will already have a default driver. For
example, something like "pci.sys" might pick up a few of
those entries.

If your Haswell has a built-in GPU, then that might require
a video driver. The responsibility there is split, with
signal buffering in the chipset (HDMI connector driven by
the PCH). But the 16 EU GPU might need a video driver, so
all the features, DVXA for video decoder or the like,
are exposed.

Intel HD 4000/5000 Graphics, DirectX 11.1

Now, all of that being said, the driver list looks nice.
You will need to look inside each driver file, to determine
if they are lying to you. For example, I could put a Windows 8
driver file in the WinXP list, to make you think there was
an actual WinXP driver. I would download all the driver
files, and inspect them (look at the INF files) and
see if the drivers are consistent with a WinXP install.

VGA XP_32_bit.zip / xp_64_bit.zip

That one is rather small, so I can take a look.

At least a cursory examination, doesn't suggest
an inappropriate attempt. It looks legit. If I was
spending the money, I'd check all of them. Note
that the above INF is dated Sept.2013, to give some
idea when it was created for that specific package.

Paul



Ads