Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!bionet!apple!rutgers!cs.utexas.edu!sm.unisys.com!ucla-cs!prince
From: prince@maui.cs.ucla.edu (Larry Prince)
Newsgroups: comp.sys.mac
Subject: Re: Pyro 3.0 / Disktop 3.02 Compatibility Problems
Message-ID: <17613@shemp.CS.UCLA.EDU>
Date: 7 Nov 88 18:28:10 GMT
References: <17450@shemp.CS.UCLA.EDU> <5841@fluke.COM>
Sender: news@CS.UCLA.EDU
Reply-To: prince@cs.ucla.edu (Larry Prince)
Organization: UCLA Computer Science Department
Lines: 32

In article <5841@fluke.COM> moriarty@tc.fluke.COM (Jeff Meyer) writes:

 >>Just got Pyro 3.0 . . . oboy!  Didn't work . . . oh no!
 >>
 >>(Initial copyright screen appears, but then it jumps right back out
 >>to the desktop.)
 >>
 >>According to Fifth Generation Systems, problem is incompatibility with
 >>Disktop 3.02 which bumps heads with it resource-wise.  The fix: Disktop 3.03.
 >
 >Huh!  I've been using Pyro 3.0 and Disktop 3.02 for a couple days, and no
 >problems have occured with either.  Pyro seems to work fine -- do you have
 >certain options set which cause it not to work with DiskTop?  Also, did CE
 >say whether DiskTop 3.03 is an upgrade for any other reason besides Pyro
 >3.0?
 >

I don't know what's different between my system and yours...they didn't
indicate to me whether it would work in some cases and not others.  The
tech I spoke to just immediately asked me (after I described the above
symptom) whether I was running Disktop 3.02...when I said yes, he told
me to get 3.03 and the problem would go away.

I then called CE Software and asked them for the upgrade...they didn't
say whether it would fix anything else (and I neglected to ask).  I did
ask, however, why it wasn't publicized, and they said it was such a
minor upgrade that it wouldn't affect many users (!).


		    UCLA Computer Science Department
   -- Larry         3413 Boelter Hall   Los Angeles 90024  (213) 825-2145
	 Prince     UUCP:    {ucbvax,sdcrdcf}!ucla-cs!prince
		    ARPAnet:  prince@CS.UCLA.EDU