Recommended Posts

Tried installing ubuntu on a computer at work recently, it crashed on startup with a kernel panic because of the CPU. and while it was old, it wasn't that old, newer than this P4 I believe at the very least.

The only thing that could have crashed it would have been the requirement of the "i686 instruction set" and that has there since Pentium Pro.

According to all the information that I have seen, all Pentium 4 CPU's support SSE2

I think the number of CPUs that support SSE2 but not NX is very small. The requirements are NX+PAE+SSE2. From what I understand, everything that supports NX also supports SSE2.

The whitepaper someone linked to earlier in the thread explains all this in detail.

The only thing that could have crashed it would have been the requirement of the "i686 instruction set" and that has there since Pentium Pro.

From what I recall, some Linux distros are compiled with SSE2 instructions and others are not.

running w8 on celeron 430 1.8ghz with no problems. has to something wrong with your configuration.

You processor is at least 5 years newer than OP's. And it supports NX. The processor that this thread is about does not support NX.

http://ark.intel.com/products/29735/Intel-Celeron-Processor-430-(512K-Cache-1_80-GHz-800-MHz-FSB

The only thing that could have crashed it would have been the requirement of the "i686 instruction set" and that has there since Pentium Pro.

Hate to break you, but your facts don't match up with real world facts. Maybe I'll hook it up to the screen and try to boot the stick again and photo the screen.

I think the number of CPUs that support SSE2 but not NX is very small. The requirements are NX+PAE+SSE2. From what I understand, everything that supports NX also supports SSE2.

The whitepaper someone linked to earlier in the thread explains all this in detail.

Not really true. NX as we currently know it only made it's way into the Pentium 4 range from later iterations of Prescott cores and onwards, which means that all of the Williamette, Northwood, and first iterations of Pentium 4-M, Pentium 4 Mobile, and Gallatin (Pentium 4 Extreme edition) processors have SSE2 but no hardware support for NX, which is well over half of the Pentium 4 range. More specifically the Socket 775 or 5xJ and 5x9J series were the first CPU's to support hardware NX)

Not really true. NX as we currently know it only made it's way into the Pentium 4 range from later iterations of Prescott cores and onwards, which means that all of the Williamette, Northwood, and first iterations of Pentium 4-M, Pentium 4 Mobile, and Gallatin (Pentium 4 Extreme edition) processors have SSE2 but no hardware support for NX, which is well over half of the Pentium 4 range. More specifically the Socket 775 or 5xJ and 5x9J series were the first CPU's to support hardware NX)

You're arguing with the wrong person. I believe Brandon works for Microsoft. I think he'd know what's up more than you would.

According to http://en.wikipedia.org/wiki/Pentium_4 Javik is right, though.

Well, not necessarily. I mean, yes, Javik is right. But so is Brandon Live.

I think the number of CPUs that support SSE2 but not NX is very small. The requirements are NX+PAE+SSE2. From what I understand, everything that supports NX also supports SSE2.

The whitepaper someone linked to earlier in the thread explains all this in detail.

Everything that supports NX also supports SSE2. True.

The number of CPUs that support SSE2 but not NX is very small. True-ish? The number of CPUs that were manufactured that support SSE2 but not NX may be large, but how many of those are still in use today, 10 years later? All modern CPUs support SSE2 and NX. The number of CPUs that support SSE2 but not NX are a small percentage.

You're arguing with the wrong person. I believe Brandon works for Microsoft. I think he'd know what's up more than you would.

Sorry, but arguments to authority only work when the authority is right. The authority isn't right, I am. Google it and see for yourself.

Everything that supports NX also supports SSE2. True.

Well technically that is true if you count Segment level NX which has been included in Intel CPU's since the 80286. However neither old nor modern versions of Windows ever had support for segment based NX. NX as we see it today is known as the "flat memory model" and this is the only form of NX that all modern operating systems support, and that is the version that I was referring to. In terms of any form of useful functionality software NX has only been available since Windows XP SP2 and hardware based NX has only been available in a usable form since the Pentium 4 models I already mentioned, and AMD Athlon 64 CPU's. Given how far back Segment based NX goes there's a 0% chance the Windows 8 installer can be referencing it, as even absolutely ancient CPU's supported it. That therefore means that Brandon is referring to the more modern form of NX and as such the information he has provided is verifiably false.

As for how many are still in use... I'd wager it's a lot more than you think. The Northwood range of Pentium 4 processors in particular were extremely popular and sold strongly.

wow 5 pages already.

Ok to get a few things straight the rig I am talking about isn't my main every day rig it is my dads old one it is just now for experimenting purposes and it does run windows 7 quite well with all the bells and whistles. I am trying this simply because I am bored and now have this computer to screw around with rather than doing things in a VM. I am going to try burning it to a dvd when I get some and I do think it will work.

If it still fails I think would think ms needs to be a little more specific for their requirements rather than generalizing saying they will be no higher than windows 7.

