Member Login

Forgot Your Password?

      1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30

HP Invent

Level Double-A conformance icon, W3C-WAI Web Content Accessibility Guidelines 1.0

Software Library

Alphabetical Index

This index was generated automatically at 23-JUL-2004 15:24:27.77

0 1 2 3 4 5 8 9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

About This Index

This is an automatically generated index, in an attempt to add some navigational aids to the Encompass FTP Library.

It's definitely not perfect!

Is there any new content?

No, this is the same old FTP Library that's been around since the DECUS days. These web pages are only an attempt to make it more usable.

How do I use the index?

If you're looking for a submission by name (e.g. TREK), click on the appropriate letter and see if you find it there. If you have the old DECUS Library number, look on the V page.

How is the index organized?

Ultimately, it all comes down to README files.

  • Each README file that appears in the FTP library (exceptions noted below) was embedded within an HTML file. Each of these HTML files includes a link to the FTP directory where the README was found.
  • The parent directory name becomes the heading under which the README is referenced on an index page. For example, if there's a lib/this/that/aaareadme.txt, that file will be referenced under the heading THAT. If there are also a lib/this/readme.txt and a lib/readme.1st, those files will also appear under their own headings (THIS and LIB, respectively).
  • Because of the number of README files, the index has been split into a main index (which you're looking at now) and a series of sub-indexes, one per initial character for the headings.

Which README files were included?

The entire FTP directory tree was scanned for *readme*.*; /exclude=(*.exe, *.dir, *.tem, *.tmp, *.rn%, *.tex, *.aux, *.q, *.dvi). For those who don't speak DCL: That's all files where README appears in the name, except for files of selected types; the excluded file types are for those not ordinarily intended to be human-readable. Of those README files, a few were omitted when it came time to generate the HTML file names (the files that would contain the README file). If the generated name (which is based on the full path name) ran longer than 39 characters, the README file was omitted from consideration. The hope is that if a file was skipped because of the long path name, there'd at least be a README file earlier in the path that will cover the need.

What about directories without a README file?

These web pages won't lead you there directly. The hope is that there's a README file somewhere in the file's directory path that will get you there eventually.