SOLUTION: Windows XP SP2 and Nikon Software

K

Ken-L

Guest
I found this in a Google search and it might be helpful for those with a problem.

This is from: "Michael Howard's Web Log
A Simple Software Security Guy at Microsoft!"


Windows XP SP2 and Nikon Software
Last night I bought a shiny new PC for home; it's based on an AMD Athlon 64 FX, with 2x160Gb SATA RAID-0 drives, 1Gig of RAM and an nVidia GeForce 6800 Ultra. It's pretty quick :)

I got the AMD Athlon CPU primarily for the Data Execution Protection support.

I then set about installing a whole bunch o' software: Office 2003 (it took 4mins 23secs to install! I'm serious!), Virtual PC, Visual Studio "Whidbey", PhotoShop CS, CA eTrust antivirus software, Acrobat, some "network analysis" tools :), a couple of games (I don't play games much - I just want to see what the video card is capable of! Well, that's my excuse, and I'm sticking to it,) print drivers (Canon i9100 and Kodak Pro 8500,) and a whole bunch of other things, including the software for my camera, a Nikon D100.

Anyway - everything runs fine, except the Nikon software; Nikon Capture 4.x and Nikon View 6.x. Looks like this code has a couple of issues which are caught by DEP. The remedy is easy, just add these processes to the DEP exception list, and then the apps run nicely. Read this for more info: "You receive a "Data Execution Prevention" error message in Windows XP Service Pack 2" at http://support.microsoft.com/default.aspx?scid=kb;en-us;875351

I take my hat off to the Windows shell guys - if a user mode app fails with a DEP failure, the exception list pops up, with the process in the list, you then just tick the process name, and voila, it's all done. I think this is a great usability enhancer; compare that with clicking the Start menu, right clicking My Computer, clicking properties, clicking Advanced, clicking Performance Settings, clicking the Data Execution Protection Tab and then finding the executable on the hard drive!

Good work, guys!

Now I need to have a chat with someone at Nikon to get this fixed so I can remove them from the exception list.

posted on Friday, August 20, 2004 10:24 AM by michael_HOWARD
 
Joined
May 15, 2005
Messages
1,827
Location
Israel
Real Name
Heiko
Hi again, Ken,

I don't have the AMD-64 (yet), but it sure is on my shopping list. I also heard about this problem, but didn't know this fix.

Unfortunately Nikon software - both NikonCapture and particularly NikonView - has quite some bugs and is not very stable. Did you ever try to view pictures in NikonView and go forth and back many times, including 100% views? NikonView creates dozens of .tmp files and one large one in your \Documents and Settings\yourname\Local Settings\Temp directory and eventually crashes. This happened to me on 3 different PCs and I'm already used to delete them manually (since NikonView usually forgets to delete them after a crash).

A friend of mine reported that he can't get the NikonCapture update to run on his PC - makes me think that he may have an AMD-64. :roll:

I'm sure your post will help some people out of their missery.

Regards,
 
Joined
Jan 28, 2005
Messages
301
Location
Cary, NC
Ken,

Before seeing your post, I did a similar search to find a solution and came across the same thread. I rebuilt my PC over the weekend with an AMD Athlon FX-55 CPU (my first use of AMD) and discovered that Nikon Capture crashed the machine. So off I go into cyberspace to see if I had a unique problem or a common one. Seems that many are having the same problem. After making the modification to my system to disable DEP, Capture works fine.

Joe
 
Joined
May 15, 2005
Messages
1,827
Location
Israel
Real Name
Heiko
In my previous post I mentioned that a friend had also problems running Nikon Capture. It turned out that he has a Pentium P4 CPU with Hyperthreading, which also crashes NC.

Here a remedy:

http://forums.dpreview.com/forums/read.asp?forum=1021&message=13440909

Makes me wonder about Nikons software QA. Instead of wasting development time on a useless WB encryption, they should have done some more debugging and improve the speed.
 
Joined
Jan 29, 2005
Messages
2,761
Location
nowhere
Hyperthreading may actually slow computation-intensive programs with well-balanced threads. Intel also points that out.
 
Joined
May 7, 2005
Messages
241
Location
Louisiana
I'm running Capture with DEP disabled also. I'm running a Dual 244 opteron system. I had did have a problem with installing Capture. I had an original copy of capture 4.0. When I installed it on my new machine it blue screened when I tried to run it. The resolution according to nikon was is run the 4.2 update. However the new version has a new type of registration key. I could not run the 4.0 version to register it and when I did the 4.2 update it asked for a new key to which mine did not work.
After calling tech support and going through a series of removing and reinstalling capture in safe mode and downloading the new security software from another site it still asked me for the new key after running the 4.2 update. The tech told me to fax a copy of the registration and a copy of the recipt and they would send me a fixed copy. Sure enough 4 days later I got a cd of capture 4.2 with my original key already encoded in the software.

I can't wait to see what is resolved/new problems in the 4.3 update coming this month.
Larry
 
K

Ken-L

Guest
oooh, a new version? I can hardly wait.....maybe it will give me an excuse to get a new system.....but I was hoping I could wait until "Longhorn" was shipping with new systems.....
 
Joined
May 7, 2005
Messages
241
Location
Louisiana
Ken,
4.3 is actually out. I saw it listed on Nikons to purchase. The trial/upgrade will be available within a week from what I've read. As far as specs of what's new I haven't found any of that yet.
Larry
 
Links on this page may be to our affiliates. Sales through affiliate links may benefit this site.
Nikon Cafe is a fan site and not associated with Nikon Corporation.
Forum post reactions by Twemoji: https://github.com/twitter/twemoji
Copyright © 2005-2019 Amin Forums, LLC
Top Bottom