Epson 2200 Problem with Win XP Pro

[Rick Rieger]

The ink level monitor seems to hang the printer after printing an image in
Photoshop 7.0. The first image to print works fine, complete with the ink
monitor graphic. When attempting to print the next image, the "Printing..."
dialog appears and then nothing. Eventually, PhotoShop stops responding.
Ending the Photoshop task and then rebooting gives me warning messages about
"EPAPI" and "STM3S Backmon" processes running. Stopping these, then
continuing the reboot, allows me to restart PhotoShop and print one more
image, then the same process occurs. I am running the printer off a USB 2.0
port. Interestingly, when installing the latest driver 5.40, the software
cannot find the printer (although XP can).

Interestingly, when I installed this printer a year ago evidently the
drivers were involved in a conflict so that when booting the OS would
encounter a catastrophic failure, reboot, encounter a catastrophic failure,
etc., etc. The problem occurred whether using a USB or a IEEE 1394
connection. I solved in by restoring the system to a known good state
(with msconfig.exe), then used the Windows installer and pointed it to the
Epson driver on the CD (ver 5.3.1 I believe). No ink monitor, but at least
everything else worked.

Any ideas? TIA!

Rick Rieger

 

[CWatters]

Is there an error in the Application or System Event log around the time the
problem occurs? (use Event Viewer to examine the event log).

I have an Epson 2100 on WinXP Pro and it works fine but I don't use
Photoshop.

 

[Rick Rieger]

The System Event Log shows errors with source "scsiscan" with this detailed
info:

The description for Event ID ( 11 ) in Source ( scsiscan ) cannot be found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
\Device\Scanner0.

Don't know what this means, or if it in fact has anything to do with the
printer.

 

[CWatters]

A Google search on "scsiscan" produces a few hits that mention it in the
same context as printing and scanning - so it probably has something to do
with the problem - unfortunately I couldn't see an immediate answer.

This bit...

The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer

....suggests you might have the printer might be connected to another
computer (eg a shared printer?). If that's correct have a look at the logs
on the computer that the printer is connected to.

Colin

 

[Rick Rieger]

Thanks for your help, Colin. I do appreciate you taking the time.

This printer is not shared. I'll call Epson support and see if they have
anything useful to say (probably not based on prior experience with them).

Rick Rieger

 

[CWatters]

I did a bit more digging....

This page confirms the link between scsiscan and IEE1394.

http://www.microsoft.com/whdc/hwdev/bus/1394/1394tech.mspx

This paragraph on the above page is sort of interesting...

Quote:
If you need to provide the updated version of Scsiscan.sys to customers,
this can be done under the license provision of the Windows DDK. If you
choose to redistribute the Scsiscan.sys file, the file must be copied only
as part of a [CopyFiles] INF section so that proper version checking
occurs."

End Quote"

So that means it might be provided by third parties. I wonder if a printer
or scanner driver you installed provided an old copy of scsiscan that wrote
over the top of the one provided with WinXP?

I did a search on my PC and the ONLY place I found scsiscan was in
c:\windows\driver cache\i386\driver.cab which I think means it isn't
installed on my PC. That would make sense as I don't use 1394 or SCSI
devices only USB.

It might be worth searching your PC for scsiscan.exe to see what date it is
has. See if that date is earlier than the one in your i386 folder?

If you have got an older one installed then I guess you need to figure out
how to extract the later version from the .cab.

Colin

 

[Rick Rieger]

Colin,

Thank you very much for all your work!! I will follow your advice and check
out scsiscan.sys. I'll let you know what I find.

FWIW, I called Epson support and they said they didn't know what to do about
my problem.

Rick Rieger

I did a bit more digging....

This page confirms the link between scsiscan and IEE1394.

http://www.microsoft.com/whdc/hwdev/bus/1394/1394tech.mspx

This paragraph on the above page is sort of interesting...

Quote:
If you need to provide the updated version of Scsiscan.sys to customers,
this can be done under the license provision of the Windows DDK. If you
choose to redistribute the Scsiscan.sys file, the file must be copied only
as part of a [CopyFiles] INF section so that proper version checking
occurs."

End Quote"

So that means it might be provided by third parties. I wonder if a printer
or scanner driver you installed provided an old copy of scsiscan that wrote
over the top of the one provided with WinXP?

