Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!mips!pacbell.com!att!ucbvax!VMS.HUJI.AC.IL!gilf
From: gilf@VMS.HUJI.AC.IL (GIL FREUND)
Newsgroups: comp.os.msdos.desqview
Subject: Perstor ARLL controller and DESQview
Message-ID: <31MAY91094739@vms.huji.ac.il>
Date: 31 May 91 06:47:39 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: gilf@vms.huji.ac.il
Organization: The Hebrew university of Jerusalem
Lines: 22

Hi All,

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 heard elsewhere the Prestor and Zmodem conflict, and that Perstor 
is sending a fix for it, but my mail to Perstor was returned stamped
"Service Discontinued".
Does anyone else have any information? I think the problem is that the 
Perstor controller 1) uses memory locations that conflict with DESQview,
and, 2) uses an interupt that conflicts with communication.
Does anyone have any idea if those problems can be resolved using software
alone? Can anyone send me the address for Perstor (the one on the manual
is either wrong, or outdated)?

Thanks in advance.

Gil