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.]
#96Internetting between VAX and Apollo ring network
Applies to Claims 1
Last updated: 2 months ago
Summary / Description
Summary / DescriptionPaper that identified the problem of different operating systems having different filename limitations. Proposed a mapping solution for this problem.
 
Basic Information
Type of Prior ArtPrint Publication
 
Publication Title *Applications, Technologies, Architectures, and Protocols for Computer Communication archive Proceedi
 
AuthorN. N. Y. Chu
 
ISBN
 
Page Range3-8
 
MediumOther printed publication
 
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 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
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