PDA

View Full Version : Xvid modules cannot be found


Perfect_Form
10th May 2008, 23:20
Hello,
I'm trying to use the latest Xvid release from Koepi. The problem is that after installing, I see no evidence of the codec in the System32 directory. When I try to configure the decoder, it says, "Error loading xvid.ax, The specified module could not be found." I get a similar error when trying to configure the encoder, but this time it is xvidvfw.dll, that cannot be found.

I'm running Vista Ultimate 64-bit
AMD Athlon X2 4800+
4GB RAM
SLI Geforce 8800GT
Creative X-FI Platinum

Thank you for your help,
Perfect_Form

jeffy
10th May 2008, 23:23
I might be wrong, but aren't they supposed to be in the Syswow64 directory?

Perfect_Form
15th May 2008, 01:49
Thanks for the reply.

You are correct, they should be there, not System32. I just looked and they are in SysWOW64, but I still get that error. I think my computer is still looking in System32. How do I correct this?

Perfect_Form

unskinnyboy
15th May 2008, 02:41
Koepi's builds are 32-bit. You need to use a 64-bit Xvid installer. Either this (http://members.optusnet.com.au/squid_80/xvid64.zip) or this (http://ffdshow.faireal.net/mirror/XviD/XviD64-setup.exe).

squid_80
15th May 2008, 03:35
The problem here is Koepi's installer is creating the start menu shortcuts using system32 hardcoded, when it should be using something like %sysdir% in the install script (depends on installer/version). You'll have to right-click each shortcut, choose properties and correct the target.

Perfect_Form
15th May 2008, 20:22
I changed the start menu shortcuts to the sysWOW64 directory, and it works fine now. Thanks!

Perfect_Form

clsid
17th May 2008, 01:25
Koepi should replace {sys} with {syswow64} in the [Icons] section of his InnoSetup script. {syswow64} is the correct constant for the 32-bit system directory. For some script sections, such as [Files], {sys} will work as well because of the automatic redirection that is done by Windows.