64 Bit Windows Photo Gallery - Slowww...

Having upgraded my mainboard, CPU and RAM, I thought this might be a good time to go 64 bit on my production machine. For the most part, I'm very happy, but I find WPG is extremely slow to start up.

before I upgraded, my x2 4400 in 32 bit VU opened WPG almost instantly. Now, with a Q9550 on 64 bit VU, it takes 13 seconds to open. This happens even when opening, closing and opening again to see if it opened faster from RAM.

Once open, it's very fast and responsive. I had disabled indexing while I set the machine up, so I thought that might be the issue, but re-enabling it made no difference (after 48 hrs.)

I googled around, but this doesn't seem to be a common issue. One thing I liked about WPG is that it opened fast and I use it to quickly search reference images tagged for business.

Thanks (relevant specs below),
James

GA-EP45-UD3R mb
Q9550
8 GB G-Skil,
VU 64

Could be your 64bit Premium at fault. there are a few anomilies reported with it.

If it was quick on your 32bit, then that points at the 64bit OS,

I use the Ultimate 64bit, which seems much more "in tune" with the system.

wysiwyg said:

Could be your 64bit Premium at fault. there are a few anomilies reported with it.

If it was quick on your 32bit, then that points at the 64bit OS,

I use the Ultimate 64bit, which seems much more "in tune" with the system.

Click to expand...

Hi wysiwyg,

I agree with that assessment...I can't see it being the HW change. However, a search reveals that this must not be a common issue. A few other things I've tried: changing the write caching settings for HDs in DevMgr, unchecking the 'Check for Updates' setting in WPG options.

When starting WPG, during the 13 seconds it takes to load, the HD is thrashing the whole time. There have been no significant changes in the number of images, and the images are on a separate HD. Thanks for your thoughts, and any other ideas welcome.

James

Just a little more info that might help:

To provide a little more info, running task manager shows (when it starts) that WPG's memory usage starts at 10k, then incrementally rises (i.e., 10k, 10,600k, 11,100k, 11,853k, etc.) until it gets to about 15k, at which time WPG appears (about 13 secs later), then the mem usage jumps to 24,xxxk, then to above 28k, finally resting at 29,xxxk.

Also, an instance of dllhost.exe appears about that time and then disappears about 5 secs later.

I don't know if this is the normal start up process (sans the lengthy time), but perhaps someone will recognize an issue.

Anyone?