Buggy Nikon Capture 3 software

when it crashes doe you get the little dialog box pop up that lets you click on a link for more information ?? then you can see the DLL that caused the crash . it might not be a nc3 problem but rather a nc3 and another program together.

John Swenson said:

Nikon Capture3 is just not fully debugged. It's beta software that
Nikon rushed out too early as the final version.

Baywing said:

John Swenson said:

The Nikon Cature 3.00 trial software that came with my D100 has a
serious bug that can cause NC3 to freeze when saving .NEF files on
Windows.

I've tried NC3 on three separate Windows XP PCs and it has locked
up on me on all three when saving NEF files that I have edited.
What's so bad is it locks up the entire PC (forcing a hard reboot),
not just NC3!

Maybe this is why Nikon still has not released NC3 in the U.S. (I
can't find it available yet anywhere).

Has anyone else had a problem with NC3 freezing their PC after they
edit a NEF file and then try to save the file?

I am certain this is a software bug in Nikon Capture 3.00 and not
Windows XP. NC3 is the only one of dozens of Windows apps I use
that freezes like this on any of the Windows XP computers I have.

I called Nikon tech support to complain, but got a customer service
rep who seemed confused about my complaint, and refused to escalate
me to their Level 2 support.

Until Nikon fixes NC3, IMHO it is unusable for Windows XP users.

John Swenson

Click to expand...

Click to expand...

Click to expand...

NC3 doesn't crash on my Windows XP PCs -- it freezes. This is the same problem reported by two other people on this thread. Probably a severe software conflict caused by programming errors by Nikon's developers.

3eyefish said:

when it crashes doe you get the little dialog box pop up that lets
you click on a link for more information ?? then you can see the
DLL that caused the crash . it might not be a nc3 problem but
rather a nc3 and another program together.

Click to expand...

I'm a Windows software developer (for a large software company, not for Nikon) and, time permitting, would be willing to take a look at the freeze problem. I don't currently have a copy of the Nikon software or a NEF file to run it against (waiting on my D100) but if the problem is reproducible with the trial version of the software and somebody could send me a NEF file and describe the exact steps to reproduce, I'll download the trial software and give it a look. I might not be able to tell much without debugging information from Nikon but you never know.

Not to be defensive (and I don't know how much Nikon tests their software) but you might be surprised at how much software can be tested on various versions of various operating systems on various hardware and yet problems still surface after release. The product I develop is tested by 20 or more people all day, every day for months on every conceivable combination of hardware and software and problems found are fixed yet new problems still crop up after release. There's just an infinite number of conditions under which software may run and be used so you can't possibly try them all.

rjackb

well it still might not be the nc3 software, could be a erratic driver . another service that is running might also be the cause..

how about trying to start in safe mode and trying to run it ?

John Swenson said:

3eyefish said:

when it crashes doe you get the little dialog box pop up that lets
you click on a link for more information ?? then you can see the
DLL that caused the crash . it might not be a nc3 problem but
rather a nc3 and another program together.

Click to expand...

Click to expand...

Hi

Member said:

NC3 doesn't crash on my Windows XP PCs -- it freezes. This is the
same problem reported by two other people on this thread. Probably
a severe software conflict caused by programming errors by Nikon's
developers.

Click to expand...

I am not too sure wether NC3 is the only problem... I found the XP explorer behaving strange some times too... not really crashing but restarting after a strange message... Maybe there is a conflict when NC3 accesses memory or swap-files...?

Regards, A. Schiele.