Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!rutgers!clyde!wayback!atux01!perry From: perry@atux01.UUCP (Perry S. Kivolowitz) Newsgroups: comp.sys.amiga Subject: Re: FACC Message-ID: <495@atux01.UUCP> Date: Tue, 21-Jul-87 00:51:43 EDT Article-I.D.: atux01.495 Posted: Tue Jul 21 00:51:43 1987 Date-Received: Thu, 23-Jul-87 07:27:22 EDT References: <405@sugar.UUCP> Organization: erehwon Lines: 29 Keywords: Problems, suggestions. Summary: All Taken Care Of In article <405@sugar.UUCP>, peter@sugar.UUCP (Peter da Silva) writes: > We just bought FACC, and immediately noticed a few things that are, um, > not optimal. It's really cool, and I understand a new version (FACC II?) > is coming out, but... Peter, many of the things you mentioned were in fact mentioned before (but thank you none-the-less) and have been accounted for in FaccII. I will be formally premiering FaccII at the BCS meeting in Boston Tuesday night (but Jaug did get a sneak preview). Concerning making Facc a disk cache rather than a drive cache: It can be done but it is really not easy. The driver (the level at which Facc does its work) is asked to read sector number of unit N not sector number of disk ``Workbench''. There is no straight forward means for getting around that but as I said, I believe I might have a workable means. If so, then you'll see it become part of the Facc evolutionary path. The FaccII programmer's manual is available from us at no charge if you send a stamped self addressed 8 x 10 inch envelope or larger. Using the FaccII programmer's interface, you can write applications which can control the many new (and of course the old) features re- motely. If the net is interested, I can post a complete run down of new FaccII capabilities and features. Perry S. Kivolowitz - ASDG Incorporated - (201) 563-0529