Word 2004 crashes when cutting text

T

Tony

Hi,

Word 2004 on Mac OS X 10.3.5 crashes (unexpectedly quits) just when
cutting text on 12 cells of a table. All the times that I try it (100%
consistent).

This is the console.log report:
 
E

Elliott Roper

Tony said:
Hi,

Word 2004 on Mac OS X 10.3.5 crashes (unexpectedly quits) just when
cutting text on 12 cells of a table. All the times that I try it (100%
consistent).
Cannot find executable for CFBundle 0x1472b0
</System/Library/PrivateFrameworks/liberty.framework> (not loaded)

This may not be all that helpful.
I checked that liberty.framework is present on my system. Googling
seems to indicate that it is not a piece of Office, but a system
component related to SSL and security in general.
... which begs the question of what Word is doing there when all you are
doing is laying about a table with your cmd-X axe.

Therefore, I'd conclude that your OS has been meddled with, did not
install properly, has had a hardware nightmare or is otherwise unsound.

To check before re-installing the whole shooting match, a daunting
prospect, I'd recommend a couple of confirmatory tests.

1. Make sure it really is missing.
In terminal utter:-
cd /System/Library/PrivateFrameworks/
then:-
ls -l|grep liberty
you should see
drwxr-xr-x 4 root wheel 136 24 Sep 2003 liberty.framework

If instead you see nothing but your command prompt, it really is
missing.

2. Try the same operation on the same file on a different Mac
If it works there, then either your Mac is unwell (likely) or your Word
is b0rked - i.e- it had no business looking for liberty.framework
under those circumstances.
If that all points to your Mac being ill, back everything up and just
for laughs, copy the framework from another Mac or the install disks
(there is some magic available on versiontracker for dipping into the
installation packages)

No matter whether that fixes it, it would still be a good idea to
re-install and re-update your OS X and applications unless you could
find a clear and unambiguous proof that the missing framework was the
only thing missing.

Caution. I have the developer tools on my Mac. It might be the source
of that framework (I don't think so though) If it were, then Word
wanting to get it would be even stranger.

If you don't have another Mac handy, and your doc is not too sensitive,
or much more than a Megabyte, I don't mind checking it for you here. My
sig is a teco joke as well as directions for constructing an e-mail
address. In english: change nospam to elliott.
 
T

Tony

Elliott,

Thanks.

There is even more: the thing has corrupted so much that when I try to
copy some text (even a few words) from the table ten Word 2004 crashes,
but if it does not and I try to paste it into a blank Word file, I get
the error message:

--
There is insufficient memory. Save the document now.
--

I must say that only Word 2004 was open and that I have 1 GB RAM.

I have suspected for a long time that this was a memory issue related
to Word somehow. It is really, really, really FRUSTRATING!

Maybe it is also related to my system, but absolutely no other
application crashes on my Mac and the system itself is rock solid (not
a single crash).

For me this is due to a peculiar memory handling of Word 2004 (and also
of previous Word v.X versions).

In relation to your suggestions, these are the results:

1.-Terminal
--
Last login: Mon Aug 30 13:20:37 on ttyp1
Welcome to Darwin!
[MyMac:~] me% cd /System/Library/PrivateFrameworks/
[MyMac:/System/Library/PrivateFrameworks] me% ls -l|grep liberty
drwxr-xr-x 4 root wheel 136 24 Sep 2003 liberty.framework
[MyMac:/System/Library/PrivateFrameworks] me%
--

2.-I am sending you the file itself by eMail with instructions on what
I do to get the crash (virtually 100% of the times -- just copying
text).

Thanks again.

---
 
E

Elliott Roper

Tony said:
Elliott,

Thanks.

There is even more: the thing has corrupted so much that when I try to
copy some text (even a few words) from the table ten Word 2004 crashes,
but if it does not and I try to paste it into a blank Word file, I get
the error message:

Google the group for 'insufficient memory'. That is fairly famous. I
have never seen it so I paid no attention.

You might have 'fast saves' enabled in preferences. Turn it off and
leave it off.
I must say that only Word 2004 was open and that I have 1 GB RAM.

I have suspected for a long time that this was a memory issue related
to Word somehow. It is really, really, really FRUSTRATING!

Maybe it is also related to my system, but absolutely no other
application crashes on my Mac and the system itself is rock solid (not
a single crash).

For me this is due to a peculiar memory handling of Word 2004 (and also
of previous Word v.X versions).

In relation to your suggestions, these are the results:

1.-Terminal
--
Last login: Mon Aug 30 13:20:37 on ttyp1
Welcome to Darwin!
[MyMac:~] me% cd /System/Library/PrivateFrameworks/
[MyMac:/System/Library/PrivateFrameworks] me% ls -l|grep liberty
drwxr-xr-x 4 root wheel 136 24 Sep 2003 liberty.framework
[MyMac:/System/Library/PrivateFrameworks] me%

OK So Word went to its death lying to the last. In a way that is a good
result, since only one thing is wrong and not the system too.
--

2.-I am sending you the file itself by eMail with instructions on what
I do to get the crash (virtually 100% of the times -- just copying
text).

OK, not here yet. Be aware I am still on v.X I mistakenly thought you
were too. My test may not be as definitive as you may have liked.
 
E

Elliott Roper

There is even more: the thing has corrupted so much that when I try to
copy some text (even a few words) from the table ten Word 2004 crashes,
but if it does not and I try to paste it into a blank Word file, I get
the error message:
[/QUOTE]
Oops. I missed that in the last post.

If only a single document is misbehaving in this way, it needs stomach
stapling.

To stomach staple a corrupted Word document (Get rid of great mounds of
useless gnarly fat in one painless operation), select all but the very
last paragraph mark, (¶) copy, and then paste into a new document.

It sounds like your document is too fat to get onto the operating table
though ;-)
 
