My goal is to interface with the murmur speech server (<a href="http://mumble.sourceforge.net/">http://mumble.sourceforge.net/</a>). This server ships with the following dbus-daemon.exe mt-jog:/c/Program Files/Mumble> ./bin/dbus-daemon.exe --version D-Bus Message Bus Daemon 1.1.1-2 Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others I guess my next step would be to checkout the windbus tree and try to compile it on windows, but what I saw scared me a little - and I'd like to have a fair confidence in the fact that it would solve my problems.            /jog <div class="gmail_quote">On Tue, Jun 10, 2008 at 9:54 AM, Christian Ehrlicher <<a href="mailto:Ch.Ehrlicher@gmx.de">Ch.Ehrlicher@gmx.de</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Von: "Jacques-Olivier Goussard" <div><div></div><div class="Wj3C7c">> So I set > <auth>DBUS_COOKIE_SHA1</auth> > in the daemon configuration. > I use > DBUS_TEST_HOMEDIR=C:/tmp > in the daemon environment and > -Duser.home=C:/tmp > on the client java command line - both should read/write the cookies from > the > proper place right ? The doc is really thin on those issues. > I get : > 15684: server: got command "AUTH DBUS_COOKIE_SHA1 6a6f67" > 15684: server: Trying mechanism DBUS_COOKIE_SHA1 > 15684: server: data: 'jog' > 15684: Using fake homedir for testing: C:/tmp > ... > 15684: server: data: '821f3865ae9ebb4af7e7e9ffafa31c9f2309117b > 5df4c83adaa60c550 > f38edb1d121cadba04e6dbb' > 15684: server: going from state WaitingForData to state WaitingForBegin > 15684: server: authenticated client using DBUS_COOKIE_SHA1 > 15684: exchange_credentials: do_reading = 1, do_writing = 0 > ... > 15684: server: got command "BEGIN" > 15684: server: going from state WaitingForBegin to state Authenticated > 15684: _dbus_getsid() returns 1 > 15684: Client authorized as SID > 'S-1-5-21-52702793-1996691837-315576832-2805' bu > t our SID is 'S-1-5-21-52702793-1996691837-315576832-2805', disconnecting > 15684: _dbus_transport_disconnect start > ... > and it fails. > This is with the DBusVIewer client from dbus-java-2.4. > Log attached. </div></div>Just out of curiosity  - what windbus do you use? Where do you have it from? Christian -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: <a href="http://www.gmx.net/de/go/multimessenger" target="_blank">http://www.gmx.net/de/go/multimessenger</a> </blockquote></div>