<div class="gmail_quote">On Mon, Apr 11, 2011 at 9:57 PM, Ralf Habacker <<a href="mailto:ralf.habacker@freenet.de">ralf.habacker@freenet.de</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Am 09.04.2011 03:40, schrieb Mat:<div class="im"> <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> hi, as I know, the default env setting on windows is, "DBUS_SESSION_BUS_ADDRESS=autolaunch:scope=install-path" the "install-path" let dbus resolve the dbus session channel by "path of libdbus-1.dll", so "the file location of libdbus-1.dll" and "the search path order" will affect the connections between run-time processes. btw, in my previous test, dbus seems to check libdbus-1.dll's parent dir's name, and its related path "bin/libdbus-1.dll" ( parent dir name should be "bin" ), and ...etc/. So I suggest that preserver the original directory sturcture and put it on one of the system default search path. </blockquote></div> This is documentated at <a href="http://dbus.freedesktop.org/doc/dbus-specification.html#meta-transports-autolaunch" target="_blank">http://dbus.freedesktop.org/doc/dbus-specification.html#meta-transports-autolaunch</a> </blockquote><div> so should I use DBUS_SESSION_BUS_ADDRESS=autolaunch:scope=install-path or DBUS_SESSION_BUS_ADDRESS=autolaunch:scope=*install-path ? Vincent Torri </div></div>