Doesn't appear DB is updating properly

[lnh]

I have a couple of different Photo Supreme databases. Today I wanted to access one where the files sit on a Synology NAS. PS wanted to update the database to be compatible with the latest version running on Windows 8 Pro 64 bit. After getting to the third update dialog box, the process stops showing progress as shown in the attached picture. Several times every minute a file (idimager.cat.db-journal) appears for a few seconds and then goes away. So far I've let it sit doing this for several hours, but to me it isn't clear if it's still making useful progress. If it's actually still working, it feels like the process could take years. What should I do?

[Hert]

Keep it running, don't kill it. Eventually it will finish

[lnh]

Thank you. After several hours it did indeed finish.

If there is some way make the progress dialog show progress rather than look like a hung program that would improve the user experience. Seeing the journal file come and go was the only reason I thought it might be still working. A progress bar which sits still for 4+ hours makes you believe something might be wrong.

[Hert]

The dialog tells you not to kill it and if you would have then, as also mentioned in the dialog, you would have a risk of about 80% that your database got corrupted as a result.

Windows has bad ghosting implementation, it shouldn't tell you that an application is "not responding" when it's still working. Sometimes an application needs to process a single task that takes a long time (as in this case) and then the application waits for the task to complete and Windows shouldn't then say that the application is stalled. That's bad design from the friends in Seattle. An application can disable ghosting, but then can't re-enable it and I don't consider having ghosting disabled completely is a good thing either.

Luckily almost every Windows user these days knows that a "not responding" message from Windows can't be trusted, always check processor usage for the process first to confirm that it indeed doesn't do anything. With a good Ghosting implementation you shouldn't have to. Unix systems (like MacOS) have a good ghosting implementation, and Windows has had these ghosting issues ever since they first supported it (was it in XP?)