And I thought my posts were nerdy

I'm still trying to figure out what level of information is interesting and useful to everyone.  The more I talk to our TAP partners the more I'm coming to the conclusion that I need to scale back the technical detail and just focus on helping everyone learn the basics of using these new tools in the WDK.  Today, though, I ran across this nifty bit of reverse engineering.  I didn't take the time to validate its correctness.  It made me wonder though, what would anyone want that level of technical detail for?  Is it useful to you?

Comments (1)

  1. Norman Diamond says:

    I don’t expect personally to use WIM at that level of detail, but in general that kind of detail is not excessive. Sure anyone who uses it is writing non-portable code that will break the next time a Windows bug gets fixed. We’re "supposed" to stick to the contract as specified by MSDN pages. But when Windows APIs and libraries and compiler-generated code don’t obey the contract as specified by MSDN pages, we need to use this kind of detail to prove the bugs and find workarounds.

    Also Microsoft agreed with the US government to document a bunch of APIs that it hadn’t documented before, because Microsoft wasn’t the only user who needed them.

Skip to main content