Re: [greenstone-devel] Windows -compatible distribution that doesn't require playing withhosts file or using

From Katherine Don
DateTue, 05 Jul 2005 14:32:03 +1200
Subject Re: [greenstone-devel] Windows -compatible distribution that doesn't require playing withhosts file or using
In-Reply-To (1120524976-24330-67-camel-localhost-localdomain)
Hi Daniel

For the first problem, you can set the "browser" field in gsdlsite.cfg to 3.
For the second problem, we need to modify the local library server to
use "localhost" or "", instead of trying to
work out the computer's network address "intelligently".

There are now several people urgently requiring this modification, so
Michael will be looking at it tomorrow.

Katherine Don

Daniel Paul O'Donnell wrote:
> Hello,
> I've search the archives and googled this issue. I know it is
> relatively common, but am writing to this list in hopes that somebody
> knows an elegant solution.
> We are about to burn a Master CD for publication with a book that uses
> Greenstone to provide search functionality. The intended audience is
> medievalists with a computer, i.e. varying technical competence from 0.1
> to 10.
> We have two problems.
> 1) The first is with the use of IE as the default browser (the project
> is very standards based and IE doesn't work as well as other browsers;
> since we recommend against it in our system requirements, we don't want
> Greenstone to load it as the standard browser. Is there a way of setting
> up the install so that the local computer browser is the default choice?
> Since there is a "default" choice in the File menu that appears on the
> startup screen, it seems to me there must be a way of setting it so that
> option is checked by default. We just can't figure out how to do it.
> 2) The second issue has to do with problems with how Greenstone installs
> in Windows. On XP computers that are connected to networks and receive
> dynamic IP addresses (at the least), Greenstone builds the wrong
> address: computer_name.network_name instead of localhost. We've checked
> the proxies are off following the information in the FAQ
> (, and we can get the server running from or by editing /WINDOWS/drivers/etc/hosts. The issue is that we can't (necessarily) expect our final users to do this to their systems correctly. Most are going to expect the program to work out of the box.
> Does anybody know a more elegant solution to this issue? I realise it is
> quite common (e.g.
> )
> but it looks to me like it is going to force us to drop an otherwise
> quite useful adaptation of Greenstone. Does anybody have experience
> distributing a project with Greenstone to a similar range of users? What
> did you do about this problem? All solutions will be appreciated. We
> need to fix this or drop Greenstone this week.
> -d