--- rxvt/W11/w32/event.c	2003-03-31 17:26:54.000000000 -0800
+++ /desktop/rxvt--/rxvt/W11/w32/event.c	2005-04-03 21:40:37.498987200 -0700
@@ -107,7 +107,7 @@ QEvent(WinEventQ *q, NT_window *window,U
    The specific problem is that calling DefWindowProc()
    in response to a WM_SYSCOMMAND will cause windows to run its
    own event loop waiting for the mouse up event.  The application
-   therefore cannot rely on it's main event loop to get run for
+   therefore cannot rely on its main event loop to get run for
    each event.  Without running multiple threads, or setjmp, there
    is little recourse for alerting the application in the
    traditional X manner to Expose events while the window is
@@ -315,9 +315,16 @@ LONG NT_handleMsg(
                 case VK_F10:
                 case VK_F11:
 	        case VK_F12:
+                    QEvent(wineventq,window,message,wParam,lParam);
+                    break;
 	        case VK_ADD:
 	        case VK_SUBTRACT:
+                  if (GetKeyState(VK_SHIFT) & 0x8000) {
 		    QEvent(wineventq,window,message,wParam,lParam);
+                    return 0L;
+                  } else {
+                    return (NT_default(hWnd, message, wParam, lParam));
+                  }
 		    break;
 		default:
 		    return  (NT_default(hWnd, message, wParam, lParam));
