Office .X

wardo · 01-22-2002, 08:03 PM

Folks,
I own an iMac and a G4 500 DP. Both have Office .X loaded on them. My initial experience getting everything to run as expected was poor. I could get Entourage and Word to launch correctly but Excel and Powerpoint failed to open. About the time a blank document should be appearing I get "the application has unexpectedly quit". Repairing problems with DiskWarrior and NDD in the OS 9 environment, trashing preferences and uninstalling and reinstalling Office were to no avail. No damaged fonts have been found. Reinstalling OS X and the appropriate updates to bring it to 10.1.2 and then reinstalling Office did the trick. All this happened a month ago.

Now, I've encountered a repeat of this problem on the iMac. Entourage continues to open fine but now Word, Excel and Powerpoint all behave the same. They all unexpectedly quit as the new document window should be opening.

Anyone have any ideas how to rectify this problem without reinstalling everything from scratch?

Wardo

dewme5 · 01-22-2002, 08:25 PM

which build do you have? (wouldn't happen to be a beta would it?? )

wardo · 01-22-2002, 08:31 PM

Build 5P48

mervTormel · 01-22-2002, 08:36 PM

wardo,

i think we're curious what build version of Office v.X you've installed.

is it one of the betas?

wardo · 01-22-2002, 08:51 PM

Sorry . . .

Office .X 10.0.0 (1316) is what the Get Info window for Word indicates.

I'm assuming that 1316 denotes the build number.

If that be the case, then Powerpoint is build 1312, Excel build 1316 and Entourage build 1309 rounds out the list.

Wardo

mervTormel · 01-22-2002, 09:28 PM

wardo,

that's a real head scratcher. does this iMac crash/panic any? a lot? at all?

does this mac have any wonky, third party hardware in it or hanging off it?

do you have the console utility running?

if not...

launch the console app at /applications/utilities/console

edit the preferences and enable crash logs.

also, add console to your system preferences login items

now, see if anything is written to the console when you launch these apps and they crash

also, there will be crash logs written to you ~/library/logs dir

these can sometimes illuminate the problem; send them to Microsoft to see if they can deduce your situation.

or post some excerpt here and let's have a lookyloo.

hope this helps.

-b

wardo · 01-22-2002, 10:01 PM

Hi babaluguts,

I appreciate your efforts to help out. Its a mystery to me too. This little iMac has experienced ZERO kernel panics or any other out of the ordinary behavior. I shy away from alot of third party shareware in light of what I had to do to get Office to work the first time. Admittedly, I've been playing Glider Pro X a lot lately but it hasn't caused any obvious problems. Just suddenly Word quit working and discovered that Excel and Powerpoint behaved exactly the same way.

No external peripherals except for an Epson 777 usb printer.

I'll try what you suggested and see if I uncover anything.

Again, thanks!
Wardo

(at least the G4 still works perfectly!)

wardo · 01-22-2002, 10:10 PM

The Console reports the following errors when launching Word . . .

Date/Time: 2002-01-22 23:04:44 -0500
OS Version: 10.1.2 (Build 5P48)

Command: Microsoft Word
PID: 328

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0:
#0 0x7309d650 in FOReleaseNFNT
#1 0x7350a27c in GenerateFontResult
#2 0x734e5270 in FMSwapFont
#3 0x734ee9a0 in LockFontResult
#4 0x734eb73c in LockGrafPortFontResult
#5 0x734e8a54 in StdTxMeas
#6 0x735377b8 in CallTextWidth
#7 0x734ff130 in StringWidth
#8 0x012648d0 in 0x12648d0
#9 0x01264a30 in 0x1264a30
#10 0x012652c4 in 0x12652c4
#11 0x01227e6c in 0x1227e6c
#12 0x01227d20 in 0x1227d20
#13 0x01227ce8 in 0x1227ce8
#14 0x006628ac in 0x6628ac
#15 0x0065ff10 in 0x65ff10
#16 0x0065fdd0 in 0x65fdd0
#17 0x0065fd58 in 0x65fd58
#18 0x0065fcc8 in 0x65fcc8
#19 0x0065fc98 in 0x65fc98
#20 0x0065fc70 in 0x65fc70
#21 0x0065fc00 in 0x65fc00
#22 0x0065f84c in 0x65f84c
#23 0x0065f348 in 0x65f348
#24 0x0065e93c in 0x65e93c
#25 0x00651fe4 in 0x651fe4
#26 0x00651cdc in 0x651cdc
#27 0x0064fea0 in 0x64fea0
#28 0x01396dcc in 0x1396dcc
#29 0x0064fbe8 in 0x64fbe8

PPC Thread State:
srr0: 0x7309d650 srr1: 0x0000f030 vrsave: 0x00000000
xer: 0x00000017 lr: 0x7309d62c ctr: 0x7309d618 mq: 0x00000000
r0: 0x00000001 r1: 0xbfffdcb0 r2: 0x02a31088 r3: 0x00000054
r4: 0x00000000 r5: 0x02a30a50 r6: 0x00000000 r7: 0x00000000
r8: 0x00010000 r9: 0x830902f0 r10: 0x00010000 r11: 0x834e18a0
r12: 0x7309d618 r13: 0x00000000 r14: 0x00000036 r15: 0x0005a9b0
r16: 0x00000001 r17: 0x80160fa8 r18: 0x000586a8 r19: 0x00001407
r20: 0x00000000 r21: 0x0000001c r22: 0x70004234 r23: 0x700042c8
r24: 0x7016b0dc r25: 0x006bac3c r26: 0x8081ab5c r27: 0xc0d19400
r28: 0x00000000 r29: 0xbfffef00 r30: 0x00000000 r31: 0x00000001

**********

The console reports the following errors when launching Excel . . .

Date/Time: 2002-01-22 23:05:51 -0500
OS Version: 10.1.2 (Build 5P48)

Command: Microsoft Excel
PID: 330

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0:
#0 0x7309d650 in FOReleaseNFNT
#1 0x7350a27c in GenerateFontResult
#2 0x734e5270 in FMSwapFont
#3 0x734ee9a0 in LockFontResult
#4 0x734eb73c in LockGrafPortFontResult
#5 0x734e8a54 in StdTxMeas
#6 0x735377b8 in CallTextWidth
#7 0x734ff130 in StringWidth
#8 0x00fc08d0 in 0xfc08d0
#9 0x00fc0a30 in 0xfc0a30
#10 0x00fc12c4 in 0xfc12c4
#11 0x00f83e6c in 0xf83e6c
#12 0x00f83d20 in 0xf83d20
#13 0x00f83ce8 in 0xf83ce8
#14 0x0052108c in 0x52108c
#15 0x0052038c in 0x52038c
#16 0x0051fd74 in 0x51fd74
#17 0x0051eec8 in 0x51eec8

PPC Thread State:
srr0: 0x7309d650 srr1: 0x0000f030 vrsave: 0x00000000
xer: 0x00000017 lr: 0x7309d62c ctr: 0x7309d618 mq: 0x00000000
r0: 0x00000001 r1: 0xbfffe370 r2: 0x0276b2f8 r3: 0x00000054
r4: 0x00000000 r5: 0x0276acc0 r6: 0x00000000 r7: 0x00000000
r8: 0x00010000 r9: 0x830902f0 r10: 0x00010000 r11: 0x834e18a0
r12: 0x7309d618 r13: 0x00000000 r14: 0x00000036 r15: 0xbfffee58
r16: 0x00063d30 r17: 0x00000001 r18: 0x0005a618 r19: 0x00002403
r20: 0x00000000 r21: 0x0000001c r22: 0x70004234 r23: 0x700042c8
r24: 0x00000004 r25: 0x000006eb r26: 0x8081ab5c r27: 0x00629d90
r28: 0x00000000 r29: 0xbfffef00 r30: 0x8081d1cc r31: 0x00000001

**********

It all looks very similiar to me but it doesn't tip me off to the problem.

Wardo

mervTormel · 01-22-2002, 10:13 PM

sorry, buddy,

you got font problems

#0 0x7309d650 in FOReleaseNFNT # font
#1 0x7350a27c in GenerateFontResult # font
#2 0x734e5270 in FMSwapFont # font
#3 0x734ee9a0 in LockFontResult # font
#4 0x734eb73c in LockGrafPortFontResult # and font

you may have bromidrosis, too, but i can't diagnose that

rwa · 01-22-2002, 10:21 PM

There is a long thread about this on the Macfixit forums.

If Entourage is launching but Word, Excel and PowerPoint fail to, lots have people have found it is a font problem. A MSFT programmer posted a long explanation about X being pickier about fonts than 9.

Lots of people have found that it is a damaged font in the classic fonts folder (in the classic System Folder). You can just drop all your fonts into a fonts (disabled) folder in your classic system folder. Launch Word, and if it works you've confirmed a font problem. Add back until you get all the ones you need or find the one that dies. Just keep launching Word as the test.

Good luck.

wardo · 01-22-2002, 10:43 PM

Hey babaluguts and rwa,

Thanks for pointing me in the right direction! I'll let you know how things turn out.

The classic System Folder has had only stock Apple Truetype fonts in it. Now I'm thinking whether my wife's occassional install of a children's oriented CD could have installed the culprit. (Well, just checked and nothing obvious). I also just removed the Fonts folder from my classic OS 9 folder and relaunched Word but same error.

Will continue looking.

Wardo

wardo · 01-22-2002, 11:44 PM

Hey Folks,

Still stumped! Through Sherlock, I've located six different font folders.

1. Fonts folder within my OS 9 System Folder. Temporarily moved this folder out of the System Folder, relaunched Word, encountered same problem.

2. System/Library/Frameworks/JavaVM.framework/Versions/1.3.1/Home/lib/Fonts. Unable to move this folder for testing purposes because item is owned by root.

3. Home directory/Library/Fonts. Temporarily moved this folder from the Library folder, relaunched Word, encountered same problem.

4. System/Library/Fonts. Unable to move this folder for testing purposes because item is owned by root.

5. Office X/Office/Fonts. Temporarily moved this folder from the Library folder, relaunched Word, encountered same problem.

6. Hard disk/Library/Fonts. Temporarily moved this folder from the Library folder, relaunched Word, encountered same problem.

Any ideas for gaining root access to these font folders that refuse to budge? Does it look like this is where the problem lies?

In the meantime, I'll look at the forum on Macfixit.

Thanks everyone!
Wardo

mervTormel · 01-23-2002, 12:22 AM

well, that approach is pretty brutal.

i would stop for a minute.

you want to make small changes and test them.

always be able to put things back the way they were.

i don't think you want to go mucking around in /system and only in /library if you know some font was put there.

as for yanking these font folders around, i think you may have to at least logout to get the tables reloaded sans the bad font, especially if any app loads them up on login

slow down.

start with os 9 font folder, the likely culprit.

are the crash logs all the same?

glider pro? does that install any wonky fonts?

and moving whole folders may not be good. they might be expected to be there, empty or not. leave the folders, move the contents.

wardo · 01-23-2002, 12:26 AM

babaluguts was right! I had Classic font problems. However, this could not be rectified in OS X.

After rwa pointed me towards the MacFixIt forum concerning this topic (man, a lot of folks having font problems!!), I read far enough to read the input from Will Parker, the Microsoft test engineer responsible for font-related issues in Office .X.

Per his quote . . .
"If you have to make changes in the Classic System Folder fonts, reboot into Mac OS 9, make your changes, and then reboot into Mac OS X. We have recently noted a Mac OS X bug that causes problems when you change the 9.x fonts while in X."

That did the trick. Now it should be relatively easy to figure out which font(s) in Classic are causing the problem.

Wardo

griffman · 01-23-2002, 12:42 AM

... becuase I could have saved you a bit of time with this hint on macosxhints a couple weeks back ;-).

