Nikon LS-4000 ED Firewire driver W2K help needed!

[peter wagner]

Hello to all,

I encountered the following Problem:

I'm running a Nikon LS-4000 ED IEEE 1394 SBP2 Device (So calls Windows
Hardware Assistent the device) until now on a W98SE-System without
problems.
As far as I remember, also *without any* troubles when installing some
years ago.

Now I will change to a faster W2K based System and run into trouble:
The device is physically connected. Windows recognizes as "other Device
(Yellow Questionmark) with the above mentionend name and searches for
Driver and (expectedly) finds none. Not in the W2K-CD, not in the
Nikon-provided CD.

The only hint I found in Google was some Forum about some SCSI-driver,
not very precise anyway. But this is a Firewire-device, so that makes no
sense for me.

Can anybody give some clear hint, which driver is needed and where I
will find it.


Many thanks in advance

Peter (he in the moor) Wagner

 

[Chuck Tribolet]

The good news is that it will work with WinXP (I've got mine running on two
systems, my desktop with the Nikon-supplied card, and my laptop with a
SIIG 1394 CardBus Dual card (TI chipset) PCMCIA fireware card.

The scanner is currently on my laptop and Windows Device Manager
says the driver for the scanner is from Nikon, Version 4.0.0.0 dated
02/03/2003 and has files C:\WINDOWS\system32\drivers\scsiscan.sys
and C:\WINDOWS\system32\NKSCUSD.dll

SCSI is both an electical protocol and a command protocol. The command protocol
can be sent over the SCSI electical protocol, Firewire, FibreChannel, SSA,USB, ATA (=IDE)
(essentially all ATA CD-ROMs run this way) and even around the world via the
internet. So don't discount something that mentions SCSI.

Have you checked Nikon's website for a newer driver?

 

[peter wagner]

Hello, Chuck:

The good news is that it will work with WinXP (I've got mine running on two
systems, my desktop with the Nikon-supplied card, and my laptop with a
SIIG 1394 CardBus Dual card (TI chipset) PCMCIA fireware card.

I'm sure, it will work at last. I was only confused about having trouble
w/ W2K, when W98SE runs without problems. Mostly I got problems the
other way, running things in W98SE, that run with W2k without problems.

What I didn't mention: Both systems run adaptec-based SCSI-disks.

The scanner is currently on my laptop and Windows Device Manager
says the driver for the scanner is from Nikon, Version 4.0.0.0 dated
02/03/2003 and has files C:\WINDOWS\system32\drivers\scsiscan.sys
and C:\WINDOWS\system32\NKSCUSD.dll

SCSI is both an electical protocol and a command protocol. The command protocol
can be sent over the SCSI electical protocol, Firewire, FibreChannel, SSA,USB, ATA (=IDE)
(essentially all ATA CD-ROMs run this way) and even around the world via the
internet. So don't discount something that mentions SCSI.

This is new to me. Until now I didn't know of "SCSI over Firewire", but
in German they say "Du wirst so alt wie eine Kuh und lernst immernoch
dazu" (You live as long as a cow and still lerns more).
Thanks for the clarification.

Have you checked Nikon's website for a newer driver?

Not until now, but I will now. In the past their answers to (unprecise)
problems was rather slow, if at all

Many thanks for the quick response!

Peter (he in the moor) Wagner

 

[Kennedy McEwen]

Hello to all,

I encountered the following Problem:

I'm running a Nikon LS-4000 ED IEEE 1394 SBP2 Device (So calls Windows
Hardware Assistent the device) until now on a W98SE-System without
problems.
As far as I remember, also *without any* troubles when installing some
years ago.

Now I will change to a faster W2K based System and run into trouble:
The device is physically connected. Windows recognizes as "other Device
(Yellow Questionmark) with the above mentionend name and searches for
Driver and (expectedly) finds none. Not in the W2K-CD, not in the
Nikon-provided CD.

The only hint I found in Google was some Forum about some SCSI-driver,
not very precise anyway. But this is a Firewire-device, so that makes no
sense for me.

Can anybody give some clear hint, which driver is needed and where I
will find it.

In Bill Gates' infinite wisdom, Microsoft shipped Windows 2K with built
in Firewire support but without the ASPI layer that most legacy hardware
required.

Installing this driver should do the trick:
http://download.adaptec.com/software_pc/aspi/aspi_471a2.exe

 

[peter wagner]

Hello to all,

I encountered the following Problem:

I'm running a Nikon LS-4000 ED IEEE 1394 SBP2 Device (So calls Windows
....

First the good It's working at last.

<OT: Best RPG Adventure game is OS-tinkering. so some windows-user said.
<\OT>

For the record and for others with similar problems, here is what I
experienced (Errors and byways included):

First, from Chuck I knew, SCSI is an issue. But I have a working
SCSI-disk-system, so that was probablly not the issue.

Hardware-assistent told:Coolscan detected, drivers installed.
Devicemanager told: Device existent, driver NOT installed: Error31.
(This device depends upon another device, that is not or not properly
installed. No name, no hint.)

I poked around at many places. Somebody on some forum mentioned, a Nikon
support-member telling to delete (where?) all oem*.inf-files.

I Found an older NikonScan-CD WITH drivers and inf-files (Separate ones
for each OS)

Poking in the inf-files I guessed, there is involved a"device" sti or
stimon (still image monitor ?)
and there should be some sti*.sys -files in \winnt/system32\drivers\.
there were none.

By the way: this non-exact parttime guessing is because I'm not a
systemsprogrammer nor developer, only user since the nineties, but
sometimes guessing works.

Then Kennedy told of aspiinst.exe, which i downloade & installed. No
Errors, but no success either.

This noon I connected Nikon Support (they were down over the weekend):
They emphasize on finding the "correct" driver; in unclear words they
speak of the "possibility of installing a *.me-driver.

so I looked into details:
- Windows found and installed a oem11.inf, which is a Coolscan 4000, but
with no identifikation of target-OS, and which apperently does not
install any drivers.

On the NikonScanCD there are inf-files separately for each OS.
So I forced the hardware-assistent to search the new driver there and
BINGO! it worked.


Conclusion and why I wrote this lengthy history:

1: Thanks to you both for your tips. Even when they didn't shoot the
problem point-blank, anyway they made sure:
- a: it can be done and
- b: if not in this way, then there IS another way.

2: With unresolved problems:
- a: Make sure, they CAN be solved (thanks, Chuck!)
- b. Get as much opinions, facts, rumors from as much sources as
possible.
- c: Boil them down to THOSE facts, that belong to YOUR problem. Here
comes your help, Kennedy: I could be sure, that SCSI was NOT my problem.
..



Many thanks to both of you!

Peter (he in the moor) Wagner