RE: [ros-cvs] CVS Update: reactos

[Ge van Geldorp]

> From: Ge van Geldorp
>
> Log message:
>    Current versions of VMware provide a correct BIOS memory map

I removed this code:

#ifndef ACPI
  /* FIXME: VMware does not like it when ReactOS is using the BIOS memory
map */
  KeLoaderBlock.Flags &= ~MB_FLAGS_MMAP_INFO;
#endif

Casper added this code a few years back, at that point using the BIOS memory
map prevented ReactOS from booting. It appears to work fine now (with VMware
4). This email is just a heads-up for everyone, if ReactOS fails to boot now
this change may cause it (and I will reverse the change if it causes
problems).

Gé van Geldorp

[Hartmut Birr]

> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Ge van Geldorp
> Sent: Saturday, December 04, 2004 9:23 PM
> To: [e-mail]
> Subject: [ros-dev] RE: [ros-cvs] CVS Update: reactos
>
> Casper added this code a few years back, at that point using 
> the BIOS memory
> map prevented ReactOS from booting.

The cause for this problem was a bug while parsing the BIOS memory map. This
bug is fixed since a long time. The parsing routine had added some ranges to
the available memory which were marked as not usable.

- Hartmut