I did a search on my PC and the ONLY place I found scsiscan was in
c:\windows\driver cache\i386\driver.cab which I think means it isn't
installed on my PC. That would make sense as I don't use 1394 or SCSI
devices only USB.

It might be worth searching your PC for scsiscan.exe to see what date it is
has. See if that date is earlier than the one in your i386 folder?

If you have got an older one installed then I guess you need to figure out
how to extract the later version from the .cab.

Colin

Thanks for your help, Colin. I do appreciate you taking the time.

This printer is not shared. I'll call Epson support and see if they have
anything useful to say (probably not based on prior experience with them).

Rick Rieger

to

do

may

be the
time with
the

off

a evidently
the it but
at

 

[Rick Rieger]

I found scsiscan.sys in two places only: c:\windows\system32\drivers and
c:\windows\system32\dllcache. Both have the same date: Aug 17, 2001 and are
identical.

Colin,

Thank you very much for all your work!! I will follow your advice and check
out scsiscan.sys. I'll let you know what I find.

FWIW, I called Epson support and they said they didn't know what to do about
my problem.

Rick Rieger

I did a bit more digging....

This page confirms the link between scsiscan and IEE1394.

http://www.microsoft.com/whdc/hwdev/bus/1394/1394tech.mspx

This paragraph on the above page is sort of interesting...

Quote:
If you need to provide the updated version of Scsiscan.sys to customers,
this can be done under the license provision of the Windows DDK. If you
choose to redistribute the Scsiscan.sys file, the file must be copied only
as part of a [CopyFiles] INF section so that proper version checking
occurs."

End Quote"

So that means it might be provided by third parties. I wonder if a printer
or scanner driver you installed provided an old copy of scsiscan that wrote
over the top of the one provided with WinXP?

I did a search on my PC and the ONLY place I found scsiscan was in
c:\windows\driver cache\i386\driver.cab which I think means it isn't
installed on my PC. That would make sense as I don't use 1394 or SCSI
devices only USB.

It might be worth searching your PC for scsiscan.exe to see what date it is
has. See if that date is earlier than the one in your i386 folder?

If you have got an older one installed then I guess you need to figure out
how to extract the later version from the .cab.

Colin

Thanks for your help, Colin. I do appreciate you taking the time.

This printer is not shared. I'll call Epson support and see if they have
anything useful to say (probably not based on prior experience with them).

Rick Rieger

A Google search on "scsiscan" produces a few hits that mention it in the
same context as printing and scanning - so it probably has something

to

do
with the problem - unfortunately I couldn't see an immediate answer.

This bit...

The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer

...suggests you might have the printer might be connected to another
computer (eg a shared printer?). If that's correct have a look at

the
logs

on the computer that the printer is connected to.

Colin


The System Event Log shows errors with source "scsiscan" with this
detailed
info:

The description for Event ID ( 11 ) in Source ( scsiscan ) cannot be
found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You

may

be
able to use the /AUXSOURCE= flag to retrieve this description; see Help
and
Support for details. The following information is part of the event:
\Device\Scanner0.

Don't know what this means, or if it in fact has anything to do

with
the

printer.



Is there an error in the Application or System Event log around the
time
the
problem occurs? (use Event Viewer to examine the event log).

I have an Epson 2100 on WinXP Pro and it works fine but I don't use
Photoshop.


The ink level monitor seems to hang the printer after printing an
image
in
Photoshop 7.0. The first image to print works fine, complete with
the
ink
monitor graphic. When attempting to print the next image, the
"Printing..."
dialog appears and then nothing. Eventually, PhotoShop stops
responding.
Ending the Photoshop task and then rebooting gives me warning
messages
about
"EPAPI" and "STM3S Backmon" processes running. Stopping

these,
then

continuing the reboot, allows me to restart PhotoShop and

print
one

more
image, then the same process occurs. I am running the printer

off

a
USB
2.0
port. Interestingly, when installing the latest driver 5.40, the
software
cannot find the printer (although XP can).

Interestingly, when I installed this printer a year ago evidently
the
drivers were involved in a conflict so that when booting the OS
would
encounter a catastrophic failure, reboot, encounter a catastrophic
failure,
etc., etc. The problem occurred whether using a USB or a IEEE 1394
connection. I solved in by restoring the system to a known good
state
(with msconfig.exe), then used the Windows installer and

