Windows 7 32-bit with full 4 GB or 8 GB RAM support


Recommended Posts

Are you still talking about PAE? Reading this thread it seems to me that nobody denied the existence of PAE or its ability to extend memory usage in a 32-bit OS under the right conditions, but rather that it isn't practical for consumers using standard consumer hardware because of incompatibilities.

Actually, ShamRocker1 has repeatedly stated that it isn't possible.

Because I can. LoL

My point was what were you trying to say when you did that? I see that you highlighted the word patch, and this was after you asked me what patch I was talking about. Have you actually READ the first post of the thread?

I do recognize the PAE aspect. There is nobody who has given proof of this working. So, I say BS. Yes the concept is there but no actual proof. Good enough for you?

That's better. At least you aren't now repeatedly saying "it won't work" without saying why you think that. Most of your comments in this thread have reminded me of those people who will stick their fingers in their ears and say "la la la la la" when someone tries to tell them something they don't want to hear.

I'd be happy to test it, but my only 32-bit system running 7 only has 1GB in it, and to try to put more in would mean shutting down my main system and raiding the RAM from it.

I do recognize the PAE aspect. There is nobody who has given proof of this working. So, I say BS. Yes the concept is there but no actual proof. Good enough for you?

Right, so that since PAE does work, and since the server editions of Windows (which are virtually identical to the client editions) have fully supported it since 2000, how can you completely discard the possibility that it can be enabled in the client edition as well? Do you have some insight into how memory is initialized in the two editions to make this claim?

Right, so that since PAE does work, and since the server editions of Windows (which are virtually identical to the client editions) have fully supported it since 2000, how can you completely discard the possibility that it can be enabled in the client edition as well? Do you have some insight into how memory is initialized in the two editions to make this claim?

Why do you keep avoiding my question? SHOW ME PROOF! Otherwise go away. TY

Why do you keep avoiding my question? SHOW ME PROOF! Otherwise go away. TY

Well, someone wrote the patch, so presumably they have run it, as have various people who are posting about it, as well as other sites (such as the one linked earlier, dating back years) that talk about how the restriction works from a technical aspect.

You, on the other hand, simply proclaim that it's "BS!" You need to get off your high horse, and recognize that it is very possible that the patch can work, especially when you consider the technical side. It's not some magic feat we're talking about here. Since you have provided exactly zero evidence or explanation for why you believe it simply can't work (a claim you have continually made), while others have theorized that it can and given some technical background as to why, I hardly think you are in any position to tell people to "go away." The truth is that you have no idea at all.

Well, someone wrote the patch, so presumably they have run it, as have various people who are posting about it, as well as other sites (such as the one linked earlier, dating back years) that talk about how the restriction works from a technical aspect.

You, on the other hand, simply proclaim that it's "BS!" You need to get off your high horse, and recognize that it is very possible that the patch can work, especially when you consider the technical side. It's not some magic feat we're talking about here. Since you have provided exactly zero evidence or explanation for why you believe it simply can't work (a claim you have continually made), while others have theorized that it can and given some technical background as to why, I hardly think you are in any position to tell people to "go away." The truth is that you have no idea at all.

Show me PROOF. All you have done is spread a bunch of crap and have nothing to back it up as well as rework the dialog to suit your needs or agenda.

Most probably would LIKE to go to 64 bit, BUT 32 bit ONLY CPU's still do exist. And obviously 64 bit wont install if the CPU is only 32 bit. And the only way they'll be able to get out of 32 bit, is if they update everything. So, it'll support it

That is true but by the time windows9 comes out, i dont think there would be 32bit only CPUs about... @ the moment i cant see this happen cause and with windows8 ment to be 2012 i would see 99% of the market using a 64bit CPU and with 50% of those people using a Quad Core or higher..

Show me PROOF. All you have done is spread a bunch of crap and have nothing to back it up as well as rework the dialog to suit your needs or agenda.

Of what? I haven't claimed that the patch works, only that it easily could. I have no interest in running it. There's nothing for me to "prove."

You on the other hand keep insisting that it simply can't, with no explanation why. At one point you even claimed PAE doesn't work. You're just being silly.

