Uninstallation string incorrect
8.3 file path used?
from 
Stardock Forums
Stardock Forums
Hi,
Specs:
Windows XP Pro SP2 using a standalone Wise installer containing Windowblinds 6.
Msgbox displaying the error:
---------------------------
Wise Uninstall
---------------------------
Could not open INSTALL.LOG file.
---------------------------
OK
---------------------------
Uninstallation fails due to incorrect 8.3 file path being used. 8.3 file paths cannot be guessed or generated and the paths are unknown until time of file or folder creation. 8.3 paths will certainly fail when used on a file system which has 8.3 names optionally turned off. Information stated previously can be confirmed by MSDN documention.
Information taken from Regedit:
Value = InstallLocation
Data = C:\Program Files\Stardock\Object Desktop\WindowBlinds
Value = UninstallString
Data = C:\PROGRA~1\Stardock\Object Desktop\WindowBlinds\UNWISE.EXE C:\PROGRA~1\Stardock\Object Desktop\WindowBlinds\INSTALL.LOG
The uninstall string above is generated or guessed and is incorrect for a file system with no 8.3 filename support in use.
Shortcuts created from installation also display 8.3 paths used as displayed below.
Target = "C:\Program Files\Stardock\Object Desktop\WindowBlinds\wbconfig.exe"
Start in = "C:\PROGRA~1\Stardock\Object Desktop\WindowBlinds"
Target = "C:\Program Files\Stardock\Object Desktop\WindowBlinds\UNWISE.EXE" C:\PROGRA~1\Stardock\Object Desktop\WindowBlinds\install.log
Start in = "C:\PROGRA~1\Stardock\Object Desktop\WindowBlinds"
The only way to uninstall Windowblinds with this issue is to pass the parameter "install.log" to "unwise.exe" while using the Windowblinds installation directory as the working directory.
Drag'n'drop of "install.log" onto "unwise.exe" causes the same error to occur so it would seem that a another bug is within "unwise.exe" to accept a absolute long path as a parameter. I have consulted with Altiris Technical Support on the issue with 8.3 file paths causing issues and tests have been done to ensure that their Wise installation product does function correctly. Since Altiris Technical Support cannot reproduce the issue then some concern arises if Windowblinds is using an older Wise installation product that may use 8.3 file paths incorrectly.
Thank you for any time into reviewing the above issue.
Michael
Specs:
Windows XP Pro SP2 using a standalone Wise installer containing Windowblinds 6.
Msgbox displaying the error:
---------------------------
Wise Uninstall
---------------------------
Could not open INSTALL.LOG file.
---------------------------
OK
---------------------------
Uninstallation fails due to incorrect 8.3 file path being used. 8.3 file paths cannot be guessed or generated and the paths are unknown until time of file or folder creation. 8.3 paths will certainly fail when used on a file system which has 8.3 names optionally turned off. Information stated previously can be confirmed by MSDN documention.
Information taken from Regedit:
Value = InstallLocation
Data = C:\Program Files\Stardock\Object Desktop\WindowBlinds
Value = UninstallString
Data = C:\PROGRA~1\Stardock\Object Desktop\WindowBlinds\UNWISE.EXE C:\PROGRA~1\Stardock\Object Desktop\WindowBlinds\INSTALL.LOG
The uninstall string above is generated or guessed and is incorrect for a file system with no 8.3 filename support in use.
Shortcuts created from installation also display 8.3 paths used as displayed below.
Target = "C:\Program Files\Stardock\Object Desktop\WindowBlinds\wbconfig.exe"
Start in = "C:\PROGRA~1\Stardock\Object Desktop\WindowBlinds"
Target = "C:\Program Files\Stardock\Object Desktop\WindowBlinds\UNWISE.EXE" C:\PROGRA~1\Stardock\Object Desktop\WindowBlinds\install.log
Start in = "C:\PROGRA~1\Stardock\Object Desktop\WindowBlinds"
The only way to uninstall Windowblinds with this issue is to pass the parameter "install.log" to "unwise.exe" while using the Windowblinds installation directory as the working directory.
Drag'n'drop of "install.log" onto "unwise.exe" causes the same error to occur so it would seem that a another bug is within "unwise.exe" to accept a absolute long path as a parameter. I have consulted with Altiris Technical Support on the issue with 8.3 file paths causing issues and tests have been done to ensure that their Wise installation product does function correctly. Since Altiris Technical Support cannot reproduce the issue then some concern arises if Windowblinds is using an older Wise installation product that may use 8.3 file paths incorrectly.
Thank you for any time into reviewing the above issue.
Michael
WinCustomize Forums