REQ: Need help with UMAX Powerlook II scanner

[Robert Heiling]

Actually, it looks to me as though this card has a 50-pin external
connector.

It does. My own cabling is a mess since the cable connected to that 50-pin is
Centronics 25-pin on the other end to attach to a Sysquest EZ-135 removable
cassette drive that I no longer use. Chained out of that Syquest is another
Centronics that ends in a 25-pin male connector for the Umax. I'm too cheap to
pay what they ask for a scsi cable that would go direct, so the Syquest remains
there as part of my cable.<g>

That reminds me before I forget again to ask you if the scsi chain is terminated
at the scanner. There should be a terminator plug on one of the two 25-pin
connectors on the scanner. Lack of termination will usually cause problems, not
sure about the ones you're having, but.

The scanner cable I have has a printer-like end for the
scanner and a 25-pin connector that just happened to fit my UDS-IS11
ISA SCSI card that we have been discussing.

Since the Tekram has nice pricing on EBay, I am wondering if I should
try to buy a new scanner cable - one with the same printer-like end
and the other 50-pin to fit the Tekram DC-395U. I tried to find my
cable on the web, but could not. So I do not know what to look for as
a cable with PowerlookII <-> SCSI compatibility.

That's right. Cost of cable ups your real total cost. Forgot about that if the
total is higher than other options. You can find compatible cables by searching
on "scsi cables" and maybe adding 25pin & 50pin.

On the other hand, there is an Adaptec AVA-2906 that seems to be
compatible with my cable. There are a few on EBay, but with several
days left on bidding.

Not sure which way to go. What do you think?

If the price is right, I'd go for it. Adaptec is a good brand.

Bob

 

[geezer]

It does. My own cabling is a mess since the cable connected to that 50-pin is
Centronics 25-pin on the other end to attach to a Sysquest EZ-135 removable
cassette drive that I no longer use. Chained out of that Syquest is another
Centronics that ends in a 25-pin male connector for the Umax. I'm too cheap to
pay what they ask for a scsi cable that would go direct, so the Syquest remains
there as part of my cable.<g>

That reminds me before I forget again to ask you if the scsi chain is terminated
at the scanner. There should be a terminator plug on one of the two 25-pin
connectors on the scanner. Lack of termination will usually cause problems, not
sure about the ones you're having, but.

Interesting. The Powerlook II has two such 25-pin connectors. One is
used to link the optional 'lid' I have from the scanner's base. The
other is open. Maybe it does need a terminator plug. I don't have
one. If you ask how the computer's SCSI connects to the scanner,
there is another connector on the scanner which I have been calling a
'printer-like' connector. Is it Centronix?

 

[Robert Heiling]

Interesting. The Powerlook II has two such 25-pin connectors. One is
used to link the optional 'lid' I have from the scanner's base. The
other is open. Maybe it does need a terminator plug. I don't have
one. If you ask how the computer's SCSI connects to the scanner,
there is another connector on the scanner which I have been calling a
'printer-like' connector. Is it Centronix?

That could conceivably be a problem. I think you earlier mentioned that you had
found a manual for the Powerlook III. I'm looking at Page 3 which gives a rear
view and shows a UTA connector, 50-pin connector, and a 25-pin connector. That
UTA might be what you just wondered was a Centonics. From what you've been
telling me, the Powerlook II has two 25's instead of a 25 and a 50. Mine also
has two 25's. The cable to the computer scsi card uses one of them and there is
a terminator (no wire) on the other. Look at Page 6 and you'll see where they
say to terminate. If that lid is not attached & plugged, then you are not
termimnated. With the lid plugged in, it might be self-terminating, I don't
know.

On at least one of the scanners at:
http://www.popphoto.com/article.asp?section_id=3&article_id=428&print_page=y
seems to indicate that the UTA is used for the adapter (lid?)

Bob

 

[geezer]

That could conceivably be a problem. I think you earlier mentioned that you had
found a manual for the Powerlook III. I'm looking at Page 3 which gives a rear
view and shows a UTA connector, 50-pin connector, and a 25-pin connector. That
UTA might be what you just wondered was a Centonics. From what you've been
telling me, the Powerlook II has two 25's instead of a 25 and a 50. Mine also
has two 25's. The cable to the computer scsi card uses one of them and there is
a terminator (no wire) on the other. Look at Page 6 and you'll see where they
say to terminate. If that lid is not attached & plugged, then you are not
termimnated. With the lid plugged in, it might be self-terminating, I don't
know.

