Error 14001 with tk.wii
I’m about to contact the author of tk.wii, but I also wanted to cover my bases with a query here.
I’m trying to use this new external in XP that grabs wiimote data and brings it directly into MAX/MSP. Every time I attempt to load "tk.wii" I get an error message:
"error: Error 14001 loading external tk.wii"
…and the external does not run.
This is a fresh install of 4.6.2 with new Quicktime, updated .NET framework, and a fresh install of XP (SP 2).
I have also tried the external on four other XP machines with the same result.
Does anyone have any idea what causes error 14001?
I’ve heard that some of you are using this external with XP, so it must work under certain conditions…
Thanks for your help,
I’m getting the same problem, let me know if you get anywhere.
Are you guys using BlueSoliel bluetooth drivers? I don’t
think it works with anything else.
It may even be trying to load BlueSoliel dlls that
may not be present on your machine when Max instantiates
—– Original Message —–
From: Anthony Palomba
Date: Thursday, May 10, 2007 10:21 am
Subject: [maxmsp] Re: Error 14001 with tk.wii
> Are you guys using BlueSoliel bluetooth drivers? I don’t
> think it works with anything else.
I think you may be right. I’m trying the Soliel drivers this weekend…I’ll report back.
so I need:
- a wii controller
- tk.wii external for my xp system
- a bluetooth dongle from BlueSoliel.
- homemade IR pannel
Does anyone know the resolution of
the sensors coming in tk.wii?
And the last one: Does anyone know
about future plans for tk.wii to get the information
of the Nunchuk-controller and classic controller
and what about controlling the speaker and the
rumble inside the controller?
thanks for any reactions!
I’m using BlueSoleil drivers and still getting the error.
i was just wondering what people have to say about using this object. i have been able to use the aka.wiimote extension on the mac, and was hoping this would be as powerful as that.
i tried using the object and got no response, then downloaded the bluesoleil and installed, but it seems that bluesoleil only works with external bluetooth, my laptop have bluetooth built in, so if it is true that this tk.wii only works with the bluesoleil bluetooth manager i would have to buy a dongle so i could use the software (seems odd, but if it works :P)
anyway, i was just looking for some concrete feedback before i dropped the cash for a dongle.
Anyone gotten any further with Wii installation in Windows?
Until two weeks ago, I was using it happily with GlovePie and BlueSoleil, while I still had WinXP home edition SP1. I then had the time to do an installation of WinXPpro SP2, including a new installation of the BlueSoleil which came with my dongle. The device is recognized and connects just fine, the same as it did before, but neither GlovePie or tk.wii recognize it, even after trying at length to make it work.
There is one difference: I installed WinXPpro into a folder called "Windows2" for fear of losing something important. Is it possible that GlovePie and tk.wii are looking for something in the "windows" folder?
Another possibility is that the Wii somehow pairs with the computer or the hardware and leaves a digital ID somewhere (there are posts in other forums which point to this)?
Let us know if you have any answers!
Thanks for all the excellent thoughts here.
I’m on a four week hiatus from anything "compositional" so I’ve lost the momentum here.
However, I can say that my windows installation is standard (with the normal windows directory) and tk.wii is still not functioning (error 14001).
I’m using GlovePIE with very good results, without the Blue Soleil drivers.
I tried to install them, but they do not appear to be compatible with the dongle I have (Targus brand).
Anyway, we’ve now heard from Mrboni that the error is still present even with the BlueSoleil drivers…
It would be great to hear from some more folks who are having some success with tk.wii. If you could share your hardware/software setup, maybe we could figure this thing out.
My continued thanks!
PS I’ll email the author of tk.wii right now and post anything I discover.
I received a url for an update that should fix the problem. The author of tk.wii asks us to download the bug fix. Below is his message:
error 14001 when loading the "tk.wii".
I think that it work on your computer.
1) Download new object.
2) Reinstall object. and help.
3)Please install .net framework2.0. if does not install it.
Please try it!
I haven’t tried it, nor will I have a chance to for a couple of days, so please let us all know if it works when you try it.
Good luck, all the best, and thanks to Takeru!
Well it seems to work for me. I am using XP (service pack2), .net framework 2.0, BlueSoleil drivers (v2.3), and Max 4.5.
Hi, just to clarify,
Do I NEED to bluesoleil dongle to use tk.wii, or just the drivers?
Can i use my internal bluetooth, or do I need SOME external dongle?
Is there a particular dongle that works best?
can someone who’se got this working let me know? thanks!
I worked with bleusoleil for some time with
an external dongle. Now I have a new laptop
with an internal bleutooth with software:
bleutooth stack for windows by toshiba
bleutooth: 2.0, 2.1, 1.1
I wish I had this before. This software remembers my wii-motes.
Bluesoleil takes 1 or 2 whole minutes to find and connect the wiimotes. this thing takes 10 seconds hooray.
lot of usefull information on this page:
(there’s also a page with all known
dongle’s wich work with wii (I think
almost all of them))
I don’t use wii.tk anymore, I use glovepie
and midiyoke. The list of sensors is much
more complete with glovepie. I hope one day
a maxexternal will be there wich is good enough.
better resolution than midiyoke…
(btw, this is what I did in Holland
with the wiimotes and max/msp
I have only tried it with the BlueSoleil dongle. I know
BlueSoleil sells the software separately so maybe you might be
able to get it to work with third party hardware.
NO, you don’t need to use Bluesoleil. Some built-in bluetooth drivers work fine – you can’t use the *standard* windows bluetooth driver, because it isn’t a full-featured driver. Many laptops come with a better set of driver, though. I know this first-hand – HP laptops have worked for us in the past with stock drivers.