-------------------------------------------------------------------------------------------- InContext WebAnalyzer Version 1.1 README FILE Installer Notes --------------- -If you installed Beta Version 2.1, you will need to remove the registration database entries by hand before installing this version. Known Problems -------------- -InContext WebAnalyzer will only process files on the server specified in the URL. It does not automatically check aliased or distributed servers - each must be opened as a separate project. For example, the PC Magazine web address http://www.pcmag.com is actually an alias to the web address http://www.zdnet.com/pcmag/. If you open the first address in your browser, the second address will be opened and shown in the URL field of the browser. The first address is an alias to the second. If you cannot analyze a site, open it in the browser to check if the address is an alias. To analyze an aliased site, specify the full address (in the above example, http://www.zdnet.com/pcmag/) in the URL field of the WebAnalyzer. -The From Browser option only works if you have a project already open in the WebAnalyzer, and if your browser is running. -Graphics files with the .JPEG extension will appear as '?' icons. Graphics files with the .JPG extension will appear correctly as image icons. -The Edit URL command is not yet fully supported by some HTML editors. The editor will launch upon the command, but the specified node may not be loaded into the editor. There are two options for the command line Arguments for the editor, specified in the Tools/Customize/Editor dialog box. $URL is documented; $LOCALFILE is not. $URL passes the full URL of the selected node to the editor, $LOCALFILE passes the complete file pathname -- for any local files -- to the editor. Most editors will only support the use of local pathnames, therefore we recommend that you use $LOCALFILE in the Editor Arguments field, not $URL. -When loading a project file, a blank line appears after the first item in the List View. This is harmless. -Sorting in the File List during processing can generate unexpected results. Things may appear out of order since new nodes are being inserted while the sort is happening. You should therefore only sort files in the File List after processing has completed, or while processing is suspended. -Selecting 'File/From Browser' may cause a fault if the path of the URL is too large. -Selecting 'Edit' for something other than an HTM (HTML) document may hang InContext Spider version 1.1, if you have InContext Spider version 1.1 configured as your editor. Improving Performance --------------------- -If you are experiencing memory problems while working with WebAnalyzer, you can save memory by turning off the options to download pictures, audio and video. To do this, open the Customize dialog box in the Tools menu, and select the Project Properties tab. Uncheck any of the "Get Data for" options. With the "pictures" option turned off, you will not be able to view Thumbnails of the images. In addition, if you make a local copy of the site, the files for the unchecked options will not be copied over. We recommend that by default you turn off the "Get Data for" option for audio and video, but leave it turned on for pictures. Manual Errata ------------- The information in the manual about the contents of the Report is incorrect. Consult the help file for a correct list. Advanced Initialization File Options ------------------------------------ ProxyServer: This field specifies a proxy server to use for web server requests. If you access the Internet through a firewall or proxy server, it may be necessary to set this field. If in doubt as to what these settings should be, look at the configuration of your web browser. If, under the "Network Configuration", you see a "proxy HTTP host" configured, use those same settings for this field. The format of the field is host:port (e.g., sandblast.widget.com:8080). If you do not access the Internet through a firewall or proxy server, do *not* set this field, otherwise normal net access will be prevented. UserAgent: This field specifies what WebAnalyzer identifies itself as to remote Web servers. The default is to masquerade as Mosaic 1.1. Some web servers use this information to determine what pages to send to browsers. If you wish to use WebAnalyzer to retrieve pages intended for a different browser (such as Internet Explorer), set this field to the User Agent you wish to masquerade as. Here are the strings used by some popular browsers at the time of this writing: Netscape 1.22 Mozilla/1.22 (Windows; I; 32bit) Netscape 2.0 Mozilla/2.0 (Win95; I) MS Internet Explorer Mozilla/1.22 (compatible; MSIE 2.0; Windows 95) Lynx Lynx/2.3.7 BETA libwww/unknown To set either of these options, simply edit the lines in the analyzer.ini file. For example, ProxyServer=sandblast.widget.com:8080 UserAgent=Mozilla/1.22 (compatible; MSIE 2.0; Windows 95) -----------------------------------------------------------------------