Chinese Language slowdown for non-Admin user

M

menloschool

Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel

Our students here are using 2 GHz MacBooks (2GB RAM) running Leopard 10.5.4 and Office 2008 version 12.1.2.

There are two kinds of accounts on the computer, Admin and a local generic student account.

Logged in as Student (non admin user) the Chinese language input is dramatically slower than when we log out and log back in as the Admin user.

We are forced to switch to TextEdit because the students feel Office 2008 is not useable for Chinese Language input.

Any advise on this matter would be greatly appreciated!

Thanks-
Stefan
 
J

John McGhie

My Suggestions:

1) Start by using Disk Utility to Repair Permissions, then do a power-off
shut-down and restart.

2) Make sure the students have write access to the local disk.

3) Don't try to run this across the network.

4) Make sure the machines have enough memory: the Chinese Language Kit is
huge! :)

Hope this helps


Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel

Our students here are using 2 GHz MacBooks (2GB RAM) running Leopard 10.5.4
and Office 2008 version 12.1.2.

There are two kinds of accounts on the computer, Admin and a local generic
student account.

Logged in as Student (non admin user) the Chinese language input is
dramatically slower than when we log out and log back in as the Admin user.

We are forced to switch to TextEdit because the students feel Office 2008 is
not useable for Chinese Language input.

Any advise on this matter would be greatly appreciated!

Thanks-
Stefan

--

Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Nhulunbuy, NT, Australia. mailto:[email protected]
 
M

menloschool

Thank you for your response!

1. Regarding running Disk Utility Permissions - Apple's Disk Utility can ONLY repair Permissions on files it installs from the installation reference disk. Besides, this on every single MacBook we have here, over 100. Running Repair Permissions is basically only of any service when you are having an issue proven to be OS related-

See "Seriously, ‘Repair Permissions’ Is Voodoo"
<http://daringfireball.net/2006/04/repair_permissions_voodoo>

2. We don't want the students to have Write Access to the disk. Those are Student accounts and we don't want them installing software or changing our configuration.

3. We do not run any of this over the network. This is a local account.
It runs perfectly when logged in as the administrator.

4. The machines all have 2 GB of RAM. Since the operation work perfectly as the admin user (I've looked at Memory usage) this is not the problem.

It might indeed have something to do with the second option, but we can't change them all to administrators. Not an option.

This really needs to be regressed by Microsoft QA.

Thanks for help

Stefan
 
C

CyberTaz

Hi Stephan -

Re #1 - I'm not sure what you mean by "installation reference disk", but
permissions are involved with any installation or update that uses the Apple
Installer as opposed to some other installation method. Office 2008 & its
updates do use the Apple Installer.

The article you cited hardly states that repairing disk permissions is
worthless. The points made ‹ as I understand them ‹ are that it is neither a
preventive maintenance tool nor a "routine" periodic maintenance
requirement. Both are quite valid. However, performance degradation does
seem to qualify as "OS related", does it not?

I'd respectfully suggest that you expand your research to include material
that is somewhat less than 2 1/2 years old ‹ April of 2006 is quite soon
after Tiger appeared & Leopard was still forming in the minds of its
developers. A few more current publications are:

http://support.apple.com/kb/HT2963

http://support.apple.com/kb/HT1452

http://docs.info.apple.com/article.html?path=DiskUtility/10.5/en/duh17.html

I don't know that it *will* correct the current problems you're
experiencing, but it certainly won't hurt... And it's a valid step in the
troubleshooting process. Your reluctance to arbitrarily run it on 100
systems is quite understandable, but don't you think it might be worth
trying on a few of them before dismissing the suggestion?

Regards |:>)
Bob Jones
[MVP] Office:Mac
 
M

menloschool

This is great! I love these "Repair Permissions" blowhards who suggest every problem can be solved by the answer "Well, did you Repair Permission ;) ? Try that!"

Ever notice this is always followed by the response:

"Nope, that didn't do anything"

Guess what? I worked at Apple Computer for 11 years. So I know what I am talking about and since I worked on Mac OS X Updates I am very familiar with the "repair permissions" crowd, the new "zapping the PRAM" for our generation!

Here's something from June, 2008 from MacWorld.
<http://www.macworld.com/article/133684/2008/06/maintenance_intro.html>

Myth #1: “You should repair permissions regularly.”

"But contrary to popular belief, repairing permissions—a procedure which simply resets permissions to a known state—works only on a particular subset of OS X system files. It doesn’t affect user files, nor does it affect third-party files or programs. "

Also, from the Disk Utility Program itself:

