en:docs:fapi:dosmkdir

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:docs:fapi:dosmkdir [2021/08/20 03:50] prokusheven:docs:fapi:dosmkdir [2025/07/12 16:23] (current) prokushev
Line 5: Line 5:
 This call creates a subdirectory. This call creates a subdirectory.
  
-==Syntax==+===== Syntax =====
  
-  DosMkDir (DirName, Reserved)+<code c> 
 +DosMkDir (DirName, Reserved) 
 +</code>
  
-==Parameters==+===== Parameters =====
  
-  *DirName (PSZ) - input : Address of the ASCIIZ directory path name, which may or may not include a drive specification. If no drive is specified, the current drive is assumed. 
  
-:DosQSysInfo is called by an application during initialization to determine the maximum path length allowed by OS/2.+  * DirName ([[PSZ]]) - input Address of the ASCIIZ directory path name, which may or may not include a drive specification. If no drive is specified, the current drive is assumed. [[DosQSysInfo]] is called by an application during initialization to determine the maximum path length allowed by OS.
  
-  *Reserved (ULONG) - input : Reserved and must be set to zero.+  *Reserved ([[ULONG]]) - input : Reserved and must be set to zero.
  
-==Return Code==+===== Return Code =====
  
-  rc (USHORT) - return+rc ([[USHORT]]) - return
  
 Return code descriptions are: Return code descriptions are:
 +
   * 0        NO_ERROR    * 0        NO_ERROR 
   * 3        ERROR_PATH_NOT_FOUND    * 3        ERROR_PATH_NOT_FOUND 
Line 30: Line 32:
   * 206      ERROR_FILENAME_EXCED_RANGE   * 206      ERROR_FILENAME_EXCED_RANGE
  
-==Remarks==+===== Remarks =====
  
 If any subdirectory names in the path do not exist, the subdirectory is not created. Upon return, a subdirectory is created at the end of the specified path. If any subdirectory names in the path do not exist, the subdirectory is not created. Upon return, a subdirectory is created at the end of the specified path.
  
-DosQSysInfo must be used by an application to determine the maximum path length supported by OS/2. The returned value should be used to dynamically allocate buffers that are to be used to store paths.+[[DosQSysInfo]] must be used by an application to determine the maximum path length supported by OS. The returned value should be used to dynamically allocate buffers that are to be used to store paths.
  
 If a program running with the NEWFILES bit set tries to create a directory with blanks immediately preceding the dot on a FAT drive, the system rejects the name. For example, if c: is a FAT drive, the name "file .txt" is rejected and the name "file.txt" is accepted.  If a program running with the NEWFILES bit set tries to create a directory with blanks immediately preceding the dot on a FAT drive, the system rejects the name. For example, if c: is a FAT drive, the name "file .txt" is rejected and the name "file.txt" is accepted. 
  
-==Example Code== +===== Example Code =====
-=== C Binding===+
  
 +==== C Binding ====
 +
 +<code c>
   #define INCL_DOSFILEMGR   #define INCL_DOSFILEMGR
      
Line 49: Line 53:
      
   USHORT           rc;            /* return code */   USHORT           rc;            /* return code */
 +</code>
  
-===MASM Binding===+==== MASM Binding ====
  
 +<code asm>
   EXTRN  DosMkDir:FAR   EXTRN  DosMkDir:FAR
   INCL_DOSFILEMGR     EQU 1   INCL_DOSFILEMGR     EQU 1
Line 58: Line 64:
   PUSH   DWORD               ;Reserved (must be zero)   PUSH   DWORD               ;Reserved (must be zero)
   CALL   DosMkDir   CALL   DosMkDir
 +</code>
  
 Returns WORD Returns WORD
  
-=== Note ===+===== Note ===== 
  
 Text based on http://www.edm2.com/index.php/DosMkDir Text based on http://www.edm2.com/index.php/DosMkDir