Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!VAX1.CC.UAKRON.EDU!mcs.kent.edu!usenet.ins.cwru.edu!news
From: drz@po.cwru.edu
Newsgroups: comp.sys.mac.misc
Subject: Re: Macintalk Replacement?
Message-ID: <1990Oct25.012356.29336@usenet.ins.cwru.edu>
Date: 25 Oct 90 01:23:56 GMT
References: <1990Oct24.042001.25106@usenet.ins.cwru.edu> <1990Oct24.221107.11950@athena.mit.edu>
Sender: news@usenet.ins.cwru.edu
Organization: Case Western Reserve Univ. (Student)
Lines: 30
Nntp-Posting-Host: b63111.student.cwru.edu

In article <1990Oct24.221107.11950@athena.mit.edu> rsfinn@athena.mit.edu
(Russell S. Finn) writes:
>In article <1990Oct24.042001.25106@usenet.ins.cwru.edu>, drz@po.CWRU.Edu
(David
>R. Zinkin) writes:  [in reponse to my claim to the contrary]
>|> 
>|> What's all the talk about System 6.0.7 being incompatible with
>|> MacinTalk?  I've been running the two together for the past three
>|> days with no problems whatsoever.
>|> 
>
>Well, all I know is what I read; I'm not using 6.0.7 yet.  Everything I've
>heard says "Macintalk isn't compatible with the new Sound Manager."  If it
>works for you, that's terrific.  What configuration are you using?
>
>Russell S. Finn
>rsfinn@{athena,lcs}.mit.edu
>

I'm using a Mac SE/30 with 5 MB RAM, two hard drives (80 MB and 40 MB), System
6.0.7, Finder 6.1.7, MultiFinder 6.1b9, and various INITs.  The INITs aren't
making a difference since the same thing happens with or without all INITs
disabled.

It makes me wonder, though; is it possible that MacinTalk works only because
Apple put in "work-around" code?  If anyone has seen the "6.0.6b19 Change
Notes" from apple.apple.com, you'll notice that it mentions that 6.0.5 had
problems with On Cue, and 6.0.7 has special code to allow On Cue to continue to
work.