Microsoft Updates causes printing problem

G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.device_driver.dev (More info?)

Some time in June after an automatic windows update my
printer stopped printing. I have an Epson Stylus 82 Inkjet
that goes through all the motions but when the page comes
out it is blank. I purchased $75.00 in new ink and still
have the problem. I even installed the printer on another
computer and it works fine there. When I try to reload or
remove the driver to attempt a re-install, I get a message
window that reads:
16 bit windows subsystem
C:\windows\system32\autoexec.nt
The system file is not suitable for running ms-dos and
microsoft windows applications.
What can I do to solve this problem?
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.device_driver.dev (More info?)

First thing to do is to uninstall the printer and then, before reinstalling
it, run a System File Check.

Follow the instructions at my website down to Step 5.

http://www.coribright.com/windows/Article%20One.htm

Then, after the reboot, from the Command Prompt, type:

sfc /scannow

(note the space between the c and the /)

After the check, download and install updated XP drivers from the Epson
website and reinstall the printer.
--
Cari (MS-MVP Printing, Imaging & Hardware)
www.coribright.com

"Pete Donahue" <anonymous@discussions.microsoft.com> wrote in message
news:2ecd01c4a7ca$b1a88420$a601280a@phx.gbl...
> Some time in June after an automatic windows update my
> printer stopped printing. I have an Epson Stylus 82 Inkjet
> that goes through all the motions but when the page comes
> out it is blank. I purchased $75.00 in new ink and still
> have the problem. I even installed the printer on another
> computer and it works fine there. When I try to reload or
> remove the driver to attempt a re-install, I get a message
> window that reads:
> 16 bit windows subsystem
> C:\windows\system32\autoexec.nt
> The system file is not suitable for running ms-dos and
> microsoft windows applications.
> What can I do to solve this problem?
>