Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!tut.cis.ohio-state.edu!ucbvax!SUVM.BITNET!MAXG From: MAXG@SUVM.BITNET (Gerry Greenberg) Newsgroups: comp.sys.atari.st Subject: magic sac/translator? problems Message-ID: <8902200430.AA04601@ucbvax.Berkeley.EDU> Date: 20 Feb 89 04:30:32 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 58 X-Unparsable-Date: Sun, 19 Feb 89 22:49:15 LCL I am having some problems with my magic sac set up and was hoping that someone might be able to help me. I figured I'd try this group first because I'm trying to cut down on my GENIE costs, I know there a whole lot of people who read the digest who know quite a bit, and finally I figure that since Dan Moore and David Small post things here periodically, if no one else can help out, maybe they can and would be willing to give me some tips. Anyway, before I get to the problem, here's my setup: 520ST upgraded to 1Meg (MONO) Magic Sac and Translator1 One SF354 (Single Sided Drive) [Drive A] One Mitsubishi Double Sided drive that I bought used...it was an IBM drive that was adjusted to work with the ST [Drive B] I work with MS Word. I have the application, help file, main dictionary, and standard glossary on a double sided disk in drive B and I keep the documents on a single sided disk in drive A. I ran this system for about 6 months without the translator and had no problems...I bought the translator used and had no problem for 2 or 3 months, but have recently started to have the following problem: I will save a document and then quit Word. When I get back to the Finder level, the double sided disk will sometimes need minor repairs, will sometimes have the same files that are on the disk in Drive A (while retaining the same number of bytes used as it did before I ran Word...e.g. I just tried it out and here's what happened...I used a new document disk and save a 4 line file on it...that took up, let's say, 3K. When I quit Word, the application disk in Drive B showed that it only had this one document file, but that the disk had over 500K or 600K with over 100K or something left---this is what it should be with Word, the dictionary, etc. on the disk). So, the application disk in Drive B sometimes looks just like the disk in Drive A, sometimes it retains all of its original files, but then picks up the saved document, even though I didn't save the document to that drive. Once or twice I was able to get the disk back to normal by ejecting it (dragging to trash) and then reinserting it, but this doesn't always work. A little more info...I tried running the translator test on the drives...Drive A is OK, but Drive B doesn't seem able to Format Mac disks...I didn't think this should matter with regard to my other problem because I only use 800K disks that are in Magic format. Drive B formats fine in Magic mode, and I have no trouble with it in ST mode. Well, I think that is about all that I can think of ... I did have a problem with two other disks...but I didn't really play around with them as much as I did in connection with the problem I outlined above. I have MacWrite on two disks and when I tried to open it on both disks, I got a message that the disks were too full to open a document. Both disks showed that they had over 100K free, and I even copied a file to one disk, but still couldn't open MacWrite. This situation, too, has happened only after adding the translator to the system...I haven't used MacWrite in a long time, so I don't remember if the problem is really directly related to the translator...I do know that I used MacWrite just after I got the Sac for a while and had no problems. Well, that's it...I hope I was able to describe the problem understandably enough...I would greatly appreciate hearing from anyone who has had this (or a similar) problem, and even more greatly appreciate hearing from someone who has a solution to this problem. You can post replies to the network, or send them to me at either of the following addresses: MAXG @ SUVM (BITNET) ggreenbe @ rodan.acs.syr.edu (Internet)