On at least one of the scanners at:
http://www.popphoto.com/article.asp?section_id=3&article_id=428&print_page=y
seems to indicate that the UTA is used for the adapter (lid?)

Bob

In my downloaded documentation, page 6 is for the MAC, but it does
clearly say to put a terminator in the other 25-pin connector, the
'remaining SCSI port'. So - I will try to find a terminator
somewhere.

Thanks

Geezer

 

[geezer]

That could conceivably be a problem. I think you earlier mentioned that you had
found a manual for the Powerlook III. I'm looking at Page 3 which gives a rear
view and shows a UTA connector, 50-pin connector, and a 25-pin connector. That
UTA might be what you just wondered was a Centonics. From what you've been
telling me, the Powerlook II has two 25's instead of a 25 and a 50. Mine also
has two 25's. The cable to the computer scsi card uses one of them and there is
a terminator (no wire) on the other. Look at Page 6 and you'll see where they
say to terminate. If that lid is not attached & plugged, then you are not
termimnated. With the lid plugged in, it might be self-terminating, I don't
know.

On at least one of the scanners at:
http://www.popphoto.com/article.asp?section_id=3&article_id=428&print_page=y
seems to indicate that the UTA is used for the adapter (lid?)

Bob

I bought a 'terminator' and tried the scanner again. No luck.
Same 'scan failed' result. I guess the next thing to try will be
another SCSI card (PCI), if I can get my hands on one. My friend says
he may have found one that could have come with the scanner, and is
mailing it to me.

Thanks for helps

Geezer

 

[Robert Heiling]

I bought a 'terminator' and tried the scanner again. No luck.
Same 'scan failed' result. I guess the next thing to try will be
another SCSI card (PCI), if I can get my hands on one. My friend says
he may have found one that could have come with the scanner, and is
mailing it to me.

I just fired up our Win98 machine and looked around. It has a usb Canon scanner
and all the twain modules are the old original 1996-7 ones, so that doesn't
enlighten. But we might have been missing something as there is a
C:\Windows\twain.log that could possibly contain some useful error reporting in
your case! Take a look. The previous session on my Win98 machine was a clean one
and here's its log:
TWAIN_32.DLL - MESSAGE - CTwunk ::AppInitialize - Reset Log

TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Starting Thunker

TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Startup Complete To Twain
TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Received Startup Complete From
Thunker

TWAIN_32.DLL - MESSAGE - DSM --DSM_Entry - Nested Call From Source Allowed

TWAIN_32.DLL - MESSAGE - DSM --DSM_Entry - Nested Call From Source Allowed

TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Posting Close To Thunker

TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Shutdown Complete To Twain
TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Received Shutdown Complete From
Thunker


Bob

 

[geezer]

I just fired up our Win98 machine and looked around. It has a usb Canon scanner
and all the twain modules are the old original 1996-7 ones, so that doesn't
enlighten. But we might have been missing something as there is a
C:\Windows\twain.log that could possibly contain some useful error reporting in
your case! Take a look. The previous session on my Win98 machine was a clean one
and here's its log:
TWAIN_32.DLL - MESSAGE - CTwunk ::AppInitialize - Reset Log

TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Starting Thunker

TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Startup Complete To Twain
TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Received Startup Complete From
Thunker

TWAIN_32.DLL - MESSAGE - DSM --DSM_Entry - Nested Call From Source Allowed

TWAIN_32.DLL - MESSAGE - DSM --DSM_Entry - Nested Call From Source Allowed

TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Posting Close To Thunker

TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Shutdown Complete To Twain
TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Received Shutdown Complete From
Thunker


Bob

Bob-

This is the content of my log file:

TWAIN_32.DLL - MESSAGE - CTwunk ::AppInitialize - Reset Log

TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Starting Thunker

TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Startup Complete
To Twain
TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Received Startup
Complete From Thunker

TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Posting Close To
Thunker

TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Shutdown Complete
To Twain
TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Received Shutdown
Complete From Thunker

Doesn't tell me anything. Does it you?

Thanks

Geezer

 

[Robert Heiling]

Bob-

This is the content of my log file:

