Mike@wsc

OK, I looked at the initial hang and compared it to the date of all of the files within the vectorworks directory. There is one file that corresponds to the initial crash called Architect-v which looks like a quicktime resource file. I moved that out of the directory and the application started again. Do you want a copy of this file. Let me know. Thanks, Mike

Here is the initial Hang; Hanging Application vectorworks.exe, version 12.5.2.5505, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Now, everytime I try to start the VectorWorks applications, I receive; Faulting application vectorworks.exe, version 12.5.2.5505, faulting module quicktime.qts, version 7.0.2.120, fault address 0x000fb7c5. Thanks, Mike

Kaite, I m a local IT support person for an architectual firm that is having this same problem. It starts with a Vectorworks application hang, and then it will not start faulting quicktime as the problem. I reloaded the OS for this person and repatched vectorworks to v12.5 with the version of quicktime that comes with V12.0. In less than a week, the vectorworks hung up and and will not start faulting quicktime.qts as the problem. If I completely uninstall both vectorworks and quicktime, includig registry entries, and then reload them, it will run for a couple of days and then hang again. I think its a bug in Vectorworks 12.5. Let me know if you need any more information. Thanks, Mike Casey