HUBBYWIFEYDOTCOM Tales of Life and Adventure of an Intrepid Couple

7Jan/104

Indeo Video IV50 on Windows 7 Fix

Running into unnecessary problems trying to play a movie encoded with the accursed IV50 codec? I sure did. Some of my AVI videos were encoded with the Ligos Indeo XP Video codec awhile back via Pinnacle Studio 8.12.7, and has since stirred up a fuss trying to let me access them in Windoze 7. After much scouring the search results and tinkering and testing stuff, I believe I finally have that gremlin drawn and quartered.

First and foremost, you will need the Ligos Indeo Legacy Package (IV31, IV32, IV41, IV50, YVU9), which I believe is freeware according to my source. It will install Indeo Video codecs for 3, 4, 5, and Indeo Raw (YVU9). The filesize should be about 2,068,266 bytes. You can get it at...

Indeo Codecs Legacy Package (IV31, IV32, IV41, IV50)

Once installed, incredibly enough (believe it or not) you may still run into problems opening your IV50 encoded video. Why? That's because the Indeo installer FAILED (tch! tch!) to register the dll on Windows 7! Is it Indeo's fault, or WINDOZE SEVEN's fault, or BOTH? Who knows? Who cares? OK, I do, but that's a debate for another time. Right now I am itching to share the solution for the good of all mankind.

So go ahead and click that round Microsoft thingy at the bottom leftmost part of your desktop. Then click on All Programs followed by Accessories. Look for Command Prompt and right-click on it. Then click on Run as administrator. Helloooo, are you paying attention there? There's a reason why it's ITALICIZED and BOLDED! I cannot stress enough how *VERY* important this Run as administrator priviledge is, which is a very common problem in Windows 7 with some programs. Ignore it for this instance, and you will be smacked with a pop-up window out of nowhere happily informing you that "... the codec was loaded but the call to DllRegisterServer failed with the error code 0x8000ffff".

Assuming that you had followed the given instructions right down to the letter, you should be idling at the command prompt right now. Go ahead and type in the following:

regsvr32 ir50_32.dll

Press your Enter key, and voila, *hopefully* your problem should be solved. I know it did mine. ;)

5Jan/100

Happy New Year… and Microsoft bug!

HAPPY NEW YEAR! Yep, this is *my* year... the Year of the Tiger! :) It's been an interesting ride the last 4 days... eating (more like gorging on) wifey's freshly baked bread, researching on going to law school until one look at a sample of the LSAT pretty much gave me an endless headache that will rival me wifey's migraine. And of course, who can forget an annoying computer bug thanks to Microsoft's newest operating system, Windoze Seven. Just what I need to keep things interesting.

"The action can't be completed because the file is open in windows explorer."

Yeah... right. So, Explorer's got a chokehold on one of my files and wouldn't let me rename nor delete it. Yes, I have configured the permissions correctly, giving myself enough control to supposedly smash the file to smithereens if I should have wished it so. Unfortunately, it was all an illusion. How cruel of Microsoft. No matter. I still *smile* through it just as one of my many past martial art instructors had advised regardless of the circumstances. He taught me well. And through an enlightened peace of mind I discovered... tadaa... LOCKHUNTER.

Check out http://lockhunter.com

Unlocker has had its glory days with XP (thanks for the memories while it lasted), but this newest bomb of an atom literally tore Explorer's chokehold on my file to shreds, leaving the file finally at my mercy to do whatever I wanted to do with it. Here kitty kitty... HEY, where ya going? Wait till I get my hands on...