Bug #439 | Wrong description of the mysqld-nt server | ||
---|---|---|---|
Submitted: | 16 May 2003 19:34 | Modified: | 21 Jul 2003 8:37 |
Reporter: | Miguel Solorzano | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | all | OS: | Windows (Windows) |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
[16 May 2003 19:34]
Miguel Solorzano
[14 Jul 2003 9:42]
Paul DuBois
Miguel, I don't understand this report. Using MySQL 4.0.13, I can start either mysqld-nt or mysqld-max-nt on Windows Me with no problems, and clients can connect to it. Is your comment about the __NT__flag specific only to some versions of MySQL? Regarding the comment: Windows 9x/Me only support client named pipes. The client library supports only local named pipes, so isn't the comment effectively equivalent to saying that Windows 9x/Me don't support named pipes *at all*?
[14 Jul 2003 22:42]
MySQL Verification Team
Shows Win95 issue.
Attachment: win95.png (image/x-png, text), 11.25 KiB.
[14 Jul 2003 22:45]
MySQL Verification Team
Paul on my machine Win95 happens the start problem showed in the picture win95.png I added in the section Files.
[17 Jul 2003 10:14]
Paul DuBois
I'm stealing this bug report from Arjen and assigning it to myself.
[21 Jul 2003 8:37]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant product(s). mysqld-nt and mysql-max-nt do work on Windows 98 and Me, but apparently not on Windows 95. Updated documentation to reflect that.