After over a decade, I finally took two afternoons to revamp this personal web-page and to merge the content of the old NTCore page with the content of its blog (rcecafe.net). All the URLs of the old web-page and blog have been preserved in the process.
The people who voted for this on Twitter are the guilty ones.
You know who you are.
10 thoughts on “NTCore revamped”
Thanks a lot Daniel.
Great you didn’t forget about this website 🙂
Molte grazie 🙂
Thanks Tony, much appreciated 🙂
After years of using this little 4GB patch for my Dragon Age play thru I can finally thank you for it.
So can many others: https://answers.ea.com/t5/Dragon-Age-Origins/Crash-in-Denerim/td-p/5132085
Thank you for leaving it up there to download all these years.
Thank you, wantnofriends! It’s great to hear that one’s work has been helpful to many. 🙂
Can you please say what “4GB Patch” does technically ?
If it sets the IMAGE_LARGE_ADDRESS_AWARE flag then it should be 3GB not 4GB ?
no need to answer me on 4Gb patch.
Made an x86 exe with the flag and memory map viewer, run on Win10 x64, looked into the map… oh,shi-…
Still, it would give only 3GB per process by the original documentation about x86 Windows NT Server OSes.
Or who knows, maybe none extra at all on desktop x86 OSes. (i remember they did disabled some EMS-like feature in or after XP for non-servers, citing bad drivers quality for desktop-class NT)
And year, one day those game developers would manage to make textures overcoming or fragmentizing even 4GB space 😀
But yeah, perhaps you still could add a hint what technically that patch does 😀
Yeah, maybe a good idea. I never deemed it necessary because there are tons of guides over the internet explaining how to set the flag manually using CFF Explorer. 🙂
Yep, lots of the guides how to set flag this way or that way, but no “guides” that the specific tool does the specific action of setting that flag, that is the difference, just different questions 🙂
Just curious but is there a way to allocate even more RAM like 8GB? The 4GB Patch lets WinDirStat do a much better job with less crashing but it gets to a certain point – I’m not sure if it’s the RAM limitation or program limitation but it doesn’t finish processing it just goes unresponsive. Before the 4GB Patch I could get to 72% but that took over 12 hours. With the Patch I get to 56% within a few minutes then it just stagnates, I will probably just let it run for a while.. Anyhow Thank you very much in any regard because this has been incredibly helpful and useful.
Hello Lady, you’re welcome! Unfortunately, 4GB is a physical limit for 32-bit applications.