Unable to delete Movies? 100% CPU in explorer?

[psylence]

Been having some problems for a few days having explorer peak to 100% cpu, pissed me off big time and it turns out it was a bad movie file, go figure.

This also seems to fix my occaisional problem with not being able to delete certain movie files, usually AVIs that are incomplete.

Explorer tries to preview dimensions, bitrates etc. And a reg hack to disable that, ending the lock on the file and stopping the CPU usage/mem usage.

http://www.windowsxpuser.com/forums/vie ... 11&start=0

Has info from suprisingly dumb sounding people but one managed to find a fix , the reg key is
HKEY_CLASSES_ROOT\\SystemFileAssociations\\.avi\\shellex\\PropertyHandler

Delete the default value (it gets replaced automatically w/a null) and viola.

Haven't had any trouble deleting media files since nor do I have the CPU issue. Haven't seen anyone post a definitive fix here, but if it has been feel free to nuke this post.

Fixing the first real problem I've had with XP managed to fix my only gripe as well, Merry Christmas to me.

[Fuzzy]

smooth... I had always resorted to safe mode

[aerogems]

And the rest of us who are able to think outside the box a bit, just open up a DOS prompt window, and delete the file that way.

[Nerð]

smooth... I had always resorted to safe mode

And the rest of us who are able to think outside the box a bit, just open up a DOS prompt window, and delete the file that way.

I have had a situation or two where neither of those individually solved the problem, but safe mode command prompt only was the way to go. If a file is deemed "in use," if you can't delete it in Explorer then you can't delete it from a cmd window either.

One newer solution I saw recently, can't remember which thread or who said it, was to use taskmgr to kill the explorer.exe process, then run a cmd prompt to delete the file, and relaunch explorer.

[Fuzzy]

And the rest of us who are able to think outside the box a bit, just open up a DOS prompt window, and delete the file that way.

That hasn't worked for me before =/

[psylence]

And the rest of us who are able to think outside the box a bit, just open up a DOS prompt window, and delete the file that way.

Please, please tell me you're not an idiot.

Oh wait, even if you did it wouldn't matter.

My God, could you even begin to knock down your wall-o-faggotry and begin to think like a normal person?

Who the FUCK wouldn't try that? Who wouldn't try any of the vast amount of ways to delete a file before assuming something is wrong?

Hey, lets play the "here's what happens when you do that you fucking idiot" game:

C:\\WINDOWS\\Temp>rm test
rm: test: Permission denied

C:\\WINDOWS\\Temp>del test
C:\\WINDOWS\\Temp\\test
Access is denied.

Pretty fucking simple. Even the Unix port of rm to Win32 plays by the rules and knows the file is locked.

I almost want to change majors to Psychology just so I can understand how someone could be so consistantly idiotic.

And now on with your regularly scheduled helpful thread.

[psylence]

smooth... I had always resorted to safe mode

And the rest of us who are able to think outside the box a bit, just open up a DOS prompt window, and delete the file that way.

I have had a situation or two where neither of those individually solved the problem, but safe mode command prompt only was the way to go. If a file is deemed "in use," if you can't delete it in Explorer then you can't delete it from a cmd window either.

One newer solution I saw recently, can't remember which thread or who said it, was to use taskmgr to kill the explorer.exe process, then run a cmd prompt to delete the file, and relaunch explorer.

You tried the above key deletion and it didn't help?

If a general file is deemed in use the kill explorer method may work, but it never worked for my corrupt video files. Regardless it would not delete, even in a different shell!

Dunno about other files though, I've never not been able to delete other files, AVI's have been my only pain and it's over, shit I didn't even have to log out or re-start explorer, as soon as that registry key was gone I could delete the file.

[pussykatz]

And the rest of us who are able to think outside the box a bit, just open up a DOS prompt window, and delete the file that way.

Please, please tell me you're not an idiot.