Glad you got it working, though!

-rob.

shower · 01-23-2002, 10:12 AM

My problem seems a little different. Word opens fine, but when I try and open or save a document it crashes. This is what the crash log says....

OS Version: 10.1.2 (Build 5P48)

Command: Microsoft Word
PID: 361

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0:
#0 0x00d9c99c in 0xd9c99c
#1 0x00d9c974 in 0xd9c974
#2 0x0090fb40 in 0x90fb40
#3 0x009109b8 in 0x9109b8
#4 0x00791570 in 0x791570
#5 0x007912b4 in 0x7912b4
#6 0x00790fcc in 0x790fcc
#7 0x00790c34 in 0x790c34
#8 0x0078f8e0 in 0x78f8e0
#9 0x0078f0bc in 0x78f0bc
#10 0x0078eff0 in 0x78eff0
#11 0x0072949c in 0x72949c
#12 0x0078ea04 in 0x78ea04
#13 0x0078e7c0 in 0x78e7c0
#14 0x013d82b8 in 0x13d82b8
#15 0x012530ec in 0x12530ec
#16 0x0125306c in 0x125306c
#17 0x01252ff4 in 0x1252ff4
#18 0x01252ea0 in 0x1252ea0
#19 0x73118504 in DispatchEventToHandlers
#20 0x731017b4 in SendEventToEventTargetInternal
#21 0x731b59e0 in SendEventToEventTarget
#22 0x7310b488 in SendHICommandEvent
#23 0x731a76d0 in SendMenuItemSelectedEvent
#24 0x7318aec0 in FinishMenuSelection(OpaqueMenuHandle *, MenuResult *, MenuResult *, unsigned long)
#25 0x731651a8 in MenuSelectCore(Point, double, unsigned long, OpaqueMenuHandle **, unsigned short *)
#26 0x73187748 in MenuSelect
#27 0x01252ba4 in 0x1252ba4
#28 0x73118504 in DispatchEventToHandlers
#29 0x731017b4 in SendEventToEventTargetInternal
#30 0x731b59e0 in SendEventToEventTarget
#31 0x7310d15c in HandleMouseEvent
#32 0x731ab538 in ToolboxEventDispatcherHandler
#33 0x731185b0 in DispatchEventToHandlers
#34 0x731017b4 in SendEventToEventTargetInternal
#35 0x731b59e0 in SendEventToEventTarget
#36 0x0124432c in 0x124432c
#37 0x00710f40 in 0x710f40
#38 0x006501a0 in 0x6501a0
#39 0x01396dcc in 0x1396dcc
#40 0x0064fbe8 in 0x64fbe8

