Groups > comp.os.msdos.programmer > #311

HIMEMX and XMSDSK

From	"Rod Pemberton" <do_not_have@noavailemail.cmm>
Newsgroups	comp.os.msdos.programmer
Subject	HIMEMX and XMSDSK
Date	2011-10-24 20:25 -0400
Organization	Aioe.org NNTP Server
Message-ID	<j84vll$la8$1@speranza.aioe.org> (permalink)

Show all headers | View raw

In another thread, I previously stated:

> Memory is capped at 1GB for WinSE by HIMEMX, but full 4GB
> should be available in MS-DOS.  I've not confirmed though.

and,

> Actually, after playing around a bit with HIMEMX.  It now recognizes 2GB
> after adding /NUMHANDLES=128 to it's config.sys line.  WinSE is capped
> to 1GB via "MaxPhysPage=3FFFF" in system.ini.
>
> I'm not sure why HIMEMX isn't mapping more memory.

Well, I now know why I wasn't getting more memory with HIMEMX.  It wasn't
HIMEX that was the problem ...

HIMEMX v3.32 (Japheth's 2007 fixes) maps all XMS memory that's available.
That's 4GB minus 768MB or so for via MMIO (video card), PCI bus, and BIOS
mapping which leaves about 3.2 or 3.4GB.  However, I was using Franck
Uberto's XMSDSK (v1.9i) to setup a 100MB ramdisk.  It reports just over
100MB by DIR.  However, Japheth's XMSSTAT (in his JEMM package) shows it's
allocating a total of 1GB!  It's allocating 10x as much as it should!  I
confirmed the allocation with another XMS status program called XMSTAT.  It
also seems to use about 60 XMS file handles, eventually freeing 30 of those.
XMSDSK also has problems if XMS is not capped at 2GB or less.  We can guess
why now ...

I did find a 3.33 patch for HIMEMX here that Japheth apparently missed:
http://www.bttr-software.de/forum/board_entry.php?id=6445

That patch has 3 corrections, and 2 errors - 2 unecessary text lines ...
The comments mentions another fix for DRIVER_VER.  And, I found one other
error.  The second driver version value should be in hex also.  This error
is in 3.32 too.  v3.32 reports version 3.20 instead of 3.32 because of it.
E.g.,

DRIVER_VER equ 300h+33h

Japheth's HIMEMX and JEMM
http://www.japheth.de/Jemm.html

Unfortunately, I'm not able to rebuild HIMEMX correctly.   I had to use
JWasm v2.05 v with OpenWatcom's Wlink from v1.3 instead of the recommended
utilities.   That combination produces an incorrect exe header which causes
the info screen to display incorrectly.  I'll be attempting to locate the
incorrect memory for the older machine, i.e., 64MB vs 256MB problem, with
HIMEMX shortly.  I suspect HIMEMX may need another BIOS call to query
memory.

XMSDSK is on Simtel and other sites.  I hope somebody fixes it.  Marko
Kohtala's SRDISK didn't seem to work with WinSE ...  Can someone else
suggest an XMS ramdisk that works for both (DOS, WinSE)?


Rod Pemberton

Back to comp.os.msdos.programmer | Previous | Next — Next in thread | Find similar

Thread

HIMEMX and XMSDSK "Rod Pemberton" <do_not_have@noavailemail.cmm> - 2011-10-24 20:25 -0400
  Re: HIMEMX and XMSDSK "Rod Pemberton" <do_not_have@noavailemail.cmm> - 2011-10-25 12:57 -0400
    Re: HIMEMX and XMSDSK Martin Strömberg <ams@dexter.ludd.luth.se> - 2011-11-02 12:43 +0000
      Re: HIMEMX and XMSDSK "Rod Pemberton" <do_not_have@noavailemail.cmm> - 2011-11-04 04:19 -0400
        Re: HIMEMX and XMSDSK 98 Guy <98@Guy.com> - 2011-11-04 21:02 -0400
          Re: HIMEMX and XMSDSK "Rod Pemberton" <do_not_have@noavailemail.cmm> - 2011-11-06 02:48 -0500
  Re: HIMEMX and XMSDSK Rugxulo <rugxulo@gmail.com> - 2011-10-26 14:04 -0700
    Re: HIMEMX and XMSDSK "Rod Pemberton" <do_not_have@noavailemail.cmm> - 2011-10-26 19:00 -0400
      Re: HIMEMX and XMSDSK "Rod Pemberton" <do_not_have@noavailemail.cmm> - 2011-10-31 18:07 -0400
        Re: HIMEMX and XMSDSK Rugxulo <rugxulo@gmail.com> - 2011-11-01 15:07 -0700
          Re: HIMEMX and XMSDSK "Rod Pemberton" <do_not_have@noavailemail.cmm> - 2011-11-06 04:08 -0500

csiph-web