
Corrupt NORMAL.DOT when starting Word97
Hey, I just invented the same error message tonight. For whatever it may
be worth to the knowledgeable readers, here's how -- I have a networked
system with a DOT file (call it OhNo.DOT) in the /Programs/Microsoft Office/
Office/Startup subdirectory. It's a kitchen-sink 1.7-meg wonder with, um,
more wonderful things than I can possibly use while editing large docs.
So I take it out of the directory, pull the network cable out of the wall,
reboot, and have a stable desktop system temporarily.
BUT when I forget to pull the network cable -- I get the same warning
that NORMAL.DOT is corrupt, offering to restore it (I declined since I
have de-selected NORMAL and OhNo.DOT entirely, for this big document).
And I found out that something in there IS restoring the OhNo.DOT
template to the Startup folder automagically. For all I know, the
custom setup we have is confusing the two DOT files, or else taking
out OhNo.DOT makes Word somehow corrupt NORMAL.DOT during a work session.
I don't know anything about Windows or Word, and have to do other work, so
can't just dump all the company software, have to wiggle around it thus.
Anyhow, with de-selecting /Tools/Templates/ Normal.DOT and OhNo.DOT and
pulling the network, my doc's been stable, 1500+ pages using INCLUDE fields
(/Insert/ File/Link...) for each of my 52 chapters. Finally been able to get
the page numbers right, spellcheck the thing into a custom dictionary to
review all the words in it, and begin musing on how to index it.
I've asked the Tech Support manager to lend me a plain vanilla PC with
nothing installed but Microsoft NT, Windows, and WinZip so I can work
without trying so hard to disconnect all his company-specific setup.
I'm expecting a visit of a group with pitchforks and torches tomorrow.
There's your error message, anyhow another way to elicit it.
Quote:
>Greg:
>I have never seen this exact scenario, however this is what I suggest:
...
>You need to check that the user has read/write access to their copy of
>normal.dot, and that no other user has! All sorts of interesting things
>happen if normal.dot is on the network, or is read-only to the user, or is
>accessable by another user, or is replaced by the login script :-)
...
>>When Word 97 starts, the message appears that NORMAL.DOT is corrupt and the
>>user is then asked if she would like to attempt AutoRecovery or not. If No
>>is selected and Word exited and then entered, the error does not appear.
>>The NORMAL.DOT has been deleted and a new one created by Word ...