Newsgroups: comp.os.msdos.desqview
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!ukma!jayh
From: jayh@ms.uky.edu (Jay Hofacker)
Subject: Re: Perstor ARLL controller and DESQview
Message-ID: <1991Jun2.173146.9926@ms.uky.edu>
Organization: University Of Kentucky, Dept. of Math Sciences
References: <31MAY91094739@vms.huji.ac.il>
Date: Sun, 2 Jun 1991 17:31:46 GMT
Lines: 22

gilf@VMS.HUJI.AC.IL (GIL FREUND) writes:

>I have been having problems working with a Perstor ARLL. This controller 
>doubles the capacity of some MFM disk drives, and even speeds them up 
>a little. 
>However, since I installed this controller, DESQview hang, in almost
>every session, and communications are interupted. The dealer I baught
>the controller from refuses to acknowlage the problem, puting is down
>to the software (what else).

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.


-- 
Jay Hofacker, sysop of the Audio/Visual Exchange, (606)254-1751 3/12/24 MNP 5
Mail: jayh@ms.uky.edu / uk02779@ukpr.uky.edu -- Yes, my signature is only 2 lin