I just posted beta4 to
http://www.tux.org/~peterw/slim/BottleRocket/
It includes your Win32 approach to invoking BR.EXE, and some code from
Greg Brown for Insteon support (via Smarthome Device Manager software,
http://www.insteon.net/sdk/files/dm/docs/). Please try it if you have a
chance and
I hsould have mentioned, system returns with 2304 (I assume errno 9 *
256).
I tried messing around with standard FDs a bit, no joy.
I tried using Open3() instead of system(), no joy.
I have changed the code to use Win32::Process::Create, and this seems
to work.
I've attached the changed
This is fantastic news -- thank you!
I'll try to roll out a new beta in the next few days that uses your
Win32::Process::Create approach for Windows users. I'd love it if you
could try the next beta before an official release.
Again, many thanks for the fix and the education!
Peter
--
Yes, I tried stopping and starting the service, and changing the service
so that it runs as me. I don't think control ever makes it to br.exe,
suggesting that system() is failing. I have gleaned from some oblique
postings that this may be because Windows services run with no stdin.
I'm
nadams;226999 Wrote:
Running on Windows XP, beta2 of BottleRocket, SlimServer 6.5.4 I got the
BottleRocket plugin to work, but only when I run perl slimserver.pl
from a Windows console.
If I start it from the server using SlimTray.exe, then the call that
BottleRocket.pm makes to
Running on Windows XP, beta2 of BottleRocket, SlimServer 6.5.4 I got the
BottleRocket plugin to work, but only when I run perl slimserver.pl
from a Windows console.
If I start it from the server using SlimTray.exe, then the call that
BottleRocket.pm makes to system(...br.exe,...) fails with
gaffer;207255 Wrote:
Good news, I appear to be in business.
...
Ian, that's great to hear. Please let me know if those open3() lines
make a difference -- system() seems a much cleaner approach, especially
if open3() doesn't solve the pop-up problem (and I'm glad to hear that's
not a
Hi Peter -
Good news, I appear to be in business. The plugin now appears to be
working for me. Unfortunately, my scientific method has been a bit
dodgey - the main change I've made was the addition of the four lines
of code you proposed below, but I've also shutdown a few other programs
that
Hi Peter -
I tried playing with this a little more, and found the following:
- As you quite rightly point out, BR.exe expects /dev/ttyS0 - I used
BR.exe manually and got to work with the command structure you propose
- no problems. More to the point, using COM1 as an arguement
definitely
The pop-up sounds terribly annoying (and somewhat encouraging -- at
least BR.EXE is being executed).
I don't know if IPC::Open3 is available in Slimserver (IPC::Open2 is),
but it seems that changing system(@cmdArgs); around line 520 to
something like
Code:
Long time reader, first time writer.
I was thrilled to stumble across the Bottlerocket plugin today, but
have had some problems getting it running. I've got BR.exe running, no
problem - I've been able to turn on and off devices no problem from the
command line. I've installed the plugin and
gaffer;206739 Wrote:
I was thrilled to stumble across the Bottlerocket plugin today, but
have had some problems getting it running. I've got BR.exe running, no
problem
...
In any case, turning either my SB2 or softsqueeze on or off fails to
turn the associated amp on or off.
...
peterw;206846 Wrote:
If you find, as I thought I did, that BR.EXE wants serial port names
like /dev/ttyS0 instead of COM1 for the -x argument, then I'd
suspect a permissions problem -- that the SlimServer process is running
as a user account that doesn't have permissions to the serial
13 matches
Mail list logo