As for me "spreading a bunch of crap," you'll have to back that up with quotes. Actually, don't, as I no longer have any interest in talking to someone that willfully ignorant.

Of what? I haven't claimed that the patch works, only that it easily could. I have no interest in running it. There's nothing for me to "prove."

You on the other hand keep insisting that it simply can't, with no explanation why. At one point you even claimed PAE doesn't work. You're just being silly.

As for me "spreading a bunch of crap," you'll have to back that up with quotes. Actually, don't, as I no longer have any interest in talking to someone that willfully ignorant.

Go back through the posts.

I have a 32 Bit PC ? 3,4 GHz, single core. And I think it's running fine and fast enough for me. I can't install Windows 7 64 Bit.

I have installed 4 GB of RAM (4x1 GB) ? but with Windows 7 32 Bit I only can use 3.25 GB of RAM. What for I have paid for 4 GB RAM - when I only can use 3.25 GB ?

If I had paid for a 1 terabyte hard disk and could only use 750 GB I also would be angry.

I borrowed from a friend 4x2 GB RAM modules ? and the test shows that I can use all of this 8 GB RAM.

OK ? you are right: With the patch I still have a 32 Bit operating system and any single application can only use 2 GB of RAM. But, hey, Windows 7 is a multitasking system. So I can run several applications to use all of my 4 GB RAM.

