(a) Common name space for long and short filenames
Microsoft Corp.This patent was asserted by Microsoft Corp. against TomTom.
Last updated: 2 months ago
Summary / Description
| Summary / Description | Article that identified the problem of different operating systems having different filename limitations. Proposed a mapping solution for this problem. |
Basic Information
| Type of Prior Art | Print Publication |
| Publication Title * | Applications, Technologies, Architectures, and Protocols for Computer Communication archive Proceed |
| Author | N. N. Y. Chu |
| ISBN | |
| Page Range | 3-8 |
| Medium | Journal article |
| Publication Date * | January 1, 1983 |
| URL | |
Notes / To Do
| Notes | |
Excerpt
The experiment required that the VAX and the Apollo be interconnected. Filename characteristics of the VAX and the Apollo were different. The VAX distinguished upper and lower cases in filenames. Each name contained up to 14 characters. Characters such as "\", "-" are allowed in composing a filename, but not "$".
The Apollo naming convention was quite different and often just the opposite. Upper and lower case letters were treated the same. Character "$" would be allowed, but "\" and "'" would not be allowed. Maximum 32 characters were allowed in a filename.
The presentation layer would perform text conversion for the two machines. In the LAN plan, only the filenames would need to be converted since the file content would have been processed into machine independent object code. An algorithm was designed to map VAX 11/780 filenames to Apollo filenames as shown in Table IV.
Relevance
Claims
Long file name associated with short file name
In a computer system having a processor running an operating system and a memory means storing the operating system, a method comprising the computer-implemented steps of:
(a) storing in 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 the operating system;
(b) storing in the memory means a second directory entry for a the file wherein the second directory entry holds a long filename for the file and wherein the second directory entry includes an attributes field which may be set to make the second directory entry invisible to the operating system and the step of storing the second directory entry further comprises the step of setting the attributes field so that the second directory entry is invisible to the operating system, said long filename including more than the maximum number of characters that is permissible by the operating system; and
(c) accessing the first directory entry with the operating system.
Relevance
Identified the problem of different operating systems having different filename limitations. Proposed a mapping solution for this problem.
Identified the problem of different operating systems having different filename limitations. Proposed a mapping solution for this problem.
Claim Chart
All


