Can't print emails...brand new problem

[George]

7-18-04

A few days ago (after operating great for 6-months) my
system just stopped printing my email messages. Also, it
won't print saved messages that I've sent to my Documents
file. (If it has an SBC logo in front of it, it I get
the "error message" listed below). I'm using an
Emachine that came with windows 98, an HP 612c printer and
Yahoo's SBCglobal.net. When I go to "print", I get the
following message window:
-----------------------------------------------------------
INTERNET EXPOLORER SCRIPT ERROR
-----------------------------------------------------------
LINE: 228
CHAR: 1
ERROR: Incompatable Version of the RPC STUB
CODE: 0
URL: res://C:\WINDOWS\SYSTEMS\SHDOCLC.DDL/preview.dlg

DO YOU WANT TO CONTINUE RUNNING SCRIPTS ON THIS PAGE?
YES NO
-----------------------------------------------------------
After two calls to SBC they decided it was Microsoft's
problem to solve, because the connection is OK. Microsoft
suggested I contact this newsgroup. Please help me if you
can!!!

Thank you,
George Kanaan

[PattyL]

See several causes and resolutions on Sandi's site:

http://inetexplorer.mvps.org/answers_5.htm

PattyL


"George" > wrote in message
...
>
> 7-18-04
>
> A few days ago (after operating great for 6-months) my
> system just stopped printing my email messages. Also, it
> won't print saved messages that I've sent to my Documents
> file. (If it has an SBC logo in front of it, it I get
> the "error message" listed below). I'm using an
> Emachine that came with windows 98, an HP 612c printer and
> Yahoo's SBCglobal.net. When I go to "print", I get the
> following message window:
> -----------------------------------------------------------
> INTERNET EXPOLORER SCRIPT ERROR
> -----------------------------------------------------------
> LINE: 228
> CHAR: 1
> ERROR: Incompatable Version of the RPC STUB
> CODE: 0
> URL: res://C:\WINDOWS\SYSTEMS\SHDOCLC.DDL/preview.dlg
>
> DO YOU WANT TO CONTINUE RUNNING SCRIPTS ON THIS PAGE?
> YES NO
> -----------------------------------------------------------
> After two calls to SBC they decided it was Microsoft's
> problem to solve, because the connection is OK. Microsoft
> suggested I contact this newsgroup. Please help me if you
> can!!!
>
> Thank you,
> George Kanaan
>