We're trying to update machines running Mac OS X Leopard 10.5.2 from VectorWorks 12.5.0 to 12.5.3.
All users are network clients to Mac OS X Server 10.5.2 with network home folders.
Every time we go through the installation process, when asked to choose an existing VectorWorks folder the installer always responds with a message saying "You have not selected a location containing a copy of VectorWorks to be updated".
The 12.5 copy we have installed works normally (apart from the bugs that 12.5.3 is supposed to fix, i.e. being able to see lines etc.).
I've repaired permissions, cleared and ACLs on /Applications and /Library, tried the big 12.5.x to 12.5.3 update as well as the smaller version and also tried to update to just 12.5.2 first. None of these work, all responding with the same error.
Any ideas? Is it possible to do the install by hand (copy individual files)? At least then I could script it and roll it out across the network.
Why on earth is this install process so painful, particularly for network admins? The dongles weren't enough punishment?
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
SJT
Hi All,
We're trying to update machines running Mac OS X Leopard 10.5.2 from VectorWorks 12.5.0 to 12.5.3.
All users are network clients to Mac OS X Server 10.5.2 with network home folders.
Every time we go through the installation process, when asked to choose an existing VectorWorks folder the installer always responds with a message saying "You have not selected a location containing a copy of VectorWorks to be updated".
The 12.5 copy we have installed works normally (apart from the bugs that 12.5.3 is supposed to fix, i.e. being able to see lines etc.).
I've repaired permissions, cleared and ACLs on /Applications and /Library, tried the big 12.5.x to 12.5.3 update as well as the smaller version and also tried to update to just 12.5.2 first. None of these work, all responding with the same error.
Any ideas? Is it possible to do the install by hand (copy individual files)? At least then I could script it and roll it out across the network.
Why on earth is this install process so painful, particularly for network admins? The dongles weren't enough punishment?
Sam
Link to comment
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.