Hi, if HIMEM64 crashes but FDXXMS PS does not, try the new
/VERBOSE and /METHOD:... command line options of HIMEM/HIMEM64
to find out which of the A20 methods cause the troubles.
When exactly does the crash happen, did you try F8 single step
mode and combinations of DOS={HIGH,LOW},{UMB,NOUMB} and loading /
not loading EMM386 or similar things to pinpoint the problem?
I hear that DOS=UMB can - in some cases - crash because of a
corrupted MCB at 9fff:0 more or less right after the "allocated
... disk buffers" kernel message (which indicates that the
kernel starts to use HMA, no idea why those HMA / UMB cross-
effects happen) in kernel 2032..2034.
My A20 comments which you quote are probably quite outdated by now.
Still valid, however, is the idea that MEMDISK should check
if A20 is actually open before it accesses memory beyond the
first MB (every time), for the case that something in DOS
had the idea to access the virtual disk during a period when
A20 is closed.
Eric
> http://unattended.sourceforge.net/
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/emm386/
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/fdxms/
>
> ... spontaneous reboot on IBM Thinkpad T20 after Kernel diskbuffer HMA info
> ... does not happen if I use
> "DEVICE=fdxxms.sys ps" instead of himem64.exe. And it does not happen
> if I boot from a physical floppy instead of PXELINUX+memdisk.
PS: Try ftp://ftp.devoresoftware.com/downloads/ for emm386/himem updates.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Freedos-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
