Jump to content

Recommended Posts

Posted

Why is the function creating a file that is always locked?

#include "winapi.au3"
#include <winapifiles.au3>

#pragma compile(console, true)
#NoTrayIcon


func _CreateFileW($lpFileName, $dwDesiredAccess, $dwShareMode, $lpSecurityAttributes, $dwCreationDisposition, $dwFlagsAndAttributes, $hTemplateFile)
    local $aResult = DllCall("kernel32.dll", "handle", "CreateFileW", "wstr", $lpFileName, "dword", $dwDesiredAccess, "dword", $dwShareMode, "struct*", $lpSecurityAttributes, "dword", $dwCreationDisposition, "dword", $dwFlagsAndAttributes, "ptr", $hTemplateFile)
    return $aResult[0]
endfunc

local $hMyFile = _CreateFileW('c:\\dev2.txt', BitOR($GENERIC_READ, $GENERIC_WRITE), BitOR($FILE_SHARE_READ, $FILE_SHARE_WRITE, $FILE_SHARE_DELETE), 0, $CREATE_NEW, BitOR($FILE_ATTRIBUTE_NORMAL, $FILE_ATTRIBUTE_TEMPORARY, $FILE_FLAG_DELETE_ON_CLOSE), 0); 

Sleep(100000)

 

Posted

Doesn't seem to work :(

 

local $hMyFile = _WinAPI_CreateFileEx('c:\\dev2.txt', _ 
                                            BitOR($GENERIC_READ, $GENERIC_WRITE), _
                                            BitOR($FILE_SHARE_READ, $FILE_SHARE_WRITE, $FILE_SHARE_DELETE), _
                                            0, _
                                            $CREATE_ALWAYS, _ 
                                            BitOR($FILE_ATTRIBUTE_TEMPORARY, $FILE_FLAG_DELETE_ON_CLOSE), _
                                            0); 
ConsoleWrite($hmyfile)

 

Posted

Creates the file still locked for editing though.

 

local $hMyFile = _WinAPI_CreateFileEx('c:\\dev2.txt', _ 
                                           $CREATE_ALWAYS, _ 
                                            BitOR($GENERIC_READ, $GENERIC_WRITE), _
                                            BitOR($FILE_SHARE_READ, $FILE_SHARE_WRITE, $FILE_SHARE_DELETE), _
                                            BitOR($FILE_ATTRIBUTE_TEMPORARY, $FILE_FLAG_DELETE_ON_CLOSE), _
                                            0, _
                                            0); 

 

Posted

Have you tried using _WinAPI_CloseHandle to close the handle to the file after you've created it?

If I posted any code, assume that code was written using the latest release version unless stated otherwise. Also, if it doesn't work on XP I can't help with that because I don't have access to XP, and I'm not going to.
Give a programmer the correct code and he can do his work for a day. Teach a programmer to debug and he can do his work for a lifetime - by Chirag Gude
How to ask questions the smart way!

  Reveal hidden contents

I hereby grant any person the right to use any code I post, that I am the original author of, on the autoitscript.com forums, unless I've specifically stated otherwise in the code or the thread post. If you do use my code all I ask, as a courtesy, is to make note of where you got it from.

Back up and restore Windows user files _Array.au3 - Modified array functions that include support for 2D arrays.  -  ColorChooser - An add-on for SciTE that pops up a color dialog so you can select and paste a color code into a script.  -  Customizable Splashscreen GUI w/Progress Bar - Create a custom "splash screen" GUI with a progress bar and custom label.  -  _FileGetProperty - Retrieve the properties of a file  -  SciTE Toolbar - A toolbar demo for use with the SciTE editor  -  GUIRegisterMsg demo - Demo script to show how to use the Windows messages to interact with controls and your GUI.  -   Latin Square password generator

Posted

Remarks

_WinAPI_CreateFileEx

When an application is finished using the object handle returned by this function, use the _WinAPI_CloseHandle() function to close the handle.
This not only frees up system resources, but can have wider influence on things like sharing the file or device and committing data to disk.

So yes i guess you have to close it.

  Reveal hidden contents

IUIAutomation - Topic with framework and examples

Au3Record.exe

Posted (edited)

I made the assumption that the file was not being created at all.  Your question clearly states that it is.  Perhaps I should work on my reading comprehension, lol.  Anyways, I believe your problem is being caused by FILE_FLAG_DELETE_ON_CLOSE.  Microsoft states: "If there are existing open handles to a file, the call fails unless they were all opened with the FILE_SHARE_DELETE share mode".  Perhaps the file is not locked, just prevented from being opened without the proper flags?

Edited by Tekk

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...