This sample is alternative documentation, written to demonstrate that it can be both feasible and productive to derive high-quality technical specifications by analysing binary code. The interfaces studied for this sample are seemingly simple, yet the manufacturer’s specification has errors and omissions. Highlights are applied to points where the author believes a third-party programmer who relies on the manufacturer’s documentation could be misled or confused.
The article starts with an overview of the IFSMGR’s attitude to character sets, including expectations about registry entries and the UNICODE.BIN file. The bulk of the document is reference material, detailing the VxD services that the IFSMGR provides so that other VxDs may convert strings, especially pathnames, from one character set to another.
The article is presented as a Microsoft Word for Windows 7.0 document, compressed into a cabinet file.
Copyright © 1997. Geoff Chappell. All rights reserved.
[Home][Programming Samples][Application Notes][Security Notes][Editorial][Consultation][Contacts]