kik@wjh12.harvard.edu (Ken Kreshtool) (03/21/91)
I would like a stack to talk, but I am having trouble. Trouble City is a IIsi, System 6.0.7, 5 meg RAM, temporarily no INITs or CDEVs or viruses, HC 2.0v2. Both an earlier version of Macintalk (1.2.1?) and the new Macintalk 2.0 give the same trouble. The trouble is as follows. I have tried, one at a time, the XCMDs TALK, SAY (from the excellent but aging HyperMacintalk stack) and SPEAK. All three talk fairly well. But the first system sound that comes along later, e.g. a scripted beep, flashes the menubar silently. Uh-oh. And the second system sound locks the machine, although frantic clicking on the Multifinder icon sometimes eventually frees it. The second system sound can be from anywhere, it seems: another scripted beep, or a click on the Volume slider in the Control Panel, or even a SuperClock chime. The TALK/SAY/SPEAK XCMD is not running at the same time as any sound. The same problem occurs (tested only with TALK) on an SE/30. Needless to say, none of this is ideal. If anybody has anything that works, I'd be VERY grateful. Interestingly, TALK (but not SAY or SPEAK) works with HC 2.0, the bundled non-debugged version -- but only if a sound is still playing when the TALK command is reached by the script. (I discovered this by forgetting to _wait until the sound is done_ one day.) So now I always play Silence and then immediately talk, and run the stack under 2.0. But it seems kind of stupid to ask people to dig out and run HC 2.0. Does anyone have a better way? Thanks, thanks, thanks in advance. And Apple, how about making Macintalk into a real, robust, non-crashy little gizmo. Macintalk is terrific, even if it does sound vaguely Scandinavian; please make it work. Ken Kreshtool (kik@wjh12.harvard.edu) By the way, this is my first attempt both at posting and at using our wildly buggy editor, so if things are screwy, I apologize.
bin@primate.wisc.edu (Brain in Neutral) (03/22/91)
My experience with MacinTalk on new machines is that *any* system beep but the built in beep will hang the machine. That is, any sampled sound. This is probably due to contention between the new Sound Manager and MacinTalk, which wants to directly control the sound hardware itself. I make sure to select the default system beep before I run something which requires MacinTalk. This is with System 6.0.7. The situation will only get worse with System 7.0, unless Apple comes up with another MacinTalk that behaves itself. BTW, MacinTalk 2.0 isn't really any different than the previous version. Open 'em both with ResEdit and compare the DRVR resources. Same size. -- Paul DuBois dubois@primate.wisc.edu
tom@wcc.oz.au (Tom Evans) (03/28/91)
In article <4088@uakari.primate.wisc.edu>, bin@primate.wisc.edu (Brain in Neutral) writes: > My experience with MacinTalk on new machines is that *any* system beep For ALL the information on MacinTalk, refer to Macintosh Technical Note 268, dated February 1990 (yes, last year), and titled "MacinTalk - The Final Chapter". > The situation will only get worse with System 7.0, unless Apple > comes up with another MacinTalk that behaves itself. Not a prayer. I started including bits of this Tech Note, but you really should read the lot. Using MacinTalk without full knowledge of all the things that go wrong and what it interferes with is "dangerous". Hasn't anyone ever released a commercial, supported replacement? ======================== Tom Evans tom@wcc.oz.au ** ADD ".au" MANUALLY (don't trust "reply") ** Webster Computer Corp P/L, 1270 Ferntree Gully Rd Scoresby, Melbourne 3179 Victoria, Australia 61-3-764-1100 FAX ...764-1179 A.C.N. 004 818 455
dlong@ux1.cso.uiuc.edu (David Long) (03/29/91)
tom@wcc.oz.au (Tom Evans) writes: >> The situation will only get worse with System 7.0, unless Apple >> comes up with another MacinTalk that behaves itself. >Not a prayer. I started including bits of this Tech Note, but you >really should read the lot. Using MacinTalk without full knowledge of >all the things that go wrong and what it interferes with is >"dangerous". >Hasn't anyone ever released a commercial, supported replacement? The folks who wrote the Talking Moose apparently managed to patch it enough to get it running under 6.0.7. I don't have it myself- a programmer friend bought it and it seems to run fine on his system. If you're *really* interested in a working MacinTalk, you might give them a call. -- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ dave long dlong@ux1.cso.uiuc.edu research programmer dlong@uxh.cso.uiuc.edu computing services office AppleLink: A0377
cpk@valideast.COM (C. Kumar) (04/17/91)
In article <1667@wcc.oz.au> tom@wcc.oz.au (Tom Evans) writes: >Hasn't anyone ever released a commercial, supported replacement? Try "Talking Moose" Xcmds. Nice implementation, no bombs. As far as I know Macintalk was not even modified. -- C. Kumar Valid Logic Systems, PCB Division, 2 Omni Way Chelmsford, MA. (508) 256-2300 !uunet!valideast!cpk