PRB: Windows 3.1 SDK HOOKS Sample Causes a GP Fault

CAUSE

In the HOOKS sample, CBTFunc() is incorrectly casting lParam (a DWORD value) to a WORD when it calls CallNextHookEx() to pass the info on to the next hook in the hook chain. This causes the receiving hook function to receive the CBT notification with a modified lParam (the HIWORD stripped off), thus translating to an invalid pointer and eventually causing a GPF.

A GPF occurs similarly when an application that installs a WH_CALLWNDPROC hook is run along with the HOOKS sample and the CallWndProc hook menu-item is selected. In the same manner, the HOOKS sample function CallWndProcFunc() incorrectly casts its lParam (a DWORD value) to a WORD on its call to CallNextHookEx().

In addition, the HOOKs sample will GPF when the WH_JOURNALRECORD hook is installed and some other application calls SetSysModalWindow(). As mentioned in the Windows 3.1 SDK help,

If a WH_JOURNALRECORD hook is in place when SetSysModalWindow is called,
the hook is called with a hook code of <B>HC_SYSMODALON</B> (for turning on the system-modal window) or <B>HC_SYSMODALOFF</B> (for turning off the system-modal window).
				

   if( nCode >= 0) {
   // do not  record if SysModalOn or SysModalOff and let other filter know
   // about it.

      if(nCode == HC_SYSMODALON || nCode == HC_SYSMODALOFF)
      {
      // let other hook filters know about this
         CallNextHookEx(hhookHooks[JOURNALRECORDINDEX], nCode, wParam,
            lParam);
         return;
      }