Desktop shortcut for Basic Home Editor crashes with MP 1.6. (1 Viewer)

[Neff]

I've just upgraded to MP1.6 preview (clean install) and I've re-installed StreamedMP (2.1.4.3385) but the Basic Home Editor won't work. Every time I try to run it I get the message "SMPEditor has stopped working" but no further details.

The Windows log file has this information.

Faulting application name: SMPEditor.exe, version: 2.1.4.3385, time stamp: 0x5280a6b8
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
Exception code: 0xe0434f4d
Fault offset: 0x0000c41f
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13


Any suggestions on how to try and sort this out? Is it anything to do with MP1.6 needing the 4.0 .Net framework?

(Windows 7 64bit)

 

[Neff]

A small update, it seems to be only from the desktop shortcut that it does that. If I go via the MP Configuration editor I can edit the Basic Home Page.

 

[Holzi]

A small update, it seems to be only from the desktop shortcut that it does that. If I go via the MP Configuration editor I can edit the Basic Home Page.

That is fixed for MP 1.6.0 Final.

 

[Neff]

Thanks

 

[BrownGhost]

Thanks i was going crazy, just made hole new HTPC, win 8 everyting clean install and could not start basic home editor lol
mepo pre 1.6
all other things newst also

 

[Holzi]

and could not start basic home editor

It should start from MP Config > Plugins tho.

 

[Airw0lf]

A small update, it seems to be only from the desktop shortcut that it does that. If I go via the MP Configuration editor I can edit the Basic Home Page.

That is fixed for MP 1.6.0 Final.

Weird - I still have this issue with 1.6 final. I have SMP v2.1.4.3385. Any ideas?

 

[Spaldo]

Yep, I also have this issue since upgrading to the latest StreamedMP with MP 1.6. As the posts above say, I can launch it from the MP Config...

 

[ltfearme]

Is it anything to do with MP1.6 needing the 4.0 .Net framework?

Yes. Nothing you can do until a new release is compiled against .Net 4.