Printable View
Hello all. Been a while since I've been on here.
I have a program that uses a handle, and another program that needs access to that handle after it's created. All I know is the handle name.
Is there a way to get that handle with just the name of the handle?
(No is a perfectly fine answer if you are 100% sure. I just need to know which direction to take this.)
Thanks a bunch.
What sort of handle - Windows uses "handles" for many things:
Files
IPC objects
Windows
Icons and other graphical objects.
Threads
... The list goes on...
There isn't, as far as I'm aware, any "find the name belonging to this name". There may be side-ways approaches that will get you the (for example) filename from a handle (most likely, you'd have to use undocumented system calls to find the list of files open, and from that find the filename by matching with the handle). The same principle applies to other types of handles.
--
Mats
It's a waitable timer object. :)
I don't think there is a way to do that (officially).Quote:
Originally Posted by System_159
What are you ACTUALLY trying to do (bigger picture - you are asking how to remove a wheel-nut when you are actually wanting to fix a puncture).
Edit: Are you even sure that the object HAS a name? Waitable Timer Objects do not HAVE to have a name, only if CreateWaitableTimerEx is used does it have a name, if one is supplied.
--
Mats
I didn't think so.Quote:
Originally Posted by matsp
Basically I have several programs that all need to be synchronized together. So for that I've got a waitable timer as a seperate program.
Hard to get in to specifics without writing a novel(I've spent about a week and a half just deciphering the existing code to get to this point).
edit: and Yes, one thing that I am sure of is the name of the timer
But if you KNOW the name, then you can use OpenWaitableTimer() to open a new handle to the timer. I suspect that is what you really want to do anyways.
Edit: The reason I say "that's what you want to do anyways" is that going the other way around, is that I think handles are actually "process local", meaning that each process has it's own handle, that is different from the other processes that connect to the same timer.
--
Mats
Excellent. Thanks a bunch.
This will at least give me another launching pad. I may not be able to use it in the end, but I need to know about it in order to make that decision... if that makes sense. :D
Sure does.Quote:
Originally Posted by System_159
--
Mats