C'mon guys! Only thinking in the money?
Some interesting news here:
It seems BtCeIf.dll (and friends) don't load at boot time. I still think it's because they are not signed. I've developed a little C++ program that calls several times to ActivateDeviceEx API. With this, drivers.exe loads BtCeIf.dll, BtCeProfiles.dll and BtCeStack.dll using the settings stored in the registry.
Well, using version 1.6, Beemer's .reg file for this version and another .reg file built taking some keys from the full x50 WM2003 registry dump, I've managed to switch bluetooth on (blue led flashing) without the driver memory error. I can run bluetooth manager too. Anyway, there's still something not working because I cannot "see" other devices.
I'll post the files tomorrow morning (football match on TV this evening, sorry).
It'll be interesting if someone with Visual Studio 2005 and WM5 SDK could try to sign the dlls with SDK Certificate in order to test if they load at boot time this way.