I was taking a look at this teacher(a photography mentor to be exact)'s computer and realized that his BIOS was not set up (Asus P4P800 + P4 Northwood which is same as mine):
HDD was NOT running in 32 bit Transfer Mode (160gb Maxtor),
CPU+RAM wasn't in Turbo mode to gain safe extra boost.
RAM was running in SPD value mode
and so on.
Well, I changed the HDD to run in 32 bit Transfer Mode and set the CPU+RAM to run on turbo mode and didn't touch the RAM setting as I wasn't sure what kind of RAM was in the system.
Well, once I rebooted the system, it gave me the 'missing NTDR.whatever' error message. I remembered seeing that error message whenever my HDD went dead.
I was screwed or that's what I thought.
This guy hasn't backed up his data for a long time and there are tons of his works that just can't be replaced with anything else.
And of course, as I'm the one who f!@#ed up, I can't just say that he should've backed up his data.
Damn.....I was sitting there sweating and hoping that this is different than my past experiences.
I changed everything back to what it used to be and it booted up fine.
After that, I didn't even want to change anything as I just got sick of it.
Well, I'm now wondering what'd be the possible cause.
I'm thinking it must be the HDD being in 16bit mode when it was partitioned and formatted. Or am I right?
HDD was NOT running in 32 bit Transfer Mode (160gb Maxtor),
CPU+RAM wasn't in Turbo mode to gain safe extra boost.
RAM was running in SPD value mode
and so on.
Well, I changed the HDD to run in 32 bit Transfer Mode and set the CPU+RAM to run on turbo mode and didn't touch the RAM setting as I wasn't sure what kind of RAM was in the system.
Well, once I rebooted the system, it gave me the 'missing NTDR.whatever' error message. I remembered seeing that error message whenever my HDD went dead.
I was screwed or that's what I thought.
This guy hasn't backed up his data for a long time and there are tons of his works that just can't be replaced with anything else.
And of course, as I'm the one who f!@#ed up, I can't just say that he should've backed up his data.
Damn.....I was sitting there sweating and hoping that this is different than my past experiences.
I changed everything back to what it used to be and it booted up fine.
After that, I didn't even want to change anything as I just got sick of it.
Well, I'm now wondering what'd be the possible cause.
I'm thinking it must be the HDD being in 16bit mode when it was partitioned and formatted. Or am I right?