qknight

fixPath is a tool to modify the path to a certain DLLs (Dynamic Shared Objects) for Microsoft Windows Executables by rewriting parts of the executable’s PE header, when the .fixPath section is present and indicates support for such rewrite, but without having to realign the PE headers. In concept, it is similar to patchelf but instead of changing search paths, fixPath hard-codes each DLL to a particular filepath.

see fixPath project page:

    https://github.com/nixcloud/fixPath

release with prebuilt fixPath.exe tool + test program:

    https://github.com/nixcloud/fixPath/releases/tag/v0.1.0

i'd love to get in contact with microsoft research about this, in particular with the MSVC compiler/linker team.

best, joachim

i guess my setup is about 200-300 euros summing all the single devices and casings together.

this does not include the days of assembling the hardware.

i've seen many such proprietary solutions and i dislike them all for various reasons. i've added a list in the motivation of my article.

why do these vendors not honor open source development?

good point. but i do think that my setup works stable and safe for me.

however, i had added the disclaimer because others might be facing a different situation and therefore they are warned.

interesting. this one-way problem was the main reason not to use 433mhz controllers.

thanks for your posting.

i will consider erlang for the next project - you got interesting points.

thanks for providing your link. very nice writeup but as i pointed out, 433mhz is not an option for me as i wanted to know if a set(..) really was working and 433mhz usually doesn't provide any return value.

seeing your post earlier would have saved me some effort getting into REST ;-)

thanks for your feedback! it is very cool stuff but i do not want to rely on external SaaS stuff.

anyway, it seems to be really cool - especially the part where the server replies with JSON ;-)