[comp.windows.ms] What is WINHIRAM.VXD?

kapela@prism.poly.edu (Ted Kapela) (04/14/91)

I have checked the manuals for QEMM/Manifest and could not find
what this is.  By doing a "strings" on it, it appears to me
to be another driver for windows 3.0.  If anyone knows what it
is, or where I can find out, please let me know.  Don't just
say RTFM, tell me where, since I already DID RTFM.

Thanx in advantz.
-- 
..............................................................................
    Theodore S. Kapela			ted@{tasha|gracie}.poly.edu
					(516) 755-4299 [Days]
           "Another brilliant mind corrupted by education"

jjw@hpcndpc.CND.HP.COM (Jimmy Wright) (04/16/91)

> I have checked the manuals for QEMM/Manifest and could not find
> what this is.  By doing a "strings" on it, it appears to me
> to be another driver for windows 3.0.  If anyone knows what it
> is, or where I can find out, please let me know.  Don't just
> say RTFM, tell me where, since I already DID RTFM.

	This is a Virtual Device Driver that was provided by Microsoft
	to 3rd Party Memory Managers.  Whenever Windows 3.0 is started up
	in 386 Enhanced Mode this Virtual Device Driver ( Microsoft calls
	it LoadHi ) will be loaded by QEMM-386.  This virtual device
	driver will fix problems in instancing and supporting TSRs loaded
	between 640-1MB (i.e. UMB memory) via QEMM-386.  If you had
	386MAX they call theirs 386MAX.VxD.  Same concept.  The LoadHi
	VxD distributed by Microsoft to them was given in the form so that
	vendors could change it.  The one that Quarterdeck shipped with
	5.11 was buggy and caused all kinds of problems under certain
	circumstances.  It mostly caused problems for networks that were
	also using VxD's to support their networking.  The WINHIRAM.Vxd
	shipped with 5.11 changed the way ( actually incorrectly ) some
	of the Windows kernel memory management calls returned.  Most of
	these calls that failed were only used by other Virtual Device
	Drivers whose purpose was to bridge Windows Applications or DOS
	applications running in Virtual Machines to software such as
	networking which was loaded before Windows.

	I know all of this because I reported most of the problems to
	Microsoft, QuarterDeck, and Qualitas since I was responsible for
	modifying our networking to work with Windows 3.0.

	There was an article I believe in PC Week or some PC trade rag
	that talked about this VxD.

> 
> Thanx in advantz.
> -- 

	JJ