Bug #25157 destination path for .zip (no installer) MyODBC incorrectly set.
Submitted: 18 Dec 2006 22:01 Modified: 15 Mar 2007 21:49
Reporter: Daniel DiSisto Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51.12 OS:Microsoft Windows (Windows (All))
Assigned to: Kent Boortz CPU Architecture:Any

[18 Dec 2006 22:01] Daniel DiSisto
Description:
file: mysql-connector-odbc-noinstall-3.51.12-win32
        \Install.bat
        \Uninstall.bat

For the windows .zip distribution (no installer), the batch files included have the destination path as 'C:\Windows\System32'. When running these batch files on a system on which windows is not installed at C:\Windows, the batch file causes a bunch of errors and doesn't work.

On Win2k, XP, and others, the default Windows install path is actually <drive>:\WINNT, where <drive> is not necessarily going to be C: - this means that on the vast majority of Windows systems in use today, the batch files are broken.

How to repeat:
Run the install\uninstall batch files on any Windows system where Windows is installed to a path other than C:\Windows

Suggested fix:
Windows has an environment variable for the install path that can be used instead of having the absolute path explicitly defined. To make use of this, replace all occurrences of C:\Windows\System32 with %windir%\System32

(type 'echo %windir%' at a Windows command prompt to see where this goes)

Note: you could instead use %SystemRoot%, which expands to exactly the same thing as %windir% and is the preferred variable to use on WinNT, 2k & XP, but this is not available on Win9x. For compatibility with all Windows version from Win9x to Vista, I would recommend using %windir%.
[12 Jan 2007 11:13] Valeriy Kravchuk
Thank you for a bug report. Verified just as described. One will find references to \Windows\System32 in Install.bat and Uninistall.bat, and this is, indeed, is incorrect for NT/2000 at least.
[15 Mar 2007 21:49] Kent Boortz
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release,
3.51.15.