Device Object Viewer and WinObj

NTDEV
1

Hi,

Can anyone tell me the difference between Device Object Viewer (Walter Oney)
and WinObj (Sysinternals). They appear to have an almost identical front
end. Which of the two is the most recent? Is there a more recent alternative
to the both of these?

Regards FarmerJo

2

WinObj is a heck of a lot newer. What do you think it is missing?

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

“FarmerJo” wrote in message news:xxxxx@ntdev…
> Hi,
>
> Can anyone tell me the difference between Device Object Viewer (Walter
> Oney) and WinObj (Sysinternals). They appear to have an almost identical
> front end. Which of the two is the most recent? Is there a more recent
> alternative to the both of these?
>
> Regards FarmerJo
>
>

3

I’m sorta partial to the OSR GUI Object View myself: http://www.osronline.com/article.cfm?article=42

Peter
OSR

4

The big advantage with Oney’s viewer is that it can jumps through symbolic links whereas the other viewers force you to search for the sym link target. However, to achieve that functionality, Oney’s viewer install a kernel mode driver which make the browsing less safe. (Don’t doubt, I admire Oney’s knowledge and programmatic abilities, however not having a kernel module is much safer than a “perfect” driver…).

Eran.

5

Hi,

I did notice that when I attempt to inspect either a driver or device when
using WinObj I get an error message. For example if I select the Driver
folder in the left hand pane and then double click “Serial” in the right
hand pane I get “Unable to open \Driver\Serial”. However if I do the
equivalent using DevView I am able to view the device and their PDOs, FDOs
etc without error.

Although I have no preference regarding these two utilities I would like to
know why I cannot get WinObj to work properly.

Any ideas?

Regards FarmerJo