Results 1 to 5 of 5

Thread: For win32 users - a script that allows actual usage of 4GB+ of RAM....

  1. #1

    For win32 users - a script that allows actual usage of 4GB+ of RAM....

    For years Ive wanted to find a way to use PAE to allow windows 32bit to actually use 4GB+ RAM...since thats basically what PAE is really for. On modern machines windows nearly always has PAE turned on because DEP(nx bit) requires PAE be used. So, by default most windows 32bit installs actually use the PAE enabled kernel.
    But, even when PAE is forced on or is on because of DEP... RAM above 4GB is still locked away and unusable.
    After coming across this article: http://www.geoffchappell.com/notes/w...nse/memory.htm

    Ive been inspired to get this working for myself. So, Ive successfully been able to patch vista_32 & win7_32 kernels, resign them and boot from them. This has been tested on a couple different machines and works fantastic.
    After confirming both kernel types are patchable, I set out to write an autoit script that automates the process on both vista & 7.
    So, Ive made my first release of the patch. It basically patches the kernel, creates a cert, signs the patched kernel w/ the cert, modifies BCD to add entry of picking between original kernel & patched copy of the kernel.
    NOTE: this is ONLY for vista or 7. Win8 32 I have not tested. XP this patch is not possible.
    TO INSTALL: Simply run the exe

    TO UNINSTALL: by creating a shortcut to my script, and putting 'uninstall' (without quotes) as an argument, it will remove the BCD entries and delete the modified kernel.

    I am posting links to my script, one is the precompiled version(the executable)
    The other is the source so you can see for urself what it does.
    https://dl.dropbox.com/u/1791919/Kernel4GBpatcher.exe
    https://dl.dropbox.com/u/1791919/Kernel4GBpatcher.au3
    Screenshot:
    https://dl.dropbox.com/u/1791919/5GB_32bitWin7.PNG

    -
    NOTE: after applying the patch, your system may show "test" mode water mark on the desktop in the corner(s). This is normal. There are guides to get rid of this watermark(by editing user32.dll.mui file). I may make it as part of my script in the future if there is enough demand for it.

  2. #2

    For win32 users - a script that allows actual usage of 4GB+ of RAM....

    neat, but probably a better idea to simply get out of the stone age and just install 64 bit.

    license keys work across both, what's the point?

    edit: cool certificate name: Bitcoin Forever

  3. #3

    For win32 users - a script that allows actual usage of 4GB+ of RAM....

    I agree. Going 64-bit is probably the best way to go for Vista & 7.

    On the other hand, great work. There will be some that will appreciate your work greatly but such people are starting to move towards 64-bit as well.

  4. #4

    For win32 users - a script that allows actual usage of 4GB+ of RAM....

    Looks like the script extracts some binaries into a temp directory and then automates some button pushing. Did you put the patcher together too? That's the binary I would be most interested in seeing the source of....

  5. #5

    For win32 users - a script that allows actual usage of 4GB+ of RAM....

    PAE is hard coded in HOME 32 bit OSes to disable more than 4GB of memory. The only 32 bit OSes you could enable more than 4GB of memory on was Server grade. That's why forcing it doesn't do squat. Also running PAE mode without certified drivers for it can cause some serious issues.

    I hate PAE threads.

    In the past 2 years I've moved everything over to 64 bit. For the occasional App that doesn't officially support 64 bit or run under 64 bit, I call whoever is trying to sell it to me, tell them off, and find something else. I've no patience for companies who are stuck in the past.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •