Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: wrag on January 01, 2009, 08:06:13 AM
-
got a film file that failed to write correctly?
Discovered it when I was de-fragging drive.
Says I have about 7 mg that defrag wont touch?
Tried deleting the file and moving the file and tried accessing the file and says "Cannot delete file: Cannot read from the source file or disk."
Keep getting this "Cannot read from the source file or disk."
So what is the fix?
This is a Sata drive BTW.
Windows XP
-
Sounds like a hard error on the disk and XP is locking it out to prevent the operating system from crashing.
-
any suggestion as the drive is still under warranty?
-
A low-level format normally takes care of those bad sectors as virtually all modern hard drives have the ability to swap out bad sectors due to a number of "spares" available in the drive.
The drive should have come with a low-level formatter. If not, one should be available from WD's WEB site. If they do not provide a low-level formatter, then I would never own a WD drive to begin with. All drives can develope errors over time.
If a low-level formatter is not available, the only recourse is the Microsoft partion formatter, which might not catch the errors. If they are hard errors, it will catch them, but it usually misses soft errors that the low-level formatter should catch.
-
Solution ?? http://blog.dotsmart.net/2008/06/12/solved-cannot-read-from-the-source-file-or-disk/
-
This did it for me...
http://ccollomb.free.fr/unlocker/
gonna try a defrag later to be sure but used the above and deleted it.
-
You do realize that if that area is a bad disk area, you just delayed the inevitable and potentially created more problems for yourself?
-
You do realize that if that area is a bad disk area, you just delayed the inevitable and potentially created more problems for yourself?
yep if it keeps happening I'll stop fixin it BUT read this...
http://blog.dotsmart.net/2008/06/12/solved-cannot-read-from-the-source-file-or-disk/
from dentin's link, explaining how it MIGHT have happened, and followed it to the unlocker link from there.
Used it and the file was deleted and defragged so.....
Gonna see if it's fixed and stays fixed.
If it is as the link describes then...
Hope it's not a a new AH film bug?
If it's a bad disk area and not as the link described then will try the low level thing later.
Thanks for all the replies!
-
If you wipe out the file name provided when you save the film, but do not give the film a name, then it could possibly create a file with an illegal name.
HiTech/Sudz is going to check on this.
-
If you wipe out the file name provided when you save the film, but do not give the film a name, then it could possibly create a file with an illegal name.
HiTech/Sudz is going to check on this.
Thank you Sir!
And it is possible that I did what you described inadvertently while hurrying to reup....
-
Nope. It would have required an effort on your part as we always supply a legal file name. You would have had to wipe out the file name and then hit the ok button to save it.
-
Nope. It would have required an effort on your part as we always supply a legal file name. You would have had to wipe out the file name and then hit the ok button to save it.
YEP :O
I Might have done it even so!
In a hurry to reup into a good fight and....
I MIGHT have wiped file name and hit OK then remembered I needed to type in a file name?
BUT the file did have a name it just had NO extension.
-
No extension is not something the game/film viewer is capable of doing. That is hardwired.