On 9/29/07, Jim Kusznir <[EMAIL PROTECTED]> wrote:
>
> I tried it, and seem to have gotten the same results. Again, the
> debug just shows programming pulse = 0; it never = 1.
>
If there's an easy way to verify what version of owfs I'm running (to
> ensure its the one with your chnages), I'd like to do that to make
> sure.
Well, I made a new release 2.6p7 which should make determining the version
used easier.
You do need to close existing owfs-type applications before starting the new
verion -- the libow shared library stays in memory otherwise.
libow is used by owfs, owserver, owhttpd, owftp, owperl, owtcl, ... but not
the owshell or ownet programs.
Also, I'm assuming you write to memory in the same way: echo -n
> "whatever" > memory
> If I'm misunderstanding this as well, please let me know. It seems
> like somewhat of an awkward interface for a add-only burn.....
Well, it's a "file". The echo technique isn't very precise. You can right a
program that uses fancier commands (like C's write function).
owhttpd lets you change a single byte easily too, on screen in your browser.
All that said, looking through your debug file, I can see some problems in
the code.
Can you try the newest CVS version and report?
Paul Alfille
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
