Everytime a new version of DVDP is released the installation file is named DVDProSetup.exe. I also like to keep older versions of setup files on my HD, incase there is a problem with the latest release, so I'm forced to eather change the filename or save it to another folder.

I tried to rename installation file to DVDProSetup3.7.1.xxxx.exe (I cannot remember the exact version at the moment). After that when I executed it the installation fails right away. So I renamed the installation file back and everything went smooth.

When next version came out I let the filename be, but instead put it under folder:

C:\Mytemp\Software\DVDprofiler softat\DVDProInstall.3.7.1.1436 FINAL\DVDProSetup.exe

Same failure happens, but it works under:

C:\Mytemp\Software\DVDprofiler softat\DVDProSetup.exe.

So it seems that if there is a full stop character anywhere in the folder path or file name (excluding the one before file extension) installation fails. Could it be possible that you could include file version to setup file name? For example DVDProSetup_3_7_1_1436.exe so old and new versions of installation files could be located in same folder.

I'm using Win 7 64-bit EN. The error message I get is:

Setup was unable to create the directory "C:\Users\My_username\AppData\Local\Temp\is-JE29T.tmp".

It doesn't matter which rights I use. If logged in as an Administrator it crashes right away and if logged in as a normal user, it crashes right before UAC should ask administrator credentials.

Quoting Staid S Barr:

Quote:
Solution is to change the file name after the install, for storage.

Or even better solution is to include the version number to original installation file name to avoid unnesessary user work and/or propably unwanted installation problems.

Quoting Staid S Barr:

Quote:
True, but inserting a full stop character is asking for trouble, like inserting \ or /.

Asking for trouble, debateable yes, but not the same. / and \ are not alloved characters on file names in NTFS, full stop is. It's even mandatory in folder names in some cases. First example that comes in mind is if you have an Active Directory environment where users use both Win XP and Win 7 OSs with roaming profiles. Since they don't use same profile, folders are named username (win xp) and username.V2 (win 7).

I cannot see the issue here. I found a bug from software and reported it to Ken. Nothing more, nothing less. It's his matter if he reacts to this report or not.