pointed
it

to
the
Epson driver on the CD (ver 5.3.1 I believe). No ink monitor, but
at
least
everything else worked.

Any ideas? TIA!

Rick Rieger

 

[Safetymom123]

Have you tried contacting Epson through the tech link on their web site?
They are usually very good at providing answers.

Colin,

Thank you very much for all your work!! I will follow your advice and check
out scsiscan.sys. I'll let you know what I find.

FWIW, I called Epson support and they said they didn't know what to do about
my problem.

Rick Rieger

I did a bit more digging....

This page confirms the link between scsiscan and IEE1394.

http://www.microsoft.com/whdc/hwdev/bus/1394/1394tech.mspx

This paragraph on the above page is sort of interesting...

Quote:
If you need to provide the updated version of Scsiscan.sys to customers,
this can be done under the license provision of the Windows DDK. If you
choose to redistribute the Scsiscan.sys file, the file must be copied only
as part of a [CopyFiles] INF section so that proper version checking
occurs."

End Quote"

So that means it might be provided by third parties. I wonder if a printer
or scanner driver you installed provided an old copy of scsiscan that wrote
over the top of the one provided with WinXP?

I did a search on my PC and the ONLY place I found scsiscan was in
c:\windows\driver cache\i386\driver.cab which I think means it isn't
installed on my PC. That would make sense as I don't use 1394 or SCSI
devices only USB.

It might be worth searching your PC for scsiscan.exe to see what date it is
has. See if that date is earlier than the one in your i386 folder?

If you have got an older one installed then I guess you need to figure out
how to extract the later version from the .cab.

Colin

Thanks for your help, Colin. I do appreciate you taking the time.

This printer is not shared. I'll call Epson support and see if they have
anything useful to say (probably not based on prior experience with them).

Rick Rieger

A Google search on "scsiscan" produces a few hits that mention it in the
same context as printing and scanning - so it probably has something

to

do
with the problem - unfortunately I couldn't see an immediate answer.

This bit...

The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer

...suggests you might have the printer might be connected to another
computer (eg a shared printer?). If that's correct have a look at

the
logs

on the computer that the printer is connected to.

Colin


The System Event Log shows errors with source "scsiscan" with this
detailed
info:

The description for Event ID ( 11 ) in Source ( scsiscan ) cannot be
found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You

may

be
able to use the /AUXSOURCE= flag to retrieve this description; see Help
and
Support for details. The following information is part of the event:
\Device\Scanner0.

Don't know what this means, or if it in fact has anything to do

with
the

printer.



Is there an error in the Application or System Event log around the
time
the
problem occurs? (use Event Viewer to examine the event log).

I have an Epson 2100 on WinXP Pro and it works fine but I don't use
Photoshop.


The ink level monitor seems to hang the printer after printing an
image
in
Photoshop 7.0. The first image to print works fine, complete with
the
ink
monitor graphic. When attempting to print the next image, the
"Printing..."
dialog appears and then nothing. Eventually, PhotoShop stops
responding.
Ending the Photoshop task and then rebooting gives me warning
messages
about
"EPAPI" and "STM3S Backmon" processes running. Stopping

these,
then

continuing the reboot, allows me to restart PhotoShop and

print
one

more
image, then the same process occurs. I am running the printer

off

a
USB
2.0
port. Interestingly, when installing the latest driver 5.40, the
software
cannot find the printer (although XP can).

Interestingly, when I installed this printer a year ago evidently
the
drivers were involved in a conflict so that when booting the OS
would
encounter a catastrophic failure, reboot, encounter a catastrophic
failure,
etc., etc. The problem occurred whether using a USB or a IEEE 1394
connection. I solved in by restoring the system to a known good
state
(with msconfig.exe), then used the Windows installer and

pointed
it

to
the
Epson driver on the CD (ver 5.3.1 I believe). No ink monitor, but
at
least
everything else worked.

Any ideas? TIA!

Rick Rieger

 

[CWatters]

That's the same date as the one in my CAB so it's probably not been replaced
by a "old" copy.

Running out of ideas sorry.

Colin

