Etienne Lorrain wrote:
> These two files in memory have also to be at fixed linear
> addresses in real mode - and if you have a memory manager
> (himem.sys) loaded, these address may not be free. Usually
> you will find at the bottom of the himem memory the smartdrv
> (disk cache) data. It is then impossible to load a file at a random
> memory address and stay in real mode to do futher processing.
> In this case, Gujin is just malloc'ing the memory (using himem.sys),
> loading and decompressing this file (checking its CRC32), and
> only then disable interrupts, switch to protected mode, copy
> the file at its intended linear address and jump to the kernel
> code.
>
hmm.
You say: BIOS/hardware can be broken, let use DOS do load Linux!
IMHO using DOS (himem.sys and letting DOS to setting our
hardware in ibmbio.com and ibmdos.com) give us more problem
that solution!
We should have complete control to hardware, not letting DOS
to hide/modify the BIOS segment 0040:0000 and some other
hardware setting.
Thus we should (if possible) use only BIOS call (or directly hardware),
but forget DOS. (BTW you know what DOS makes before himem.sys ?
Do we have the sources?)
giacomo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Aug 15 2001 - 21:00:33 EST