PCMech Forums - View Single Post

stephenahayes · 06-05-2001, 06:15 PM

Problem may be with BIOS chip or other part of MB not WIN2000, when I got this KA266 to boot up, two 30G HD's IBM deskstar, on w2000 compatible list, they (type) are detected by Bios, but only as 2114 MB , auto detect numbers come up as 4096 Cyl, 16 Head, 0 precomp, 4095 Landing Zone, and 63 sector,
Numbers from HDD case are 16383 Cyl, 16 HD, 63 Sec
when W2000 pro setup is ready to create partitions, it only shows 2016MB of unpartitioned space for each drive. I have Sys Admin book, etc about disk mgmt to design partitions, but no mention what to do if size does not match, or examples of numbers to expect to see, I tried using Bios to manually enter Cyl, HD, Sect info about the hard drives, save and exit, but next boot with w2000 still does not see more than 2016MB. It appears BIOS recognizes hard drive label, but not contents. This MB was delivered with BIOS chip in backward which I found during troubleshooting, maybe chip did not survive completely intact.

06-05-2001, 06:15 PM	#4
stephenahayes Member (3 bit) Join Date: Jun 2001 Location: herndon, va Posts: 7	Problem may be with BIOS chip or other part of MB not WIN2000, when I got this KA266 to boot up, two 30G HD's IBM deskstar, on w2000 compatible list, they (type) are detected by Bios, but only as 2114 MB , auto detect numbers come up as 4096 Cyl, 16 Head, 0 precomp, 4095 Landing Zone, and 63 sector, Numbers from HDD case are 16383 Cyl, 16 HD, 63 Sec when W2000 pro setup is ready to create partitions, it only shows 2016MB of unpartitioned space for each drive. I have Sys Admin book, etc about disk mgmt to design partitions, but no mention what to do if size does not match, or examples of numbers to expect to see, I tried using Bios to manually enter Cyl, HD, Sect info about the hard drives, save and exit, but next boot with w2000 still does not see more than 2016MB. It appears BIOS recognizes hard drive label, but not contents. This MB was delivered with BIOS chip in backward which I found during troubleshooting, maybe chip did not survive completely intact.