Journal Playback hook?

  • Thread starter Thread starter Alex Chmut
  • Start date Start date
A

Alex Chmut

Hello everybody,

Does anybody know why MSFT does no longer allows to install Journal Playback
hooks when UAC is enabled?
Such restriction causes many troubles to the applications that generate
key-strokes and the SendKeys-like functions are no longer working (for even
Office 2007 VBA and .NET).

I can also see that other people hampering on this
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=221181&SiteID=1

Does anybody know what are MSFT's plans as to such situation?

Thanx,
AlexC
 
Hey Alex--

I think some of their reasoning is provided on this blog and there is much
discussion on it as you say in the comments of different blogs and on MSDN
forum threads. You might want to put that into the msdn general group and
see if youcan draw some Softie responses:

Jouarnal PlaybackProc Function
http://msdn.microsoft.com/library/d...ference/hookfunctions/journalplaybackproc.asp

Is the SendKeys juice worth the squeeze?
http://blogs.msdn.com/michkap/archive/2006/06/10/625285.aspx

You can also interact by commenting to Micheal Kaplan [MSFT] who is a
developer and Technical Lead on the Globalization Infrastructure, Fonts,
and Tools team who may deal directly with this using the email contact box
on his blog.

http://blogs.msdn.com/michkap/articles/280092.aspx

CH

P.S.Michael Kaplan has also blogged on the Red Screen of Death in Longhorn
alpha prior to Vista Beta. My undrestanding is that the Red Screen of Death
is what you see when you're sitting there and you evoke a blue screen of
death and a bull is charging you simultaneously. It probably happens to
road warriors who are mobile more often than people on desktops.


The Red Screen of Death in Longhorn/ Longhorn on Virtual PC
http://blogs.msdn.com/michkap/archive/2005/05/07/415335.aspx
 
Hello,

Unfortunately, due to the potential for privilege escalation, UAC prevents
applications from installing complete system-level hooks and also prevents
the sending of window messages to processes/windows that are running in a
higher integrity level (for example, a process running that does not require
administrative privilges cannot send window messages to a process that is
running with administrative privileges).

An application can bypass this behavior by setting uiAccess=true in their
manifest. However, I believe that Microsoft's intention is for this setting
to only be used by accessibility-related applications.

Here's some related reading:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnlong/html/AccProtVista.asp

http://msdn.microsoft.com/library/d...ry/en-us/IETechCol/dnwebgen/ProtectedMode.asp

- JB

Vista Support FAQ
http://www.jimmah.com/vista/
 
Hello Jimmy,

I know about that. But we seem not to be able to have uiAccess="true"
without also level="requireAdministrator" which is, of course, not an
acceptible way to go with. But I should also mention the fact that we cannot
install this type of hook (having 'access denied' return value from
::SetWindowsHookEx()) when even running under full admin. The only possible
way to do that is to disable UAC at all.
Our app CAN be categorized as an accessibility-related one, and we don't
have any problems installing other types of hooks (like WH_KEYBOARD,
WH_MOUSE, WH_CBT) as well as we don't have any problems with message
sendings cross processes.

As I posted originally this Journal Playback hook problem is spread through
out many areas, even for Office 2007 VBA and .NET key-sending functions, and
I'm pretty much sure MSFT is going to address this somehow. So I'd like to
know this 'how', if possible, and/or any of MSFT's plans in this regard.

Thanx,
AlexC
 
Back
Top