Skip to main content

VMware Fusion 2.0.6 + Alibre Design 12 = Good News

For the early adopters who ran Alibre Design on Windows in VMware Fusion virtual machines, VMware 2.0.6 brings some very good news: the dreaded stuck-red-highlight bug is gone.

When you move the mouse cursor, Alibre's 3D views highlight the face or edge closest to the cursor. In VMware, this red highlight would be stuck -- or rather, it would only turn ON, but never OFF.

The issue was present in every VMware 2 up to and including 2.0.5, and in every version of Alibre Design starting with at least 10. I only tried it on MBP with NVidia graphics, so it might have been an NVidia-only issue.

I was very nicely surprised after updating VMware to 2.0.6 today. Not only did networked Windows startup take perhaps 25% less time (somehow), but Alibre's workspace starts up much faster (feels like 50%) and the workspace display is bug-free, as far as I can tell.

This, coupled with significant speed improvements in Alibre 12, means that a very solid parametric CAD is available for OS X on Intel machines for ~$300 extra over the per-set price on Windows. That $300 factors in the eBay cost of Windows XP license, and the cost of a VMware license. Never mind that you could get a basic Alibre seat for $99 in a promotion that just expired a few days ago. Sweet!

Update: things still work just fine with Fusion 3.1.1 and Alibre Design 12.1 - as shown in the picture above.

Comments

Popular posts from this blog

Both INCLUDEPATH and DEPENDPATH are usually needed in qmake .pro project files.

qmake, the build tool provided with the Qt toolkit, converts project files written in its own mini-language to platform-specific Makefiles.

This process includes adding necessary dependencies to the Makefile, so that changes in source files trigger rebuilding of the outputs that depend on said sources.

If your project is spread across directories, you'll likely add an INCLUDEPATH line to your .pro file so that the #include directives look sane -- say #include "library/foo.h" instead of #include "../library/foo.h". This can be done by adding INCLUDEPATH += "../" to the .pro project file.

This, by itself, doesn't cause the files in include directories to be treated as dependencies. This is a sane default, since you likely don't want to rebuild your whole project if a system library changes -- assuming, of course, that the library is meant to stay binary compatible between releases!

Thus, if any of your source files references a file from somewhe…

Asterisk 1.8 with SELinux on RHEL 6 / CentOS 6

Asterisk 1.8 is the current long term support (LTS) version of Asterisk. You can find it in the atrpms repository. Using atrpms requires a bit of ingenuity, since you must enable yum priorities. Here's how I've set up my yum priorities and excludes to play well with RHEL (lower priority is higher):

# /etc/yum/pluginconf.d/rhnplugin.conf
priority = 9

# files in /etc/yum/repos.d - current samba and subversion override those of RHEL
sernet-samba - 5
wandisco - 6
rhnplugin - 9
centos-base - 20, includepkgs=xfs* fftw-* glpk-* dell-firmware-repository - 30 dell-omsa-repository - 30 rpmforge-repo - 50, exclude=hdf5*
epel - 60, exclude=dahdi* atrpms - 70
I'm using a bunch of non-redhat packages, including Asterisk, recent subversion, octave, xfs tools, and Dell server management tools.

For Asterisk proper, I'm running an AGI caller id script, and a fax receiving script. The fax script uses cups to print. Those scripts require exceptions to the targeted SELinux policy. Note that the polic…

Details of Migrating Zimbra 6 to Zimbra 8

I have a small Zimbra system that needed to be migrated from 6.0 to 8.0. Generally:
You must update to 6.0.16 on the source system. The account export functionality is broken in versions prior to 6.0.15 and will fail on some accounts.Start with a fresh 8.0 install. On a small system (dozens of users), that seems like the simplest option.Keep the 6.0 system running. Use the migration wizard in 8.0's admin console (Tools & Migration -> Account Migration) to move over account records only.
Set "type of mail server" to Zimbra Collaboration Suite. Set "would you like to import mail" to No.Import from another Zimbra LDAP directory.Set the LDAP Search Base to "dc=foo,dc=com" where foo.com would be your domain. This saves work on manually moving accounts between systems.
To move account contents and filter settings between servers, you can do the following on the source server:
su - zimbra
ACCT=user@foo.com      # account to move
DEST=root@destination  # ss…