Do you mean the modified RosAsm exe? If not the answer is regrettfully no. But it should not be to hard to verify.
1
Enable the PE header bit below the label "WritePEeaders" the bit is called &IMAGE_FILE_LARGE_ADRESS_AWARE
2
Ask windows, repeatedly for memory in 0_1000_0000 chunks, until the return adress > 0_8000_0000
3
Verify that the returned pointer is grayed out in the Debugger and cannot be inspected, but that the memory
is valid and can be written with code.
I suspect this is a C mindset that has lead the author of the debugger to think that those adresses are invalid.
Note that windows may not be able to return a LARGE chunk at once, but that it will return upto about 3.8 G if
asked for several smaller chunks. The largest single contigous chunk will be around 1.8G. Thats why I ask
for 0_1000_0000 at a time, when I was testing this.