Existing users, log in.  New users, create a free account.  Lost password?

Mac OS X  |  Business / Productivity  |  Office Suites  |  Microsoft Office 2004  |  The update worked but . . .

Microsoft Office 2004

Microsoft Office 2004

Entourage, PowerPoint, Excel, Word suite.

Version:  11.5.6

   [ Views: 798 ]

The update worked but . . .

Feedback Type:  Review

Contributed by: hkim Tuesday, November 07 2006 @ 04:38 AM PST

Product Platform: MacOSX

Used Product For: Less than a month

Recommend Product: NO

I installed the update immediately after installing Office on a Mac Mini with 10.4.8. It works fine but the applications in Office are really *slow* to boot and close, not to mention running.

I only got this because of a client that must deal with Windows documents but I find it to be unable to handle files that are encoded with two-byte characters as well. Getting support or information from Microsoft's website is a pain as well. One is flooded with URLs but little that is really useful.

Office works but I am not impressed.   
Overall Rating:

Ease of Use:

Support:

Features:

Price:

0 of 1 users found this helpful.

Rate this Review

Was this Review helpful? Yes | No

Comments

2 comments |

The update worked but . . . - Ataritox

"It works fine but the applications in Office are really *slow* to boot and close, not to mention running. "

I have not done this update yet, but just so you know my version that is previous to the update opens REALLY SLOW as well. I think it is just the way it is with this app. especially Word.. QuarkXpress opens ten times faster and is ten times more powerful of a program. I am guessing it has something to do with how office handles/goes through your fonts at launch.

Reply to This

Wednesday, November 08 2006 @ 08:10 AM PST


The update worked but . . . - md

Just general advice, but make sure you have between ten and twenty percent of your boot hard drive empty for optimal performance (space for the virtual memory swap file). And, after installing any application, make sure you run "Repair Permissions" in Disk Utility.

Reply to This

Tuesday, December 12 2006 @ 03:46 PM PST