File: hints.html

package info (click to toggle)
linklint 2.3.5-5
  • links: PTS
  • area: main
  • in suites: jessie, jessie-kfreebsd, lenny, squeeze, wheezy
  • size: 660 kB
  • ctags: 228
  • sloc: perl: 2,561; makefile: 37
file content (807 lines) | stat: -rw-r--r-- 20,956 bytes parent folder | download | duplicates (7)
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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
<html><head><title>

Linklint Documentation - hints

</title></head><body text="#000000" link="#6666aa" vlink="#6688aa" alink="#6688aa" bgcolor="#ffffff">  
<font face="helvetica,sans serif,ariel">

<font size=5>
<a name=top>
Linklint Documentation - hints
</a>
</font>

<table cellpadding=0 cellspacing=2 border=0 width="90%">
<tr><td bgcolor="#8888dd"><img src=dot.gif alt="" width=1 height=1></td></tr>
</table>


<font size=3>
Version 2.3.5 August 13, 2001
</font>


<p>

<table cellpadding=0 cellspacing=1 border=0><tr><td align=right>

<table cellpadding=0 cellspacing=0 border=0 bgcolor="#8888dd">
<tr><td>
<table bgcolor="ddddff" cellpadding=2 cellspacing=1 border=0>


</td></tr>
</table></td></tr></table>

</td><td>
<table cellpadding=0 cellspacing=0 border=0 bgcolor="#8888dd">
<tr><td>
<table bgcolor="ddddff" cellpadding=2 cellspacing=1 border=0>
</table></td></tr></table>

</td></tr>

<tr><td align=right>

<table cellpadding=0 cellspacing=0 border=0 bgcolor="#8888dd">
<tr><td>
<table bgcolor="ddddff" cellpadding=2 cellspacing=1 border=0>
<tr>
<td bgcolor="white" align=right>
<font face="helvetica,sans serif,ariel"><font color="#8888dd"><b>
documentation
</b></font></font>
</td></tr>
</table></td></tr></table>
</td><td>
<table cellpadding=0 cellspacing=0 border=0 bgcolor="#8888dd">
<tr><td>
<table bgcolor="ddddff" cellpadding=2 cellspacing=1 border=0>
<tr>

<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="index.html">
Introduction
</a>
</font></td>
<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="new.html">
What's&nbsp;New
</a>
</font></td>
<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="inputs.html">
Inputs
</a>
</font></td>
<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="outputs.html">
Outputs
</a>
</font></td>

<td align=center bgcolor="white">
<font face="helvetica,sans serif,ariel"><font color="#dd6666">
Hints
</font>

</font></td>
  
<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="howitworks.html">
How it works
</a>
</font></td>
<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="bugs.html">
Bugs
</a>
</font></td>
<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="doc_index.html">
Index
</a>
</font></td>

</tr>
</table></td></tr></table>

</td></tr>


<tr><td align=right>
<table cellpadding=0 cellspacing=0 border=0 bgcolor="#8888dd">
<tr><td>
<table bgcolor="ddddff" cellpadding=2 cellspacing=1 border=0>
<tr><td bgcolor="white" align=right>
  <font face="helvetica,sans serif,ariel">
  <font color="#8888dd">
  <b>
    on this page
  </b>
  </font>
  </font>
</td>
</tr>
</table></td></tr></table>
</td><td>
<table cellpadding=0 cellspacing=0 border=0 bgcolor="#8888dd">
<tr><td>
<table bgcolor="ddddff" cellpadding=2 cellspacing=1 border=0>
<tr><td bgcolor="#f8f8ff">
<font face="helvetica,sans serif,ariel">

<a href="#command">
Cmd files
</a>
    &middot;
<a href="#memory">
Memory
</a>
   &middot;
<a href="#password">
Passwords
</a>
   &middot;
<a href="#imagemap">
Image&nbsp;maps
</a>
   &middot;
<a href="#errors">
Errors
</a>
     &middot;
<a href="#redirect">
Redirection
</a>

</font>
</td></tr></table>
</td></tr></table>
</td></tr></table>


<blockquote>

This page contains detailed hints for configuring Linklint 
for web sites that needs to make use of most of the features of
Linklint.  Some sections here may not be applicable to your site.

These hints are intended as suggestions to help you quickly get
started checking links.  Your mileage my vary.

<ul>

<li> Use the <font color="#cc0000"><tt><b>/@</b></tt></font> 
     <a href="inputs.html#linkset_def">linkset</a> to check your entire site.

