[maxsideburn]

Ok, first thing that drives me nuts is that the Volume OSD doesn't show up under Windows. It adjusts the volume, but no volume bar appears on the screen.

Secondly, how do I get XBMC to start as the shell under Windows 7? In Ubuntu I would run XBMC as the shell to ensure that it had the most CPU and RAM possible available to it. I like hitting my HTPC's power button and it booting straight into XBMC with never seeing the OS's desktop.

Lastly, do any of you find that XBMC freezes up or becomes sluggish way more on Windows than it does under Linux?

Thanks.

[jhsrennie]

1. is almost certainly because your remote is adjusting the Windows volume not the XBMC volume. Many MCE remotes send APPCOMMAND messages when you press the volume buttons. XBMC doesn't handle these so Windows grabs them and adjusts the windows volume.

It may be possible to change the way the remote behaves depending on the model. The low end remotes usually aren't configurable, but any remote using the eHome driver can be configured: see http://wiki.xbmc.org/index.php?title=Usi...in_Windows. Alternatively the development builds (from http://mirrors.xbmc.org/nightlies/win32/) allow you to configure XBMC to handle the volume APPCOMMAND messages so they change the XBMC not the Windows volume.

2. don't do this. If you want an appliance use Linux. The only good reason for using Windows rather than Linux is if you want to run Windows apps.

3. No.

JR

[maxsideburn]

yeah, but HD stuff plays smoother under Windows. I want the "appliance" feel...but also the ability to play HD video smoothly. Also occassionaly watching Netflix through it is nice as well, so is playing emulator games...I could never get emulators to work properly under Linux.