On the last years i have had some some problems with my hardrives
what is happening is that i can get a system tray message at random time whit this cryptic message
"a delayed writing failed" (mine is a swedish message so i can't the tempus for write? but i hope you see anyway)
it was impossible to
save all data for the file E:\ S mft(dollar tag ove the S) (doesnt sound to good)
some seconds after
"a delayed writing failed"
it was impossible to save to save all data for E:\P2P Temp\Winmx.exe
Winmx has ALLWAYS been active when this hardrive failure occurs and i cant neglige that any longer
this has happend 3 times this year..2 times this last week
my hardrive is then slowing down. dies and dissapear from windows explorer after restart. and starts to kill damaged file-post segment with chkdsk.ootherwise it can't recognice the hardrive with,but most data survives
but now i have thinking moore on what involvment Winmx could possible have on this "writing errors" and perhaps peases is finally falling on place now i dont know?. you decide
i think of..first i have 500 incompletes perhaps moore active to Winmx. and some of thoose are perhaps 2 years old now, its old open nap server ivolved allso in the map
thei are from different Winmx versions, thei are from different computers accually.. i saved them on a cd from a different hardrive on another computer.thei have wandered again from different hardrives boot Sata drives and from the beggining IDE file systems
and i allso copyed them finally to my new computer again.(sata)
now when i hade this last crash. and i was trying to save my lost data, and i extracted thoose old Winmx temps again
for future use
but my data rescue program did not like thoose files. i dont know what "MTF record child's claimed parent mismatch aborting" message means but? but could thei be corrupted from all other hardrives different file systems somehow?..."delayed Writing on E:\" "Winmx.exe"(E:\) hmmm..
perhaps this is just bullshit stories i dont know?, i cant enough about computers to now for sure. but my only clue is that Winmx in this case causes the hardware crashes, its allways the sam patern
and allso important..1 year ago it was DC++ instead who unleashed a "delayed writing" on i atleast think it was another of my hardrives?..but the thread is thath P2P is ALWAYS involved avtive and it was old incompletes from Dc++ from other hardrives o used allso..i remember that now
And i have done a scan on my current hardrive with my hardrives own test program. and it shows no damaged sectors on the disc
is my fear right
? ore is it just somethin else causing this disc blackouts?