![]() Neb : Here's a proc that I wrote for that. Just registering it will not make the message go away. It has to actually contain a valid resource string for the message logged as well. APN It's not enough to register twapi.dll as a valid event source. As an example, me as a tcl programmer can write generic messages to the eventlog through means of Winserv or tclsvc. sure twapi cannot conatin application specific things. The actually message itself sure comes from the caller at runtime what's missing is the registration of twapi as a valid event source. The only way would be to create a resource file on the fly on the target system and that's just too much work. That message has to be in some resource, but obviously it can't be in twapi.dll which knows nothing about the application errors. Let's say your application wants to log a message "Danger, Danger! Resource do-hickey running low!". I don't know exactly how to do event source registration by myself (with ms api's this is not uncommon. Perhaps the necessary minimal resources/definitions could be build right into twapi.dll. Or am I missing something? MHo That's right. You could do this with a resource compiler but then you would not need TWAPI. So the messages would have to be "bound" to the resource. AFAIK, to register an event source requires a resource in a DLL or other file. APN Yes it would be nice but I'm not sure how. MHo: It would be nice if there where some way to register an event source to avoid such stupid error messages within eventvwr.exe. LV : Sure would be useful if this extension became a part of ActiveTcl!ĪPN : I believe TWAPI is now available via teapot though there might be a version skew. I would not be surprised if this were quite straight-forward, in Windows XP at least.ĪPN: You might want to look at WRAPI but you would have to write a Tcl binding for that. I'm afraid of trying something like this on my single development machine and trashing it!Īlastair Davies: asks if there is an API to configure wireless networking? For example, I would like to obtain a list of available wireless networks, and to connect to one. Possibly one could also just call WriteFile after opening the raw device \\.\PhysicalDriveN using CreateFile. Looking at the SDK, it looks like a job for DeviceIOControl but seems non-trivial, particularly for testing. (See the sample code at the link on the ROT page.)Įscargo : Can TWAPI be used to read and write to raw disk devices (unformatted disks without partitions)?ĪPN: No. ![]() Since the ROT is part of system state, it seemed like TWAPI would an appropriate way to access it. So you need to know what the objects are before you can use tcom on them. There aren't any COM interfaces in TWAPI since I assumed you would be much better off using the TCOM extension for COM-related stuff.Įscargo: From what I read about ROT, it identifies objects, not their COM interfaces. RT 11Apr2005 General discussionĮscargo : Can TWAPI be used to inspect the Running Object Table ( ROT)?ĪPN: No, I don't think so. So I would use TWAPI exclusively and fall back to nt-tcl if there was no alternative. I have used a few parts of the nt-tcl package and it worked fine for me at the time (4 years ago). I would definitely favor TWAPI as it is much newer and in active development. Comparing TWAPI and Ffidl on Windows compares it with TWAPI. TWAPI Alternativesįfidl also provides access to the Win32 API along with other platforms. The source code is in a mercurial repository on sourceforge. I do not always notice changes to this wiki page so please use the above links.
0 Comments
Leave a Reply. |