I have an LS-30 scanner that -- before it broke -- worked fine with Vuescan.
However, NikonScan 3.1.2 will not run. When I try to start it, I get to the
"splash" screen, and then it freezes. The whole system comes to a crawl,
and looking at the running processes I see that 100% of the CPU is being
used. My only recourse is to restart the system. (Windows XP Pro)

I have uninstalled NikonScan, cleaned the registry using Regsweeper
(supplied by Nikon), and reinstalled. Same problem as before. Any
suggestions on how to get NikonScan software to work on my Windows XP Pro
system?

I read on the Nikon Tech site that ONLY certain files should be installed
for the
ASPI layer. I found all the files on my PC. Two are OK (wowpost.exe and
winaspi.dll), and two (aspi32.sys and wnaspi32.dll) are a later version
(4.71.1.0 instead of 4.7). Is this part of the problem with NikonScan?

The LS-2000 comes into play because I received today a new one
purchased from an individual who *never* used it - so it is brand new in
the box! I don't know what firmware will be installed, and there is a
possibility
I may need to upgrade to the latest (1.3.1). From the instructions with the
firmware update, it says that I need to have NikonScan working before I can
update the firmware.

Anyone been down this path? Any words of warning or suggestions? And BTW,
how will I know what firmware is installed on the scanner?

More info:

When I terminate the application of NS 3.1.2 (Ctl-Alt-Del), Windows
generates an error message and offers to send a report to Microsoft. Here
is the contents of the report:

C:\DOCUME~1\Craig\LOCALS~1\Temp\WERb622.dir00\Niko n Scan.exe.mdmp
C:\DOCUME~1\Craig\LOCALS~1\Temp\WERb622.dir00\appc ompat.txt

How would these temp files be involved in my problem? Also there is no such
directory (folder) and no such files on my computer.


Thanks,
Craig

Breaking news: The CD that came with the scanner from Nikon has ASPI
version 4.71, so I guess that answers one of my questions.

Craig

On Tue, 25 Jul 2006 00:26:44 GMT, "Williams" <cwillyATE@wahoo.com>
wrote:

I don't run XP but I remember reading here that XP has - shall we say
- "difficulties" with SCSI devices. Apparently you need to install the
drivers manually.

So I suspect that's the problem rather than NikonScan.

From my notes I see there's a Microsoft Knowledge Base article about
all this so check that out as well:
Q300674

You probably know this but, after connecting the scanner and powering
it up, try first the Device Manager in System Properties (or the
whatever the XP equivalent is called) to see if the scanner is
recognized by the system.

Make sure you get the latest ASPI drivers from:
www.adaptec.com
I believe (but don't know this for a fact) that the latest version is
4.7. Since you're have 4.71 on the CD, that should be OK.

Just to make sure run the ASPI check utility included in the package:
aspichk.exe.

Anyway, at least you're running the latest NikonScan (3.1.2) for the
device . As you also point out it's essential to upgrade the firmware
before you start using the scanner because NS 3.1.2 needs the firmware
to be at least 1.3.

I believe that's shown in the main Window title bar (when you run NS
stand alone). If I remember correctly, it shows where the scanner is
connected and the firmware version.

BTW, there's a very good "secret" NikonScan 3 manual at:

http://support.nikontech.com/cgi-bin...ted=1056464188

This didn't work for me so I found it at:

ftp://ftp.nikon-euro.com/DOWNLOAD/NScan3/ns3rmena1.pdf

Definitely get this manual because it's far better than anything I got
with my LS-30 on the CD way back when (I've since moved on to the
LS-50).

Don.

Thanks for the tips. The scanner was working fine with VueScan - which
means the ASPI files were OK with XP. The scanner showed as "working
properly" in Device Manager. The problem is when I try to run
NikonScan.


Thanks for the link.

Craig

My "new" scanner works just fine with VueScan. But I cannot get NikonScan 3
to run. As I previously posted, it just locks up at the splash screen. Any
suggestions?

Craig

On 25 Jul 2006 09:05:39 -0700, cwilly8@yahoo.com wrote:

Not really, because VueScan bypasses the OS and talks to SCSI
directly. In other words, VueScan doesn't need the ASPI layer. I
believe the author changed this for some scanners later on (Canon
Lide, if memory serves) but Nikons are accessed by VueScan directly.

That's good! So, you're half-way there. Any luck after reinstalling
the new version (after using RegCleaner as you point out in original
message)?

BTW, try searching the archives of this newsgroup as well because I've
seen this (XP <-> SCSI) problem come up every now and then.

Don.

Thanks, Don. It's off to the archives!


"Don" <phoney.email@yahoo.com> wrote in message
news:s2efc2p3qnfktf42fi3bk3jjafv282757r@4ax.com...

And to clarify my last posting, VueScan uses the ASPI
layer if it's installed or the Windows Still Imaging interface,
which is set up with the scanners.inf file that's included
with VueScan.

NikonScan will also work with the scanners.inf file
that's included with VueScan, so ASPI isn't needed
for NikonScan to work.

Don

"Don" <phoney.email@yahoo.com> wrote in message
news:s2efc2p3qnfktf42fi3bk3jjafv282757r@4ax.com...

I found another guy who had identical problems with Nikon Scan (about 3
years ago). He ended up reinstalling Windows, and then it worked, but was
still "quirky." I've been in touch with Nikon Tech Support, but I really
don't have high hopes for such an old version.

Craig

"Don" <phoney.email@yahoo.com> wrote in message
news:12chvihbuh92df1@news.supernews.com...

Have you got the solution yet?

If not see if you can get in touch with Bob from Arizona or mail me
personally.

There are chances you'll get to get it to work again. Not "quirky".

Peter


Williams wrote: