Hi, That sounds like the Kinect Server is crashing. Obviously that's not right -- it should just fail/refuse to start if the Kinect isn't working, rather than crash. And it makes it stranger if one of the OpenNI programs work but ours doesn't (our program is very similar to the OpenNI samples in how it uses the Kinect, so if theirs works, ours should too). Before you select right-click and try start, can you instead right click and select show log, then paste the contents of that log into a reply here? (Equally, if it crashes when you try to show log, let me know as that's also interesting.) (I can't see that screenshot: dropbox gives me a 403. Do you need to find a public link for that file instead?)

Hey nccb, sorry for the broken link ;). Here's a new one http://dl.dropbox.com/u/41579700/screenshot.JPG , the log wouldn't let me copy paste it... so it's a screenshot too, http://dl.dropbox.com/u/41579700/screenshot1.JPG . The first error seems completely unlogic to me, because I watched the kinect's cams via CLNUIDeviceTest about ten seconds before... By the way, sorry for my english and the german in my screenshots... I'm german :) Thanks in advance! alexander i forgot to post my computer's data, if you need that: hp pavilion dv6513eg Windows Vista Home Premium AMD Athlon 64x2 TK-53 2 GB DDR2 Ram @667Mhz 160GB disk nVidia GeForce 7150m

Having googled CLNUIDeviceTest, I think I know what might be causing the problem. There's several efforts to provide a driver for the Kinect on Windows. We are using OpenNI, which gives access to the skeleton tracking, as well as RGB, depth etc. Libfreenect is an alternative, which I think was released earlier, but doesn't support skeleton tracking. The CLNUIDeviceTest program appears to come from libfreenect. The problem with having both libfreenect and OpenNI installed is that the Kinect can only have one device driver at a given time, and if libfreenect is the one acting as the device driver (which by the sounds of it, is the case, given that CLNUIDeviceTest is working for you), then OpenNI can't act as the device driver. Hence no OpenNI program will work. A quick solution should be to remove libfreenect from your system, then reboot, and hopefully OpenNI should take over and the Greenfoot side should work. If you don't want to uninstall libfreenect, or it proves tricky, you may be able to poke around in the Windows device manager to tell it specifically which driver to use for the Kinect.

Hi nccb, I didn't think about that possibility at all. I'm going to try it immediately and I will tell you if it worked ;). alexander

So, I tried it, uninstalled the CLNUI platform, rebooted... But now the error stays the same and my drivers for motor, cam and audio are away :D. First question then is: Do you know where I can get the drivers belonging to OpenNI (OpenNI itself is installed)? On the greenfoot site from the first post, they only enumerate OpenNI, NITE & the OpenNI driver, which I installed all :D Crazy shit... Next problem there is: On my computer, there is no folder called C:\Program Files\OpenNI\Samples\Bin\Release (for 32 bit Windows), I also checked the 64bit version... and in my search, NiUserTracker does not exist... But, looking into my control panel, I can see OpenNi framework and NITE are installed, the drivers should appear elsewhere, I think. But I installed re-installed them now several times. :O I hope you don't get annoyed ;) alexander

The OpenNI device drivers for the Kinect are in the third file listed on the install instructions page. I think in the Control Panel, it shows the drivers under something like "SensorKinect" or "PrimeSense", so it's not next to OpenNI and NITE. If you've installed them several times, they should be there :-) In the device manager, does it show the drivers as working, or does it have the devices with a little icon indicating that the drivers are missing? As to the samples directory: that was due to me giving an OpenNI installer without the samples. I've replaced it now, so if you're still in a re-installing mood, download the first file from the previous link, which will now be a different file, and install that, which should give you the samples.

Hey nccb, I re-installed the OpenNI & then rebootet my pc, now the samples folder is included but when I try to open the NIUserTracker or anything else, the following error occures Screenshot 3 . Kinect is connected and as you can see here, the PrimeSense drivers are installed Screenshot 4 ... But taking a look into the device manager, there is only XBOX NUI Motor listed, unlike when the CLNUIPlatform was still installed, when there were also Audio and Camera. Screenshot 2 . Also for the NUI Motor, drivers are missing :O Perhaps you know a solution?? Thanks for your patience alexander

Your list of installed software seems to match fine exactly, so I think you have the right things installed. I've taken a screenshot of what the device manager looks like on my XP system with a working Kinect: There is a missing driver for the audio, but that's fine (and in fact, if the motor driver is missing that's also okay), but the key bit is that under PrimeSensor I have "Kinect Camera". That's off the bottom of your screenshot, so I can't tell if you have that or not. One thing I have read from other people who have problems with the device is to try a different USB port (e.g. if it's plugged into the front or into a hub, try plugging it into the back of your PC), but given that you had it working with libfreenect, I shouldn't imagine that will make a difference here.

:D no, there is nothing else belonging to the kinect... the category "PrimeSensor" does not exist, the Kinect camera & audio are missing, so the only thing i can see is listed in "other devices", the XBOX NUI Motor... my device manager alexander

If you don't see a PrimeSensor category, that suggests the drivers might be a problem. I think the thing to do is to try to find the Kinect devices and see what drivers they have. If you go to the "View" menu, ("Ansicht" for you), then select the "Devices by Connection" item (don't know the translation, it's the second item on the menu on Windows 7). This gives a view where, with a bit of clicking, you can drill down to find your USB devices, and hopefully find what the Kinect devices are being listed as. Here's a screenshot of the view from my Windows 7 machine with a working Kinect: (link to full-size pic) Look for the devices under "PCI Bus" that have a USB plug icon, and expand them to find something sounding like a Kinect. As you can see, mine are listed as "Kinect Camera", etc, but it will be interesting to see if you can find what yours are. (If you can't find them, try unplugging and plugging them into a different port, and see what shows up).

So, I finally did what you said and here's the results: In the PCI Bus, the only thing I can find stays the NUI Motor, as you can see here PCI Bus 1 & PCI Bus 2 ... I also unplugged&plugged the Kinect, but that did not change the situation. The only proof that it is actually connected seems to be this alert , shown when the Kinect is being plugged in, telling me that new hardware was detected. I often cancelled the search for drivers, but, just to try it, I once clicked on search&install drivers, which ended up here: drivers not found, insert disc.

Ok, so it's clearly a problem with the drivers. You need to convince Windows to use the OpenNI drivers for the Kinect. You can either do that by right-clicking on the Xbox NUI Motor device in the device manager and using "select driver" or "update driver" (or something similar), or when the search fro drivers comes up, tell it to search, but there is an option somewhere in the find-drivers wizard that allows you to tell it to search a specific directory. Use that option to tell it to search in C:\Program Files\PrimeSense\SensorKinect\Driver

Hey nccb, thanks for your patience :) It finally works perfect... The "select driver" with the given path finally did it! If you're interested in what I try to do, it's something like that. I'm working with a group of four students on a school project for a "Kinect controlled RC Car" :D kind regards alexander

Hi, I am having the same problem.I followed all the steps which you have mentioned above.when the search for drivers shown up, i told it to search, but there is an option somewhere in the find-drivers wizard that allows you to tell it to search a specific directory. Use that option to tell it to search in C:\Program Files\PrimeSense\SensorKinect\Driver. I used the above step but its give me "the hash for the file is not present in the specified catalog file." What should i do??please help me out Thanks, deepthi