I completely agree with you. I think the `cls()' for screen init (in
char_io.c)
is not a good idea. I see no problems to start the command line
interface anywhere,
not on the top.
Befure a menu is executed, a cls() is necessary, otherwise the menu is
currupted.
With friendly regards
-BEGIN PGP SIGNED MESSAGE-
On Sunday, 23. September 2001 01:52, you wrote:
So why not add some error code return values and passing so that the
boot process halts or stalls to give you time to read the error
message. Absent any error codes, clear screen and continue?
This would work
úÄÒÁ×ÓÔ×ÕÊÔÅ!
íÅÎÑ ÚÏ×ÕÔ áÌÅËÓÅÊ. éÚ×ÉÎÉÔÅ ÚÁ ÂÅÓÐÏËÏÊÓÔ×Ï, ÎÏ ÎÅ ÔÏÒÏÐÉÔÅÓØ ÕÄÁÌÑÔØ ÜÔÏ
ÐÉÓØÍÏ - ÏÎÏ ÍÏÖÅÔ ÓÙÇÒÁÔØ ×ÁÖÎÕÀ ÒÏÌØ × ÷ÁÛÅÊ ÖÉÚÎÉ! éÍÅÎÎÏ ÔÁË ÐÒÏÉÚÏÛÌÏ ÓÏ
ÍÎÏÊ ÐÏÓÌÅ ÐÏÌÕÞÅÎÉÑ - ÎÅËÏÔÏÒÏÅ ×ÒÅÍÑ ÎÁÚÁÄ - ÔÁËÏÇÏ ÖÅ ÐÉÓØÍÁ. öÅÌÁÀ É ÷ÁÍ ÎÅ
ÕÐÕÓÔÉÔØ Ó×ÏÊ ÛÁÎÓ! ïâñúáôåìøîï óïèòáîéôå üôï
Running LILO gave me some insight. My guess: Stage1 is loaded OK because the BIOS
knows how to load from SCSI ID 1.
But GRUB doesn't, so it tries to load the next stage from ID 0, gets garbage and is
confused.
--
Geoffrey Leach
Sent to you by the Sylpheed user agent from a Linux Helix/Gnome
When will you update your patch for the more recent version
(i.e. 0.90)? :-)
Regards,
Okuji
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
Ok, I think now is the time when I should comment on this issue.
First of all, I agree that GRUB shouldn't erase anything on the screen
unnecessarily. IIRC, this is not the first time that the issue rose in
this mailing list. The reason that we didn't fix the problem at that
time was just that
