Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!ns-mx!ccad12.icaen.uiowa.edu
From: cad16@ccad12.icaen.uiowa.edu (CCAD student account)
Newsgroups: comp.windows.ms
Subject: Re: HyperDisk
Message-ID: <6357@ns-mx.uiowa.edu>
Date: 5 Jun 91 21:54:04 GMT
References: <1991Jun5.205315.8938@DMI.USherb.CA>
Sender: news@ns-mx.uiowa.edu
Reply-To: cad16@icaen.uiowa.edu
Lines: 35

From article <1991Jun5.205315.8938@DMI.USherb.CA>, by aa41@terre (Eric Trepanier):
> I followed the latest SmartDrv vs HyperDisk debate with much interest.
> Certain articles in favor of HyperDisk led me to give it a try and find out
> for myself.  So I got a copy from Simtel and unzipped it.
> 

[ discussion delete ]

> 
> Has anyone had any success configuring HDK with QEMM512 and memory release
> options?  What are the best settings on a 4Mb system?

I have.  I don't use it 'cause it always screws something up so
I get some message like "packed file corrupt" when trying to
run executables (DOS type) after it runs for a while.  Who knows why,
I've seen references to this.  Anyway, I used HYPERDKX.EXE with
c:1024:512 and X (to load it into my C&T upper memory block).  It
all worked fine in general.  No goofiness, no nothin'.  Matter of
fact, it even co-existed with PC-NFS and Windows in 386 mode.  No small
matter, mind you.  If necessary, I can mail my config.sys and autoexec
files so you can see what's what.

BTW, i solved the "packed file corrupt" problem by calling hyperdk.exe
and asking it to halv the memory for the cache, then again to set it
back to full, then the packed exe's come out ok.  I don't know if
this is a EXEPACK type problem or HYPERDISK, but its there.

Mail me at cadsi@cadfx.ccad.uiowa.edu (128.255.12.10) if you want my
QEMM settings and HYPERDISK too.

|----------------------------------------------------------------------------|
|Tom Hite					|  The views expressed by me |
|Manager, Product development			|  are mine, not necessarily |
|CADSI (Computer Aided Design Software Inc.	|  the views of CADSI.       |
|----------------------------------------------------------------------------|