Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!think.com!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!sics.se!fuug!funic!nntp.hut.fi!cs.hut.fi!Juha.Hyvonen
From: Juha.Hyvonen@hut.fi (Juha Hyv|nen)
Newsgroups: comp.sys.mac.system
Subject: Re: Bringing Finder frontmost after Startup Items run
Message-ID: <JUHA.HYVONEN.91Jun11121729@sauna.hut.fi>
Date: 11 Jun 91 10:17:29 GMT
References: <0B01FFFB.hlns1b@outpost.UUCP>
Sender: usenet@nntp.hut.fi (Usenet pseudouser id)
Organization: Helsinki University of Technology, Finland
Lines: 22
In-Reply-To: peirce@outpost.UUCP's message of 8 Jun 91 06:17:00 GMT
Nntp-Posting-Host: sauna.hut.fi

In article <0B01FFFB.hlns1b@outpost.UUCP> peirce@outpost.UUCP (Michael
Peirce) writes:
+------------------------
! OK, why not. I have a "cleaned up" version of ~FinderToFront that I
! will be sending out to comp.sys.mac.binaries & sumex (& America
! Online) shortly.
!........................

Has anybody noticed that while the items in Startup Items _run_ in
alphabetical order they do not necessarily _load_ (into memory) in
the same order?

In my case, ~FinderToFront launches (loads) before Darkside but I end
up into Finder (so it runs last). And I end up with a 30K "hole" in
memory (largest available block is 30K smaller than without
~FinderToFront, which requires 30K of memory).

	   / (.__o
	  /_/ __/		..
	! /  !		Juha.Hyvonen@hut.fi	(juh@cs.hut.fi)
	!/ ) !
	 ------