Can windows XP diagnose/repair bad system files (non-boot)?

[mvollmers]

I have been having a problem with not being able to install any sort of
printer (pdf driver, printer, etc). I've got another post around here
somewhere but couldn't get it figured out; basically something crapped out
and not I keep getting an error whenever I try to install. I wonder if I've
got a sys file somewhere that is bad. Anyway, when I run the recovery
console, it talks about repairing the boot, but I can get in the computer
fine. in fact, seems to be running normal, except for the print thing. I
was wondering if I can have windows compare the originals to the ones on the
computer and replace if needed. My other thoughts are it's in the registry
(no clue there) or that I have to wipe everything and start from scratch
(also new territory). Anyway, any suggestions appreciated. Thanks!

 

[Jerry]

Boot from the XP CD and do a repair install. It will 'fix' the XP stuff and
leave your other installed programs alone.

 

[Elmo]

I have been having a problem with not being able to install any sort of
printer (pdf driver, printer, etc). I've got another post around here
somewhere but couldn't get it figured out; basically something crapped out
and not I keep getting an error whenever I try to install. I wonder if I've
got a sys file somewhere that is bad. Anyway, when I run the recovery
console, it talks about repairing the boot, but I can get in the computer
fine. In fact, seems to be running normal, except for the print thing. I
was wondering if I can have Windows compare the originals to the ones on the
computer and replace if needed. My other thoughts are it's in the registry
(no clue there) or that I have to wipe everything and start from scratch
(also new territory). Anyway, any suggestions appreciated. Thanks!

Click Start, Run, type SFC /SCANNOW, click OK. If any files are damaged
or missing, they'll be replaced. You may need to reboot afterwards so
damaged files will be replaced.

 

[John John]

Without knowing what the error is it's pretty difficult for us to give
you any advice. Did you look in the Event Log for other error messages?

sfc /scannow will scan the drive for damaged, mismatched or missing
Windows files and replace them if it can.

John

 

[mvollmers]

John-

the scan didn't show anything (or if it replaced something, I wasn't aware
of it). I tried to install the print driver again, and it didn't work. I
get a window saying that the "EPSOn printer driver setup utility has
encounter a problem and needs to close". They are very sorry for the
inconvenience... Anyway, the event log shows that the SSDP discovery service
failed to start (the account specificed for the service is different from the
account specified for other services running the same process). not sure
what that means; UPDP also has not started (I think that it needs SSDP), for
what that's worth. Maybe this helps out. Thanks.

Mark

 

[John John]

Is the Spooler service running?

John

John-

the scan didn't show anything (or if it replaced something, I wasn't aware
of it). I tried to install the print driver again, and it didn't work. I
get a window saying that the "EPSOn printer driver setup utility has
encounter a problem and needs to close". They are very sorry for the
inconvenience... Anyway, the event log shows that the SSDP discovery service
failed to start (the account specificed for the service is different from the
account specified for other services running the same process). not sure
what that means; UPDP also has not started (I think that it needs SSDP), for
what that's worth. Maybe this helps out. Thanks.

Mark

:

 

[mvollmers]

Yeah. I also got SSDP discovery and Univ plug/play device host services
going now, for what it's worth. I swept the registry, deleting everything I
could with "EPSON" in the name, and that didn't help. In fact, when I jack
the thing in directly to the USB port (I've got it on a print server), I get
a ding like I plugged in a device but the plug/play doesn't grab the printer.
The printer will work on my laptop, so it's a local problem, I'm just not
sure where.

 

[mvollmers]

I ran the repair, and it took care of whatever had been screwed up. no idea
what caused it, still, but at least I can print again. Thanks.