"If you have a problem with a file installed by the Mac OS installer, click Repair Permissions"

These KB articles you list are in fact out-of-date and have the same information that was there years ago. There was a discussion at Apple while I was there about removing the functionality because it seemed to mislead customers. It was decided to leave it in because a minority of users might become very upset.

So, yes, I am dismissing the suggestion.

Expect this utility to go away in the future. The Mac OS will probably maintain permission it cares about on its own.

Disk Utility has nothing to do with Microsoft's installation. Nothing.

Anyway, if anyone has a real suggestion that will work on a non-admin account please post it.

Thanks
 
P

Phillip Jones

What you say may be true . You sound like you know about the subject is.
Installing applications, and updates to application 8 times out ten do
screw up permissions especially when they over right or write code to
such places a Apple support folders an other.

The fact is THe Mac OSX hasn't got to nirvana yet, and it's doubtful it
ever will.

OH, PS: I am a die-hard Mac Users since the day of the Mac Se/30 9" B&W
all in one. I believe the system in use was 6.3.x.

Its a good starting point and may actually fix something. If it doesn't
then something else needs to be looked at.
This is great! I love these "Repair Permissions" blowhards who suggest every problem can be solved by the answer "Well, did you Repair Permission ;) ? Try that!"

Ever notice this is always followed by the response:

"Nope, that didn't do anything"

Guess what? I worked at Apple Computer for 11 years. So I know what I am talking about and since I worked on Mac OS X Updates I am very familiarwith the "repair permissions" crowd, the new "zapping the PRAM" for our generation!

Here's something from June, 2008 from MacWorld.
<http://www.macworld.com/article/133684/2008/06/maintenance_intro.html>

Myth #1: “You should repair permissions regularly.”

"But contrary to popular belief, repairing permissions—a procedure which simply resets permissions to a known state—works only on a particular subset of OS X system files. It doesn’t affect user files, nor does it affect third-party files or programs. "

Also, from the Disk Utility Program itself:

"If you have a problem with a file installed by the Mac OS installer, click Repair Permissions"

These KB articles you list are in fact out-of-date and have the same information that was there years ago. There was a discussion at Apple whileI was there about removing the functionality because it seemed to mislead customers. It was decided to leave it in because a minority of users might become very upset.

So, yes, I am dismissing the suggestion.

Expect this utility to go away in the future. The Mac OS will probably maintain permission it cares about on its own.

Disk Utility has nothing to do with Microsoft's installation. Nothing.

Anyway, if anyone has a real suggestion that will work on a non-admin account please post it.

Thanks

--
------------------------------------------------------------------------
Phillip M. Jones, CET |LIFE MEMBER: VPEA ETA-I, NESDA, ISCET, Sterling
616 Liberty Street |Who's Who. PHONE:276-632-5045, FAX:276-632-0868
Martinsville Va 24112 |[email protected], ICQ11269732, AIM pjonescet
------------------------------------------------------------------------

If it's "fixed", don't "break it"!

mailto:p[email protected]

<http://www.kimbanet.com/~pjones/default.htm>
<http://www.kimbanet.com/~pjones/90th_Birthday/index.htm>
<http://www.kimbanet.com/~pjones/Fulcher/default.html>
<http://www.kimbanet.com/~pjones/Harris/default.htm>
<http://www.kimbanet.com/~pjones/Jones/default.htm>

<http://www.vpea.org>
 
J

John McGhie

Well, I am afraid that if Microsoft had the answer, they would have issued
it as an update by now.

Let's see now: There's about 50-odd million copies of Word 2008 out there
by now. And 100 of them have a problem. Right.

Guess what? I worked at Apple Computer for 11 years. So I know what I am
talking about

Excellent! You won't need our help, then. None of us ever worked for Apple
(or Microsoft...)
Anyway, if anyone has a real suggestion that will work on a non-admin account
please post it.

Yes: I already gave it to you, but you won't do it. Let me give it to you
again: "Microsoft Office applications will not run unless they can write to
disk."

So: You have to figure out a way to allow those copies of Word to write
their preferences and templates etc to the local disk.

--

Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Nhulunbuy, NT, Australia. mailto:[email protected]
 
C

CyberTaz

This is great! I love these "Repair Permissions" blowhards who suggest every
problem can be solved by the answer "Well, did you Repair Permission ;) ? Try
that!"

Nobody wrote that it is *the* answer or *the* solution or that it will
*solve* the problem... In fact, the last para of my post stipulates exactly
that.
Ever notice this is always followed by the response:

"Nope, that didn't do anything"

