
ReactOS r52053 was tested for bug#6031 on VMs and real hardware, with BootCD and LiveCD
 with Delay_3s_after_RAM_size_print.patch applied.
Regretfully this notebook has no serial port to test ROS with FreeLdr-debug on real hardware.


Tested with RAM sizes, with what actually was found:

*** BootCD, + freeldr-debug of 2011-06-01 from attachment by rafalh 2011-06-01 12:37:01 CET
                                              (attachment id=6409).

 RAM set in VM | RAM found, Mbs
---------------+-----------
      100         99
     3080       3079
     3700       3583
     3900       3583
     4000       3583
     4096       3583
--------------------------
 Real machine  | RAM found
---------------+----------
     4096        Unknown -it's not been shown even with my 'delay' patch, &no serial port

Both Virtual machine and Real machine run ROS setup sucessfully run until message: 
"Setup could not find a harddisk", (since on RH real HDD is on SATA, and I have turned HDDs off on VM).
Ros setup (usetup.exe?) on Real machine possibly was consuming very small amount of RAM (<=25Mb), 
but I was not able to check this.


 *** LiveCD: (no connection with debug version of FreeLdr)
RAM set in VM  | RAM found, Mbs
---------------+-----------
       3900     3583
       4000     3583
       4096     3583
--------------------------
 Real machine  | RAM found
---------------+----------
       4096       25 (viewed with my 'delaying' patch 
                      http://www.reactos.org/bugzilla/attachment.cgi?id=6413)

Virtual machine was fully loaded and was working OK, including until GUI.
I suppose this was due ROS ntoskrnl really was faced with 3583 Mb starting with FreeLdr stage.

ROS on Real machine behaves same way as earlier, and has found only 25 Mb.

