Since Apple has released Mavericks, Vectorworks 2011 no longer runs on Macs with 10.9 / Mavericks – although this has been widely criticised, Nemetschek is most likely to stick with its policy to only provide support for the last 2 versions of Vectorworks.
An overview on which version runs on what is available here.
Currently you only have the following options to deal with this situation:
1. upgrade to the latest version of Vectorworks;
2. downgrade your Mac(s) to 10.8 / Mountain Lion (if you still have an installer), we have done this successfully on a variety of models – however the latest MacBookPro11,2 series can no longer easily be downgraded and it is only a matter of time before the new iMacs can no longer be downgraded either;
3. if the above is too radical, setup a bootcamp partition as explained here.
4. use Fusion or Parallels to setup a virtual instance of 10.8 and run VW2011 inside that – we must admit this is not ideal as VW2011 seems to have some speed issues when virtualised…
To convert a mobile (a.k.a. portable home directory) to a local user account do the following:
If you are using network user accounts on 10.7 / Lion and later, you will also have to do the following:
1. login to network user account;
2. go to System preferences > Users & Groups > Current User > Mobile account: Create
3. click on ‘Create’…
4. when prompted confirm with user network account login details (screen goes blank…. wait – do not interrupt);
5. once back at login screen, log back in – check that when creating new folders on desktop they show also in ~/Desktop…. also note in Users & Groups Network has changed to Mobile
6. log out of local account, then continue as described below…
1. in a local Administrator account, open System Preferences > Accounts
2. select and delete the User account, by choosing ‘Don’t change the home folder’;
3. rename the ‘deleted’ user account, via Terminal to its previous shortname…
sudo mv /Users/jdoe (Deleted) /Users/jdoe
IMPORTANT: Please be very careful when using the sudo command!
4. go back to System Preferences > Accounts and create a new local User account by utilising the previous mobile accounts details, e.g. John Doe / jdoe;
5. when prompted choose to utilise the existing home folder – all permissions will then be set automatically;
6. login as the new user and check when prompted create a new keychain;
7. check that all data has come across, then change the users PHD settings in WGM to ‘none and also remove the PHD user folder from your server;
We have started to use the excellent Carbon Copy Cloner (CCC) to sync various Folders on a File Server to a dropbox account to share its content ‘automatically’ with an external party.
Initially we had some problems, as we had simply scheduled a Backup Tlan to run every hour, which resulted in a couple of errors regarding hidden files that dropbox seems to generate for its syncing process and which stalled the CCC backup.
Thankfully the support for CCC is excellent and we ended up getting a solution directly from Mike Bombich, which you also might find useful.
To get it working properly you need to stop and start Dropbox via pre / post flight shell scripts, which can be attached to the Backup Task inside CCC’s > Backup Task Scheduler > Before & After panel.
osascript -e 'tell application "Dropbox" to quit'
sudo -u YOURNAME open -a "Dropbox"
Simply copy and paste the scripts above into the Text Editor of your choice, amend with your accounts shortname, save them as plain text with .sh as extension, then attach them to your CCC Backup Task.
Regarding the ‘sudo -u’, Mike Bombich writes…
“CCC’s pre and postflight scripts run within the root user security context, so there are some limitations placed on the use of AppleScripts and specifically the “open” command. Precede those commands with “sudo -u yourname “(replace “yourname” with your account’s shortname) and the script should work fine.”
We can confirm it does work perfectly.
When setting up Google’s 2-step authentication, you will also have to create application specific passwords for apps which are not ready to use this new process natively, e.g. Apple Mail.
Once you have created app-specific passwords, to make later identification easier you might want to name these based on the device and app, e.g. iMac Apple Mail, etc.
On the respective device you will be prompted to enter your new password, however also check under Apple Mail > Preferences > Accounts > Account Information that the proper password is used for both the Incoming and Outgoing Mail Servers.
At this stage you might think that you are done, but it really depends on how your Gmail (Apps) account was originally setup. If you happen to get an error message in Apple Mail that reads…
‘Unable to connect… The server returned the error: Application-specific password required: http://support.google.com/accounts/bin/answer.py?answer=185833 (Failure)’
…then open System Preferences > Mail, Contacts & Calendars > YOUR GMAIL ACCOUNT and provide your app specific password here as well, in fact you will be prompted as soon as you select YOUR GMAIL ACCOUNT.
Posts tagged with ‘10.9’
macinteract > 10.9