James Finnigan : WMI

Using WMIC to check for predicted disk failure (S.M.A.R.T. analysis)

jamesfinnigan — Tue, 16 Jan 2007 01:41:22 GMT

I was looking at the Windows Vista Reliability and Performance Monitor and noticed that the data collector sets for System Diagnostics included a SMART disk check. I've been waiting for Windows to make better use of SMART and hadn't noticed that there was a WMI entry for it. I took a look at it in WMIC to see what data was there. You can also view the data and thresholds used to predict failure, etc.

WMIC /NAMESPACE:\\root\wmi PATH MSStorageDriver_FailurePredictStatus
Active InstanceName PredictFailure Reason
TRUE IDE\DiskWDC_WD1200BB-00CAA0_____________________16.06V16\5&134a4e1&0&1.0.0_0 FALSE 0
TRUE IDE\DiskWDC_WD740GD-00FLA1______________________27.08D27\5&14d2dd2b&0&0.0.0_0 FALSE 0
TRUE IDE\DiskST3250823AS_____________________________3.03____\5&278c8dd0&0&1.0.0_0 FALSE 0

WMIC /NAMESPACE:\\root\wmi PATH MSStorageDriver_FailurePredictData
WMIC /NAMESPACE:\\root\wmi PATH MSStorageDriver_FailurePredictThresholds

WMI Folder - codeplex project

jamesfinnigan — Thu, 11 Jan 2007 01:03:43 GMT

Well, I've put the WMI folder code up on codeplex. Please remember that this code is very much pre-alpha. I think that this will be a good way to share the code, allow others to contribute, etc. If it works well, then I will probably create codeplex projects for some of the other things that I'm putting together.

If you're interested in contributing, leave a comment here or via the codeplex project.
Happy new year!
James

WMI Shell Folder GetDisplayNameOf - untangling the flags

jamesfinnigan — Tue, 07 Nov 2006 00:24:43 GMT

So I have a bit of a beef with GetDisplayNameOf - I don't like the flags. I understand that when it was created, the flexibility of flags made a ton of sense. It wasn't well understood what potentially wildly different uses might be needed, and flags are a good alternative to a giant enumeration. But I think there are really only about 4 possibilities that matter most of the time (caveat: I'm still pretty new to shell programming). It's a pain to figure out the flags and there are combinations that don't even make sense. It seems to make a lot more sense to me to use an enumeration (like in IShellItem).

Anyway, I ended up liking a solution that very similar to the one that was put into the Registry sample that a few of us are putting together (more on that later). I created four different functions for the different GetDisplayNameOf possibilities and hopefully the table that links them to the flags isn't too scary.

HRESULT CWMIFldr::GetDisplayNameOf(

/* [in] */ PCUITEMID_CHILD pidl,

/* [in] */ SHGDNF uFlags,

/* [out] */ STRRET *pName)

{

TRACEFNENTER();

HRESULT hr;

ZeroMemory(pName, sizeof(*pName));

if (!ILIsEmpty(pidl))

{

static const DisplayNameFn s_rgSIGDNMapping[2][2] =

{

// unfriendly // friendly

{{&CWMIFldr::_GetAbsoluteParsingName}, {&CWMIFldr::_GetAbsoluteDisplayName}}, // absolute

{{&CWMIFldr::_GetRelativeParsingName}, {&CWMIFldr::_GetRelativeDisplayName}}, // relative

};

bool fRelative = (uFlags & SHGDN_INFOLDER) == SHGDN_INFOLDER;

bool fFriendly = (uFlags & SHGDN_FORPARSING) != SHGDN_FORPARSING

|| (uFlags & SHGDN_FORADDRESSBAR) == SHGDN_FORADDRESSBAR;

PWSTR pszDisplay;

hr = (this->*s_rgSIGDNMapping[fRelative][fFriendly])(pidl, &pszDisplay);

if (SUCCEEDED(hr))

{

pName->uType = STRRET_WSTR;

pName->pOleStr = pszDisplay;

}

else

{

hr = E_NOTIMPL;

}

TRACEFNEXIT();

return hr;

}

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm