Bug #39103 | Cannot open refman-5.0-en.chm | ||
---|---|---|---|
Submitted: | 28 Aug 2008 16:39 | Modified: | 3 Apr 2009 16:41 |
Reporter: | Jack Liu | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | 5.0, chm, refman |
[28 Aug 2008 16:39]
Jack Liu
[28 Aug 2008 16:49]
MySQL Verification Team
Thank you for the bug report. Which exactly server package you have installed?. Thanks in advance.
[28 Aug 2008 17:02]
Jack Liu
Hello, It is not a problem with SQL server, it is the chm help file. Download link is http://downloads.mysql.com/docs/refman-5.0-en.chm Thanks, Jack
[28 Aug 2008 17:26]
MySQL Verification Team
Thank you for the feedback. Sorry I thought it was the .chm file shipped within the server installer package. I got an information that Manual was updated so please wait some hours to download it again. Thanks.
[28 Sep 2008 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[1 Apr 2009 15:40]
Peter Santiago
Just downloaded http://downloads.mysql.com/docs/refman-5.0-en.chm. Still won't open correctly. Error message: Address not valid
[1 Apr 2009 15:42]
Peter Santiago
Screenshot of the chm file
Attachment: mysql-chm1.JPG (image/jpeg, text), 106.32 KiB.
[1 Apr 2009 15:43]
Peter Santiago
2nd Screenshot of the chm file
Attachment: mysql-chm2.JPG (image/jpeg, text), 106.62 KiB.
[1 Apr 2009 16:24]
Jack Liu
If you open in Win XP, you need to unblock it first. Right click and Select Properties, then click on unblock. The links then work fine.
[2 Apr 2009 9:50]
Peter Santiago
OMG.... Extremely sorry for not being able to figure that out. I never thought that CHM files needs to be unblocked under XP. Thanks a lot.
[3 Apr 2009 16:41]
Stefan Hinz
From the reporter's last comment, it looks like this has been resolved, thus closing this bug.