hunter@oakhill.UUCP (Hunter Scales) (01/22/90)
Last nigh I noticed that Tappy Type ( the typewriter sound init)
wasnt working. After some experimentation, I found that with
Suitcase II installed, Tappy Type wont work. Has anybody else
noticed this?
--
Motorola Semiconductor Inc. Hunter Scales
Austin, Texas {harvard,utah-cs,gatech}!cs.utexas.edu!oakhill!hunter
#include <disclaimer.h>hankin@sauron.osf.org (Scott Hankin) (01/23/90)
hunter@oakhill.UUCP (Hunter Scales) writes: > Last night I noticed that Tappy Type ( the typewriter sound init) > wasnt working. After some experimentation, I found that with > Suitcase II installed, Tappy Type won't work. Has anybody else > noticed this? Yes, I pointed this out to the author when TappyType came out, and he has been working on fixing it. The only solution I could come up with was to rename TappyType to .TappyType so it would load before Suitcase II. If this is done, it will work just fine. - Scott ------------------------------ Scott Hankin (hankin@osf.org) Open Software Foundation
lnb@eleazar.dartmouth.edu (L. N. Brosnahan) (01/23/90)
In article <2851@cerberus.oakhill.UUCP> hunter@oakhill.UUCP (Hunter Scales) writes: > > Last nigh I noticed that Tappy Type ( the typewriter sound init) > wasnt working. After some experimentation, I found that with > Suitcase II installed, Tappy Type wont work. Has anybody else > noticed this? > Load Tappy Type before Suitcase II by renaming the INITs to 01Tappy Type and 02Suitcase II. That worked for me. And yes, the developer of Tappy Type does know about the problem. -- | "To-morrow, and to-morrow, and to-morrow, creeps in this petty pace | | from day to day to the last syllable of recorded time; . . . It is a | | tale told by an idiot, full of sound and fury, signifying nothing." | | ---- L.Nicholas.Brosnahan@Mac.Dartmouth.EDU ---- |
lsr@Apple.COM (Larry Rosenstein) (01/23/90)
In article <2851@cerberus.oakhill.UUCP> hunter@oakhill.UUCP (Hunter Scales) writes: > Suitcase II installed, Tappy Type wont work. Has anybody else > noticed this? There's some chance that Suitcase isn't the culprit. I've noticed that there are INITs that call PBHGetVol & PBHSetVol to save and restore the current directory, which is a bad thing to do (according to Tech Note 140). What happens is that INIT "A" call PBHGetVol & PBHSetVol. This sets the current volume to refer to an explicit dirID. Then Suitcase (or some other INIT) calls GetVol and since the system can't return an explicit dirID, it returns just the volume refnum. When Suitcase restores the current volume with a call to SetVol, the current directory is set to the root of the volume. The system code that searches for INIT files then start looking at the root of the volume. Since it won't normally find any INITs there, and INITs that are after Suitcase in alphabetical order won't run. You can see if this is the case by testing whether *ANY* init that follows Suitcase alphabetically is run. (For example rename another INIT to follow Suitcase and see if it is also disabled.) If this is the problem, then you can figure out which INIT is calling PBHSetVol using Macsbug. Larry Rosenstein, Apple Computer, Inc. Object Specialist Internet: lsr@Apple.com UUCP: {nsc, sun}!apple!lsr AppleLink: Rosenstein1