Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rochester!pt.cs.cmu.edu!andrew.cmu.edu!postman From: jv0l#@andrew.cmu.edu (Justin Chris Vallon) Newsgroups: comp.sys.mac Subject: Re: Macintalk Answers... Message-ID:Date: Fri, 9-Jan-87 13:33:57 EST Article-I.D.: andrew.MS.V3.18.jv0l.80020d02.mercer.ibm032.744.4 Posted: Fri Jan 9 13:33:57 1987 Date-Received: Sat, 10-Jan-87 00:36:01 EST Organization: Carnegie-Mellon University Lines: 42 ReSent-Date: Fri, 9 Jan 87 13:37:58 est ReSent-From: postman#@andrew.cmu.edu ReSent-To:nntp-xmit#@andrew.cmu.edu Return-path: To: outnews#ext.nn.comp.sys.mac@andrew.cmu.edu In article <4484@@mit-eddit.MIT.EDU>, barmar@@mit-eddie.MIT.EDU (Barry Margolin) writes: >In article <856@@uwmacc.UUCP> rick@@unix.macc.wisc.edu.UUCP (Rick Keir) writes: >>Big catch: "Macintalk must be in the same folder as your application." >>It looks like a system file. Put it in the system folder and your >>application will not talk. Some will warn you that "Macintalk" could >>not be found; others will simply crash. Put it in the application's >>folder. > >I've never noticed this restriction. I admit that I only use a few >speaking applications (Servant, VCS, ExceptionEdit) but they all work >with MacinTalk in the system folder. And yes, I am using HFS. > >Since Macintalk is just a device driver, I can't imagine why it would >be any different from any other device. Macintalk is not a device driver, it is a resource file which contains a device driver. This presents a problem to developers who did not think about the location of the Macintalk file. When the applications open the resource file to get the driver out of it, they should use the path :system folder:macintalk if under HFS to enable the application to open the file in the system folder. Problems arise if the application was written for MFS, since the path would be: macintalk because there are no subdirectories. Under HFS, non-prefixed files are prefixed to the subdirectory that the application was opened in (or the last subdirectory selected in an FSGetFile dialog). So, depending on whether the application was written for MFS or HFS, the application will get confused if placed into the other file system. -- Justin Vallon jv0l@andrew.cmu.edu