Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site uw-beaver
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxb!mhuxn!mhuxm!mhuxj!houxm!vax135!cornell!uw-beaver!info-mac
From: info-mac@uw-beaver
Newsgroups: fa.info-mac
Subject: Lisa Workshop Questions
Message-ID: <646@uw-beaver>
Date: Wed, 30-Jan-85 05:49:29 EST
Article-I.D.: uw-beave.646
Posted: Wed Jan 30 05:49:29 1985
Date-Received: Thu, 31-Jan-85 01:35:36 EST
Sender: daemon@uw-beaver
Organization: U of Washington Computer Science
Lines: 42

From: zauderer%ucbcory@Berkeley (Marvin M. Zauderer)



   I keep telling myself that there are other equally frustrated souls
'out there' who are using the Lisa to develop software for the Mac. We've
had a tremendous number of problems with both the hardware and the workshop
software; here are two that we are currently agonizing over -- can you help?
   The first concerns the disk drive (we think). We had been creating Mac-
executable programs for quite a time, yet 'all of a sudden' the (Mac) disk
to which the Lisa writes these files became unreadable (by the Mac). It
would not boot on the Mac, nor could it be initialized on the Mac (an
initialization attempt resulted in an 'initialization failed' message). 
But, strangely enough, we COULD use the disk under MacWorks on the Lisa!
We thought this was fairly strange, but put up with it for a day while
we thought about what to do next. Of course, the disk then became unreadable
by the Lisa as well (Murphy's law?). We tried using a brand new disk, but
had the same problem. So, we opened up the Lisa, played
a little frisbee with the disk drive, and put everything back together
again. 
   Everything then worked fine. My questions are these: any ideas on how
to recover the contents of the 'trashed' disks? Has anyone else had this
problem? 
   The second problem concerns Version 3.0 of the Workshop. We've noticed
that something seems to eat up disk space at an alarming rate. Every time
we use the editor or compile, more disk space is eaten. If we let the
process go on for too long, we end up having fewer free blocks than is
necessary to run the Workshop, and it crashes. We've been using the 'Repair'
feature of the Pascal 1 disk before this happens, and that manages to
restore all of our free space. We also did an 'Online' (in the File
Manager), which listed a '24' under the 'Open' column for the hard disk.
I haven't looked in the manual yet, but I'm guessing that means 'open
files', which might account for the great loss of disk space. I may be
reaching, but I also don't know what could be causing this problem. Any
ideas?
   Your help and/or encouragement is greatly appreciated. The until-recently
free-of-charge 'Lisa Hotline' has now been magically transformed into a
'10 dollars per solution' service, so our budget appreciates your help as
well.

Cheers,
Marvin