There is a way to achieve it in 9x.
I actually found this thread because I'm playing around with it a bit right now.
Basically it (seems) to come down to this reg key:
[HKEY_LOCAL_MACHINE\Enum\HTREE\RESERVED\0]
"ForcedConfig"=hex:00,04,00,00,00,00,00,00,00,00,00,00
That is the default setting. I'm not promising anything, but I've had a play around with figuring out how the reg key 's data is formatted. Not that I have any idea.
To manually add a blocked range: device manager > "computer" > properties > reserve resources > memory
I added 0000A000-0000A001 as a reserved range.
The reg key changed to:
"ForcedConfig"=hex:00,04,00,00,00,00,00,00,2c,00,00,00,01,00,00,00,01,00,14,00,\
00,a0,00,00,01,a0,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00
It's hard to figure out the order there. I think it's actually backwards.
So let's change it to a weird one.
98765432-98765433
"ForcedConfig"=hex:00,04,00,00,00,00,00,00,2c,00,00,00,01,00,00,00,01,00,14,00,\
32,54,76,98,33,54,76,98,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00
And there it is. That wonderful forward-backward endianness many hex files seem to like.
But what does 2c,00,00,00,01,00,00,00,01,00,14,00 mean?
Ideally... if the collective (we) here can figure out the behaviour of that properly, a trivial script will convert the badram output of memtest86 into a reg key.
https://www.memtest86.com/blacklist-ram-badra … memorylist.html
I would assume there are some limitations to reserving blocks of bad memory, like no bad memory in the first 640k, or the various other reserved ranges, but I'm sure it would extend the life of a fair bit of otherwise "junk" ram.