G
Guest
I have been having an intermittent problem with Office
2003 and blaming the printer driver.
-Whenever I open Outlook, I get an error message saying
Office crashed and then it "recovers" a blank Word
document.
-Office programs crash with no discernible pattern.
-Whenever I send an "error report," I get an "automated
crash analysis"(which is about as useful as anything from
Redmond, which is to say, not at all) blaming the driver
for an HP d135 printer.
-First I tried here, and was told to try updating the
printer driver.
-I tried to pull out and reinstall the printer driver.
Although Windows can find it to blame it for the Office
crash (which is manifestly a Microsoft problem..
incompatibility with anyone else's software is a common
MicroSoft "feature"), the driver does not show up in
control panel.
-Fortunately, HP (Unlike MicroSoft) has the occasional
competent programmer and their install program
automatically (and, unlike Windows, successfully) removed
the old driver, so I have, in spite of Windows,
successfully updated the driver.
-This did not solve the problem. It's not the printer
driver.
It's either a typical random-crash-generating
MicroSoft "feature" or a typical incompatibility-with-
anything-not-from-Redmond "feature."
2003 and blaming the printer driver.
-Whenever I open Outlook, I get an error message saying
Office crashed and then it "recovers" a blank Word
document.
-Office programs crash with no discernible pattern.
-Whenever I send an "error report," I get an "automated
crash analysis"(which is about as useful as anything from
Redmond, which is to say, not at all) blaming the driver
for an HP d135 printer.
-First I tried here, and was told to try updating the
printer driver.
-I tried to pull out and reinstall the printer driver.
Although Windows can find it to blame it for the Office
crash (which is manifestly a Microsoft problem..
incompatibility with anyone else's software is a common
MicroSoft "feature"), the driver does not show up in
control panel.
-Fortunately, HP (Unlike MicroSoft) has the occasional
competent programmer and their install program
automatically (and, unlike Windows, successfully) removed
the old driver, so I have, in spite of Windows,
successfully updated the driver.
-This did not solve the problem. It's not the printer
driver.
It's either a typical random-crash-generating
MicroSoft "feature" or a typical incompatibility-with-
anything-not-from-Redmond "feature."