"Always"? Absolutely not, because ‹ as above ‹ it isn't typically mentioned
as anything more than one part of the process.
Guess what? I worked at Apple Computer for 11 years. So I know what I am
talking about and since I worked on Mac OS X Updates I am very familiar with
the "repair permissions" crowd, the new "zapping the PRAM" for our generation!

Then one would also expect that you'd be familiar with the aspects of
Frameworks in OS X and the fact that supporting applications need proper
permissions in order to execute properly.
Here's something from June, 2008 from MacWorld.
<http://www.macworld.com/article/133684/2008/06/maintenance_intro.html>

Myth #1: ³You should repair permissions regularly.²

"But contrary to popular belief, repairing permissions‹a procedure which
simply resets permissions to a known state‹works only on a particular subset
of OS X system files. It doesn¹t affect user files, nor does it affect
third-party files or programs. "

The very next paragraph from that same Macworld article:

"If you ever do have a problem with system-level permissions, your Mac will
likely behave oddly, and you¹ll usually be able to use the Repair Disk
Permissions function then to fix the problem without any data loss or
long-term effects. So I recommend repairing permissions as a troubleshooting
tool rather than a maintenance task. For a comprehensive look at this topic,
see Repairing Permissions: What you need to know."

That's all that was expressed here.
Also, from the Disk Utility Program itself:

"If you have a problem with a file installed by the Mac OS installer, click
Repair Permissions"

Yeah... that pretty much sums up part of that was offered ‹ just worded
differently.
These KB articles you list are in fact out-of-date and have the same
information that was there years ago. There was a discussion at Apple while I
was there about removing the functionality because it seemed to mislead
customers. It was decided to leave it in because a minority of users might
become very upset.

Sorry, but "Last Modified" June 2008 & August 2008, respectively, still
seems a good deal more current than April 2006. I don't dispute that such
discussions took place, but if Apple finds it better to deceive millions in
order to avoid disappointing a few by not publishing factual, valid
information perhaps it is Apple who should bear the brunt of your ire rather
than the fellow users who offer suggestions based on their experience.

Perhaps I'm a bit naïve & misguided, but I generally find it more advisable
to follow the recommendations of those who design the hardware & develop the
software than the advice of every self-proclaimed "expert" who's figured out
how to blog. BTW: I mean no disrespect for Mr. Gruber ‹ as previously stated
there is no dispute whatsoever with his position on repairing permissions as
a matter of routine or preventive maintenance, but that isn't the context in
which the procedure was suggested.
So, yes, I am dismissing the suggestion.

Which is your right ‹ but that right doesn't encompass being dismissive of
or rude to those who reply to your request for assistance.
Expect this utility to go away in the future. The Mac OS will probably
maintain permission it cares about on its own.

Disk Utility has nothing to do with Microsoft's installation. Nothing.

Nor was it stated that it does ‹ Disk Utility has nothing to do with the
installation any program.
Anyway, if anyone has a real suggestion that will work on a non-admin account
please post it.

Thanks

You're most certainly welcome ‹ and any time you feel the need to denigrate
& misquote others along with a bit more sophomoric name-calling please don't
hesitate to drop by.

Good Luck |:>)
Bob Jones
[MVP] Office:Mac
 
P

Phillip Jones

Second attempt, Bad proofreading

Phillip said:
What you say may be true . You sound like you know about the subject.
Installing applications, and updates to application 8 times out ten do
screw up permissions especially when they *overwrite* or write code to
such places the *Apple support folders and other system Folders*.

The fact is *The* Mac OSX hasn't got to nirvana yet, and it's doubtful it
ever will.

OH, PS: I am a die-hard Mac Users since the day of the Mac Se/30 9" B&W
all in one. I believe the system in use was 6.3.x.

Its a good starting point and may actually fix something. If it doesn't
then something else needs to be looked at.

--
------------------------------------------------------------------------
Phillip M. Jones, CET |LIFE MEMBER: VPEA ETA-I, NESDA, ISCET, Sterling
616 Liberty Street |Who's Who. PHONE:276-632-5045, FAX:276-632-0868
Martinsville Va 24112 |[email protected], ICQ11269732, AIM pjonescet
------------------------------------------------------------------------

If it's "fixed", don't "break it"!

mailto:p[email protected]

<http://www.kimbanet.com/~pjones/default.htm>
<http://www.kimbanet.com/~pjones/90th_Birthday/index.htm>
<http://www.kimbanet.com/~pjones/Fulcher/default.html>
<http://www.kimbanet.com/~pjones/Harris/default.htm>
<http://www.kimbanet.com/~pjones/Jones/default.htm>

<http://www.vpea.org>
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top