RE: filmscanners: Nikon Coolscan iv ed trashes Windows 98SE

["Paul Graham" <peegee@btinternet.com>]

Sounds like you have been caught by excpetionally bad problems with NS 3.1
It is known to be more or less broken with W2K, (works but crashes
erratically) and with dual processor machines (yours?) The archive lists
many, many posts on the topic, I enclose one below. Supposedly 98 was much
more stable though.
If you are content with Vuescan then use it. It has better colour
management, you will get better results, but get no pretty histogram to play
with.
Otherwise hold your breath for 3.1.1 like the rest of us, which is a major
bug fixer, hopefully...

Paul

>>>

---Archive Message---

From: owner-filmscanners@halftone.co.uk
[mailto:owner-filmscanners@halftone.co.uk] On Behalf Of Stuart Nixon
Sent: 14 October 2001 18:39
To: filmscanners@halftone.co.uk
Subject: filmscanners: NikonScan 3.1 does not work under W2K (report on
tests)


Hi.

I am sure you are aware that people have reported NikonScan 3.1 is
unable to scan - especially batching multiple scans - without crashing.

SUMMARY:

With rare exceptions, NikonScan 3.1 crashes for Windows 2000 users.

My testing and feedback from other users has confirmed
that NikonScan 3.1 does not operate correctly under Windows 2000.
This software should never have been released in its current buggy state.

Please feel free to distribute this report to Nikon Japan, Europe
and USA technical support, and also to people who have performed
reviews of Nikon scanners.  Perhaps we can finally get Nikon to
get serious about fixing their software.


Background:

Some weeks ago I asked for feedback on running NikonScan 3.1
under Windows 2000.  Many people responded, and quite a few
were kind enough to provide additional feedback when I requested,
including Joe Blaze, Paul Graham, Bob Kehl, Tom Scales,
Charles Volkland and many others. Thank you.

A couple of people reported that NikonScan 3.1 never failed
for them.  There was no particular commonality on those systems that
worked - one was a fast AMD single CPU, and two others were slower
dual CPU Intel chips.  About the only interesting thing was that
two of the working systems did not use the Nikon supplied Firewire card.

Everyone else (about 80% of responses) reported that NikonScan 3.1
failed constantly for them under Windows 2000, for single or dual CPU
machines.  Most people reported having swapped to other products such
as VueScan (which incidentally is rock solid from what I have seen),
or if they really *had* to use NikonScan, ran it from within PhotoShop,
scanning a single photo at a time.  Because Photoshop restarts the
scanner software each time, this reduced the crashes to "only" 1 out 10
scans or so.



Ways to reduce NikonScan 3.1 crashes:

-       Use something else. If you are serious about bulk scanning,
        then basically NikonScan 3.1 is a waste of time unless you are
        one of those very rare & lucky people to have it run without crashing.
        VueScan and Silverfast are two alternative scanning products.

-       If you can, run Windows 98 on the scanner PC instead
        of W2K.  NikonScan seems more stable under W98.

-       Run a slower PC.  It is more stable on PCs less than 350Mhz or so.

-       Set the Temp drive *and* the scanner output location to a network
        drive. This will reduce NikonScan crashes by about 50%.  So if you
        are lucky, you might get 6 scans instead of 3 before it crashes.

-       On dual CPU machines, lock NikonScan to run in UniProcessor mode.
        This will reduce crashes somewhat.



Testing performed:

Given Nikon has been aware of these crash problems since NikonScan 3.0
and has not fixed them, I wanted to see if the problem could be pinned
down and perhaps a work around could be found.


