What are the minimum requirements for RTP without the graphics?
I am attempting to load a very minimal shell/kernel onto a older test
systems I have to simply explore latency timings. I have a 386 with 640K
base and 384k ext memory. I can’t imagine a minimal system would not boot
with this much memory. I have created a boot floppy with some bare minimum
utils (ls, cat, etc.) I know it works because I can use it to boot my
desktop fine. However, on the min system it starts to load, I get the press
esc for alt system message and the dots indicator progress across the screen
but then it reboots the system.
Anyone have any ideas? Is there anyway to tell the boot loader/kernel etc
to output status messages as it proceeds so I can tell at which point it
dies?
any suggestions would be appreciated.
Mark
Mark Ford <mford@thorlo.com> wrote:
What are the minimum requirements for RTP without the graphics?
I am attempting to load a very minimal shell/kernel onto a older test
systems I have to simply explore latency timings. I have a 386 with 640K
base and 384k ext memory. I can’t imagine a minimal system would not boot
with this much memory. I have created a boot floppy with some bare minimum
utils (ls, cat, etc.) I know it works because I can use it to boot my
desktop fine. However, on the min system it starts to load, I get the press
esc for alt system message and the dots indicator progress across the screen
but then it reboots the system.
Anyone have any ideas? Is there anyway to tell the boot loader/kernel etc
to output status messages as it proceeds so I can tell at which point it
dies?
For your little system you will really not have a lot of room. The first
thing that you will probably want to do is to remove the compression
from the image (you probably have a compress= line in your image).
Now you will start to see the real footprint of your applications as
you use them. The problem is that the things that you put into your
image (ie ls,cat etc) go into the image filesystem … the image
filesystem need backing ram to store in. Ideally you don’t want to
really have anything in your image filesystem.
You can crank up verbosity on both proc and startup by adding -vvvvv’s
Thomas