I found scsiscan.sys in two places only: c:\windows\system32\drivers and
c:\windows\system32\dllcache. Both have the same date: Aug 17, 2001 and are
identical.

Colin,

Thank you very much for all your work!! I will follow your advice and check
out scsiscan.sys. I'll let you know what I find.

FWIW, I called Epson support and they said they didn't know what to do about
my problem.

Rick Rieger

I did a bit more digging....

This page confirms the link between scsiscan and IEE1394.

http://www.microsoft.com/whdc/hwdev/bus/1394/1394tech.mspx

This paragraph on the above page is sort of interesting...

Quote:
If you need to provide the updated version of Scsiscan.sys to customers,
this can be done under the license provision of the Windows DDK. If you
choose to redistribute the Scsiscan.sys file, the file must be copied only
as part of a [CopyFiles] INF section so that proper version checking
occurs."

End Quote"

So that means it might be provided by third parties. I wonder if a printer
or scanner driver you installed provided an old copy of scsiscan that wrote
over the top of the one provided with WinXP?

I did a search on my PC and the ONLY place I found scsiscan was in
c:\windows\driver cache\i386\driver.cab which I think means it isn't
installed on my PC. That would make sense as I don't use 1394 or SCSI
devices only USB.

It might be worth searching your PC for scsiscan.exe to see what date

it
is

has. See if that date is earlier than the one in your i386 folder?

If you have got an older one installed then I guess you need to figure out
how to extract the later version from the .cab.

Colin


Thanks for your help, Colin. I do appreciate you taking the time.

This printer is not shared. I'll call Epson support and see if they have
anything useful to say (probably not based on prior experience with them).

Rick Rieger

A Google search on "scsiscan" produces a few hits that mention it

in
the

same context as printing and scanning - so it probably has

something
to

do
with the problem - unfortunately I couldn't see an immediate answer.

This bit...

The local computer may not have the necessary registry

information

or

cannot

be information
or You
may around
the don't
use printing
an complete
with printer
off 5.40,
the IEEE
1394 monitor,
but

 

[Rick Rieger]

Nope, but I will try. I did phone their technical support number, because
Epson's website said a call "will more likely resolve your problem than
sending an email." The tech support guy on the phone had me check a few
things (all were OK), and then said he had no other advice to offer.

Have you tried contacting Epson through the tech link on their web site?
They are usually very good at providing answers.

Colin,

Thank you very much for all your work!! I will follow your advice and check
out scsiscan.sys. I'll let you know what I find.

FWIW, I called Epson support and they said they didn't know what to do about
my problem.

Rick Rieger

I did a bit more digging....

This page confirms the link between scsiscan and IEE1394.

http://www.microsoft.com/whdc/hwdev/bus/1394/1394tech.mspx

This paragraph on the above page is sort of interesting...

Quote:
If you need to provide the updated version of Scsiscan.sys to customers,
this can be done under the license provision of the Windows DDK. If you
choose to redistribute the Scsiscan.sys file, the file must be copied only
as part of a [CopyFiles] INF section so that proper version checking
occurs."

End Quote"

So that means it might be provided by third parties. I wonder if a printer
or scanner driver you installed provided an old copy of scsiscan that wrote
over the top of the one provided with WinXP?

I did a search on my PC and the ONLY place I found scsiscan was in
c:\windows\driver cache\i386\driver.cab which I think means it isn't
installed on my PC. That would make sense as I don't use 1394 or SCSI
devices only USB.

It might be worth searching your PC for scsiscan.exe to see what date

it
is

has. See if that date is earlier than the one in your i386 folder?

If you have got an older one installed then I guess you need to figure out
how to extract the later version from the .cab.

Colin


Thanks for your help, Colin. I do appreciate you taking the time.

This printer is not shared. I'll call Epson support and see if they have
anything useful to say (probably not based on prior experience with them).

Rick Rieger

A Google search on "scsiscan" produces a few hits that mention it

in
the

same context as printing and scanning - so it probably has

something
to

do
with the problem - unfortunately I couldn't see an immediate answer.

This bit...

The local computer may not have the necessary registry

information

or

cannot

be information
or You
may around
the don't
use printing
an complete
with printer
off 5.40,
the IEEE
1394 monitor,
but