<li> Use <font color="#cc0000"><tt><b>-limit NNN</b></tt></font> to check more than 500 HTML files.

<li> Always use the <font color="#cc0000"><tt><b>-doc dir</b></tt></font> option.

<li> Consider using the <font color="#cc0000"><tt><b>-docbase</b></tt></font> option 
     if you are doing a local site check.

<li> Read all the documentation.


<!--- <li> For thoroughness use the <font color="#cc0000"><tt><b>-http</b></tt></font> flag to check your pages 
     through your http server.  This will automatically take care of pages
     generated by CGI and any server redirections that may occur.

<li> For speed don't use the <i>-http</i> flag. Linklint will get
     pages directly from your file system which will be much faster.

<li> Don't use the <btt>-net</btt> flag.  Instead, run Linklint a second
     time with the <btt>@@</btt> option.

-->

</ul>

</font>
</blockquote>
<table bgcolor="#8888dd" width="90%" cellpadding=3 cellspacing=2 border=0>
<tr>
<td>
<font face="helvetica,sans serif,ariel">
<font size=3 color="#ffffff"><b>
<a name="command">
Create a Command File
</a>
</b></font>
</font>
</td></tr></table>

<font face="helvetica,sans serif,ariel"><font size=2>

<a href="#top">&nbsp;(top)</a>
<a href="doc_index.html#command_index">&nbsp;(command index)</a>
<a href="doc_index.html#topic_index">&nbsp;(topic index)</a>

</font></font>

<blockquote>
<font face="helvetica,sans serif,ariel">

Before checking your site, take the time to put some information about
your site in a command file.  This will avoid a lot of retyping (and
possible typos) later on.  It often makes sense to name the command
file after your host name.  The command file should look like:
<font color="#006600"><pre>
# general command file for hostname

-host www.hostname.com
-root /absolute/path/to/your/htmlrootdirectory
-doc linkdoc
-http
-limit 1000</pre></font>

Resist the temptation to include any <i>linksets</i> in this command
file.  The reason will become clear when you start <b><a href="#errors">tracking down broken links</a></b>.  If you need to use a
large list of linksets, another option is to include these in their
own separate command file.

<p>

You can check your home page with <tt><b>linklint @hostname</b></tt>.
You can check your entire site with <tt><b>linklint @hostname /@</b></tt>.

<p>

Often the easiest way to understand some of the many features that
Linklint has to offer is to try them out.  Linklint is very fast and
it is easy to try play around with it on just a few pages.  Start with
a simple command file like the example above and then add features and
options as needed.  In the spirit of Perl, Linklint has been designed
to "<i>do the right thing</i>".


</font>
</blockquote>
<table bgcolor="#8888dd" width="90%" cellpadding=3 cellspacing=2 border=0>
<tr>
<td>
<font face="helvetica,sans serif,ariel">
<font size=3 color="#ffffff"><b>
<a name="memory">
Resolving Memory Problems
</a>
</b></font>
</font>
</td></tr></table>

<font face="helvetica,sans serif,ariel"><font size=2>

<a href="#top">&nbsp;(top)</a>
<a href="doc_index.html#command_index">&nbsp;(command index)</a>
<a href="doc_index.html#topic_index">&nbsp;(topic index)</a>

</font></font>

<blockquote>
<font face="helvetica,sans serif,ariel">


Here are some things you can do to reduce the amount
of memory that Linklint uses.

<p>
<table bgcolor="#88aacc" width="85%" cellpadding=3 cellspacing=0 border=0>
<tr><td>
<font face="helvetica,sans serif,ariel">
<font size=3 color="#ffffff"><b>
<a name="sections">
Check Your Site in Sections
</a>
</b></font>
</font></td></tr></table>
<p>

If you have a very large site (thousands of pages), it might make
sense to check your site up into several sections and check each
section separately.  One way to do this is to check all the files
in the root directory and then check files in each subdirectory.

<p>
<font color="#cc0000"><tt><b>Note:</b></tt></font> Linklint is designed so that all links between
the sections will be checked correcty.  Currently, the output files
for each section will not be merged.

<p>

Create a command file named <i>root</i> for checking the root directory:
<font color="#006600"><pre>
# root directory command file
@hostname
-doc rootdoc
/#</pre></font>


For each subdirectory (or group of subdirectories) create a command file
name <i>subdir</i>:
<font color="#006600"><pre>
# command file for subdir
@hostname
-doc subdirdoc
/subdir/@</pre></font>

