Background of this document is a small 7KB GIF of a "White Leather Patch" that is tiled repeatedly by automatic action of the browser.

An HTML form is used to accept user's input of a client-side file spec. JavaScript is then invoked locally on the client machine to dynamically prepare a nicely formatted directory table. The JavaScript resides in a separate document and executes exclusively on the client side. Communication is achieved by temporarily storing in a Named Cookie on the client side, a Dictionary Object containing the appropriate Environment variable names and values. The Cookie is set-up to expire in 24 hours. The interesting possibility of this technique, is that once configured with a Cookie, the JavaScript program could be continued to be invoked until the Cookie expires, independently of the original Referring HTML form. Client side file I/O is performed thru use of the ActiveX FileSystemObject in the Microsoft Scripting Library. In phase II of the execution, you will likely be prompted to authorize the execution of the ActiveX Object. That is a part of the Microsoft COM Security Mechanisms and is also contingent on how permissions are configured in your browser. If you decline to allow the ActiveX Object to execute, you may still inspect the JavaScript source. Please note that Tripod dynamically inserts their own small JavaScript into all pages invoked from their server in order to effect the use of pop-up ads. You may blur the ads to the background out of sight by a small up and down scroll of the main window.