>In all cases I use a newer AWARD bios (4.51), there is no chance to >disable the mouse... How about if you disconnect the mouse while booting and connect it only after booting? This is not practical for daily use of course, it's just to prove a theory. >>This experiment to see if the BIOS is doing something special in the >>presence of a mouse. I suspect it's loading some code or data at the >>top of 640k, which would upset Etherboot's stack. > >I'm still a little confused, how the improvement came from out of version >4.2.9 to 4.2.10 and why it isn't able to tftp ... I think it was random. It could have just as easily become worse if the wrong part of the stack was destroyed. What about other models of NICs, do they have the same problem? If they do then it's a strong possibility that the BIOS is using some memory just under 640k. =========================================================================== This Mail was sent to netboot mailing list by: Ken Yap <email@example.com> To get help about this list, send a mail with 'help' as the only string in it's body to firstname.lastname@example.org. If you have problems with this list, send a mail to email@example.com.
For requests or suggestions regarding this mailing list archive please write to firstname.lastname@example.org.