Hi there,
I've been strugling for some time with booting Elks on 286 motherboard.
Symptons were booting up to ..: and than a freeze.
The boot gave one error but resumed after it. I believe now that any error
during boot is fatal while it looks if it recovers from the error.
The cau
m.
>
> The problem is that with palmtops which boot from ROM we don't have access
> to the machine until DOS has started. There is no boot disk, so we cannot
> put any code on it.
Here's what I'd like to see with booting ELKS from a palmtop:
1) boot to DOS, with as littl
Well, I'm lost in a lot of emails and I don't know if I've sent you this,
but there is a routine made by Dr. Richard L. Dubs (www.erols.com/rld):
"Unfortunately, the HP200LX boots its operating system from ROM; it has no
need to boot from either a floppy disk or a hard disk. For this reason, the
On Tue, 4 May 1999, Araujo, Isaque G. wrote:
> Shane, I don't know if you read my old mails which I've sent to Alistair
> Riddoch and to the ELKS-list, but this already exists (BOOTELKS by Steffen
> Gabel), what is need is a effort to change this code for don't write any
> VII, just start ELKS. T
uld have a solution faster.
Isaque.
> -Original Message-
> From: Shane Kerr [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, May 04, 1999 8:05 AM
> To: Alistair Riddoch
> Cc: David Murn; Mailing List
> Subject: Booting ELKS from DOS Re: your mail
>
> On Tue, 4
Shane Kerr writes:
>
> I'm fairly excited about the plans to incorporate loadable device drivers
> in ELKS. Unfortunately, after I thought about it, they STILL won't help
> me get my HP 200LX booted. :(
>
> The problem is that there is neither a floppy drive nor a hard disc on the
> machine, w
I'm fairly excited about the plans to incorporate loadable device drivers
in ELKS. Unfortunately, after I thought about it, they STILL won't help
me get my HP 200LX booted. :(
The problem is that there is neither a floppy drive nor a hard disc on the
machine, which I believe ELKS requires to bo
Michael W. Shaffer writes:
>
> > The display funniness would be caused by ELKS being ignorant about
> >clobbering the video memory. The kernel would have to be told not to use
> >the memory (might be tricky if it's in the area where the kernel is loaded
> >- quite likely since it's loaded at 64K
I'd move the loading segment to 128K (segment 0x2000). As long
as memory below 128K is not set up with the memory subsystem (not sure if
it is) the problem should go away. In fact I think what was happening
before was that BSS space was being corrupted by the BIOSs use of the
'video' m
> The display funniness would be caused by ELKS being ignorant about
>clobbering the video memory. The kernel would have to be told not to use
>the memory (might be tricky if it's in the area where the kernel is loaded
>- quite likely since it's loaded at 64K unless that's changed). I dunno
>abo
PCjr's IIRC used regular system memory to double as the display
memory. This idea pops up every so often in PC's and somewhat more often
elsewhere - the Tandy 1000 had it (it was really a PCjr/PC hybrid clone)
and some SIS chipsets use system memmory for VGA (example mobo : Asus SP97
se
I inherited an IBM PCjr some time ago and have recently begun playing with
trying to boot ELKS on it. This machine has an expansion module manufactured
by Racore which gives it 640K of RAM and a second 360K floppy drive. My
understanding was that this makes the machine roughly equivalent to an XT
12 matches
Mail list logo
