M
mvollmers
I've got a desktop, XP pro version 2002 SP1 that had my epson cx4800
printer/scanner attached to it. Something happened, and I had a system error
and got a blue screen. When I rebooted, the printer could not be found. I
tried to reinstall, and got the following message: "epson printer driver
setup utility has encountered a problem and needs to close. we are sorry for
the inconvenience." I uninstalled the driver, downloaded it, tried again,
same thing. Espon says it is a windows thing. I can hook my laptop up to
the printer, and it works fine. I can actually scan on the desktop fine.
won't even ackoweldge the printer is there. When I loaded up my tax
software, it crapped out at the install of the pdf print driver, so it
appears that there is something that is preventing whatever part of windows
prints from playing. anyone seen anything like this? I had a hardware issue
with a floppy drive, so I was playing around getting that resolved, and in
the process I uninstalled sp2 (also, no room on boot drive), but I think this
happened after that was resolved. Any thoughts appreciated. Thanks!
printer/scanner attached to it. Something happened, and I had a system error
and got a blue screen. When I rebooted, the printer could not be found. I
tried to reinstall, and got the following message: "epson printer driver
setup utility has encountered a problem and needs to close. we are sorry for
the inconvenience." I uninstalled the driver, downloaded it, tried again,
same thing. Espon says it is a windows thing. I can hook my laptop up to
the printer, and it works fine. I can actually scan on the desktop fine.
won't even ackoweldge the printer is there. When I loaded up my tax
software, it crapped out at the install of the pdf print driver, so it
appears that there is something that is preventing whatever part of windows
prints from playing. anyone seen anything like this? I had a hardware issue
with a floppy drive, so I was playing around getting that resolved, and in
the process I uninstalled sp2 (also, no room on boot drive), but I think this
happened after that was resolved. Any thoughts appreciated. Thanks!