Thread 1:
#0 0x70030bbc in accept
#1 0x02dfa55c in FWaitForConnection
#2 0x012cec54 in 0x12cec54
#3 0x012f81c8 in 0x12f81c8
#4 0x012f8348 in 0x12f8348
#5 0x702cbcc4 in _MP_CFMTaskProc
#6 0x702831a8 in PrivateMPEntryPoint
#7 0x7002054c in _pthread_body

Thread 2:
#0 0x70044cf8 in semaphore_timedwait_signal_trap
#1 0x70044cd8 in semaphore_timedwait_signal
#2 0x7003f2b8 in _pthread_cond_wait
#3 0x70283ea4 in TSWaitOnConditionTimedRelative
#4 0x702ae8b4 in MPWaitOnSemaphore
#5 0x012f87d8 in 0x12f87d8
#6 0x702cbcc4 in _MP_CFMTaskProc
#7 0x702831a8 in PrivateMPEntryPoint
#8 0x7002054c in _pthread_body

Thread 3:
#0 0x70000978 in mach_msg_overwrite_trap
#1 0x70005a04 in mach_msg
#2 0x70026a2c in _pthread_become_available
#3 0x70026724 in pthread_exit
#4 0x70020550 in _pthread_body

PPC Thread State:
srr0: 0x00d9c99c srr1: 0x0000f030 vrsave: 0x00000000
xer: 0x00000020 lr: 0x00d9c998 ctr: 0x00000000 mq: 0x00000000
r0: 0x00000000 r1: 0xbfffbe40 r2: 0x019ee000 r3: 0x00000000
r4: 0xfffffffc r5: 0x00000004 r6: 0x02d63b43 r7: 0xbfffbf2b
r8: 0x00000000 r9: 0x8023fe34 r10: 0xbfffbdd0 r11: 0x80240bb0
r12: 0x7024fe34 r13: 0x00000000 r14: 0x00000036 r15: 0x0005f6b0
r16: 0x00000001 r17: 0x80160fa8 r18: 0x00060be8 r19: 0x00001007
r20: 0x00000000 r21: 0x0000001c r22: 0x70004234 r23: 0x700042c8
r24: 0x7016b0dc r25: 0x006bac3c r26: 0x8081ab5c r27: 0x00000000
r28: 0x00000000 r29: 0xbfffef00 r30: 0x2a150000 r31: 0x00000001

If anyone can help please let me know. Thanks

mervTormel · 01-23-2002, 03:46 PM

curious. can't really tell where the app is when it gaks, but some menu was accessed recently.

are you mousing to file->open, or file->save as ?

does it crash when the menu is accessed, released, or when the dialog box begins to open?

if so, what happens when when you try command-O or command-S ?

shower · 01-23-2002, 04:27 PM

Word crashes when the mouse clicks/releases on Open/Save doc. Just tried command-O and command-S. Exactly the same. As soon as the programme has to respond to something it quits.

I have'nt come across others with this problem.Its a mystery to me. Do you think there will be some kind of update released soon?

mervTormel · 01-23-2002, 05:03 PM

perhaps, but if M$ don't know about it, it might not get fixed.

check M$ for similar bugs and send them that situation if appropriate.

brodie · 01-23-2002, 05:20 PM

i think i read something about it in a forum i got to through mactopia.com something to do with ttf font suffixes, quit suitcase or ATM if you are running it and make sure only your original system fonts are in their correct location, ie:
osx volume/library/fonts and osx volume/system/library/fonts all other font folders including 9.x move out of their location, even into the trash. you don't have to delete them.
hope this resolves it.

Thread Tools
Show Printable Version Email this Page
Display Modes	Rate This Thread
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode	Rate This Thread:

01-22-2002, 08:03 PM	#1
wardo Prospect Join Date: Jan 2002 Location: Louisville, KY Posts: 10	Office .X Folks, I own an iMac and a G4 500 DP. Both have Office .X loaded on them. My initial experience getting everything to run as expected was poor. I could get Entourage and Word to launch correctly but Excel and Powerpoint failed to open. About the time a blank document should be appearing I get "the application has unexpectedly quit". Repairing problems with DiskWarrior and NDD in the OS 9 environment, trashing preferences and uninstalling and reinstalling Office were to no avail. No damaged fonts have been found. Reinstalling OS X and the appropriate updates to bring it to 10.1.2 and then reinstalling Office did the trick. All this happened a month ago. Now, I've encountered a repeat of this problem on the iMac. Entourage continues to open fine but now Word, Excel and Powerpoint all behave the same. They all unexpectedly quit as the new document window should be opening. Anyone have any ideas how to rectify this problem without reinstalling everything from scratch? Wardo

