Installling Printers

[Richard]

I have a Kyocera FS-1020D printer. I've always had a problem of being able
to install the printer, yet WindowsXP not recognising that it exists,
causing the New Hardware Wizard to come on whenever the printer is switched
on. This even though the printer is shown installed in "Printers and Faxes".

In an effort to use the latest drivers, instead of using the CD that came
with the printer, I downloaded an installer program made by Kyocera called:
KXDriver-W2k_XP_3.1.1434.

Running this programe installs the printer, but of course XP does not
recognise that there is a printer installed.

It's weird how you can install a printer, but how XP cannot know of it.

What is the basic problem?

 

[Al]

I have a Kyocera FS-1020D printer. I've always had a problem of being able
to install the printer, yet WindowsXP not recognising that it exists,
causing the New Hardware Wizard to come on whenever the printer is switched
on. This even though the printer is shown installed in "Printers and Faxes".

In an effort to use the latest drivers, instead of using the CD that came
with the printer, I downloaded an installer program made by Kyocera called:
KXDriver-W2k_XP_3.1.1434.

Running this programe installs the printer, but of course XP does not
recognise that there is a printer installed.

It's weird how you can install a printer, but how XP cannot know of it.

What is the basic problem?

The key question is, "Does the printer work?"
It sounds like it's not completely installed and may be missing some
driver files. I assume you followed directions for the installation.
You probably need to install the drivers before turning on the printer
and then let XP find it and install the drivers waiting in the temp
files.

It could also be that XP is giving you an "Access Denied" message so
quickly flashing on the screen that you can't observe it. Then it goes
ahead with the partial installation. This can happen even when you are
signed on as administrator. Certain keys in the registry can be set to
stay closed by various previous software changes made on the computer.
I encountered this when trying to ad SP3 to XP and found a special
program that went through the registry and turned everything back on.
I had no problems since.