Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!crdgw1!barnett From: barnett@grymoire.crd.ge.com (Bruce Barnett) Newsgroups: comp.sys.mac.misc Subject: Re: MS Mail and SAM Problems Message-ID: Date: 9 Aug 90 18:29:56 GMT References: <4379@crystal9.UUCP> <43804@apple.Apple.COM> Sender: news@crdgw1.crd.ge.com Reply-To: barnett@crdgw1.ge.com Distribution: comp Organization: GE Corp. R & D, Schenectady, NY Lines: 42 In-reply-to: chuq@Apple.COM's message of 9 Aug 90 17:29:34 GMT In article <43804@apple.Apple.COM> chuq@Apple.COM (Spot the Wonder Dog) writes: > I can make a broad, semi-educated guess about your problems. The guess is > "It isn't SAM's fault". I can make a narrow, educated guess: It is. :-) We saw this problem when we have Sam 2.0, MS Mail, and a StartUp Picture. Deleting the startup picture was one way around the problem. Paul Cozza, Author of SAM, sent me the following note with three other ways to work around the problem. ------------------------- From: D1660@applelink.apple.com (SoftPlus, Paul Cozza,PRT) Date: 29 Jun 90 21:39 GMT If you have SAM Intercept 2.0 installed on those machines, then I know what your problem is. There is a very bizarre compatibility problem between MS Mail and early versions of SAM 2.0 that cause exactly what your seeing (it wasn't easy trying to figure out what a startup screen could have to do with it!). Anyway the solution is any ONE of the following: 1) Rename MS Mail to run before SAM Intercept 2) a) Open up the MS Mail file from ResEdit b) Open up the WDEFs window c) Select the only WDEF (#16) and choose Get Info from the file menu d) Click the System Heap check box on e) Save the change 3) Call Symantec, tell them the problem and ask for the latest version of SAM. I put in code to handle this situation some time ago. [Note - this is verison 2.0.2b] Paul Cozza Author of SAM -- Bruce G. Barnett barnett@crd.ge.com uunet!crdgw1!barnett