CVI 2009 Base Package won't activate CVI 8.1

Question

I own a license for CVI 2009 Base Package, which is activated and works correctly.  A customer of ours requires that we use CVI 8.1.
When I launch CVI 8.1, I first got an evaluation period, but now I'm unable to launch at all since the evaluation is expired.
I already tried removing my cvi_base_pkg_080100.lc and downloading the new one from NI's site (http://joule.ni.com/nidu/cds/view/p/id/78/lang/en).
License manager shows that the license is installed correctly:
What should I do next?
Josh W.
Certified TestStand Architect
Formerly blue

Answer 1

Louis,
Thanks for cluing me into how NILM works with NI software.  I didn't realize that it was linked as a static library.  I had seen in the past when NI moved to WinVista-compliant paths that licenses didn't need to be in the old folders and that software pre-change and post-change worked equally well with the new folders, so I had guessed that it was all handled by the NILM runtime.
Nick,
This may not be a reproduceable case.  I wish I could tell you my install order...but unfortunately this machine isn't that clean.  I think the order goes something like this, but I'm not completely certain:
Install CVI 7.1 (eval)
Install CVI 2010 (eval)
Install CVI 8.1 (eval)
Install TestStand 4.2.1 (eval)
Install TestStand 2010 beta (beta license)
License CVI 2010 & CVI 7.1
Install LabVIEW 2010 (full)
Uninstall TestStand 2010 (after beta expires)
Uninstall TestStand 4.2.1
I originally had all of the usual license files for CVI, but I removed the extraneous ones (full/debug/etc.) as part of my debugging to make sure they weren't interferring in some way. I still have those licenses, they're just in a subfolder called 'old' within the Licenses folder.
My UAC is set to "Notify me only when programs try to make changes to my computer (do not dim my desktop)".
I'm logged in as "VIRGINIA\Josh" (VIRGINIA is the name of our local domain), and I'm an administrator.
If you can't reproduce this, and it's not immediately obvious what's causing it, don't spend too much time at it. I'm worried it's an interaction between the TestStand beta license expiring, and the CVI license being in eval at that time.  I can work around it for now (I can write the code on my machine where I have better monitors and then compile it on a test machine where it licenses correctly).  We're also considering moving to Win7 x64 by the end of the year, so I'll have to re-install everything then anyway.
Josh W.
Certified TestStand Architect
Formerly blue