VxDs and [version] Resources
DeVerl Stokes
It appears that Microsoft has a nifty little tool that allows them to bind
version resources to VxDs that they're not sharing.
If you search the developer's CD for information on this, you will find:
"the Windows Resource Compiler binds a version resource to a file that
has the Windows (new- style) executable-file header. Because VxD files
do not have the new-style header, a VxD file cannot contain a version
resource".
However, if you use file manager to look at the properties of most of
the VxDs that ship with Windows, or do a hex dump of some of them, you
will quickly convince yourself that there really is a version resource
residing in most of them.
My questions are: Does anyone know what the trick is?
Has anyone ever successfully done this?
Any help would be appreciated.
Later,
DeVerl
Frank McConnell
>It appears that Microsoft has a nifty little tool that allows them to bind
>version resources to VxDs that they're not sharing.
Actually, they are, but the only place I know to get it is the
Compuserve WINSDK forum. Check lib 17 for a file called VXDVER.ZIP;
it contains the ADRC2VXD program that does this.
If anyone knows another source for this, I'd like to hear about it.
I don't really need it, but I'd like to be able to point folks
without Compuserve access somewhere.
[Note followups trimmed; don't know what this has to do with winhelp
or controls]
--
Frank McConnell <f...@rahul.net>