Xref: utzoo comp.sys.mac.system:4959 comp.sys.mac.misc:11758 Newsgroups: comp.sys.mac.system,comp.sys.mac.misc Path: utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!geac!alias!rae From: rae@alias.com (Reid Ellis) Subject: Re: ** Watchout for the Abaton Interfax ** Message-ID: <1991May4.210847.19797@alias.com> Sender: news@alias.com (USENET News) Organization: Alias Research, Inc. Toronto ON Canada References: <1991May01.163100.8093@mthvax.cs.miami.edu> <1991May1.214012.365@eng.umd.edu> <1991May01.231623.13064@mthvax.cs.miami.edu> <1991May2.011240.20370@swbatl.sbc.com> <1991May02.041101.15995@mthvax.cs.miami.edu> Date: Sat, 4 May 91 21:08:47 GMT I just wanted to mention the major reason that CE Software's QuickMail is not compatible with System 7 -- it's not 32-bit clean. Note that this is also a problem under A/UX, so it's not really a matter of a company supporting a non-released version of system software; it's more a matter of a company NOT FIXING A BUG in their software. What do you have to do to make yourself 32-bit dirty? [that's not a rhetorical question, I'm trying to remember..] Lessee, one way is to set bits in the highest byte of a handle to mark a handle as locked or whatever instead of using Toolbox calls to do it [LockHandle() etc]. Another has to do with NuBus boards that have to call SwapMMUMode() or something and are passing addresses to functions around [which can have a "dirty" byte in it] -- these guys have to call StripAddress() on the addresses i think. Anyways, I was NOT asking CE Software to be compatible with System 7 per se -- rather, I want them to FIX THEIR BUGS. And, basically, they said "we're not fixing our bugs until System 7 is released." I mean, really, what does the release date of a version of system software have to do with fixing bugs in your own software? 32-bit cleanliness has been around a LOT longer than rumours about/copies of System 7.0{d,a,b,fc}[0-9]+. Reid -- Reid Ellis rae@utcs.toronto.edu || rae@alias.com CDA0610@applelink.apple.com || +1 416 362 9181 [work]