Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bbn!apple!claris!scott
From: scott@claris.com (Scott Lindsey)
Newsgroups: comp.sys.apple
Subject: Re: RE: Re: Bad //gs?
Message-ID: <8499@claris.com>
Date: 30 Jan 89 03:17:39 GMT
References: <8901290144.aa16380@SMOKE.BRL.MIL>
Organization: Claris Corporation, Mountain View CA
Lines: 22

From article <8901290144.aa16380@SMOKE.BRL.MIL>, by V112PDL5@UBVMSC.CC.BUFFALO.EDU:
> 
>    I've experienced multiple directory corruptions while using AWGS.
> Two people I know have had similar experiences. If you wish to know
> more just ask.

You're not alone.  I've heard several horror stories already.  It appears
that the GS/OS cache is getting corrupted (& I think it's by either GS/OS
itself or tools).  We're trying to see what Apple can do about it.

On a similar note, after an AWGS crash one of our programmers went looking
through memory.  He found that it had crashed somewhere in GS/OS(ProDOS)
code & that it had died because a string had been blasted on top of
code.  The string was something like *:SYSTEM:DRIVERS: ... very probable
that the print manager was responsible.


-- 
Scott Lindsey, wombat    | UUCP: {ames,apple,portal,sun,voder}!claris!scott
Product Development      | Internet:  scott@claris.com  |  AppleLink: LINDSEY1
Claris Corp.             | Disclaimer: These are not the opinions of Claris,
(415) 960-4070           | Apple, the author, or anyone else living or dead.