And it is even possible that specific applications can use more then 2 GB of RAM. This feature is named "AWE" ("address windowing extension"- see wikipedia http://en.wikipedia.org/wiki/Address_Windowing_Extensions). But this is a Windows API ? so the software must support it.

With the borrowed 8 GB RAM I do this test:

I installed "VMware Player 3" and created a virtual machine with 5 GB of RAM. And this works.

And about driver stability: All drivers that are included in Windows 7 are WHQL certificated. So all pointers within these drivers must be 64 bit able. That's because DEP (data execution protection) and the NX bit. So this driver works fine and with no problems ? even in a 32 bit enviroment. If you use "not WHQL" certificated drivers it's your own risk. Windows 7 warns you to use them. And in Windows 7 64 bit it is even not possible to use "not WHQL" certificated drivers.

I have a 32 Bit PC ? 3,4 GHz, single core. And I think it's running fine and fast enough for me. I can't install Windows 7 64 Bit.

I have installed 4 GB of RAM (4x1 GB) ? but with Windows 7 32 Bit I only can use 3.25 GB of RAM. What for I have paid for 4 GB RAM - when I only can use 3.25 GB ?

If I had paid for a 1 terabyte hard disk and could only use 750 GB I also would be angry.

If you brought a pre-made system with that much memory and 32-bit Windows preinstalled, then you would have a point. That would be a ripoff. If you go and buy Windows yourself though, then it is your own responsibility to ensure that it is compatible with your hardware. The restrictions in Windows are widely published.

And about driver stability: All drivers that are included in Windows 7 are WHQL certificated. So all pointers within these drivers must be 64 bit able. That's because DEP (data execution protection) and the NX bit. So this driver works fine and with no problems ? even in a 32 bit enviroment. If you use "not WHQL" certificated drivers it's your own risk. Windows 7 warns you to use them. And in Windows 7 64 bit it is even not possible to use "not WHQL" certificated drivers.

Well, if you go back in time, Windows has actually shipped with several drivers that are not PAE-aware and would crash. In Windows 7, who knows, but it's not impossible since the scenario in question would never actually occur unless someone hacked the OS.

The real issue here though, is that most people end up also running drivers that aren't bundled with Windows. This is where the problem could theoretically occur. Windows runs on so many systems that they have to make sure it's as stable as possible for absolutely everyone. This happens at the expense of people like you, but that's the price.

And in Windows 7 64 bit it is even not possible to use "not WHQL" certificated drivers.

They do not have to be certified, they just have to be signed. Anyone can go buy a certificate and sign their driver with it. There are no requirements regarding code quality. The signing requirements exists only to make drivers more identifiable.

A 32bit driver uses 32bit pointers, a 64bit driver uses 64bit pointers, a driver that runs under an OS with PAE uses 36bit pointers, the WHQL "sticker" doesn't mean it'll use all 3 dynamically.

There are no 36-bit pointers. It uses 64-bit addressing. All drivers that are correctly designed have to support this, which doesn't really mean much since there are thousands of devices out there of extremely poor quality.

The main thing to bear in mind with running a true x64 system is that the processes/applications themselves have a wider memory range. 32bit system with PAE will still restrict each process to 2GB. I grant you that many applications are still 32bit however with the push to 64bit we will start to see more and more apps take advantage of this.

I don't understand why someone would still push for a 32bit system, as 64bit systems are pretty new with relevant driver support.

...

There are no 36-bit pointers. It uses 64-bit addressing. All drivers that are correctly designed have to support this, which doesn't really mean much since there are thousands of devices out there of extremely poor quality.

Doh, of course, there's no 36bit data type. You'd just use a 64bit pointer and ignore 28bits of it.

And yeah, I've got a webcam that causes crashes whenever apps try to access it, and that's a using the driver that Windows automatically installs for it.

And in most CPU's made in the last decade, they aren't 32-bit either, they are 36-bit.

There are no CPUs with 36-bit registers. PAE doesn't change register sizes. It just adds another level of hierarchy to the page table structures.

A 32bit driver uses 32bit pointers, a 64bit driver uses 64bit pointers, a driver that runs under an OS with PAE uses 36bit pointers, the WHQL "sticker" doesn't mean it'll use all 3 dynamically.

There is no such thing as a 36-bit pointer.

And about driver stability: All drivers that are included in Windows 7 are WHQL certificated. So all pointers within these drivers must be 64 bit able. That's because DEP (data execution protection) and the NX bit. So this driver works fine and with no problems ? even in a 32 bit enviroment.

32-bit client versions of Windows always run with PAE enabled in the CPU. This is what allows hardware DEP / NX to work. This does NOT result in 64-bit pointers magically appearing, and has no impact at all on driver compatibility.

Allowing support for greater than 4GB of memory is what causes compatibility problems, not PAE or DEP.

If you use "not WHQL" certificated drivers it's your own risk. Windows 7 warns you to use them. And in Windows 7 64 bit it is even not possible to use "not WHQL" certificated drivers.

This is utterly false. 64-bit Windows does not prevent you from using non-WHQL drivers. It prevents you from using unsigned drivers. You can sign a driver without going through WHQL. How do you think 64-bit users install non-WHQL display drivers all the time?

Driver signing is done by the manufacturer and has nothing to do with driver quality.

For some background on the complications which resulted in >4GB of addressing using PAE being disabled for client editions of Windows:

http://www.microsoft.com/whdc/system/platf...PAE/PAEdrv.mspx

For some background on the complications which resulted in >4GB of addressing using PAE being disabled for client editions of Windows:

http://www.microsoft.com/whdc/system/platf...PAE/PAEdrv.mspx

Looks like it isn't limited in Windows 2000. Someone should give it a go.

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

    • No registered users viewing this page.
  • Posts

    • It's amazing that anyone still uses this bloated trash.
    • @Sayan...I have defended you at various points as I hope you know. This headline however is utter trash...shame on you sir!
    • An actual cosmic "Eye of Sauron" had been looking straight at us all along by Sayan Sen Image by Kovin P. Vasquez via Pexels | Not representative An international team of researchers has solved a long-standing mystery surrounding a distant blazar known as PKS 1424+240, helping explain why it produces some of the brightest high-energy gamma rays and cosmic neutrinos ever observed despite appearing to have a relatively slow-moving jet. The findings were published on June 6 in Astronomy & Astrophysics Letters. The study addresses a broader challenge in astrophysics: understanding how extreme cosmic objects accelerate particles to very high energies and produce very high-energy (VHE) photons and neutrinos. PKS 1424+240 is located billions of light-years from Earth. It has attracted attention for years because it is both a powerful source of VHE gamma rays and the brightest known neutrino-emitting blazar in the sky, according to observations by the IceCube Neutrino Observatory. It is also associated with one of the strongest peaks in IceCube's nine-year neutrino sky map A blazar is a type of active galactic nucleus powered by a supermassive black hole that pulls in surrounding matter and launches jets of plasma moving close to the speed of light. What makes blazars unique is their orientation. One of their jets points almost directly toward Earth, making them appear exceptionally bright across the electromagnetic spectrum and allowing scientists to study some of the most extreme physical processes in the Universe. The scientists exclaimed it's like the 'Eye of Sauron' in deep space. Usually, the brightest gamma-ray-emitting blazars are expected to have jets that appear to move very quickly. However, radio observations of PKS 1424+240 suggested that its jet was moving much more slowly, creating a contradiction that became part of a long-running problem known as the "Doppler factor crisis." To investigate, researchers analyzed 15 years of observations from the Very Long Baseline Array (VLBA), a network of 10 radio antennas spread across the continental United States, Hawaii and St. Croix. Using a technique called Very Long Baseline Interferometry (VLBI), astronomers combine signals from widely separated radio telescopes to create a virtual Earth-sized telescope capable of revealing extremely fine details. The team combined 42 polarization-sensitive radio images collected between 2009 and 2025, creating a much deeper and more detailed view of the jet than had previously been possible. The observations were carried out as part of MOJAVE (Monitoring Of Jets in Active galactic nuclei with VLBA Experiments), a long-running program that studies the brightness, polarization and magnetic field structures of jets produced by active galaxies. The project aims to better understand how activity near supermassive black holes is linked to high-energy radiation and neutrino emission. “When we reconstructed the image, it looked absolutely stunning,” said Yuri Kovalev, lead author of the study and Principal Investigator of the European Research Council-funded MuSES project at the Max Planck Institute for Radio Astronomy. “We have never seen anything quite like it — a near-perfect toroidal magnetic field with a jet, pointing straight at us.” The image revealed an unusual geometry. The researchers found that Earth lies almost directly in line with the jet, with a viewing angle of less than 0.6 degrees. In simple terms, astronomers are looking almost straight down the jet. This turned out to be the key to the mystery. Because the jet is aimed almost directly at Earth, a relativistic effect called Doppler boosting dramatically increases its apparent brightness. The study found that this effect boosts the emission by a factor of about 30 while also making the jet appear slower than it actually is. “This alignment causes a boost in brightness by a factor of 30 or more,” said Jack Livingston, a co-author at the Max Planck Institute for Radio Astronomy. “At the same time, the jet appears to move slowly due to projection effects — a classic optical illusion.” The nearly head-on view also gave scientists a rare look at the jet's magnetic field. Using polarized radio signals, they detected a clear toroidal, or doughnut-shaped, magnetic field component. The observations suggest the jet carries an electric current and that its magnetic field helps launch, shape and stabilize the flow of plasma. Researchers believe this magnetic structure may also play a key role in accelerating particles to energies high enough to produce both gamma rays and neutrinos. “Solving this puzzle confirms that active galactic nuclei with supermassive black holes are not only powerful accelerators of electrons, but also of protons — the origin of the observed high-energy neutrinos,” Kovalev said. The research was conducted under the MuSES (Multi-messenger Studies of Energetic Sources) project, which investigates how active galactic nuclei accelerate particles and generate different cosmic signals, including light and neutrinos. Scientists say understanding how protons are accelerated and linked to neutrino production remains one of the major unanswered questions in astrophysics. The findings help explain why some blazars can appear to have slow jets while still producing extremely bright high-energy emissions. More broadly, the study strengthens the link between relativistic jets, magnetic fields, gamma rays and high-energy neutrinos. Researchers say the results provide new clues about how some of the Universe's most powerful natural particle accelerators work and offer important insights for multimessenger astronomy, which combines different types of cosmic signals to study extreme events in space. Source: European Research Council, EDP Sciences This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Gotenks98 is right... Outlook (new) is absolute trash. Doesn't Mozilla have an Enterprise Version of Firebird?
  • Recent Achievements

    • One Month Later
      lamborghiniv10 earned a badge
      One Month Later
    • Week One Done
      lamborghiniv10 earned a badge
      Week One Done
    • Reacting Well
      X-No-file earned a badge
      Reacting Well
    • One Month Later
      pestcontrol46 earned a badge
      One Month Later
    • Week One Done
      pestcontrol46 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      273
    3. 3
      Skyfrog
      75
    4. 4
      +Edouard
      72
    5. 5
      FloatingFatMan
      68
  • Tell a friend

    Love Neowin? Tell a friend!