[dommer]

Most of the time (but not always) my mouse cursor does not show up in 8.10. I can still navigate with my keyboard, but not the mouse. Why might this happen, and how can I address it? Below is my log file.

16:26:14 T:5604 M:1049862144 NOTICE: Mapping drive Z to C:\Program Files\XBMC\cache
16:26:14 T:5604 M:1049763840 NOTICE: Mapping drive T to C:\Program Files\XBMC\userdata
16:26:14 T:5604 M:1049763840 NOTICE: Mapping drive Q to C:\Program Files\XBMC
16:26:14 T:5604 M:1049763840 NOTICE: Mapping drive U to C:\Program Files\XBMC
16:26:14 T:5604 M:1049661440 NOTICE: -----------------------------------------------------------------------
16:26:14 T:5604 M:1049657344 NOTICE: Starting XBMC, Platform: Windows Vista, 32-bit build 6000. Built on Nov 13 2008 (compiler 1500)
16:26:14 T:5604 M:1049657344 NOTICE: AMD Athlon™ 64 X2 Dual Core Processor 5600+
16:26:14 T:5604 M:1049657344 NOTICE: Desktop Resolution: 1920x1080 32Bit at 60Hz
16:26:14 T:5604 M:1049657344 NOTICE: Q is mapped to: C:\Program Files\XBMC
16:26:14 T:5604 M:1049657344 NOTICE: The executable running is: C:\Program Files\XBMC\XBMC.exe
16:26:14 T:5604 M:1049657344 NOTICE: Log File is located: C:\Program Files\XBMC\xbmc.log
16:26:14 T:5604 M:1049657344 NOTICE: -----------------------------------------------------------------------
16:26:14 T:5604 M:1049636864 NOTICE: Setup SDL
16:26:14 T:5604 M:1048121344 NOTICE: load settings...
16:26:14 T:5604 M:1048117248 NOTICE: Mapping drive P to C:\Program Files\XBMC\userdata
16:26:14 T:5604 M:1048113152 NOTICE: loading C:\Program Files\XBMC\userdata\guisettings.xml
16:26:14 T:5604 M:1047998464 NOTICE: Getting hardware information now...
16:26:14 T:5604 M:1047998464 NOTICE: Checking resolution 10
16:26:14 T:5604 M:1047998464 NOTICE: Setting autoresolution mode 12
16:26:14 T:5604 M:1047990272 NOTICE: No advancedsettings.xml to load (C:\Program Files\XBMC\userdata\advancedsettings.xml)
16:26:14 T:5604 M:1047990272 NOTICE: C:\Program Files\XBMC\userdata\sources.xml
16:26:14 T:5604 M:1047982080 ERROR: Missing or invalid <name> and/or <path> in source
16:26:14 T:5604 M:1044152320 NOTICE: start dvd mediatype detection
16:26:14 T:5604 M:1044152320 NOTICE: initializing playlistplayer
16:26:14 T:5604 M:1044148224 NOTICE: DONE initializing playlistplayer
16:26:14 T:5604 M:1044135936 NOTICE: load default skin:[PM3.HD]
16:26:14 T:5604 M:1031585792 NOTICE: initialize done
16:26:14 T:5604 M:1031585792 NOTICE: Running the application...
16:26:14 T:5604 M:1030725632 NOTICE: ES: Starting event server
16:26:14 T:4668 M:1030664192 NOTICE: ES: Starting UDP Event server on 127.0.0.1:9777
16:26:14 T:4668 M:1030660096 NOTICE: UDP: Listening on port 9777
16:26:21 T:5604 M:1014775808 NOTICE: Storing total System Uptime
16:26:21 T:5604 M:1014775808 NOTICE: Saving settings
16:26:21 T:5604 M:1014624256 NOTICE: stop all
16:26:21 T:5604 M:1014628352 NOTICE: ES: Stopping event server
16:26:21 T:4668 M:1014788096 NOTICE: ES: UDP Event server stopped
16:26:21 T:5604 M:1014796288 NOTICE: stop dvd detect media
16:26:21 T:5604 M:1014796288 NOTICE: stop sap announcement listener
16:26:21 T:5604 M:1014796288 NOTICE: clean cached files!
16:26:21 T:5604 M:1014788096 NOTICE: unload skin
16:26:21 T:5604 M:1028886528 NOTICE: stop python
16:26:21 T:5604 M:1028886528 NOTICE: stopped

[CrashX]

Please update your build to Beta 1 and test again .. http://sourceforge.net/project/showfiles..._id=283294

[ewodzien]

I have the same problem and tried 9.04 and still have the same issue. I wonder if the OP tried 9.04 yet?

[Spinoza]

Had the same problem myself. Re-starting XBMC usually fixes it, for me.

[ewodzien]

Hmm.. for me, I loose both keyboard and mouse input sometimes when starting XBMC.

I wonder if it is because the KB/mouse drivers haven't completely loaded before starting XBMC? I don't recall having the same problem if I manually start XBMC via double-clicking the icon from the desktop. Perhaps I'll try a delay script.

If anyone can comment and other possible solutions, please let me know.

-Ed

[bananaman]

have the same pointer issue in 9.04. Restart some times seems to fix it

[WiSo]

Perhaps I'll try a delay script.

try calling XBMC.exe with -d X (X = seconds to delay)

[ewodzien]

Ahh.. thanks for the tip.. I'll give that a try and report back!

try calling XBMC.exe with -d X (X = seconds to delay)