Update Rollup 1 - Service Pack 4 Bug?

[Sal]

Archived from groups: microsoft.public.win2000.general (More info?)

The new update rollup 1 seems to be causing an issue with printing to DELL
printers. Has anyone else had this happen? When installing the printer
through Windows, the process will encounter an error (application referenced
memory ...), but the printer will still be installed. However when trying to
print from an application, the application will crash as soon as the 'Print'
option is used, most likely while trying to get the printer's
status/properties.. as when trying to view the properties of the printer,
another 'memory referenced' error will appear.

Furthermore, the printers were installed on SP4 machines and working, but
after we applied Rollup 1, the issue turned up.

I tested this issue on non rollup 1 machines, and it's fine.

Anyone have ideas or similar issues with the new Rollup?

Non-Dell printers are unaffected (HP for example).

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

These articles may help. Also there is now a v2 of the rollup but WU won't
suggest it if v1 is installed.

http://support.microsoft.com/kb/832219/
http://support.microsoft.com/kb/891861
http://www.microsoft.com/downloads/details.aspx?familyid=B54730CF-8850-4531-B52B-BF28B324C662&displaylang=en

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Sal" wrote:
| The new update rollup 1 seems to be causing an issue with printing to DELL
| printers. Has anyone else had this happen? When installing the printer
| through Windows, the process will encounter an error (application
referenced
| memory ...), but the printer will still be installed. However when trying
to
| print from an application, the application will crash as soon as the
'Print'
| option is used, most likely while trying to get the printer's
| status/properties.. as when trying to view the properties of the printer,
| another 'memory referenced' error will appear.
|
| Furthermore, the printers were installed on SP4 machines and working, but
| after we applied Rollup 1, the issue turned up.
|
| I tested this issue on non rollup 1 machines, and it's fine.
|
| Anyone have ideas or similar issues with the new Rollup?
|
| Non-Dell printers are unaffected (HP for example).

 

[Sal]

Archived from groups: microsoft.public.win2000.general (More info?)

Thanks so much for the help. Unfortunately, this is occuring with V2 of the
rollup

The exact error message is from explorer.exe:

Function address 0x77fcb21d caused a protection fault. Exception code
0xc0000005.
Some or all property pages may not be displayed.





"Dave Patrick" wrote:

> These articles may help. Also there is now a v2 of the rollup but WU won't
> suggest it if v1 is installed.
>
> http://support.microsoft.com/kb/832219/
> http://support.microsoft.com/kb/891861
> http://www.microsoft.com/downloads/details.aspx?familyid=B54730CF-8850-4531-B52B-BF28B324C662&displaylang=en
>
> --
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Sal" wrote:
> | The new update rollup 1 seems to be causing an issue with printing to DELL
> | printers. Has anyone else had this happen? When installing the printer
> | through Windows, the process will encounter an error (application
> referenced
> | memory ...), but the printer will still be installed. However when trying
> to
> | print from an application, the application will crash as soon as the
> 'Print'
> | option is used, most likely while trying to get the printer's
> | status/properties.. as when trying to view the properties of the printer,
> | another 'memory referenced' error will appear.
> |
> | Furthermore, the printers were installed on SP4 machines and working, but
> | after we applied Rollup 1, the issue turned up.
> |
> | I tested this issue on non rollup 1 machines, and it's fine.
> |
> | Anyone have ideas or similar issues with the new Rollup?
> |
> | Non-Dell printers are unaffected (HP for example).
>
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

You might want to get in touch with Dell to see if there is an updated
driver for the printer.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Sal" wrote:
| Thanks so much for the help. Unfortunately, this is occuring with V2 of
the
| rollup
|
| The exact error message is from explorer.exe:
|
| Function address 0x77fcb21d caused a protection fault. Exception code
| 0xc0000005.
| Some or all property pages may not be displayed.

 

[Sal]

Archived from groups: microsoft.public.win2000.general (More info?)

I figured I would have to pursue that option, I just haven't heard back from
them yet on it, and thought maybe someone here had a solution.

Thanks so much, I'll give them another whirl


"Dave Patrick" wrote:

> You might want to get in touch with Dell to see if there is an updated
> driver for the printer.
>
> --
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Sal" wrote:
> | Thanks so much for the help. Unfortunately, this is occuring with V2 of
> the
> | rollup
> |
> | The exact error message is from explorer.exe:
> |
> | Function address 0x77fcb21d caused a protection fault. Exception code
> | 0xc0000005.
> | Some or all property pages may not be displayed.
>
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

You're welcome. Good luck.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Sal" wrote:
|I figured I would have to pursue that option, I just haven't heard back
from
| them yet on it, and thought maybe someone here had a solution.
|
| Thanks so much, I'll give them another whirl