My testing basically showed that for all configurations I could try,
NikonScan 3.1 is unstable.  I did manage to get it to batch scan 6 slides
just once without crashing. Big deal :-(

-       Coolscan 4000ED, using the Nikon supplied Firewire controller.

-       Three different Windows 2000 machines.  Each machine had 1GB RAM,
        IDE drives, and dual CPUs.  However, each machine had a different
        motherboard, and different CPUs. I tried ASUS, Intel and Tyan
        motherboards, and Intel P3, P4 and AMD Athlon MP CPUs. Each
        ran different nVidia cards (2's and 3's). I also tested
        against a 4th machine that had been heavily used for processing
        jobs that ran into CPU-weeks, and was known to be very stable.
        Machines were 733Mhz, 933Mhz and 1.2Ghz.
        Significantly, each machine had very different motherboards
        and add-on cards from different manufacturers.

-       Each machine was clean loaded within Windows 2000 Server.
        The latest motherboard/IDE/etc drivers were updated, then SP2,
        then the latest security patches.

-       Only Photoshop 6, and NikonScan was installed on each machine.
        No printers were installed (earlier versions of NikonScan
        had problems with different printers installed).

Testing was to simply run NikonScan stand alone, turn on ICE but
not GEM/ROC, and try and scan a 6 photo positive strip out to
TIFF files.

Before giving up in disgust, I tried various other combinations:

-       Forcing NikonScan to run on one CPU
        Result: Crashed less often (every instead of 3 slides)

-       Temp and output directories network not local:
        Result: Crashed a bit less often

-       Forcing scanner driver interrupts to a single CPU:
        Result: No difference, still crashes

-       Running Windows 2000 as a UniProcessor build (so only one CPU):
        Result: No difference, still crashes

-       Trying different NikonScan options (no rotate, no ICE, etc)
        Result: No difference, still crashes

I don't think there is much point in any more testing.  NikonScan 3.1
is broken, at least for me and most other people using Windows 2000,
and enough time has been wasted on it.

Please note that some people *have* reported that NikonScan runs
robustly for them (generally W98 users and some rare W2K users).
So NikonScan just might run for you.  If it does, the rest of
us would sure like to know what you did to make it run. Note
it will generally complete scanning for a single slide, especially
if used inside Photoshop - scanning multiple photos is where the
trouble starts.



Once again, I encourage distribution of this information to
Nikon people to try and get this software sorted out.


Apologies to the list for the length of this email.

Regards

Stuart


-----Original Message-----
From: owner-filmscanners@halftone.co.uk
[mailto:owner-filmscanners@halftone.co.uk]On Behalf Of Pete Cutter
Sent: 31 October 2001 15:02
To: scan
Subject: filmscanners: Nikon Coolscan iv ed trashes Windows 98SE


Hi,

I don't know if anyone has had a similar experience but I have had some
major problems with my Nikon Coolscan IV since I bought it.

It all started when I turned the scanner on one day (yes I know it was a
rash thing to do) and it caused a fatal exception error in Windows. When I
rebooted my machine, I had some kind of protection error, and could only
boot in safe mode.

I spent the rest of that night, and much of the following day, trying to get
it (and the rest of my machine) working again. I tried almost everything,
including uninstalling the Nikon Scan software, uninstalling my other USB
device (Epson 1270). I even went through the instructions on Microsoft's web
site for diagnosing boot problems step by step, removing all drivers and
startup programs until you find the cause of the problem.

Anyhow, after several long hours of this, I ended up reinstalling Windows
98SE completely. This fixed the problem, or at least fixed the boot problem,
So then I reinstalled my printer, and reinstalled Nikon Scan 3.1. I even
downloaded the latest firmware upgrade and applied it.

Then I fired up NS 3.1 and set about ACTUALLY SCANNING SOMETHING. I
carefully played around with all the preview settings, and when I was
finally ready, I hit the SCAN button. At which point Nikon Scan crashed and
started writing Dr Watson logs, and I gave up in disgust.

Of course I can still use the damn scanner because I was smart enough to buy
Vuescan some time ago, otherwise it would be a very fetching and expensive
doorstop.

Can anyone out there who has had similar problems throw any light on what
may be the problem now? Perhaps I should have avoided the firmware upgrade?
Does anyone know if it will run under Windows XP without screwing up the
entire USB setup and trampling other bits of the OS?

Actually the latest symptom is that Nikon Scan cannot even see the scanner,
although Vuescan still can.

Any help gratefully received ....

Pete Cutter
p.s. any news of Nikon Scan 3.2? or 4.0 even?