Cary, NS 3.1 is not even remotely crash happy on my PC (Windows 98 normal
version) so your assertion that single CPU is as bad as SMP is wrong. It
runs for days without crashing (8 hour scanning sessions in which NS is open
I am happy to acknowledge, though, that I was unfair to you, before, with
respect to NS 3.x and dual-processor W2K crashes. I had suggested a while
back that you had a duff install of "something". Evidence from peeps on
this list clearly shows I was wrong in that respect.
But 3.1 for us "normal" peeps (single processor crowd!) is really solid.
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com]On Behalf Of Enoch's Vision,
> Inc. (Cary Enoch R...)
> Sent: 05 October 2001 22:47
> To: firstname.lastname@example.org
> Subject: Re: filmscanners: Nikonscan and dual processors
> In Win2K it's simple to set an application to use just one processor by
> using Task Manager. Right-click on the application name in the
> process list
> and select Processor Affinity. However, I've done this with NS 3.1 and it
> makes no difference whatsoever. All that the message from Nikon
> tells me is
> that they're clueless or that they vaguely suspect that their
> multithreading is less than optimal. They really need to hire
> development people instead of those high school interns they're using.
> Perhaps they should make an offer to Ed Hamrick that he can't refuse;-)
> Everyone knows that NS crashes just as readily on a single CPU as it does
> on an SMP system.
> Cary Enoch Reinstein aka Enoch's Vision, Inc., Peach County, Georgia
> http://www.enochsvision.com/, http://www.bahaivision.com/ -- "Behind all
> these manifestations is the one radiance, which shines through
> all things.
> The function of art is to reveal this radiance through the
> created object."
> ~Joseph Campbell