He's not an idiot, Windows is just stupid. Believe it or not this approach works sometimes. I've also managed to pull off weird things using SUBST (a file on a SUBST-ed drive can't be deleted, I just SUBST/d and re-SUBST it and then delete it)

[Nerð]

to clarify, I was saying the two methods I had quoted were not universally going to work.

One thing that occasionally worked was right-clicking the movie and obtaining its Properties. This would consume vast amounts not of CPU, but of RAM, and also time: up to five minutes in some cases. However, once the properties had been loaded, then I was able to delete the file.

But yeah, sometimes that didn't work. I'll have to try that key sometime.

[aerogems]

And the rest of us who are able to think outside the box a bit, just open up a DOS prompt window, and delete the file that way.

Please, please tell me you're not an idiot.

Oh wait, even if you did it wouldn't matter.

My God, could you even begin to knock down your wall-o-faggotry and begin to think like a normal person?

Who the FUCK wouldn't try that? Who wouldn't try any of the vast amount of ways to delete a file before assuming something is wrong?

Hey, lets play the "here's what happens when you do that you fucking idiot" game:

Pretty fucking simple. Even the Unix port of rm to Win32 plays by the rules and knows the file is locked.

I almost want to change majors to Psychology just so I can understand how someone could be so consistantly idiotic.

And now on with your regularly scheduled helpful thread.

Please please tell me your not a fucking idiot. You didn't even try the -f flag for rm! Christ, what the hell do you expect? If it doesn't work the first time, try rm -f, and if that doesn't work, you don't have permission to access the file.

But still, what the hell do you expect? Porting means you make it work on that operating system, meaning you have to abide by whatever rules might be in place for that OS. If there's a bug in Windows that prevents file locks from being removed properly, what the hell do you think a port of rm is going to do that the del command can't do? They both will pretty much call the same kernel function to remove the file. If you run into the bug where the OS doesn't remove the file lock, you're going to have a problem no matter what program you try and use to remove the file.

I'd ask you if you'd like to try the idiot game again, but it looks like you've mastered that pretty well all on your own. You have become a master of idiots, and there's little I could teach you for you have surpassed me in how to be a successful idiot. I humbly bow down and recognize the idiocy that is you.

[EasyE]

Anyhow... does changing this reg key have any other side effects to it, ie not being able to view item properties correctly etc?

[psylence]

Anyhow... does changing this reg key have any other side effects to it, ie not being able to view item properties correctly etc?

Never even thought about that but yeah I just tested it and apparently it does prevent you from being able to check properties of the file. Could be annoying for some I guess, but it's worth the trade for me.

I would assume similar problems like thumbnailing and stuff wouldn't work but I doubt many non-geriatric people view their files that way.

[psylence]

Please please tell me your not a fucking idiot. You didn't even try the -f flag for rm! Christ, what the hell do you expect? If it doesn't work the first time, try rm -f, and if that doesn't work, you don't have permission to access the file.

lol holy shit dude, --force just prevents prompting, it's not like an "all-powerful annihilate flag" or something...

But still, what the hell do you expect? Porting means you make it work on that operating system, meaning you have to abide by whatever rules might be in place for that OS. If there's a bug in Windows that prevents file locks from being removed properly, what the hell do you think a port of rm is going to do that the del command can't do? They both will pretty much call the same kernel function to remove the file. If you run into the bug where the OS doesn't remove the file lock, you're going to have a problem no matter what program you try and use to remove the file.

Umm, so basically you just admitted that the bug locked the file and the command line versions of file deletion make no difference. Thanks, that's what I wanted.

The Windows port of rm plays by the rules of Windows, which shows it's a pretty good port.

I'd ask you if you'd like to try the idiot game again, but it looks like you've mastered that pretty well all on your own.

Tried it out of curiousity, no change (surprisingly, I mean man, it's -f for God's sake it should take out 1/2 my hard drive). Any other skeleton-key command line flags to try? Or can you realize it doesn't work?

You have become a master of idiots, and there's little I could teach you for you have surpassed me in how to be a successful idiot. I humbly bow down and recognize the idiocy that is you.

Heheh that's good shit sugar, try chiming in sometime when you can actually be correct and contribute next time, thx.

Sorry 'bout this little spiff, but we all know Aerogems.

[Russ]

In before I lock!

The information has been posted. This has gotten to personal attacks. Knock it off.

-=Russ=-