hm?
I am trying to boot "real" DOS from linux.
> emm386.exe attempts to go to protected mode. That's how it works.
and when going into protected mode, it crashes. I wonder why. I can
start DOS4GW, which does not crash, and I think that DOS4GW too works
with the protected mode features of the CPU.
> That's how it's able to make "high-RAM" appear in "low-RAM" windows
> for the emm386 specification. Of course it will fail when you
> are in virtual 386 mode. The real DOS-EMU emulates the extended/expanded
after executing "machine_real_start", the system is in 16 bit real mode,
not in vm86 mode.
> memory specification so you don't need this in 'config.sys'. I sometimes
> boot real DOS usinf DOS-EMU and it works fine. You need to configure
> it so it will look at, say config.emu, instead of the DOS config.sys.
> That way, you can keep boot-specific configuration files.
the problem is not only with DOS. when booting M$-Windows (w2k), the
boot-process will hang as soon as w2k tries to enter protected mode.
starting loadlin will hang the system too, as I just found out. hm,
well, at least it's easier looking into loadlin than looking into
emm386 !
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
> Why is the government concerned about the lunatic fringe? Think about it.
>
>
-
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/