T

Tony

Elliott,

I cannot "Shift Command Home" to copy all but the last carriage return,
because then Word 2004 also unexpectedly quits!

All my Save preferences are disabled except "Save preview picture with
new documents".

Thanks for your help.


Tony said:
Elliott,

Thanks.

There is even more: the thing has corrupted so much that when I try to
copy some text (even a few words) from the table ten Word 2004 crashes,
but if it does not and I try to paste it into a blank Word file, I get
the error message:

Google the group for 'insufficient memory'. That is fairly famous. I
have never seen it so I paid no attention.

You might have 'fast saves' enabled in preferences. Turn it off and
leave it off.
I must say that only Word 2004 was open and that I have 1 GB RAM.

I have suspected for a long time that this was a memory issue related
to Word somehow. It is really, really, really FRUSTRATING!

Maybe it is also related to my system, but absolutely no other
application crashes on my Mac and the system itself is rock solid (not
a single crash).

For me this is due to a peculiar memory handling of Word 2004 (and also
of previous Word v.X versions).

In relation to your suggestions, these are the results:

1.-Terminal
--
Last login: Mon Aug 30 13:20:37 on ttyp1
Welcome to Darwin!
[MyMac:~] me% cd /System/Library/PrivateFrameworks/
[MyMac:/System/Library/PrivateFrameworks] me% ls -l|grep liberty
drwxr-xr-x 4 root wheel 136 24 Sep 2003 liberty.framework
[MyMac:/System/Library/PrivateFrameworks] me%

OK So Word went to its death lying to the last. In a way that is a good
result, since only one thing is wrong and not the system too.
--

2.-I am sending you the file itself by eMail with instructions on what
I do to get the crash (virtually 100% of the times -- just copying
text).

OK, not here yet. Be aware I am still on v.X I mistakenly thought you
were too. My test may not be as definitive as you may have liked.
 
E

Elliott Roper

Tony said:
Elliott,

I cannot "Shift Command Home" to copy all but the last carriage return,
because then Word 2004 also unexpectedly quits!

All my Save preferences are disabled except "Save preview picture with
new documents".

Don't you just love it when months of work go down the plughole?

I mailed your tester back after doing the stomach stapling here.

With a bit of luck.... ;-)
 
T

Tony

