Reply to thread

My final Solution...

So here's what I ended up with...  I've written two batch files that I put in the MP directory (so any errors and logs will show up there).  I placed a shortcut to the first batch file in the startup folder for "All Users".  This one copies the settings for that user and will start MP on login for my dedicated account "MediaPortal".

Batch file 1:  MediaPortalMove.bat

[code]copy "c:\Documents and Settings\%username%\My Documents\MediaPortal.xml" "c:\Program Files\Team MediaPortal\MediaPortal\MediaPortal.xml"

if "%username%"=="MediaPortal" "c:\Program Files\Team MediaPortal\MediaPortal\MediaPortalLaunch.bat"

[/code]

The second batch file I use to launch MP.  It starts a shell that will run until MP exits and then will copy the current MP settings back to the logged in user's "My Documents".  I just use this to manually start MP instead of the .exe itself. 

Batch file 1:  MediaPortalLaunch.bat

[code]cd "c:\Program Files\Team MediaPortal\MediaPortal\"

start /wait .\MediaPortal.exe

copy "c:\Program Files\Team MediaPortal\MediaPortal\MediaPortal.xml"  "c:\Documents and Settings\%username%\My Documents\MediaPortal.xml"

[/code]

It's not perfect but it works.  It's useless when I run setup while MediaPortal is running, as it will respawn itself the normal way, but how often do you do that?

I still think this is an insanely easy feature to add to the next build.  MP could call the settings file %username%-MediaPortal.xml and then just look at who's logging in/launching it?  Maybe I'm the only one using it for MP multiusers?

8) I love MP regardless, nothing can change that!!!

von