OC AMD XP1600+ @ XP1900+ NO PROBLEM!

Voila moja konfiguracija:
AMD 1600XP+
Elite ECS K7S5A
RAM 2 X MICRON 256 SDR CAS 2
RADEON 8500 RETAIL(he he LE)
dodaten hladnjak za mamoplato
ventialtor vulcano 6
bla bla...
potem pejte na: http://www.ocworkbench.com/ecs/ al pa: http://forum.ocworkbench.com/ocwbcgi/ul...
dol dajte program chfsb(disketa)! In voila ste že zmagal, postopek je natančno opisan tle:
________________________________________________________________________
CHFSB FAQ (1)
Cheepoman and Mpapec

Q1: So what is Chfsb?
A: The official ECS bios releases for the k7s5a only allow the standard 100 and 133 MHz front system bus (fsb) settings. Some time ago a few beta bioses which included several additional fsb settings were leaked. These are known as the "overclocking" or "OC" bioses. The programming for the extra fsb options is still present in the newer official bioses, but they were removed from the bios menu. Chfsb is a little program that makes it possible to use these extra fsb settings with all bios versions. You can download it here.
Q2: Which are these extra settings?
A: Currently Chfsb supports frequencies of 112/112, 124/124, 138/138, 150/150 and 166/166 (fsb/memory), in addition to the official ones: 100/100, 100/133 and 133/133.
Q3: What bios versions are supported by Chfsb?
All k7s5a bios versions starting from 010724, official and unofficial, are supported and automatically detected
Q4: How do I install/run Chfsb?
A: Chfsb can be run from DOS prompt under win9x/ME issuing "chfsb /i" command which offers multiple FSB speeds. After speed selection you have to reboot your system in order to activate the desired speed. Alternatively, if you prefer more frequent FSB altering chfsb (with full path) can be put on top of autoexec.bat and invoked by holding [shift] key during bootup. Linux/NT/XP users are advised to use it with DOS/win9x startup floppy disk.

Q5: Who wrote it? Is this a commercial program or anything?
A: Chfsb has been developed by Cheepoman and Mpapec, members of the ECS forum at Ocworkbench.com. Other members like cbozo, who had the original idea, udma and many others also contributed. It's 100 percent free for you to enjoy.

Q6: What does the program exactly do?
A: The battery on your motherboard has the only purpose of maintaning the CMOS, which is the small memory area where the BIOS stores its settings. When the computer is powered up the BIOS reads the CMOS contents and then it initializes everything according to these values. The good news is that not only the bios setup utility can read and write the cmos; a number of free utilities, such as cmostool, can do that too. As a result, all bios settings can be modified from outside the bios, if you know what bytes to overwrite and which values to put in. The bios has an internal list of valid values for each setting; some of them are labeled as "reserved" and cannot be selected in the bios setup utility, but they would be accepted anyway if read from the cmos. What Chfsb offers is the possibility of overwriting the fsb related bits with the suitable values for any these "reserved" modes.

Q7: Quite interesting. I would like to know all the details
A: Read here.
Q8: But, isn't this the same as CPUFSB does?
A: Not quite. CPUFSB directly addresses the PLL, which is the chip that provides the clock signals for the cpu, memory and pci/agp buses. This is nothing but pure overclocking: the pll increases the clock frequency and everything goes proportionally faster. In principle, the Chfsb approach is preferable as all the work is done by the bios, which not only initializes the pll to the desired frequency, but also has the opportunity to set all other internal timings properly. There are some other differences between both programs. CPUFSB allows to change the frequency on the fly, with the computer running. Also, it supports all the frequency settings that the pll can handle, including 142 and 146 MHz. ECS never programmed these modes in the bios, so they cannot be activated with Chfsb. CPUFSB has some problems, though. It hangs most of the time when changing from asynchronous modes (such as 100/133) to synchronous ones (like 133/133). Also, it may hang if to activate the desired mode the pci divider has to be changed (for instance going from fsb=138 MHz pci=34.5 MHz, pci divider=4 to fsb=150 pci=30, pci divider=5). A major advantage of Chfsb is that it doesn't care what operating system you have installed. It will run from the command prompt under win9x/Me, or the win98 compatibility mode of Windows XP. But if you have any other OS all you need is a simple DOS boot disk with Chfsb in it.

