Joel <Joel@NoSpam.com> wrote
> Rod Speed <rod.speed.aaa@gmail.com> wrote

>>>> I downloaded, installed, and looking at the report right now.
>>>> I haven't found any option to do any specific test but just run
>>>> and check the report.

>>>> - Computer Summary

>>>> Drive C: 100GB (93GB)

>>>> - Storage (Local Drives)

>>>> Drive C: = 57498MB (used 17G, free 40GB)

>>>> Hahaha even Everest gives me 2 different reports <bg>

>>> Some correction here. Everest reports 3 hard drives

>>> - Computer Summary

>>> 1. 100GB
>>> 2. 250GB
>>> 3 250GB

>>> - Sorage (Local Devices)

>>> 1. Drive C = 56GB

>>> So, Everest does detect the 100GB drive, but like
>>> Win XP it doesn't know where the 44GB's gone.

>> Likely the partition table on that drive has got scrambled,
>> maybe due to a problem with the drive, but more likely
>> due to a problem outside the drive. The Everest SMART
>> report should show whether the drive itself has a problem.

> That's what it seems happening, and the whole thing
> is so weird that I have never seen before. Lets see

> 1. First the system started locking up for about
> 3-4 days (or 4-5 day?) then won't boot

Thats likely when the partition table got stomped on.

> 2. After the first several locking up it gave the option
> to press F1 to continue and it ran for few hrs.

Some bios will do that if it gets confused about the
cpu params for some reason, essentially gets you to
confirm that the cpu params are appropriate with F1.

> 3. CMOS still recognize the 100GB but changed from Master to Slave

Thats the really weird bit. I meant to suggest checking the
drive jumpering before and managed to forget to do that.

If both drives arent correctly jumpered, quite a few pairs will come
up fine even with incorrect jumper settings. Its possible that with
incorrect jumper settings you might get a different result on some boots.

The other possibility is a flakey cable with the drives jumpered for cable select.

Another obvious possibility is either a flakey jumper itself, too loose,
or a dry joint or cracked trace associated with the jumpers on one drive.

> and won't boot

That may just be due to either the bios now attempting
to boot the wrong drive once the master/slave stuff has
changed, or due to the relatively complex NT boot process
getting confused by the master/slave stuff changing.

> 4. After I replaced the dead fan of the
> video card the system works again,

I bet that's a coincidence and whatever flakeyness caused
the master/slave stuff to change changed back again and
would have done that even if you hadnt changed the fan.

> but the 100GB drive becomes 56GB.

Likely thats just a damaged partition table and may well
have happened earlier, when it would no longer boot.

> Everest and CMOS still recognize 100GB but not Windows.

Because the partition table is damaged.

> Also, Everest recognizes as 100GB drive but also report 56GB total.

Because it gets the data from the drive itself, and from the partition table too.

> I checked (a little) drive C: to find any strange folder or file
> (since I just reinstalled Win XP few weeks and only use this for
> Windows so don't have lot of junks) and didn't find any, I also
> SORTED by SIZE hoping to detect easier but can't find any large file
> either.

I bet its the partition table thats the problem.

> But didn't check very closely so I am not 100% sure,
> so right now partition is the only thing left ... but still
> can't figure out how or what can change the partition

Likely that happened when the master/slave changed.

> (but seem like it did fool the CMOS about the Mster/Slave ...
> but how it changed them back to normal??????).

You could certainly get that with something intermittent in what determines
the master/slave, the jumpering or bad cable if cable select is used.

> It's just so weird <bg>

You should put heaps of garlic into the case and drive a
stake thru its 'heart' at midnight on a night of the full moon |-(