R
Rod Speed
More likely the diag is accessing it directly.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Help me keep this drive working long enough to rescue data from it...
More likely the diag is accessing it directly.
P
Pennywise
More likely the diag is accessing it directly.
Well same thing thru INT 13
http://en.wikipedia.org/wiki/INT_13
R
Rod Speed
Well same thing thru INT 13
Nope, not the same thing at all.
I know what it is.
P
Pennywise
Nope, not the same thing at all.
I know what it is.
I'm not going to chase this one down one way or the other.
Surfice (SP?) to say the diagnostic program access's the drive
differently.
F
Fred Tehbot
guffed in said:Nope, not the same thing at all.
No, legally we can't do that. [Flight attendant refusing to help a woman
(weak from a long illness) put her suitcase in an overhead rack]
I know what it is.
Does anyone else know what it is?
F
Folkert Rienstra
I still have no idea what kind of drive failure would result in this
behavior. I'm guessing maybe the drive had become incapable of handling
lots of requests at once.
Most likely That the diagnostic program is accessing the drive at the
bios level,
Like the bios won't work it as hard as an OS driver will.
Thanks for that superfluous proof that you and babblebot don't have a
single clue.
and your not.
And can't even manage to work out who the OP is here.
P
Pennywise
Folkert Rienstra said:Like the bios won't work it as hard as an OS driver will.
Thanks for that superfluous proof that you and babblebot don't have a
single clue.
Who's hard drive isn't working.