Tutorial 12: Memory Management and File I / O
WE WILL Learn The Rudimentary of Memory Management and File I / O Operation In this Tutorial. In Addition We'll Use Common Dialog Boxes as Input-Output Devices.
Theory: Memory management under Win32 from the application's point of view is quite simple and straightforward Each process owns a 4 GB memory address space The memory model used is called flat memory model In this model, all segment registers (or selectors) point... to the same starting address and the offset is 32-bit so an application can access memory at any point in its own address space without the need to change the value of selectors. This simplifies memory management a lot. There's no "near" or " FAR "Pointer Anymore.
Under Win16, there are two main categories of memory API functions:.. Global and Local Global-type API calls deal with memory allocated in other segments thus they're "far" memory functions Local-type API calls deal with the local heap of .
Steps in Allocating and use Memory Areas Follows:
Allocate a block of memory by calling GlobalAlloc. This function returns a handle to the requested memory block. "Lock" the memory block by calling GlobalLock. This function accepts a handle to the memory block and returns a pointer to the memory block. You can use the pointer to read or write memory. "Unlock" the memory block by calling GlobalUnlock. This function invalidates the pointer to the memory block. Free the memory block by calling GlobalFree. This function accepts the handle to the memory block. You can also substitute "Global" by "Local" such as LocalAlloc, LocalLock, etc.The above method can be further simplified by using a flag in GlobalAlloc call, GMEM_FIXED. If you use this flag, the return value from Global / LocalAlloc will be the pointer to the allocated memory block, not the memory block handle. you do not have to call Global / LocalLock and you can pass the pointer to Global / LocalFree without calling Global / LocalUnlock first. But in this tutorial, I'll use the " TRADIO NAL "Approach Since You May Encounter It When Reading The Source Code of Other Programs.
. File I / O under Win32 bears remarkable semblance to that under DOS The steps needed are the same You only have to change interrupts to API calls and it's done The required steps are the followings..:
Open or Create the file by calling CreateFile function This function is very versatile:. In addition to files, it can open communication ports, pipes, disk drives or console On success, it returns a handle to file or device You can then use.. this handle to perform operations on the file or device. Move the file pointer to the desired location by calling SetFilePointer. Perform read or write operation by calling ReadFile or WriteFile. These functions transfer data from a block of memory to or from the file. So you have to allocate a block of memory large enough to hold the data Close the file by calling CloseHandle This function accepts the file handle.Content:... The program listed below displays an open file dialog box It lets the user select a text file To open and shows the content of this file in an escher. The User CAN Modify The Text In The Edit Control As He Wishes, And Can Choose To Save The Content in A File.
.386 .model flat, stdcall option casemap: none WinMain proto: DWORD,: DWORD,: DWORD,: DWORD include /masm32/include/windows.inc include /masm32/include/user32.inc include / masm32 / include / kernel32. Include /masm32/include/comdlg32.incinc includelib /masm32/lib/user32.lib incrudelib /masm32/lib/kernel32.lib includeliB /masm32/lib/comdlg32.lib
.const IDM_Open EQU 1 IDM_SAVE EQU 2 IDM_EXIT EQU 3 MaxSize EQU 260 Memsize EQU 65535
Editid EQU 1; ID of the Edit Control
.data classname DB "Win32asmeditclass", 0 AppName DB "Win32 ASM Edit", 0 EditClass DB "Edit", 0 Menuname DB "Firstmenu", 0 OFN OpenFileName <> Filterstring DB "All Files", 0, "*. *" 0 DB "text files", 0, "*. Txt", 0, 0 buffer db maxsize dup (0) .Data? Hinstance Hinstance? CommandLine LPSTR? HWndE to the Edit Control HFile Handle?; File Handle HMEMORY HANDLE?; HANDLE TO THEOCATED MEMORY BLOCK PMEMORY DWORD?; POINTER TO THEOCATED MEMORY BLOCK SIZEREADWRITE DWORD?; Number of Bytes Actually Read or Write
. Code Start: Invoke GetModuleHandle, Null Mov Hinstance, Eax Invoke Getcommandline Mov Commandline, Eax Invoke Winmain, Hinstance, Null, CommandLine, SW_SHOWDEFAULT INVOKE EXITPROCESS, EAX
WinMain proc hInst: HINSTANCE, hPrevInst: HINSTANCE, CmdLine: LPSTR, CmdShow: SDWORD LOCAL wc: WNDCLASSEX LOCAL msg: MSG LOCAL hwnd: HWND mov wc.cbSize, SIZEOF WNDCLASSEX mov wc.style, CS_HREDRAW or CS_VREDRAW mov wc.lpfnWndProc, OFFSET WndProc mov wc.cbClsExtra, NULL mov wc.cbWndExtra, NULL push hInst pop wc.hInstance mov wc.hbrBackground, COLOR_WINDOW 1 mov wc.lpszMenuName, OFFSET MenuName mov wc.lpszClassName, OFFSET ClassName invoke LoadIcon, NULL, IDI_APPLICATION mov wc. hIcon, eax mov wc.hIconSm, eax invoke LoadCursor, NULL, IDC_ARROW mov wc.hCursor, eax invoke RegisterClassEx, addr wc invoke CreateWindowEx, WS_EX_CLIENTEDGE, aDDR ClassName, aDDR AppName, / WS_OVERLAPPEDWINDOW, CW_USEDEFAULT, / CW_USEDEFAULT, 300,200, NULL, NULL , / Hinst, Null Mov HWnd, Eax Invoke Showwindow, HWnd, SW_SHOWNORMAL INVOKE UPDATEWINDOW, HWND .WHILE TRUE INVOKE GETMESSAGE, ADD R msg, null, 0 ,0 .break .if (! EAX) Invoke TranslateMessage, Addr Msg Invoke DispatchMessage, Addr Msg .Endw Mov Eax, Msg.wParam Ret Winmain Endp
WndProc proc uses ebx hWnd: HWND, uMsg: UINT, wParam: WPARAM, lParam: LPARAM .IF uMsg == WM_CREATE invoke CreateWindowEx, NULL, ADDR EditClass, NULL, / WS_VISIBLE or WS_CHILD or ES_LEFT or ES_MULTILINE or / ES_AUTOHSCROLL or ES_AUTOVSCROLL, 0 , / 0,0,0, hwnd, editid, / hinstance, null mov hwndedit, eax invoke setfocus, hwndit; ========================= =====================; Initialize the Members of OpenFileName Structure; ===================== ================================== Mov off.lstructSize, Sizeof offn Push HWnd pop offs.hwndowner push hinstance pop offshinstance mov offslpstrfilter, offset FilterString mov ofn.lpstrFile, OFFSET buffer mov ofn.nMaxFile, MAXSIZE .ELSEIF uMsg == WM_SIZE mov eax, lParam mov edx, eax shr edx, 16 and eax, 0ffffh invoke MoveWindow, hwndEdit, 0,0, eax, edx, TRUE .Lse IF umsg == wm_destroy invoke postquitmessage, null .elseif umsg == wm_command mov Eax, wparam .IF lparam == 0 .IF AX ==
IDM_OPEN mov ofn.Flags, OFN_FILEMUSTEXIST or / OFN_PATHMUSTEXIST or OFN_LONGNAMES or / OFN_EXPLORER or OFN_HIDEREADONLY invoke GetOpenFileName, ADDR ofn .if eax == TRUE invoke CreateFile, ADDR buffer, / GENERIC_READ or GENERIC_WRITE, / FILE_SHARE_READ or FILE_SHARE_WRITE, / NULL, OPEN_EXISTING, FILE_ATTRIBUTE_ARCHIVE , / NULL mov hFile, eax invoke GlobalAlloc, GMEM_MOVEABLE or GMEM_ZEROINIT, MEMSIZE mov hMemory, eax invoke GlobalLock, hMemory mov pMemory, eax invoke ReadFile, hFile, pMemory, MEMSIZE-1, ADDR SizeReadWrite, NULL invoke SendMessage, hwndEdit, WM_SETTEXT, NULL , Pmemory Invoke Closeh andle, hFile invoke GlobalUnlock, pMemory invoke GlobalFree, hMemory .endif invoke SetFocus, hwndEdit .elseif ax == IDM_SAVE mov ofn.Flags, OFN_LONGNAMES or / OFN_EXPLORER or OFN_HIDEREADONLY invoke GetSaveFileName, ADDR ofn .if eax ==
TRUE invoke CreateFile, ADDR buffer, / GENERIC_READ or GENERIC_WRITE, / FILE_SHARE_READ or FILE_SHARE_WRITE, / NULL, CREATE_NEW, FILE_ATTRIBUTE_ARCHIVE, / NULL mov hFile, eax invoke GlobalAlloc, GMEM_MOVEABLE or GMEM_ZEROINIT, MEMSIZE mov hMemory, eax invoke GlobalLock, hMemory mov pMemory, eax invoke SendMessage, hwndEdit, WM_GETTEXT, MEMSIZE-1, pMemory invoke WriteFile, hFile, pMemory, eax, ADDR SizeReadWrite, NULL invoke CloseHandle, hFile invoke GlobalUnlock, pMemory invoke GlobalFree, hMemory .endif invoke SetFocus, HWndIt .ELSE Invoke DestroyWindow, Hwnd .ndif.ndif.Else Invoke DefWindowProc, HWnd, Umsg, WParam, LParam Ret .ndif xor EAX, EAX RET WNDPROC ENDS:
Invoke CreateWindowex, NULL, AddR Editclass, Null, /
WS_VISible or WS_CHILD or ES_LEFT or ES_MULTILINE OR /
ES_AUTOHSCROLL OR ES_AUTOVSCROLL, 0, /
0,0,0, hwnd, editid, /
Hinstance, NULL
Mov hwndedit, EAX
In WM_CREATE section, we create an edit control. Note that the parameters that specify x, y, width, height of the control are all zeroes since we will resize the control later to cover the whole client area of the parent window. Note that in This Case, We don't have to call showwindow to make the edit control Appear on the screen.. You can use this trick in the parent window Too.; ============ ================================================================================================================== ================================================================================================================================================================================00 HWNDOWNER PUSH HINSTANCE POP OFN.HINSTANCE MOV OFN.LPSTRFILTER, OFFSET FILTERSTRING MOV OFN.LPSTRFILE, OFFSET BUFFER MOV OFN.NMAXFILE, MAXSIZE
After creating the edit control, we take this time to initialize the members of ofn. Because we want to reuse ofn in the save as dialog box too, we fill in only the * common * members that're used by both GetOpenFileName and GetSaveFileName. WM_CREATE Section Is a Great Place to Do Once-Only Initialization.
.ELSEIF UMSG == WM_SIZE MOV EAX, LPARAM MOV EDX, EAX SHR EDX, 16 And Eax, 0fffh Invoke MoveWindow, Hwndit, 0, 0, Eax, EDX, TRUE
We receive WM_SIZE messages when the size of the client area of our main window changes. We also receive it when the window is first created. In order to be able to receive this message, the window class styles must include CS_VREDRAW and CS_HREDRAW styles. We use this opportunity to resize our edit control to the same size as the client area of the parent window. First we have to know the current width and height of the client area of the parent window. We get this info from lParam. The high word of lParam contains the height and the low word of lParam the width of the client area. We then use the information to resize the edit control by calling MoveWindow function which, in addition to changing the position of the window, can alter the size too. .IF AX == idm_open mov off == d, _ _ _ _ _ g g Name, Addr OFN
WHEN THE USER SELECTS FILE / Open Menu Item
. IF EAX == True Invoke CreateFile, AddR Buffer, / Generic_read or generic_write, / file_share_read or file_share_write, / null, open_existing, file_attribute_archive, / null mov Hfile, EAX
After the user selects a file to open, we call CreateFile to open the file. We specifies that the function should try to open the file for read and write. After the file is opened, the function returns the handle to the opened file which we store in a global variable for future use This function has the following syntax:. CreateFile proto lpFileName: DWORD, / dwDesiredAccess: DWORD, / dwShareMode: DWORD, / lpSecurityAttributes: DWORD, / dwCreationDistribution: DWORD /, dwFlagsAndAttributes: DWORD /, hTemplateFile: DWORD
DwdesiredAccess Specifies Which Operation You Want to Perform on The File.
0 Open the file to query it, you have to rights. Generic_ve open the file forread. Generic_write open the file for write.
DWSHAREMODE Specifies Which Operation You Want To Allow Other Processes To Perform on The File Tat 's Being Opened.
0 DON 'THARE THE FILE WILE WILE_SHARE_READ ALLOW OTHER Processes To Read The Data from The File Being Other Processes To Write Data To The File Being Opened.
LPSecurityAttributes Has No Significance Under Windows 95.
DWCREATIONDISTRIBUTION SPECIFORM WHEN The File Specified in lpFileName EXISTS or WHEN IT DOESN'T.
CREATE_NEW Creates a new file. The function fails if the specified file already exists. CREATE_ALWAYS Creates a new file. The function overwrites the file if it exists. OPEN_EXISTING Opens the file. The function fails if the file does not exist. OPEN_ALWAYS Opens the file , if it exists. If the file does not exist, the function creates the file as if dwCreationDistribution were CREATE_NEW. TRUNCATE_EXISTING Opens the file. Once opened, the file is truncated so that its size is zero bytes. The calling process must open the file with at least GENERIC_WRITE access. The function fails if the file does not exist. dwFlagsAndAttributes specifies the file attributesFILE_ATTRIBUTE_ARCHIVE The file is an archive file. Applications use this attribute to mark files for backup or removal. FILE_ATTRIBUTE_COMPRESSED The file or directory is compressed. for a File, this Means That All of the data in the file is compressed. for a Directory, this Means That Compression Is The Default for Newly Created Fi les and subdirectories. FILE_ATTRIBUTE_NORMAL The file has no other attributes set. This attribute is valid only if used alone. FILE_ATTRIBUTE_HIDDEN The file is hidden. It is not to be included in an ordinary directory listing. FILE_ATTRIBUTE_READONLY The file is read only. Applications can read .
INVOKE GLOBALLOC, GMEM_MOVEABLE OR GMEM_ZEROINIT, MEMSIZE
Mov HMemory, EAX
Invoke GlobalLock, HMemory
Mov Pmemory, EAX
When the file is opened, we allocate a block of memory for use by ReadFile and WriteFile functions. We specify GMEM_MOVEABLE flag to let Windows move the memory block around to consolidate memory. GMEM_ZEROINIT flag tells GlobalAlloc to fill the newly allocated memory block with zeroes. When GlobalAlloc returns successfully, eax contains the handle to the allocated memory block. We pass this handle to GlobalLock function which returns a pointer to the memory block.invoke ReadFile, hFile, pMemory, MEMSIZE-1, ADDR SizeReadWrite, NULL invoke SendMessage, hwndEdit , WM_SETTEXT, NULL, PMEMORY
When the memory block is ready for use, we call ReadFile function to read data from the file. When a file is first opened or created, the file pointer is at offset 0. So in this case, we start reading from the first byte in the file onwards. The first parameter of ReadFile is the handle of the file to read, the second is the pointer to the memory block to hold the data, next is the number of bytes to read from the file, the fourth param is the address of the variable of DWORD size that will be filled with the number of bytes actually read from the file. After we fill the memory block with the data, we put the data into the edit control by sending WM_SETTEXT message to the edit control with lParam containing The Pointer to the Memory Block. After this Call, The Edit Control Shows The Data In Its Client Area.
Invoke Closehandle, Hfile Invoke Globalunlock, Pmemory Invoke Globalfree, HMemory .ndif
At this point, we have no need to keep the file open any longer since our purpose is to write the modified data from the edit control to another file, not the original file. So we close the file by calling CloseHandle with the file handle as its parameter. Next we unlock the memory block and free it. Actually you do not have to free the memory at this point, you can reuse the memory block during the save operation later. But for demonstration purpose, I choose to free it here .invoke setfocus, hwndedit
When the open file dialog box is displayed on the screen, the input focus shifts to it. So after the open file dialog is closed, we must move the input focus back to the edit control. This end the read operation on the file. At this point, the user can edit the content of the edit control.And when he wants to save the data to another file, he must select File / Save as menuitem which displays a save as dialog box. The creation of the save as dialog box is not much different from the open file dialog box. in fact, they differ in only the name of the functions, GetOpenFileName and GetSaveFileName. You can reuse most members of the ofn structure too except the Flags member.
Mov off.flags, OFN_LONGNAMES OR / OFN_EXPLORER OR OFN_HIDEREADONLY
In our case, we want to create a new file, so OFN_FILEMUSTEXIST and OFN_PATHMUSTEXIST must be left out else the dialog box will not let us create a file that does not already exist. The dwCreationDistribution parameter of the CreateFile function must be changed to CREATE_NEW Since We want to create a new file. The remaining code is identical to those in the open file section except the fol
invoke SendMessage, hwndEdit, WM_GETTEXT, MEMSIZE-1, pMemory invoke WriteFile, hFile, pMemory, eax, ADDR SizeReadWrite, NULLWe send WM_GETTEXT message to the edit control to copy the data from it to the memory block we provide, the return value in eax Is The Length of The Data INSIDE The Buffer. After The Data IS in The Memory Block, We Write The New File.