01-22-2002, 08:25 PM	#2
dewme5 Prospect Join Date: Jan 2002 Posts: 33	which build do you have? (wouldn't happen to be a beta would it?? ) __________________ iMac 24 2.66 dual intel 1TB G4 400 yikes OS X (10.2) 576 MB ram 100 GB (3 HD's)

01-22-2002, 08:31 PM	#3
wardo Prospect Join Date: Jan 2002 Location: Louisville, KY Posts: 10	Build 5P48

01-22-2002, 08:36 PM	#4
mervTormel League Commissioner Join Date: Jan 2002 Posts: 5,536	ms build wardo, i think we're curious what build version of Office v.X you've installed. is it one of the betas? __________________ On a clear disk, you can seek forever.

01-22-2002, 08:51 PM	#5
wardo Prospect Join Date: Jan 2002 Location: Louisville, KY Posts: 10	Sorry . . . Office .X 10.0.0 (1316) is what the Get Info window for Word indicates. I'm assuming that 1316 denotes the build number. If that be the case, then Powerpoint is build 1312, Excel build 1316 and Entourage build 1309 rounds out the list. Wardo

01-22-2002, 09:28 PM	#6
mervTormel League Commissioner Join Date: Jan 2002 Posts: 5,536	hem haw wardo, that's a real head scratcher. does this iMac crash/panic any? a lot? at all? does this mac have any wonky, third party hardware in it or hanging off it? do you have the console utility running? if not... launch the console app at /applications/utilities/console edit the preferences and enable crash logs. also, add console to your system preferences login items now, see if anything is written to the console when you launch these apps and they crash also, there will be crash logs written to you ~/library/logs dir these can sometimes illuminate the problem; send them to Microsoft to see if they can deduce your situation. or post some excerpt here and let's have a lookyloo. hope this helps. -b __________________ On a clear disk, you can seek forever.

01-22-2002, 10:01 PM	#7
wardo Prospect Join Date: Jan 2002 Location: Louisville, KY Posts: 10	Hi babaluguts, I appreciate your efforts to help out. Its a mystery to me too. This little iMac has experienced ZERO kernel panics or any other out of the ordinary behavior. I shy away from alot of third party shareware in light of what I had to do to get Office to work the first time. Admittedly, I've been playing Glider Pro X a lot lately but it hasn't caused any obvious problems. Just suddenly Word quit working and discovered that Excel and Powerpoint behaved exactly the same way. No external peripherals except for an Epson 777 usb printer. I'll try what you suggested and see if I uncover anything. Again, thanks! Wardo (at least the G4 still works perfectly!)