Elliott,

Wow, I just cannot believe it. YOU did the trick!

The file (safer restored) that you sent me works fine and no longer crashes.

So you just copy/pasted all contents except the last carriage return
into a new Word file to fix it? Please, let me know so that I can fix
these issues myself in the future. As said I could not do it because
when I tried Word 2004 also unexpectedly crashed.

And in any case this is the kind of issues that I am experiencing with
Word 2004 on a daily basis. Every few minutes Word 2004 unexpectedly
quits. I was working on such Word file without a problem doing such
copy/paste actions into the table at the beginning of the document. And
then, suddenly it started to quit unexpectedly if I tried to copy or
copy/paste text from the table cells.

This is frustrating. I must do "Command S" every few seconds or
minutes; whenever I type or copy/paste something because I am afraid of
the Word 2004 unexpected quits (same with previous Word v.X versions on
Mac OS X). I do not have activated any autosave or auto-recover feature
because I guess it could be worse.

Why? I mean, why Word 2004 gives me all these nightmares when
absolutely no other application (and I use dozens of them!) causes me
any problem at all and never ever crash on my rock-solid Mac OS X
10.3.5 system? I mean also word processor applications with similar or
identical files, including (always the latest versions):

--
AppleWorks
BBEdit
Mariner Write
Mellel
Nisus Writer Express
TextEdit
TextWorks
--

Note: if you are wondering, I use Word because my colleagues use it, th
and and we must exchange documents.

If my system was corrupted, then I guess I would have also problems
with everything else, yet that is not the case.

Any idea most appreciated.

And many many thanks for your great help on this matter.

You saved my day --I just could not work with the damaged file that you
rescued-fixed for me!

Best regards,

---
 
E

Elliott Roper

Tony said:
Elliott,

Wow, I just cannot believe it. YOU did the trick!

The file (safer restored) that you sent me works fine and no longer crashes.

So you just copy/pasted all contents except the last carriage return
into a new Word file to fix it? Please, let me know so that I can fix
these issues myself in the future. As said I could not do it because
when I tried Word 2004 also unexpectedly crashed.

That's it.
And in any case this is the kind of issues that I am experiencing with
Word 2004 on a daily basis. Every few minutes Word 2004 unexpectedly
quits. I was working on such Word file without a problem doing such
copy/paste actions into the table at the beginning of the document. And
then, suddenly it started to quit unexpectedly if I tried to copy or
copy/paste text from the table cells.

This is frustrating. I must do "Command S" every few seconds or
minutes; whenever I type or copy/paste something because I am afraid of
the Word 2004 unexpected quits (same with previous Word v.X versions on
Mac OS X). I do not have activated any autosave or auto-recover feature
because I guess it could be worse.
The *EVIL* one is in preferences -> save -> "allow fast saves" -- and
the more frequently you hit cmd-s, the quicker your file gets
corrupted.

If they are not going to fix it - it has been there and faulty for
years and years - might I suggest they rename it to "encourage frequent
crashes"

On the other hand, I am glad I had "save auto recover info" set, when,
a couple of weeks ago, a failing DVD drive dragged the power supply and
killed the machine. When I rebooted, my Word doc, which contained all
the changes I had made in discsussion over the phone with a colleague
that had lasted about 2 hours was almost all there in the 'recovered'
version. Apple were dead good with the warranty repair. It was exactly
3 days to the hour from the UPS guy bringing the empty box to me
getting my fixed Mac back.
Why? I mean, why Word 2004 gives me all these nightmares when
absolutely no other application (and I use dozens of them!) causes me
any problem at all and never ever crash on my rock-solid Mac OS X
10.3.5 system? I mean also word processor applications with similar or
identical files, including (always the latest versions):

You might now have a lot of similarly corrupted documents.
--
AppleWorks
BBEdit
Mariner Write
Mellel
Nisus Writer Express
TextEdit
TextWorks
--
Wot no LaTeX?
Note: if you are wondering, I use Word because my colleagues use it, th
and and we must exchange documents.

