Forum Moderators: phranque
Why in the world does it frequently prevent me from editing or deleting files because they claim they are being used by other program?
What's probably happening is that the program you used to work with the file isn't properly releasing the memory blocks it needed when it worked with the files you are having problems with, I have this problem with WS_FTP and other smaller apps sometimes. The app programmers probably forgot to release some flag that tells windows it can now safely use the file, that's their fault, not MS's, often anyway.
This isn't XP's fault, it's the fault of the people who wrote the app running on xp, and it's not unique to Windows XP, 2000, and probably most other windows, do the same thing.
Windows is often blamed for things it has nothing to do with, and few think to blame the frequently shoddy software people run on Windows. I prefer to blame MS/Windows for the things they do do wrong/illegally, and give them credit for the things they do right, like making some of the sloppiest application programming in the world not crash it.
Then go back to "Applications" tab and press "New Task...". Type in "cmd", it will pring the the old "looks-like-dos" prompt.
Find the directory with the files you want to delete. Then delete the files.
You will need the following commands: cd, dir, remove.
After you are done deleting the files you don't want, press "New Task..." in the Windows Task Manager again and type in "explorer" and it will bring back the desktop.
the program is supposed to tell windows when it doesn't need the file anymore, sometimes they don't, but almost always when you fully shutdown the program all the memory is released, the file flags are switched to available, or however windows does it, except for when something like NS 4x crashes, then you often have to reboot...