The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: xPLHal V1.5 released


  • Subject: RE: xPLHal V1.5 released
  • From: "Michael Avanessian" <mkanet@xxxxxxxxx>
  • Date: Sun, 20 Nov 2005 13:06:04 -0800

Thank John!  I currently have xPLHalSetup.zip (ver 1.45) and xplcm12.zip
installed.  I'm not sure if the upgrade to Hal 1.5 will break my current
setup or not.  Please advise on the correct upgrade procedure to avoid
problems with a Hal being built-in or not.

If I remember correctly, I had to make a change a while back somewhere in
my
setup so that I wouldn't get Event Viewer error messages complaining about
a
Hub already existing (or something to that effect).  So, please consider
this issue as well in the upgrade procedure.

Thank in advance!
-Michael

-----Original Message-----
From: ukha_xpl@xxxxxxx [mailto:ukha_xpl@xxxxxxx] On Behalf
Of John B
Sent: Sunday, November 20, 2005 11:54 AM
To: ukha_xpl@xxxxxxx
Subject: [ukha_xpl] xPLHal V1.5 released

Hi all,

Version 1.5 of the xPLHal server is now available for download at:
http://www.xplhal.org/downloads/xplhal.zip

The most important change in this build is that there is no longer a
built-in hub, so you must be running a stand-alone xPL hub.

To upgrade, stop your xPLHal service, then copy the files xpllib.dll and
xplhal.exe from the downloaded ZIP file over the top of your current
versions, then restart the xPLHal service.

Regards,

John



xPL Links: http://www.xplproject.org.uk http://www.xplhal.com
http://www.xpl.myby.co.uk
To Post a Message: ukha_xpl@xxxxxxx
To Subscribe:  ukha_xpl-subscribe@xxxxxxx
To Unsubscribe:  ukha_xpl-unsubscribe@xxxxxxx

xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.