Sorry, I should have been clearer:
The *application* is crashing, not Windows. Tracebacks of the application's
crash show that it is failing mostly in kernel level code, which often indicates
a driver problem (it is rare for applications to crash in kernel code
rather than in the application code). The OS continues to run fine.
I did try reinstalling the Firewire drivers. VueScan runs with on the scanner.
I am doing further testing, with three different W2K dual CPU machines,
loaded from scratch with clean OS's, to try and pin down the problem.
Other than one report from Tom Scale (not sure if he is using single
or dual CPU), there has been NOT ONE person reporting that NikonScan 3.1
works without crashing under W2K / dual CPU.
I'll summarize back to the list in a week or so.
Regards
Stuart
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED]
Sent: Friday, October 05, 2001 3:52 PM
To: [EMAIL PROTECTED]
Subject: Re: filmscanners: Nikon Scan 3.1 / Windows 2000: Could not
open Nikon Scan 3...
In a message dated 10/5/2001 9:47:50 AM EST, [EMAIL PROTECTED]
writes:
P.S. I've tried to start VueScan 7.1.20, but that one causes Windows to
re-start
immediately during startup..
If Windows 2000 crashes, the problem is (by definition) with something
in the kernel. Even the most poorly behaving application should be
unable to crash a Windows 2000 system.
You might try re-installing the driver for the Firewire card, since this
is the most likely problem area.
Regards,
Ed Hamrick
