The easiest solution is to add
--nozero
to the command line.
This actually seems to solve my problem in the (slightly misspelled)
thread SD2480B and MAX232 segfault above.
Nicklas Björk
--
Open Source Business
I confirm that p15 solved also the issue about channel selection. !=)
thanks
2009/2/18 Paul Alfille paul.alfi...@gmail.com:
Very nice!
You can share the info as you've done here, or
1. create a diff patch
or
2, become an owfs developer and get CVS access to add your changes directly.
It
Humm, sorry for reporting so actively...
everything is fine when starting owhttpd directly on the physical interface.
However, when I work via owserver like this:
owserver --i2c=/dev/i2c-0:ALL -p 40666 --error_level 9 --foreground
owhttpd -s piccolo:40666 -p 81
I can see and control all
Hi,
The new settings ActivePullUp and PulsePresenceMask are always shown
as checked in interface/settings.
However, after placing some tracing, in SetConfiguration(), I confirm
that settings are modified as requested.
For overdrive, the problem is exactly the reverse:
the shown setting change as
@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
__ Information from ESET NOD32 Antivirus, version of virus signature
database 3865 (20090218) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__ Information from ESET
(20090218) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__ Information from ESET NOD32 Antivirus, version of virus
signature
database 3865 (20090218) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
On Wed, Feb 18, 2009 at 5:05 PM, Pascal Baerten pascal.baer...@gmail.comwrote:
Hi,
The new settings ActivePullUp and PulsePresenceMask are always shown
as checked in interface/settings.
However, after placing some tracing, in SetConfiguration(), I confirm
that settings are modified as
On Wed, Feb 18, 2009 at 5:51 PM, Pascal Baerten pascal.baer...@gmail.comwrote:
Humm, sorry for reporting so actively...
Please don't stop.
everything is fine when starting owhttpd directly on the physical
interface.
However, when I work via owserver like this:
owserver