Miles500 said:
Bill,
I am really pleased to hear that version 3 is stable. I was simply reporting what others had said to me
I suspect what you are seeing is that every version of every product has bugs that only affect a small number of people, but the people whom those bugs naturally affect will perceive the product as unstable. It's difficult if not impossible for any one user to put into perspective just how widespread the problems might be, but spend enough time here in the forums and you might get some sense
I for one haven't seen the problems described here on 2.5, but I do perceive it crashed and hung much more often than other versions of ACDSee, and probably more often than "average" across all applications I used. Nothing that prevented me from getting work done with it, though - on restart, all was well again every time. Between other people reporting the same thing (relatively frequent but "harmless" crashes or hangs), and a small number of people for whom 2.5 just would not work at all for some reason, I definitely get an impression of Pro 2.5 being less "stable" than most versions, although certainly perfectly usable for most.
Pro 3.0 hasn't really been out long enough to get that kind of perspective. My personal experience is that it crashes or hangs *much less often* than 2.5 did, so my first instinct would be to call it *much more stable* than 2.5. I certainly see that others are having issues getting up and running, although it's still kind of hard to get a handle on how much of that is just because, as a new product, it has seen a disproportionate number of new installations in the past few weeks. But at this early stage, I would say my read of the forums suggests 3.0 is indeed more stable overall than 2.5 was - not that is any consolation to the people who are being affected by whatever bugs there are.
Anyhow, regarding getting 2.5 running better, I don't know what other kind of advice support has given, but my standard tricks for resolving db problems (occasionally my own, but more often ones others have reported here) include
[ first, back up db by simply making a copy of the folder ]
- Optimize db and try again
- If that doesn't help, rename db folder, restart acdsee so it starts with a new empty db, then copy files from the old db into the new to see if you can get it to a working state (seems potentially scary, but there's nothing to lose since you're keeping your original, and it *has* proven effective surprisingly often)
- If that doesn't help, and you've been religiously embedding all your db info into your files (using "batch set information" to write to iptc or "embed database information" to write to xmp), then go back to the empty db and run Catalog Files over all your images to rebuild the db
- If you don't have your db info embeded, or if that didn't help, return to original db, export entire db to a text file, again get acdsee to restart with a new empty db, and import that text file, then run Catalog Files as necessary to rebuild thumbs
Pretty much withut fail anyone who has tried all these steps meets success somewhere along the way. Good luck!
Posted On October 16, 2009 - 04:18 PM (1 month ago) (
Permalink to this post)
New Content Since Last Visit
No New Content Since Last Visit
