[comp.sys.ibm.pc.misc] Dos 5 - strange result from mem /c command

leoh@hardy.hdw.csd.harris.com (Leo Hinds) (06/20/91)

I was messing around with my recently installed dos5 and did a "mem /c" ... 
interesting results ... a portion of my path statement is using 13.7k !!

	Conventional Memory :
	
	  Name                Size in Decimal       Size in Hex
	-------------      ---------------------   -------------
	  MSDOS              16752      ( 16.4K)       4170
	  SETVER               400      (  0.4K)        190
	  HIMEM               2896      (  2.8K)        B50
	  ANSI                4192      (  4.1K)       1060
	  NI5210              3328      (  3.3K)        D00 <== ethernet driver
	  SMARTDRV           21712      ( 21.2K)       54D0
	  PCNFS              69152      ( 67.5K)      10E20 <== pcnfs driver
	  SOCKDRV             1200      (  1.2K)        4B0 <== pcnfs driver
	  COMMAND             2624      (  2.6K)        A40
	  PRT                 4848      (  4.7K)       12F0 <== pcnfs driver
===>	  p;c:\net           14016      ( 13.7K)       36C0 <== mouse-supposedly
	  FREE                  64      (  0.1K)         40
	  FREE                 192      (  0.2K)         C0
	  FREE              513632      (501.6K)      7D660
	
	Total  FREE :       513888      (501.8K) 
	
	Total bytes available to programs :                   513888   (501.8K)
	Largest executable program size :                     513392   (501.4K)
	
	   1048576 bytes total contiguous extended memory
	         0 bytes available contiguous extended memory
	    196608 bytes available XMS memory
	           MS-DOS resident in High Memory Area


Anyone seen this? ... any thoughts? ... looks like some kind of data 
structure/array has been corrupted ... I wounder what else was/will be affected?
leoh@hdw.csd.harris.com         	Leo Hinds       	(305)973-5229
Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n
creireg ?!!!!!!? ... znlor arkg gvzr

gtoye@hp835.mitek.com (Gene Toye) (06/20/91)

In <3710@travis.csd.harris.com> leoh@hardy.hdw.csd.harris.com (Leo Hinds) writes:

>I was messing around with my recently installed dos5 and did a "mem /c" ... 
>interesting results ... a portion of my path statement is using 13.7k !!

>===>	  p;c:\net           14016      ( 13.7K)       36C0 <== mouse-supposedly

>Anyone seen this? ... any thoughts? ... looks like some kind of data 
>structure/array has been corrupted ... I wounder what else was/will be affected?

I suspect you have a mouse driver that deallocates its environment memory
block.  Several guides on TSR development recommend this as a way to
reduce TSR memory requirements, since most TSRs don't need an environment.
For this, it works well (I've used the technique myself in some TSRs I
wrote).  It does have the side effect of rendering memory utilities unable
to display the program name, since it is kept in the same memory block
as the environment.  Anybody have any other ideas?
>leoh@hdw.csd.harris.com         	Leo Hinds       	(305)973-5229
>Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n
>creireg ?!!!!!!? ... znlor arkg gvzr
-- 
Gene Toye, Software Engineer                               gtoye@hp835.mitek.com
OpenConnect Systems, 2033 Chennault Drive, Carrollton, TX 75006
214/308-0454
DISCLAIMER: My employer had no idea I was going to say that.