Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ucla-cs!ucivax!orion.oac.uci.edu!ucsd!qualcom.qualcomm.com!cancun.qualcomm.com!rdippold
From: rdippold@cancun.qualcomm.com (Ron Dippold)
Newsgroups: comp.os.msdos.desqview
Subject: Re: Perstor ARLL controller and DESQview
Message-ID: <1991Jun6.181124.22687@qualcomm.com>
Date: 6 Jun 91 18:11:24 GMT
References: <31MAY91094739@vms.huji.ac.il> <1991Jun2.173146.9926@ms.uky.edu> <7021@bwdls58.bnr.ca>
Sender: news@qualcomm.com
Organization: Qualcomm, Inc., San Diego, CA
Lines: 20
Nntp-Posting-Host: cancun.qualcomm.com

In article <7021@bwdls58.bnr.ca> mlord@bwdls58.bnr.ca (Mark Lord) writes:
>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..

It must be the Perstor or your version of HyperDisk.  HyperDisk 4.20 works
perfectly well with DesqView with full functionality.
-- 
Standard disclaimer applies, you legalistic hacks.     |     Ron Dippold