> Connections are all ok. I dont think I hit any thing static while changing
> the hdd.
> I am trying to install xp in to the 160bg hdd using a cd. In the meantime
> the old hdd is been taken out during thr installation process. Well that's
> the plan but at the moment we cannot get past the POST.
> Fyi when I try to connect the old hdd(40gb) as Primary master, I cant get
> pass POST or I think at least there is no POST. What can I try next ////
> Thanks
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> "Paul" wrote:
>
>
>>bb202 wrote:
>>
>>>Suspecting that my hdd may be failing, ran a seatool test and it confirm that
>>>the hard disk is failing. So I decided to replace a new hdd from a 40gb to
>>>160gb hdd. As usual mount on the pc> power on> and it says
>>>checking system health ok>cpu id...> checking NVRAM...update ok> 262144kb
>>>and the pc just hang there. Some times it wil show an extra line "F1>Set Up"
>>>and then nothing doing. I try to change/reset the cmos jumper but to no
>>>avail. I event put back the original hdd, but its the same situation.
>>>Question is why is the mobo behaving this way?
>>>Details of mobo
>>>62-1001-001199-00101111-071595-v604v686-ga6940006-f
>>>
>>>and I suppose this pertain to the bios: 6VXC4X-6VXC7-4X-P F9
>>>
>>>With these I cannot reformat the hdd.Olease advice, thanks
>>
>>You could be installing a 160GB disk, on a motherboard
>>with a 128GiB/137GB capacity limit. My old P2B-S is like
>>that.
>>
>>In the past, if dealing with an IDE disk in a situation like
>>that, a person might use the "clip" jumper, as a test. The clip
>>jumper on an IDE drive, causes the drive to report a different
>>geometry to the BIOS, which will keep the BIOS happy. But doing
>>so, might mean you only get to use 32GB of your disk.
>>
>>A solution, is to get a PCI IDE card, such as a Promise Ultra133 TX2,
>>and connect the hard drive to that. That is a way of breaking the
>>capacity barrier (since the PCI IDE card is compatible with a later
>>version of the ATA/ATAPI spec). Then, it is up to your OS, as to
>>whether there are further capacity related issues. WinXP SP1 and
>>Win2K SP4 are prepared to handle >137GB disks, if the hardware is
>>capable.
>>
>>Seagate makes this document available, which discusses the many
>>possibilities.
>>
>>
http://www.seagate.com/support/kb/disc/tp/137gb.pdf>>
>>This is as close as I could get to a board ID. They may have
>>mistyped one character when they entered this in the database.
>>
>>
http://www.motherboards.org/tools/moboidtools.html>>
>>Gigabyte GA-6VX 62-1001-001199-00101111-071595-V694V686-9A694006-F
>>
>>Picture.
>>
>>
http://www.motherboards.org/mobot/motherboards_d/Gigabyte/GA-6VX/>>
>>Manufacturer - uses VIA VT82C691 & VT82c596 AGPset chipset
>>
>>
http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassValue=Motherboard&ProductID=1523&ProductName=GA-6VX>>
>>It'll be something from around that era. The capacity limit
>>is not documented that well, and I couldn't find any info
>>for that board.
>>
>>As for the motherboard behavior, you'd think that clearing
>>the CMOS (with the A.C. power plug pulled before using the jumper),
>>would return things to normal. There is a small possibility
>>the BIOS flash chip on an old board can fail (that is called
>>"bit rot" when it happens). The main body of the BIOS
>>is supposed to be protected by a checksum, and you'd
>>expect that to flag a bit rot problem. If you try to
>>reflash such a BIOS, to fix the problem, the
>>board may not survive the flash. In that case,
>>you may need to get a new BIOS chip, from badflash.com
>>or some other similar site. And you have to tell badflash.com
>>what BIOS file to use, so they can program that BIOS into
>>a new chip.
>>
>> Paul
>>