08-30-2007 03:12 PM
08-30-2007 03:33 PM
08-30-2007 04:42 PM
Thanks for the reply.
It's in the distribution. I can install on a PC which has never had our application installed on it and I see c:\program files\system32\cvirte.dll installed and all is well.
This application is meant to be fully self installing so it's not acceptable to download the runtime engine to fix failed installations.
As luck would have it, the only failing PC is at a customer site over seas. This same PC has had our previous versions of our application installed ok. The user has tried uninstalling and reinstalling several times with no luck.
So what's differant now? Wish I knew. That's why I'm fishing for information that might help me understand the situation.
I would appriciate any background or possible investigation clues you might have to offer.
08-30-2007 05:11 PM
08-30-2007 05:14 PM
08-31-2007 03:41 PM
08-31-2007 05:53 PM
More info:
If I delete the cvirte directory from System32 on a working installation I see exactly the same two error messages as reported from the failing PC.
It all seems to come down to this: the cvirte directory is not always created on installation.
I've also observed that this directory is usually, but not always removed on uninstall.
Can you explain why the cvirte directory fail to be created?
09-04-2007 12:23 PM
09-04-2007 03:10 PM
09-04-2007 03:13 PM
I'm using:
LabWindows 8.0.0 (273)
(Microsoft Windows 2000/XT)