Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!mips!daver!leadsv!iscnvx!jay
From: jay@iscnvx.uucp (Jay D Ward)
Newsgroups: comp.windows.ms
Subject: Re: HyperDisk
Message-ID: <1991Jun10.142600.26759@iscnvx.uucp>
Date: 10 Jun 91 14:26:00 GMT
References: <1991Jun5.205315.8938@DMI.USherb.CA> <2770026@hparc0.HP.COM> <1991Jun7.173530.27497@iscnvx.uucp> <50211@ut-emx.uucp>
Organization: LMSC -  Information Services
Lines: 36

In article <50211@ut-emx.uucp> victor@ccwf.cc.utexas.edu (Victor Menayang) writes:
>In article <1991Jun7.173530.27497@iscnvx.uucp> jay@iscnvx.uucp (Jay D Ward) writes:
>>
>>Be careful!!  According to the author of HyperDisk, it needs a whole
>>64k segment in order to test and initialize it's buffers. If it
>>doesn't have enough memory, it will appear to function, but it will
>>actually be disbled!  
>
>Are you saying that you cannot even rely on hyperdk's report
>to tell whether hyperdisk is functioning or not?

No, I'm saying that there is no indication of an error when it initializes.
You won't realize that it's not working until you run hyperdk.

>
>>                      The registered version can be loaded high via
>>the "xs" parameter, which works with QEMM or the C&T bios w/o QEMM.
>
>Nowhere in the online manual does the author mention something
>about disabling the XS feature in the unregistered version.
>Am I missing something here?

That was definately the case with version 4.11. I haven't
upgraded to 4.2 yet, so maybe that has changed.

>
>-- 
>Victor Menayang         victor@ccwf.cc.utexas.edu (Internet) 
>                                           vm@UTXVM (BITNET)
>                     ...!cs.utexas.edu!ut-emx!rtf1000 (UUCP)
>-------------------------------------------------------------

------------------------------------------
Jay D. Ward,  jay@iscnvx.lmsc.lockheed.com
-- 
----------------------------------------------------