Q9: But, booting from a diskette is quite inconvenient. A Win98 boot disk takes ages to load.
A: To run Chfsb you don't need cdrom drivers or FAT32 compatibility. A good old MS-DOS boot disk will do. Please refer to the main k7s5a FAQ on how to prepare a simple boot disk. In addition, you don't need to boot from the floppy all the time. You only need to run Chfsb when you want to change the frequency to a "reserved" value. Once the new frequency is set, it will stay here every time you reboot, just like if you had set it in the bios.
Q10: So after running Chfsb all these new frequencies will be selectable from the bios?
A: No. When you next enter the bios setup utility the fsb frequency will be listed as "reserved". You can change it for any of the official ones (100, 133, 100/133), but then you won't be able to switch back to the unofficial one without running Chfsb again. Please note that you can change anything else within the bios without losing the fsb setting.

Q11: I tried the cmostool method and there were checksum errors or it didn't work at all. Can I use Chfsb?
A: These errors have been corrected. You should have no problem with Chfsb.

Q12: Wouldn't it be easier if someone modified the bios file?
A: Many people in this forum has tried to do so, and the conclusion is that with the tools that we have now, it can't be done. Amibcp 7.53 allows to change many bios settings, but those related to FSB remain hidden.
Q13: Still, perhaps ECS will release a new overclocking bios soon.
A: No way. ECS has stated clearly that there will be no more beta bioses.

Q14: Are you sure I can't damage my bios by using this program?
A: Absolutely. Chfsb does not modify the bios in any way, only overwrites the settings that are stored in the cmos. Although the terms "bios" and "cmos" are sometimes used in a confusing way they are different things. The cmos is just a tiny memory area, 256 bytes (although only 128 are used), and it is not even located in the bios chip, but in the Sis735 chipset.

Q15: I have set the frequency with Chfsb, but on reboot I only get a blank screen
A: Your system can't boot at the specified frequency with your current configuration. Clear the cmos by shorting the corresponding jumper for 30 seconds with the power cord unplugged.
Q16: I have tried 100/133 and performance is lower than with 100/100. What's wrong?
A: Sis 735 is known to be very fast in synchronous mode (when ram speed=fsb speed, for instance 100/100), but it doesn't perform very well in asynchronous mode. Therefore, 100/133 is way slower than 100/100. Similarly 133/166 is slower than 133/133. There is nothing wrong with your particular setup. Just stick to synchronous modes.

Q17: Is FSB overclocking safe?
That depends on how extreme you go. When the multiplier is raised only the CPU is stressed, but with the fsb also the chipset, memory and pci/vga cards have to be considered. For instance, for the pci cards a fsb of 150 MHz (pci=30 MHz) is safer than 147 MHz (pci=37 MHz). Usually components simply won't function if the selected frequency is too high for them, without permanent damage. But this is by no means a general rule. Be careful. In addition, severe overclocking means lots of heat, and heat is more likely to damage components than speed itself. Without proper cooling overclocking should never be considered . Having said that, the k7s5a was never intended to be an overclocker's board, so probably the overclocking that you will get from it will be quite moderate and relatively harmless.
Q18: When I overclock my athlon XP 1600+ to 138 FSB, it is detected as a regular Athlon at 1450 MHz. Is there anything wrong?
A: The bios detects the real CPU speed and then tries to match it with its internal table of CPU models. When your XP is set to 138 FSB (in fact, 137.3), it runs at some 1442 MHz, roughly halfway between an Athlon XP 1600+ (1400 MHz) and a 1700+ (1466 MHz). In the bios table 1450 MHz is a valid Athlon model and this frequency is much closer to your real 1442, so this will be the model selected by the bios to show at boot up. This is just cosmetic. Your CPU should work normally.
Q19: The overclocking bios works fine with me. Should I update the bios and use Chfsb?
A: Only the official bios releases are supported by ECS, and the latest versions have corrected many compatibility issues. However, if you don't need any of these fixes there isn't any reason for you to flash your bios. There is always the possibility that the bios modification that solved some other's problem might create a new one for you. Remember, if it isn't broken, don't fix it.

Q20: I can't possibly boot at 166/166, but I'm convinced my system should be able to. I've modified the board to raise the core, memory and chipset voltages, and lowered the multiplier. I've had moderate success at 166 with cpufsb. What's wrong?
A: Nobody has ever reported being able to boot at 166/166 with a k7s5a board. One possibility is that there be a bug in the bios programming for this mode. Remember, Chfsb only enables what's already programmed in the bios, so it can do nothing if the bios itself has errors.

