Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!sgi!silvlis.com!jimb From: jimb@silvlis.com (Jim Budler) Newsgroups: comp.sys.mac.system Subject: Re: Interrupt on IIsi? Message-ID: <1990Nov11.065314.10056@silvlis.com> Date: 11 Nov 90 06:53:14 GMT References: <1990Nov10.090339.3404@silvlis.com> Sender: usenet@silvlis.com (USENET news maint) Reply-To: jimb@silvlis.com (Jim Budler) Organization: Silvar-Lisco,Inc. Sunnyvale Ca. Lines: 33 In article <1990Nov10.090339.3404@silvlis.com> I write: > >Why couldn't readers of this newsgroup from Apple answer the question? >Are they ALL off somewhere else right now? Maybe, they've been silent >lately. > Tom Dowdy at Apple has correctly written to me pointing out that Apple employees participating on Usenet are doing so of their own volition, on their own time, and that most aren't in a position to have known the answer to my question. I apologize to these Apple employees for misdirecting my anger at Apple for failing to provide the information making a specified function of my MacIIsi work. For those who missed the thread, the interrupt on the MacIIsi only works when you have an unreleased version of Macsbug, 6.2b1 or newer. For those unfamiliar with Apple versioning, 6.2a? and 6.2d? are not newer, and they don't enable the command-poweron for the MacIIsi. The released Macsbug 6.1 also does not. Scott Winder *did* provide the necessary information. My apologies to the individual Apple employees. jim -- __ __ / o / Jim Budler jimb@silvlis.com | Proud / / /\/\ /__ Silvar-Lisco, Inc. +1.408.991.6115 | MacIIsi /__/ / / / /__/ 703 E. Evelyn Ave. Sunnyvale, Ca. 94086 | owner