Posted: Mon Mar 31, 2008 1:28 pm Post subject: Conflict with VectorWorks 10
After downoading 2.2.3, I noticed that Vector Works 10, when operated together with NeoOffice, would sometimes quit without warning.
I also noticed today - this after hours of using the spreadsheet - that the menu bar would not be shown when no file is open. This happend once; after quitting and reloading did not happen any longer.
I have now downloaded patch 3, will see.
Joined: Jun 16, 2003 Posts: 10952 Location: California, USA
Posted: Mon Mar 31, 2008 1:50 pm Post subject:
Sorry, but that makes no sense. On Mac OS X, one application cannot crash another application. In fact, neither application can access the other without both writing code that cooperatively talk to each other. Mac OS X keeps them separate and "fenced off" from each other.
Possible issues are:
1. Vector Works 10 is crashing due to bugs in its own code.
2. Vector Works 10 is crashing due to bug in a system hack.
While we cannot help you with the first, you can see if #2 is the cause by opening the /Applications/Utilities/Terminal application, copying the following lines into the Terminal window, pressing the Enter key, and then posting the output:
Code:
ls -l /System/Library/SystemConfiguration
ls -l ~/Library/InputManagers
ls -l /Library/InputManagers
Patrick
Last edited by pluby on Mon Mar 31, 2008 1:59 pm; edited 1 time in total
Joined: Apr 25, 2006 Posts: 2315 Location: Montpellier, France
Posted: Mon Mar 31, 2008 1:54 pm Post subject:
pluby wrote:
While we cannot help you with the first, you can see if #2 is the cause by opening the /Applications/Utilities/Terminal application, copying the following lines into the Terminal window, pressing the Enter key, and then posting the output.
You mean something like this:
Code:
ls /Library/InputManagers/; ls ~/Library/InputManagers/
Edit: See Patrick's edited post above; please ignore my Terminal command.
Last edited by Samwise on Mon Mar 31, 2008 2:07 pm; edited 1 time in total
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Mon Mar 31, 2008 9:37 pm Post subject:
Also don't forget that VectorWorks 10 seems to be an older software version there. From their website it seems they're up to version 12 or 13 now. Some system updates can cause older versions of software to stop functioning reliably, something with which we experience with Neo.
Yes, I know the "fenced off" (nice definition) concept. But it is there. Never had a problem with Neo Office - VectorWorks10 before, just after installing 2.2.3. (same machine, BTW, a MacBook Intel with 10.4.9). Bah, we'll see. I have also to upgrade VW 10 to 2008 as soon as I find the time to Applecare my notebook - combo does not work.
Joined: Jun 16, 2003 Posts: 10952 Location: California, USA
Posted: Tue Apr 01, 2008 12:44 am Post subject:
If you can, definitely post the output of those Terminal commands in my earlier posts. Also, don't discount the effect of limited memory. NeoOffice is not a small application so it will use a good chunk of memory which may make bugs appear in applications that would not normallly show up when memory is not such a scarce resource.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
Forum FAQ
Search
Usergroups
Profile
Private Messages
Log in
