So now that Cubby is pulling the rug out from under it's users, what sync service et al are you moving to?

I was getting all ready to try it based on recommendations from Donation Coder.

Apparently, Windows will be getting a package manager sometime in the future that will use Windows PowerShell.

I have it installed, but have never tried to use it as anything but a CLI.  I think that should change and I have done multiple searches for resources to help me start to learn.

However, seeing as though one of my favourite online communities is stuffed with clever programmers (erm, that would be you-all if you didn't get that reference ;)), I thought it prudent to ask here as well.

I did a search on the forums and while there were a lot of hits, they were pretty old and I couldn't find one directly related to learning, so any suggestions are appreciated.

I have a client who has a spanking new PC and is using Lightroom 4 on Windows 7 64bit.  She has moved from a previous version on Windows XP, details unknown.

Lightroom has some very irritating behaviour that she has not encountered before.  When typing in a dialog or other text field within the program, it often suffers from some sort of "outage" as it "goes to sleep" for 15 to 20 seconds. Sometimes, Windows even displays the partly opaque "white screen", which generally indicates the system is trying to cope with demands on the system.

During the outage, the system continues to capture keystrokes as evidenced when it comes back to life - all keystrokes captured during the outage are subsequently shown in the text field.

Original observations led me to conclude that something like Windows Indexing might be playing a part - the behaviour very much looks as though the system is struggling to index something or struggling to search an index of something, perhaps a repository of auto-name-completion information. It's difficult to explain.

In order to eliminate some of the typical Windows irritations, a number of configuration changes have been made, but none have made a difference.  Co-workers have suggested that there might be some configuration options within the program itself that can be tweaked to smooth out the program's performance.  I am in the process of researching those at the Adobe site, specifically looking through their forums and some of their troubleshooting documents.

Specifically, one co-workers was able to resolve another clients Adobe problem (not the same software) by moving some resources like a disk-based cache to another physical hard drive.

As I am not at all familiar with the product, I'm hoping someone here may have gone through the same experience or might be a frequent user of the software and therefore be more aware of what's at play here.

As usual, any help, pointers, or references are very much appreciated!