I've read on this forum that there's a 3.8 beta BIOS around that fixes large hard drive support for this BIOS - unfortunately, Microstar tech support seems to be ignoring my e-mails.
Can anyone point me towards a possible alternate location for obtaining this BIOS?
40GB - MS-5169 version 3.7
-
- The Hardware Archivist
- Posts: 6287
- Joined: Wed Mar 20, 2002 7:11 pm
- Location: Netherlands
- Contact:
version 3.83 now online here:
http://www.elhvb.com/mboards/msi/bios/MS-5169.rar
you need winrar to unpack it:
http://www.rarlabs.com/download.htm
http://www.elhvb.com/mboards/msi/bios/MS-5169.rar
you need winrar to unpack it:
http://www.rarlabs.com/download.htm
edwin/evasive
Do not assume anything
System error, strike any user to continue...
Do not assume anything
System error, strike any user to continue...
-
- BIOS Guru
- Posts: 3153
- Joined: Thu Mar 21, 2002 8:16 pm
- Location: Near Hannover (CEBIT) Germany
- Contact:
I have reports of working 80Gb HDD with this Bios so either you have done somethign wrong or a compatibility problem with your HDD .
Please Clear CMOS and then load Optimal/Performance Settings in Bios .
Try IDE HDD Autodetect in Bios
If this does not work enter HDD parameters manually
Please Clear CMOS and then load Optimal/Performance Settings in Bios .
Try IDE HDD Autodetect in Bios
If this does not work enter HDD parameters manually
I haven't tried wiping the CMOS totally, I can indeed give that a whirl and see what happens. I will also try the 'optimal parameters' menu option as well.
Manually entering the parameters didn't work - the BIOS still seems to query every IDE device during the initial POST and displays info about them - i.e. "FUJITSU blah blah blah, S.M.A.R.T. capable and status OK" - at this point the boot times out for 30-40 seconds and an error is reported (after which booting can continue, minus the drive of course).
I know the drive works as I plugged it into my primary PC in order to actually get the parameters. The Fujitsu drive I tried came out of my primary PC just for a test.
Tried a new cable already - no dice.
What I might also test is seeing if the drive works on the other channel - it just dawned on me that whatever caused the original drive to die may have also damaged that channel (smacks self in forehead)...
Manually entering the parameters didn't work - the BIOS still seems to query every IDE device during the initial POST and displays info about them - i.e. "FUJITSU blah blah blah, S.M.A.R.T. capable and status OK" - at this point the boot times out for 30-40 seconds and an error is reported (after which booting can continue, minus the drive of course).
I know the drive works as I plugged it into my primary PC in order to actually get the parameters. The Fujitsu drive I tried came out of my primary PC just for a test.
Tried a new cable already - no dice.
What I might also test is seeing if the drive works on the other channel - it just dawned on me that whatever caused the original drive to die may have also damaged that channel (smacks self in forehead)...
The drive is being detected and is working now!
The secondary channel apparantly is blown, as the drive had no detection problems as soon as I connected it to the primary channel. This explains why the 10GB drive I tried also wouldn't work when I connected it up - again, it was on the secondary channel.
Thanks for providing the BIOS!
The secondary channel apparantly is blown, as the drive had no detection problems as soon as I connected it to the primary channel. This explains why the 10GB drive I tried also wouldn't work when I connected it up - again, it was on the secondary channel.
Thanks for providing the BIOS!
Good to hear you got it working.
Just monitor that system carefully. I always assume that if I can identify a fault on a component, that component may have other faults which I do not know about, and those other faults may or may not be causing a problem (depending what the faults are and what you use the system for).
Any problems you have with software that you are unable to resolve may be due to other problems with that main board.
Just monitor that system carefully. I always assume that if I can identify a fault on a component, that component may have other faults which I do not know about, and those other faults may or may not be causing a problem (depending what the faults are and what you use the system for).
Any problems you have with software that you are unable to resolve may be due to other problems with that main board.