In the meantime, there might be a couple of other things you can try to attempt to fix the problem. First would be to uninstall and reinstall the DTK. It's not too likely that this will solve the problem, but it should be very straightforward and take minimal time.
A second option is available if you have another machine with the .Net 2.0 framework available. If you have another machine available, you can try putting the DTK on that machine and see if the same problem occurs. The combination of problems you're seeing (that Commander works, but Director doesn't) is fairly unique, it's possible there's something installed on the machine that is interacting with Director.
Alberto - in one of your other posts, you said that you attached the log files that have all the errors listed in them into this thread. I am not seeing any attachments. Could you please attach the file again so that we can look at it? Also I need to look back through this thread to see if you already let us know and if not, you will need to post the following info: What version of the Director are you running? Did you install the corresponding verion of the AMT Commander? Did you install the .Net Framework? What system are you trying to run it on? What OS are you running? Again, if you already posted this information, then just disregard - I just can't see the whole thread from this window.
One more thing: Are you running the Director exe from the "C:Program FilesIntelIntel AMT Developer Tool Kit" folder, or did you move it somewhere? You will need to make sure all the dll files are in the directory where you are running it from.
Also, please keep your Directorquestions in this thread in order to make helping you a little less confusing.
I'm wondering about your version of the Windows .Net Framework. The readme file for the DTK states that it requires the Windows 2.0 .NET Framework. It wouldn't surprise me if this is your problem. Before we can really help you further we need to make sure your system has all of the right software loaded on it.
Are you saying in #3 that you had version 2.0 installed at one point and the Director was still not working, or that you couldn't install version 2.0 at all? If this is the case, it sounds like you have something going on with your system that is preventing you from installing 2.0 and you will most likely need to resolve that issue.
As I have never had problems running either the Commander or the Director with having the version 2.0 of the .NET framework, I am tending to think that this may be your problem.
I hope this helps (we have sent your question to the folks that actually know more about the Director and are waiting for their response as well - but we also need to make sure your operating environment is correct.)
To the original poster:
Have you been able to resolve this issue? I see that you have another recent post regarding Director where you were presumably able to launch and use it. Therefore, I would assume that you have managed to fix or otherwise move past this issue. In order for us to close this issue, I would like to know if you are still experience an issue with Director throwing an exception upon launch.
- Brett McKown