C
charlie
Connecting a networked printer in Win7 can be simple and "automatic" or,
a real pain, as it sometimes was with earlier win versions. There seem
to be several factors involved. Part of the issues certainly involve the
way "ports" are handled by win7.
The presence of a Win7 included default "stripped down" driver may have
some bearing. Finally, some of the printer mfrs have install software
that seems to work if you install it before the printer is "seen" by
windows. Sometimes manual editing of the registry or a restore is needed
to recover.
My most recent experience with this involves multifunction printers from
Epson. Of three models in the Workforce series (600,610,635), the 635
was the most automatic and trouble free install.
But, if you install and additional printer, such as the older/lesser
600, or 610 after the 635, on the same P/C, you can have problems with
some of the epson monitoring modules.
More interesting is the end results of the printer installs. It turns
out that the printers may appear multiple times. One entry may be the
mfrs drivers, a second a WSD (scan device) or/and even some sort of
entry that carries a model number related designation.
It makes some sense when you look at the entries, and is difficult to
easily describe.
As to scan devices that are part of a printer, this gets more confusing.
Usually, the mfrs drivers & software work when nothing else does.
In my case, the work force printers have USB Ethernet, and wireless
capability. The WSD drivers and configuration works, but a multipage
scan from an auto feeder seems to need the mfrs software to work properly.
On the other hand you can often get third party scan software to work
using the WSD drivers, etc.
The LPT1 bit is older than dirt, and is a work around that has stood the
test of time, from MSDOS to the present.
a real pain, as it sometimes was with earlier win versions. There seem
to be several factors involved. Part of the issues certainly involve the
way "ports" are handled by win7.
The presence of a Win7 included default "stripped down" driver may have
some bearing. Finally, some of the printer mfrs have install software
that seems to work if you install it before the printer is "seen" by
windows. Sometimes manual editing of the registry or a restore is needed
to recover.
My most recent experience with this involves multifunction printers from
Epson. Of three models in the Workforce series (600,610,635), the 635
was the most automatic and trouble free install.
But, if you install and additional printer, such as the older/lesser
600, or 610 after the 635, on the same P/C, you can have problems with
some of the epson monitoring modules.
More interesting is the end results of the printer installs. It turns
out that the printers may appear multiple times. One entry may be the
mfrs drivers, a second a WSD (scan device) or/and even some sort of
entry that carries a model number related designation.
It makes some sense when you look at the entries, and is difficult to
easily describe.
As to scan devices that are part of a printer, this gets more confusing.
Usually, the mfrs drivers & software work when nothing else does.
In my case, the work force printers have USB Ethernet, and wireless
capability. The WSD drivers and configuration works, but a multipage
scan from an auto feeder seems to need the mfrs software to work properly.
On the other hand you can often get third party scan software to work
using the WSD drivers, etc.
The LPT1 bit is older than dirt, and is a work around that has stood the
test of time, from MSDOS to the present.