ÁÅÇ ×ÅÃÎ ÍÅËÜÇß
- Èçáàâèòüñÿ îò áðþøíîãî äèñêîìôîðòà, çàïîðîâ, ïîíîñîâ, ìåòèîðèçìîâ,
àëëåðãèè, íåïðèÿòíîãî çàïàõà èçî ðòà è îò òåëà, ÷àñòîé
ãîëîâíîé áîëè, äèïðåññèè, óñòàëîñòè;
- èçáàâèòüñÿ îò ïðîáëåì ñ êîæíûì ïîêðîâîì, îñòàíîâèòü âûïàäåíèå âîëîñ;
- çàíèìàòüñÿ êîððåêöèåé ôèãóðû è áîðîòüñÿ ñ
What brand BIOS do you have? What I've done to debug stage1 and
stage2 is to add simple 1 char output around places I think things are
going wrong. Of course having an In-target probe or in-circuit
emulator helps debug these things much easier.
Cheers,
Matt
On Mon, Sep 17, 2001 at
It is an AMI BIOS. v 1.00.11.CS1 on an Intel VS440FX (Venus) PPro motherboard.
FWIW, GRUB is booting off of SCSI ID 1. INT 13 does not appear to be involved.
On Mon, 17 Sep 2001 15:36:06 -0400
Matt Wilson [EMAIL PROTECTED] wrote:
What brand BIOS do you have? What I've done to debug stage1
Even so, I've run into several problems with AMI BIOS. What SCSI card
do you have?
Most likely what's happening is that the stack is becoming corrupted
and when you return from an interrupt call you're jumping to a point
other than where you called the INT 13 from.
Cheers,
Matt
On Mon, Sep
Dear Grub'ers;
I was trying to get a djgpp coff to load with
grub.
The a.out header was right, the kludge bit was
set,
but it would fail as an unsupported
format.
I tried several variations of the kernel.c linked
to the
start.asm that had the header. Some worked!
some
did not. The size
