I finally got around to upgrading from CNX 2.1 to 2.2 and I have immediately started to get an error when opening the Quick Fix adjustment in the develop section. The sliders are missing from the histogram and there is a red "x" in their place.

There was a post on what appears to be the same error in this topic: http://www.nikonians.org/forums/dcboard.php?az=set_threaded_mode&forum=196&topic_id=54820&prev_page=show_topic&gid=54820#54878 However, it doesn't look like there was a solution. Does anyone have any suggestions before I re-install 2.1.1?


Here are the details:

I am running Windows XP Home SP3 and version 3.5 SP1 of the .NET framework. I have 1GB of RAM in an older desktop, but it ran 2.1.1 fine (albeit a bit slowly sometimes)


Here are a couple of screen shots:







Here is the text of the error:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.OverflowException: Overflow error.
at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
at System.Drawing.Graphics.DrawImage(Image image, Rectangle destRect, Int32 srcX, Int32 srcY, Int32 srcWidth, Int32 srcHeight, GraphicsUnit srcUnit, ImageAttributes imageAttrs, DrawImageAbort callback, IntPtr callbackData)
at System.Drawing.Graphics.DrawImage(Image image, Rectangle destRect, Int32 srcX, Int32 srcY, Int32 srcWidth, Int32 srcHeight, GraphicsUnit srcUnit, ImageAttributes imageAttr, DrawImageAbort callback)
at System.Drawing.Graphics.DrawImage(Image image, Rectangle destRect, Int32 srcX, Int32 srcY, Int32 srcWidth, Int32 srcHeight, GraphicsUnit srcUnit, ImageAttributes imageAttr)
at System.Windows.Forms.ControlPaint.DrawImageDisabled(Graphics graphics, Image image, Rectangle imageBounds, Color background, Boolean unscaledImage)
at System.Windows.Forms.ControlPaint.DrawImageDisabled(Graphics graphics, Image image, Int32 x, Int32 y, Color background)
at nik.Windows.Forms.LevelAndCurves.GradientSliderControl.OnPaint(PaintEventArgs e)
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Capture NX 2
Assembly Version: 2.2.0.31924
Win32 Version: 2, 2, 0, 0
CodeBase: file:///C:/Program%20Files/Nikon/Capture%20NX%202/Capture%20NX%202.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
NxController
Assembly Version: 2.2.0.27150
Win32 Version: 2.2.0.0
CodeBase: file:///C:/Program%20Files/Nikon/Capture%20NX%202/NxController.DLL
----------------------------------------
nik.GUIBase
Assembly Version: 2.2.0.31924
Win32 Version: 2.2.0.0
CodeBase: file:///C:/Program%20Files/Nikon/Capture%20NX%202/nik.GUIBase.DLL
----------------------------------------
GUI_Common_Managed
Assembly Version: 2.2.0.31924
Win32 Version:
CodeBase: file:///C:/Program%20Files/Nikon/Capture%20NX%202/GUI_Common_Managed.DLL
----------------------------------------
msvcm80
Assembly Version: 8.0.50727.3053
Win32 Version: 8.00.50727.3053
CodeBase: file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.3053_x-ww_b80fa8ca/msvcm80.dll
----------------------------------------
nik.Base
Assembly Version: 2.2.0.31924
Win32 Version: 2.2.0.0
CodeBase: file:///C:/Program%20Files/Nikon/Capture%20NX%202/nik.Base.DLL
----------------------------------------
nik.GUIBase.Resources
Assembly Version: 2.2.0.31924
Win32 Version:
CodeBase: file:///C:/Program%20Files/Nikon/Capture%20NX%202/nik.GUIBase.Resources.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
h7jlzbgs
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
zhjbagov
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
NxCursors
Assembly Version: 2.2.0.31924
Win32 Version: 2.2.0.0
CodeBase: file:///C:/Program%20Files/Nikon/Capture%20NX%202/NxCursors.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Bart
D300s D40 F3HP FE FM2n Nikkormat FTN

Everything is a subject. Every subject has a rhythm. To feel it is the raison d'être.
The photograph is a fixed moment of such a raison d'être, which lives on in itself.
- Andre Kertesz

My Nikonians Gallery

Visit my Nikonians gallery.

Attachment #1, (jpg file)
Attachment #2, (jpg file)

I had (have) exactly the same problem. We're certainly not the only ones! All XP updates, and those to .NET Framework 2 and 3.5, are in place. I rolled back to 2.1.1 with no problems.

