Path: utzoo!utgpu!cunews!bnrgate!bwdls58!mlord
From: mlord@bwdls58.bnr.ca (Mark Lord)
Newsgroups: comp.os.msdos.desqview
Subject: Re: Perstor ARLL controller and DESQview
Message-ID: <7021@bwdls58.bnr.ca>
Date: 5 Jun 91 14:38:53 GMT
References: <31MAY91094739@vms.huji.ac.il> <1991Jun2.173146.9926@ms.uky.edu>
Sender: mlord@bwdls58.bnr.ca
Reply-To: mlord@bwdls58.bnr.ca (Mark Lord)
Organization: Bell-Northern Research, Ottawa, Canada
Lines: 21

In article <1991Jun2.173146.9926@ms.uky.edu> jayh@ms.uky.edu (Jay Hofacker) writes:
<I have no problems running my PS180-16FN 16 bit Perstor card in my BBS machine,
<which runs Maximus BBS software under Desqview 2.31 and QEMM 5.11.  When I
<first installed the Perstor card, I did have problems with lock ups under DV,
<but I traced the problems to HyperDisk, a disk cache.  The system locked up
<under DV when I had HyperDisk doing 'stagged writes', which means it caches
<writes to the drive as well as reads.  After I set Hyperdisk to be a read-only
<cache (just like Microsoft's smartdrv.sys), the problem went away.

How interesting.  And I thought it was just my system.  I too cannot use 
Hyperdisk Staged writes while inside Desqview, even though it works fine
outside and in windows3 etc.. and the HyperDisk docs claim that it should
work okay in Desqview.  Hmm.. time to reverse engineer the Perstor BIOS
and see 'xactly what they're doing in them ROMs..
-- 
MLORD@BNR.CA  Ottawa, Ontario *** Personal views only ***
begin 644 NOTSHARE.COM ; Free MS-DOS utility - use instead of SHARE.EXE
MZQ.0@/P/=`J`_!9T!2[_+H``L/_/+HX&+`"T2<TAO@,!OX0`N1(`C,B.P/.DS
<^K@A-<TAB1Z``(P&@@"ZA`"X(27-(?NZE@#-)P#-5
``
end