Optimization of the BIOS
The last submenu with some importance, although in this case only for a pair of options:
Parallel Port Mode: it will have to be exact to the type of printer or other devices of parallel port that we have (scanner, ZIP...). The normal thing EPP is or in any case ECP, but it should never be elected "either " "Standard" or "SPP", the speed would be much minor.
IDE Prefetch Mode, which must be activated (Enabled) for an ideal functioning. This option is not in many computers.
Often we light the computer and see how there happen some valuable seconds of our valued time with a reiterative checkup of the memory, the detection of hard disks and cross-checks of keyboard or disk drive.
Well, this will be the last thing that we will be able to optimize, the necessary time until the awaited logotype of Windows XX appears on our screen, or the screen in way text that gives us the welcome to the version 2.2. X of Linux (does anybody use BeOS or Solaris?: what is what appears at first?, he would remain an onlooker to include it in next reviews of the article).
In the submenu STANDARD CMOS SETUP we find some interesting options. If it has tried to light the computer without connecting a keyboard, it will have noticed that it gives an error. This takes place because there exists an option called "Halt on:" that there indicates to the BIOS that must verify certain things and stop in case it finds some error (normally in disk drive and keyboard). If we say "not Errors" to him it will not stop before any error.
Also we observe on the same screen four lines with the channels IDE. Normally they are in "Edict", with what whenever we start the computer, the BIOS will have to detect our hard disks. The correct option happens for deactivating the detection in the channels that have no hard disks (selecting "None"). As for those who have hard disks, if we do not want to insert his characteristics of manual form (there is no need), we can resort to the option IDE HARD DISK DETECTION of the principal menu, which will detect our hard disks and will place the correct options. Only there exists a case in which the option Edict turns out to be advisable (practically necessary), and it is when the disk drive is extraíble.
Finally, we can reduce the number of tests of memory that realizes the system on having started, selecting "Enabled" in the option "Quick Power On Self Test".
You try yield
Since it shows a button; we are going to verify if our optimization it has been worth while. For it we will compare the values for defect and the optimization that we obtain with the option PRAISE TURBOCHARGER DEFAULTS. Also, also we will measure the yield on having changed the basic configuration of CAS 3 to CAS 2. The used program has been Sandra 2000, and the PC a "simple" AMD K6-2 with memory PC100.
Since we see, the activation of an option or other one can lead us to obtaining unexpected values. The best thing is to be proving the most correct options up to obtaining the ideal one. Of course, we verify that the values more optimizables are in those specific functions of the chipset of the motherboard, which are those that the BIOS controls. Therefore, the most affected values will be those related to the memory traffic.
On the other hand, we must not rely on any of the values of the hard disks, since they can present anomalies due to the proper nature of the operating system, although we have deactivated all the resident programs that one has been able.
An important characteristic that we observe is the important yield increase simply selecting for the memory CAS 2 instead of CAS 3: 5 more % of band, something really spectacular for the only change, which can come up to more 14 % if we fit simultaneously other values. It is a sorrow that the memory PC133 "normal" working to 133 MHz CAS 2 supports only... but in return, if it has memory PC100 that CAS 2 supports, perhaps he does not need PC133.
We have already seen that it does not turn out to be so complicated to optimize our BIOS. Also, the fact that the article is based on a BIOS Award should not have the minor importance, since the rest of manufacturers has very similar configuration options.
Of course, it is very advisable to measure the yield of our system before realizing the modifications, in the opposite case we will not know if we have improved our yield or on the contrary we have worsened it.
And although the yield difference normally will not be very big, except perhaps in programs to which it affects very much the breadth of memory as those of renderizado and any games, the important thing is that he will know more on his system...: and that nearly that improves the yield, will be free!