Areas where you might find this of interest include very large database files with fixed records, audio processing, string operations and image processing. The other side of memory mapped files is to implement shared memory. As you will probably know, Win32 puts each process into its own address space, thus making it impossible to pass ordinary pointers across process boundaries. With memory mapped files you get back this very useful mechanism. The source zip file contains the CMemMapFile source code and a simple dialog based application which demonstrates all the functionality of the class.
Class now avoids trying to lock the mutex if only read access is required.
User now has the option of specifying whether a file should be mapped with a NULL terminator at the end. Can prove helpful when you want to use some of the C runtime functions on the pointer returned. Mapping a file now has the option of making it named or not. New documentation in the form of a HTML file. Sample now ships as standard with VC 5 workspace files.