Hello Special People,

That's what it feels like. NX is barely functioning. I now have three unsolvable issues -- according to Nikon tech support:

1. Printing and file size. ALL files (NEF) print with a white border on the top and right sides. Regardless of the file size (unless I resize it), each NEF balloons to 272 MB -- from usually around 18 MB;

2. Slowness and non-responsiveness, which I know is a near universal problem;

3. AND this is the one I'm asking for your help, suggestions, observations. When I send a NEF to CS3 for touch up work, of course, NX converts the file to a TIFF. After I have finished in CS3 and saved the TIFF, I cannot open the newly saved TIFF in NX as it was saved in CS3. It opens as a contact sheet with 9 black and white images of the file. The TIFF does open as it should in CS3 and LR. NOW, the original NEF, untouched by CS3 of course, will not open in NX at all! It does open normally in CS3 and LR.

I have uninstalled and reinstalled NX several times, which has not changed anything.

Thank you so much for your wonderful help and ideas... always greatly appreciated,

Guy

A lot of times its other software or what other software does thats incompatible with other software like capture nx or view nx. . capture nx runs just fine on all my machines but view nx is another story. i cant get the slide show to run on my vista machine properly or my xp machine. after endless trying this and trying that im realizing since alot of other software is common to both machines it has to be that.

even starting view nx with all the other programs shut down dosnt help. the mere fact that something else that was installed altered something needed by view nx keeps it from running properly.


these kinds of problems end up being unique to just your system and unfortunetly no one can help with it

Visit:http://mm-photography.smugmug.com/Other

Hello mathjak107,

Thank you for your generous and thoughtful... but somewhat discouraging... response. I understand what you've written. Nikon has too. I've sent them two "snapshots" of my hard drives. Of course, this didn't identify conflicts, merely showed what was present. Nothing came of those revelations. I suppose the only way to uncover conflicts is to uninstall one program at a time and test the results.

Thanks so much again,

Guy

OK first off, which operating system are you using?

Visit my Nikonians gallery.

Hello Noel,

I am running XP - also have 2 GB of ram. What else can I supply?

Thank you,

Guy

Hello Guy

