Don't shoot me.Īt any rate, if you know you should change the cables but haven't done so yet. which contradicts putting it in a paragraph all it's own that starts with "things I haven't tried". More often than you would believe, people will do exactly what you did there, but then come back to explain that they were saying that they DID change the cables. So you are saying that you haven't tried changing the drive cabling yet? Your use of the past tense there, the period after the word "finding", and leaving out either "I have" or "I have not" before the word "changed" makes it a bit ambiguous. changed the data cable and the PWR SATA cables. running Seatools in DOS such better for fault finding. There are things that I haven't tried yet. This seatools user’s guides don’t give me any help with this, I don’t understand the instructions in mkboot.txt that’s in the zip file.I'm pretty sure that you are going to comment back and apologize that you meant the opposite. Running that DOS kernel from the separate freeDOS package gotten from sourceforge works fine, so the problem must be in seatools for DOS rather than in my machine or my procedures. I see that the DOS source file is in the file ke2035asrc.zip included in the ISO but I don’t know where to put the files extracted from the zip to make a DOS-bootable CD.
But after rearranging the boot order, seatools for DOS won’t run my machine just loads Vista as usual. The download instructions say simply " download, burn, run." I’ve downloaded the ISO file (SeaToolsDOS223ALL.ISO) and burned it to a CD without trouble. But I’m having trouble setting up seatools for DOS. I gather from the seatools documentation that seatools for DOS might be a able to isolate the blocks. I’ve got an internal WD boot drive that’s showing bad blocks as reported by my disk maintenance apps, including seatools for windows. I don’t know in what forum this question would be best, I hope someone knowledgeable can address it here.
0 kommentar(er)
