On 27 Oct 00 at 22:51, arachne-digest wrote:
> From: [EMAIL PROTECTED]
> Neil Parks wrote:
> > LOADLIN complains that it does not like my EMM386.
> It is true that LOADLIN chokes on the NOVCPI parameter,
> but I've never met anyone who needed NOVCPI.
> I suggest you leave out the NOVCPI.
> Cheers,
> Steven
Tried that, but Loadlin still doesn't like it:
[Network] C:\BASLINUX>boot
LOADLIN v1.6 (C) 1994..1996 Hans Lermen <[EMAIL PROTECTED]>
CPU is in V86-mode (may be WINDOWS, EMM386, QEMM, 386MAX, ...)
You need pure 386/486 real mode or a VCPI server to boot Linux
VCPI is supported by most EMS drivers (if EMS is enabled),
but never under WINDOWS-3.1 or WINDOWS'95.
(However, real DOS-Mode of WINDOWS'95 can have EMS driver with VCPI)
If loading via VCPI you also MUST have:
1. An interceptable setup-code (see MANUAL.TXT)
2. Identical Physical-to-Virtual mapping for the first 640 Kbytes
Your current DOS/CPU configuration is:
load buffer size: 0x00000000 , setup buffer size: 0x3E00
total memory: 0x00100000
CPU is in V86 mode
SetupIntercept: NO
stat3: VCPI_present, but physmap != logmap (check aborted)
input params (size 0x002A):
zimage root=/dev/ram rw initrd=baslinux.gz
LOADLIN started from DOS-prompt
WARNING: Not enough free memory (load buffer size)
[Network] C:\BASLINUX>
--
...This msg brought to you by NEIL PARKS Beachwood, Ohio
mailto:[EMAIL PROTECTED] http://www.en.com/users/neparks/