I'm the same, but you gotta admit, Word *is* addictive. I imagine truck
racing would be similar.
If my system was corrupted, then I guess I would have also problems
with everything else, yet that is not the case.

Any idea most appreciated.

And many many thanks for your great help on this matter.

You saved my day --I just could not work with the damaged file that you
rescued-fixed for me!

A pleasure. Others on this excellent group have dug me outta holes more
than once. It is a kinda indirect payment.
 
T

Tony

Elliott,

Thanks.

As said, the only option that I have active in the
?Edit/Preferences/Save? is ?Save preview picture with new documents?.
All the other are not active.

So you say that if I use the keyboard ?Command S? frequently it is
worse? But if I do not do it and get an unexpected quit, then my work
will be lost.

And then the ?Save auto-recover info? in preferences is not the same? I
do not want to have it active because I do not want to save every x
minutes but after I do something important to the document, or after a
while of typing.

I can confirm that I do not have these unexpected quits with any other
application, including the other word processors. Only with Word. So
far I have not tested LaTeX on Mac OS X. Is there a true Aqua version
for it? I could not find it.

I am glad to --finally-- hear about the real culprit:

-
The *EVIL* one is in preferences -> save -> "allow fast saves" -- and
the more frequently you hit cmd-s, the quicker your file gets
corrupted.

If they are not going to fix it - it has been there and faulty for
years and years - might I suggest they rename it to "encourage frequent
crashes"
-

A last request to you and the other administrators (I understand that
you are an administrator-moderator) of these discussion forums: if
possible, please let Microsoft know about this serious bug-flaw of Word
2004 (and previous versions as you well say), so that it is fixed with
the next update. I just cannot work with it any more. It is utterly
frustrating.

Thanks again for all your great support.
Best regards,


---
 
B

Beth Rosengard

Hi Guys,

A couple of comments on what's been going on.

Tony, you don't have to use "Shift Command Home" to copy all but the last
paragraph mark. You can do it manually.

Secondly, there's another (better, according to John McGhie) way to
uncorrupt a document in Word 2004 (but not Word X). It involves saving the
document as a web page. For the exact steps, see here:
<http://word.mvps.org/MacWordNew/DocumentCorruption.htm>.

Next: In this case, it appears that the corruption existed in the whole
document, but it could have resided just in the table. (Tables, especially
nested ones, are particularly prone to corruption.) To uncorrupt just a
table, select it and go to Table> Convert> Convert Table to Text and then
immediately, without changing anything, Convert Text to Table again.

On the topic of memory: It sounds to me, Tony, as if you're running into
the 60 Saves bug. Briefly, what happens is that every time you hit Save,
Word has to make a temporary copy of your document as it exists at that
moment so that if you hit Undo, it has a history of all your actions in the
document. Each time it makes a temporary copy it has to give it a file
handle and Word has a finite number of file handles (approx. 60) it can use.
When it runs out of file handles, it gives you the memory error ­ which is
usually expressed as Disk Full.

The simplest way to avoid getting this error is to close and reopen your
document periodically. This wipes out all those temp files. Another
workaround is detailed here:
<http://word.mvps.org/MacWordNew/DiskFullError.htm>. Now this error is
*supposed* to have been fixed in Word 2004 (as explained in the article).
So either the fix isn't as effective as expected or you're experiencing
something else altogether. (You DO have Allow Fast Saves turned off, don't
you?)

Hope this helps!

--
Beth Rosengard
Mac MVP

Mac Word FAQ: <http://word.mvps.org/MacWordNew/index.htm>
Entourage Help Page: <http://www.entourage.mvps.org>
 
B

Beth Rosengard

Hi Tony,

A few more comments (since I saw this message after posting my last one):

As said, the only option that I have active in the
?Edit/Preferences/Save? is ?Save preview picture with new documents?.
All the other are not active.

So you say that if I use the keyboard ?Command S? frequently it is
worse? But if I do not do it and get an unexpected quit, then my work
will be lost.

