The setup took several minutes, I don't know how many MBs where copied to the disc/registry but it must be a lot. Even after closing MP there is still TV server and SQL server running taking more then 150 MB working memory together and there is no option to automatically shut it down.
I wish things would be designed with efficiency having a much higher priority, even with jitting and all other stuff going on in the CLR on startup, it's possible to build applications that startup instantly on a second start, MP takes more then 5 seconds on my dual core machine, simple things like changing key/remote mapping are a challange because it takes 5 secs startup the config dialogs (even closing takes seconds) + 5 secs to restart MP and because of the poor usability due to unecessary complexity in the config dialog. It might for instance be much more efficient if all input devices (keyboard and remotes) would share the same config interface like in DVBViewer. It's easy to bitch of course, maybe I can help working on efficiency and usability.
I wish things would be designed with efficiency having a much higher priority, even with jitting and all other stuff going on in the CLR on startup, it's possible to build applications that startup instantly on a second start, MP takes more then 5 seconds on my dual core machine, simple things like changing key/remote mapping are a challange because it takes 5 secs startup the config dialogs (even closing takes seconds) + 5 secs to restart MP and because of the poor usability due to unecessary complexity in the config dialog. It might for instance be much more efficient if all input devices (keyboard and remotes) would share the same config interface like in DVBViewer. It's easy to bitch of course, maybe I can help working on efficiency and usability.