I empathise with you. Machines not working is --(*$#@#%*!!!)-- yet your post is surprisingly calm, given the level of frustration this problem must surely be causing

My setup may be similar to yours (Pro-XP2, dual processors, 2GB RAM, NX v1.2, CS3, etc) and the Nikon software that's installed behaves rather . . . well, the best way to describe it would be to say that, at times, its behaviour is rather odd

Weird stuff, the like of which I've never seen with any other utility, and, in addition to NX, I use Camera Control Pro to tether my camera, Picture Project as a down-loader and am now experimenting with View NX. All of them (grrr!!!) have had their moments!

Mathjak raises an important point, I think, least-ways it is insofar as how I managed to resolve the issues on my machine. I would be very pleased if this resolves your problem(s) too

In my view, the underlying problem for this software is the .NET protocol. This is not a criticism of .NET and it's not a criticism of Nikon, but there appears to be some situations where other unrelated utilities and software installs will "break" the Nikon installs. In my case, sometimes it will be all of them at once, or just one of them, or all of them together - but in a different way with each

Anyways, to the point:

* Research which version of the .NET framework is best suited for your requirements on your machine

* Make a clean install of the .NET framework version you decide on - using a fresh download of that version plus all the patches

* In my situation, on my machine with my configuration, my problems were resolved when I rolled .NET 3.0 back to .NET 2.0


I wish you well with this...

Regards



Succat

Hello Succat,

Thank you so much for your time and encouraging - guardedly - response. I don't know how 'calm' I am(?)

Sorry for my ignorance, but I don't know what you are referring to when you write about the .NET framework. (Are you referring to XP versions?) Thanks for your further explanation and advice on determining which version is best.

Guy

.net is a windows based app that nx requires you have installed in order to run and imo is why nx is so botchy and slow.

you cant run nx without net.

and imo .net leads to a lot of conflicts/holes in windows.


how many mac users have complaints on nx out of curiousity?


for the record...my hp quad core vista macine runs nx fine...my xp machine with amd x2 proc hates it.

Thanks for sharing,

Jeff

Hello again, Guy

First, thank you to voodoo for the useful contribution regarding number of processors. This was good to learn

Okay then...to my knowledge the.NET framework does not come bundled with Windows XP and, as you weren't aware of this protocol, I can draw a reasonable presumption that .NET v1.0 was installed on your system by Capture NX. The Nikon installer checks your system and then loads it by default if not present (there would have been a warning box)

I recall having problems early this year with the Nikon software after installing security patches for .NET v1.0 from the MS Download Site. I resolved that issue by upgrading to .NET v2.0

Do you have "MS Automatic Updates" running? It's possible a problem developed when your .NET v1.0 install from Nikon was patched. In any event that may now be a moot point because I am going to suggest you upgrade to .NET v2.0

I won't raise your expectations of a fix, Guy, but I am reasonably confident this may resolve the issues you have. Other members might be able to offer a better method than what I will outline here - comments or contributions are welcome

Here are the steps:

(1.) Download .NET v2.0 from Microsoft - http://www.tiny.cc/LINK01

(2.) Ensure you have the latest version of Capture NX (which is v1.2) a free upgrade from the Nikon Site for your Region

(3.) Un-install existing install of .NET using your system's Control Panel. Assuming you have .NET v1.0 installed, here's a useful article from Microsoft on the procedure that you may wish to read first - http://www.tiny.cc/LINK02

(4.) Reboot your system

(5.) Un-install Capture NX using your system's Control Panel

(6.) This step is optional - but I *will* recommend it because there have been several reinstalls of the software on your system and a messy Registry with old keys might interfere with what we are trying to do. Here is a useful article from Nikon on the subject - http://www.tiny.cc/LINK03

(7.) Okay, with both .NET and Capture NX now un-installed - reboot your system twice (yes, 2 x times)

(8.) Install .NET v2.0 downloaded in Step (1.)

(9.) Reboot your system twice (yes, 2 x times)

(10.) Check the Microsoft Site and download all patches available for .NET v2.0. This MS Knowledge Base article KB928365 applies and the patch is available here - http://www.tiny.cc/LINK04336

(11.) Install the patch or patches for .NET v2.0

(12.) Reboot your system

(13.) Okay - now for the the good bit (and fortuitously, with #13 being my lucky number,things are looking good) ... install Capture NX downloaded in Step (2.)

(14.) Reboot your system twice (yes, 2 x times)

* Then . . . Enjoy! Be Happy! Have a great Life! Take lots of pictures!



Succat


* PS...I had a few problems gettings the Links & URLS in this post to poulate correctly and resorted to using the useful "Tiny URL" service. I haven't had enough time to check that each is correct

Hello Succat,

Thank you for your incredibly generous response! You're great!

I downloaded .NET v2.0 (there are several versions on the Microsoft website), and then went to uninstall v1.0 and found six instances of .NET being installed including v1.0, v1.1, v2.0 and v3.0. Do you have any further ideas, suggestions?

My best to you,

Guy

>Hello Succat,
>
>Thank you for your incredibly generous response! You're
>great!
>
>I downloaded .NET v2.0 (there are several versions on the
>Microsoft website), and then went to uninstall v1.0 and
>found six instances of .NET being installed including v1.0,
>v1.1, v2.0 and v3.0. Do you have any further ideas,
>suggestions?


Get rid of them *all* especially 3.0; then re-install 2.0 (only) per the instructions above.

Only install a 1.x or 3.x if you have specific software that depends on it.

--
Camera <ˈkæ mə rə>, n. Device for taking pictures in bright light.
http://www.flickr.com/photos/nantonos

Hello Chris,

Thank you so much for your both of your responses... and for generously providing the technical information you have.

My technical knowledge (computer/digital) is limited, and in this case particularly so about .NET. I do not know from your post whether or not I should keep v1.0 and v3.0 because programs other than NX require them. I do not know how to determine what those programs might be.

Thank you again Chris,

Guy

Guy,

Have you tried moving Nikon's cache to a folder on a drive other than the one (usually "C")NX runs on?

I have a "NikonTempFile" folder that I created on my "D" drive.

I believe it helped my Capture 4.x and Capture NX performance more than a little.

fred

(look under "Edit" -> "Preferences" -> "Cache settings")

Hello Fred,

A very good idea. I ran across it a couple of months ago and made that change. It didn't seem to help me very much, but at about the same time NX 1.2 arrived and I loaded that -- so I really didn't give the move a 'scientific' opportunity to observe a performance difference.

Thank you so much for your concern and response,

Guy

*
Good morning, Guy (or is it evening where you are?) and hello again...

Thank you for your kind comment on my contribution; you are most welcome and I will be very pleased when we sort out this annoyance for you

First, let me acknowledge and thank Fred for his contribution. Moving the location of NX's cache has delivered performance improvements for many people and, while results will vary depending on one's system and its configuration, this is well worth a try. On my system that tweak did not provide any improvement (slowed things down, if anything) but I would encourage you to experiment . . . after/when NX is up and working again

Okay then, your system has six versions of .NET Framework installed and you record four of them (v1.0, v1.1, v2.0 and v3.0) so I will work on the assumption the others are beta versions, patches or service packs. Also, given that you did not know what .NET was prior this thread, a reasonable presumption can be made that you did not "knowingly" install the .NET Framework and it came about when installing other software or via Microsoft's Automatic Update Service

On the face of it, this situation would support my initial assessment that your underlying problem is the .NET Framework. Three unattended installs - with beta versions and service packs thrown into the mix - sounds haphazard and a fresh, clean start makes a lot of sense

I will suggest that you follow the steps in my previous post - along with the following addendum and NOTES:

(a) Un-install *all* instances of the .NET Framework existent on your system...commencing with the most recent installation (v3.0 ?) and working back wards to the first (beta v1.0 ?)

(b) While (normally) it should not be necessary to reboot between the un-install of each component, I *will* recommend you do so in this situation - reason being that un-installing the .NET Framework can be problematic and with so many steps to take in this case, rebooting will (hopefully) keep the Windows (un)Installer in order

(c) With regards a fresh install of .NET, I have given the matter some more thought and will suggest that, initially, you *only* install a fresh download of .NET 1.1, my reason being that Capture NX v1.2 is built on the language of Microsoft .NET 1.1 and fixing NX is our primary objective right now. Should it be necessary, .NET 2.0 can be installed later - see addendum (e) below

(d) It might be useful to familiarise yourself with the potential problems (and their solutions) prior commencing the process, so here are two links I suggest you read:

http://blogs.msdn.com/astebner/archive/2005/04/08/406671.aspx

http://support.microsoft.com/kb/824643

(e) NOTE: It is possible that some other utility or utilities you have installed on your system might not work now with only .NET 1.1 installed on your system. Do not be concerned by this, I would suggest, because it is likely to identify what caused the .NET conflict with your Capture NX install

(f) NOTE: If the method described here and above remedies your problem with NX (and I expect it will) you might then want to identify what process is/are responsible for those other "unattended" installs of the .NET framework. It might be desirable to take back the control of your system

I wish you well...



Succat

Hello again, Succat -

And once more, thank you so much for everything!

I have uninstalled all .NET(s) and reinstalled .NET v1.1 by itself. (Are the 2 reboots a magical incantation or computer science? Either way or both are good for me.)

When I tried to reinstall NX I received a message that it would not install without .NET 2.0. Should I uninstall 1.1 again before installing 2.0, or what do you suggest?

Thank you as always,

Guy

**

Hello Guy

just a quick response...

(i) NX INSTALL v1.2 = WARNING MESSAGE


"...would not install without .NET 2.0..."


Good! This good news! You have made excellent progress and I'm very pleased you appear to have completed this most "dangerous" part of the process without mishap or event

(ii) QUESTION: "...Are the 2 reboots a magical incantation or computer science?..."

ANSWER: Yes


(iii) Nikon Capture NX v1.2 requires .NET v2.0 on Windows XP - you have established that, and I have learnt something new

Kewl!

My advice will be:

- *keep* your fresh install of .NET 1.1 on the system

- Reboot your system once again (1 x time) prior to installing the fresh download of .NET v2.0

- Install .NET v2.0

- Reboot system twice (yes, 2 x times)

- Install Nikon Capture NX v1.2

- Reboot system

- um, and then...{{{ ~ I presume you know how to drive this software ~ ??? ~ }}}



Regards



Succat

Good Morning (my time) Succat,

I can only thank you once more! Thank you! I hope to have the opportunity to return your incredible favor and effort to you one day -- I will certainly 'pay it forward'.

The magic/scientific moment arrived and departed quietly. After completing the last of the steps I launched NX and found that my three problems persisted, despite my belief... and continuing belief.

Do you have any other ideas? After hammering away at these issues for months, my only idea is to try to find someone at Nikon/Nik who will listen to me and request a refund on software that simply does not function in my particular machine. (Do you think that is possible?) They will tell me, 'no one refunds for software,' which, of course, isn't true. Even Adobe makes refunds when software doesn't work exactly as advertised.

My very, very best to you,

Guy

I just started following this thread. I have never done an install of NX 1.2 having performed and upgrade from 1.1 so the experience may be different. Doesn't NX install .NET 1.1 on it's own and need this to install at least? I removed 1.1 after NX installed and ran off of .NET 2.0, but NX if you didn't have 1.1 installed it. Is that not the case for NX 1.2?

Thanks,

Milkman

Visit my Nikonians gallery.

Visit my Nikonians gallery.

Visit my Nikonians gallery.

Hello Milkman,

Thank you for your thoughtful response and concern. I don't know how the .NET(s) function/interact with NX. In all of the conversations/communications with Nikon, they never mentioned .NET. NX 1.2 would not install without .NET v2.0 being installed first.

I think we will now uncover the mystery.

Guy

>(c) With regards a fresh install of .NET, I have given the
>matter some more thought and will suggest that, initially,
>you *only* install a fresh download of .NET 1.1, my reason
>being that Capture NX v1.2 is built on the language of
>Microsoft .NET 1.1 and fixing NX is our primary objective
>right now. Should it be necessary, .NET 2.0 can be installed
>later - see addendum (e) below

You analysis was correct for Nikon Capture NX 1.2.

Note that Capture NX 1.3 (recently released latest version, as I post) requires .NET 2.0 instead.

--
Camera <ˈkæ mə rə>, n. Device for taking pictures in bright light.
http://www.flickr.com/photos/nantonos

~

Guy - I am more than happy to help you fix this if you are willing to continue

Your Capture NX solution is simply waiting for us to arrive with the correct combination of one or more .NET Framework versions installed on your system - simple in concept but somewhat akin to reading tea leaves in practise

I am not discouraged and here is an outline of what I suggest you do next...


------------------
* STEP-(A).
----------

First, create a new, TEMP folder directly on the root of your C:\DRIVE (or other DRIVE where Windows & Programme folders are located should the DRIVE LETTER be different) then download the following Utilities and place them in your new TEMP location


(1.) REGISTRY TOOLS:

(i) ERUNT: erunt-setup.exe (772 KB)

(ii) NTREGOPT: ntregopt-setup.exe (472 KB)

HERE - http://www.larshederer.homepage.t-online.de/erunt/


(2.) .NET TOOLS:

http://blogs.msdn.com/astebner/archive/2007/11/04/5899888.aspx

(i) .NET Framework Verification Tool

HERE - http://astebner.sts.winisp.net/Tools/netfx_setupverifier.zip

(ii) .NET Framework Cleanup Tool

HERE - http://astebner.sts.winisp.net/Tools/dotnetfx_cleanup_tool.zip


(3.) WINDOWS INSTALLER v3.1:

HERE - http://support.microsoft.com/?id=893803


-------------------
* STEP-(B).
----------


Here are directions for manually removing Nikon's KEYS from the Registry


======= copy below this line =========

Close all running programmes and then go:

(1.) "Start" > "Run" > type "regedit" (sans quotes) in "Run" box > click "Okay" > Registry Editor opens

(2.) Left-click on "+" at HKEY_LOCAL_MACHINE folder > left-click on "+" at "Software" folder > drill down and locate "Nikon" folder > right-click on "Nikon" folder then left-click "delete" > left-click "Yes" on confirmation box

(3.) NOTE: if there is no Nikon folder at this location, continue to Step (4.)

(4.) Close HKEY_LOCAL_MACHINE folder with left-click on "-" at location

(5.) Left-click on "+" at "HKEY_CURRENT_USER" folder > left-click on "+" at "Software" folder > drill down and locate "Nikon" folder > right-click on "Nikon" folder then left-click "delete > left-click "Yes" on confirmation block

6. Close Registry Editor and reboot system

======== copy above this line ==========


NOTE: You might find it helpful to create a new text document inside TEMP folder at STEP-(A) then copy/paste this content over for easy reference later if needed


---------------------
* STEP-(C).
-----------

Okay...time out! I need to pause right now, Guy. A small matter at this location needs my attention and I may be away for up to 24 hours

Speak with you soon



Succat

Hello Succat,

Thank you. I have not begun to set up this information yet. I will begin in a few minutes. I want you to know that I am still here with you... and profoundly grateful that you remain with this issue and me. I believe that NX (and perhaps so many others who have troubled installations of NX) are merely waiting for you to arrive with the right -- and amazing -- combination. Thank you.

I hope the matter you refer to is not serious and will be resolved within the 24 hours,

Guy

Hello Succat,

Okay, I am at Step (C).

Guy

~

Thank you for your patience, Guy

Time on...!

-------------------------------
STEP-(C).
-------------

A few points to note:

* You will need to be logged on to your system with an Administrator Account. Also worth noting - Capture NX does not run properly unless run from an Administrator's Account

* I will recommend you copy/paste these steps into a text document and print them off for easy reference

* Don't hesitate to post any questions you have about this process - and please ask if you are unsure of anything (explanations have not been included at this point to save time and avoid cluttering the directions)

* (EDIT) ... Before commence - move your fresh downloads of the .NET Framework and that of Capture NX into the TEMP folder on Root Drive we created at STEP-(A.)

I wish you well...




(1.) REGISTRY TOOLS: :

(i) Set-up both the registry tools downloaded at STEP-(A)(1) - (i) ERUNT and (ii) NTREGOPT

(ii.) Run ERUNT > click OK, check (enable) all boxes including "Other open user registries" > click OK > click "Yes" to create new directory (and I suggest you allow ERUNT to use its default address) > wait while ERUNT backs up registry hives > click OK. Done!


(2) CLEAN-UP:

(i) Enable the view for system and hidden folders/files

Go - Windows Explorer > Tools > Folder Options > View > check (enable) "Display the contents of system folder" > check (enable "Show hidden files and folders" > un-check (disable) Hide protected operating files" and click "Yes" to Warning Box > then click OK. Done!

(ii) Empty all TEMP & CACHE folders. The addresses on my system, for example, are at:

C:\WINDOWS\Temp\
C:\Documents and Settings\Administrator\Local Settings\Temp\
C:\Documents and Settings\Operator\Local Settings\Temp\
C:\Documents and Settings\LocalService\Temp
C:\Documents and Settings\Default User\Local Settings\Temp\

Retain TEMP Folder we created in STEP-(A)


(3.) NIKON NX:

(i) Un-Install Nikon NX using your system's Control Panel.
(ii) Do you have any other Nikon software installed on your system? I will recommend you un-install it, too
(iii) Reboot computer system
(iv) Manually remove Nikon references from registry using directions at STEP-(B)


(4.) .NET FRAMEWORK:

(i) Un-Install all instances of .NET using your systems Control Panel
(ii) Reboot computer system
(iii) Run ".NET Framework Cleanup Tool" downloaded at STEP-(A)(2)(ii)
(iv) Reboot computer system


(5) INSTALL WINDOWS INSTALLER:

(i) First, do a manual check that .NET Framework has been un-installed, as follows:

* Go - Start > "Run" > type "Installer" (sans quotes) in "Run" box and click OK > on "View" tab in Windows Explorer click "Details" > RIGHT-click on "Name" column header then left-click (enable) the "Comments" column in context menu > click once on "Comments" column header to arrange comments alphabetically > check and ensure there are no references to .NET Framework in "Comments" column > if .NET references are existent - remove them by RIGHT-click on each .NET file then left-click "Un-install" on context menu > following un-install process, close the Installer

(ii) Secondly, do a manual check that folders and contents for .NET Framework have been removed, as follows:

(a) Go - Start > "Run" > type "system32" (sans quotes) click OK > delete the "URTTemp" folder (including contents) if existent

(b) While in the System32 folder - search for and delete "mscoree.dll" if existent

(b) Go - Start > "Run" > type Microsoft.NET" (sans quotes) click OK > delete "Framework" folder (including contents) if existent

(iii) Now install the "Windows Installer v3.1" downloaded at STEP-(A)(3)

NOTE: there is nothing in the documentation that I could find with reference to either un-installing or un-unregistering an earlier version of the "Windows Installer" - and I am also trusting that with our thorough un-install of the .NET Framework, the .NET Framework does not need to be unregistered with the "Windows Installer".

(iv) Reboot computer system


(6.) REGISTRY:

(i) Run the NTREGOPT registry tool you set up at STEP-(C)(1)(i)
(ii) Reboot computer system
(iii) Run NTREGOPT one more time (yes, once again)


(7.) COMPUTER SYSTEM:

(i) Reboot computer system
(ii) When computer restarts - turn it off (yes, OFF)
(iii) Wait 12 seconds - then bootup computer system again


(8.) DON"T SKIP THIS STEP: set Scan Disk tool to "Automatically fix file system errors" > enable it to run at next start-up > reboot computer system > allow scan to run


(9.) INSTALL .NET

(i) First - disable all (third-party) running services using "System Configuration Tool" as follows:

*Go: "Start" > "Run" > type "msconfig" (sans quotes) in "Run" box > click OK or press Enter > click "Services" tab > check (enable) box "Hide all Microsoft Services" > click (enable) the "Disable All" box. Then...click on System Configuration tool > click on "General" tab > click (enable) the "Selective Start-up" box > un-check (disable) box "Load Startup Items" > click OK > reboot system
to effect changes. Done!

(ii) Install your fresh download of the .NET Framework v1.1
(iii) Reboot computer system
(iv) Install your fresh download of the .NET Framework v2.0
(v) Reboot computer system


(10.) INSTALL NIKON NX:

(i) Install Nikon NX v1.?.? from your first, original install disk (have code key handy)
(ii) Reboot computer system
(iii) Install NX v.1.2 upgrade from your fresh download
(iv) Reboot computer system


(11.) SERVICES:

(i) Enable all (third-party) running services using the reverse steps at (9)(i) above
(ii) Reboot computer system


(12.) SYSTEM:

(i) The TEMP folder created in STEP-(A.) may now be removed from Directory Root and placed for future reference in your normal download directory
(ii) Repeat Step (8.) above
(iii) Repeat Step (6.) above ... but only need to run NTREGOPT once on this occasion
(iv) Reboot computer system
(v) Repeat Step (1.) (ii) above


DONE!


(13.) .... Sweet! my lucky number as you know...so, start up NX and let's see how we did, huh?


Regards



Succat

Hello Succat,

Very good to hear from you. I hope you are well, and that all is well.

I've read the instructions up to and including 'sweet' 13. No questions came to mind from the details -- yet. I have two general questions though before I begin:
1) I am the only user of my computer. As well as I remember, I did not set up a separate Administrator Account. However, one may exist. How do I discover this and either eliminate it or enter the computer as the administrator; and
2) Drive C already had a TEMP file on it, of course. I created another TEMP file as TEMP 1 for our purposes. Should I use the computer generated original file instead?

Thank you....

Guy

.

Thank you for posting back with your enquiries...

By your numbering, Guy:

1. By default, WindowsXP creates an Administrator Account when it first starts following install. If you have not created a separate or purpose built account for yourself, the account you are currently using will be an Administrator's Account.

From a security point of view, users running Administrator Accounts for general, everyday usage is not regarded as "best practise" - but that is a topic for another thread

To check what "User Accounts" you have created on your system, go to the Control Panel and open "User Accounts"

Here are two useful references:

* An overview of "User Accounts" - Microsoft's on-line product documentation for WindowsXP Professional:

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/usercpl_overview.mspx?mfr=true

* Same thing, but more reader friendly - "Windows for Dummies" on-line version:

http://www.dummies.com/WileyCDA/DummiesArticle/id-350.html

2. With regards the existing TEMP folder on rive and our new TEMP-1 created at STEP-(A) there is no difference, they serve the same purpose. Had I known a TEMP was already existent on the Root Drive - that extra direction would not have been included

If you wish, drag the fresh downloads you are about to install into C:\TEMP and delete TEMP-1



Succat

Might have missed it, but do you need .NET 1.1 on the computer for anything ?
I notice I have both 1.1 and 2.0 on my drive.
Kind regards
Nielsen

Kind regards
Nielsen

Hello Succat,

I am here... as are you. Thank you (and for the last quick computer lesson about accounts.)

Sorry for the delay. I wanted to get back to this sooner.

Another question: I've gotten to "(2) Clean-up." The TEMP file under C:\Documents and Settings\(my name)\Local Settings\Temp\ has 19 file folders in it as well as many individual files. All together, this TEMP file contains 1.19 GB. Do I empty everything, including the file folders, one of which is labeled 'Adobe' and another - the largest (563 MB)- is 'hp_webrelease'?

Not quit flying yet,

Guy

Guy,



Two issues, by my numbering...

(1) Delete contents of TEMP:

Yes, you may safely delete *all* content (including sub-folders) from the TEMP directory at C:\Documents and Settings\(your name)\Local Settings\Temp ... plus *all* content (including sub-folders) from the TEMP directories at other addresses in Documents & Settings

This process is safe - and desirable, given our task at hand

Your system will rebuild the sub-folders again if/when they are needed

(2) .NET v1.1:

Nielson asks why have .NET Framework v.1.1 installed (EDIT: oops, correct a missquote...)

There are many issues we are working through to have Capture NX 1.2 run on Guy's system and .NET v1.1 is one example

If NX 1.2 does not run correctly after following the steps of this process, we will then work through our options methodically - confident of a solid, clean and tidy base from which to start

Thank you Nielsen, good question

Comment and input from members is welcome...



Succat

Hello Succat,

Thank you.

I am in steps (3)/(4). (3) -- I uninstalled NX and four other Nikon programs. Picture Project would not uninstall completely using Add and Remove Programs. I went to Program Files on the C drive and deleted its contents there. Also, I noticed a Nikon file folder in C:\Documents and Settings\(your name)\Application Data. Should that go? More - 5 files in
C:\Documents and Settings\(your name)\Local Settings\Temp will not be deleted. The message is that they are in use by other programs.

(4) -- I have uninstalled the .NET installations. I am ready to reboot my computer.

Guy

Hello (during your night... I think),

I pushed slightly ahead after rebooting, and encountered two more issues in step (5): 1. The mscoree.dll in (5)(ii)(b) would not delete; and 2. The "Framework" folder in (5)(ii)<(c)> would not delete. A fusion.dll prevented this deletion. There may be other files that would do the same in "Framework."

Still here and there,

Guy

Okay then, Guy, it's all good...




(1.) UN-INSTALLING NIKON SOFTWARE:

(i) Picture Project's (un)install data is possibly corrupt, hence your hiccup there. In anticipation of some problems with Nikon's un-installers I wrote the Registry instructions in STEP-(B) and this will resolve your latest issue

I recommend that prior executing the directions in STEP-(B) you also manually delete *all* Nikon folders (including their contents) from C:\Program Files - and also from C:\Program Files\Common Files

(ii) Good work spotting the Nikon folder in "Application Data" at Documents and Settings (I deserve a spanking for overlooking that directory!)

Yes, delete the Nikon folders (including their content) from *all* "Application Data" directories in Documents and Settings


(2.) CLEAN UP:

You may disregard the files "in use by the system/other programmes" that won't delete, they won't be an issue


(3.) UN-INSTALLING .NET FRAMEWORK:


Hmmm, the problems you have encountered here are interesting. While it would not hurt to press ahead and leave the mscoree.dll in-situ, I suspect we would need return here if NX does not run correctly...

So, I will recommend we deal with it now via the Registry - along with the fusion.dll which is also part of the .NET framework

CAUTION: do not attempt this task if you are tired, stressed, distracted, in a rush or otherwise less than your best. Although we took the precaution of backing up your Registry in STEP-(C)(1.)(ii) - it is better to avoid having to start again should you break something else

Having said that, I am sure you will be fine...so let's proceed:


*** (EDITING NOTE...Guy, after posting the following, I have given this more thought and now have a better, more effecient and easier method for you to achieve the outcome we need. It will take me a little while to write this up - so I suggest you hold off until my next post. I apologise for any confusion this might cause...)


===== STOP! Please Read my Editing Note =====

(i) Go - Start > "Run" > type "regedit" (sans quotes) in "Run" box > click OK or press Enter > Registry Interface will open

(ii) Click "Edit" on tool bar > click "Find" > type ".NET" (sans quotes) in "Find What" box > press "Find Next" > Registry search will commence

(iii) We are looking for every .NET reference, which you will DELETE, either with "Delete" on your keyboard or "Delete" on the right-click context menu. After each instance either click "Find Next" or press F3 on your keyboard, which ever is easier

(iv) AN IMPORTANT NOTE: the Registry search will present you with the word "NET" "Net" or "net" in quite a few results...and so you MUST be sure to ONLY delete ".NET" results

(v) After completion, reboot your computer system, delete the folders and mscoree.dll - and then continue...

Isn't this fun!



Succat

Guy, to simplify matters and avoid too much confusion I have gone ahead and rewritten No.(5) in STEP-(C)

This makes it much easier if you wish to append a copy/paste print-out onto the original

Importantly...I wish to acknowledge and give credit to Aaron Stebner for the method I have employed here



============= REVISED STEP-(C)(5) ===============


(5) INSTALL WINDOWS INSTALLER 3.1:


(i) First, do a manual check that the .NET Framework has been un-installed, as follows -

(a) In Registry, go to: HKEY_LOCAL_MACHINE > Software> Microsoft > .NETFramework > and delete those keys and values that have the same .NET version number(s) as was installed on your system (such as 1.0 or 1.1 or 2.0 or 3) - PLUS delete any keys and values that are in sub keys under .NETFramework

(b) In Registry, go to: HKEY_LOCAL_MACHINE > Software > Microsoft > .NETFramework > Policy > and delete any keys or values that have the same .NET version numbers, as above.

(c) In Registry, go to: HKEY_LOCAL_MACHINE > Software > Microsoft > ASP.NET > and delete any keys or values that have the same .NET version numbers, as above


(ii) Second, remove ASPNET User Account from your system, as follows -

(a) Go - Right-click My Computer > left-click "Manage" > expand Computer Management (Local) > expand Local Users and Groups > double left-click on Users Folder in right-hand pane > right-click on the ASPNET user account and left-click "Delete" in context menu

(b) Drill down to - C:\Windows\Assembly and delete any folders that are named with the same numbers as your .NET versions (as above) - PLUS also delete the GAC_32 and GAC_MSIL folders

NOTE: you will not be able to view the folders inside C:\Windows\Assembly if the .NET Framework has not been un-installed and (because our problem up until this point has been effecting an un-install of the .NET Framework) if you cannot see the folders - then enable the view, as follows -

(c) Go - Start > "Run" > type "regedit" (sans quotes) in the "Run" window > click OK or press Enter > drill down to HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Fusion > Right-click on Fusion Folder > select (left-click) "New DWORD Value" > rename by typing "DisableCacheViewer" (sans quotes - with no gaps) and press Enter > right-click new key and left-click "Modify" > change the existing value to number "1" (sans quotes) and left-click OK > close Registry. Done!

You will now be able to view the contents and folders inside C:\Windows\Assembly, and, after completing the steps in (5)(ii)(b) - return to the "DisableCacheViewer" key you created in your Registry and delete it


(iii) Third, remove Microsoft.NET folders, as follows -

(a) Drill down to C:Windows\Microsoft.NET \Framework and delete the folders (including sub folders). If you still get error messages because some of the files are in use - reboot your system and try again. If this does not work, rename the files as <filename> ".OLD" (sans quotes) and delete them following your next reboot

(b) Use the same method with "mscoree.dll" in C:\Windows\system32 if there is a problem - rename it "mscoree.dll.OLD" (sans quotes)


(iv) Fourth, reboot your computer system


(v) Now...install the Windows Installer 3.1 you downloaded at STEP-(A)(3)



========== CONCLUDE REVISED STEP-(C)(5) ============



Just keep your questions coming, Guy. We are making good progress


Of course, the really funny thing in all of this, is, that all we ever wanted to do...was take photographs (pmsl!)




Succat

============================


* (EDIT) ... here is a cleanup tool from Microsoft that (reportedly) will remove both v1.1 and v2.0 of .NET Framework at the Registry level

I have not tried this utility and can make no comment regarding its use. The link is included here simply for the purpose of providing information:

http://download.microsoft.com/download/e/9/d/e9d80355-7ab4-45b8-80e8-983a48d5e1bd/msicuu2.exe

CREDIT: Thanks to Nikonian Member, JVSabados, who provided that link in the context of this following thread:

http://www.nikonians.org/dcforum/DCForumID36/16328.html

Dear Succat,

Thank you for the latest installment -- and to Aaron Stebner, please. I am keeping up with you.

Here is my progress by the (new) numbers:

1. (5)(i)(a) - okay;

2. (5)(i)(b) - okay, except that when I deleted the keys in "Policy" I mistakenly deleted the "Policy" folder itself, which had been emptied;

3. (5)(i)(c) - okay;

4. (5)(ii)(a) - okay;

5. (5)(ii)(b) - okay, and I was able to see the contents of "Assembly" the first time. Two files here I did not delete -- NativeImages_v1.0.3705 and ...v2.0.50727_32. Should I delete these(?);

6. (5)(ii)(c) - I did not have to do this step;

7. (5)(iii)(a) - Only one folder, "v.1.0.375", existed under C:Windows\Microsoft.NET \Framework. I could not delete the folder itself. I opened it instead and deleted the contents by first selecting them all. That folder shows no contents, yet when I try to delete the folder itself, it will not delete. I get the ususal ...in use... message(?);

8. (5)(iii)(b) - mscoree.dll (after renaming it to .old and rebooting) finally deleted(!);

I rebooted and stopped before proceeding with (v).

Wow. Yes, we just want to take photographs! However, what you are doing is creating that...

Guy

This is good, Guy

Okay then, by your numbering:

2. (5)(i)(b) - I don't expect that will cause any problem; the system will rebuild it when we re-install the .NET Framework

5. (5)(ii)(b) - good to read you could "view" the contents first up, indicating your existing Installer is working well (we'll still upgrade it, though) ... and yes, delete both NativeImages_v1.0.3705 and v2.0.50727_32

7. (5)(iii)(a) - try renaming the folder to "v.1.0.375.OLD" (sans quotes) then reboot your system and try again. Should that not work - try deleting the whole "Microsoft.NET" directory. If that fails - rename it "Microsoft.NET.OLD" (sans quotes) then reboot and try again. If that fails - will simply NUKE it!

Kewl!

Keep us posted...



Succat

Hello!

Thanks for #2. I deleted both 'Native...' files without a hiccup. v.1.0.375.OLD and Microsoft.NET.OLD are another story. They do not want to go; they do not - even - want to be renamed! Is it time to nuke?

Guy

"...Is it time to nuke...?"

LOL!

Probably not, try this first:

Right-click on the Microsoft.NET Folder > left-click "Properties" > un-check (disable) "Read Only" > select yes or OK to change all sub-folders and files (cannot remember the exact syntax) > wait for change to effect > left-click Apply/OK

Now remove and, if that works - sorry to take away the fun



Succat

No... I think it's Nuke time.

All three folders are empty: Microsoft.NET, Framework and v1.0.3705, but none will delete and none will allow disabling of "Read Only." The "Read Only" box will let me un-check it, then it rechecks itself as soon as it closes from applying the change and clicking OK. It's quit amazing -- they are still "...being used by another person or program"!

Are we looking at the fun part now?

Guy

...Fun?

L-O-L!!!

No, sorry to be the Grinch - one more attempt - try deleting in "Safe Mode" as follows:

Reboot your system > press F8 while system starts up > then drill down as normal. There's something of a knack in pulling this off successfully; some users press the F8 repeatedly in rapid secession throughout the start up process to ensure they catch it

I use the word 'normal' but, should this be your first experience of working in Safe Mode, your monitor's display and appearance will not be normal

After deleting, reboot your system and continue...

...Fun?! Sheesh, this isn't s'posed to be fun (chuckle~chuckle)



Succat


** (EDIT) Guy, before attempting "Safe Mode" delete - please read my following post...

I'm not a Grinch (really, I'm not) but please humour me with a few more steps...

It's possible (just possible) we have made a breakthrough that will not only resolve your particular issue(s) - but may also identify a simple, underlying glitch that has been the cause of so much annoyance for NX users


Please carry out the following on your system:


(1.) Go - Start > "Run" > type "Installer" (sans quotes) in "Run" box and click OK > on "View" tab in Windows Explorer click "Details" > RIGHT-click on "Name" column header then left-click (enable) the "Comments" column in context menu > click once on "Comments" column header to arrange comments alphabetically > check...are there any references to .NET Framework - in particular "v.1.0.375" - ?

Don't delete any entry(s) - just report back


(2.) Go - Start > "Run" > type "regedit" (sans quotes) in "Run" box and click OK or press Enter and drill down to > HKEY_LOCAL_MACHINE \ Software \ Microsoft \ .NET Framework > Open all sub-folders (left-click all "+") > check...is there any reference to "v.1.0.375" - ?

Don't delete any entry(s) - just report back


(3.) Repeat same process at this address > HKEY_LOCAL_MACHINE \ Software \ Microsoft \ ASP.NET

Don't delete any entry(s) - just report back


(4.) Go - Start > "Run" > type "C:\Windows" (sans quotes) and click OK or press enter then scroll down to Microsoft.NET folder > Right-click on folder > left-click "Properties" > left-click "Security" > left-click once on "Administrators" (to highlight) > left-click "Advanced" > left-click "Owner" Tab > please note down the entry in "Current owner of this item" > left-click "Cancel" > left-click "Cancel"...and report back what you noted


I look forward to your next post...



Succat


*(2 x EDITS)...Typo's

Hello Succat,

Very good to hear from you - twice - this morning!

"It's possible (just possible) we have made a breakthrough that will not only resolve your particular issue(s) - but may also identify a simple, underlying glitch that has been the cause of so much annoyance for NX users"

YES. This has been in my digitally limited mind since your first post -- that what you are truly working on is Capture NX for all users. I've created a "book" with all of your entries -- 20 pages so far (Georgia, 12 pt. type, 1 1/2 line spacing - with just your entries and my first one to define the issues). I also thought that when you came to the end of your successful hunt, I would send it to Nikon! (Of course, that would be completely your call. I would not do anything like this on my own. You may already have a better idea.) Anyway, I have a provisional title: The Saga of Succat's Adventure Through Capture NX (OR how he saved Nikon's Software Bum).

To business:

(1.) There were no references to ".NET Framework" or v.1.0.375 here.

(2.) There are no sub-folders under .NET Framework. However, there is one InstallRoot file within .NET Framework -- C:\WINDOWS\Microsoft.NET\Framework\.

(3.) The only sub-folder under ASP.NET is "Machine Accounts". Within that is an ASPNET file.

(4.) Clicking on the Properties of the Microsoft.NET folder only reveals two tabs: General and Sharing. There is no Security tab.

I have not gone into Safe Mode yet,

Guy

SIDE NOTE:

Thank you for your vote of confidence and kind comment on my
contribution to your thread, Guy, but we are simply following
standard trouble-shooting practise - even if our process appears
inscrutable, almost arcane, to people just starting out

Our "break-through" (if that transpires) will only be the result of
noting the interconnectedness of two simple, and hitherto seemingly
unrelated factors

Credit - if credit be due - must go to our Teachers and those who
came before because ..."“if (we) have seen farther than others
it is because (we) have stood on the shoulders of giants.”
(Sir Isaac Newton)


========================================


Okay, let's get rid of this pesky file and move on...


In the following order, try this:

(1.) Restart your computer and Go - Start > "Run" > type "cmd.exe" (sans quotes) in "Run" box and left-click OK or press Enter > type "del" (sans quotes) in the Command (black screen) window + space (press SPACE bar) and type the directory's address (example below, sans*) > press enter > click OK or press Enter at warning box

* del(single space)c:\winnt\Microsoft.NET

Reboot your computer system and proceed to STEP-(c) (5)(iv)


(2.) If that doesn't work, restart your computer system and try "Safe Mode" delete following the directions in Message #35 (above)

Reboot your computer system and proceed to STEP-(C)(5)(iv)


(3.) If that doesn't work, restart your computer system and try this:

There are two steps...

(i) Open Task Manager (hold down ALT + CTRL + DEL) > left-click "Task Manager" tab - or, if already open, left-click "Processes" > scroll down and left -click once (to highlight) on "explorer.exe" > left-click "End Process" > (don't be concerned with the dire warnings) left-click "Yes" to terminate process

(ii) Go - Start > "Run" > type "cmd.exe" (sans quotes) in "Run" box and left-click OK or press Enter > type "del" (sans quotes) in the Command (black screen) window + space (press SPACE bar) and type the directory's address (example above, sans*) > press enter > click OK or press Enter at warning box

Reboot your computer system and proceed to STEP-(C)(5)(iv)




Succat


P.S. (chuckle~chuckle) ... this after noon I will load a roll of film (yes, film - remember film?) into my FM3A and take a leisurely walk. Afterwards, I'll drop the film off at some 1-hour lab, pay a few shekels, enjoy a coffee while I wait...then pick up my pics

Simple, huh?

The World has been conned! (chuckle~chuckle)

Hello Succat,

Yes. Shooting with film. Where you are is more fun than where I am.

Yes, to giants too. However, who is "we"? The ones standing on the uncountable shoulders who then become the giants -- endless giants....

Business, again:

(1.) This did not work. When I entered "del c:\winnt\Microsoft.NET", the command prompt merely reappeared. Nothing changed after I rebooted.

(2.) This worked. In Safe Mode, I deleted the folders: v.1.0.375, Framework and Microsoft.NET itself - just because. These are the only changes I made.

(3.) Under System 32 I noticed a file titled, "mscories.dll". "mscoree.dll is still gone. Should mocories.dll be deleted?

I have stopped here, awaiting your leisured cup of coffee,

Guy

Since we are the world, who is conned?

I forgot to mention that each time I've rebooted the last couple of days a program entitled, "PhotoGallery" tries to - unsuccessfully - install itself automatically. I presume this is (or was) something inside one of the Nikon packages I uninstalled.

Hello Guy

Just a brief comment from me on a few matters at this point:


(i) Pleased to read our "Safe Mode" delete method worked


(ii) For our purposes, you may disregard the "mscories.dll" - but well spotted, nonetheless. This driver is associated with .NET Framework and provides for Internet Explorer's security registration


(iii) I don't know what programme your "PhotoGallery" is associated with - but will presume that, with .NET Framework gone, we've broken its install and some related ".ini" file is attempting to effect the repair/reinstall

We'll deal with that matter later but, meantime, I will recommend you temporarily disable it from starting up - along with temporarily disabling your other start-ups, too, prior the fresh installs of .NET and Capture NX - as follows:

(a) Go - Start > "Run" > type "msconfig" (sans quotes) in the "Run" window and left-click OK or press Enter > left-click on "Startup" Tab

(b) Scroll down the list of programs and un-check (disable) everything (yes, everything) that is listed - with the exception of your antivirus software and firewall should you have such installed

(c) Close out of the utility when done and restart your computer system. Click OK on the warning box and check "don't show this again" when Windows starts

(d) NOTE: This is just a temporary measure because the method described here is intended for trouble shooting purposes - but it will also serve us well in this case. Depending on the number of programmes you have temporarily disabled from Start-up, you will notice an improvement in performance from your system

(e) NOTE: These programmes have only been disabled from Start-up: they will run as normal if/when you require them, such as your printer, for example


(iv) Okay - so you are now ready to install Windows Installer 3.1 at STEP-(C)(*5)(iv) (*Revised)

Slowly, but surely...




Succat

Hello Succat,

Thank you. Always good to 'hear' your cheery voice!

(C)(5)(iv) finally arrived. I have installed the installer - and PhotoGallery gave up. Do I proceed with (6)?

Hope you got some wonderful shots....

Guy

~

Good work, Guy!

Nice!

Yes, continue on...but please make two small changes at STEP-(C)(9)(iii) and (v) when installing .NET Framework v1.1 and v2.0 - as follows:

In some earlier, original directions I prescribed rebooting your computer system twice at install but changed that to a single boot when writing STEP-(C) directions

As we saw when trying to remove it, the .NET Framework likes to dig in quite deep...so I will recommend you help it along and reboot your computer system twice (yes, 2 x times) after installing both v1.1 at (9)(ii) - and v2.0 at (9)(v)

Keep me posted, and don't hesitate to ask questions...



Succat


**(EDIT)...Guy, I have been thinking some more about correctly lining up all our ducks in relation to the various versions of .NET and Capture NX

Please read my following post before proceeding

Thanks

(1.) Guy, would you please provide the following:

(a) What versions of Capture NX do you have?

(b) Which of them are full versions and which of them are "updates"?

(c) Which of them are on factory install discs and which of them are downloads via the Internet?

(d) Very briefly (a paragraph or less) please outline the upgrade path you followed from first NX installation up to the NX installation at time of your original post on this thread

(e) Very briefly (a paragraph or less) please outline the sequence of your problems. You could integrate this response with your response in (d) should you choose

(f) I would have also liked to ask of your upgrade path for the .NET Framework (vis-a-viz Capture NX) but you were not aware of .NET prior this thread. Notwithstanding that situation - is there anything (anything?) you might be able to add which may give me some clues, even if nothing more than some hazy memories?


(2.) Please allow me to think aloud:

(a) If you have a full version of NX v1.2 with an activation key - is it necessary to first install NX v1.x.x?

(b) If we can go directly to installing NX v1.2 - is it necessary to first install .NET v.1.x.x?

(c) Capture NX v1.3 (Updater) is available - is this a recommended step with regards possibly improved code and/or bug fixes?


(3.) Guy, as you are probably aware, there are some gifted and expert NX users at Nikonians - some (or one) of whom may be willing to offer an authoritative opinion on questions (2.)(a) - (c)

I would defer to the opinion of these users, but wouldn't expect they will be following this thread - so here's some homework for you...

Please make some contact(s) via Nikonians' PM function and request advice on this matter

Thank you



Succat


*(EDIT) typo

Hello Succat,

Here is the latest installment....

(1.) Guy, would you please provide the following:
(a) What versions of Capture NX do you have?

ANSWER: I have v1.1 on a CD. I have v1.2 as an .EXE file downloaded from Nikon. (I believe the CD version is v1.1. Neither the CD nor its case, nor its contents specify a version. It could be v1.0, but I don’t think so.)

(b) Which of them are full versions and which of them are "updates"?

ANSWER: v1.1 is a full version. v1.2 is an update. (I have not downloaded v1.3 yet.)

(c) Which of them are on factory install discs and which of them are downloads via the Internet?

ANSWER: v1.1 is a factory install disc. v1.2 is a download.

(d) Very briefly (a paragraph or less) please outline the upgrade path you followed from first NX installation up to the NX installation at time of your original post on this thread

ANSWER: I downloaded the trial version of NX first. Then I ordered the CD-ROM and installed it, (I believe without uninstalling the trial version – on Nikon’s advice). I recall that problems (issues) began immediately and before v1.2 became available. I was uninstalling v1.1 on the advice of Nikon before v1.2 existed. After I downloaded v1.2 from the Internet, each uninstall and reinstallation, of which there were several, did not involve reinstalling NX from the CD first. All reinstallations happened from the 1.2 .EXE file.

(e) Very briefly (a paragraph or less) please outline the sequence of your problems. You could integrate this response with your response in (d) should you choose

ANSWER: The problems happened in the following sequence:
1. Extreme slowness and non-responsiveness;
2. Regardless of the file size (unless I resized it), each NEF balloons to 272 MB -- from usually around 18 MB when I print;
3. All files and sizes (NEF) print with a white border on the top and right sides;
4 After sending a NEF (as a TIFF) to CS3 for touch up work and I have saved the file as a TIFF, I cannot open the newly saved TIFF in NX as it was saved in CS3. It opens as a contact sheet with 9 black and white images of the file. The TIFF opens as it should in CS3 and LR. Also, the original NEF, untouched by CS3, will not open in NX at all. It opens normally in CS3 and LR.

(f) I would have also liked to ask of your upgrade path for the .NET Framework (vis-a-viz Capture NX) but you were not aware of .NET prior this thread. Notwithstanding that situation - is there anything (anything?) you might be able to add which may give me some clues, even if nothing more than some hazy memories?

ANSWER: Yes, hazy here. I just noticed when I searched the NX CD-ROM, that .NET v1.1 is included there. I suppose that’s how the first version appeared on my computer – although it and .NET v2.0 could have preexisted NX. I assume Microsoft automatically downloaded v2.0. That’s the best I can do.

(2.) Please allow me to think aloud:
(a) If you have a full version of NX v1.2 with an activation key - is it necessary to first install NX v1.x.x?

MY CONTRIBUTION: Of course, I’ve used the same original CD-ROM activation key with each installation.

(b) If we can go directly to installing NX v1.2 - is it necessary to first install .NET v.1.x.x?
(c) Capture NX v1.3 (Updater) is available - is this a recommended step with regards possibly improved code and/or bug fixes?

MY CONTRIBUTION: In researching the last issue noted in (2) (e) above, I discovered from others and in speaking directly with Nikon that v1.3 only accommodates the new D300 and D3. It does not attempt to fix any known bugs, etc.

(3.) Guy, as you are probably aware, there are some gifted and expert NX users at Nikonians - some (or one) of whom may be willing to offer an authoritative opinion on questions (2.)(a) - (c)
I would defer to the opinion of these users, but wouldn't expect they will be following this thread - so here's some homework for you...
Please make some contact(s) via Nikonians' PM function and request advice on this matter

ANSWER: I will begin a new thread for (2.)(a) – (c).

Thank you

Succat...

AND now from Guy

*



First, a *big* thanks to Nielsen for his valuable assistance on another thread to clarify the situation regarding (2)(a)-(c) above

Thank you, Nielsen, much appreciated...!

--------------------------------------

Hello again, Guy

Thank you for your prompt, concise response


Okay then, given my current understanding of all these matters I will recommend the following rebuild, and, to ensure these versions are the actual versions existent in your TEMP folder at STEP-(A), may I suggest fresh downloads from these links:


(a) .NET v1.1 Redistributable Package

(b) MS-KB928366 .NET v1.1 Hotfix

(c) .NET v2.0 Redistributable Package (x86)

(d) MS-KB928365 .NET v2.0 Security Update

(e) NikonCapture NX v1.2 Full Version Installer for Windows


Following that, please download these utilities into your TEMP folder also:


(f) CCleaner v2.02

(g) Startup CTRL Panel from Mike Lin

(h) StartupMonitor - also from Mike Lin


Meantime, while you finish that, I will rewrite the remainder of STEP-(C)(6) to (x?)...




Succat

Hello Succat,

Thank you!

I've downloaded all but two:

(b) will not download until I Install IE 7.0. I have 7.0 already, but downloaded it again. I still get sent to the download 7.0 message first.

(e) This link will not open at all. Is it possible you can only download 1.3 now?

Waiting for your next appearance,

Guy

.

PS I went to the Nikon site and downloaded the NX 1.2 Full/(30 day)Trial version .exe file. I'm still missing item (b)...

:)

Hello Guy,

(1.) Here are some notes regarding the mixed results you had with recommended downloads & links...

I was not aware Internet Explorer (v7.0) was required to run KB928366 - HOTFIX for MS.NET v.1.1 - nor could I find reference to this in Microsoft's documentation. In any event, I would certainly recommend an upgrade to Internet Explorer v7.0 (plus patches)

Check to see what version of Internet Explorer is currently installed:

From a browser window inside Internet Explorer > left-click "Help" > left-click "About Internet Explorer" > note down the version number - that's what you have (least ways, that's what your System thinks you have)

Try a repair of the Browser, as follows: first, close any open programmes and back-up your "favourites" folder, and your "address book" if using Outlook or Outlook Express, then - Open Internet Explorer > left-click Tools > left-click Internet Options > left-click advance > left-click "Reset" button > follow your on-screen directions

If you are unable to resolve this issue with your Browser, we may have to disregard patching .NET v.1.1 with the HOTFIX at this time

NOTE: Windows Installer v3.1 is also required - have you installed that? (see above, Windows Installer 3.1 at STEP-(C)(*5)(iv) (*Revised)



(2.) Some additional notes...


(b) MS-KB928366 .NET v1.1 Hotfix

* Here is the LINK provided, above:

http://support.microsoft.com/kb/928366

* Here is an ALTERNATIVE LINK that home-users could try:

http://www.microsoft.com/protect/computer/updates/bulletins/200707.mspx

* Here is an EXTRACT...from the Microsoft Web Site:

APPLIES TO: (Microsoft .NET Framework 1.1 Service Pack 1, when used with)

Microsoft Windows XP Home Edition
Microsoft Windows XP Media Center Edition 2002
Microsoft Windows XP Professional
Microsoft Windows XP Starter Edition
Microsoft Windows XP Tablet PC Edition
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Datacenter Server
Microsoft Windows 2000 Professional Edition
Microsoft Windows 2000 Server

PREREQUISITES:

• To install this security update, you must have Microsoft Windows Installer 3.1 installed on your computer. To obtain the latest version of Windows Installer for your computer, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=889482fc-5f56-4a38-b838-de776fd4138c

• To install this security update, your computer must be running one of the following operating systems:

- Microsoft Windows XP with Service Pack 2 (SP2)
- Microsoft Windows 2000 with Service Pack 4 (SP4)

(...no mention of Browser)


(e) NikonCapture NX v1.2 Full Version Installer for Windows

Hmmm, the link I provided won't now work for me, either. Ooops, I must have coded it wrong! Sorry

Not to worry - the "trial" version you downloaded becomes a "full" version once your "Product Key" is loaded


(3.) Before progressing further, I will wait and see your outcome with Internet Explorer v7.0




Succat

Hello Succat,

Good to hear from you....

I already had IE installed, but I reinstalled it again yesterday. The version is: 7.0.5730.13.

I did your "Try a repair of the Browser" next. After completion, I searched for http://support.microsoft.com/kb/928366 and got the same web site as before. This time when I tried to download the 'hot fix' I was directed to a 'check of my computer for software updates'. That downloaded two "Genuine Advantage Validation Tool" files. Once installed, the site took me to a download window that wants to download: Security Update for Microsoft .NET Framework, Version 1.0 Service Pack 3 (KB930494). I stopped there. I don't think this is the file we want -- nor to start uninstalling again.

I installed Windows Installer 3.1 a couple of days ago.

I await,

Guy

That's all good, Guy, you did well...

I expect your problems at MS-Downloads in this case result from your system not having a .NET Framework installed; we'll address issues with this particular Hotfix later

Meantime, download "Service Pack 1" for .NET v1.1 and leave in TEMP folder. Here's the link:

.NET v1.1 Service Pack 1

http://www.microsoft.com/downloads/details.aspx?FamilyID=a8f5654f-088e-40b2-bbdb-a83353618b38&DisplayLang=en

Keep me posted



Succat

Hello (and good day from my morning),

It is accomplished. Service Pack 1 is downloaded.

Hope all's well with you,

Guy

:)

Hello Guy, and good morning to you, too (my time)

* Here are the revised STEP-(C) directions

* I recommend you un-install your printer before starting. I suspect a conflict (is it an HP ?)

* Please post any questions you have...


/
====== COMMENCE: STEP-(C) (*6) to (*13) (*REVISED) =====


(6.) INSTALL CCleaner:

(i) Go to TEMP folder at STEP-(A) and install CCleaner. Some notes for your information:

(a) "Install Options" at setup are a personal choice. These are mine - ALL options are disabled except "Add CCleaner..." to Recycle Bin Context menu

(b) In the event of Runtime errors on your system at MSVBVM60.DLL - reinstall Microsoft's VB6 Runtime components (available here) and try again

(c) FAQ, Tour and On-line Help for CCleaner available here: http://www.ccleaner.com/helpForassistance


(ii) Run CCleaner. Some notes on recommended use for our current process::

(a) Open CCleaner > "Cleaner" tab > "Windows" tab > un-check (disable) "Advanced" tab > un-check (disable) any items you wish to KEEP on your system (such as cookies, for example) > select "Application" tab > check (enable) ALL items > left-click "Analyse" > wait for CCleaner to complete analysis (this may take some time being the first run) > left-click "Run Cleaner". Done!

(b) With CCleaner still open > select "Registry" tab > un-check (disable) "Registry Integrity" > check (enable) INDIVIDUALLY (i.e., one at a time) each of the "Issues" in (c) below > then left-click "Scan for Issues" > uncheck (disable) ALL items - EXCEPT entries relating to ".NET Framework" + "Nikon" + "Your Printer" > left-click "Fix selected Issues" and follow onscreen directions. Done!

(c) These are the "Issues" to scan at this time:

* Applications
* Application Paths
* Installer
* Obsolete Software
* MUI Cache

(d) Restart computer system


(7.) REGISTRY:

(i) Run the NTREGOPT registry tool you set up at STEP-(C)(1)(i)
(ii) Reboot computer system
(iii) Run NTREGOPT one more time (yes, once again)


(8.) COMPUTER SYSTEM:

(i) Restart computer system
(ii) When computer restarts - turn it off (yes, OFF)
(iii) Wait 12 seconds - then startup computer system again


(9.) DON"T SKIP THIS STEP: set Scan Disk tool to "Automatically fix file system errors" > enable it to run at next start-up > reboot computer system > allow scan to run


(10.) INSTALL .NET Framework

(i) First, disable all (third-party) running services using "System Configuration Tool" as follows:

Go - "Start" > "Run" > type "msconfig" (sans quotes) in "Run" box > click OK or press Enter > click "Services" tab > check (enable) box "Hide all Microsoft Services" > click (enable) the "Disable All" box. Then...click on System Configuration tool > click on "General" tab > click (enable) the "Selective Start-up" box > un-check (disable) box "Load Startup Items" > click OK > restart computer system to effect changes. Done!

(ii) Install fresh download of .NET Framework v1.1
(iii) Restart computer system
(iv) Install fresh download of SERVICE PACK 1 (.NET Framework v1.1)
(v) Restart computer system twice (yes, 2 x times)
(iv) Install fresh download of the .NET Framework v2.0
(v) Restart computer system twice (yes, 2 x times)


(11.) INSTALL NIKON NX:

(i) Install fresh download of Nikon Capture NX v1.2 (full version installer)
(ii) Restart computer system


(12.) SERVICES:

(i) Install "Startup Control Panel" from TEMP
(ii) Enable all startup programmes - REVERSE my steps in Message (40)(iii)(a) & (b)
(iii) Enable all (third party) running services using the reverse steps at (10.)(i) above
(iv) Restart computer system
(v) Open Control Panel > double-click "Startup" - the control panel installed at (12)(i) > enlarge panel window to convenient size > left-click each startup tab, one at a time, and configure as required. Settings are a matter of personal choice - these are mine:

* Startup (user): right-click ALL entries and delete
* Startup (common): right-click ALL entries and delete
* HKLM/Run: right-click ALL entries and delete - EXCEPT Antivirus & Firewall protection (if existent)
* HKCU/Run: right-click ALL entries and delete
* Run Once: right-click ALL entries and delete
* Deleted: Keep ALL entries for in the event you wish to reinstate any process


(13.) SYSTEM:

(i) Move utilities from TEMP folder to your normal download directory for future reference
(ii) Repeat Step (9.) above
(iii) Repeat Step (7.) above ... but only need to run NTREGOPT once on this occasion
(iv) Restart computer system
(v) Repeat Step (1.) (ii) above

DONE!


========== CONCLUDE: STEP-(C)(*6.) to (*13.)(*Revised) ============


Okay then, Guy, you're good to go...



Succat

Hello Succat!

Are we close to the end of the adventure? It feels so....

Before I begin, a few notes. Yes, my printer is an HP. I will uninstall it first. Do I reinstall after lucky (13.)?

Scan Disc on my computer is named Check Disk. Run time is usually slightly over two hours -- just so you know.

I think I am ready to go. Strapped in?

Guy

PS Hiccup -- again! When I went to uninstall the printer, I noticed that Microsoft .NET Framework 1.0 Hotfix (KB930494) had reinstalled itself (?) on the 21st. I will wait to hear from you (and going any further) about whether or not I should uninstall it again.

Will this bird ever fly?

Guy


PPS (Nikonians, the website is running very slow from here and sometimes not at all today.)

"...Strapped in?"

LOL!!!

(Nuh...where's the fun in that?!...look ma' - no hands!)

~chuckle~chuckle~

_________________________________________


Okay, a quick response regarding your notes:

* Re-install the printer *after* you have trialled your rebuild

* Scan disc = check disk; gotcha

* Okay...hit the button!



Succat


EDIT...Guy, seems like we posted past each other; there's a 3 minute difference between this post and your previous "hiccup" post.

Please check back in 10 minutes, I will give the matter some thought...

Right, I'm back. The answer to your "hiccup" proved to be a no-brainer as it happens; within seconds of logging off, the answer came to me:

You may recall a previous question..."Are (these) a magical incantation or computer science?" (your post at #12 refers)

Well, so far it's all been science - dry, horrible stuff - so let's have some magic, huh?

I will recommend you allow the "hiccup" to stand (yes, keep the Hotfix)

My reasoning is quite sound, but unprintable (some things simply escape the mundane!)

So...unbuckle your seat beat...hit the button...and...fly





Succat


~
Come to the edge, he said.
No! No! We are afraid
Come to the edge, he said.
So they came, he pushed them - and they flew

(Anon - Old French Saying)

Okay, Captain, My Captain --

1. Old French Saying... yes.

2. Magic... yes.

3. Mundane/obvious... no.

Signed,

Guy "the button"

Is this the same as talking to myself -- whoever that is.

The time here is 2:30 AM, as in morning. My guess is that where you are the time is about 5:30 PM on a partly cloudy, semi-tropical evening.

I have many thoughts and some questions for -- later.

Just now I am at (13.)(ii). I think I may start this 2 hour extravaganza, get some rest (sleep) and pick up later -- perhaps when you are sleepy.

"Okay then, Guy, you're good to go..." I love this....

Guy

Hello Succat,

I've been working on the issues here for about three hours, without any luck (or anything else).

When I finished the process this morning only one thing had changed: instead of NEF files ballooning to 272 MB when sent for printing, they're only ballooning to @ 70 MB. The printing area is still less than the paper size area, e.g., 4x6 in. paper has a 3.74 x 5.74 printing area.

I hope you've had a good night!

Guy

~



Hello Guy, don't you sleep?

~chuckle~chuckle~

Okay, well that was loads of fun so let's see what we got: the "ballooning" of NEF files sent to your printer has gone from 272 MB (previous) to 70 MB (current) ... Nuh! Sorry, we can't fly that and call it progress, no matter what the spin

I need give the matter some thought and will come back with suggestions

In the interim:

(i) please run the ".NET Framework Verification Tool" downloaded at STEP-(A)(2)(i) and report back your results

(ii) I have never sent a NEF file to the printer. You might like to try sending the same image to the same printer in, say, TIFF format and also the JPEG format in addition to the NEF format and report results, including size of original RAW file

I admire your coolness under fire...



Succat

Hello Succat,

Very good to hear from you. Always a wonderful pleasure....

I ran the verification tool, which verified .NET Framework v2.0 (x86). It created a long log file the contents of which I cannot explain to you. Is there something I ought to look for or copy?

I sent a 4.4 MB TIFF for printing that exploded to 83.3 MB. Not bad, eh?

Why do so many photographers create additional files like JPEGs and TIFFs from RAW files to do their printing? I presume they keep the edited RAW as well as the new JEPG or TIFF(?)

Mysteriously,

Guy

Hello Guy,

(i) please copy & paste the verification results of your .NET v2.0 into the body of an email and send it to me

(*address below)

(ii) Would you also scan .NET v1.0 and .NET v1.1 then send me the results?

Should you need help with this - a useful text document (setupverifier_readme) would have been enclosed in the .ZIP download of that utility

(iii) This "ballooning" of your files when sent to printer is outside my experience (I don't send files to the printer in my line of work) and your problem remains a mystery to me

In any event...first thing we need do is establish that .NET Framework is correctly installed on your system and I will wait your scan results

Cheers!



Succat

(*) maewyn_succat (at) hotmail (dot) com