No. You *should* hit Save frequently. It's a very good habit even if it
does lead to potential problems as outlined in my previous post. You should
also turn on "Always make backup" which will update every time you hit save.
And then the ?Save auto-recover info? in preferences is not the same? I
do not want to have it active because I do not want to save every x
minutes but after I do something important to the document, or after a
while of typing.

No, it's not the same. Here's what John McGhie has said on this subject:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Regrettably, no Autorecover does not save backups. It saves "Deltas".
Autorecover saves only the changes, not the document itself. This works
well if the document is still available, however...

Word starts. The first place it looks is in its Temp directory. If it
finds anything in there, it knows it did not exit normally the most recent
time it stopped. As part of a normal exit, Word cleans out its Temp
directory, so if there's anything in there it knows it crashed last time.

If Word does find abandoned autorecover files, it then attempts to open the
document these are associated with. If that document can be opened, Word
applies the changes from the autorecover files to the document and you get
your document and all its changes back, in the same state it was when you
left it (possibly excepting the last ten minutes).

However, if the reason we crashed was that Word was unable to continue due
to document corruption, Word may not be able to open the document. It then
has nothing to apply the changes to, and you lose the lot.

If you have been performing manual saves with Command + S every time you
pause to think (and if you have been using Word longer than a week or two,
you will be :)) then the Autorecover file may well be older than the
document. When it restarts, Word will offer to reclaim your document: if
you say YES, you could be taking the document back ten minutes, abandoning
changes you have already saved to the document. There will be no sign that
this has happened. You may be severely embarrassed because you added new
content in the ten minutes since the last autorecover. You saved the
changes, and a few seconds later, Word crashed. You recover, and continue
without checking the document. A month later you discover that the new
material you thought you had added is magically "not there" and the customer
is on your case. Your new material was in the file but not the autorecover,
when you recovered, Word stepped the document back a version and lost your
changes. This is the biggest hazard with Autorecover. If you are saving on
Command + S as often as you should be, your Autorecover files are almost
always older than your document.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A last request to you and the other administrators (I understand that
you are an administrator-moderator) of these discussion forums: if
possible, please let Microsoft know about this serious bug-flaw of Word
2004 (and previous versions as you well say), so that it is fixed with
the next update. I just cannot work with it any more. It is utterly
frustrating.

Neither Elliott nor any of the MVPs is an administrator or moderator of
these newsgroups (there is no such thing). We're all just users like you
but some of us have more experience than others. Periodically, MS awards
some of us as MVPs, basically as a thank you for the volunteer work we do
here. You can read more about the MVP program here:
<http://www.word.mvps.org/AboutMVPs/index.htm>

--
Beth Rosengard
Mac MVP

Mac Word FAQ: <http://word.mvps.org/MacWordNew/index.htm>
Entourage Help Page: <http://www.entourage.mvps.org>
 
T

Tony

Beth,

Thanks.

Update (also to Elliott): I have tested the copy/pasted in the
"original" document but in other system: PowerMac G4/400 with 1 GB RAM
and Word 10.1.4 (Office 10.1.5) on Mac OS X 10.3.5 (Panther). I got
exactly the same as you told me: works fine, but when I save the
document and then close it, Word unexpectedly quits. Right as you said.

Note that both Macs are booted not from the internal drive but from an
external FireWire disk (different for each Mac). In case that may be
relevant.

-

On the other hand, answering to Beth...

I know about selecting manually, but I got the same "nice" crash when I
"Command C" to copy or "Command V" to cut after selecting. The crash is
not fired by the selection but for the copy, cut or paste afterwards.
Besides, it is easier "Shift Command Home" on a 29-page long document.

The table was a plain one-column with about 250 rows. But I rarely use
tables. 99% of my crashes are on documents without tables. Bookmarks
from text copy/pasted from web or eMail pages were also a crash culprit
and I deleted them all using the "Insert/Bookmark" option. But even
with all that fixed crashes continue. You can never be sure with Word.
It crashes at any time (and no other application does it my rock-solid
Mac OS X 10.3.5).

I never had a "disk full" error. On the other hand I rarely use "undo".
Maybe I did it three times in total on that session. Certainly not 60
or near it.

