VOGONS


First post, by tokyoracer

User metadata
Rank Member
Rank
Member

Hi chaps.

I am having issues with a motherboard I aquired some months back (maybe a year now or so). It's a Gigabyte BX-2000 board with a rather handy "DuelBIOS" feature. Both had an older version on the chips that didnt allow Hard drives much above 20GB to be read but I tried installing two 80GB drives and it just hangs when posting (when it searches for them in the IDE). I can manually feed the BIOS the sectors, cylinders, and other bits but it will only address 8GB that way.

I did some research and found the latest BIOS update fixed this issue allowing 120GB and beyond so I gave it a go flashing onto the secondary BIOS (just in case it goes a-skew) and success! It detected the hard drives correctly but now after it posts past the IDE detection, it just goes to a blank screen with a blinking underscore curser top left of the screen and sits there.

I wonder if I might have a jumper set incorrectly or something but I can't say for sure since I am a bit lost looking at the .PDF manual. All the old threads I found about people having hard drive issues with this motherboard all suggest the person/people "just get a PCI IDE controller card" and not really fixing the solution (words to that effect anyway). Not to mention I don't actually have a PCI slot free currently! I'm not sure where else to go from here so I am curious if any gurus here might have any idea what might be at fault when reading IDE devices correctly and ultimately, booting past the posing process, hopefully to put 98SE on it. 😀

Thanks in advance.

Reply 1 of 4, by shamino

User metadata
Rank l33t
Rank
l33t

Have you ever seen this motherboard successfully boot an IDE hard drive from it's onboard controller?
Is the BIOS configured to boot a CDROM or floppy which you have provided, or is it trying to boot from one of the hard drives? It might be freezing up because of whatever's on the drive.

I don't have any great ideas, but for whatever it's worth, try simplifying the configuration as much as possible. Reduce to just one hard drive, and verify the master/slave/CS jumpering. For now I'd probably jumper the drive explicitly as master (and that drive should be at the end of the cable). If this doesn't help, move the cable to the other IDE channel.
Remove all but a single VGA card - something might be causing a resource conflict with the onboard drive controller. And if that doesn't help, try moving that VGA card to a different slot.
If you haven't already, make sure the drives work correctly in another machine.

Reply 2 of 4, by Zup

User metadata
Rank Oldbie
Rank
Oldbie

Some things to try:
- Clear all the CMOS values (using the clear CMOS jumper first, then the load default values setting).
- Make sure that your HDD is properly configured (= check all the jumpers) and empty. If it had a system previously installed, it may not be able to boot with your new computer (it happens when you switch CHS/LBA or RAID configurations).
- Try to boot from a Linux live CD (I use Puppy Linux or Knoppix), or from Hiren's Boot CD Windows XP. Then, try to access your HDD (and verify it via MHDD or Victoria). If it can see the contents, you're clear to install any new OS.

I have traveled across the universe and through the years to find Her.
Sometimes going all the way is just a start...

I'm selling some stuff!

Reply 3 of 4, by buyerninety

User metadata
Rank Newbie
Rank
Newbie

We assume that you have checked to verify the bios revision in the
first post screens, so you are certain that the 2nd bios chip has
been updated with the later bios (whose version you did not tell us,
and whether it is an AWARD bios).
You said it detects the (80GB) hard drives 'correctly' - does this mean
you can see the drive maker/model info (which you did not tell us) ?

Try connect (a single) 80GB drive using a 40 wire (not 80 wire) IDE cable.
Things to try if the above doesn't work;
I agree then proceed with previous advice; "Reduce to just 1 hard drive,
and verify ...jumpering...Remove all but a single VGA card...clear CMOS"
(for bios in 2nd Bios chip), and I would add have not more than 256MB
of RAM installed.
(If it is not too inconvenient, perhaps you could fdisk and format the
empty 80GB drive(s) to their full LBA size on another computer.)
_EDIT*{I think that if the 80GB drives have been previously fdisk'd and
_formatted in C/H/S, attempts to access the drives would fail using LBA
_(even when later using an updated 'LBA aware' bios). }
If the above doesn't work, then, using the 2nd Bios,
(Again, connect (a single) 80GB drive using a 40 wire IDE cable.)
in the Bios screens, try setting the mode to Auto or try LBA if such
exists. Try setting UDMA, if such exists.

If the above doesn't work;
Try fdisk and format one of the the 80GB drive to less than 64GB, but more
than 32GB size, LBA, on another computer, then connect that (single) drive
using a 40 wire IDE cable.

*(I'm really missing the 'strikethrough' code used on other
phpBB boards...)

Last edited by buyerninety on 2015-02-26, 22:20. Edited 5 times in total.

Reply 4 of 4, by RacoonRider

User metadata
Rank Oldbie
Rank
Oldbie

Might be completely useless information, yet the only time I had this problem was with bad daemon tools 3.47 installation. I know this program is often the reason for such a behavior. Just FYI.