Hi All I spent yesterday installing SuSE 9.1 as an upgrade to my previous 9.1 setup, on a dual boot W2k/Linux. Broadly, I use ATAPI drives on Windows, and SCSI on Linux. I had been having problems with my SCSI CD-ROM reader & writer, and ended up buying a new IDE DVD/CD R/W drive. Because of this, I had one of my Windows IDE drives disconnected when installing SuSE. This caused me some separate problems (I had to edit /etc/fstab to comment out the unconnected drive) but got me up and running. So I'm now booting using LILO off a small sector on my first IDE drive, /dev/hda1, which contains my various kernels. My Linux root drive is /dev/sdc1, and all is well. My Windows D: drive (IDE channel 2, master), /dev/hdb1 IIRC, has been disconnected during the installation. I can boot Linux fine with the new 2.6.xx kernel 9.1 installed - it's just that Windows is getting confused because of the lack of all the applications on the missing D drive. So, I power down the machine, plug back in the IDE D drive, and power back up. Select Linux and ... EBDA too big !!! Now, I've come across this message before, when compiling my own kernel. But how can this be affected by whether a hard disk - and one not 'relevant' to the Linux system - is connected or not? This doesn't seem like the same LILO problem I've encountered before. Can anyone explain what is going on here? I'm quite happy to recompile my kernel, but in this instance I'm not convinced it's going to make a difference. Thanks for any pointers Jon N (sorry about company spiel below) This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. You must not disclose, copy or rely on any part of this correspondence if you are not the intended recipient. If you have received this email in error, please delete it from your system and notify the System Administrator at Thales e-Security +44 (0)1844 201800 or mail postmaster@thales-esecurity.com