Same thing, just unresponsive Capture and no CPU pegging.So how did you arrive at that file set? Maybe the technique could help me.-Updated -Actually, cdsMsgServer/NameServer don't appear in the task list unless I include all those files, but Capture still doesn't run.
Then I introduced cdsCommon.dll, then the minor dll's. No missing DLL messages or anything like that. I don't get the CPU pegging, now, and I see cdsMsgServer/NameServer running with a single instance, finally, but Capture still doesn't execute just hangs for about a minute and then gets killed off as 'unresponsive'.I tried just copying over cdsMsgServer/NameServer.exe but I get the same thing.