I guess the good news is that a hardware fault is unlikely at this point. It sounds like the problem is, as you say, that EigenD doesn’t load your vsts, soundfonts, etc. I don’t actually use any vsts, samples or soundfonts inside EigenD myself, so I suspect someone else will do a better job helping you with that. But it sounds like you are nearly there!
In the meantime, just to make sure: have you installed the Resources file from Eigenlabs? A large file that contains the sample loops, soundfonts, etc that EigenD wants to load.
Apologies if the following is obvious information (it is sometimes difficult to know what «tech level» someone is at.) It has probably been mentioned, but in case you aren’t familiar with the difference between 32bit and 64bit vsts: EigenD is a 32bit application and only works with 32bit vsts. However, these days most plugins are 64bit and thus won’t work in EigenD. If you want to host 64bit plugins inside EigenD you’d want to use a VST bridge, i.e. a 32bit plugin «shell» that then itself hosts the 64 bit plugin. A 32bit to 64bit adapter, if you will.
However, many of us don’t load any samples or plugins in EigenD. Instead we send midi out of EigenD and route that to some other host (for instance GigPerformer or a DAW like, say, Cubase). That way the Tau/EigenD is strictly a midi controller and the plugins actually sending audio to your soundcard is in the other software. I prefer this way myself. If you want help setting something like this up I can explain it in detail.
In any case, if you aren’t up and running soon, feel free to send me a PM if you want me to try and help you via Skype.