One other thing you can try and already have more than likely is a
smaller cache size and moving your cache to a fast secondary drive
away from the OS drive.
It's getting a little faster which I'll address later in this email, but as to the above, yes, I played with NX2 cache settings and unlimited is the way to go with my system. Any limitation of cache size/files causes my thumbs to fail to render as well as lockups on many things including exit, so that's not the solution in my case.
As for .NET, I know some have had nightmares with this and I'm not
sure why. The client .Net 2.0 can cause issues when installing
orginal versions of 3.5 over the top and that may be the problem your
having.
I think the only thing .NET 3.5 might gain is some type of minor fix/update to .NET 2.0 since NX2 does not make use of .NET 3.5. I have .NET 2.0 Service Pack 1 installed which I suspect incorporates any files from .NET 3.5 that may be beneficial to NX 1.3 or NX2. First I'll try a repair of .NET 2.0. If that doesn't help I'll try uninstalling .NET 2.0, uninstalling NX2, then resinstalling NX2 allowing it to do with .NET 2.0 as it wishes. As far as I can tell from .NET documentation from MS it is typically branded by the vendor, so that may be an issues with NX upgrades for some, depending on platform. And clearly if the .NET installation gets corrupted some how in the process of installing the vendor software it wreaks havoc.
The links below may help. Use the information within at your own
risk. I would suggest a restore point prior to making changes. I
personally, didn't have to deal with these issues, as my install was
smooth on both my desktop and laptop running XP Pro with SP2. I did
say a little prayer prior to installation
How to remove and troubleshoot .Net 2.0.
http://support.microsoft.com/kb/908077/en-us
Where to get .Net 3.5
http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en
Thanks Ray, this is my last resort step and I'll likely skip installing 3.5 because I don't think I'll gain anything from that and I stand a risk of corrupting .NET(if it's not already). I'm entirely familiar with this routine as this is how I repaired my corrupted .NET installation a few months back which occurred after attempting to install .NET 3.5 on top of Nikon's .NET install. ;-) I have it bookmarked and will go through the troubleshooting MSKB article if necessary. Honestly it's not a difficult fix to follow and can clean up a lot of inconsistency issues with .NET installation. Someone back then chastised me for recommending this fix to others saying it was a Nikon issue and they should handle it. All I know is it worked well for me in the past as a last resort when the symptoms led me to believe my .NET installation was corrupted.
Now, as to my apparently starting to enjoy a little more speed for unexplained reasons ... after tweaking various settings in CNX2 and my XP paging file (let system decide amount for paging file) I think it's picking up a little in speed. After forcing myself to suffer through the sluggishness and edit a few files like I normally would (albeit painfully as regards rendering speed) I think it's starting to go a little faster. It looks like maybe CNX2 is building some sort of library in it's temp or cache files based on user routine and most frequently used algorithims, or something to that effect. Sounds weird I know but it sure feels like that's what's happening. I have no other explanation for why now it's a little more snappy and responsive other than that. It's still slow on load and save, which I'll try to continue to tweak for improvements, but my editing steps including selective editing steps, use of the mask overlay and some other things are faster than yesterday. Go figure. It's not a difference in processes running on my machine in the background to the best of my knowledge as I tried hard to rule that out as I've been testing things. I honestly think it's building temp files and cache files that call routines more quickly after I've used them a few times on a few photos. Rather odd, but I remember thinking this in the past upon upgrading NX which stared out sluggish and later picked up speed. Since I typically cleared out my cache on NX 1.3 often I'm thinking the temp files might be a better candidate for this? Don't know, only know going through the routine on a few files seems to have improved speed. Heck, maybe I'll try running a few batch processes to see if it improves my load and save times.
Thanks Ray! If I find any new tricks to speed things up for others on slow platforms I'll pass them along. And as I suspected, now that it's not so painfully slow I can learn to like the new interface and features. Have to get the nuisance issues out of the way to do that.
Kelley
--
The start of my galleries:
http://www.zenfolio.com/kshoffman
Visit my Belgian Shepherds:
http://www.basquelaine.com 
