Nobody works on a GRUB installer, so I've written it. This version
is completely untested. Be careful.
--
OKUJI Yoshinori <[EMAIL PROTECTED]> ^o-o^
http://duff.kuicr.kyoto-u.ac.jp/~okuji (in English) m /
From: Stephen Early <[EMAIL PROTECTED]>
Subject: Re: Graphics mode support
Date: Wed, 17 Nov 1999 13:49:14 + (GMT)
> GGI assumes a reasonably Unix-like environment. The systems I work
> with (like many current research operating systems) are generally not
> even slightly Unix-like. Some of th
From: Peter Åstrand <[EMAIL PROTECTED]>
Subject: Re: Graphics mode support
Date: Wed, 17 Nov 1999 17:47:43 +0100 (CET)
> The native GGI hardware drivers are quite few, but libggi works good with
> other targets.
I took a look at KGI in the latest snapshot, and I found there
existed many drive
> Goran Koruga writes:
GK> So I wrote dumb "stage1" which just told me whether the value in
GK> DX is >= 80 or not. And it wasn't.
Do you mean that you put this dumb stage1 on the hard disk, and booted
it from the BIOS? What value did %dl actually have?
GK> PS. Maybe it's worth putting
> > That's right. So you can use GGI instead of writing drivers
> > yourself.
>
> I doubt GGI supports as many graphics cards as VESA2. Besides, isn't
> it quite Linux-centric? (I haven't used it very much)
GGI mainly consists of libraries: libggi etc. These works on most Unices.
Libggi draws
OKUJI Yoshinori <[EMAIL PROTECTED]> writes:
> > I don't have time to write device drivers for each new operating
> > system; it would be completely unproductive.
> That's right. So you can use GGI instead of writing drivers
> yourself.
I doubt GGI supports as many graphics cards as VESA2. Besi
On Wed, 17 Nov 1999, OKUJI Yoshinori wrote:
> From: Stephen Early <[EMAIL PROTECTED]>
>
> > measurements, or whatever, as quickly as possible. I don't have time
> > to write device drivers for each new operating system; it would be
> > completely unproductive.
>
> That's right. So you can use
