09-29-2005 02:14 PM
09-30-2005 02:59 PM
09-30-2005 03:18 PM
Thanks, JLS.
We figured it out. There's an entry in the registry that lvanyls.dll points to specifying the location of the LV shared directory (and therefore the MKL directory). If it's not found in that exact location, the dll load aborts.
We're trying to not include the runtime installer in our application installer because of the size, so we're figuring out our own workaround (and trying to CYA in the meantime 🙂 ).
-Scott
10-03-2005 12:09 PM