I have "Allow Fast Saves" turned off and, as previously indicated, all
options in the Save preferences are off except "Save preview picture
with new documents". Should I turn them on? I have them off because I
think that is best to avoid problems with Word --I am becoming paranoid
after all this nightmare-- and because I do not want to save every x
minutes but when I want (Command S), which usually is after doing
something on the document that if lost would take me time to recover.

But then, again, this is ludicrous. I have no crash or problem with any
of the dozens of applications (including other words processors) that I
use on Mac OS X 10.3.5. Why with Word? There is something wrong with
Word for sure.

My final suggestion to Microsoft would be to fix this serious problem.
I am experiencing these unexpected quits every day. Perhaps it is
because due to this I "Control S" every few minutes as well. I never
save with any other application except at the end of my work. If I do
with Word it is because it unexpectedly quits in the middle of my work.
And now it seems that frequent savings manually (Command S) can also
corrupt the file, as said by Elliott. This is frustrating. What should
I do then: save or not save manually frequently (Command S). Should I
activate any auto-save or auto-recover option in preferences). I am
lost until Microsoft fixes this.

And I want to thank you all for your kind support. I only with that
Microsoft would listen.

---
 
T

Tony

Beth,

Thanks for the feedback.

I have activated "Always create backup copy" in the "Preferences/Save".
The other options in the "Save" preferences are not activated (except
the "Save Preview Picture with new Documents", which is also activated).

Only one question: if Word crashes (sadly it will do!) where can I look
to find such ?backup copy?? Or perhaps Word would open it for me
automatically next time that I open such file?

Good to know the difference between Auto-recover and "Command S". I am
glad that I am doing the right thing (Command S and not auto-recover).

Well I must say that not being administrators you know so much about
Word. I want you to thank you twice for offering such great help being
also Word users as I am...

Best regards,

---
 
J

Jeffrey Weston [MSFT]

Hey Tony, these frequent quits or Crashes that you get, would it be possible
for you to send me directly the text file of your Crash Log?

It be helpful for us if I could get your crash log and also get a
description of what you were doing at the time Word crashed.

Maybe this way, us on the technical side you on the customer side can figure
this out together.

You can send the log to my email address: (e-mail address removed)
(without the "online")

Jeffrey Weston
Mac Word Test
Macintosh Business Unit
Microsoft
 
B

Beth Rosengard

Hi Tony,

I'm going to give you a couple of recommendations at the bottom of this, but
see inline responses first.

The table was a plain one-column with about 250 rows. But I rarely use
tables. 99% of my crashes are on documents without tables. Bookmarks
from text copy/pasted from web or eMail pages were also a crash culprit
and I deleted them all using the "Insert/Bookmark" option. But even
with all that fixed crashes continue. You can never be sure with Word.
It crashes at any time (and no other application does it my rock-solid
Mac OS X 10.3.5).

Word crashing for no apparent reason is not typical. Something is wrong; we
just have to find it.
I never had a "disk full" error. On the other hand I rarely use "undo".
Maybe I did it three times in total on that session. Certainly not 60
or near it.

You misunderstood. It doesn't matter how many times you use Undo (if ever);
what matters is how many times you hit Save. Every time you save, Word has
to create a temporary document *in case* you hit Undo, so it knows what to
undo. Eventually it runs out of file handles for all these temp docs.

But if you've never gotten the "disk full" error message, this is probably
irrelevant anyway. Do you remember the more-or-less exact wording of the
memory error you say you're getting?
I have "Allow Fast Saves" turned off and, as previously indicated, all
options in the Save preferences are off except "Save preview picture
with new documents". Should I turn them on? I have them off because I
think that is best to avoid problems with Word --I am becoming paranoid
after all this nightmare-- and because I do not want to save every x
minutes but when I want (Command S), which usually is after doing
something on the document that if lost would take me time to recover.

Do you actually use the preview pictures? I seem to remember hearing that
they use a lot of space so if you don't, turn this option off. Otherwise,
you should turn on "Always make backup" as a safety measure and forget all
the other options.
But then, again, this is ludicrous. I have no crash or problem with any
of the dozens of applications (including other words processors) that I
use on Mac OS X 10.3.5. Why with Word? There is something wrong with
Word for sure.

