Printable View
Hello,
I just wanted to how can i make my application lock certain drives or folder or file? and make it unaccessible to all applications till my application does not turn off the lock? Please provide me some hints so i can proceed on making my application.
Thanks in advance :)
Open a certain file and specify the share mode. I'm not sure about directories.
NO! that doesn't work out, because it occupies memory i just want to place a lock on it (and even make it invisible), and perhaps not only for files but also for folders and whole drives.
... >_>
You need to better specify your question. valaris answered exactly what you asked. Now you are asking something different. Do you want to hide files, & keep people from accessing them? If so, why not use an encrypted partition/file?
hello Cactus,
Kindly read my post first..
"Hello,
I just wanted to how can i make my application lock certain drives or folder or file?"
does valaris solution work for folder or drives? :o
And why not? In Linux, a file is a drive, so yes, it does. I would expect Windows to behave similarly -- is a drive not a HANDLE of some sort? I believe there are paths to open a drive with the proper invocation of CreateHandle(). The equivalent may or may not be possible in C#, not at least without some difficultly. Access could not be parallel -- two things writing to the same drive at the same time would be chaos.
At any rate, you've missed my point. A simple clarification was needed to your original post. Furthermore, I still feel your second post clouds the issue, specifically:
What is it? A file generally does not reside in memory -- it resides on disk. While it is possible to have a file or a file's contents in memory, I am unsure of what you mean here.Quote:
Originally Posted by chottachatri
I suppose a proper kernel-land hook could block the presence of a file, likewise, if you could embed code in user-land processes and capture calls to the proper system calls. However, masking the presence of a file or directory is similar to the behaviour of a root kit. Just why do you want to hide a file?
Proper file permissions and/or holding the file open would probably fill you need, which, we have no idea about. Perhaps you should... clarify, and tell us what you're trying to accomplish?
And just what would "locking" a directory do?
In linux everything is a file. I am not a Linux user.
Say suppose i have some private things in my folder or drive and i want to lock it then how to do it?See this link you will get better idea of what i want to create and why i want to create.
Hide Folders XP - Files and Folders Password Protection - Hide Folder Lock Folder Password Protect Folder - FSPro Labs
I'd suggest you use file/directory permissions then (only works on NTFS).
And catcus: you are way off on how Windows work. Directories aren't files, and handles aren't drives/directories. CreateHandle creates a new handle, but not a directory/drive. I don't even know if it's possible to open a directory to lock it.
Nevertheless, these solution would require the app to permanently reside in memory since as soon as it closes, the locks go away.
Thanks Elysia! you got what i wanted to do.
This cactus is really a cactus on this forum. Everytime i post my query he behaves as though he knows everything and misguides newbies in such a way that they themselves forget what was their query and think twice before posting another query! :o
I wouldn't go around badmouthing members of the board, however.
There was a slight typo on my part -- I meant CreateFile(), not CreateHandle (which is not a Win32 API function, to my knowledge). With CreateFile(), you can open a drive, ie:Quote:
And catcus: you are way off on how Windows work. Directories aren't files, and handles aren't drives/directories. CreateHandle creates a new handle, but not a directory/drive. I don't even know if it's possible to open a directory to lock it.
...which was the point of my post. Unfortunately, the typo makes it rather confusing.Quote:
When opening a physical drive x, the lpFileName string should be the following form: \\.\PhysicalDriveX. Hard disk numbers start at zero.
No, and I was quite aware of that. It was an analogy -- the two systems are quite similar in some respects. This is one of them. In Linux, both drives & files are openable as files. It is the same in Windows.Quote:
In linux everything is a file. I am not a Linux user.
I never equated a directory to a file, nor said you could open it to lock it, in fact, read the last line of that post. I was attempting to both get clarification from the OP, and suggest possible things he/she was looking for. It would seem that the answer was, in fact, one of the things I listed. Apparently, I merely confused the issue - my apologies.
Aha! That makes more sense.Quote:
Originally Posted by Cactus_Hugger
I am unsure of how much CreateFile can actually do (miserably misnamed function!), but you're probably correct or not far off.