by > I'm just guessing here, but it may be that DOS/Windows is the culprit.
> After all, you have to launch DOS first, then loadlin inside DOS reads
> the kernel into memory and starts executing it. Assuming loadlin and the
> kernel don't touch the BIOS image (if they did it would happen all the
> time),
> it may be that DOS/Win is wiping it for some reason before Linux starts.
> I'm afraid I haven't a clue how you might correct that. (Maybe "format
> C:"? he-he!)
Linux. The Linux part would have LOADLIN.EXE as a shell, and Loadlins
paramaters as shell parameters. The DOS part would have the usual stuff
in it. This way, the "DOS launch" phase is minimized - I had to switch
to this solution in order to get the svgalib-1.3.1 VESA driver to work.
Before that, I let DOS boot up completely, and then ran Loadlin from
the command prompt - this caused some interrupt vectors to be modified
by some DOS drivers & TSRs, and made the VESA driver crash under Linux
as a result.
Insert these lines at the beginning of your CONFIG.SYS (modify the
SHELL= line to reflect your system settings):
---<snip>--------------------------------------------
[Menu]
MenuItem=DOS
MenuItem=Linux
Me*fault=DOS,3
[Linux]
[DOS]
---<snip>--------------------------------------------
... (your original CONFIG.SYS goes here)
HTH,
Thomas
--
=---------------------------------------------------------------------=
- Thomas Zajic aka ZlatkO ThE GoDFatheR, Vienna/Austria -
- Spam-proof e-mail: thomas(DOT)zajic(AT)teleweb(DOT)at -
=---------------------------------------------------------------------=