Patents by Inventor Nicholas Judge

Nicholas Judge has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).

  • Publication number: 20070227683
    Abstract: A method for forming an investment casting core comprises cutting a patterned core precursor from refractory metal-based sheet. The cutting forms recast along the cuts. An oxide is grown on non-recast areas. The recast is substantially chemically removed but substantially leaving the oxide. The core precursor may then be shaped.
    Type: Application
    Filed: September 19, 2005
    Publication date: October 4, 2007
    Inventors: Nicholas Judge, Joseph Parkos, Gary Lomasney
  • Publication number: 20060212727
    Abstract: Transitioning to a suspend to RAM sleeping state while also protecting against power losses while sleeping is provided. System state context data is saved to non-volatile storage and components in the computer system prepare to transition to a suspend to disc sleeping. A transition to the suspend to RAM sleeping state is then effected. Alternatively, after the system context is saved and the components are prepared to transition, the system may wake to a working state. The components may be directed to prepare for transitioning to a suspend to RAM sleeping state, and then the BIOS may be directed to execute the transition. In either embodiment, if power to the system is lost while the system is in the suspend to RAM system state, then the system may resume to a working state by reading the context file stored to non-volatile storage.
    Type: Application
    Filed: March 16, 2005
    Publication date: September 21, 2006
    Applicant: Microsoft Corporation
    Inventors: Nicholas Judge, Jacob Oshins, Stephane Plante, Andrew Ritz
  • Publication number: 20050030555
    Abstract: A job processing framework according to the present invention allows an application to be developed independent of any particular service. Tasks performed by the application are broken up into smaller units of work, or “jobs,” which are each bound to a particular service at execution, or “deployment.” The binding occurs via a “deployer” comprising a configuration source. The configuration source includes instructions that bind particular jobs with a particular service. Therefore, if improved services are developed subsequent to the application, only the configuration source needs to be updated, not the application. Accordingly, significant time and expense is saved by allowing applications to be developed independent of particular services.
    Type: Application
    Filed: May 17, 2004
    Publication date: February 10, 2005
    Inventors: John Phenix, Nicholas Judge
  • Publication number: 20050034127
    Abstract: A service interface enables an application to be developed independently from a particular service. At execution of the application, the application is wrapped or bound to a service. Advantageously, a configuration file includes instructions that bind particular applications with a particular service. Therefore, if improved services are developed after the application is written, only the configuration file needs to be updated, not the application source code. Accordingly, significant time and expense is saved by allowing applications to be developed independently from particular services.
    Type: Application
    Filed: May 17, 2004
    Publication date: February 10, 2005
    Inventors: John Phenix, Nicholas Judge