
Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
UNSOLVED
R
rfeuerherm
67 Posts
0
1673
March 28th, 2001 16:00
"Illegal operation"
Attn: KayH:
Kay, I followed your instructions in removing the illegal operation warnings when sending documents from Microsoft Works to my HP Deskjet 895Cse printer. I unistalled, than reinstalled my DJ printer software.
I went into Microsoft Works and opened a document and printed it out.....no problem.....no warnings.
Then I went into another document and as I was reading it an "illegal operation" warning appeared.
The details: Winword caused an invalid page fault in module user32.dll@0167:bff558c6.
What now "Oh Great One".
Thanks much
Richard
Kay, I followed your instructions in removing the illegal operation warnings when sending documents from Microsoft Works to my HP Deskjet 895Cse printer. I unistalled, than reinstalled my DJ printer software.
I went into Microsoft Works and opened a document and printed it out.....no problem.....no warnings.
Then I went into another document and as I was reading it an "illegal operation" warning appeared.
The details: Winword caused an invalid page fault in module user32.dll@0167:bff558c6.
What now "Oh Great One".
Thanks much
Richard
Responses (6)
Solutions (0)
Hi Richard,
This post offers Dell's preferred solution to this error. The moderator notes that simply uninstalling Word and reinstalling it won't help the problem, so if the workarounds in the Microsoft article aren't helping, you may want to pursue his posted solution.
I couldn't find anything but this post and the Microsoft article in an internet search. The article and the post presume that the error is appearing on closing a Word document, but in your case, it is appearing while a document is open. If you would like, you might want to post this error in the Works Suite conference, located here. Perhaps someone there knows of a solution if the error message appears when a document is not being closed.
HTH,
Kayrfeuerherm
67 Posts
302
0
Posted March 29th, 2001 01:00
KayH:
Thank you very much for finding this info on Winword prblm. I printed up the "article" (3 pages) and will work on it tomorrow. I was thinking that maybe I would just uninstall the current MicroWorks program I am using, than reinstall it. Maybe this will clear up the problem similar to the printer problem that I was having. So far the printer is working fine.
I'll let you know what happens.
Thanks so much again, really appreciate all your good advise. You have restored my confidence in Dell support.
Richard
Hi Richard,
No problem at all; if I'm able to help at all, I'm happy to do it :)
You can try uinstalling the program and see if that will do it. The Dell Tech in the Works Suite conference indicated that further jobs had to be done, in the event that the error is occurring when you attempt to close a document window. Since your error occurs at other times, possibly just uninstalling and reinstalling the program will be enough, but be prepared to go on with the other fixes he named.
Hopefully this will go as well as the printer problem did; that would be really nice :)
Good luck with it,
Kayrfeuerherm
67 Posts
302
0
Posted March 29th, 2001 15:00
KayH:
"WONDERFUL". I followed your instructions and clicked on the article then printed up the instructions (3 pgs). I selected the 1st resolution "Disable Off.Asst. & Recreate the Word 2000 Document". After recreating the document, I printed same. The document printed both pages, without getting "illegal operations" warning.
Thank you again, you have been very helpful.
Richard
Hi Richard,
I'm so glad this is working again for you! That's great news :)
I'm hopeful that all of the products--the printer drivers, Word, and Windows are now on the same page with what they are supposed to be doing, so they can work together for you again.
Thanks a lot for letting me know :)
Have a good one,
Kay

KayH
1116 Posts
302
0
Posted March 28th, 2001 20:00
Hi Richard,
I'm glad the printer is back, anyway; that's a good thing :)
In terms of this error, there isn't much available on it. The Microsoft Knowledge Base has this article on it, but I don't know if this applies to you.
I'll continue looking for other possibilities and post back if I find something usable.
Talk to you later,
Kay