Skip to content
Snippets Groups Projects
Commit 48256329 authored by chrfranke's avatar chrfranke
Browse files

Windows: Remove outdated entry from WARNINGS file.

git-svn-id: https://smartmontools.svn.sourceforge.net/svnroot/smartmontools/trunk@2804 4ea69e1a-61f1-4043-bf83-b5c94c648137
parent d7a79de7
No related branches found
No related tags found
No related merge requests found
CHANGELOG for smartmontools
$Id: CHANGELOG,v 1.804 2009/06/13 14:56:20 chrfranke Exp $
$Id: CHANGELOG,v 1.805 2009/06/18 17:24:51 chrfranke Exp $
The most recent version of this file is:
http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/CHANGELOG?view=markup
......@@ -41,6 +41,9 @@ NOTES FOR FUTURE RELEASES: see TODO file.
<DEVELOPERS: ADDITIONS TO THE CHANGE LOG GO JUST BELOW HERE, PLEASE>
[CF] Windows: Remove outdated entry about undocumented system calls
from WARNINGS file.
[CF] Print General Purpose Logs even if GPL feature bit is missing.
Needed for some older disks which implement READ LOG EXT but
do not report the GPL feature set.
......
$Id: WARNINGS,v 1.33 2006/05/19 16:33:33 chrfranke Exp $
$Id: WARNINGS,v 1.34 2009/06/18 17:24:51 chrfranke Exp $
The most recent version of this file can be found here:
http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/WARNINGS?view=markup
......@@ -99,17 +99,7 @@ SOLARIS
CYGWIN and WINDOWS
------------------
SYSTEM: Any Windows NT4, 2000 or XP system.
PROBLEM: Use of undocumented system calls for IDE/ATA read log
(smartctl -l, --log, -a, --all) may affect system stability.
REPORTER: Christian Franke <smartmontools-support@lists.sourceforge.net>
NOTE: The IOCTL call SMART_RCV_DRIVE_DATA does not support
ATA_SMART_READ_LOG_SECTOR on NT4/2000/XP. The Win32
implementation of smartctl/smartd uses undocumented
and possibly buggy system calls for this purpose:
NT4: IOCTL_SCSI_PASS_THROUGH with undocumented pseudo SCSI
command SCSIOP_ATA_PASSTHROUGH (0xCC).
2000/XP: Undocumented IOCTL_IDE_PASS_THROUGH.
[No problem reports yet.]
DARWIN
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment