Hi Richard - apologies... I may have misunderstood the issue.
I'm not an expert on Bridge, but if I understand it properly when you export a directory (you are editing) to cache, it builds that cache right in that directory; I can see it when I list. This helps with loading that directory again when I come back a few hours later, because it is referring to the cache that is right in the same spot.
Now that being said, I can see that I have not really addressed your problem of Bridge loading slowly.
Mine does not open like lightning, but it's reasonably fast. I'm using CS2, ACR & Bridge, with the program files installed on my 160GB C drive. No images are stored on C - they all reside on the 250GB internal (and physically separate) scratch drive. Everything gets defragged AT LEAST once a week as I do a lot of editing and deleting.
My workflow is RAW files on CF Card =>Card Reader=>Win Explorer, and then I just do manual copy and paste into the Client Named subdirectory on the scratch drive; not very elegant, but thorough
.
Richard_Miami wrote in post #3325286
SAPearl -- thanks for the tip. However, I am a bit confused (like always). The Export to Cache would be something done while Post Processing yes?? After Bridge is open? Remember that my issue is getting Bridge to open. Once I get past that, I am good to go.
My normal workflow for large directories is Image Ingester to Bridge to ACR to CS3 - where in that flow does Export to Cache take place? If it's only a few shots I skip Image Ingester (d/l manually or thru Bridge from the card reader) and then use Bridge to get organized. The issue is not with the card reader.. if I open Bridge first, having it pointed to any of my hard drives, it is still very slow to open. Hope this makes sense.