a nice program - I can test with Vista on my laptop and on my stationary

Sorry for that -I missunderstood your message...
I'm glad you sorted it out in the end - so I deleted my line there as well...

First: I'd seriously consider figuring out a new Name.  WiimoteConnect or or something.  WiiConnect is awfully close to WiiConnect24, and likely to draw ire from the N.

Beyond that, we should work together.  I'm working on a cross-platform system for accessing Wii Remotes.  You have a platform-specific app that connects to the Wii Remotes and keeps them happy while not in use, then "client" programs connect to that app via localhost TCP sockets.  That way all the really platform-specific stuff is in one place, letting the client be mostly cross-platform (or entirely cross-platform if it uses SDL or the like).  It also lets you keep the Wii Remtoes connected between runs, since connecting them is still a bit annoying.

Not sure what you mean by interface definitions.   API?

Yeah, and it's fairly thin.  All of the Wii Remote management logic is pushed into the client app*.  Right now it uses unix-domain sockets instead of TCP sockets, but you can see it here: http://www.soe.ucsc.edu/~Inio/wii.html

It's a zip archive, so you should be able to unpack it in windows.

For the change to TCP, I'm thinking the following will happen:

+ connection host listens on a specific port on the loopback device only (not visible to network, less likely to cause UAC alerts)
+ single connection is used to communicate with all connected Wii Remotes, second byte of packet in either direction indicates which remote it's from (first is length)
+ this would change the API exposed by wiidev_client.h a bit  relating to opening and updating devices, and would require a new enumeration API.

* there's two big reasons for pushing wii remote logic into client app:
1. removes version dependency from client to connection host
2. allows clients to use features as they're discovered

ok, what is the path in the textbox? can you paste it here?

does the bottom of the dialog become green and says connected?

after doing the connecting procedure the program waits a few seconds and thenn checks if the wii is connected after that it launches the programm, maybe the period is to short and when i check if it is connected it isn't jet so the program isn't gonna start.

but i just got an idea how to fix this, i aint got my wiimote with me but i gonna wite it now and upload another version. i can't test it with my wiimote so you have to.

thex

hm, is there any error or does it say "connected" but just the whiteboard doesnt work?

as long as no programm is startet that uses the wiimote countinious blinking means the wiimote is connected properly, if there is no connection the wiimote will stop flashing after some 20 seconds or so.

johnnys whiteboard is using the wiimote lib you can download the lib and the package contains a test tool, if jou get a connection with that one something other goes wrong.

also using the built in bt doesn't necessarily mean you are using the ms bluetooth stack, som vendors bundle their products with widcom or similar stacks... see attachement, thats what you need (sorry only in german)

also i can't really test x64 compatibility

thex

no prob, hope you go on testing the app because i'm not sure if it eventually works with other bt stacks too.

i just found out something that might be your problem!
i tried to use wiinremote with my wiimote but it didnt work. it somehow messed up my wiimote. the connection is established just as before but when i start the whiteboard it says "no wiimote found". to make it work again you have to take out the batteries and then put them back in place and then reconnect it.

i'm working on the code right now i already programmed a new way to determine if the wiimote is connected.
gonna upload an update later

thex