I need a bottom line explanation of how to get 133fsb on K7T Turbo-R

[coomarlin]

I've been reading through many of the turbo-r threads and it seems I'm running in circles. I just got my replacement turbo-R to go along with my tbird 850. I have no problem reaching 1000mhz when I run (10x100). The system is very stable and I'm happy. But I'd like to try (7.5x133). I have good quality PC133 Crucial CL2 ram I have the original bios that allows me to go to 132fsb. I read some horror stories about flashing problems on turbo-r boards the cause the loss of low multipliers. How do I get past this? I saw an overclocker bios posted on MSI sight, but it doesn't say weather it is for the RAID version of the board. I'd hate to flash it and lose my RAID controller. What gives? Help would be appreciated.

 

[KRogers]

Jumper 17 sets the fsb to 100 or 133. The manual shows how to set it. The overclocker's BIOS or fsb do not disturb the FastTrak functionality. I'm still unsure of which multipliers may be affected using the newer BIOS.

 

[ivanov]

set your multiplier real low, save the setting and then power off your system. remove jumper 17, and then power up the system, go into the bios and u're at 133fsb... u're free to set it up to 166...change the multiplier to whichever works for you...

 

[RBuck]

Ivanov: Are you running either of the beta bios? I am looking for absolute confirmation that the Promise controller (chip) wont be damaged by either of the beta bioses..

 

[bluesky]

ivanov.
Did you set bios as default except the multiplier as lowest, or just make the multiplier lowest and other settings don't matter?

 

[jfkaiser]

Hi,
This method seems to work for me on my K7t Turbo Raid with a Duron at 133 fsb.....it refers to info from another posting I have running in this same forum.

Ok here is the latest attempt at a solution.
I had been running back at the 100 FSB speed after my failures to get back to 133fsb mentioned above. PC had been running for about 3-4 hours....not sure if PC being warmed up had anything to do with what follows....

I decided to try and get back to a bootable 7.5 multiplier (whether it be at 100 or 133) I just wanted to see if I could ever get machine to hold at 7.5 again.

I kept bus at 100 fsb and set Duron600 for 9x. I hit F10 to save and rebooted OK..no power off and bleed this time. I did NOT hit F10 and power off immediately as describe in my earlier post. I just did F10 and saw if PC got video sync or not. That is same for what is described below too.

Next I went for 8.5 and saved. Got no video sync after save reboot, so powered off and bled PC by depressing power button with Power strip off. This time machine DID come back at 8.5 x 100.

Next I went down to 8x then finally the desired 7.5x multiplier following exact process mentioned above about powering off and bleeding.......woo hoo I got machine to talk to 7.5 again.

Final step was to change jumper to 133fsb and see if machine came up.....YES success, and once again I am writing this from a PC actually running 7.5 x 136 fsb = 1020MHhz.

I only pray that tomorrow when I turn the PC on again it will come up at 1020 and not fail as it did earlier today.

I don't know if the changing back to 100 fsb and then starting to go down from 9x to 7.5 is really necessary.......If I have to do this again I will try leaving the fsb at 133 and coming down from 9x to 7.5 (if my Duron can handle 9 x133 just to get the wierd process going on way down to 7.5

I would hope that something here can be logically explained and fixed in future bios release. I read something about Hi and Low states of the Durons and maybe my strange procedure somehow switches those states and lets me re-attain the 7.5 multiplier....I'm not sure.

Thx,
Jon