DR. THOMAS T. MILLER, M.D.
Osteopathic Medicine at 116 Ave, Bellevue, WA

5745902, Apr 28, 1998

Jul 6, 1992

7/909984

Thomas J. Miller - Bellevue WA
Gary D. Kimura - Kirkland WA

Microsoft Corporation - Redmond WA

G06F 1730

707200

A multiple file name referencing system stores multiple file names in a file. These multiple file names include an operating system formatted file name and an application formatted file name. When an operating system formatted file name is created or renamed, the multiple file name referencing system automatically generates an application formatted file name having a potentially different format from, but preserving the extension of, the operating system formatted name. The multiple file name referencing system similarly generates an operating system formatted name upon creation or renaming of an application formatted name. A B-tree is provided which contains an operating system entry for the operating system formatted name and an application entry for the application formatted name, each entry containing the address of the same file to which both names refer. The multiple file name referencing system converts the operating system formatted file name to the application formatted file name by accessing the B-tree with reference to the operating system entry, and vice versa. As a result, either file name can be used to directly reference the file without requiring additional file name translation.

2012025, Oct 11, 2012

Jun 22, 2012

13/530269

Jonathan M. Cargille - Seattle WA, US
Thomas J. Miller - Yarrow Point WA, US
William R. Tipton - Seattle WA, US

Microsoft Corporation - Redmond WA

G06F 17/30

707649, 707E17005, 707E1701

Aspects of the subject matter described herein relate to checkpoints for a file system. In aspects, updates to the file system are organized into checkpoint buckets. When a checkpoint is desired, subsequent updates are directed to another checkpoint bucket. After global tables have been updated for updates in the current checkpoint bucket, a logical copy of the global tables is created. This logical copy is stored as part of the checkpoint data. To assist in recovery, a checkpoint manager may wait until all updates of the current checkpoint bucket have been written to storage before writing final checkpoint data to storage. This final checkpoint data may refer to the logical copy of the global tables and include a validation code to verify that the checkpoint data is correct.

2011031, Dec 22, 2011

Jun 17, 2010

12/817219

Thomas J. Miller - Yarrow Point WA, US
Jonathan M. Cargille - Seattle WA, US
William R. Tipton - Seattle WA, US
Surendra Verma - Bellevue WA, US

MICROSOFT CORPORATION - Redmond WA

G06F 12/00, G06F 11/00

711154, 711E12001, 714699, 714E11001

Aspects of the subject matter described herein relate to error detection for files. In aspects, before allowing updates to a clean file, a flag marking the file as dirty is written to non-volatile storage. Thereafter, the file may be updated as long as desired. Periodically or at some other time, the file may be marked as clean after all outstanding updates to the file and error codes associated with the file are written to storage. While waiting for outstanding updates and error codes to be written to storage, if additional requests to update the file are received, the file may be marked as dirty again prior to allowing the additional requests to update the file. The request to write a clean flag regarding the file may be done lazily.

5247676, Sep 21, 1993

Feb 4, 1992

7/830730

Mark C. Ozur - Redmond WA
Charles T. Lenzmeier - Bothwell WA
Thomas J. Miller - Bellevue WA

Digital Equipment Corporation - Maynard MA

G06F 938, G06F 940, G06F 942

395650

A method is provided for use in a computer system, the method for performing callbacks to a first calling thread that has made an RPC to a second called thread comprising the steps of: creating at least one respective helper thread in the address space of the second called thread; and for each respective created helper thread, providing a respective thread-specific identifying mechanism for identifying the first calling thread.

2013032, Dec 5, 2013

Aug 9, 2013

13/963675

Thomas J. Miller - Bellevue WA, US
Robert G. Atkinson - Woodinville WA, US

MICROSOFT CORPORATION - Redmond WA

G06F 17/30

707703

A transactional file system wherein multiple file system operations may be performed as a transaction. An application specifies that file system-related operations are to be handled as a transaction, and the application is given a file handle associated with a transaction context. For file system requests associated with a transaction context, a file system component manages operations consistent with transactional behavior. Logging and recovery are also facilitated by logging page data separate from the main log with a unique signature that enables the log to determine whether a page was fully flushed to disk prior to a system crash.

2013006, Mar 14, 2013

Nov 23, 2011

13/303170

Chesong Lee - Issaquah WA, US
Thomas J. Miller - Yarrow Point WA, US
Neal R. Christiansen - Bellevue WA, US
Matthew S. Garson - Seattle WA, US

Microsoft Corporation - Redmond WA

G06F 11/08, G06F 11/14

714 61, 714E11118, 714E1103

Aspects of the subject matter described herein relate to querying and repairing data. In aspects, a component may detect that data on storage has become corrupted. In response, the component may request data from one or more redundant copies of the data and may determine which of the redundant copies, if any, are not corrupted. If a non-corrupted copy is found, the component may send a request that the corrupted data be repaired and may identify the non-corrupted copy to use to repair the corrupted data.