Michael R Marcelais

6591379, Jul 8, 2003

Jun 23, 2000

09/602051

Eric A. LeVine - Seattle WA
Kirk A. Glerum - Redmond WA
Matthew J. Ruhlen - Redmond WA
Michael R. Marcelais - Redmond WA
Jeff David Mitchell - Waterloo, CA
Steven Miles Greenberg - Hastings-on-Hudson NY

Microsoft Corporation - Redmond WA

H02H 305

714 38, 714 15

A method and system for injecting an exception into a hung program module to recover unsaved data. The method and system allows a user to determine that the program module is hung and inject an exception into the hung program module. In response to the injected exception, program code, within the program module, is activated to detect the crash and launch a failure reporting executable program that instructs the hung program module to execute its data recovery program. The file recovery program recovers the unsaved data and notifies the failure reporting executable program when it has completed the data recovery. Once the failure reporting executable program receives the notification, it will instruct the operating system to restart the program module. The restarted program module then displays a user interface with a list of the unsaved data that were recovered. The user interface also provides controls for a user to select, from the list of recovered data, the data that the program module will keep.

6675295, Jan 6, 2004

Jun 19, 2000

09/596591

Michael R. Marcelais - Redmond WA
Brian T. Hill - Renton WA
Eric LeVine - Seattle WA
Steven Miles Greenberg - Hastings-on-Hudson NY

Microsoft Corporation - Redmond WA

G06F 15177

713 2, 713 1, 713200, 714 1, 714 2, 714 38

Methods and systems for detecting and correcting computer software problems that cause an application program to crash upon startup are provided. Unsafe startup actions that are costly to initiate in terms of processor time and memory are handled by placing an unsafe startup action marker into the system registry prior to attempting startup. If an unsafe program module starts or boots successfully without causing the software application to crash, the unsafe startup action marker is deleted from the system registry. If loading the unsafe program module causes the application to crash, then startup actions, including corrective actions, are written into the unsafe startup action marker and are used on subsequent startup of the crashed application program to instruct the application on how to fix the problem. Other unsafe startup actions that are not costly in terms of processor time and memory are initially handled by an exception handler. If the application crashes as a result of such an unsafe startup action, then an unsafe startup action marker is written to the system registry as described above.

6701454, Mar 2, 2004

Jun 5, 2000

09/588165

Kevin Joseph Fischer - Redmond WA
Eric Fox - Seattle WA
Eric A. LeVine - Seattle WA
Brian T. Hill - Renton WA
Michael R. Marcelais - Redmond WA
Jeffrey Larsson - Seattle WA

Microsoft Corporation - Redmond WA

G06F 1100

714 15, 714 38

Method and system for recovering information from open files during a failure in a program module. Once a failure is detected in the program module, control passes to an exception handler that determines whether the open files have been modified. If so, the open files are verified and stored as recovery versions of the files at the time of the failure. The program module is then terminated and restarted. Upon restarting the program module, the recovery version of the file at the time of the failure is opened and displayed to the user.

6857085, Feb 15, 2005

May 15, 2000

09/570621

Matthew J. Ruhlen - Redmond WA, US
Michael R. Marcelais - Redmond WA, US
Brian T. Hill - Renton WA, US

Microsoft Corporation - Redmond WA

G06F011/00

714 38, 714 48, 714124

A system and method for handling the generation of an unexpected exception by an application. When the application generates an unexpected exception (i. e. , crashes), the application's exception filter launches an outside exception handling program (EHP) that is separate and distinct from the application. Through a special protocol, the application and the EHP collaborate in responding to the unexpected exception. In this protocol, the application and the EHP communicate through kernel objects accessible by handles in a shared memory structure that the application creates before launching of the exception handling program and then shares with the EHP. Through this shared memory, the application also provides the EHP with information about the types of recovery options to offer the user. Through a graphical user interface, the EHP is then responsible for notifying the user of the application that an unexpected exception has occurred. Through the graphical user interface, the EHP also provides the user with the ability to specify various courses of action in response to the unexpected exception.