01-22-2002, 10:10 PM	#8
wardo Prospect Join Date: Jan 2002 Location: Louisville, KY Posts: 10	The Console reports the following errors when launching Word . . . Date/Time: 2002-01-22 23:04:44 -0500 OS Version: 10.1.2 (Build 5P48) Command: Microsoft Word PID: 328 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 Thread 0: #0 0x7309d650 in FOReleaseNFNT #1 0x7350a27c in GenerateFontResult #2 0x734e5270 in FMSwapFont #3 0x734ee9a0 in LockFontResult #4 0x734eb73c in LockGrafPortFontResult #5 0x734e8a54 in StdTxMeas #6 0x735377b8 in CallTextWidth #7 0x734ff130 in StringWidth #8 0x012648d0 in 0x12648d0 #9 0x01264a30 in 0x1264a30 #10 0x012652c4 in 0x12652c4 #11 0x01227e6c in 0x1227e6c #12 0x01227d20 in 0x1227d20 #13 0x01227ce8 in 0x1227ce8 #14 0x006628ac in 0x6628ac #15 0x0065ff10 in 0x65ff10 #16 0x0065fdd0 in 0x65fdd0 #17 0x0065fd58 in 0x65fd58 #18 0x0065fcc8 in 0x65fcc8 #19 0x0065fc98 in 0x65fc98 #20 0x0065fc70 in 0x65fc70 #21 0x0065fc00 in 0x65fc00 #22 0x0065f84c in 0x65f84c #23 0x0065f348 in 0x65f348 #24 0x0065e93c in 0x65e93c #25 0x00651fe4 in 0x651fe4 #26 0x00651cdc in 0x651cdc #27 0x0064fea0 in 0x64fea0 #28 0x01396dcc in 0x1396dcc #29 0x0064fbe8 in 0x64fbe8 PPC Thread State: srr0: 0x7309d650 srr1: 0x0000f030 vrsave: 0x00000000 xer: 0x00000017 lr: 0x7309d62c ctr: 0x7309d618 mq: 0x00000000 r0: 0x00000001 r1: 0xbfffdcb0 r2: 0x02a31088 r3: 0x00000054 r4: 0x00000000 r5: 0x02a30a50 r6: 0x00000000 r7: 0x00000000 r8: 0x00010000 r9: 0x830902f0 r10: 0x00010000 r11: 0x834e18a0 r12: 0x7309d618 r13: 0x00000000 r14: 0x00000036 r15: 0x0005a9b0 r16: 0x00000001 r17: 0x80160fa8 r18: 0x000586a8 r19: 0x00001407 r20: 0x00000000 r21: 0x0000001c r22: 0x70004234 r23: 0x700042c8 r24: 0x7016b0dc r25: 0x006bac3c r26: 0x8081ab5c r27: 0xc0d19400 r28: 0x00000000 r29: 0xbfffef00 r30: 0x00000000 r31: 0x00000001 ******** The console reports the following errors when launching Excel . . . Date/Time: 2002-01-22 23:05:51 -0500 OS Version: 10.1.2 (Build 5P48) Command: Microsoft Excel PID: 330 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 Thread 0: #0 0x7309d650 in FOReleaseNFNT #1 0x7350a27c in GenerateFontResult #2 0x734e5270 in FMSwapFont #3 0x734ee9a0 in LockFontResult #4 0x734eb73c in LockGrafPortFontResult #5 0x734e8a54 in StdTxMeas #6 0x735377b8 in CallTextWidth #7 0x734ff130 in StringWidth #8 0x00fc08d0 in 0xfc08d0 #9 0x00fc0a30 in 0xfc0a30 #10 0x00fc12c4 in 0xfc12c4 #11 0x00f83e6c in 0xf83e6c #12 0x00f83d20 in 0xf83d20 #13 0x00f83ce8 in 0xf83ce8 #14 0x0052108c in 0x52108c #15 0x0052038c in 0x52038c #16 0x0051fd74 in 0x51fd74 #17 0x0051eec8 in 0x51eec8 PPC Thread State: srr0: 0x7309d650 srr1: 0x0000f030 vrsave: 0x00000000 xer: 0x00000017 lr: 0x7309d62c ctr: 0x7309d618 mq: 0x00000000 r0: 0x00000001 r1: 0xbfffe370 r2: 0x0276b2f8 r3: 0x00000054 r4: 0x00000000 r5: 0x0276acc0 r6: 0x00000000 r7: 0x00000000 r8: 0x00010000 r9: 0x830902f0 r10: 0x00010000 r11: 0x834e18a0 r12: 0x7309d618 r13: 0x00000000 r14: 0x00000036 r15: 0xbfffee58 r16: 0x00063d30 r17: 0x00000001 r18: 0x0005a618 r19: 0x00002403 r20: 0x00000000 r21: 0x0000001c r22: 0x70004234 r23: 0x700042c8 r24: 0x00000004 r25: 0x000006eb r26: 0x8081ab5c r27: 0x00629d90 r28: 0x00000000 r29: 0xbfffef00 r30: 0x8081d1cc r31: 0x00000001 ******** It all looks very similiar to me but it doesn't tip me off to the problem. Wardo

01-22-2002, 10:13 PM	#9
mervTormel League Commissioner Join Date: Jan 2002 Posts: 5,536	font problems sorry, buddy, you got font problems #0 0x7309d650 in FOReleaseNFNT # font #1 0x7350a27c in GenerateFontResult # font #2 0x734e5270 in FMSwapFont # font #3 0x734ee9a0 in LockFontResult # font #4 0x734eb73c in LockGrafPortFontResult # and font you may have bromidrosis, too, but i can't diagnose that __________________ On a clear disk, you can seek forever.

01-22-2002, 10:21 PM	#10
rwa Prospect Join Date: Jan 2002 Posts: 6	There is a long thread about this on the Macfixit forums. If Entourage is launching but Word, Excel and PowerPoint fail to, lots have people have found it is a font problem. A MSFT programmer posted a long explanation about X being pickier about fonts than 9. Lots of people have found that it is a damaged font in the classic fonts folder (in the classic System Folder). You can just drop all your fonts into a fonts (disabled) folder in your classic system folder. Launch Word, and if it works you've confirmed a font problem. Add back until you get all the ones you need or find the one that dies. Just keep launching Word as the test. Good luck.

01-22-2002, 10:43 PM	#11
wardo Prospect Join Date: Jan 2002 Location: Louisville, KY Posts: 10	Hey babaluguts and rwa, Thanks for pointing me in the right direction! I'll let you know how things turn out. The classic System Folder has had only stock Apple Truetype fonts in it. Now I'm thinking whether my wife's occassional install of a children's oriented CD could have installed the culprit. (Well, just checked and nothing obvious). I also just removed the Fonts folder from my classic OS 9 folder and relaunched Word but same error. Will continue looking. Wardo

