H
hdn
On a number of systems, the normal.dot seems to freeze after installation of
SP2. All changes get lost when word is closed, change time of normal.dot on
all those systems stays at a time before SP2 was installed. After removing
the old normal.dot, word does not create a new one. A complete re-install of
Office didn't change behaviour. Unfortunately, not all SP2 installed systems
show the bug, so it has at least to be something more than just SP2 that
causes it.
I know, an OS update should`nt affect the internal behaviour of word and i
also can't find any clue in SP2 docs on modifying office in any way, but
given the security motivation of SP2 and the central role of normal.dot in
macrovirus based attacks together with the striking correlation of the time
stamps, i woud like to hear, if there are similar incidents aout there.
We are also currently exploring a finding here on msdn that deals with
Acrobat v7 blocking normal.dot to be updated, although up to now, we use only
older versions of Acrobat.
Please comment or give any idea.
SP2. All changes get lost when word is closed, change time of normal.dot on
all those systems stays at a time before SP2 was installed. After removing
the old normal.dot, word does not create a new one. A complete re-install of
Office didn't change behaviour. Unfortunately, not all SP2 installed systems
show the bug, so it has at least to be something more than just SP2 that
causes it.
I know, an OS update should`nt affect the internal behaviour of word and i
also can't find any clue in SP2 docs on modifying office in any way, but
given the security motivation of SP2 and the central role of normal.dot in
macrovirus based attacks together with the striking correlation of the time
stamps, i woud like to hear, if there are similar incidents aout there.
We are also currently exploring a finding here on msdn that deals with
Acrobat v7 blocking normal.dot to be updated, although up to now, we use only
older versions of Acrobat.
Please comment or give any idea.