SCSI problems - Nikon LS-30 on XP with IWill/Advansys 2930U+

[edhead]

Hello all,

Just picked up a Nikon LS-30 on fleaBay and wondering whether I will
(no pun intended) regret it...

This is my environment:

Windows XP Pro SP1 (and don't want to go to SP2)
LS-30
IWill 2930U+ PCI SCSI adaptor - this appears to have an Advansys
chipset

After inserting the SCSI card, XP recognised it and installed it using
the default Advansys driver - I am unable to find *any* support for
this card anywhere online so I don't have much choice with the driver.

I then installed the most recent Adaptec ASPI layer (4.6 although the
installer is labelled as 4.7 see:
http://radified.com/ASPI/forceaspi.htm for an explanation) and it shows
up as installed correctly in ASPIchk.exe. I also installed the most
recent NikonScan (although this is pointless if I can't see the device
I suppose)

Although the adaptor is visible and reported as working in Device
Manager, there is no sign of the LS-30. When I start the machine I can
go into the SCSI card control panel with Ctrl-A - from here, the
scanner is not found when I do a bus scan.

I have tried all non-reserved SCSI IDs and all spare PCI slots to no
avail. So, a few questions:

- (obvious) anyone had this card working under XP?
- does anyone know about the truth of this ForceASPI site referenced
above? (Basically, allegedly the Adaptec ASPI layer only recognises
Adaptec products?)
- should the scanner be visible in a SCSI bus scan - I'm thinking
perhaps not since it is not a 'drive'
- could this be a bad cable or would that have different symptoms?
- can anyone recommend a SCSI card for XP that *definitely* works for
the LS-30?
- any other insights?

Many thanks for any help,
cam

 

[Paul Simons]

Although the adaptor is visible and reported as working in Device
Manager, there is no sign of the LS-30.

These statements do not contradict each other. Your scanner may be not
ready. Did you turn it on before booting your computer (you should,
otherwise try 'scan for hardware changes' in the Windows Device manager)?
What is the length of the SCSI-cable? Try to use a short cable (1 meter
max.). Is the SCSI-chain terminated (perhaps you can set up the scanner to
do so, read the manual). Try using other SCSI-equipment to see if they work,
that way you can determine wether the SCSI-card or the scanner is causing
the problem.

Good luck,
Paul

 

[colmmccartan]

Paul,

Good advice - my first plan will be to try a different cable and,
failing that, I will cadge a known-good SCSI card from somewhere and
try that. I'm suspicious of the Iwill because its pretty old and there
are just so few responses for it on a Google search...

I should have said that I have the built-in terminator activated on the
LS-30 and that I tried scanning for hardware changes. I made a habit of
starting up the scanner first, but once or twice tried starting after
the computer and then re-scanning. No results with any combination of
power-ons.

The cable is about a meter long.

Cheers for the response.
cam

 

[edhead]

Paul,

Good advice - my first plan will be to try a different cable and,
failing that, I will cadge a known-good SCSI card from somewhere and
try that. I'm suspicious of the Iwill because its pretty old and there
are just so few responses for it on a Google search...

I should have said that I have the built-in terminator activated on the
LS-30 and that I tried scanning for hardware changes. I made a habit of
starting up the scanner first, but once or twice tried starting after
the computer and then re-scanning. No results with any combination of
power-ons.

The cable is about a meter long.

Cheers for the response.
cam

 

[CSM1]

Hello all,

Just picked up a Nikon LS-30 on fleaBay and wondering whether I will
(no pun intended) regret it...

This is my environment:

Windows XP Pro SP1 (and don't want to go to SP2)
LS-30
IWill 2930U+ PCI SCSI adaptor - this appears to have an Advansys
chipset

After inserting the SCSI card, XP recognised it and installed it using
the default Advansys driver - I am unable to find *any* support for
this card anywhere online so I don't have much choice with the driver.

I then installed the most recent Adaptec ASPI layer (4.6 although the
installer is labelled as 4.7 see:
http://radified.com/ASPI/forceaspi.htm for an explanation) and it shows
up as installed correctly in ASPIchk.exe. I also installed the most
recent NikonScan (although this is pointless if I can't see the device
I suppose)

Although the adaptor is visible and reported as working in Device
Manager, there is no sign of the LS-30. When I start the machine I can
go into the SCSI card control panel with Ctrl-A - from here, the
scanner is not found when I do a bus scan.

I have tried all non-reserved SCSI IDs and all spare PCI slots to no
avail. So, a few questions:

- (obvious) anyone had this card working under XP?
- does anyone know about the truth of this ForceASPI site referenced
above? (Basically, allegedly the Adaptec ASPI layer only recognises
Adaptec products?)
- should the scanner be visible in a SCSI bus scan - I'm thinking
perhaps not since it is not a 'drive'
- could this be a bad cable or would that have different symptoms?
- can anyone recommend a SCSI card for XP that *definitely* works for
the LS-30?
- any other insights?

Many thanks for any help,
cam

Problems Using SCSI Scanner Without an Updated ASPI Layer
http://support.microsoft.com/default.aspx?scid=kb;en-us;300674

For SCSI ID try something other than 0,1 or 7. Zero and One are usually for
hard drives and 7 is sometimes reserved. When I had a SCSI scanner, I used
ID 2 or ID 3.

You have said that you installed some kind of ASPI.

Adaptec ASPI works with all scanner product brands.

The only one I know that works is the one from Adaptec.
http://www.adaptec.com/worldwide/su...roduct/ASPI-4.70&prodkey=Windows+ASPI+Package

The current version ASPI download for Windows XP.
http://download.adaptec.com/software_pc/aspi/aspi_471a2.exe

 

[RSD99]

"CSM1" posted:
"...
For SCSI ID try something other than 0,1 or 7. Zero and One are usually for
hard drives and 7 is sometimes reserved.
...."

IIRC there's no "sometimes" about it. SCSI ID 7 actually *is* reserved ...
always! It's the ID for the controller itself.

 

[edhead]

Problems Using SCSI Scanner Without an Updated ASPI Layer

http://support.microsoft.com/default.aspx?scid=kb;en-us;300674

I'm asuming that, since I do have an ASPI layer, and one which is
reported as functioning by aspichk.exe, that this is not relevant. In
any case, it just advises you to go toAdaptec and download the ASPI
drivers.

For SCSI ID try something other than 0,1 or 7. Zero and One are usually for
hard drives and 7 is sometimes reserved. When I had a SCSI scanner, I used
ID 2 or ID 3.

I tried all IDs apart from 7 which is reserved by the controller. I'd
be really interested if anyone can tell me whether I should be able to
see the scanner when I do a Bus Scan from the controller's Setup menu.

It reports "No drives found" which I assume means it can't see the
scanner but I just had an inkling of doubt since it specically says
"drives" - would it ignore the scanner because it is not a hard drive?

You have said that you installed some kind of ASPI.

Adaptec ASPI works with all scanner product brands.

The only one I know that works is the one from Adaptec.
http://www.adaptec.com/worldwide/su...roduct/ASPI-4.70&prodkey=Windows+ASPI+Package

The current version ASPI download for Windows XP.
http://download.adaptec.com/software_pc/aspi/aspi_471a2.exe

Thanks - this is the version that I installed. I just happened to
stumble across that ForceASPI site which said some people had had
better results using theirs... tried it as a last resort, but with no
result.

Thanks again for the responses - still keen to hear about the bus scan
thing and any recommended cards for XP/LS-30.

Cheers
cam

 

[birdman]

The number one cause of this problem, presuming the scanner is not dead, is
a problem with the scsi cable. This is one of the many reasons why SCSI
never caught on except when it was forced down Apple users throats.
Look at your own cable and make sure none of the pins are bent and that it
seats properly in the receptacles. CAble problems have sent many functional
scsi peripherals to the dumpster.
Unfortunately SCSI cables are very expensive in most stores and the naming
conventions for the different pin sets is incomprehensible to most people.
However you may have to obtain another scsi cable to see if that is the
problem. If your computer recognizes and installs your SCSI card it is not
likely the cause of your problem.

 

[CSM1]

I'm asuming that, since I do have an ASPI layer, and one which is
reported as functioning by aspichk.exe, that this is not relevant. In
any case, it just advises you to go toAdaptec and download the ASPI
drivers.

If aspichk.exe finds a working ASPI layer, why is it advising to download a
ASPI layer? Oh, you mean Microsoft is advising downloading the ASPI layer.

I tried all IDs apart from 7 which is reserved by the controller. I'd
be really interested if anyone can tell me whether I should be able to
see the scanner when I do a Bus Scan from the controller's Setup menu.

It reports "No drives found" which I assume means it can't see the
scanner but I just had an inkling of doubt since it specically says
"drives" - would it ignore the scanner because it is not a hard drive?


Thanks - this is the version that I installed. I just happened to
stumble across that ForceASPI site which said some people had had
better results using theirs... tried it as a last resort, but with no
result.

Thanks again for the responses - still keen to hear about the bus scan
thing and any recommended cards for XP/LS-30.

Cheers
cam

Are you pretty sure that the scanner is not malfunctioning? If the scanner
is Dead On Arrival, then nothing will work.

You must be Administrator.

Is there any failed scanner software installation on the computer? If so
remove it. Start over.

Is there more that one SCSI controller showing in Device Manager? If so,
remove all of them. Reboot. XP will install the correct driver for the card.

If the SCSI card is working in Windows XP, and you have ASPI installed. And
you have installed the Manufacturers Scanner Driver. (You must install the
TWAIN driver before connecting the scanner). See below for download link.

Keep the cable length to 1 meter (about 3 feet) or less. Look for any bent
or broken pins on the cable connectors. Be sure the connectors are seated
well.

Set the ID before connection and powering on the scanner. Try ID 2. Switch
is usually on the rear of the scanner beside the SCSI plug. It must be the
only device on the SCSI line with that ID. If there is a terminator,
activate it. Once the scanner is recognized, never change the ID.

When you have the computer running, then turn on the scanner.
Windows XP's reaction is to start the Hardware wizard (or at least but a
notice on the task bar) if it sees the scanner hardware on the SCSI line.

The first time takes a few seconds to react.
Once XP installs the TWAIN driver for the scanner, it will start up the
TWAIN pretty damn quick.
You also must have some image editor software with a TWAIN interface.
Irfanview, Photoshop Elements or Photoshop for example.

If the TWAIN is installed, you will find a .ds (and maybe more files) in
%SYSTEMROOT%\Twain_32\scannername\
%SYSTEMROOT% is usually C:\Windows.

You should download and install the latest software from Nikon for the
LS-30.
http://support.nikontech.com/cgi-bin/nikonusa.cfg/php/enduser/std_alp.php

The latest for the LS-30 is Nikon Scan 3.1.2 full version for Windows.
In order to install Nikon Scan version 3.1.x the user must have
Administration rights on the computer.

 

[edhead]

OK, thats interesting to hear - I have rarely used SCSI with a PC and
never on this home machine. I'm kind of hoping it's the cable...

 

[edhead]

If aspichk.exe finds a working ASPI layer, why is it advising to
download a

ASPI layer? Oh, you mean Microsoft is advising downloading the ASPI layer.

Yes, sorry - I meant that tech note you kindly dug up for me...

Are you pretty sure that the scanner is not malfunctioning? If the scanner
is Dead On Arrival, then nothing will work.

No, I'm by no means sure.. but this is the worst case. The original
seller seems genuine and is trying to help me get it going, but who
knows? It may have been damaged in transit (the transport screws were
not secured but I would expect this to cause mechanical problems rather
than this sort of thing).

You must be Administrator.
Sure.

Is there any failed scanner software installation on the computer? If so
remove it. Start over.

None whatsoever. I have never had a scanner or any other SCSI devices
or controllers on this machine.

Is there more that one SCSI controller showing in Device Manager? If so,
remove all of them. Reboot. XP will install the correct driver for the card.

No, just the Advansys which it autodetected and says is running
successfully.

If the SCSI card is working in Windows XP, and you have ASPI installed. And
you have installed the Manufacturers Scanner Driver. (You must install the
TWAIN driver before connecting the scanner). See below for download link.

I grabbed the latest NikonScan from nikonusa (away from the machine now
and don't remember the version - can anyone state a version which
definitely works with the LS-30 on XP?)

Keep the cable length to 1 meter (about 3 feet) or less. Look for any bent
or broken pins on the cable connectors. Be sure the connectors are seated
well.

I will check it out. Its about a meter in length anyway. The original
seller says that this was his 'spare' and he's mailing me the actual
cable which he used with the scanner himself (altho on Win2K).

Set the ID before connection and powering on the scanner. Try ID 2. Switch
is usually on the rear of the scanner beside the SCSI plug. It must be the
only device on the SCSI line with that ID. If there is a terminator,
activate it. Once the scanner is recognized, never change the ID.

I tried them all but left it at 2 since this is the original Nikon
factory state according to the manual. Built-in terminator is switched
on. Tried both SCSI ports (the LS-30 has 2 and the manual says either
can be used).

When you have the computer running, then turn on the scanner.
Windows XP's reaction is to start the Hardware wizard (or at least but a
notice on the task bar) if it sees the scanner hardware on the SCSI line.

The first time takes a few seconds to react.
Once XP installs the TWAIN driver for the scanner, it will start up the
TWAIN pretty damn quick.
You also must have some image editor software with a TWAIN interface.
Irfanview, Photoshop Elements or Photoshop for example.

If the TWAIN is installed, you will find a .ds (and maybe more files) in
%SYSTEMROOT%\Twain_32\scannername\
%SYSTEMROOT% is usually C:\Windows.

I will check for these and I already have Photoshop, GIMP and IrfanView
on this machine.

Either switching the scanner on before the machine or doing it later
and then starting a 'scan for hardware changes', the machine is
blissfully unaware of the scanner. As is VueScan which, I am told, some
people say can find the scanner even when the Device Manager is having
trouble.

Note that scanning the bus from the SCSI startup control panel shows no
devices which makes me suspect the cable for some reason.

You should download and install the latest software from Nikon for the
LS-30.
http://support.nikontech.com/cgi-bin/nikonusa.cfg/php/enduser/std_alp.php

The latest for the LS-30 is Nikon Scan 3.1.2 full version for Windows.
In order to install Nikon Scan version 3.1.x the user must have
Administration rights on the computer.

Done - this should install the TWAIN stuff, yes? I should say that I
went straight for this rather than install the CD-ROM that came with
the scanner since I thought the CD-ROM would be so out of date...

I think I really have to try a new cable and then a new SCSI card in
that order. Thereafter, trying it on another machine somehow is the
next step before I assume it's just knackered...

I'm sure you all know how miserable it can be when things 'just *don't*
work' so I much appreciate the detailed responses - I won't get a
chance to try stuff out until next week but I will post a summary.

Cheers again,
cam

 

[justinet13]

edhead napisał(a):

OK, thats interesting to hear - I have rarely used SCSI with a PC and
never on this home machine. I'm kind of hoping it's the cable...

Hi. I'm afraid you need to change your Advansys SCSI card with Adaptec
one instead of new cable. I've tried to work on LS-30 with Advansys card
but not succesful. You should read compatible SCSI cards on Nikon site
and buy one . Regards, Bogdan
PS Sorry for my poor english

 

[edhead]

edhead napisal(a):
Hi. I'm afraid you need to change your Advansys SCSI card with Adaptec
one instead of new cable. I've tried to work on LS-30 with Advansys card
but not succesful. You should read compatible SCSI cards on Nikon site
and buy one . Regards, Bogdan
PS Sorry for my poor english

Bogdan, I've seen that list and noticed that they're keen on Adaptec.
Thanks for letting me know your experiences (and your English is a lot
better than my Polish...)

Thanks,
cam

 

[Danny]

Hello, aspi is not a factor when you talk about running the scis bus
scan utility onboard your scsi controller. In fact the OS is not a
factor at all. The scsi bus scan is occurring BEFORE windows begins to
load.

The scsi bus scan should detect the microcode found on the firmware of
whichever device you connect - with or without device drivers. If the
bus scan doesn't detect any devices other that the scsi controller
itself on ID 7, that would mean one of 2 things:

Either the connectivity to the device is bad ( bad cable, bad interface
on either the scsi card or the interface of the scanner,etc...
====OR====

bad scanner

note: make sure the scanner is powered up and at a ready state prior to
scanning the bus. also check with the manufacturer to see if there's
any diagnostic tests which can be run on the imaging hardware if you
suspect it may be the point of failure.

Hope this helps...

 

[edhead]

Hello, aspi is not a factor when you talk about running the scis bus
scan utility onboard your scsi controller. In fact the OS is not a
factor at all. The scsi bus scan is occurring BEFORE windows begins to
load.

This makes sense.

The scsi bus scan should detect the microcode found on the firmware of
whichever device you connect - with or without device drivers. If the
bus scan doesn't detect any devices other that the scsi controller
itself on ID 7, that would mean one of 2 things:

Either the connectivity to the device is bad ( bad cable, bad interface
on either the scsi card or the interface of the scanner,etc...
====OR====

bad scanner

Again, this makes a lot of sense but I was unsure so thanks for
confirming it.

note: make sure the scanner is powered up and at a ready state prior to
scanning the bus. also check with the manufacturer to see if there's
any diagnostic tests which can be run on the imaging hardware if you
suspect it may be the point of failure.

Hope this helps...

Cheers, it already does.
cam

 

[catfish]

Hello all, --snip--
- any other insights?

Many thanks for any help,
cam

a thought - the correct sequence for powering up must be followed.
1 - EVERYTHING off
2 - turn on scanner power
3 - turn on the rest of the stuff - and only now turn on the computer

SCSI devices are NOT plug and play self sensing the same way usb or
firewire devices are. They need to be powered on BEFORE the computer
is.

hope this helps

 

[edhead]

An Adaptec AVA-2904 (tenner off ebay) fixed it. This was incorrectly
auto-recognised as an AIC-7815 ( I think?) but the scanner was seen by
the hardware wizard at next reboot.

Still don't have an XP driver for the LS-30 but Vuescan and NikonScan
both work great.

Thanks for all the responses.
cam

 

[CSM1]

An Adaptec AVA-2904 (tenner off ebay) fixed it. This was incorrectly
auto-recognised as an AIC-7815 ( I think?) but the scanner was seen by
the hardware wizard at next reboot.

Still don't have an XP driver for the LS-30 but Vuescan and NikonScan
both work great.

Thanks for all the responses.
cam

Just go to Nikon Support in the USA.

Support and Software download for Nikon LS-30.
http://www.nikonusa.com/template.php?goingto=dtc_options&cat=1&grp=2&productNr=9234

Click on Software downloads.
Select Nikon Scan 3.1.2 Full Version - Windows.
Or select Current Versions of Nikon Software for the complete list of
available software.

Nikon Scan 3.1.2 supports Windows XP.