01-22-2002, 11:44 PM	#12
wardo Prospect Join Date: Jan 2002 Location: Louisville, KY Posts: 10	Still stumped! Hey Folks, Still stumped! Through Sherlock, I've located six different font folders. 1. Fonts folder within my OS 9 System Folder. Temporarily moved this folder out of the System Folder, relaunched Word, encountered same problem. 2. System/Library/Frameworks/JavaVM.framework/Versions/1.3.1/Home/lib/Fonts. Unable to move this folder for testing purposes because item is owned by root. 3. Home directory/Library/Fonts. Temporarily moved this folder from the Library folder, relaunched Word, encountered same problem. 4. System/Library/Fonts. Unable to move this folder for testing purposes because item is owned by root. 5. Office X/Office/Fonts. Temporarily moved this folder from the Library folder, relaunched Word, encountered same problem. 6. Hard disk/Library/Fonts. Temporarily moved this folder from the Library folder, relaunched Word, encountered same problem. Any ideas for gaining root access to these font folders that refuse to budge? Does it look like this is where the problem lies? In the meantime, I'll look at the forum on Macfixit. Thanks everyone! Wardo

01-23-2002, 12:22 AM	#13
mervTormel League Commissioner Join Date: Jan 2002 Posts: 5,536	aye yi yi well, that approach is pretty brutal. i would stop for a minute. you want to make small changes and test them. always be able to put things back the way they were. i don't think you want to go mucking around in /system and only in /library if you know some font was put there. as for yanking these font folders around, i think you may have to at least logout to get the tables reloaded sans the bad font, especially if any app loads them up on login slow down. start with os 9 font folder, the likely culprit. are the crash logs all the same? glider pro? does that install any wonky fonts? and moving whole folders may not be good. they might be expected to be there, empty or not. leave the folders, move the contents.

01-23-2002, 12:26 AM	#14
wardo Prospect Join Date: Jan 2002 Location: Louisville, KY Posts: 10	Problem Solved! babaluguts was right! I had Classic font problems. However, this could not be rectified in OS X. After rwa pointed me towards the MacFixIt forum concerning this topic (man, a lot of folks having font problems!!), I read far enough to read the input from Will Parker, the Microsoft test engineer responsible for font-related issues in Office .X. Per his quote . . . "If you have to make changes in the Classic System Folder fonts, reboot into Mac OS 9, make your changes, and then reboot into Mac OS X. We have recently noted a Mac OS X bug that causes problems when you change the 9.x fonts while in X." That did the trick. Now it should be relatively easy to figure out which font(s) in Classic are causing the problem. Wardo

01-23-2002, 12:42 AM	#15
griffman MVP Join Date: Dec 2001 Location: Portland, OR Posts: 1,471	Sorry I missed all this ... ... becuase I could have saved you a bit of time with this hint on macosxhints a couple weeks back ;-). Glad you got it working, though! -rob.

