MacOS X + VueScan + SCSI scanner, was OK, now fails

H

Henry

Folks:

OK, buying an EPSON Expression 800 SCSI scanner wasn't the best choice.

It got worse: EPSON provided a working driver for this device for only a
small proportion of the time MacOS X has been out.

VueScan to the rescue. As long as I had the scanner powered at restart
time, VueScan would faithfully recognize and do a great job scanning.

Until today. Even with a restart... Nada. The cables all look OK -- and
are protected so I can't kick them. The SCSI card is found by System
Profiler.

MacOS X 10.3.3 with latest updates, Viewscan 7.6.72.

I'm certain this all worked last week, only difference I can think of is I
installed some OS updates yesterday.

Any ideas?

Thanks,

Henry
 
W

Wilfred

Henry said:
Until today. Even with a restart... Nada. The cables all look OK -- and
are protected so I can't kick them. The SCSI card is found by System
Profiler.
Click to expand...

.... but the scanner is not?
MacOS X 10.3.3 with latest updates, Viewscan 7.6.72.

I'm certain this all worked last week, only difference I can think of is I
installed some OS updates yesterday.
Click to expand...

If the system profiler sees the SCSI card but it doesn't see the
scanner, you may have to reinstall the driver for your SCSI card. My
experience is that some OS X updates remove the driver.
 
H

Henry

Wilfred:

Thanks for your reply on this thred:

... but the scanner is not?
Click to expand...

Doesn't seem to be, but I'm not sure it ever has been.
If the system profiler sees the SCSI card but it doesn't see the
scanner, you may have to reinstall the driver for your SCSI card. My
experience is that some OS X updates remove the driver.
Click to expand...

Hmmm... This is a Adaptec 2930CU that was part of the original system
configuration and has always been supported by the OS. Sorry, I should
have given this info with my original post.

I can imagine that the driver for a third-party user-installed card might be
removed as part of an OS install -- rude, but understandable at some level.
But this is an inherent driver, as far as I know.

The change that seemed to make a difference was most recent update -- last
week, I think.

I think I'll bite the bullet, shut down, and double-check the cables. (Last
time I fooled with the SCSI cable with the machine up, I had a very strange
system crash -- the screen went "foggy". Fortunately, no lost data -- but I
learned my lesson.)

Thanks,

Henry

(e-mail address removed) remove snoring
 
H

Henry

My apologies for bothering everyone, especially Wilfred.

The problem was a hidden loose connector -- the one I checked before posting
the first time. D'oh!

By the way System Profiler _does_ see the scanner when the cable is
connected properly.

Thanks,

Henry

(e-mail address removed) remove sleep
 
Top