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: Stand-alone hub - Testers Needed



I'll test it for you Mal - I have W2K3 server, NT4SP6A, XPSP2 and WIN98
to test on :)

Ian.

-----Original Message-----
From: ukha_xpl@xxxxxxx [mailto:ukha_xpl@xxxxxxx] On
Behalf Of Mal Lansell
Sent: 17 September 2005 19:36
To: ukha_xpl@xxxxxxx
Subject: [ukha_xpl] Stand-alone hub - Testers Needed

Hi Guys,

I've written a new stand-alone xPL hub application in C++ (so that it
doesn't require the .NET framework) and I need some help testing it.
I've tried it on XP and 2000, and it's appears to be working fine.
However, my setup is not as complex as some peoples' and the hub could
do with a proper thrashing before it becomes "official".

I'd be especially interested in seeing what happens on Win95, 98 and ME,
and also if any memory leaks become apparent (looking at the memory
usage in the Task Manager is probably the best way to do this).

This hub can run either as a service or a console application.  On
95/98/ME, the installer creates a shortcut in the users startup folder,
and the hub should run as a minimised console app.
On NT/2000/XP, it is installed as a service, and will start straight
away.

Make sure disable any other hubs (don't forget the one in xPLHal!)
before installing this stand-alone version!!!

I've also updated the W800 service to be hubbless.  The SDK will be
updated once I'm sure both the new hub and new W800 service are behaving
properly.

The applications can be downloaded via the links below:

Hub:  www.xplmonkey.com/downloads/xplhub.msi
W800: www.xplmonkey.com/downloads/xplw800.msi

Thanks

Mal




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.