Q21: 133/166 was present in the 010806 bios. Why can't I select it from Chfsb?
A: We weren't able to test it. If you can boot at 133/166 with that bios please contact us and we'll add it. Later bios versions don't include support for this FSB setting, so it can't be activated.

Q22: Will all the modes work on all bios versions?
A: Not necessarily. Some older bios versions had problems with the 100/133 setting and particular memory configurations, which was solved in a later revision. We cannot discard the possibility that similar issues exist with some of the hidden settings.

Q23: I have a 133 FSB rated processor which won't even boot at stock speed. I'm stuck at 100/100 MHz. How possibly could an overclocking program help me?
A: Most probably you will be able to run at 124/124. It's not perfect, but still it's 24 percent more than 100/100. Please do search the forum for help on your problem.

Q24: I know that the PCChips 830 LR is the same board as the k7s5a. Can I use Chfsb with a PCChips board/bios?
A: The current version of Chfsb doesn't have support for the PCChips board, but it could be easily added if any user would do the testing. Please contact us. In general, using a PCChips bios on the K7s5a is not recommended. While the latter bios versions seem to be ok, there were reports from users that 'fried' their ECS boards with earlier versions of the PCChips bios. Anyway, if you have a specific issue with your board that only a PCChips bios can solve, please contact us and we'll try and find a solution for you.

Q25: Nice program. If only you added fsb frequencies of 142 and 147 and multiplier/vcore settings...
A: Chfsb only allows to activate what already was in the bios. Multiplier and vcore settings were never implemented in the k7s5a bios. The only additional fsb settings that are there but we have not activated are 66/66, 66/100 and 133/100. If someone is interested we could add these to the next version.

Q26: I have tested thoroughly both Chfsb and CPUFSB and the results are rather disappointing compared with other motherboards. The k7s5a is not any good as an overclocking board.
A: ECS just doesn't make extreme overclocking boards, it's not their policy. But in a sense, the k7s5a is one of the better oc-boards out there, since with the money you'll save by buying it instead of some manufacturer's board, you'll be able to buy a much faster CPU. And then you can even overclock it a little bit...Can you ask for anything more? Oh, well, yes. A k7s6a.
CHFSB FAQ (2)
By Cheepoman and Mpapec
The details
The cmos area in the Sis 735 chipset is 256 bytes long, but only the first 128 bytes are used. If you dump it with Cmos Tools (which unfortunately only works under Win9x/Me), it will look something like that:

The upper table in the picture is the current CMOS table, which corresponds to a fsb of 133/133 MHz. On the lower table we can upload a previously saved table, in this case one with the at 100/100. Using the "compare" function of Cmos Tools we can see that the only differences are in registers 00h, 02h, 06h, 3Fh and 70h. The first three, 00h, 02h and 06h are related to the onboard clock, whereas 3Fh is the lower byte of the Checksum register. These are standard registers, located in the same addresses for every motherboard out there coming from the IBM AT legacy. A good guide on these registers can be found here. On the other hand we have many other registers that are chipset specific, and in our case undocumented. The Sis735 databook has not been released, so to the only possible way of learning anything about these registers is try and error.
By comparing the cmos tables corresponding to the available settings of several bios versions you can easily conclude that the fsb settings are always stored in 70h-71h. Studying these registers in their binary form, we can see that there is a 4-bit pattern which is common to all k7s5a bios versions, although its particular position within the 70h-71h bytes does depend on the particular version. To go further we have to study the registers in their binary form. I started with the 010911-OC bios because it's the bios I use on my k7s5a, and it has the extra fsb settings. Later I discovered that luckily enough this is also the bios with the simplest setting syntax, which made the whole thing much easier to grasp. In this particular version only the value of 70h does change, according to the following table:

FSB speed 70h Hex Value Binary
H/W TRAP 02 00000010
100 12 00010010
112 16 00010110
124 1A 00011010
100/133 22 00100010
133 32 00110010
138 36 00110110
150 3A 00111010


