GIF Animater 5 - Crash on Startup - Initial Video I/O

[GoldenEagles]

I have read all the information here on this subject regarding this behavior where GIF Animator 5 crashes at start up, in Windows XP, at the point where it is processing initial video I/O, and I wanted to post some additional information.

The information in the sticky note above, regarding the contents of the "vio" folder, of course works.

In my case, the offending entry was "uvavi.vio", and I moved it to a temp folder. After doing that, GIF Animator 5 starts fine. But as viking notes, the program has no way to deal with ".avi" files once that file is removed.

Now, this approach does not get into the root problem, regarding the particular codec that is in conflict with "uvavi.vio".

I wanted to dig a little deeper into that.

On the error dialog, there is a line that reads: "For more information about this error, click here."

I clicked there.

On the next dialog, there was No module information displayed. That almost looked like a dead-end.

But there was a line that reads: "To view technical information about the error report, click here."

I clicked there.

The technical information is in a scrollable window.

I Scrolled through the list of active modules of which there were 93 listed, and I looked for the last reference to a codec file with the extenstion ".ax"

In my case it was "3ivxDSVideoEncoder.ax"

The first thing I tried, was the suggestion made by viking to unregister this.

Going to the Windows Xp run function, I typed "regsvr32 /U 3ivxDSVideoEncoder.ax" (without the quotes)

This returned an error saying the library could not be found.

I did a google search on "3ivxDSVideoEncoder.ax"

What caught my eye, was that this is a file associated with Verizon Media Manager, which allows FIOS subscribers to watch videos from their computer on their TV. I have that installed, so I went looking for that under Program files on the c: drive.

I could see a "verizon" folder, and a "Verizon Media Manager" subfolder, and a "3ivx" subfolder. That looked like the right place.

In the "3ivx" subfolder I found "3ivxDSVideoEncoder.ax" and I changed the name to "3ivxDSVideoEncoder_old.ax"

I invoked GIF Animator 5, and it started, normally, with the exception that a information dialog popped up asking me some questions about the effort of GIF Animator to associate itself with FFDSHOW (or something like that) It said that GIF Animator was not listed on its white list or black list, and it said a lot of other stuff, and fortunately this dialog box had a timed count down to it, as I did not know what to do at that point, and it just disappeared, and GIF Animator 5 opened. And I immediately went to a folder where I have a few AVI files, and tried to load one, and it loaded successfully.

Well, problem solved, as far as GIF Animator 5 is concerned. Though I expect to see a problem if I want Verizon Media Manger to handle an AVI file. I will hope that it is smart enough to go look for another codec, as GIF Animator itself did.

I am wondering nevertheless, why this did NOT work - "regsvr32 /U 3ivxDSVideoEncoder.ax" Perhaps Viking could explain.

[VikingAnimations]

Windows may be looking in the Windows folders for the file, expecting it to be there. http://en.wikipedia.org/wiki/Regsvr32

Undo your renaming.

regsvr32 /U C:\Program Files\Verizon\Verizon Media Manager\3ivx\3ivxDSVideoEncoder.ax

If that doesn't work, go back to the fix you already found.

[GoldenEagles]

Thanks viking.

Per your suggestion, I restored the filename.

For the second part of your suggestion to work:

regsvr32 /U C:\Program Files\Verizon\Verizon Media Manager\3ivx\3ivxDSVideoEncoder.ax

It Required quotation marks around the file path and name:

regsvr32 /U "C:\Program Files\Verizon\Verizon Media Manager\3ivx\3ivxDSVideoEncoder.ax"

With this, I got a proper response:



And of course GIF Animator 5 will start up properly, and I can import .AVI videos successfully.

Again, GIF Animator 5 appears to know how to compensate for the missing "3ivxDSVideoEncoder.ax" or perhaps the windows registry has a list of .AVI compatable codecs, and once this is removed, it just goes to the top of the revised list? How does that work?

[VikingAnimations]

Don't know. Better off asking someone familiar with the inner workings of Windows. Your GA 5 works, smile and be satisfied.

[GoldenEagles]

I am indeed happy that GIF Animator 5 is again working on my Windows XP machine. Thanks for your Help. We appreciate your commitment to this forum.