Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[alexgit]

Whenever I try to start MC (tried 12.0.14 and 151) via remote desktop or via FireDaemon (as media server) it just exits with no message.
I was able to start it when I use primary console (tv in my case).
Gents, if you have some hidden logic (like the one that would not start it for the second user) - at least provide appropriate messaging.
Any comments?

Alex

[alexgit]

After I rebooted it popped up error dialog
for every time it didn't start.
Here is information, if interested:
szAppName : Media Center 12.exe     szAppVer : 12.0.251.0     
szModName : Media Center 12.exe     szModVer : 12.0.251.0     offset : 0042aec5

I can't figure how to attach dump file to the post.

Alex

[Matt]

I'm not sure if this is the issue, but two user accounts can't be running MC at the same time.

[Matt]

I should add that MC > Help > Logging... can be used to see what MC is doing during startup.

[alexgit]

No I don't have other copy of MC running. I just try to start it via remote desktop or as library server via FireDaemon.
In both cases it crashes leaving message in the log (follows). I am using Windows Server 2003 by the way.

Event Type:   Error
Event Source:   Application Error
Event Category:   (100)
Event ID:   1000
Date:      19.06.2007
Time:      23:33:25
User:      N/A
Computer:   MEDIA
Description:
Faulting application Media Center 12.exe, version 12.0.259.0, faulting module Media Center 12.exe, version 12.0.259.0, fault address 0x00425af5.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 4d 65 64   ure  Med
0018: 69 61 20 43 65 6e 74 65   ia Cente
0020: 72 20 31 32 2e 65 78 65   r 12.exe
0028: 20 31 32 2e 30 2e 32 35    12.0.25
0030: 39 2e 30 20 69 6e 20 4d   9.0 in M
0038: 65 64 69 61 20 43 65 6e   edia Cen
0040: 74 65 72 20 31 32 2e 65   ter 12.e
0048: 78 65 20 31 32 2e 30 2e   xe 12.0.
0050: 32 35 39 2e 30 20 61 74   259.0 at
0058: 20 6f 66 66 73 65 74 20    offset
0060: 30 30 34 32 35 61 66 35   00425af5

[JimH]

Please use MC's logging (under Help).

[Chili-Jam]

If you use Remote Desktop and start MC and you try to start in Theater Mode
then MC crashes without a sign.
Remote Destop and 3d graphics just don't work when starting MC. Are you trying to show
anything using 3d?

Normally i set MC to start in Theater MOde on my HTPC.
I created another shortcut that starts MC in mormal View when using Remote Destop as a workaround.

There's another thread reporting crashing in Windows 2003:

I am finishing up a windows server 2003 client box, and it looks like everything is working but Theater View.  If I try to go into theater view, MJ12 crashes with the message: "Faulting application Media Center 12.exe, version 12.0.240.0, faulting module Media Center 12.exe, version 12.0.240.0, fault address 0x00425c85".

[JimH]

If you use Remote Desktop and start MC and you try to start in Theater Mode
then MC crashes without a sign.
Remote Destop and 3d graphics just don't work when starting MC. Are you trying to show
anything using 3d?

Normally i set MC to start in Theater MOde on my HTPC.
I created another shortcut that starts MC in mormal View when using Remote Destop as a workaround.

There's another thread reporting crashing in Windows 2003:

If 3D fails to run on whatever system you're running, MC Theater View will fail.

[alexgit]

Ok that was it. And I had some other reason for FireDaemon to fail to start it.
I assume that by release MC will be able to give some meaningful message rather then just crash in case of 3D graphic not available.

On the second note, is there a compelling reason not to allow more than 1 process? Especially with library read only.
How can I run media server as daemon and at the same time use UI in home theater console? I think I brought this issue up long ago and somebody mentioned that
something is going to be done.


Thanks

[Matt]

A recent change caused MC to stop nicely handling Direct3D errors.  It'll be fixed next build.