7089455, Aug 8, 2006

May 5, 2004

10/839623

Matthew J. Ruhlen - Redmond WA, US
Michael R. Marcelais - Redmond WA, US
Brian T. Hill - Renton WA, US

Microsoft Corporation - Redmond WA

G06F 11/00

714 38, 717124

A system and method for handling the generation of an unexpected exception by an application. When the application generates an unexpected exception (i. e. , crashes), the application's exception filter launches an outside exception handling program (EHP) that is separate and distinct from the application. Through a special protocol, the application and the EHP collaborate in responding to the unexpected exception. In this protocol, the application and the EHP communicate through kernel objects accessible by handles in a shared memory structure that the application creates before launching of the exception handling program and then shares with the EHP. Through this shared memory, the application also provides the EHP with information about the types of recovery options to offer the user. Through a graphical user interface, the EHP is then responsible for notifying the user of the application that an unexpected exception has occurred. Through the graphical user interface, the EHP also provides the user with the ability to specify various courses of action in response to the unexpected exception.

7139894, Nov 21, 2006

Sep 12, 2003

10/661721

Rob Martin Mensching - Redmond WA, US
Michael R. Marcelais - Redmond WA, US
Marcin Szuster - Seattle WA, US

Microsoft Corporation - Redmond WA

G06F 12/00
G06F 13/00
G06F 17/30
G06F 11/00

711170, 711147, 711148, 711149, 711150, 711151, 711152, 711153, 707201, 714 15

A system and methods for sharing configuration information with multiple services, or processes, via shared memory. The configuration information, typically, comprises runtime information utilized by processes during operation, including without limitation, information describing data communication connections between the local computer and other computing resources (i. e. , port and wire information), and information defining numeric values or character string values (i. e. , genre and record information). The system architecture includes a plurality of APIs which: reside at the local computer; populate, manage, and control access to a shared memory containing the configuration information; and, are executable only by processes executing at the local computer, thereby limiting access to the shared memory. Access to the configuration information is further limited to only those processes identified as having appropriate permission. The methods enable the configuration information of the shared memory to be modified during local computer operation and without impeding access to the configuration information.

7302531, Nov 27, 2007

Nov 15, 2006

11/599978

Rob Martin Mensching - Redmond WA, US
Michael R. Marcelais - Redmond WA, US
Marcin Szuster - Seattle WA, US

Microsoft Corporation - Redmond WA

G06F 12/00
G06F 12/14
G06F 13/00
G06F 17/30
G06F 11/30

711147, 711148, 711149, 711150, 711151, 711152, 711153, 711170, 707201, 714 15

A system and methods for sharing configuration information with multiple services, or processes, via shared memory. The configuration information, typically, comprises runtime information utilized by processes during operation, including without limitation, information describing data communication connections between the local computer and other computing resources (i. e. , port and wire information), and information defining numeric values or character string values (i. e. , genre and record information). The system architecture includes a plurality of APIs which: reside at the local computer; populate, manage, and control access to a shared memory containing the configuration information; and, are executable only by processes executing at the local computer, thereby limiting access to the shared memory. Access to the configuration information is further limited to only those processes identified as having appropriate permission. The methods enable the configuration information of the shared memory to be modified during local computer operation and without impeding access to the configuration information.

7814288, Oct 12, 2010

Mar 29, 2007

11/731262

Thomas S. Coon - Kirkland WA, US
Michael R. Marcelais - Renton WA, US
Christopher C. White - Seattle WA, US

Microsoft Corporation - Redmond WA

G06F 12/00
G06F 13/00
G06F 13/28
G06F 11/00

711163, 711100, 711111, 711170, 714100, 714 25, 714 37, 714 39, 714 48, 714 53

Applications are protected from being exposed to exploits and instabilities due to memory operations involving zero byte allocations. Memory operations involving a zero byte allocation are handled by a zero byte memory manager. When an application requests a zero byte allocation, a pointer to a protected part of memory is returned such that when the application attempts to read and/or write to the location the program flow is interrupted.