(b) Common name space for long and short filenames
Microsoft Corp.This patent was asserted by Microsoft Corp. against TomTom.
[Note: The claims listed are those claims surviving or amended by that Reexamination Certificate issued October 10, 2006.]
Summary / Description
| Summary / Description | The Sun386i VP/ix MS-DOS emulator subsystem contained a utility which created DOS compatible short filenames with Unix long filename support. Available under SunOS releases 4.0, 4.0.1 and 4.0.2 |
Basic Information
| Type of Prior Art | Online Publication |
| URL | http://docs.sun.com/app/docs/do... |
| Author/Creator | Sun Microsystems |
| Title | pcfs- DOS formatted file system |
| Publication Date | 1988 |
| Publisher | Sun Microsystems |
| Directions to Document Location | |
| Additional Information | |
Notes / To Do
| Notes | |
Excerpt
Files and directories created through pcfs must comply with either the DOS short file name convention or the long file name convention introduced with Windows 95. The DOS short file name convention is of the form filename[.ext], where filename generally consists of from one to eight upper-case characters, while the optional ext consists of from one to three upper-case characters.
The long file name convention is much closer to Solaris file names. A long file name can consist of any characters valid in a short file name, lowercase letters, non-leading spaces, the characters +,;=[], any number of periods, and can be up to 255 characters long. Long file names have an associated short file name for systems that do not support long file names (including earlier releases of Solaris). The short file name is not visible if the system recognizes long file names. pcfs generates a unique short name automatically when creating a long file name.
Given a long file name such as This is a really long filename.TXT, the short file name will generally be of the form THISIS~N.TXT, where N is a number. The long file name will probably get the short name THISIS~1.TXT, or THISIS~2.TXT if THISIS~1.TXT already exits (or THISIS~3.TXT if both exist, and so forth). If you use pcfs file systems on systems that do not support long file names, you may want to continue following the short file name conventions. See EXAMPLES.
When creating a file name, pcfs creates a short file name if it fits the DOS short file name format, otherwise it creates a long file name. This is because long file names take more directory space. Because the root directory of a pcfs file system is fixed size, long file names in the root directory should be avoided if possible.
When displaying file names, pcfs shows them exactly as they are on the media. This means that short names are displayed as uppercase and long file names retain their case. Earlier versions of pcfs folded all names to lowercase, which can be forced with the PCFS_MNT_FOLDCASE mount option. All file name searches within pcfs, however, are treated as if they were uppercase, so readme.txt and ReAdMe.TxT refer to the same file.
Relevance
Claims
Additional directory entries contain checksum
The computer-readable medium of Claim 12 wherein the step of creating at least one additional directory entry for the long filename further comprises the step of providing a checksum of the first filename in each additional directory entry.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Extra directory entries for long filenames
The method as recited in Claim 1 wherein each additional directory entry may hold only a fixed number of characters of the long filename and how many additional directory entries are created is dictated by how many additional directory entries are required to store characters of the long filename which are not already stored in the second directory entry.
Relevance
The long file names had to be broken down in order for the DOS format to store the long filename information.
The long file names had to be broken down in order for the DOS format to store the long filename information.
Claim Chart
All
Checksum in additional directory entries
The method as recited in Claim 1 wherein the step of creating at least one additional directory entry for the long filename further comprises the step of providing a checksum of the first filename in each additional directory entry.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Subsequent directory entries hold portion of long filename
[Note: The original Claim 22 was canceled in that Reexamination Certificate issued October 10, 2006.]
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Short filenames used by operating system
The method of Claim 24 wherein the program that uses only short filenames is an operating system.
Relevance
The SunOS could use short filenames if desired.
The SunOS could use short filenames if desired.
Claim Chart
All
Subsequent directory entries hold portion of long filename
[Note: The original Claim 9 was canceled in the Reexamination Certificate issued October 10, 2006.]
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Directory entries in computer-readable medium
In a computer system having a directory device for accessing directory entries and a file system that uses the directory entries to access files, a computer-readable medium holding computer-executable instructions for executing a method comprising the computer-implemented steps of:
(a) creating a first directory entry for a file wherein the first directory entry holds a short filename for the file and the location of the file;
(b) creating a second directory entry for a file wherein the second directory entry is configured to appear as if it holds a short filename to a program that uses only short filenames and wherein the second directory entry holds at least one portion of a long filename for the file, said long filename having more characters then the short filename; and
(c) accessing one of the first directory entries and the second directory entry by the directory service in order to access the file.
Relevance
The DOS floppies were directly compatible with MS-DOS.
The DOS floppies were directly compatible with MS-DOS.
Claim Chart
All
Comingled directory entries
In a computer system having a storage, a directory service for accessing directory entries and a file system that uses the directory entries to access files, a comnputer-readable medium holding computer-executable instructions for performing a method comprising computer-implementented steps of:
(a) creating a first direct0ry entry for a file wherein the first directory holds a short filename for the file and the location of the file;
(b) creating a second directory entry for the file wherein the second directory entry holds at least one portion of a long filename having a fixed number of characters;
(c) creating a sequence of at least one additional directory entry for holding a next sequential portion of the long filename;
(d) storing the first directory entry the second directory entry and the at least one additional directory entry on the storage among the directory entries used by the directory service; and
(e) accessing the second directory entry and the at least one additional directory entry by the directory service to access the file.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
Some
Additional directory entries of equal length
The computer-readable medium of Claim 12 wherein each additional directory entry may hold only a fixed number of characters of the long filename and how many additional directory entries are created is dictated by how many additional directory entries are required to store characters of the long filename which are not already stored in the second directory entry.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Long filename longer than short filename
The method as recited in Claim 1 wherein the long filename contains more characters than the short filename.
Relevance
by definition
by definition
Claim Chart
All
Signature identifies portion of long filename
The computer-readable medium of Claim 17 wherein the step of creating at least one additional directory entry for the long filename further comprises the step of providing a signature in each additional directory entry that identifies which portion of the long filename the additional directory entry holds.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Short filename checksum in second directory entry
The computer-readable medium of Claim 20 wherein a checksum of the short filename is stored in the second directory entry and the at least one additional directory entry.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Signature associated with additional directory entries
The method as recited in Claim 1 wherein the step of creating at least one additional directory entry for the long filename further comprises the step of providing a signature in each additional directory entry that identifies which portion of the long filename the additional directory entry holds.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Second directory entry holds longest applicable file name
In a computer system having a directory service for accessing directory entries and a file system that uses the directory entries to access files, a method comprising the computer-implemented steps of:
(a) creating a first directory entry for a file wherein the first directory entry holds a short filename for the file and the location of the file,
(b) creating a second directory entry for a file wherein the second directory entry is configured to appear as if it holds a short filename to a program that uses only short filenames and wherein the second directory entry holds at least one portion of a long filename for the file, said long filename having more characters then the short filename; and
(c) accessing one of the first directory entries and the second directory entry by the directory service in order to access the file.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Checksum in additional directory entries
The method as recited in Claim 7 wherein the step of storing the second directory entry further comprises the step of storing a checksum of the short filename in the second directory entry.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
First and second directory entries are adjacent
The method of clain 24 wherein the storage includes storage locations and wherein the first directory entry and the second directory entry are stored in adjacent storage locations.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Signature associated with additional directory entries
The method as recited in Claim 7 further comprising storing a signature in each of the second directory entry and the at least one additional directory entry that uniquely identifies which portion of the long filename is stored in that directory entry.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Long filename directory entries stored in sequence
[Note: The original Claim 14 was canceled in that Reexamination Certificate issued October 10, 2006.]
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
All
Signature identifies beginning of long filename
The computer-readable medium of Claim 12 wherein the step of creating the second directory entry further comprises the step of providing a signature in the second directory entry that identifies that the second directory entry holds the first portion of the long file name.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Long file name with signature
In a computer system having a storage, a directory service for accessing directory entries and a file system that uses the directory entries to access files, a method, comprising the computer-implemented steps of:
(a) creating a first directory entry for a file wherein the first directory entry holds a short filename for the file and the location of the file;
(b) creating a second directory entry for the file wherein the second directory entry holds at least one portion of a long filename having a fixed number of characters and a signature that identifies that the second directory entry holds a first portion of the long filename;
(c) storing the first directory entry and the second directory entry on the storage among the directory entries used by the directory service;
(d) accessing the second directory entry by the directory service to access the file; and
(e) creating and storing in the storage a sequence of at least one additional directory entry for holding a next sequential portion of the long filename.
Relevance
mapped Unix long filenames to DOS compatible filenames, compatible with Windows 95
mapped Unix long filenames to DOS compatible filenames, compatible with Windows 95
Claim Chart
Some
Long filename associated with short filename
In a data processing system having a processor running an operating system and a memory means with memory locations, wherein said memory means stores the operating system, a computer-readable medium holding computer-executable instructions for performing a method comprising the steps of:
(a) storing in a first of the memory locations of the memory means a first directory entry for a file wherein the first directory entry holds a short filename for the file, said short filename including at most a maximum number of characters that is permissible by an application program;
(b) storing in a second of the memory locations of the memory means that is adjacent to the first of the memory locations a second directory entry for the file wherein the second directory entry holds at least a first portion of a long filename for the file, said long filename including a greater number of characters than the maximum number of characters that is permissible by the application program;
(c) storing at least one additional directory entry in at least one other of the memory locations that is adjacent to the second of the memory locations of the memory means wherein the at least one additional directory entry holds a next portion of the long filename; and
(d) accessing one of the directory entries to locate the file.
Relevance
by definition
by definition
Claim Chart
All
Creating extra directory entries for long filenames
The method as recited in Claim 1 wherein the step of creating at least one additional directory entry for the long filename further comprises the step of creating a plurality of additional directory entries.
Relevance
Unknown. Space had to be allocated to hold the long filenames on disk. Specifically how that was implemented I am not sure.
Unknown. Space had to be allocated to hold the long filenames on disk. Specifically how that was implemented I am not sure.
Claim Chart
None
Signature identifies portion of long filename
The computer-readable medium of Claim 20 wherein a signature is stored in each of the second directory entry and the at least one additional directory entry, each signature uniquely identifying which portion of the long filename is stored in its respective directory entry.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Directory holds only a portion of long filename
In a data processing system having a processor running an operating system and a memory means having memory locations wherein the operating system is stored in the memory means, a method, comprising the steps of:
(a) storing in a first of the memory locations of the memory means a first directory entry for a file wherein the first directory entry holds a short filename for the file, said short filename including at most a maximum number of characters that is permissible by an application program;
(b) storing in a second of the memory locations of the memory means that is adjacent to the first of the memory locations a second directory entry for the file wherein the second directory entry holds at least a first portion of a long filename for the file, said long filename including a greater number of characters than the maximum number of characters that is permissible by the application program;
(c) storing at least one additional directory entry holding a next portion of the long filename in the memory means; and
(d) accessing one of the directory entries to locate the file.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Checksum in additional directory entries
The method as recited in Claim 7 wherein the step of storing at least one additional directory entry further comprises the step of storing a checksum of the short filename in the additional directory entry.
Relevance
unknown. Need detailed documentation from Sun.
unknown. Need detailed documentation from Sun.
Claim Chart
None
Short filename used by application program
The method of Claim 24 wherein the program that uses only short filenames is an application program.
Relevance
Any application running in the DOS emulator could use short filenames.
Any application running in the DOS emulator could use short filenames.
Claim Chart
All
Long filename longer than short filename
The computer-readable medium of Claim 12 wherein the long filename contains more characters than the short filename.
Relevance
by definition
by definition
Claim Chart
All
Multiple additional directoy entries
The computer-readable medium of Claim 12 wherein the step of creating at least one additional directory entry for the long filename further comprises the step of creating a plurality of additional directory entries.
Relevance
multiple nested directories were supported
multiple nested directories were supported
Claim Chart
All