Now you can check just your root directory with <tt><b>linklint
@root</b></tt> and each subdirectory with <tt><b>linklint @subdir</b></tt>
and the results will be kept in separate output directories.

<!---- You are now ready to start checking your site.  Run Linklint with the
appropriate command file.  Examples:

<table cellspacing=0 cellpadding=0>
<tr><td><font face="helvetica,sans serif,ariel"><font color="#cc0000"><tt><b>
linklint @hostname /@
</b></tt></font></face></td><td><font face="helvetica,sans serif,ariel">check the entire site using command file <i>hostname.</i>
</face></td></tr>

<tr><td><font face="helvetica,sans serif,ariel"><font color="#cc0000"><tt><b>
linklint @root 
</b></tt></font></face></td><td><font face="helvetica,sans serif,ariel">check the root directory using command file <i>root.</i>
</face></td></tr>

<tr><td><font face="helvetica,sans serif,ariel"><font color="#cc0000"><tt><b>
linklint @subdir
</b></tt></font></face></td><td><font face="helvetica,sans serif,ariel">check subdir and below using command file <i>subdir.</i>
</face></td></tr>

</table>


Most likely there will be some warnings and errors.  There might even
be some hints in the summary.  Review the results that were created
in the <i>-doc</i> directory.

---->

<p>
<table bgcolor="#88aacc" width="85%" cellpadding=3 cellspacing=0 border=0>
<tr><td>
<font face="helvetica,sans serif,ariel">
<font size=3 color="#ffffff"><b>
<a name="run_twice">
Run Linklint Twice
</a>
</b></font>
</font></td></tr></table>
<p>

If you have a large site, don't use the  <i>-net</i> when you are
checking your site.  Instead, after you check your site (without the
<i>-net</i> command) run Linklint again as:

<p>
<b><font color="#dd666666">linklint -doc doc_dir @@</font></b>
</p>

You will end up with the same results as with a single pass of Linklint
but the memory requirements will have been eased.

<p>
<table bgcolor="#88aacc" width="85%" cellpadding=3 cellspacing=0 border=0>
<tr><td>
<font face="helvetica,sans serif,ariel">
<font size=3 color="#ffffff"><b>
<a name="no_anchor">
Use the -no_anchor option
</a>
</b></font>
</font></td></tr></table>
<p>

Since there are often many named anchors on a single page, the list of
named anchors that Linklint generates and checks can be larger than
the list of HTML pages.  You can use the <font color="#cc0000"><tt><b>-no_anchors</b></tt></font>
option to tell Linklint to ignore named anchors which should reduce
memory consumption.


</font>
</blockquote>
<table bgcolor="#8888dd" width="90%" cellpadding=3 cellspacing=2 border=0>
<tr>
<td>
<font face="helvetica,sans serif,ariel">
<font size=3 color="#ffffff"><b>
<a name="password">
Add Passwords
</a>
</b></font>
</font>
</td></tr></table>

<font face="helvetica,sans serif,ariel"><font size=2>

<a href="#top">&nbsp;(top)</a>
<a href="doc_index.html#command_index">&nbsp;(command index)</a>
<a href="doc_index.html#topic_index">&nbsp;(topic index)</a>

</font></font>

<blockquote>
<font face="helvetica,sans serif,ariel">

If you get warning messages that say <i>need password for
"realm"</i>, you will have to provide Linklint with a username and
password for each password protected realm.  Add these lines to your
<i>hostname</i> file:

<font color="#006600"><pre>
-password "realm1" username1:password1
-password "realm2" username2:password2</pre></font>

The realms are double quoted in the warning messages.  You will have
to use double quotes in the command file if the realm contains any
space characters.  You can also use the realm "DEFAULT" to
provide a default username and password. The default will be tried
only if a password for the specific realm was not given.  Once you
have made these changes to your command file, check the site again to
make sure that you entered all the information correctly.  You will
get warning messages for invalid username/password combinations.

<p>

<font color="#cc0000"><b>Note:</b></font> The HTTP protocol uses a named <i>realm</i> to
identify a set of pages that share a common set of username/password
combinations.  This system was created so that visitors only need to
be prompted for their username and password once (per session) in
order to browse any number of pages in a given realm.  Realms are
often used to protect all the files under a particular subdirectory,
but they can be used in other configurations.