TWAIN_32.DLL - MESSAGE - CTwunk ::AppInitialize - Reset Log
TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Starting Thunker
TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Startup Complete
To Twain
TWAIN_32.DLL - MESSAGE - CTwunk ::OpenServer - Received Startup
Complete From Thunker
TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Posting Close To
Thunker
TWUNK_16.EXE - MESSAGE - Twunk --WinMain - Posting Shutdown Complete
To Twain
TWAIN_32.DLL - MESSAGE - CTwunk ::CloseServer - Received Shutdown
Complete From Thunker

Doesn't tell me anything. Does it you?

Only that your system is working as well as mine for that part. They did't
bother to timestamp those messages, but if the "modified" date on that file
agrees with the recent testing then we'll know that it wasn't just a leftover
from some past time and comes from the current testing. I had just figured that
if there was some error message in there we wouldn't want to miss it.

We'll probably just have to wait for that other card to arrive in the mail and
see what happens then.

Bob

 

[geezer]

Only that your system is working as well as mine for that part. They did't
bother to timestamp those messages, but if the "modified" date on that file
agrees with the recent testing then we'll know that it wasn't just a leftover
from some past time and comes from the current testing. I had just figured that
if there was some error message in there we wouldn't want to miss it.

We'll probably just have to wait for that other card to arrive in the mail and
see what happens then.

Bob

Good catch! The file date is 1/1/98! Obviously it was not updated or
used. Now I have to figure out why I guess.

Thanks

Geezer

 

[geezer]

Only that your system is working as well as mine for that part. They did't
bother to timestamp those messages, but if the "modified" date on that file
agrees with the recent testing then we'll know that it wasn't just a leftover
from some past time and comes from the current testing. I had just figured that
if there was some error message in there we wouldn't want to miss it.

We'll probably just have to wait for that other card to arrive in the mail and
see what happens then.

Bob

Partial Success!

I reverted to first base - and downloads a basic set of UMAX software
- the stuff I am some familiar with.
That software includes so-called VISTASCAN which I have used. After
removing all prior loadings (except SCSI stuff), I installed the basic
stuff, including VISTASCAN - it worked!

Then I installed MAGICSCAN V4.5 which is really neat-looking software
and is supposed to be compatible with the Powerlook. It killed the
scanner. Not only did it not work as before, but VISTASCAN no longer
worked either.

I uninstalled everything and start over again with just VISTASCAN - it
works again thank goodness, Now I have to find out why MAGICSCAN
fails so badly.


BTW the TWAIN log file is being updated now, unlike before.

Thanks for your helps.

Geezer

 

[Robert Heiling]

Partial Success!

I reverted to first base - and downloads a basic set of UMAX software
- the stuff I am some familiar with.
That software includes so-called VISTASCAN which I have used. After
removing all prior loadings (except SCSI stuff), I installed the basic
stuff, including VISTASCAN - it worked!

That's certainly good news!

Then I installed MAGICSCAN V4.5 which is really neat-looking software
and is supposed to be compatible with the Powerlook. It killed the
scanner. Not only did it not work as before, but VISTASCAN no longer
worked either.

I guess some modules must have gotten overwritten. There are 2 versions of
Vistascan on my machine here with different skins that I can choose between, but
they must use compatible .dll's etc. Magicscan has a warning about installing
different versions of Magicscan at the same time, but I can't tell if that also
applies against Vistascan.

I uninstalled everything and start over again with just VISTASCAN - it
works again thank goodness,

Does that mean that you've done an actual scan using Irfanview or only used the
testing function?

Now I have to find out why MAGICSCAN
fails so badly.

If you've now established that the scanner is good are you sure that you want to
spend any more time on the Win98/ISA card testing machine? WinXP and the PCI
card will be another playing field with its own set of challenges.

BTW the TWAIN log file is being updated now, unlike before.

I don't have Magicscan installed, so I don't know what different modules it has,
but perhaps it has some other .log file that might yield a clue or a .ini file
with suspicious value(s).

Bob

 

[geezer]

Only that your system is working as well as mine for that part. They did't
bother to timestamp those messages, but if the "modified" date on that file
agrees with the recent testing then we'll know that it wasn't just a leftover
from some past time and comes from the current testing. I had just figured that
if there was some error message in there we wouldn't want to miss it.

We'll probably just have to wait for that other card to arrive in the mail and
see what happens then.

Bob

It arrived - guess what? It is an ISA card, just like my present one.
However I have since downloaded several versions of MagicScan, and I
found that v3.1 runs under W98SE fine. So I am in good shape for now.

Thanks again

Geezer