Nikon said to uninstall completely and start over. I haven't tried that, yet. I thought I would see how many others were reporting problems in the hope of Nikon bringing out a fix. If everyone who's getting this problem reports to Nikon they might realise it's a significant issue, albeit not affecting everyone.

Other applications that are known to use .NET Framework are working fine.

It would be interesting to know whether this only affects users who have installed 2.2 over the top of 2.1 as I did (as opposed to installing "clean").

I'm sure I saw something (here) referring to 2.2.1, but it's certainly not on the UK download site.

John Gruffydd
Mold, Wales, UK
D300, D200, OM1, OM2n, Bronica ETRSi, Lumix LX5

John,

Glad to hear I am not alone. How much RAM did you have when you experienced this problem. Nikon Tech Support just sent me what appears to be a pat response saying I don't have enough memory to run NX2.

I informed them that the Nikon website states 769MB is the minimum with 1GB or more recommended. We'll see what they say...

Bart
D300s D40 F3HP FE FM2n Nikkormat FTN

Everything is a subject. Every subject has a rhythm. To feel it is the raison d'être.
The photograph is a fixed moment of such a raison d'être, which lives on in itself.
- Andre Kertesz

My Nikonians Gallery

Visit my Nikonians gallery.

Here's an update with the response I received rorm Nikon USA tech support after I posed the original question to them and sent them the same screen shots.

Here is their initial reply:

Hello,

Thank you very much for your inquiry we are sorry for all issues, but you do need more memory in the computer to be able to run this software.

Thank you.

This response did not seem very well considered to me. I had the feeling it was more about clearing the rep's queue, so I responded:

I do not find this to be a very considered response given that the Nikon USA web site ( http://www.nikonusa.com/Find-Your-Nikon/Product/Imaging-Software/25385/Capture-NX-2.html ) stated the following on the Tech Specs tab for NX2:

RAM (Memory) 768 MB minimum (1 GB or more recommended)

Their reply now seems a bit patronizing to me:

Thank you very much for your very reasonable response, I am glad you could notice all of the software specifications, however when we state that 768 MB are needed to run this application, we mean 768 MB Free, meaning that from the total amount of RAM memory available on your computer Capture NX 2 will require 768 MB. Eventually, your Windows XP along with other applications that are always running on your computer such as an Antivirus software, consumes part of the RAM memory and most likely would not leave enough for Capture NX 2.

This is why I strongly recommend you to upgrade the total RAM memory in your computer for improved performance.

I haven't pointed out that the section with memory requirements is named system requirements. Also, I would find it unlikely that the change from 2.1 to 2.2 would consume so much more memory as to put me over the top, given that my system would run 2.1 acceptably.

If I upgrade my memory and it doesn't fix the problem, wonder if they would reimburse me for the cost.

This is actually disappointing. Up to this point, my interactions with Nikon service have been stellar. Capture NX is wonderful software, but these kind of issues (and the less than spectacular response) are frustrating.

I just have a gut feeling that this issue is not memory-related. I am certainly overdue to upgrade my PC and at this point it makes better sense to put the money towards a new PC than it does to buy more RAM for my old one. Of course, the upgrade decision would mean a 64 bit version of Vista and that raises a bunch of different compatibility issues with NX2 and drivers for printers, a scanner and my colorimeter.

For now the roll back to NX 2.1 is looking like the way to go...

Bart
D300s D40 F3HP FE FM2n Nikkormat FTN

Everything is a subject. Every subject has a rhythm. To feel it is the raison d'être.
The photograph is a fixed moment of such a raison d'être, which lives on in itself.
- Andre Kertesz

My Nikonians Gallery

Visit my Nikonians gallery.

>Here's an update with the response I received rorm Nikon USA
>tech support after I posed the original question to them and
>sent them the same screen shots.
>
>Here is their initial reply:
>
>Hello,
>
>Thank you very much for your inquiry we are sorry for all
>issues, but you do need more memory in the computer to be able
>to run this software.


>I haven't pointed out that the section with memory
>requirements is named system requirements. Also, I
>would find it unlikely that the change from 2.1 to 2.2 would
>consume so much more memory as to put me over the top, given
>that my system would run 2.1 acceptably.
>
I agree. FWIW I have 1G of system memory. I run a lot of fairly memory intensive software (including PS CS3) and have never, ever seen this error message before.

>I just have a gut feeling that this issue is not
>memory-related.

Agreed again.

>For now the roll back to NX 2.1 is looking like the way to
>go...

which is what I've done - working perfectly.

Cheers

John Gruffydd
Mold, Wales, UK
D300, D200, OM1, OM2n, Bronica ETRSi, Lumix LX5

John,

Thanks for the confirmation. Sounds like we had exactly the same issue. I just reloaded NX 2.1 and it is working perfectly for me, too. (In fact it seems a bit faster than before for some reason.) Guess I will have to ponder that P6000 purchase after a new computer...

For me, NX is kind of a "killer app" that really adds value to shooting digital with a Nikon. Jason's point in the most recent Image Doctors podcast about the P6000 leveraging existing (NX) workflow really got me to thinking about that camera (and hence made me think about updating to 2.2).

I hope some of this feedback finds its way to Nik and to Nikon. Either their tech support staff is just dispensing platitudes, or they need to examine updating the system requirements to reflect the memory required by the latest version. I tend to think it's the former.

Bart
D300s D40 F3HP FE FM2n Nikkormat FTN

Everything is a subject. Every subject has a rhythm. To feel it is the raison d'être.
The photograph is a fixed moment of such a raison d'être, which lives on in itself.
- Andre Kertesz

My Nikonians Gallery

Visit my Nikonians gallery.

>For me, NX is kind of a "killer app" that really
>adds value to shooting digital with a Nikon. Jason's point in
>the most recent Image Doctors podcast about the P6000
>leveraging existing (NX) workflow really got me to thinking
>about that camera (and hence made me think about updating to
>2.2).
>

ahhhhh... Me too! that P6000 is looking pretty good. I was looking at the Leica D-lux4 also... still not sure which way to go...

~Maura~

CT Nikonian
D-80

www.photographybymaura.com
www.flickr.com/photos/by_maura

When the Power of Love overcomes the Love of Power, our World will know PEACE.

A bit OT, but I'd suggest taking a look at the Panasonic Lumix LX3. I think it's basically the same camera as the Leica, but less expensive. FYI, there is a decent article in this month's Shutterbug comparing the G10, P6000 and LX3.

Hope you find a good "high end" P&S...

Bart
D300s D40 F3HP FE FM2n Nikkormat FTN

Everything is a subject. Every subject has a rhythm. To feel it is the raison d'être.
The photograph is a fixed moment of such a raison d'être, which lives on in itself.
- Andre Kertesz

My Nikonians Gallery

Visit my Nikonians gallery.

ahhhhh... Me too! that P6000 is looking pretty good. I was
>looking at the Leica D-lux4 also... still not sure which way
>to go...
>
>~Maura~

Hi Maura,

Sadly, the P6000 is pretty terrible...simply not in a class with the others. Took one for a week, and happily returned it...Nikon has yet to get a serious P&S right.

Always being on the hunt for a compact that I would enjoy, I have gone through a bunch. Got the G10 when it came out, not bad but too big to be called compact, and lousy low light performance.

I bought the Panasonic LX3 in January, liked it much more than the G10 both size, lens and low light performance... then just 2 months later after borrowing one from a friend, I switched to the Leica D-LUX4. The switch was simple, the jpegs coming from the D-LUX4 are demonstrably better than those from the LX3, hands down. Leica's firmware made a great difference.

Plus since Leica dropped its price from $849 to $699, and my dealer discounted it to $649 the difference in cost between the LX3 is $149. I get a better warranty (2 years instead of 90 days), and a $100 Capture One license with the Leica. Plus, Leica always holds value like no other company, so when the next great compact arrives I will be able to recoup some money here.

Check out some really impressive D-LUX4 work from Jim Radcliffe at http://www.boxedlight.com/dlux4/. Killer stuff.

I find the images really impressive, and the f2 24mm lens combined
with a larger 10MP sensor makes this the best compact I have tried in
available light. I applaud how Leica/Panasonic are rebelling against
the megapixel race, staying with the same number of pixels as last
year and increasing photosite size and lens speed.

Plus...believe it or not the D-LUX4 will use my Nikon SB-600 and
SB-800s in M or A mode, and sync, GET THIS...up to the max shutter
speed of 1/2000th. I had not read that tidbit anywhere else.

Bottom line, after trying the P6000 (sorry Nikon), owning the G10, the LX3 and the D-LUX4, IMHO the D-LUX4 is the best compact camera out there today. The f2 lens is amazing, the camera is comfortable and has all the features a serious photographer needs when I don't want to tote my D3 or D300 and pounds of kit. It is with me at all times.


Sincerely,

K. J. Doyle

I'm happy with my P6000 now that I can open NRW files in Capture NX2.

I agree, it might not be the *best*, but no P&S offers anywhere near the quality of our DSLRs. I also enjoyed using the GPS function as a way to geotag my D3 images with Photo Mechanic. The little GPS in the P6000 is quite accurate!

-Jason

Jason P. Odell
Colorado Nikonian
Author, The Photographer's Guide to Capture NX2

Join me online for Capture NX training!

www.luminescentphoto.com

Read my blog

Listen to The Image Doctors

>however when we state that 768 MB are needed to run this
>application, we mean 768 MB Free, meaning that from the total
>amount of RAM memory available on your computer Capture NX 2
>will require 768 MB.

This is hilarious and evidence of a disconnect between the software author at Nik and photographers using NX2. Expecting users to discern how much physical memory is installed in their computer is at the knowledge limits of many users. Expecting users to understand how much physical memory is free, I suppose on average, when the OS and resident apps are loaded is a big stretch. If one looks at the XP performance monitor, one sees parameters such as physical memory, page file usage history, system cache stats, kernel memory stats, etc. I don't think photographers using NX2 should have to try understand all of that.

>would find it unlikely that the change from 2.1 to 2.2 would
>consume so much more memory as to put me over the top, given
>that my system would run 2.1 acceptably.

Well, I wouldn't be too quick to assume that because 2.2 is supposedly a performance improvement release,. no? That means the authors may have improved how the internal image data arrays are manged, memory management algorithms, perhaps less use of disk cache and more of physical memory to manipulate images, perhaps more frequent instances of the image in raw format in physical memory for faster processing, etc. All of these could increase the need for physical memory in order to implement speed ups.

Cheers,
Peter

>

>
>This is hilarious and evidence of a disconnect between the
>software author at Nik and photographers using NX2. Expecting
>users to discern how much physical memory is installed in
>their computer is at the knowledge limits of many users.
>Expecting users to understand how much physical memory is
>free, I suppose on average, when the OS and resident apps are
>loaded is a big stretch. If one looks at the XP performance
>monitor, one sees parameters such as physical memory, page
>file usage history, system cache stats, kernel memory stats,
>etc. I don't think photographers using NX2 should have to
>try understand all of that.
>

Quite! Also, I find it hard to believe that I can run PS CS3 with several images open *and* other programs running at the same time, yet NX2.2 *alone* crashes out. Luckily for me, I already had a stable version of NX2 that I could revert to. I feel very sorry for anyone who's paid well over £100 for this program from scratch and then finds it won't work.

I think it's rather naughty of Nikon (and they're not alone) to have withdrawn earlier versions for sale or download before ensuring that the latest version is stable and will run on the specified equipment without problems, especially when those earlier versions have run fine on those computers that won't run the latest version. In any case, when you take a "minor version upgrade" (which is what this is) who actually looks at the system specs again? I certainly didn't! And there was certainly no "health warning" on Nikon's website that this minor upgrade needed a substantial upgrade to the computer to run it.