</font>
</blockquote>
<table bgcolor="#8888dd" width="90%" cellpadding=3 cellspacing=2 border=0>
<tr>
<td>
<font face="helvetica,sans serif,ariel">
<font size=3 color="#ffffff"><b>
<a name="imagemap">
Add Server-Side Image Maps
</a>
</b></font>
</font>
</td></tr></table>

<font face="helvetica,sans serif,ariel"><font size=2>

<a href="#top">&nbsp;(top)</a>
<a href="doc_index.html#command_index">&nbsp;(command index)</a>
<a href="doc_index.html#topic_index">&nbsp;(topic index)</a>

</font></font>

<blockquote>
<font face="helvetica,sans serif,ariel">

If your site makes use of server-side images maps, you may have to
add a <i>-map</i> option to your command file so Linklint knows how to
find your <b>.map</b> files.  See <b><a href="howitworks.html#imagemap">
Server-Side Image Maps</a></b> for a detailed explanation.  You may have
to add one of the following lines to your <i>hostname</i> file:

<font color="#006600"><pre>
-map /cgi-bin/imagemap
-map /cgi-bin/imagemap.exe
-map /cgi-bin/htimage</pre></font>

You will also need to have the <i>-root</i> directory specified so Linklint
knows where to look for map  files locally on your machine.

</font>
</blockquote>
<table bgcolor="#8888dd" width="90%" cellpadding=3 cellspacing=2 border=0>
<tr>
<td>
<font face="helvetica,sans serif,ariel">
<font size=3 color="#ffffff"><b>
<a name="errors">
Tracking Down Errors
</a>
</b></font>
</font>
</td></tr></table>

<font face="helvetica,sans serif,ariel"><font size=2>

<a href="#top">&nbsp;(top)</a>
<a href="doc_index.html#command_index">&nbsp;(command index)</a>
<a href="doc_index.html#topic_index">&nbsp;(topic index)</a>

</font></font>

<blockquote>
<font face="helvetica,sans serif,ariel">

Sometimes the error messages generated by Linklint do not provide
sufficient information for figuring out why an error was reported.
In these cases it can be useful to look at the HTML tags that caused
the errors.  One way to see these tags is to use the <i>-db3</i> flag.
This flag causes all HTML tags that contain links to be printed out
followed by the fully expanded links.

<p>

Here is one strategy for tracking down errors:
<ol>

<li>Look in the <i>errorF.txt</i> or <i>errorX.txt</i> file to find
the file that caused the error.  Let's call its full (URL) path: /some/file.html

<li>Run <font color="#cc0000"><tt><b>linklint @hostname /some/file.html -db3 -doc
dbdoc</b></tt></font><br>

This will cause all the tags containing links in <i>/some/file.html</i>
to be printed out in <i>dbdoc/log.txt.</i>

<li>Examine the <i>dbdoc/log.txt</i> file to see the HTML tags
found by Linklint and the links that were extracted from these tags.

</ol>

If you use this technique frequently, you can avoid repeated typing
by making a <i>debug</i> command file:
<font color="#006600"><pre>
# debug command file
@hostname
-db3
-doc dbdoc
</pre></font>

You can use this file to debug an HTML page with the command:<br>
<tt><b>linklint @debug /some/file.html</b></tt>.

</font>
</blockquote>
<table bgcolor="#8888dd" width="90%" cellpadding=3 cellspacing=2 border=0>
<tr>
<td>
<font face="helvetica,sans serif,ariel">
<font size=3 color="#ffffff"><b>
<a name="redirect">
Server Redirection
</a>
</b></font>
</font>
</td></tr></table>

<font face="helvetica,sans serif,ariel"><font size=2>

<a href="#top">&nbsp;(top)</a>
<a href="doc_index.html#command_index">&nbsp;(command index)</a>
<a href="doc_index.html#topic_index">&nbsp;(topic index)</a>

</font></font>

<blockquote>
<font face="helvetica,sans serif,ariel">

One of the worst causes of confusion in debugging broken links is
<i>server redirection.</i> Some http servers are programmed to
deliver a different page than the one a visitor asks to see.  

<p>

The most benign form of redirection is when the server program sends
back a <i>moved</i> status code (301 or 302), telling the browser
that the page requested has moved, along with a new url. Linklint
follows these links and reports all moved urls in the file
<i>mapped.txt.</i>

<p>

Sometimes a server is programmed to serve up the contents of a page
that is different from the page requested without giving any hints
to the browser (or to Linklint) that a switch has been made. Take a
simple example where <i>fileA.html</i> is mapped to
<i>fileB.html.</i> 

