Details
-
Bug
-
Resolution: Unresolved
-
Trivial
-
None
-
None
-
Operating System: ReactOS
Platform: x86 Hardware
Description
FreeLDR/NTOSKRNL is supposed to have the /MAXMEM option to limit the amount of system memory that FreeLDR and ReactOS see.
My assumption is it needs to be entered in \FREELDR.INI in the option path of a specific startup, in the form of /MAXMEM=x
{yyy}, without adding anything to it like K, M, G for units, and defaulting to MB.
Thus, I modified the section [ReactOS_Debug]'s options:
from : Options=/DEBUG /DEBUGPORT=COM1 /BAUDRATE=115200 /SOS
into : Options=/DEBUG /DEBUGPORT=COM1 /BAUDRATE=115200 /SOS /MAXMEM=100
However in both FreeLDR and ReactOS I still see 200MB (or rather 199, for some reason it's off by 1) listed.
As I ran into paging file issues on large memory machines, I'd like to have this option working properly.
Reproduction steps:
1 Boot reactOS using the ReactOS (Debug) option
2 Write down the amount of memory FreeLDR sees
3 Write down the amount of memory ReactOS sees ( either system properties or CMD, then MEMORY
4 modify C:\FREELDR.INI as mentioned above
5 Reboot
6 Perform steps 2 and 3
7 Notice that the amounts are the same despite the /MAXMEM parameter.