Windows XP 32/64-bit/ and W2k on Haswell and Broadwell - Discussion

[Jakob99]

8 hours ago, K4sum1 said:

PCI\VEN_8086&DEV_1616&SUBSYS_062D1028&REV_09

I did also test x86, however it was Server 2003 x86.

No BSOD, but code 10

Would it be possible for you to procure a copy of POSReady2009, install it, and try it?

[user57]

15 hours ago, Jakob99 said:

You'd have to ask @K4sum1 for the version he is using. I wonder... Are there any dependencies in POSReady 2009 that aren't in normal XP?

we never shall forget that XP is a OS that was fixed, upgrade and patched for 20 years - thats the longest time i can think of for a OS - in this case XP is rather unique 

that reduced exactly these, also the security is very high - there is a reason why nuclear silo´s use windows xp and not win10

 

even for a virus problem (that you downloaded and executed) that could be a problem - it might no longer knows so exactly what to do 

for older vaccines like the POX-virus they use a trick for humans 

the POX virus (for humans/and apes) get put into a COW´s body (win10), therefore the virus mutated to fix for the "new operating system"

 

but back into a human body the virus forgot what to do, it is now like a alien in a wrong body - it no longer know what to do

the virus who was in the COW put back into the human (xp) is no longer dangerous for the human

 

that might also be from consideration, some exploids, bugs or viruses might no longer work on XP either

 

dietmar described recently how to do install all the XP upgrades, but however i think dietmar should rather make a ISO that do not need the a upgrade.exe and has all the files within the windows installer

that is certainly possible, someone called out nlite ? but even if we would not have nlite, we can actually see what these upgrades are doing (it useally are just renames of files and registry entrys)

[NotHereToPlayGames]

52 minutes ago, user57 said:

we never shall forget that XP is a OS that was fixed, upgrade and patched for 20 years - thats the longest time i can think of for a OS - in this case XP is rather unique

Technically, I wouldn't classify Win11 as a "new OS".  It's just a rebranded Win10.

[D.Draker]

Momiji

@K4sum1, from my attempts, the earliest beta driver was the most stable. Though, I have a different device, not GT2.

Also, I remember it worked for Dixel on Pentium G, but on Vista.

[K4sum1]

1 minute ago, D.Draker said:

from my attempts, the earliest beta driver was the most stable.

That makes me realize I forgot to send version, I tested 6.14.10.5445.

What version is this beta you tried?

[D.Draker]

On 7/27/2024 at 3:52 AM, K4sum1 said:

PCI\VEN_8086&DEV_1616&SUBSYS_062D1028&REV_09

I did also test x86, however it was Server 2003 x86.

No BSOD, but code 10

BSOD stop 50 indicates that invalid system memory has been referenced. Most likely due to the inability to set proper memory allocation since Intel Driver and Intel chipset uses your usual system RAM sticks, it doesn't have its own memory, unlike most dedicated GPUs.

[D.Draker]

11 hours ago, K4sum1 said:

That makes me realize I forgot to send version, I tested 6.14.10.5445.

What version is this beta you tried?

6.14.10.5437 (14.51.11.5437

[Dixel]

11 hours ago, D.Draker said:

Also, I remember it worked for Dixel on Pentium G, but on Vista.

 

G3420, desktop version, not laptop, and I had no Aero on Vista with that XP driver, of course. 

As a note, I tried a driver which they marked as "FORCED" (written in capslock).

Sorry, don't remember the exact version. 

 

 

[K4sum1]

That makes no sense. 5437 should be Sandy/Ivy Bridge only, or at least the version I have is.

[D.Draker]

12 hours ago, K4sum1 said:

That makes no sense. 5437 should be Sandy/Ivy Bridge only, or at least the version I have is.

I totally agree with you! But then again, 5437 was written for XP, while 5445 can't even allocate VRAM properly.

Edited July 27, 2024 by D.Draker
typo

[D.Draker]

12 hours ago, Dixel said:

As a note, I tried a driver which they marked as "FORCED" (written in capslock).

 

The full name, I know it. Old links are gone, maybe @K4sum1 will find it.

Intel-FORCED-5x64-Haswell_6.14.10.5445-drp.exe

[D.Draker]

11 hours ago, D.Draker said:

Intel-FORCED-5x64-Haswell_6.14.10.5445-drp.exe

Intel-FORCED-5x32-Haswell_6.14.10.5445-drp.exe for 32 bit, respectively.

[Dixel]

"Universal VESA/VBE Video Display Driver"

https://yeokhengmeng.com/2016/04/installing-windows-xp-on-a-modern-unsupported-haswell-system-in-2016/

*not tried myself

Edited July 28, 2024 by Dixel

[K4sum1]

22 hours ago, D.Draker said:

The full name, I know it. Old links are gone, maybe @K4sum1 will find it.

Intel-FORCED-5x64-Haswell_6.14.10.5445-drp.exe

That's 5445?

14 hours ago, Dixel said:

"Universal VESA/VBE Video Display Driver"

https://yeokhengmeng.com/2016/04/installing-windows-xp-on-a-modern-unsupported-haswell-system-in-2016/

*not tried myself

I guess that could work, I would need to try it when I have time to put the XP SSD back in.

[Jakob99]

33 minutes ago, K4sum1 said:

That's 5445?

I guess that could work, I would need to try it when I have time to put the XP SSD back in.

VESA will work fine with 32-bit, I can confirm, however, when I tried it with 64-bit, it did not work. Yeah, you do need to copy a file into System32 manually, as apparently the inf does not tell Windows to copy it over, but despite that, it still Code 10.