Log in

View Full Version : Explorer Crashing Previewing AVI's


dar1us
26th August 2003, 00:51
Hi, I have perfectly valid AVIs with open fine and dandy like in media player classic. When ever I click on them, it causes explorer to crash.

This is under Windows 2000 SP4 w/hotfixes. Ideally, I would like to disable the preview.

Before I get yelled at, this is not the same problem that the windows xp guys are having trying to delete files that just wont go cos corruption causes explorer to crash on left click.

Ideally, prievew would go alltogether as it is useless to me and I am sure most as double-clicking the file takes a second to load (MPC).

Anticipating help,

Additon:
Oops, I completly omitted details, Windows 2000 SP4...
The codec I use is ffDShow and the files that fail to work are XVIDs, I use the libacodec in ffDShow... I remember reading somewhere that this is bad and I should select XVID. An (OT) explaination why wouldn't go a miss please.


harrison

Sirber
26th August 2003, 02:09
hihihi disable preview in explorer. Don't let windows taking over your computer!!! :scared:

dar1us
26th August 2003, 03:33
in explorer
tools > folder options > general > web view > use windows classic folders


I followed this to disable preview... problem is that I like preview, especially in control panel, network places... that kind of thing... I just want to disable the video/audio feature of it.

is it possible?


harrison

eMMo
4th September 2003, 09:19
During the last few days I encoded 10 episodes of a TV-Series, ripped from DVD. Most avis are correct without issues. Two of them however show the same pecularity as dar1us describes above. When I only select them Windows Explorer would crash immediately.

So, after this happening yesterday I thought it might be an encoding issue and did one of the problem files once again. But as I checked first thing today in the morning it shows the same behavior after the second encoding :(.

I use WinXP, Sp1 and encode with GKnot 0.28.5, XviD (XviD Koepi 24062003-1), mp3.

mic
4th September 2003, 14:58
A real guess, so please take it for what it's worth...

Based on a similar problem - not identical - *Might* have some success going through the codecs &/or filters installed in windows. This is because often windows uses whichever filters are there, regardless if one's more appropriate, or if different filters conflict. To find out if this sort of thing might be causing prob., might use something like the Analog X DXman app to see just what's installed & where, then rename the files or folders temporarily to see if the prob goes away.