creative-foc.us

Latest

Enable DTS passthrough for .dts audio files in XBMC

XBMC by default will not pass DTS to your audio receiver when playing .dts files or DTS .wav files. This is because XBMC by default plays all audio using PAplayer, which apparently does not handle DTS; the audio is downmixed to 2 channels. You can easily get around this by playing the audio via XBMC’s DVD Player. You can’t do this song-by-song as XBMC will only let you open video files with the DVD Player via the interface. There’s a fix that allows you to make XBMC play your DTS files via DVD Player automatically via the Music menu, though:

Find your playercorefactory.xml file (is at /usr/share/xbmc/system in XBMC live/XBMCbuntu) and add this line somewhere below the line “<rules name=”system rules”>”, and before “</rules>”:

<rule filetypes=”(dts|wav)” player=”DVDPlayer” />

Note: Visualizations won’t work and there is a ~1 second delay before you hear audio after hitting play, so each song is missing the first one second. It’s certainly better than your 5.1 mix outputting over only 2 channels though.

Default Gateway Disappearing From TCP/IPv4 Properties

You might’ve experienced a strange problem, perhaps after cloning a sysprepped Windows VM, where the default gateway you set in TCP/IPv4 (TCP/IP if on 2k3) properties just disappears. You’ve tried rebooting, setting it back to DHCP, and it keeps happening. Give this a shot!

Disclaimer: This will reset all network interfaces’ configuration, so use with caution.

In an elevated command prompt:

netsh int ip reset resetlog.txt

Then Reboot. If you still see this issue, give this one a try too:

netsh winsock reset catalog

Fetid Edge

VMWare ESX 4.1 update oddities

initrd /initrd.img

Error 15:File not Found

Press any key to continue …

See this? Want to scream? It’s okay, I might have a solution for you:

1. Boot into Troubleshooting mode.
2. cd /boot
3. ls -al (see if there’s an initrd.img link that is broken, it will show up red)
4. rm initrd-2.4.xx-xxx.esx.img (remove the oldest initrd .img file if there is more than one)
4. ln -s initrd-2.4.xx-xxx.esx.img initrd.img (Replace x’s with the newest version that is actually there, which will re-link the broken link to another img, if one is available. You will if you are seeing this for the same reason I saw it.)
5. reboot

Ignore all the kernal mismatch errors you will probably see, and wait about 5-10 minutes. Then:

6. cd /boot
7. ls -al (see if the missing initrd .img version from step 3 is actually there now. It will be a newer version than the one you linked in step 4.)
8. ln -s initrd-2.4.xx-xxx.esx.img initrd.img (link to the newer one you now should see, since vmware now has had the chance to finish its update script.)
9. reboot

That should do it. What probably happened was your update script tried to copy a new version of the initrd image into /boot, but since you followed vmware best practices and there is obviously a bug in their update software causing old versions to not be removed, the /boot partition was full. The script should try to recover once you boot up with that old initrd, though. :)

Hope that helps any.

Looking for passphrase ideas?

If you’ve been tasked with changing some passwords and would like some great ideas, check out IMDb quotes. Sci-Fi movie quotes always make good passphrases.

Total Recall quotes

The Amazing Love

First attempt at painting on the iPad

Zombie Robot

Leviathan