In the long haul the p4 rig will likely be turned into a file server or something so I can retire my old athlon xp from 2002 as my file server being that it is from 2001 and the police basically destroyed it

fx5500 - you mean NVIDIA FX 5500? Like that really old thing that is older than history itself? Is that thing even supported on Windows 7?

yep Nividia drivers still support FX GPUs.....wtf u smoking the Fx5500 is approx 8-10years old max years old.....hardly older than "history itself" seeesh Riva tnt16 anyone?

Well technically that is true if you count Segment level NX which has been included in Intel CPU's since the 80286. However neither old nor modern versions of Windows ever had support for segment based NX. NX as we see it today is known as the "flat memory model" and this is the only form of NX that all modern operating systems support, and that is the version that I was referring to. In terms of any form of useful functionality software NX has only been available since Windows XP SP2 and hardware based NX has only been available in a usable form since the Pentium 4 models I already mentioned, and AMD Athlon 64 CPU's. Given how far back Segment based NX goes there's a 0% chance the Windows 8 installer can be referencing it, as even absolutely ancient CPU's supported it. That therefore means that Brandon is referring to the more modern form of NX and as such the information he has provided is verifiably false.

I think you misread what I wrote. I said that as far as I am aware, all x86 CPUs which support NX also support SSE2. You haven't provided any evidence that this is not correct. The inverse is not true, as I also said. The early P4s supported SSE2 but not NX. These are now quite old and the number of these which someone would want to upgrade to Win8 is incredibly small.

I think you misread what I wrote. I said that as far as I am aware, all x86 CPUs which support NX also support SSE2. You haven't provided any evidence that this is not correct. The inverse is not true, as I also said. The early P4s supported SSE2 but not NX. These are now quite old and the number of these which someone would want to upgrade to Win8 is incredibly small.

Evidence on this forum suggests, however that it's not zero. This is the second or third time that I have seen this question asked. It's a limitation people are running into. And your assertion that it had anything to do with SSE2 was simply false. SSE2 and NX don't require each other to function, and pretty much any CPU fast enough to run Windows 8 supports SSE2. People who get this error are almost certainly getting it due to their lack of NX support, not their lack of SSE2 support.

Evidence on this forum suggests, however that it's not zero. This is the second or third time that I have seen this question asked. It's a limitation people are running into. And your assertion that it had anything to do with SSE2 was simply false. SSE2 and NX don't require each other to function, and pretty much any CPU fast enough to run Windows 8 supports SSE2. People who get this error are almost certainly getting it due to their lack of NX support, not their lack of SSE2 support.

What evidence?

You're putting words in my mouth. All three are required. PAE, NX, and SSE2. If PAE and NX are disabled in the BIOS, Windows will actually force them on at start-up. Anything which supports NX also supports PAE and SSE2. So it's easiest to ask if the CPU supports NX. If it does, it should work.

NX is crucial for security. SSE2 is needed because code in the OS and apps made in the last couple of years use SSE2 instructions. Without it, the system will crash.

What evidence?

You're putting words in my mouth. All three are required. PAE, NX, and SSE2. If PAE and NX are disabled in the BIOS, Windows will actually force them on at start-up. Anything which supports NX also supports PAE and SSE2. So it's easiest to ask if the CPU supports NX. If it does, it should work.

NX is crucial for security. SSE2 is needed because code in the OS and apps made in the last couple of years use SSE2 instructions. Without it, the system will crash.

I never disagreed that the OS needed SSE2 I just pointed out that any CPU capable of running the OS already supports it. I'd also disagree that NX is a killer security feature. It certainly helps things a great deal but it's not as if disabling it suddenly turns your computer into a hotspot of hacking activity it just makes you a little more vulnerable. Windows 7 can work without NX so whilst I absolutely understand the advantages of having it enabled, not allowing people to install because of lacking it still seems like a pretty tacky move to me as plenty of hardware without NX support is capable of running Windows 8.

Everything that supports NX also supports SSE2. True.

Well technically that is true if you count Segment level NX which has been included in Intel CPU's since the 80286.

You have it backward. That's evidence of a CPU that supports NX but not SSE2. That would make it technically false.

However neither old nor modern versions of Windows ever had support for segment based NX. NX as we see it today is known as the "flat memory model" and this is the only form of NX that all modern operating systems support, and that is the version that I was referring to. In terms of any form of useful functionality software NX has only been available since Windows XP SP2 and hardware based NX has only been available in a usable form since the Pentium 4 models I already mentioned, and AMD Athlon 64 CPU's. Given how far back Segment based NX goes there's a 0% chance the Windows 8 installer can be referencing it, as even absolutely ancient CPU's supported it. That therefore means that Brandon is referring to the more modern form of NX and as such the information he has provided is verifiably false.

Name a CPU that supports NX but does not support SSE2. Only then will it be verifiably false. No, we're not talking about segment based NX.

My point: NX implies SSE2, but SSE2 does not imply NX.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!