-Brading Software Message Board
+--Forum: Mp3/Tag Studio Support and Bug Reports
+---Topic: Access Violation at address xxx started by Pierre Roy
Posted by: Pierre Roy on Aug. 15 2002,16:30
After successfully downloading the tag studio, I first ran (successfully) auto rename on all my files. I then successfully ran auto tag on all my files.
Having changed my mind on the convention I wanted for no "_" between the titles and ".", I ran again auto rename, but deselecting that option.
I got the error message at 58% completion:
" access violation at address 00492e75 in module 'mp3tag_s.exe. Read of address 561069bf."
Since Tag studio hung up, I shut it down, and tried again, then yet again, but this time with auto tag, all with the same hanging results.
I then moved on to Browse and edit tags and encoding info, and it is here that I got the same message for my Sheryl Crow - Soak up the sun mp3 file.
I suspect that the file is somehow corrupt. I tried repairing it thru Repair mp3, but that didn't work.
I've tried deleting the file thru Windows explorer, but it hangs when I try, I've tried deleting thru dos (I'm running windows 98), but get a access denied message.
Am I correct in thinking the problem lies with the 1 file, is it anything that I did to create the problem, and how can I kill the file ?
pierre.roy@canadapost.ca
Posted by: Magnus Brading on Aug. 15 2002,18:11
This sounds to me like some kind of file system error (or possibly physical disk error, but not very likely) on your disk.
I would try to run a disk diagnostics program on the disk (including surface scan if the other scan types don't detect anything). I can recommend Norton Disk Doctor (in Norton Utilies), or Microsoft ScanDisk (I can't find ScanDisk in my Windows XP installation, isn't it included anymore, anybody knows?).
Can't you even delete the file if you boot in DOS mode (from a boot disk, or by using the Windows boot menu)?
In any case, it is highly unlikely that Mp3/Tag Studio has anything to do with causing this problem, it just crashes because some inconsistent program state is caused by the file error.
Posted by: Disposable Hero on Aug. 15 2002,23:50
I agree with Magnus that you should immediately run scandisk, and enable "bad sector checking". I don't have access to Win98, so I don't know the exact wording. You should look for and enable anything like "Automatically fix file system errors" and "Scan for and attempt recovery of bad sectors" - this is the language used in Win2000.
Warning: the following may take a long time to complete, especially on a larger drive. Let it run when you are not going to use the computer for a while, and do not interrupt the process.
To get to these options, I can only give you the Win2000 method, but it's similar in Win98 if I recall correctly. In any Windows Explorer window, right-click on the drive containing the bad file, click the Tools tab - ther should be a section titled "Error-checking". Click the "Check Now..." button and check both of the boxes, then click Start. When it's done, reboot.
If the file's still there after reboot, and you still can't delete it, I can give instructions for forcing that to happen
end