01-23-2002, 10:12 AM	#16
shower Prospect Join Date: Jan 2002 Posts: 3	If not a font problem? My problem seems a little different. Word opens fine, but when I try and open or save a document it crashes. This is what the crash log says.... OS Version: 10.1.2 (Build 5P48) Command: Microsoft Word PID: 361 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 Thread 0: #0 0x00d9c99c in 0xd9c99c #1 0x00d9c974 in 0xd9c974 #2 0x0090fb40 in 0x90fb40 #3 0x009109b8 in 0x9109b8 #4 0x00791570 in 0x791570 #5 0x007912b4 in 0x7912b4 #6 0x00790fcc in 0x790fcc #7 0x00790c34 in 0x790c34 #8 0x0078f8e0 in 0x78f8e0 #9 0x0078f0bc in 0x78f0bc #10 0x0078eff0 in 0x78eff0 #11 0x0072949c in 0x72949c #12 0x0078ea04 in 0x78ea04 #13 0x0078e7c0 in 0x78e7c0 #14 0x013d82b8 in 0x13d82b8 #15 0x012530ec in 0x12530ec #16 0x0125306c in 0x125306c #17 0x01252ff4 in 0x1252ff4 #18 0x01252ea0 in 0x1252ea0 #19 0x73118504 in DispatchEventToHandlers #20 0x731017b4 in SendEventToEventTargetInternal #21 0x731b59e0 in SendEventToEventTarget #22 0x7310b488 in SendHICommandEvent #23 0x731a76d0 in SendMenuItemSelectedEvent #24 0x7318aec0 in FinishMenuSelection(OpaqueMenuHandle , MenuResult , MenuResult , unsigned long) #25 0x731651a8 in MenuSelectCore(Point, double, unsigned long, OpaqueMenuHandle , unsigned short ) #26 0x73187748 in MenuSelect #27 0x01252ba4 in 0x1252ba4 #28 0x73118504 in DispatchEventToHandlers #29 0x731017b4 in SendEventToEventTargetInternal #30 0x731b59e0 in SendEventToEventTarget #31 0x7310d15c in HandleMouseEvent #32 0x731ab538 in ToolboxEventDispatcherHandler #33 0x731185b0 in DispatchEventToHandlers #34 0x731017b4 in SendEventToEventTargetInternal #35 0x731b59e0 in SendEventToEventTarget #36 0x0124432c in 0x124432c #37 0x00710f40 in 0x710f40 #38 0x006501a0 in 0x6501a0 #39 0x01396dcc in 0x1396dcc #40 0x0064fbe8 in 0x64fbe8 Thread 1: #0 0x70030bbc in accept #1 0x02dfa55c in FWaitForConnection #2 0x012cec54 in 0x12cec54 #3 0x012f81c8 in 0x12f81c8 #4 0x012f8348 in 0x12f8348 #5 0x702cbcc4 in _MP_CFMTaskProc #6 0x702831a8 in PrivateMPEntryPoint #7 0x7002054c in _pthread_body Thread 2: #0 0x70044cf8 in semaphore_timedwait_signal_trap #1 0x70044cd8 in semaphore_timedwait_signal #2 0x7003f2b8 in _pthread_cond_wait #3 0x70283ea4 in TSWaitOnConditionTimedRelative #4 0x702ae8b4 in MPWaitOnSemaphore #5 0x012f87d8 in 0x12f87d8 #6 0x702cbcc4 in _MP_CFMTaskProc #7 0x702831a8 in PrivateMPEntryPoint #8 0x7002054c in _pthread_body Thread 3: #0 0x70000978 in mach_msg_overwrite_trap #1 0x70005a04 in mach_msg #2 0x70026a2c in _pthread_become_available #3 0x70026724 in pthread_exit #4 0x70020550 in _pthread_body PPC Thread State: srr0: 0x00d9c99c srr1: 0x0000f030 vrsave: 0x00000000 xer: 0x00000020 lr: 0x00d9c998 ctr: 0x00000000 mq: 0x00000000 r0: 0x00000000 r1: 0xbfffbe40 r2: 0x019ee000 r3: 0x00000000 r4: 0xfffffffc r5: 0x00000004 r6: 0x02d63b43 r7: 0xbfffbf2b r8: 0x00000000 r9: 0x8023fe34 r10: 0xbfffbdd0 r11: 0x80240bb0 r12: 0x7024fe34 r13: 0x00000000 r14: 0x00000036 r15: 0x0005f6b0 r16: 0x00000001 r17: 0x80160fa8 r18: 0x00060be8 r19: 0x00001007 r20: 0x00000000 r21: 0x0000001c r22: 0x70004234 r23: 0x700042c8 r24: 0x7016b0dc r25: 0x006bac3c r26: 0x8081ab5c r27: 0x00000000 r28: 0x00000000 r29: 0xbfffef00 r30: 0x2a150000 r31: 0x00000001 If anyone can help please let me know. Thanks

01-23-2002, 03:46 PM	#17
mervTormel League Commissioner Join Date: Jan 2002 Posts: 5,536	curious. can't really tell where the app is when it gaks, but some menu was accessed recently. are you mousing to file->open, or file->save as ? does it crash when the menu is accessed, released, or when the dialog box begins to open? if so, what happens when when you try command-O or command-S ?

01-23-2002, 04:27 PM	#18
shower Prospect Join Date: Jan 2002 Posts: 3	Word crashes when the mouse clicks/releases on Open/Save doc. Just tried command-O and command-S. Exactly the same. As soon as the programme has to respond to something it quits. I have'nt come across others with this problem.Its a mystery to me. Do you think there will be some kind of update released soon?

01-23-2002, 05:03 PM	#19
mervTormel League Commissioner Join Date: Jan 2002 Posts: 5,536	perhaps, but if M$ don't know about it, it might not get fixed. check M$ for similar bugs and send them that situation if appropriate.

01-23-2002, 05:20 PM	#20
brodie Triple-A Player Join Date: Jan 2002 Posts: 143	i think i read something about it in a forum i got to through mactopia.com something to do with ttf font suffixes, quit suitcase or ATM if you are running it and make sure only your original system fonts are in their correct location, ie: osx volume/library/fonts and osx volume/system/library/fonts all other font folders including 9.x move out of their location, even into the trash. you don't have to delete them. hope this resolves it.