Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!ucsd!sdd.hp.com!elroy.jpl.nasa.gov!ncar!boulder!pikes!mercury.cair.du.edu!orion.cair.du.edu!rcarver
From: rcarver@orion.cair.du.edu (RANDALL CARVER )
Newsgroups: comp.windows.ms
Subject: Windows 3.0, Priam Hard Drives, and Bastard Clone Boards
Summary: AAARRRGGGHHH!!!
Message-ID: <1990Aug7.045746.15483@mercury.cair.du.edu>
Date: 7 Aug 90 04:57:46 GMT
Sender: news@mercury.cair.du.edu (netnews)
Organization: University of Denver
Lines: 32


I caught an inkling of the problem that windows 3.0 has with the Priam 
InnerSpace program EDVR.SYS.  While we are not using EDVR.SYS windows
is still barfing up pretty badly.  I think part of the problem may lie
in the fact that the priam disk is not a true Dos disk (chkdsk doesn't
think so), and they also warn you pretty strongly about using dos 
formatting.  I'm still waiting to here from Priam on this though.

Furthermore we're running a bastard 386 clone board - a Precision 386
baby II (No I wasn't here when it was purchased so at least that much
isn't my fault) with 640K and 8M expanded memory.  

The errors I'm getting are as follows:
	win /s - either no error message just the win intro then back to dos
			 - or insufficient memory 
	win /3 - same in both cases
***note: these error messages seem to appear randomly with no change to 
config.sys or autoexec.bat

It will run in Real Mode, Telling me that mem is something like 531K
328K EMS, and expanded is up at about 6M
	Inside windows Real Mode-
			Often get the message Insufficient memory to run application.

As to the exact nature of these messages I must apologize. I nuked 
Windows 3.0 until either Priam or MS get back to me.

Please if anyone has any information email me or post it if you
think its worthwhile.

Thanx in advance,
Randy Carver