Linklint will tell you <i>fileA.html</i> is missing whenever
<i>fileB.html</i> is missing even if <i>fileA.html</i> exists!

<p>

Since the server is not providing any clues that this switch
has been made, there is nothing Linklint can do to alleviate the
situation.  I can only suggest that you minimize your use of this
type of server redirection and familiarize yourself with which links
on your site have been mapped this way.


</blockquote>

<table cellpadding=0 cellspacing=2 border=0 width="90%">
<tr><td bgcolor="#8888dd"><img src=dot.gif width=1 height=1 alt=""></td></tr>
</table>

<p>

<table cellpadding=0 cellspacing=1 border=0><tr><td align=right>

<table cellpadding=0 cellspacing=0 border=0 bgcolor="#8888dd">
<tr><td>
<table bgcolor="ddddff" cellpadding=2 cellspacing=1 border=0>


</td></tr>
</table></td></tr></table>

</td><td>
<table cellpadding=0 cellspacing=0 border=0 bgcolor="#8888dd">
<tr><td>
<table bgcolor="ddddff" cellpadding=2 cellspacing=1 border=0>
</table></td></tr></table>

</td></tr>

<tr><td align=right>

<table cellpadding=0 cellspacing=0 border=0 bgcolor="#8888dd">
<tr><td>
<table bgcolor="ddddff" cellpadding=2 cellspacing=1 border=0>
<tr>
<td bgcolor="white" align=right>
<font face="helvetica,sans serif,ariel"><font color="#8888dd"><b>
documentation
</b></font></font>
</td></tr>
</table></td></tr></table>
</td><td>
<table cellpadding=0 cellspacing=0 border=0 bgcolor="#8888dd">
<tr><td>
<table bgcolor="ddddff" cellpadding=2 cellspacing=1 border=0>
<tr>

<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="index.html">
Introduction
</a>
</font></td>
<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="new.html">
What's&nbsp;New
</a>
</font></td>
<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="inputs.html">
Inputs
</a>
</font></td>
<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="outputs.html">
Outputs
</a>
</font></td>

<td align=center bgcolor="white">
<font face="helvetica,sans serif,ariel"><font color="#dd6666">
Hints
</font>

</font></td>
  
<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="howitworks.html">
How it works
</a>
</font></td>
<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="bugs.html">
Bugs
</a>
</font></td>
<td align=center bgcolor="#ddddff">
<font face="helvetica,sans serif,ariel">
<a href="doc_index.html">
Index
</a>
</font></td>

</tr>
</table></td></tr></table>

</td></tr>


<tr><td align=right>
<table cellpadding=0 cellspacing=0 border=0 bgcolor="#8888dd">
<tr><td>
<table bgcolor="ddddff" cellpadding=2 cellspacing=1 border=0>
<tr><td bgcolor="white" align=right>
  <font face="helvetica,sans serif,ariel">
  <font color="#8888dd">
  <b>
    on this page
  </b>
  </font>
  </font>
</td>
</tr>
</table></td></tr></table>
</td><td>
<table cellpadding=0 cellspacing=0 border=0 bgcolor="#8888dd">
<tr><td>
<table bgcolor="ddddff" cellpadding=2 cellspacing=1 border=0>
<tr><td bgcolor="#f8f8ff">
<font face="helvetica,sans serif,ariel">

<a href="#command">
Cmd files
</a>
    &middot;
<a href="#memory">
Memory
</a>
   &middot;
<a href="#password">
Passwords
</a>
   &middot;
<a href="#imagemap">
Image&nbsp;maps
</a>
   &middot;
<a href="#errors">
Errors
</a>
     &middot;
<a href="#redirect">
Redirection
</a>

</font>
</td></tr></table>
</td></tr></table>
</td></tr></table>

<p>

<table width="90%" cellpadding=0 border=0>
<tr><td colspan=3 bgcolor="#8888dd"><img src=dot.gif width=1 height=1 alt=""></td></tr>
<tr>
<td>
<a href="http://www.linklint.org">
<img src=linklint.gif alt="Checked by Linklint" border=0 WIDTH="74" HEIGHT="29">
</a>
</td>
<td></td>
<td align=right>

<font face="helvetica,sans serif,ariel"><font size=2>
&copy; Copyright 1997 - 2001

<a href=mailto:jbowlin@linklint.org>
James B. Bowlin
</a>

</font></font>

</td>
</tr>

</table>




<!-- HTML pre-processed by htp 1.11 RELEASE -->

</body>
</html>