Yeah, I kind of agree about the MFC dll's...on the other hand, if you code something to play nice with Windows specific modules, you tend to have less issues with the OS. I've just gotten in the habit of installing Visual C++ 6 as part of a standard Windows install (the RenderCows are far from the only proggie I use that starts screaming for MFC42.dll, VBRXXX, and a handful of others. And I have the handy option of debugging whatever goes Tango Uniform, and if tech support asks for more info, I can send them the text file). E-on's code monkeys aren't the only ones who tend to forget that development boxes have a lot of things stuffed into System32 that the average user doesn't, more's the pity (and if you happen to have the zip file from E-on, then the required files are in there in the correct folder location; I just copied them into System 32 on my renderboxes. And archived the zip for future needs... ;P ). On the other hand, considering how 'compatible' various iterations of those files are, and the way they get overwritten so happily by other installations, I can kind of see the logic in letting the consumer deal with their own config. Or at least the financial neccessity... Was this a sidegrade to VuePro? The reason I ask is that I found things stabilized considerably when I had left the Vue4 Cow on the system. Both Cows boot properly, running on port 5000 and 5002, respectivly. There could be a file that the Vue4 Cow requires that is better behaved, or the sidegrade Cow simply assumes that it's older sister is there, and makes use of some of the framework in place...