11-30-2007 05:56 PM
11-30-2007 06:25 PM
05-16-2008 10:37 AM
05-16-2008 10:45 AM
05-20-2008 12:43 AM
Newton, Can you explan your remedy again.It has cut off in the middle.
05-21-2008 09:33 AM - edited 05-21-2008 09:34 AM
05-22-2008 06:10 AM
05-22-2008 09:02 AM
05-22-2008 09:11 AM
05-22-2008 12:09 PM - edited 05-22-2008 12:10 PM
Been awhile since I've dealt with this, so I'm going by memory - I deny responsibility for any inaccuracies in the following post.
The installer files are read only after creation maybe?. In any case, the installer creator doesn't check to see if the old files are read only. It cannot overwrite them, and keeps on proceeding with the operation without a warning or error. The answer is to delete the old installer or change it from Read Only. If you install to a different location, it works because the old files aren't there!
NI needs to have the installer detect if it cannot overwrite the file, then either bomb out or prompt the user for permission to overwrite the file.
I'm amazed NI hasn't encountered this in testing.
Actually, I'm not.