View Full Version : DVDshrink 3.0 beta 5 problem: HD capacity????
mikewillnot
17th December 2003, 23:25
Weird problem, don't think it's a bug. I'm shrinking a movie that is ripped to an 85gb external hard drive with 35 gb unused capacity. At the 92% point in the shrink operation, the program burps out an error to the effect that the operation could not continue due to insufficient space on the target drive (it might say folder; don't remember). I know it's pointed to the right drive, and that the drive has tons of empty space. ANY ideas as to what might be going on would be greatly appreciated. Thanks.
mrbass
18th December 2003, 00:00
only thing I can think of is something like norton undelete or systemworks.
Kedirekin
18th December 2003, 01:33
On rare occasions I've seen disk drives report incorrect free space. In fact, IIRC Smart Ripper used to leave my old PC several GB off on a fairly regular basis (though I don't really know if it was Smart Ripper's fault, or if my PC was just hinky - Windows 98 ya' know).
Running a disk scanning utility might be a good idea.
[Aside: Does XP even come with a disk scanning utility?]
Pooka
18th December 2003, 15:32
yes for XP: go to command prompt, change to the drive in question, then type CHKDSK /F (hit enter). You may be required to reboot to complete the check disk operation. I fthis is the case, check event viewer at start-up for the WINLOGON entry, ths will summarize chkdsk's findings. note, you must have administrative privledges to run CHKDSK.
Tonio Roffo
18th December 2003, 18:07
Spoken like a true sysadmin :)
You must be in the business somewhere? :-)
Pooka
19th December 2003, 16:22
:) Indeed I am sir. Director of IT for a popular fast-food chain. Hope CHKDSK helped with your issue.
mikewillnot
19th December 2003, 16:44
I'm not sure what caused the problem, but it's gone. Did the disk check thing, some other diagnostics, rebooted, and problem gone. Thanks, all. I must say, I've had persistent complaints about that pesky Norton Protected Trash program, which seems impossible to get rid of or dislodge, and often ties up disk space.
b0b0b0b
20th December 2003, 07:16
Glad to hear it's solved, but in case you ever want to know which process is writing to what file and where, have a look at filemon at sysinternals.com.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.