|
|
|
|
![]() ![]() |
Oct 19 2006, 12:06 PM
Post
#1
|
|
|
S.P.A.M.S.W.A.T. Group: Members Posts: 814 Joined: 22-January 05 From: San Antonio, Texas (No, I'm not dumb. I just moved here...) Member No.: 2,284 |
I was upgrading some software and came across a corrupt file that halted the installation process. I went to see what was wrong with the file, and failed to manually delete it. I tried moving (cut&paste) it to another location, and the installation succeeded. However, the file is still on my drive, taking up a KB of space. I know that's not a lot, but where am I supposed to put it? In a folder created especially for all the corrupt files on my computer?
I've heard something about using the chkdsk utility to fix the problem. However, I am not sure on how to use this tool. Microsoft's documentation didn't make it clear... |
|
|
|
Oct 19 2006, 01:36 PM
Post
#2
|
|
|
Member [ Level 1 ] Group: Members Posts: 42 Joined: 1-September 06 Member No.: 15,660 |
Use Unlocker:
http://ccollomb.free.fr/unlocker/ It's an explorer extension. It calls itself automatically whenever the deleting process failed. It frees all the calls to the file, so you can delete it, but it does not work always (atleast for me) You can also choose if you want to delete the file after a reboot. But other than that its a pretty handy program |
|
|
|
Oct 19 2006, 02:46 PM
Post
#3
|
|
|
Way Out Of Control - You need a life :) Group: [MODERATOR] Posts: 1,980 Joined: 16-August 05 Member No.: 7,896 |
Booting on the Knoppix CD also helps.
You are under windows then, having less problems. You click on your Windows partition, choose mount, choose switch to write-enabled mode, go to your folder, choose your file and choose "delete". Probably the Linux file manager will have no problem deleting this corrupted file. The only reason I see for being really definitively unable to delete the file would be a physical corrupted sector on the disk, then, only a disk format would be able to recover the error. Regards yordan |
|
|
|
Oct 19 2006, 02:51 PM
Post
#4
|
|
|
Nenad Bozidarevic Group: [MODERATOR] Posts: 1,002 Joined: 7-November 05 From: Belgrade, Serbia Member No.: 9,500 |
If my memory serves me well, I have had the same problem some time ago. I can't remember exactly what helped, but trying to delete it in DOS mode seems like a good idea. Also, you might want to try booting Windows in Safe Mode and then deleting the corrupted file.
|
|
|
|
Oct 19 2006, 03:06 PM
Post
#5
|
|
|
Way Out Of Control - You need a life :) Group: [MODERATOR] Posts: 1,980 Joined: 16-August 05 Member No.: 7,896 |
QUOTE 've heard something about using the chkdsk utility to fix the problem. However, I am not sure on how to use this tool. Microsoft's documentation didn't make it clear... By the way, yes, there is a way you can use it harmless. Open a dos prompt window, and type "chkdsk c:" (or chkdsk d: depending if your file is on C: or D: or E:) It will tell you "you did not provide the /f flag, I will only look without reparing". No problem, let it look, and if it says "no errors", then chkdsk is not the solution. If it finds a problem, run it again with the /f option, like this : chkdsk d: /F sometimes it's useful, sometimes not. |
|
|
|
Oct 19 2006, 06:28 PM
Post
#6
|
|
|
Premium Member Group: Members Posts: 242 Joined: 4-August 05 From: Los Angeles Member No.: 7,624 |
Yeah I would probably just delete it from command prompt, but depending on what the file is you might have to go into safemode.
|
|
|
|
Oct 19 2006, 09:17 PM
Post
#7
|
|
|
Newbie [ Level 2 ] Group: Members Posts: 11 Joined: 18-October 06 Member No.: 16,665 |
If you are not confident with the command prompt or Linux, then you can try using GiPo@Utilities.
http://www.gibinsoft.net/gipoutils/index.htm GiPo@Utilities has a number of small programes within it. These include: * GiPo@MoveOnBoot - copying/moving/renaming/deleting files and folders on the next system boot. * GiPo@DirMonitor - monitoring changes in the file system. * GiPo@Mount - local folders substitution and local/remote drives mounting. * GiPo@Hardlink - UNIX-like (POSIX) hardlinks for NTFS creation. * GiPo@ReadTest - checking files and folders for read errors. |
|
|
|
Oct 23 2006, 05:09 PM
Post
#8
|
|
|
Way Out Of Control - You need a life :) Group: [HOSTED] Posts: 1,022 Joined: 2-August 05 From: Kapellen (Antwerp, Belgium) Member No.: 7,585 |
There's a small catch on using linux. If you have windows installed on an NTFS partition then you should be very carefull with wath you do. Linux NTFS drivers are still very buggy when it comes to writing (deleting = writing) especialy when you write a lot of data. A small amount normaly should pose not too many problems, but it's best to try windows-based software first.
|
|
|
|
Oct 23 2006, 11:09 PM
Post
#9
|
|
|
NiGHTFoX - Hiding in the dark Group: Members Posts: 680 Joined: 3-April 05 Member No.: 3,584 |
Yeah I would probably just delete it from command prompt, but depending on what the file is you might have to go into safemode. It's always best to just go into safe mode. Then nothing will try to open the file for reading. That's what I like about Linux... it doesn't leech on to a file like that. [N]F |
|
|
|
Sep 25 2007, 03:55 PM
Post
#10
|
|
|
Newbie [ Level 1 ] Group: Members Posts: 0 Joined: 1-November 07 Member No.: 25,869 |
Thanx tommydanger 'Unlocker' did the job! Had this annoying avi that refused to budge in Safe Mode or via Command Prompt. Cheers.
-bigpaul |
|
|
|
![]() ![]() |
Similar Topics
|
Lo-Fi Version | Time is now: 6th September 2008 - 06:37 PM |