Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!ndsuvax!ndsuvm1.bitnet!nu092254
From: NU092254@NDSUVM1.BITNET (Brian Dall)
Newsgroups: comp.sys.apple
Subject: MouseTalk and ramcards
Message-ID: <455NU092254@NDSUVM1>
Date: Mon, 23-Nov-87 12:12:34 EST
Article-I.D.: NDSUVM1.455NU092254
Posted: Mon Nov 23 12:12:34 1987
Date-Received: Sat, 28-Nov-87 05:20:54 EST
Organization: North Dakota Higher Education Computer Network, Fargo, ND
Lines: 29
DISCLAIMER: Author bears full responsibility for contents of this article.



     I have heard from a friend that there is a problem with using
AE Pro MouseTalk with a Ramdisk.
     He has a RamWorks II with 1 meg of Aux. memory on it and sets
a 768K /ram disk using the software provided with the card (which
leaves 256K of Aux. memory plus 64K on motherboard).

     He says that no matter what he tries, MouseTalk goes out and
actively destroys his ramdisk.  He said he tried renaming the volume
(to /tdisk or something) and tried changing the slot the ramdisk
emulates, but MouseTalk still goes out and kills the files, although
sometimes strange things happened.

     It is incredible that a program could have 320K of memory to
play around in and still want to go and zap the rest of it

     He said he sent the company a postcard, but hasn't gotten a
reply yet (truthfully, I'm not sure he actually sent it yet).

     The version that he has is 1.30.  Does anyone out there in
netland know if there is a new version out that doesn't resort
to such nasty tricks?
       take care,
                                     -Bri
________________________________________________________________________
Brian Dall        |                           |"It is dangerous to tell
PO Box 5112       |  NU092254@NDSUVM1.BITNET  | the people that laws are
NDSU Station      |                           | not just. . . ."
Fargo, ND  58105  |                           |  -Blaise Pascal