GetClipboardFormatName() returns the name of the atom that was registered by RegisterWindowMessage().

Don’t ask why

Christian

I’ll shot myself in the leg if i’ll spent another 3 minutes trying to understand all these calls:
::0×7E41FA8E(ir2,iR0)i.r1?e

i think i should look thru the system.txt to get back into these funny syntax rules
gj, anyway

Ido, I wish.

Anders, that’s a nifty little trick. Haven’t thought of using another function that manipulates the same atom table.

Did it eat my for loop ? No preview here, lets try again…

If you had asked on IRC I could have told you about a dirty little way to figure out the name of a registered message.

To dump all registered messages, do :
for (unsigned i=0xc000;i “LESSTHAN”=0xFFFF; ++i) if (GetClipboardFormatName(i,buf,ARRAYSIZE(buf)) …

I used this to figure out the messages used by the media center tray helper app.

I guess they figured they could save some mem by using the same table for both (Global class names are stored here aswell)

Can you write something intersting to me for crying out loud i dont really understand these code battles yes i know you will delete this from this thread but at least got you doing something , enjoy it and life while your at it. ido.

Hmm…
Since user32!RegisterWindowMessageW just goes ahead and calls user32!NtUserRegisterWindowMessage and the latter immediately dispatches a win32k system call, presumably the USER atom table in question is not accessible from user-mode, otherwise the ntdll lookup function would have been used.
Anyway, your System plug-in code is totally illegible Almost as bad as Perl.

Right you are… Should have thought of that. Though on retrospect, calling NtUserGetAtomName is better since you’d need to get the atom table handle from win32k.sys anyway. Unless I missed some export for that as well

Note the presence of RtlLookupAtomInAtomTable in ntdll.dll. It’s even exported:

C:\WINDOWS\system32>dumpbin /exports ntdll.dll | findstr RtlLookupAtomInAtomTable
703 2BB 00028436 RtlLookupAtomInAtomTable = _RtlLookupAtomInAtomTable@12

It seems like it would be desirable to implement atom name lookup as a Windbg extension. Indeed, the debugger could use a boost in the whole USER/GDI department, to complement Spy++.