Re: Snow Leopard: Couple of questions after upgrade



In article <1j5ecyl.1m2151d1k5mrfN%dempson@xxxxxxxxxxxxx>, David Empson
<dempson@xxxxxxxxxxxxx> wrote:

Otto Pylot <otto@xxxxxxxxxxxxxxxxxxxxx> wrote:

MacBook Core 2 Duo, 2GB memory. I just bought 10.6 yesterday and
updated today. Took about 45 minutes and went well. Only 1 app, iStat
doesn't seem to work but I haven't fiddled too much with it. What i've
noticed is this and I don't know why...

I usually add the version number to my apps so I can tell at a glance
what version it is (Word would be Word 11.5.5, etc). With the "new"
apps that SL installed, it won't let me edit the app name (I can't add
the version number to Safari for example). Getting Info shows some
changes.

If you want to see the version number of applications, you can change
the view options for the Applications folder to show the Version column.


Editing the name of standard Apple applications (or moving them) is a
very bad idea.

Whenever Apple releases a software update, you will have to rename
and/or move them back to the original location before applying the
update, or you will end up with a broken partially installed update
where the application was supposed to be, and your renamed or moved
application will not be updated.

It appears that Apple has started to enforce stricter rules for its
standard applications in Snow Leopard, to protect naïve users from
themselves.

Users with admin rights now cannot modify any of the standard Apple
applications. If you drag an application such as Mail out of
Applications, it copies it instead of moving it.

This is a good thing. It also means that a trojan horse running on an
admin user account (without authentication) cannot modify any standard
applications either. That makes it somewhat safer to be running as an
admin user all the time, which is the default configuration of Mac OS X.

The apps that I can't edit the name on, under Sharing and Permissions
show, system: Read & Write, wheel: Read only, and everyone: Read only.
The info is grayed out and locked

On the apps that I can edit the name on show, my name(Me): Read &
Write, admin: Read & Write, and everyone: Read only. It is not grayed
out and is locked.

What happened

Apple changed the rules with Snow Leopard.

and can I change it?

You could, but...

Repairing Permissions didn't do anything.

If you do change it, then Repair Permissions will put them back the way
they are now.

I'd also like to import my bookmarks from Firefox 3.5.2 to Safari and
play around with the new Safari (which loads really fast) but I can't
find the Firefox bookmarks. Where are they? Firefox, btw, loads really
slow.

[I see others have answered that question]

One last question. On the apps that allow me to under Get Info, should
I check the boxes Open in 32-bit mode and/or Open Using Rosetta. Why or
why not? Thanks.

These options can be used to force an application to run a variant
intended to be used on a different (older) processor.

They will be greyed out if the application doesn't include that variant,
or if it doesn't have any "better" variant which you could disable (e.g.
32-bit will be greyed out if the application doesn't include 64-bit
Intel code, or you aren't running on a 64-bit processor).

"32-bit" refers to the 32-bit Intel variant of the application.

"Rosetta" refers to PowerPC variant of the application.

The only reason you would ever want to use either of these is if the
application supports some kind of plug-in software or library you want
to use, and that plug-in software or library doesn't support Intel (or
64-bit Intel).

For example, a plugin might be "Universal" but only include 32-bit Intel
and PowerPC code (not 64-bit Intel). If the application includes 64-bit
code and is running on a 64-bit processor, it won't be able to use that
plugin. You can allow the use of the plugin by quitting the application,
checking the "Open in 32-bit mode" option for the application, then
launching the application again.

An older plugin might be PowerPC only. In that case you would have to
check "Open using Rosetta" for the application. This will force the
PowerPC version of the application to run, allowing the PowerPC plugin
to be used.


The main disadvantage of checking either option is it will limit the
performance of the application.

32-bit Intel runs a little slower, has at slightly greater risk of
security problems, and it limits the memory which can be accessed by the
application (to somewhat less than 4 GB). For some large memory hungry
applications, this could be a limitation. (This is more likely to be an
issue in future. There aren't very many 64-bit applications yet, apart
from the ones that come with Mac OS X, and none of them should need
gigabytes of memory.)

A possible advantage of checking this option is it will PREVENT an
application from trying to use more than 4 GB of memory, which could be
useful if it has a serious bug which causes it to keep using more and
more memory over time.

Rosetta (PowerPC) runs a lot slower, because the PowerPC code has to be
converted to Intel code. Otherwise it has the same issues as choosing
32-bit Intel.

Thank you for answering my questions. It all makes sense now.

--
Deja Moo: I've seen this bull*** before.

My address has been anti-spammed.
Please reply to: scasse@xxxxxxxxxxx replacing invalid with sonic.
.


Loading