> The error that I'm getting now, that I don't know how to work around, is > this: The problem was related to a QCA API change. Since we now bundle our own QCA with Psi (since last week), you should not see the problem anymore. Don't forget to re-configure. cheers, Remko