Vector Interrupt images are not compatible from one system to the other. The
interrupt vector table has segment:offset pointers to the ROM BIOS routines.
These segment:offset values are installed by the BIOS upon bootup of the
machine. I don't know how to get a clean 200LX image, but I can tell you that
using another machine's VII is a bad idea.
--Perry
>
> Well, I've tried to run ELKS on my palmtop and I don't know if I'm having
> success.
> I use Steffen Gabel's bootelks which needs a kernel image and a *clean*
> vector interrupt image.
> The kernel it's ok, I compiled it from last source. The problem is with the
> vector interrupt image, because I don't have how to make it.
> The bootelks uses a way to get this vii, writing a little program on sector
> 0 0 1 of a floppy disk. When you boot the system with this floppy disk, it
> gets a clean vii.
> The HP has DOS in ROM and I can't boot her from flash card or other device,
> so i can't have this image.
> I'm trying to make this image through my pentium but i guess that it's not
> working because when I run bootelks, it gives the following messages:
> BELOW!
> Loading interrupts image...
> Success.
> Loading kernel image...
> Success.
>
> then, if it doesn't crash, it reboots the system... Any idea ?
>
> .~.
> /V\ N[e]xt L[e]v[e]l
> // \\ Isaque Galdino
> /( )\ Programador C/C++, PL/SQL
> ^`~'^ Linux, DOS e Win... ops! :)
>
--
Perry Harrington Linux rules all OSes. APSoft ()
email: [EMAIL PROTECTED] Think Blue. /\
