Greetings, I would like to install Koha on my current Windows XP machine for my small library. Will Koha 3 work on Windows? I am new to most of this, so the instructions are a bit confusing. I do have perl, Apache, Zebra and MySQL installed. I would love some step by step instructions of what I need to do next. Thanks! Kim LaMarre
On Mon, Mar 24, 2008 at 11:49 AM, Kim LaMarre <canplib@canaan.lib.me.us> wrote:
Greetings,
I would like to install Koha on my current Windows XP machine for my small library. Will Koha 3 work on Windows?
Koha 3 on Windows support is not complete at the present time. Considerable work has been invested into it, but a couple of key Perl modules have yet to be compiled. Hopefully this will come about in the not to distant future. In the meantime, you can grab a copy of 2.2.9 for Windows here: http://www.koha.rwjr.com/ Kind Regards, Chris -- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org
This may be more appropriate for the koha-win list, but since it came up here, I'll try asking: When working with the Windows version, what do I need to configure to make the Intranet interface available from other computers on the network? I installed Koha 2.2.9 for Windows on one computer, currently 172.25.126.157, and if I type the IP address into my browser on 172.25.127.187, I get the opac screen. If I type :8080 at the end of the address, I get the same thing. I looked through the archives and and the Koha on Windows instructions, but didn't find what I was looking for. It works just fine on the computer running Koha, so I know the software is working; (I hope) it's just the configuration that needs tweaking. Any suggestions? Thanks, Fred King phred@philobiblios.net Chris Nighswonger writes:
On Mon, Mar 24, 2008 at 11:49 AM, Kim LaMarre <canplib@canaan.lib.me.us> wrote:
Greetings,
I would like to install Koha on my current Windows XP machine for my small library. Will Koha 3 work on Windows?
Koha 3 on Windows support is not complete at the present time. Considerable work has been invested into it, but a couple of key Perl modules have yet to be compiled. Hopefully this will come about in the not to distant future.
In the meantime, you can grab a copy of 2.2.9 for Windows here: http://www.koha.rwjr.com/
Kind Regards, Chris
-- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Hi Fred, If you used the Windows install package, it uses the Windows hosts file on the machine where you install Koha to provide name resolution for the Intranet interface. To access the intranet interface from other workstations, you can either add a record to your DNS server, or modify the hosts file on those workstations. See my previous post at http://www.nabble.com/Direct-URL-to-Intranet-tf4252150.html#a12102548 for instructions on how to do this. Rob phred wrote:
When working with the Windows version, what do I need to configure to make the Intranet interface available from other computers on the network?
Thanks Rob, that worked like a charm. It turns out I actually had that information, but I didn't realize I had it until I read your explanation of it. *sigh* Another slope up in the learning curve. And sometimes I feel like a very slow pup. Fred King phred@philobiblios.net Rob Weir writes:
Hi Fred, If you used the Windows install package, it uses the Windows hosts file on the machine where you install Koha to provide name resolution for the Intranet interface. To access the intranet interface from other workstations, you can either add a record to your DNS server, or modify the hosts file on those workstations. See my previous post at http://www.nabble.com/Direct-URL-to-Intranet-tf4252150.html#a12102548 for instructions on how to do this.
Rob
phred wrote:
When working with the Windows version, what do I need to configure to make the Intranet interface available from other computers on the network?
participants (4)
-
Chris Nighswonger -
Kim LaMarre -
phred -
Rob Weir