John Gruffydd
Mold, Wales, UK
D300, D200, OM1, OM2n, Bronica ETRSi, Lumix LX5

Peter,

Thanks for the confirmation that I'm not the crazy one with respect to iterpreting system requirements.

You raise a good point about the possible change memory requirements with the new version. After doing some web browsing on the topic, it seems to be a bit of theme that NX 2.2 does some weird things with managing memory. If there has been a significant increase in memory requirements, they should update the system requirements on their web site (and keep the older. less memory intensive version available for download).

John,

I guess we can only hope they address some of these issues in 2.3...

Bart
D300s D40 F3HP FE FM2n Nikkormat FTN

Everything is a subject. Every subject has a rhythm. To feel it is the raison d'être.
The photograph is a fixed moment of such a raison d'être, which lives on in itself.
- Andre Kertesz

My Nikonians Gallery

Visit my Nikonians gallery.

Did you upgrade from 2.1 to 2.1.1 to 2.2? If you did not that may be your problem. You must do the upgrade incrementally.

Bob Baldassano
My Nikonians Gallery

"Nikonians membership - My most important photographic investment, after the
camera"

Retirement is a gift of time - Don't waste it!

Bob,

I double checked an it looks like my prior version was (is) 2.1.0. However, I swear I did update to 2.1.1 prior to trying 2.2.0 (perhaps I just didn't keep the executable).

I will install the 2.1.1 update (it's still on the Nikon USA website), but I'm not sure if I have the patience right now to try 2.2 again...

Thanks for the great insight!

Bart
D300s D40 F3HP FE FM2n Nikkormat FTN

Everything is a subject. Every subject has a rhythm. To feel it is the raison d'être.
The photograph is a fixed moment of such a raison d'être, which lives on in itself.
- Andre Kertesz

My Nikonians Gallery

Visit my Nikonians gallery.

I have the same issue with version 2.2.0 on a Windows XP Professional with service pack 3 and 2GB RAM. I installed the CD, which is version 2.0.0 and it works fine. When I update to version 2.2.0 using the update file from Nikon I have the problem. I have not gone through all the updates because I can fine one for version 2.1.0.

I also tried the 60 day trial download, which is version 2.2.0 and have the same probelm. I think Nikon has major problem with this update, at least for an XP machine.

I contacted Nikon support, but no positive results yet. They ask for a system symmary report, but I have been unable to get their system to accept it. I am waiting for new instructions.

Visit my Nikonians gallery.

It would be interesting to find out if:

(1) Anyone with (say) 1 GB of *actual* RAM is using v.2.2.0 successfully

and/or

(2) Anyone with 2GB or more of actual RAM is getting overflow errors.

What really annoys is that Nikon *seem* to be saying that 2.2 needs significantly more resources that 2.1 and earlier, yet they must have known that people have run those earlier versions without problems and then release an "upgrade" (not a completely new version) that now doesn't work for a significant number of people.

John

John Gruffydd
Mold, Wales, UK
D300, D200, OM1, OM2n, Bronica ETRSi, Lumix LX5

Just seen this on one of the DP Review forums:

"I am having problems with version 2.2.0 on a Windows XP Professional computer that has 2GB RAM. I can only make one change in the image and when I try another slider I get an ERROR message - An unhandled exception has occured and have the option to click Continue or Close - overflow problem. If I click Continue I just get the message again after I attempt another edit. Version 2.0.0 works without any problems."

So if it *does* occur on a computer with 2GB of RAM, there must be more to the problem than Nikon will admit.

John Gruffydd
Mold, Wales, UK
D300, D200, OM1, OM2n, Bronica ETRSi, Lumix LX5

>It would be interesting to find out if:
>
>(2) Anyone with 2GB or more of actual RAM is getting overflow
>errors.

I'm running WinXP w/ 4Gigs installed (3.25 recognized) and had all kinds of problems with v. 2.2.0 as documented at http://www.dpreview.com/forums/read.asp?forum=1039&message=31990916. I finally said enough, and went back to v. 2.1.1; all problems solved ...

Ron, what processor are you using - AMD or Intel?

Visit my Nikonians gallery.

>Ron, what processor are you using - AMD or Intel?

I have a Intel P4 processor (3.4 MHz) ..

I heard over at DPReview that Nikon told a guy with v. 2.2.0 "problems" that it was due to his AMD processor ..

Maybe Nikon is getting off the "not enough memory" horse but it seems like they still refuse to admit that just maybe it might be the software .. ??

John,

Running 3 gig of Ram. On a Quad Vista 32 and NX 2.2 will not work.. same error. Funny it runs fine on my XP laptop with only 1 gig of ram.

Nikon as been no help.... just lurking around here hoping some figures it out. Or the next upgrade comes. Till then, I'm back to using NX 2.1

Also... problem is on a machine with a RADEON video card and driver... is that in common with others having the issue?

John,

I was having problems with v2.2.0 on both my desktop pc and laptop. Emailing Nikon tech support resulted in me being told I need more RAM or to go back to 2.1.1.

Chatting to a number of fellow shutterbugs one evening I found that 2.2.0 appears to have memory problems. As a result I upped the memory in my PC to 2GB (max for the mobo), added a high speed SATA drive and re-installed the OS (Windows Vista Home Premium). Since then NX2 has been okay - no crashes and reasonable speed performance. CS4 Extended runs faster!

I've also upped the RAM in my laptop (IBM Thinkpad R31) to 1GB and although NX2 is running slow the only problem that it exhibits is not remembering my preferences settings - I have to reset them each time I open the app. A new laptop is on the cards

--------
Regards
Steve G

My Nikonians gallery

I have been following this thread for a while. I had not had problems with cnx2 2.2.0 for about 2 months. Running vista 64 bit wit 4 gb ram. Since getting back from the Nikonian Yosemite Spring workshop and processing a lot of images the stability of cnx2 started to be problematic. Some observations, even though I configured the temp drive location and cache location to be on my D: drive the files are still going onto the C: drive. The problem occurs when trying to open a raw file that has edits. The image opens with a message at the top "updating image". During this time a tmp file is being created in the c:\user\username\AppData\Local\Temp\cpnx_nnnn_tiledata\0000000000.tmp
which increases in size to 9-10 GB. If this much space is not available on the drive the program crashes similar as noted on this thread, if the space is available the file does open for editing, but it can take up to 10 minutes to get to this point even with lots of memory and a fast multiprocessor. I don't have the option of going back to cnx2 2.1 since I need to work with D3x images. When cnx2 is working, this is my primary image processing platform, but I need something that works and in stable (and not a memory hog). I don't understand why a 25 MB RAW file should need 9+ GB of temp space for processing!!! I will submit the issue to Nikon/NIK but the response in the past has been they don't support Vista 64 bit. Based on what I am seeing in this thread and other locations this appears to be a cnx2 2.2.0 issue, not a 64 bit OS issue.



DJM

http://shepartphotography.smugmug.com/

Hello !

Same problem for me, win vista 64 bit with 8 gig of ram and a intel quad 2,66 ghz processor, a fast radeon x1900 graphic card with 512 mb working fine for photoshop cs4. After upgrading to nx2.2 the problems started with not enough ram messages after working on 2-5 files normaly. then i had to quit the programm and restart it. Have installed framework, nikon libraries and all the stuff i could think of related to nx2, but did not improve. A day ago vista 64 bit had a major upgrade, funny my first session afterwards with nx2 i could work on 20 D3x files in a row with no problem. But the next session i was back at 2-5 files. Makes me angry. Reply from Nikon was first the unfriendly "do not support 64 bit systems", then after pointing out that I am an NPS member and do not have the time for fooling around, they suggested a clean install - which i tried but did not help. I like nx2, as the u point technology is really saving my day, I can do 90 % of my work in nx2 and have it saved together with my nef file. Cs4 is not bad either, but I found for me nx2 suits me better.
the problem here is tech support for nx2 which is a joke in my opinnion. Not supporting 64 bit systems - lets see if we can use in a few month nx2 still when win 7 is out-or will the reply then be "sorry we do not support new win systems - just to lazy to do the work" and the money we have got from you already so why bother ?
It is a little similar to the fact that nikon is not providing 64 bit drivers for their nikon coolscan 9000 scanner - just not doing it. a nice guy then wrote his own driver and offered it for free (based on vuescan who have a 64 bit driver for the nikon 9000)Works fine now.

Sad that Nikon is treating her good customers like that - they have great gear, but software support should improve. Support here in Austria for camera and lens stuff via NPS is actually great - nice helpfull people there.

Christian

Visit my Nikonians gallery.

Did some more testing today. A raw file (D3x, 14 bit, lossless compressed ~ 25 MB) initally opened quickly in CNX2. The file was edited (Auto Retouch, Pro Contrast (NIX CEP 3), Color control point, Auto Retouch) and saved. When I tried to open the file again (now ~ 41 MB) it took 10-20 min to open. During this time a ~16 GB temp file was created. As soon as I try to do anything else the program crashes (out of memory). If I try to open the same edited file that was saved as a TIF file (~ 140 MB) no problems. Thus the problem appears to be how Capture NX2 (2.2.0) is handling edited RAW files. Just to confirm that this is not a Vista 64 problem, I tried to open the same RAW file on a Windows XP system. Observed the same problem including the creation of a ~16 GB temp file. The whole reason for using Capture NX2 where multiple edited versions of the same raw file are saved in the same file is now not usable. Since I am working with a D3x, I can't go back to Capture NX 2.1.0 unless I only work with ~140 MB tif files, and save a separate file for each edit. ARRG!!!!

DJM

http://shepartphotography.smugmug.com/

Doing my monthly searches for a NX2.2 fix I ran across this thread. It seems that (at least with Vista 32), Vista has a special directory which contains all the .dll's and you can have multiple dlls with the same name but for different apps.

The thread also talks about deleting the File "application.cfg" in the "...\Nikon\Capture NX 2\" Folder.

I have not tried either, as I just reinstalled NX2.1 (again for the third time) as it seems once a month I try something.. install NX 2.2 to test if it's working. It's not, so I reinstall 2.1

May try this fix next month... but if this does help anyone.. please post your results.

The thread:
http://forums.dpreview.com/forums/read.asp?forum=1039&message=32318415&changemode=1

-----
Ez
http://www.myworldphotos.com/