On Wed, Jan 10, 2001 at 06:59:54PM +0000, Andy Cartwright wrote:
Adam Bower wrote:
...
The chances of the software being wrong are very low indeed ;-)
I fear you are correct here!!
As a double check you can look at how much memory the kernel reports when it starts. Though this usually disappears too fast to see you can get it back by running the 'dmesg' command. the first few lines will look something like:
Linux version 2.2.18pre21 (fozzy@pelvoux) (gcc version 2.95.2 20000220 (Debian GNU/Linux)) #9 Fri Dec 29 12:26:40 GMT 2000 Detected 755301 kHz processor. ide_setup: idebus=66 Console: colour VGA+ 80x25 Calibrating delay loop... 1507.32 BogoMIPS Memory: 647560k/655360k available (668k kernel code, 416k reserved, 6676k data, 40k init)
P.S. I am not using lilo for the dual boot but am using Bootmagic, could this be the reason?
I assume from this that you have bootmagic on the MBR and have LILO installed on the boot record of the primary linux partition. If that is the case then I would expect the configuration to work correctly.
The exception would be if bootmagic had moved a LILO boot record from the MBR, where the Linux installer had put it, to the Linux partition. In that case it may be possible that the 'lilo' command would not update the boot parameters correctly.