Commit 089d7924 authored by André Hentschel's avatar André Hentschel Committed by Alexandre Julliard

kernel32: Update function docs for GetBinayType.

parent 8cf585f6
...@@ -368,6 +368,7 @@ void MODULE_get_binary_info( HANDLE hfile, struct binary_info *info ) ...@@ -368,6 +368,7 @@ void MODULE_get_binary_info( HANDLE hfile, struct binary_info *info )
* executable file runs under. lpBinaryType can be set to one of the following * executable file runs under. lpBinaryType can be set to one of the following
* values: * values:
* SCS_32BIT_BINARY: A Win32 based application * SCS_32BIT_BINARY: A Win32 based application
* SCS_64BIT_BINARY: A Win64 based application
* SCS_DOS_BINARY: An MS-Dos based application * SCS_DOS_BINARY: An MS-Dos based application
* SCS_WOW_BINARY: A Win16 based application * SCS_WOW_BINARY: A Win16 based application
* SCS_PIF_BINARY: A PIF file that executes an MS-Dos based app * SCS_PIF_BINARY: A PIF file that executes an MS-Dos based app
...@@ -377,7 +378,7 @@ void MODULE_get_binary_info( HANDLE hfile, struct binary_info *info ) ...@@ -377,7 +378,7 @@ void MODULE_get_binary_info( HANDLE hfile, struct binary_info *info )
* To find the binary type, this function reads in the files header information. * To find the binary type, this function reads in the files header information.
* If extended header information is not present it will assume that the file * If extended header information is not present it will assume that the file
* is a DOS executable. If extended header information is present it will * is a DOS executable. If extended header information is present it will
* determine if the file is a 16 or 32 bit Windows executable by checking the * determine if the file is a 16, 32 or 64 bit Windows executable by checking the
* flags in the header. * flags in the header.
* *
* ".com" and ".pif" files are only recognized by their file name extension, * ".com" and ".pif" files are only recognized by their file name extension,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment