Bug #58452 Connector/ODBC 3.51 Windows 7 logo compliance
Submitted: 24 Nov 2010 11:04 Modified: 28 Feb 2011 3:12
Reporter: Bogdan Degtyariov Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51 OS:Any
Assigned to: CPU Architecture:Any

[24 Nov 2010 11:04] Bogdan Degtyariov
Description:
In order to comply to Windows 7 logo the ODBC driver must fix the following things:

1. Clean, reversible, installation
Value InstallLocation missing from key HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F929096B-54A0-4C5C-B125-1E7EB1917412}.
Value InstallLocation missing for program MySQL Connector/ODBC 3.51.

2. Install to the correct folders by default
File C:\WINDOWS\SYSWOW64\MYODBC3.DLL was written to an incorrect location.
File C:\WINDOWS\SYSWOW64\MYODBC3.HLP was written to an incorrect location.
File C:\WINDOWS\SYSWOW64\MYODBC3.LIB was written to an incorrect location.
File C:\WINDOWS\SYSWOW64\MYODBC3I.EXE was written to an incorrect location.
File C:\WINDOWS\SYSWOW64\MYODBC3-LICENSE.TXT was written to an incorrect location.
File C:\WINDOWS\SYSWOW64\MYODBC3M.EXE was written to an incorrect location.
File C:\WINDOWS\SYSWOW64\MYODBC3S.DLL was written to an incorrect location.
File C:\WINDOWS\SYSWOW64\MYODBC3S.LIB was written to an incorrect location

How to repeat:
Install the driver and look where files go and what registry entries are created.

Suggested fix:
MyODBC 3.51 installs in WINDOWS\SYSTEM32 (SYSWOW64) directory.
We could easily do it in Program Files as with MyODBC 5.1.

And the registry key for uninstallation does not comply Win7 requirements (it is empty):

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F929096B-54A0-4C5C-B125-1E7EB1917412}

As far as I know the registry problem affected 5.1 too, but it has been recently fixed. So just merge the appropriate changes from 5.1 into 3.51. IMHO nothing very special.
[28 Feb 2011 3:12] Bogdan Degtyariov
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at

  http://www.mysql.com/downloads/