Hia,
i'm getting some weird errors, after a fressh new install.
On DCERouter.log, i've found some entries like:
The target device 20 (routed to 20) has not registered. <0xb6e27b90>
The target device 21 (routed to 21) has not registered. <0xb6d08b90>
The target device 46 (routed to 46) has not registered. <0xb6d08b90>
and
The target device 46 (routed to 46) has not registered. <0xb6d08b90>
05 09/08/10 11:32:29.018 Socket::ReceiveData 0x9a23f2b8 failed, bytes left 0 start: 620000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 130 Incoming_Conn Socket 130 127.0.0.1 <0x841d3b90>
05 09/08/10 11:32:29.018 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 130 127.0.0.1 <0x841d3b90>
05 09/08/10 11:32:29.018 TCPIP: Closing connection to -1003 (Router Dev #0) 0x9a23f2b8 m_Socket: -1 <0x841d3b90>
05 09/08/10 11:32:29.018 Router::RemoveAndDeleteSocket 0x9a23f2b8 -1003 <0x841d3b90>
05 09/08/10 11:32:29.226 Socket::ReceiveData 0x9a24f1d0 failed, bytes left 0 start: 640000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 145 Incoming_Conn Socket 145 127.0.0.1 <0x7a1bfb90>
05 09/08/10 11:32:29.226 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 145 127.0.0.1 <0x7a1bfb90>
05 09/08/10 11:32:29.226 TCPIP: Closing connection to -1003 (Router Dev #0) 0x9a24f1d0 m_Socket: -1 <0x7a1bfb90>
05 09/08/10 11:32:29.226 Router::RemoveAndDeleteSocket 0x9a24f1d0 -1003 <0x7a1bfb90>
For device 21 (21_LaunchOrbiter.sh.log), i've found the following entries.
I don't know why this is happening, but the effect is the freezed OSD.
05 09/08/10 9:15:07.977 FocusIn! <0xb5a9b6d0>
05 09/08/10 9:15:07.977 FocusOut! <0xb5a9b6d0>
05 09/08/10 9:15:07.978 FocusIn! <0xb5a9b6d0>
01 09/08/10 11:22:34.491 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.492 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.492 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.492 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.493 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.493 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.494 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.494 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.495 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.495 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.496 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.496 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.496 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.497 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.497 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.497 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.498 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
01 09/08/10 11:22:34.498 WmCtrl::LowLevelCommand Cannot open display. <0xb5a9ab90>
The DCERouter.log is at http://pastebin.org/826164
Any hint of what could be happening?
TIA
I've got the same thing going on but only notice it when starting a game. Game crashes right away the goes right back to screensaver.
Any solution?
08 09/10/10 21:07:12.913 Received Message from 10 (Media Plug-in / Living Room/Family Room) to 52 (Game Player / Living Room/Family Room), type 1 id 193 Command:Off, retry none, parameters: <0xa9940b90>
08 09/10/10 21:07:12.913 Parameter 97(PK_Pipe): -1 <0xa9940b90>
08 09/10/10 21:07:12.914 Received Message from 10 (Media Plug-in / Living Room/Family Room) to 20 (The core/hybrid / Living Room/Fa mily Room), type 1 id 192 Command:On, retry none, parameters: <0xa9940b90>
08 09/10/10 21:07:12.914 Parameter 97(PK_Pipe): 0 <0xa9940b90>
08 09/10/10 21:07:12.914 Parameter 98(PK_Device_Pipes): <0xa9940b90>
05 09/10/10 21:07:12.914 The target device 20 (routed to 20) has not registered. <0xb6525b90>
01 09/10/10 21:07:12.915 debug_stream_end MediaStream::~MediaStream c1 1002/0x9380390 <0x9010db90>
Guys, Device 20 is a device that does not have a DCE device, therefore it does not register.
The issue you are seeing with the game player is because mame or mess did not like something, and when it quit, the game player sent an event to stop the media stream. run the game outside the orbiter to see what it is complaining about.
-Thom