Skip to content

Latest commit

 

History

History
199 lines (154 loc) · 5.5 KB

nf-winbase-openfilemappinga.md

File metadata and controls

199 lines (154 loc) · 5.5 KB
UID title description helpviewer_keywords old-location tech.root ms.assetid ms.date ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.ddi-compliance req.unicode-ansi req.idl req.max-support req.namespace req.assembly req.type-library req.lib req.dll req.irql targetos req.typenames req.redist ms.custom f1_keywords dev_langs topic_type api_type api_location api_name
NF:winbase.OpenFileMappingA
OpenFileMappingA function (winbase.h)
Opens a named file mapping object. (OpenFileMappingA)
OpenFileMapping
OpenFileMapping function
OpenFileMappingA
OpenFileMappingW
_win32_openfilemapping
base.openfilemapping
fs.openfilemapping
winbase/OpenFileMapping
winbase/OpenFileMappingA
winbase/OpenFileMappingW
base\openfilemapping.htm
base
4896144c-78fc-4d21-a302-d9ba66fb2f8a
12/05/2018
OpenFileMapping, OpenFileMapping function, OpenFileMappingA, OpenFileMappingW, _win32_openfilemapping, base.openfilemapping, fs.openfilemapping, winbase/OpenFileMapping, winbase/OpenFileMappingA, winbase/OpenFileMappingW
winbase.h
Windows.h, Memoryapi.h
Windows
Windows XP [desktop apps only]
Windows Server 2003 [desktop apps only]
OpenFileMappingW (Unicode) and OpenFileMappingA (ANSI)
Kernel32.lib
Kernel32.dll
Windows
19H1
OpenFileMappingA
winbase/OpenFileMappingA
c++
APIRef
kbSyntax
DllExport
Kernel32.dll
API-MS-Win-Core-Kernel32-Legacy-l1-1-2.dll
kernel32legacy.dll
API-MS-Win-Core-memory-l1-1-0.dll
KernelBase.dll
API-MS-Win-Core-memory-l1-1-1.dll
API-MS-Win-Core-memory-l1-1-2.dll
API-MS-Win-Core-memory-l1-1-3.dll
API-MS-Win-DownLevel-Kernel32-l1-1-0.dll
MinKernelBase.dll
API-MS-Win-Core-Kernel32-Legacy-L1-1-3.dll
API-MS-Win-Core-Kernel32-Legacy-L1-1-4.dll
API-MS-Win-Core-Kernel32-Legacy-L1-1-5.dll
API-MS-Win-Core-Memory-L1-1-4.dll
OpenFileMapping
OpenFileMappingA
OpenFileMappingW

OpenFileMappingA function

-description

Opens a named file mapping object.

-parameters

-param dwDesiredAccess [in]

The access to the file mapping object. This access is checked against any security descriptor on the target file mapping object. For a list of values, see File Mapping Security and Access Rights.

-param bInheritHandle [in]

If this parameter is TRUE, a process created by the CreateProcess function can inherit the handle; otherwise, the handle cannot be inherited.

-param lpName [in]

The name of the file mapping object to be opened. If there is an open handle to a file mapping object by this name and the security descriptor on the mapping object does not conflict with the dwDesiredAccess parameter, the open operation succeeds. The name can have a "Global\" or "Local\" prefix to explicitly open an object in the global or session namespace. The remainder of the name can contain any character except the backslash character (\). For more information, see Kernel Object Namespaces. Fast user switching is implemented using Terminal Services sessions. The first user to log on uses session 0, the next user to log on uses session 1, and so on. Kernel object names must follow the guidelines outlined for Terminal Services so that applications can support multiple users.

-returns

If the function succeeds, the return value is an open handle to the specified file mapping object.

If the function fails, the return value is NULL. To get extended error information, call GetLastError.

-remarks

The handle that OpenFileMapping returns can be used with any function that requires a handle to a file mapping object.

When modifying a file through a mapped view, the last modification timestamp may not be updated automatically. If required, the caller should use SetFileTime to set the timestamp.

When it is no longer needed, the caller should call release the handle returned by OpenFileMapping with a call to CloseHandle.

In Windows Server 2012, this function is supported by the following technologies.

Technology Supported
Server Message Block (SMB) 3.0 protocol Yes
SMB 3.0 Transparent Failover (TFO) Yes
SMB 3.0 with Scale-out File Shares (SO) Yes
Cluster Shared Volume File System (CsvFS) Yes
Resilient File System (ReFS) Yes
 

Examples

For an example, see Creating Named Shared Memory.

-see-also

CreateFileMapping

File Mapping Functions

Memory Management Functions

Sharing Files and Memory