I have a few clients with Macs running Jaguar. Most of them complain that Office v. X (esp. Word X) crashes 5 or 6 times a day. Do you guys notice this too? Any thoughts?
I've been running Office v.X for several months now (since early this year), and I've only had it crash a total of 5 times or so... By any chance have they updated to the Service Pack 1 yet? I installed it when it came out, and it's running great under Jag. There are quirks, but nothing even close to several crashes per day. Anyway, there's my 2¢...
i have been using office for mac x since the very first day it was launched.
now running it under jag, and still no problems.
there are great newsgroups on the microsoft news server dedicated to office itself as whole, as well as each individual app as well. those newsgroups are regularly monitored by microsoft people, and it is always easy to get an answer to any problem you might have.
i do have a question though: i heard somewhere that the service release 1 removed the checking over the network for another computer having an instance of office running. is this true? can you now run an office app on two machines over the same nettwork without it shutting down?
i have word at home, but never use it....but i just set up a 17" iMac at work with 10.2.1 and office and the doc who uses it says that word unexpectedly quits a couple of times a day....the only program i ever see unexpectedly quit is Chimera....but that is a beta....word should be more stable....perhaps MS with come out with another service pack to bring word up to a more stable state in osX.....g
Office generally, and especially Excel, crashes all the time under Jaguar (10.2.1). I don't know what the problem is, and IE is worse. It used to be that I would get kernel panics, but now just 'the app x has unexpectedly quit'.
I don't use it too often so it doesn't make much difference to me.
I have a lot of crashes in Office and they are pretty much all font related, our corporate font which is fine in OS9, Windows etc... just crashes Office X straight away. I don't think it's a corruption of the font though as every other app I use handles them fine!
Poor coding that's my opinion.
All that rubbish about it being so hard to port office and outlook! If they hadn't made it such a bloat fest in the first place we wouldn't be having these problems would we?
Just waiting for an alternative, donb't care if it's free just as long as it's compatible.
I have been using Office X for about 4 or 5 months now and I don't recall it crashing yet. I have had an error once while it was loading but all i did was restart Office X and it went away.
My flatmate recently bought an iBook on my recommendation. She uses it to write her PhD. I installed Word X on it.
It's crashing regularly. (Not daily, but frequently - she loses work.)
Today, there were some bizarre error messages: 'Cannot save blah.doc because there are too many files open' (there was only one file open, and Word was the only app running); 'Not enough free space on Macintosh HD to save blah.doc' (there was 10MB unused); there was another nonsensical one about user privileges... and another about memory...
Word X is not up to scratch. (My flatmate was using a PC running Windows 98 and Office 97 previously - she had no problems with Word crashing or documents refusing to save.)
If Mac OS X doesn't have a decent, reliable wordprocessor (and it doesn't), then it's dead.
(Who would choose Appleworks on OS X over Word XP?)
Because Office X is so very flakey, there seems no alternative but to use Office on a PC. Is this situation likely to change?
(In my experience, I don't recall Word 97 ever crashing on me.)
If I remember right, I read that Office when it starts up optimizes the fonts before it uses them and, if like me you do alot of graphics and use any other fonts (whether you use a font mgmnt program or not), any of the office apps for Mac OSX crash alot...usually during start up of the program. I have found that if I am going to be using any office program to either start it first before I start up and activate any other fonts (so that it gets to look through a fresh, unaltered set) or quit the font mgmnt software and programs that may be using them i.e. photoshop, quarkxpress,etc. This has seemingly solved the any of the office applications crashing. I have now successfully used all of office for over two weeks doing this, *without* crashing at all. I will be purchasing office for my home computer in the next two weeks and will be able to test this on the tenth and final computer, which is my own. This will be my most hopeful subject yet!
<strong>'Not enough free space on Macintosh HD to save blah.doc' (there was 10MB unused)</strong><hr></blockquote>
I do hope you meant that there was 10 GB unused. If there really were only 10 MB free on the hard drive, I wouldn't be surprised if you are getting errors.
Even on the 700 MB hard drive of my 7100/80, I rarely went under 30 MB of free space. There was one time, though, when I went under a MB... but that's not for this thread.
EDIT: I suppose as a contribution to this thread, I have to say that I get lots of errors in both Word and Excel. I don't use Entourage or PowerPoint. But Word usually crashes every 15 minutes to half hour, and Excel crashed on me repeatedly when I tried to make a graph. I gave up and used Appleworks, which is underpowered, ugly, and also extremely reliable (so far, I haven't had a single problem with it).
I just installed the most recent update - I just got a new computer so I hadn't gotten around to updating Office yet. I haven't used them since the upgrade, but hopefully it'll be more reliable. Word and Excel really are better programs than AppleWorks.
Comments
i have been using office for mac x since the very first day it was launched.
now running it under jag, and still no problems.
there are great newsgroups on the microsoft news server dedicated to office itself as whole, as well as each individual app as well. those newsgroups are regularly monitored by microsoft people, and it is always easy to get an answer to any problem you might have.
i do have a question though: i heard somewhere that the service release 1 removed the checking over the network for another computer having an instance of office running. is this true? can you now run an office app on two machines over the same nettwork without it shutting down?
thnx
And save often.....
Nope, even after installing service release 1 I cannot run Office on both my Powermac and iMac at the same time.
I don't use it too often so it doesn't make much difference to me.
Strange...
Question:
How do I check my fonts for corruption in OS X without font utilities?
-------------------------------------------------
Date/Time: 2002-09-26 14:45:37 -0500
OS Version: 10.2 (Build 6C115)
Host: (i removed it)
Command: Microsoft Word
PID: 950
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x3fff0009
Thread 0 Crashed:
#0 0x90223df4 in GetHandleSize
#1 0x00e064c8 in 0xe064c8
#2 0x00e063b4 in 0xe063b4
#3 0x00e06300 in 0xe06300
#4 0x00e06290 in 0xe06290
#5 0x0035543c in 0x35543c
#6 0x0036f2f0 in 0x36f2f0
#7 0x0036d5ec in 0x36d5ec
#8 0x0036ca20 in 0x36ca20
#9 0x003597f0 in 0x3597f0
#10 0x0034a45c in 0x34a45c
#11 0x003e02c0 in 0x3e02c0
#12 0x002632a0 in 0x2632a0
#13 0x002e665c in 0x2e665c
#14 0x002e6328 in 0x2e6328
#15 0x0044c100 in 0x44c100
#16 0x00458968 in 0x458968
#17 0x00854684 in 0x854684
#18 0x00573120 in 0x573120
#19 0x002e5390 in 0x2e5390
#20 0x002e4ea0 in 0x2e4ea0
#21 0x002d3764 in 0x2d3764
#22 0x00f5652c in 0xf5652c
#23 0x00f57c0c in 0xf57c0c
#24 0x00f8c16c in 0xf8c16c
#25 0x00f8c09c in 0xf8c09c
#26 0x00f8aa8c in 0xf8aa8c
#27 0x00ddfe18 in 0xddfe18
#28 0x00ddfd1c in 0xddfd1c
#29 0x92ba25b4 in DispatchEventToHandlers
#30 0x92ba291c in SendEventToEventTargetInternal
#31 0x92bb4c88 in SendEventToEventTarget
#32 0x00f8b660 in 0xf8b660
#33 0x010abc64 in 0x10abc64
#34 0x010ab4bc in 0x10ab4bc
#35 0x00f8aa58 in 0xf8aa58
#36 0x00ddfe18 in 0xddfe18
#37 0x00ddfd1c in 0xddfd1c
#38 0x92ba25b4 in DispatchEventToHandlers
#39 0x92ba291c in SendEventToEventTargetInternal
#40 0x92bb4c88 in SendEventToEventTarget
#41 0x92c28488 in _Z20HandleTextInputEventP14OpaqueEventRef
#42 0x92bb208c in _Z29ToolboxEventDispatcherHandlerP25OpaqueEventHan dlerCallRefP14OpaqueEventRefPv
#43 0x92ba266c in DispatchEventToHandlers
#44 0x92ba291c in SendEventToEventTargetInternal
#45 0x92bb4c88 in SendEventToEventTarget
#46 0x92c38010 in SendTSMEvent
#47 0x92bfcc74 in SendUnicodeTextAEToUnicodeDoc
#48 0x92c03aa0 in utDeliverTSMEvent
#49 0x92c37f1c in TSMKeyEvent
#50 0x92be0744 in TSMProcessRawKeyEvent
#51 0x92bf9458 in _Z27HandleCompatibilityKeyEventP14OpaqueEventRef
#52 0x92bbaf74 in _Z25CompatibilityEventHandlerP25OpaqueEventHandler CallRefP14OpaqueEventRefPv
#53 0x92ba25b4 in DispatchEventToHandlers
#54 0x92ba291c in SendEventToEventTargetInternal
#55 0x92ba5d28 in SendEventToEventTargetWithOptions
#56 0x92bec1e0 in _Z19HandleKeyboardEventP14OpaqueEventRefm
#57 0x92bb2080 in _Z29ToolboxEventDispatcherHandlerP25OpaqueEventHan dlerCallRefP14OpaqueEventRefPv
#58 0x92ba266c in DispatchEventToHandlers
#59 0x92ba291c in SendEventToEventTargetInternal
#60 0x92bb4c88 in SendEventToEventTarget
#61 0x00e034fc in 0xe034fc
#62 0x002ce110 in 0x2ce110
#63 0x0020d2c0 in 0x20d2c0
#64 0x00f59dac in 0xf59dac
#65 0x0020cd08 in 0x20cd08
Thread 1:
#0 0x90031b0c in accept
#1 0x02c38578 in FWaitForConnection
#2 0x00e907d4 in 0xe907d4
#3 0x00ebaa48 in 0xebaa48
#4 0x00ebabd8 in 0xebabd8
#5 0x902b7e34 in _MP_CFMTaskProc
#6 0x9025e538 in PrivateMPEntryPoint
#7 0x90021428 in _pthread_body
Thread 2:
#0 0x90042d68 in semaphore_timedwait_signal_trap
#1 0x9003ef94 in _pthread_cond_wait
#2 0x902a0a4c in MPWaitOnSemaphore
#3 0x00ebb098 in 0xebb098
#4 0x902b7e34 in _MP_CFMTaskProc
#5 0x9025e538 in PrivateMPEntryPoint
#6 0x90021428 in _pthread_body
Thread 3:
#0 0x9003f188 in semaphore_wait_signal_trap
#1 0x9003efa4 in _pthread_cond_wait
#2 0x90233454 in TSWaitOnSemaphoreCommon
#3 0x9023c298 in TimerThread
#4 0x90021428 in _pthread_body
PPC Thread State:
srr0: 0x90223df4 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x90223ddc ctr: 0x90223dc4 mq: 0x00000000
r0: 0x00000000 r1: 0xbfffbcd0 r2: 0x90224ee4 r3: 0x3fff0009
r4: 0x0000001a r5: 0x00000050 r6: 0x00000050 r7: 0x00000020
r8: 0x00046010 r9: 0xa0220a00 r10: 0x06265010 r11: 0x00000001
r12: 0xa02236d8 r13: 0x034d3c62 r14: 0x0000000c r15: 0x03580d68
r16: 0x02b05810 r17: 0x00000004 r18: 0x00000000 r19: 0x00000000
r20: 0x00000003 r21: 0x00000000 r22: 0x034d3744 r23: 0x034d3744
r24: 0x00000001 r25: 0x018ad148 r26: 0x03b846d8 r27: 0x00000009
r28: 0x000001a2 r29: 0x3fff0009 r30: 0x44022442 r31: 0x90223ddc
**********
Date/Time: 2002-09-27 14:56:01 -0500
OS Version: 10.2 (Build 6C115)
Host: (i removed it)
Command: Microsoft Word
PID: 956
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x3fff0009
Thread 0 Crashed:
#0 0x90223df4 in GetHandleSize
#1 0x00e064c8 in 0xe064c8
#2 0x00e063b4 in 0xe063b4
#3 0x00e06300 in 0xe06300
#4 0x00e06290 in 0xe06290
#5 0x0035543c in 0x35543c
#6 0x003539e8 in 0x3539e8
#7 0x00351dc4 in 0x351dc4
#8 0x0096cfd0 in 0x96cfd0
#9 0x91b56e4c in _Z20aeDispatchAppleEventPK6AEDescPS_mPh
#10 0x91b597f0 in _Z25dispatchEventAndSendReplyPK6AEDescPS_
#11 0x91b56d5c in aeProcessAppleEvent
#12 0x92c82d30 in AEProcessAppleEvent
#13 0x0022d728 in 0x22d728
#14 0x00a60c94 in 0xa60c94
#15 0x00ddfe18 in 0xddfe18
#16 0x00ddfd1c in 0xddfd1c
#17 0x92ba25b4 in DispatchEventToHandlers
#18 0x92ba291c in SendEventToEventTargetInternal
#19 0x92ba5d28 in SendEventToEventTargetWithOptions
#20 0x92bb2134 in _Z29ToolboxEventDispatcherHandlerP25OpaqueEventHan dlerCallRefP14OpaqueEventRefPv
#21 0x92ba266c in DispatchEventToHandlers
#22 0x92ba291c in SendEventToEventTargetInternal
#23 0x92bb4c88 in SendEventToEventTarget
#24 0x00e034fc in 0xe034fc
#25 0x002ce110 in 0x2ce110
#26 0x0020d2c0 in 0x20d2c0
#27 0x00f59dac in 0xf59dac
#28 0x0020cd08 in 0x20cd08
Thread 1:
#0 0x90031b0c in accept
#1 0x02c38578 in FWaitForConnection
#2 0x00e907d4 in 0xe907d4
#3 0x00ebaa48 in 0xebaa48
#4 0x00ebabd8 in 0xebabd8
#5 0x902b7e34 in _MP_CFMTaskProc
#6 0x9025e538 in PrivateMPEntryPoint
#7 0x90021428 in _pthread_body
Thread 2:
#0 0x90042d68 in semaphore_timedwait_signal_trap
#1 0x9003ef94 in _pthread_cond_wait
#2 0x902a0a4c in MPWaitOnSemaphore
#3 0x00ebb098 in 0xebb098
#4 0x902b7e34 in _MP_CFMTaskProc
#5 0x9025e538 in PrivateMPEntryPoint
#6 0x90021428 in _pthread_body
Thread 3:
#0 0x9003f188 in semaphore_wait_signal_trap
#1 0x9003efa4 in _pthread_cond_wait
#2 0x90233454 in TSWaitOnSemaphoreCommon
#3 0x9023c298 in TimerThread
#4 0x90021428 in _pthread_body
Thread 4:
#0 0x9003f188 in semaphore_wait_signal_trap
#1 0x9003efa4 in _pthread_cond_wait
#2 0x90233454 in TSWaitOnSemaphoreCommon
#3 0x90248b2c in _Z15AsyncFileThreadPv
#4 0x90021428 in _pthread_body
PPC Thread State:
srr0: 0x90223df4 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x90223ddc ctr: 0x90223dc4 mq: 0x00000000
r0: 0x00000000 r1: 0xbfffd870 r2: 0x90224ee4 r3: 0x3fff0009
r4: 0x0000001a r5: 0x00000000 r6: 0x00000001 r7: 0x00012f00
r8: 0x00046010 r9: 0xa0220a00 r10: 0x07cab010 r11: 0x00000001
r12: 0xa02236d8 r13: 0x00000000 r14: 0x00000000 r15: 0xbfffe5d8
r16: 0x04000000 r17: 0x00000001 r18: 0x00000001 r19: 0xbfffe008
r20: 0x00000000 r21: 0x00000007 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x018ad148 r26: 0x06acb4ec r27: 0x00000009
r28: 0x000001fc r29: 0x3fff0009 r30: 0x4402244c r31: 0x90223ddc
<strong>njii:
Nope, even after installing service release 1 I cannot run Office on both my Powermac and iMac at the same time.</strong><hr></blockquote>
yep, because they are connected over ethernet, and each version checks on the newtork if there's another machine running with the same sr.
Poor coding that's my opinion.
All that rubbish about it being so hard to port office and outlook! If they hadn't made it such a bloat fest in the first place we wouldn't be having these problems would we?
Just waiting for an alternative, donb't care if it's free just as long as it's compatible.
It's crashing regularly. (Not daily, but frequently - she loses work.)
Today, there were some bizarre error messages: 'Cannot save blah.doc because there are too many files open' (there was only one file open, and Word was the only app running); 'Not enough free space on Macintosh HD to save blah.doc' (there was 10MB unused); there was another nonsensical one about user privileges... and another about memory...
Word X is not up to scratch. (My flatmate was using a PC running Windows 98 and Office 97 previously - she had no problems with Word crashing or documents refusing to save.)
If Mac OS X doesn't have a decent, reliable wordprocessor (and it doesn't), then it's dead.
(Who would choose Appleworks on OS X over Word XP?)
Because Office X is so very flakey, there seems no alternative but to use Office on a PC. Is this situation likely to change?
(In my experience, I don't recall Word 97 ever crashing on me.)
If I remember right, I read that Office when it starts up optimizes the fonts before it uses them and, if like me you do alot of graphics and use any other fonts (whether you use a font mgmnt program or not), any of the office apps for Mac OSX crash alot...usually during start up of the program. I have found that if I am going to be using any office program to either start it first before I start up and activate any other fonts (so that it gets to look through a fresh, unaltered set) or quit the font mgmnt software and programs that may be using them i.e. photoshop, quarkxpress,etc. This has seemingly solved the any of the office applications crashing. I have now successfully used all of office for over two weeks doing this, *without* crashing at all. I will be purchasing office for my home computer in the next two weeks and will be able to test this on the tenth and final computer, which is my own.
<strong>'Not enough free space on Macintosh HD to save blah.doc' (there was 10MB unused)</strong><hr></blockquote>
I do hope you meant that there was 10 GB unused. If there really were only 10 MB free on the hard drive, I wouldn't be surprised if you are getting errors.
Even on the 700 MB hard drive of my 7100/80, I rarely went under 30 MB of free space. There was one time, though, when I went under a MB... but that's not for this thread.
EDIT: I suppose as a contribution to this thread, I have to say that I get lots of errors in both Word and Excel. I don't use Entourage or PowerPoint. But Word usually crashes every 15 minutes to half hour, and Excel crashed on me repeatedly when I tried to make a graph. I gave up and used Appleworks, which is underpowered, ugly, and also extremely reliable (so far, I haven't had a single problem with it).
I just installed the most recent update - I just got a new computer so I hadn't gotten around to updating Office yet. I haven't used them since the upgrade, but hopefully it'll be more reliable. Word and Excel really are better programs than AppleWorks.
[ 10-08-2002: Message edited by: Luca Rescigno ]</p>