Is there a way to trigger an automatic catalog backup when the program exits? Lightroom has this capability and it saved my butt recently.fbungarz wrote: My database is now 8.7 GB and doing regular backups for a file that size is a real pain!
Phil
Is there a way to trigger an automatic catalog backup when the program exits? Lightroom has this capability and it saved my butt recently.fbungarz wrote: My database is now 8.7 GB and doing regular backups for a file that size is a real pain!
I would REALLY love incremental backups...Is there a way to trigger an automatic catalog backup when the program exits? Lightroom has this capability and it saved my butt recently.
Well, I also used IDI many, many years (since 2006!). As long as I can remember that progress bar ALWAYS froze on me and it was a complete nuisance, because it stayed always in front of ALL other windows. So, not only was it impossible to continue using IDI, one could not use ANY program at all during backup or compact. Both processes also took much, much longer, in fact backup took so long that I eventually no longer used the built-in backup capability of IDI, but instead got in the habit of running SyncBack to just copy these files.In the 7 years I used IDi, I never ever had IDi freezing on compacting and/or backupping and the progress bar was indeed a nice feature and ALWAYS worked for me in IDi also.
The progress window in IDi prevented you from doing other actions with the software and I think that was a better solution, especially when it makes the software freeze or crash.
It's really easy on my system to determine that Supreme is compacting. I simply look for the operating system's blue circle that has replaced the cursor. I can also see the display at the top indicating that the program is "not responding."fbungarz wrote:I do agree the warning message that PSu is compacting is completely useless, because it is so small and inconspicuous that it might as well not be displayed at all! At least make it orange or some other color or use a larger font!
Where in the registry is that added? In the Catalog section? Might give it a try...fbungarz wrote:
BTW - since I am a bit paranoid, I prefer running PSu in synchronous mode (see http://www.senoiaphoto.com/psu).
Simply run it as a script from within PSu and the parameter is turned on (tools -scripter - paste the code below and run it):Where in the registry is that added? In the Catalog section? Might give it a try...
Code: Select all
WriteToRegistry ('', 'Synchronous', 2);
Say ('database now in Synchronous Mode');
Code: Select all
WriteToRegistry ('', 'Synchronous', -1);
Say ('database no longer in Synchronous Mode');
Agreed. When I got this computer and started having the problems (blue screens), I visited the forums to see if others were having similar issues. PSU ... no. Lightroom ... there were a few. Clearly it wasn't widespread.Mke wrote:Chances are it isn't PSU or Lightroom directly causing the problem, but it may be that they use a common driver, or that they are two applications that both push your PC hard and expose a hardware issue.
Thank you for the suggestions! I will try them. I have tried MemTest86. I have updated drivers. The workaround I have figured out nearly eliminates the problem, so something is either not running in that situation or not interfering.Mke wrote:My top tip would be to install WhoCrashed ... and optionally turn on Windows Driver Verifier
How are the temperatures running on your machine, especially under a heavy load? Here's a handy utility for seeing what's going on: HW Monitor. If you really want to stress your system, run Prime95 while monitoring your temperatures. Prime95 makes your CPU run at 100%.When I got this computer and started having the problems (blue screens)...
Note that even if it passed the recommended 7 to 8 runs, there could still be an error (as there was in my case), so don't rule out using it (or one of the alternatives) some more...sanphotgn wrote:I have tried MemTest86.
Stephen,Stephen wrote:Computer is NOT under load, but PSu keeps locking up (beach ball in Mac terms).
I am importing small groups of maybe 50-60 files from one folder to another and renaming them in the process. Is that an unreasonable task to request? Everything is clean, database + thumbnails compacted, etc. Any clues?