You might try this program to help you identify exactly which CPU you have: WCPUID http://hp.vector.co.jp/authors/VA002374/src/download.html Another way is to look at the ordering part numbers (OPN) printed on the CPU: AXDA2600DKV3C = Athlon XP 2600+ Model 8 Tbred-B 2133Mhz (266MHz FSB) AXDA2600DKV3D = Athlon XP 2600+ Model 8 Tbred-B 2083Mhz (333MHz FSB) AXDA2600DKV4D = Athlon XP 2600+ Model 10 Barton 1917Mhz (333MHz FSB)

0

Ok, so I tried that program, and it still reading as 1900+. Which means I probably got ripped off. Which sucks a lot. If it is the 1900+, should I be running at more than 100 mhz?

0

You should still try looking at the number on the CPU. At least you will know for sure which model you have.

0

There is most likely one of two things going on here. 0. You've been had being sold a 1900+ Palomino/ Tbred as a 2600+. 1. You have your BIOS settings all wrong. Identifying and confirming the markings on the CPU easily takes care of the first scenario, with that ruled out, my advice is to clear the CMOS via jumpers and ensure it is back in normal position, then go into the BIOS after reboot to load default settings. Whom are you on computing.net?

0

Athlon XP 1900+ runs at 1.60 ghz.

0

Ok, so I checked the model number which was AXDA2600DKV3C, which means I do have a 2600+. So I reset the jumpers and CMOS and reset my BIOS......still 1900+....1.6 GHz. Still won't change to 133MHz. Like its glued on 100 MHZ. I can;t find any kind of jump on my motherboard that would allow me to change the FSB so I assume something si up with my BIOS? Any ideas?

0

I just looked at your original post and saw something very wrong: Baazar said: > I recently upgraded my processor from an AMD > XP Athlon 1800+, (1.1 Ghz) to a AMD Athlon XP > 2600+ (2.1 GHZ) The XP Athlon 1800+ should have been running at 1.5GHz (11.5x133) NOT 1.1GHz (11.5x100). Even then your FSB was only running at 100MHz instead of 133MHz. Put the XP1800+ back in and make sure it is running at it's rated speed of 1.5Gz. If you have problems make sure the FSB and RAM are running at 133MHz. If you can't get the FSB and RAM both running 133MHz then maybe your RAM is faulty. Download memtest86 and make a floppy to test your RAM.

0

Now I got to ask you.... 0. Are you sure you got some PC 2100 memory ? 1. Are you saving the changes you made in the BIOS b4 exiting ? Within your BIOS, you should have a CPU FSB Clock option that allows you to select the CPU Front Side Bus clock frequency (in MHz), it ranges from 100 to 220. Make sure you set this to 133MHz FSB, otherwise the CPU will run at the default 100MHz speed. Also set the CPU Ratio, CPU Vcore (V), DDR Voltage (V) and AGP Voltage (V) all to Auto. Ensure you save the changes before exiting the BIOS. Reboot and see if your CPU is detected appropriately. Whom are you on computing.net?

0

Ok heres the deal. My memory is clean. 768 MB of DDR RAM PC 2100. all working perfectly normal. No problems with RAM. My processors are both not reading at 133MHZ. Inside my BIOS it will NOT ALLOW ME TO CHANGE MY FSB. ITS 100 MHZ. Period, even though I should be able to change it all the way up to 220. Everything else is set to auto. So my real problem is how to get my BIOS to let me run the processor at 133MHZ. I flashed it successfully, but it didn't help. And nowhere on my motherboard is there a jumper to change it manually.

0

It is possible that your RAM is being detected wrongly and is only running at 200MHz (2x100) instead of 266MHz (2x133). Try changing it manually from SPD to 266MHz: Advanced Chipset Features DRAM Timing Control SDRAM Frequency = (SPD, 200MHz, 266MHz, 333MHz) After that see if you can now change your CPU settings manually: Frequency/Voltage Control CPU FSB Clock = (100MHz to 220MHz) CPU Ratio = (?) You should end up with these settings: SDRAM Frequency = 266MHz CPU FSB Clock = 133MHz CPU Ratio = 16.0 Note: 2133MHz = 16.0x133.3MHz One last thing. Have your tried the "Fuzzy Logic III" program that came on the MSI CD? It is supposed to allow modifying the these settings from Windows.

0

I had a look at your manual & it seems simple enough...Don't use AUTO settings...configure everything manually. Go to the Frequency/Voltage Control menu: 1. disable Spread Spectrum (From the manual: Remember to disable Spread Spectrum if you are overclocking because even a slight jitter can introduce a temporary boost in clockspeed which may just cause your overclocked processor to lock up) 2. change the CPU FSB Clock to either 133 or 166, depending on which 2600+ you have. (From the manual: Setting options range from 100 to 220. If you install a CPU other than 100MHz FSB, you should change the setting to corresponding FSB frequency; otherwise, the CPU will run at the default configuration 100MHz) 3. set the CPU Ratio (multiplier) to the proper number for your CPU 4. set the CPU Vcore to 1.65v 5. DDR Voltage can be left set to AUTO, or if you know the voltage requirement for your RAM, you can set it to that 6. leave AGP Voltage set to AUTO. Asus A7N8X-X 1800+ @8x210mhz 512mb PC3200 Ti4200/8X 128mb WDC 60GB

0

I cannot stress enough...the problem I'm having here is that the BIOS WILL NOT ALLOW ME TO CHANGE MY FSB. 100MHz is the only option! I really appreciate all the help, but everyone seems to be missing my problem entirely.

0

I did not miss that at all. I suggested checking the memory speeds because if it was only running at 100MHz then that might prevent the CPU clock from being set any higher. You have to understand all we can do is speculate since we do not have your system. Since your system has never run at 133MHz then there is always the chance that either your board is defective or your RAM is. Again this is only speculation. I have a second computer that I bought almost four years ago. When I upgraded it from a Duron 850MHz (100/200MHz) to a XP2000+ 1667MHz (133/266MHz) all I had to do was upgrade the BIOS and make sure the clock was set to 133MHz and the PC133 SDRAM was running at 133MHz. It should not be as hard as you indicate. If your RAM is running 133/266MHz and your can't set the CPU clock 133MHz then something is defective. You will have to figure out what it is. If that means swapping parts then that is what you have to try. We have done all we can do until you narrow down where tha problem lies.

0

Ok, thank you,(sorry about snapping.) I don't know how anything could be defective, everything seems to be working fine but I guess a little more tinkering should reveal something. Just curious If I manage to figure this out will I such much of a performance boost? Will the extra speed be noticeable? Thanks again to everyone who tried to help.

0