Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!apple!mips!prls!pyramid!ctnews!mitisft!jay From: jay@mitisft.Convergent.COM (Jay O'Conor) Newsgroups: comp.sys.mac.programmer Subject: Re: Opening drivers in an INIT ? Message-ID: <1318@mitisft.Convergent.COM> Date: 8 Dec 89 00:01:28 GMT References: <1609@intercon.com> Reply-To: jay@mitisft.UUCP (Jay O'Conor) Organization: Unisys Network Computing Group, San Jose Lines: 27 In article <1609@intercon.com> amanda@mermaid.intercon.com (Amanda Walker) writes: >In article , mm5l+@andrew.cmu.edu (Matthew >Mashyna) writes: >> I want to open the TCP drivers in an init so I can listen for finger >> requests. But I can't open it until after the system is done booting. Is >> there something I can do before I try to open it ? > >Just off the top of my head, I'd start by simply naming your INIT something >like "MacTCP Finger" so that it get loaded after MacTCP does (since INITs >are loaded in alphabetical order). > But why code it as an INIT at all? This could easily be handled as a MultiFinder faceless background task. Now I know that many people will complain about not wanting to run MultiFinder, but what will happen to these people when 7.0 comes out? Yes, it will probably take some time for 7.0 to become the standard system on most Macs out there, but I'd really like to see developers take better advantage of the features of MultiFinder and newer system releases. While I am very strongly in favor of maintaining compatiblity with older machines (down to a Mac Plus), why do people have to code for the lowest common denominator in system software? Apple has been working hard to supply new functionality in system releases, but it is often a long time before this turns into new functionality in applications. Jay O'Conor Unisys/Convergent