Here's two Mods for AMD's Athlon? XP processors! the first Mod will set your Athlon? XP 2000+ 2200+ or 2400+ to a XP2800 (166x13.5) defaulting to a 166 FSB.
and the second mod will help you hit 200's MHz FSB with your Athlon? XP 2600+ 2700+ or 2800+ that's like running a Barton CPU.....Hehe and as they say TRY @ Your own Risk
Thanks to Praetereo , Aceman and Nohto ! for the Mods Here's a snip from both mods! just click on the links for more Info! Please also see the second mod to set your Athlon? XP 2000+ 2200+ or 2400+ to a XP2800 (166x13.5) defaulting to a 166 FSB. Modifying A 133 Fsb T-bred B Into 166 Fsb
We mentioned earlier that there differences between Barton and TBred-B in terms of their L12 bridges. The difference can also be seen with the Athlon XP 2700+ and 2800+, which share a 166MHz FSB. Would it be possible to go straight to a 166MHz FSB by changing the L12 bridges? We decided to test this with a TBred-B Athlon XP 2200+:
To reconnect the two severed L12 bridges, we will use the same method used to unlock the multiplier. Apply correction fluid to the gap in the second bridge from the right (the bridge we will attempt to connect), then tape the adjacent bridges to prevent short-circuiting. Then connect the bridges using a conductive silver pen.
PC booted and the BIOS quite clearly shows a 166MHz FSB. A simple L12 connection to unlock 166MHz FSB speeds seems to be well worth the effort ? if you choose to unlock the multiplier, unlock this higher FSB setting as well to give a significant performance boost. Modifying A 133 Fsb T-bred B Into 166 Fsb Possible Solution for Running High FSB
On my 2700 and other new chips, they ran cut-connected-connected-connected. These bridges set the default FSB, with the former being 133, and the latter being 166. To test whether this affected the chip being able to run a high FSB in this board, I connected the third L12 bridge (one away from the "L12") on Aceman's 2200 - This would in effect make it look like a new XP2800 (166x13.5). We began testing and the chip was defaulting to a 166 FSB. We then procedded to make small increases in FSB in BIOS. We were hoping we would run into the problems that my 2700 was having. Sure enough, his chip could no longer run high FSB speeds. It started producing the exact same error screens and messages that my 2700 was, and at nearly identical FSB speeds. To further test, we pulled the 2200 out, and I broke the connection I had made on the third L12 bridge. We then immediately put the chip back in without changing anything else. The chip was instantly able to run 220+ FSB speeds again just like before. This really seemed like conclusive evidence that these bridges affected if a chip could run high FSB in this board. I then took a model knife (x-acto knife) and cut the third L12 bridge on my 2700. This made it match the factory setup of Aceman's 2200, and when we booted up, the chip did indeed default to a 133 MHz FSB. We started increasing the FSB with our fingers crossed, and I was amazed to see the chip booting perfectly fine as we started running all the way into the 200's! We tested what we could in the limited time we had, and the chip breezed through 3DMark at 220 MHz FSB. We did not have time to accomplish any in depth testing, but running Prime and Sandra at high FSB speeds was perfectly fine. Possible Solution for Running High FSB
and the second mod will help you hit 200's MHz FSB with your Athlon? XP 2600+ 2700+ or 2800+ that's like running a Barton CPU.....Hehe and as they say TRY @ Your own Risk
Thanks to Praetereo , Aceman and Nohto ! for the Mods Here's a snip from both mods! just click on the links for more Info! Please also see the second mod to set your Athlon? XP 2000+ 2200+ or 2400+ to a XP2800 (166x13.5) defaulting to a 166 FSB. Modifying A 133 Fsb T-bred B Into 166 Fsb
We mentioned earlier that there differences between Barton and TBred-B in terms of their L12 bridges. The difference can also be seen with the Athlon XP 2700+ and 2800+, which share a 166MHz FSB. Would it be possible to go straight to a 166MHz FSB by changing the L12 bridges? We decided to test this with a TBred-B Athlon XP 2200+:
To reconnect the two severed L12 bridges, we will use the same method used to unlock the multiplier. Apply correction fluid to the gap in the second bridge from the right (the bridge we will attempt to connect), then tape the adjacent bridges to prevent short-circuiting. Then connect the bridges using a conductive silver pen.
PC booted and the BIOS quite clearly shows a 166MHz FSB. A simple L12 connection to unlock 166MHz FSB speeds seems to be well worth the effort ? if you choose to unlock the multiplier, unlock this higher FSB setting as well to give a significant performance boost. Modifying A 133 Fsb T-bred B Into 166 Fsb Possible Solution for Running High FSB
On my 2700 and other new chips, they ran cut-connected-connected-connected. These bridges set the default FSB, with the former being 133, and the latter being 166. To test whether this affected the chip being able to run a high FSB in this board, I connected the third L12 bridge (one away from the "L12") on Aceman's 2200 - This would in effect make it look like a new XP2800 (166x13.5). We began testing and the chip was defaulting to a 166 FSB. We then procedded to make small increases in FSB in BIOS. We were hoping we would run into the problems that my 2700 was having. Sure enough, his chip could no longer run high FSB speeds. It started producing the exact same error screens and messages that my 2700 was, and at nearly identical FSB speeds. To further test, we pulled the 2200 out, and I broke the connection I had made on the third L12 bridge. We then immediately put the chip back in without changing anything else. The chip was instantly able to run 220+ FSB speeds again just like before. This really seemed like conclusive evidence that these bridges affected if a chip could run high FSB in this board. I then took a model knife (x-acto knife) and cut the third L12 bridge on my 2700. This made it match the factory setup of Aceman's 2200, and when we booted up, the chip did indeed default to a 133 MHz FSB. We started increasing the FSB with our fingers crossed, and I was amazed to see the chip booting perfectly fine as we started running all the way into the 200's! We tested what we could in the limited time we had, and the chip breezed through 3DMark at 220 MHz FSB. We did not have time to accomplish any in depth testing, but running Prime and Sandra at high FSB speeds was perfectly fine. Possible Solution for Running High FSB
