M
Martin
Word 2002 on XP.
Invariably after about 10 lines or so of typing the error-report box pops up
and Word sets about recovering the document. It doesn't happen if the
user is typing an e-mail.
I ran through all the stuff in
http://word.mvps.org/FAQs/AppErrors/ProbsOpeningWord.htm
except the stuff on the Startup path which I find confusing and inaccurate
regarding the registry entry
HKCU\Software\Microsoft\Office\10.0\Word\Options\"Startup-path".
There's no such "startup-path" entry in the registry - and none in my copy
of Word 2000 either.
Word similarly "crashes" using Run winword.exe /a and also in Windows "Safe
Mode" but into the second page of typing i.e. it seems to get further before
the error-report box pops up.
By elimination, I found that the problem does NOT occur provided I disable
the HAL speech synthesis (for visually impaired users).
I contacted Dolphin, the manufacturers of HAL. They've made a couple of
suggestions eg checking for updated map files, running RAM tests and
checking the hard drive. However, if anyone has any additional
suggestions, I'd be most grateful to hear them,
Thanks
Martin
Invariably after about 10 lines or so of typing the error-report box pops up
and Word sets about recovering the document. It doesn't happen if the
user is typing an e-mail.
I ran through all the stuff in
http://word.mvps.org/FAQs/AppErrors/ProbsOpeningWord.htm
except the stuff on the Startup path which I find confusing and inaccurate
regarding the registry entry
HKCU\Software\Microsoft\Office\10.0\Word\Options\"Startup-path".
There's no such "startup-path" entry in the registry - and none in my copy
of Word 2000 either.
Word similarly "crashes" using Run winword.exe /a and also in Windows "Safe
Mode" but into the second page of typing i.e. it seems to get further before
the error-report box pops up.
By elimination, I found that the problem does NOT occur provided I disable
the HAL speech synthesis (for visually impaired users).
I contacted Dolphin, the manufacturers of HAL. They've made a couple of
suggestions eg checking for updated map files, running RAM tests and
checking the hard drive. However, if anyone has any additional
suggestions, I'd be most grateful to hear them,
Thanks
Martin