As it turns out, my problem was not with WMI at all - I tracked it down to a
firmware issue. I accidentally loaded an older version of my firmware and
this problem went away. So now I've got to figure out what broke in the
newer revision. But at least now I know it's not a driver issue!

My thanks to those who offered suggestions...

Josh Stone


"Josh Stone" <josh@4sonora.com> wrote in message
news:u5HD65TUDHA.1556@TK2MSFTNGP10.phx.gbl...