Re: ~$Normal.dot

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Beth Melton (bmelton_at_NoSpam4Memvps.org)
Date: 03/07/04


Date: Sun, 7 Mar 2004 15:58:00 -0600

Hi George,

Before you continue you should know the owner file *should* be deleted
when you exit Word.

Have you tried deleting this file with Word and Outlook, if using Word
as your email editor, closed. If you have deleted it and it does not
disappear when you exit Word then let us know and we'll go from there.
:-)

However I will say there is indeed an issue here and that is whoever
wrote the KB article doesn't know what they are talking about!

~$Normal.dot is not an AutoRecovery Save (or what they are calling the
AutoSave copy). This file is a temporary file called an owner file and
it holds the user data for the individual who opened the file. In the
case of Normal.dot it is opened and loaded when Word starts.

Here's another KB article that covers this temp file:
http://support.microsoft.com/?kbid=211632

An AutoRecovery Save file is named "AutoRecovery save of <FileName>.

Here's another that covers an AutoRecovery save:
http://support.microsoft.com/default.aspx?kbid=156574

-- 
Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.
~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP
Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
"George Hester" <hesterloli@hotmail.com> wrote in message
news:OI0THGIBEHA.1600@tk2msftngp13.phx.gbl...
Hi Jay:
   I really didn't mean to complain about Word although it may sound
like it.  What I meant to "complain" actually point out is the method
in which Microsoft addresses their bugs.  That's what steams me.  The
fact that ~$Normal.dot is not removed when it should be is all that
needs to be addressed.  We don't need to know what other reasons there
are for it sticking around are.  Let's concentrate on the issue at
hand and not throw in extraneous information.  An explanation of why
it sticks around ALWAYS and a workaround would in my opionion be the
correct way of addressing this bug.  If there is no workaround say so.
The workaround they present is no workaround.  The workaround should
be how to stop ~$Normal.dot from always sticking around not how to
clean up Word's mess.
I agree this issue to be fixed at anytime in the future is likely low
on the totem pole.  But as I said I am more concerned with the method
of presenting bugs then I am in the actual bug.
-- 
George Hester
__________________________________
"Jay Freedman" <jay.freedman@verizon.net> wrote in message
news:gtrm40ts7ho944ittkg5vuqket40qtfkb1@4ax.com...
> Hi, George,
>
> First, although the language in the article could be clearer, I
think
> you're not reading what the writer intended. The point of it is that
> autosave files from ordinary documents *are* deleted when Word quits
> normally but may be left behind after a crash -- but ~Normal.dot is
> *not* deleted when Word quits normally.
>
> Second, although it's an "issue" (in Microsoft-speak) or
"undesirable
> behavior," I'd say it falls very low on the bug spectrum. It doesn't
> cause any adverse effect, and it certainly is not a threat of data
> loss. Because of the way MS Program Management evaluates the
> importance of "issues" for urgency, I'd bet that this one never gets
> fixed except as a by-product of fixing something else. For now, the
> existence of the KB article *is* the fix.
>
> If this is the worst bug in Word 2003 you can find to complain
about,
> you haven't been looking. :-) Have you tried using automatic
> numbering? Now *there's* a bugfest...
>
> "George Hester" <hesterloli@hotmail.com> wrote:
>
>
>http://support.microsoft.com/default.aspx?scid=kb;en-us;275955&Produc
t=wrd2003
> >
> >Please why does Microsoft address an issue the cause of which has
no bearing on the particular issue?
> >
> >In this article Microsoft says why ~$Normal.dot can be left behind.
They talk about Word 2003 crqashing or what not.  But that has no
bearing on this issue.  This issue occurs whether Word 2003 closes
correctly or not.
> >
> >The interesting thing here is the product was shipped by Microsoft
knowing full well about the bug and then somehow thinks the Word user
community is not going to recognize it as being what it is by waving
their hands in the air when it is addressed.  I don't know it just
goes to show how darn stupid it can be to "upgrade" software.
>
>
> --
> Regards,
> Jay Freedman
> Microsoft Word MVP        FAQ: http://www.mvps.org/word


Relevant Pages

  • Re: Framework 1.1 Service Pack 1 Question
    ... To Mr. Angry Developer ... If you want a workaround or a patch for a specific defect in the framework, ... resolving or fixing the bug, you should call Microsoft and ask product ... > I am addressing this message to Microsoft directly. ...
    (microsoft.public.dotnet.framework)
  • Re: WMEncoder.Reset Hangs
    ... Eventually opened up a Microsoft ... Microsoft confirmed that the 30-second hang was a bug. ... that we've got a workaround, and 3) I fear that a workaround would ...
    (microsoft.public.windowsmedia.encoder)
  • Re: ~$Normal.dot
    ... > "George Hester" wrote in message ... > in which Microsoft addresses their bugs. ... If there is no workaround say so. ... > of presenting bugs then I am in the actual bug. ...
    (microsoft.public.word.application.errors)
  • Re: ~$Normal.dot
    ... > "George Hester" wrote in message ... > in which Microsoft addresses their bugs. ... If there is no workaround say so. ... > of presenting bugs then I am in the actual bug. ...
    (microsoft.public.word.application.errors)
  • Re: WMP 11 Bug
    ... I answered the question and still suggested they seek a response about their problem because it really didn't sound like a bug. ... If there is another means of reporting bugs that I have left off, please feel free to point it out. ... You couldn't really believe that WMP is less simple than say, Vista, or Windows XP, or Microsoft Office, or Internet Explorer. ... Microsoft's behalf that you're having problems with Windows Media Player. ...
    (microsoft.public.windowsmedia)