199,030 users have contributed to 43,150 threads and 258,878 posts.
In the past 24 hours, we have 6 new thread(s), 14 new post(s) and 61 new user(s).
JWL:
Thanks for the tip. As you suggested, I installed the Syncrosoft update, then installed VE 2869 - - in the normal fashion, without trashing anything else.
The file in question opened without incident. Hopefully it will open tomorrow in a similarly unproblematic fashion.
Many thanks,
Stephen
Alain:
Everything worked well after I installed the Syncrosoft update. However, the next day, when I launched VE (2869) as a standalone it froze after launch. I then rebuilt the startup disk's directory with Alsoft's DiskWarrior 4. DiskWarrior claimed to have found only one problem which it reported as follows: "Incorrect values in the Volume Information were repaired." (In my experience, DiskWarrior seems not report everything that it does - as there have been a number of times when somethig was wrong and DiskWarrior did not report finding anything, but the problem, nevertheless, disappeared after the directory was rebuilt.)
Subsequent to rebuilding the directory with DiskWarrior, VE (2869) has functioned without incident (except that the license checking procedure takes a little longer than usual.)
Steve - I was the one withthe problem with VE in DP 5.13 (G5 d1.8 and 10.4.11) .... it would freeze or DP would freeze or both when opening VE or a project with VE in it (I am using VE just as a plug in in DP) ....after installing the syncrodoft update it worked fine first time - now a week or so later it is mostly fine but still crashes occasionally on startup. It's not enough to be too much of annoyance - repair permissions and a reboot usually does it (even just force quitting and a relaunch has also worked). If it was crashing after getting stuck into a project then that would be more annoying, but once VE is 'alive' it's always fine in any project right up until I shut down my mac.
Anyway if you have further any insights / cures I'd be interested to hear - likewise if I do I will post here too (although I am no good at sorting these sorts of things so don't hold your breath!)
ps Ah, JWL you must be F by another name! ;)
Hi:
My basic advice is obtain a copy of Alsoft's DiskWarrior 4 (now 4.1), start from the CD (which takes several minutes) and use DiskWarrior to rebuild the directory of the startup disk. As I note above, this appears to have a more permanent positive effect than downloading the new license. DiskWarrior, as I have said many times on these forums, is the "must have" utility for Mac users - - it has fixed many otherwise unfixable problems for me over the years.
migot, fsck means File System ChecK - see this page for details ... as you can see a little bit down the page it checks for consitency of the filesystem as such, but not for permissions as expected by the operating system
christian
Alain:
As far as I can tell, rebuilding the disk directory with DiskWarrior is not the same as starting as a single user and peforming a fsck -fy and reboot or starting in "safe" mode which does something similar. Again, my experience is that DiskWarrior has been able to fix problems that these procedures did not fix. In one, rather memorbale case, it took 14 hours, but DiskWarrior successfully retrieved a directory that every other utility declared to be damaged beyond repair. In another case. after I installed Altiverb 6, Logic could not see it and kept issuing error messages to the effect that Altiverb 5 was missing. No other procedure fised this, but, after rebuilding the directory with DiskWarrior, Logic immediately found and validated Altiverb 6. I've had many similar experiences. Do as you wish, but I would not want to be without DiskWarrior. (And, no, I am not an employee of Alsoft.)