Some programs apparently don't.
Bitspirit for example, a chinese torrent client, only see's 2 gigs max apperently.
I never paid much attention to it in x64...
I read something about patching different exe's to make them large address aware and supposedly that helps.
I'm not sure if any 32bit program in windows can use more then 2 gigs at once, without patching.
Some might though, since it's a requirement for 64bit windows I guess.
The amount of ram total in aida64 looks goofy though, 15gigs or so, when I only got 8gigs of ram and a 2gig swap.
Not sure what's up on that.
Supposedly there's an issue with some drivers not mapping into mem correctly when you do this hack, but so far I've had no probs.
Audio, video, 3d gaming all work.
I've only had it going for a little bit though.
I got the info from here:
http://www.geoffchappell.com/notes/w...nse/memory.htm
My notes:
Look for:
7C118B45FC85C0740A
7C108B45FC85C07409
Replace with:
7C11B8000002009090
7C10B8000002009090
bcdedit /set {current} kernel ntkr128g.exe
editbin /release ntkr128g.exe
I used easybcd to create a 2nd menu option to the same copy of windows, original kernel just in case.
1st time I modded it without using the editbin tool it refused to boot so it was a good idea to make that backup.
I used winhex to edit the kernel, renamed it to a bin file to make it easy (exe's don't show a open with menu in windows).
I searched for the hex code above, but in this format:
7C3F8B45FC85C0743F
I also checked the box in winhex for the hex search, wild card = 3F, that allowed me to find the 2 instances of code to patch.
Then I had to dl visual studio express..., install vc++ on my 64bit os, used it's cmd console and ran editbin from there .
That part wasn't as hard as I thought it would be.
But I gotta get it to boot without my intervention though (f8 key -> disable driver signing enforcement crap...).
I'm happy camper though, I didn't like the 64bit windows so much.
I do have to test it more to make sure it's all good though.
That and what sort of program limits there are, I would assume something like s&m memtest, or hci memtest could use all the ram in 32bit since they were meant for 64bit anyways.
There is one more mode I'de like to find out about, if it exists for windows.
64bit for 32bit windows, you can doit for dos I assume without probs, just a bit of asm code needed.
But windows, I'm sure there's a way..., I'll probably never find the info though.
You might ask why not use 64bit windows then?, because I don't like the emulation layer stuff winx64 does, it doesn't feel like real 64bit to me (coding wise).
Edit:
The exact list of changes in the kernel file, they are just renamed from exe to bin for my convenience.
Code:
Search for differences
1. C:\Users\Administrator\Desktop\ntkrnlpa.bin: 3,966,848 bytes
2. C:\Users\Administrator\Desktop\ntkr128g.bin: 3,966,848 bytes
Offsets: hexadec.
2D0: AC 99
2D1: 88 2E
2D2: 3C 3D
3605F8: 8B B8
3605F9: 45 00
3605FA: FC 00
3605FB: 85 02
3605FC: C0 00
3605FD: 74 90
3605FE: 0A 90
360638: 8B B8
360639: 45 00
36063A: FC 00
36063B: 85 02
36063C: C0 00
36063D: 74 90
36063E: 09 90
17 difference(s) found.
Bookmarks