<html>
<body>
I have added my how-I-was-able-to-do-it for installing GRASS 6.1 (but
*not* 6.0)<br>
<a href="http://jrshelby.com/grass/install-cd.htm" eudora="autourl">
http://jrshelby.com/grass/install-cd.htm</a><br>
using the WinGRASS cd, to my "WinGRASS for the GREEN"<br>
site at<br>
<a href="http://jrshelby.com/grass/index.htm" eudora="autourl">
http://jrshelby.com/grass/index.htm</a><br><br>
I found that, if when selecting packages to be included in the cd, if I
*de-selected* GRASS 6.1 and *selected* GRASS 6.0, the program would not
run, but would give an error message about a missing *6.1* .dll (I was
trying to install 6.0, not 6.1). I tried this twice; same results
each time.<br><br>
So, I did a full un-install, then re-installed using the same cd, but
this time went with the default GRASS 6.1 cvs, it installed without a
problem.<br><br>
It may be possible to install *both* 6.0 and 6.1 since 6.1 is a
"concurrent version", but that is a level of complexity I am
not yet ready for, so I did not attempt it.<br><br>
It *is* possible to install GRASS 6.0 using the methods described in
"How to install Cygwin and GRASS GIS using Huidae Cho
site"<br>
<a href="http://jrshelby.com/grass/install.htm" eudora="autourl">
http://jrshelby.com/grass/install.htm</a><br>
but for now, I am running 6.1cvs, and at the elementary level I am using
it, it will make little difference.<br><br>
FWIW, there are now 3 versions of the cross-referenced (Bash/GUI) GRASS
help file at<br>
<a href="http://jrshelby.com/grass/tutorial60/commands.htm" eudora="autourl">
http://jrshelby.com/grass/tutorial60/commands.htm</a><br>
These are:<br>
1. Bash order<br>
2. Display Mgr. menu order<br>
3. Alphabetical order, by function<br><br>
As voluminous as these files are, there are almost certainly some
errors. I'd appreciate them being pointed out to me so I can fix
them.<br><br>
I have no idea what the usefulness of such listings are, but creating
them served some usefulness to me in finding a way to "wrap my arms
around" the command structure of GRASS, which is somewhat unique to
me after 25 years of working with software. I find working with
GRASS akin to driving a "driver's ed" car with dual controls in
the front seat: manual shift on the left side and automatic transmission
on the right side. Not bad, not wrong, but decidedly
different.<br><br>
It would be possible to strip some code out and rename any of the 3 above
as full_index.html and place it in the appropriate cygwin subdir, and it
would come up whenever "Help" is clicked in the main GRASS
window, but I have not done so. If anyone is interested, I will
make such available.<br><br>
In making the above sorted listings of the help file, I linked them all
back to the Baylor website. Since GRASS insists on using
"<a href="http:///" eudora="autourl">http://</a>..." on all
screens except the main starting screen, it occurs to me that a
workaround might well be to link ALL help screens back to the Baylor site
rather than accessing the help files in the ../docs/html/
subdirectory.<br><br>
John Robertson<br><br>
<br><br>
<br><br>
</body>
</html>