Re: Forcing script to recognize application on startup disk.
Re: Forcing script to recognize application on startup disk.
- Subject: Re: Forcing script to recognize application on startup disk.
- From: Richard 23 <email@hidden>
- Date: Fri, 3 Nov 2000 01:41:28 -0800
>
Is there a way I missed to force my scripts to open the copies of
>
applications on my new startup disk, short of deleting copies on other
>
disks, as I was forced to do?
Your computer probably sees no pressing need to change the application
it launches for a given creator code because the applications on your
new disk are the same (and have the same modification date) as those
on the old disk. It would probably re-evaluate this supposition if you
were to prevent the old disk from mounting at startup. I'm not sure
whether a rebuild of the desktop would also be necessary. Once it
determines where the "new" applications are you should be able to
start up as usual.
A useful method to avoid the "Where is...?" dialog is to place an alias
in your Script Editor's folder for each of your applications (useing the
same names).
R23