Only the four bits in red do really matter for fsb setting. A little extra experimentation shows that the bios will accept any value for the other four bits, so with 70h= F5=11110101 the system will boot at 138 with no problems. However, we can never be sure that these apparently "dummy" bits do not contain some subtle settings as "spread spectrum" or something of the like. Therefore, it's wiser to leave these bits alone and only modify what really matters for fsb. So, from now on I'll use the following notation: 138:70h=36=xx1101xx , where "x" stands for a dummy bit.
These 4 significant bits do appear in every bios version, although its position within the 70h-71h bytes does vary from version to version. To make things more complicated, one or two additional significant bits may appear, as in bios 011215:
ˇˇ
FSB speed 70h-71h Hex Value Binary
100 44-2F xx0x0100-xxx0xxxx
112 45-2F xx0x0101-xxx0xxxx
124 66-3F xx1x0110-xxx1xxxx
100/133 48-3F xx0x1000-xxx1xxxx
133 6C-3F xx1x1100-xxx1xxxx
138 6D-3F xx1x1101-xxx1xxxx
150 6E-3F xx1x1110-xxx1xxxx
These two extra bits are clearly related to main bus and memory timings, which is good news because it means that the programmers at ECS did some improvement in the later bios revisions in order to get everything working properly at each bus speed.
To change the fsb in this bios version we only need to overwrite the values in 70h-71h with any others from the list. The full set of values for all k7s5a bios versions is provided in the fsball.txt file that comes with Chfsb. The job can be done within Cmos Tools, but if you don't have Win9x you may use cmostool. This is a different, older program for Ms-Dos that you can run from a boot disk. If you have trouble using it please read the short tutorial I wrote for the forum:
"With CMOSTOOL for DOS (for people with win2k/XP):
Look at the table I provided and select a FSB frequency, e.g. 138
138/138 70h=DB 71h=3F
Boot from a DOS/win95/win98 floppy with cmostool.exe in it (it's only 38 kB). Run cmostool. It will ask for the CMOS lenght: 128. There is a menu with 6 options. Type 4 to see the contents of the CMOS (Hex Dump function). The adresses we want to write to, 70 and 71, are the two leftmost ones in the bottom row. Type 5 to overwrite the CMOS. Enter the first adress (70). The appropriate syntax is: 0x0070. Enter the corresponding value: (in the previous example, DB) 0x00DB. Type 5 again to change the other adress. Enter 0x0071 and then 0x003F. Type 4 again to verify the changes. Type 6 to quit the program. Reboot."

By doing this you are overwriting the whole contents of the 70h-71h registers, including the dummy bits. This shouldn't be a problem, but for some people's systems it is and the raw Hex value from the list won't work. One user reported that his system wouldn't boot with bios 011215 and 70h-71h=45-2F (112/112 MHz). What was wrong? let's do the math:
His default value for 100/100 was 44-20 (01000100-00100000), not 44-2F (01000100-0010FFFF) as in the list. If we take 44-20 and overwrite only the significant bits then we've got 01000101-00100000=45-20. Did it work? It did.
The moral of the story is, leave the dummy bits alone. Chfsb does that.
Checksum errors
The registers in 3Eh and 3Fh contain the checksum for the "extended cmos", which includes the 70h-71h fsb registers. Therefore, if you modified the latter then the checksum would be wrong and the bios would refuse booting and present a "CMOS Checksum wrong" message. That's the theory. In practice, most of the times the bios will boot anyway and correct the checksum by itself. Contrarily to what Mr. Gates may think, it's not very nice to have a program that will only work most of the times, so Chfsb implements checksum correction, as you should do if you found that kind of error in your home experiments with the cmos. The calculation is very simple:
First of all, take note of your initial 70h-71h and 3Eh-3Fh values, say 44-20 (for 100 MHz) and checksum 32-FE. Let's assume you want to set 124 MHz (all within bios 011215).
44-20 is binary 01000100-00100000. From the table, to switch to 124 we have to overwrite the significant bits with xx1x0110-xxx1xxxx, so the new value will be 01100110-00110000 = 66-30. To go from 70h=44 to 66 we have added 22 (hex), and from 71h=20 to 30 the difference is +10 (hex). All in all we have to add 22+10=32 (hex) to the checksum, so the new values for 3E-3F will be 32 FE + 00 32 =33 30.

CPU FSB Frequency Multiplier Actual Core Frequency
Athlon XP 1800+ 133MHz 11.5x 1.53GHz
Athlon XP 1700+ 133MHz 11.0x 1.47GHz
Athlon XP 1600+ 133MHz 10.5x 1.40GHz
Athlon XP 1500+ 133MHz 10.0x 1.33GHz

Za na konec meni dela brez problema na 1900XP+ upam da še dolg na 1700+ pa spljoh tko da probite tole vam se močno splača sam RAM morte met dober...

HAVE NICE TWEAKING!

LP

ROFL
Za to narest rabs pol ure na epoxu ce zlo pocas napredujes :) Ne pa neke doktorate brat ipd in izumljat toplo vodo :)