There is certainly something wrong with the way Word is interacting with
your system; that doesn't *necessarily* mean there is anything wrong with
Word itself. Word is more complex and more demanding than probably 95% of
the Mac applications available. That means there are more opportunities for
conflicts. It also means there are more things that can go wrong during
installation.

Word also contains a good bit of legacy code. That's the stuff that was
there in the beginning (like Allow Fast Saves). From what I understand,
much of this legacy code is so deeply embedded and intertwined with later
code that removing it is likely to cause many more issues than leaving it
alone.
And now it seems that frequent savings manually (Command S) can also
corrupt the file, as said by Elliott. This is frustrating. What should
I do then: save or not save manually frequently (Command S). Should I
activate any auto-save or auto-recover option in preferences). I am
lost until Microsoft fixes this.

You *should* save frequently. Also, closing and reopening your document
every once in a while doesn't hurt. And, if you see signs of possible
corruption, don't wait till it gets worse! Uncorrupt the document right
away. It's easy enough to do following either of the methods in that
article I pointed you to.

Only one question: if Word crashes (sadly it will do!) where can I look
to find such ?backup copy?? Or perhaps Word would open it for me
automatically next time that I open such file?

You'll see the backup copy as a semi-grayed-out icon in the same folder that
you saved the original doc to. I don't know, but I suspect that Word will
not open the backup automatically. I would think you'd have to do it
manually (which can be done regardless of the fact that it looks grayed
out).
Well I must say that not being administrators you know so much about
Word. I want you to thank you twice for offering such great help being
also Word users as I am...

You're very welcome. Note that Jeffrey Weston, who *is* a Microsoft
employee has requested that you send crash logs to him directly. Please do
so!

However, try this regardless: Quit Word and then relaunch it while you hold
down the Shift key. This is known as opening in Safe Mode, since just about
everything will be disabled (macros, custom dictionaries, add-ins, prefs and
more). Now open a document that reliably crashes on you (like maybe the
original of the one that Elliott fixed for you?). Perform the actions that
made Word crash *consistently* before. If you have no problems, that means
that Word is fine but something else (one of the disabled components) is
*not* fine. If the document continues to crash, then something is wrong
with Word or your installation of it.

In that case, my recommendation would be to do a complete step-by-step
removal and reinstallation of all of Office, following the procedures
outlined here: <http://word.mvps.org/MacWordNew/RemoveReinstall.htm>. And
don't take any shortcuts! Do it right.

Good luck.

Beth
 
T

Tony

Jeffrey,

Thanks for your kind support.

I will send it to you. Just one thing: I understand that you mean the
following file (please, confirm or otherwise let me know the file or
files that you mean):

/Users/me/Library/Logs/Microsoft Word.crash.log

Thanks again,

---
 
J

Jeffrey Weston [MSFT]

Yes, that's it. Or when the Dialog asks if you want to send the information
to Microsoft, you can click "More Information" and copy and paste that to
file and send it to me.

Please also include a description of what you were doing, and we can start
from there. (I might come back and ask you more specific information so the
more you can remember about the "state" of Word when it crashed the better.)

Thanks

-- Jeffrey
 
T

Tony

Jeffrey,

This is amazing. While waiting for your answer I did a search for
"crash" and "word" (visible and invisible) on my hard disk. These are
the files that I have found:

--File 1: size of 1.1 MB last modified on August 14th 2002
/Users/me/Library/Logs/Microsoft Word.crash.log

--File 2: size of 1.1 MB last modified on May 16th 2004
/Users/me/Library/Logs/CrashReporter/Microsoft Word.crash.log

I cannot find the crash log file for Word 2004 or for the crashes I had
after May 16th 2004.

Note that on May 16th 2004 I updated from Word 10.1.4 (Office 10.1.5)
to Word 2004 (Office 2004).

I understand that maybe such word crash log file has now other name.
But which? How to find it?

Thanks.

---
 

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