🚀 go-pugleaf

"Thorsten Kettner" <QUESTIONBYthorsten.kettner@otto.de> wrote in message
news:4332d7c6$1@newsgroups.borland.com...

> I find it strange for instance that I must state again and again
> that I want to have read access.

You must not have read the MSDN documentation that describes memory-mapped
files.  An application can have multiple views of a single file, and each
view can contain different areas of the file, each one with different access
rights.

> Then: How do I tell how many bytes to read? Do I use GetFileSize on the
file handle?

Yes.

> In some forum I found VirtualQuery being used. Is that appropriate?

That depends on what you are doing with the memory mapping in the first
place.  Mapping a file gives you access to the bytes of the file, but
VirtualQuery() provides information about the paging system that is
providing that access.

> It gives me a slightly other file size (some bytes more then GetFileSize
> and Windows Explorer do).

As it should be, since pages have to aligned on particular memory
boundaries.  The extra bytes being reported are likely due to extra padding
that is being applied to align the memory properly.

>   if(!MyFileMappingHandle) return;

You did not close the file handle before returning.

>   if(!pFileView) return;

You did not close the mapping or file handles before returning.


Gambit