I am 100% against it. Here are some reasons why i am:
1. it is windows based(i prefer bios)
2. settings are not real time setting (160mhz isnt really 160mhz)
3. Its all based on theory(thats what i believe)
4. Hard to use
5. gets you nowhere (and wastes time)
6. hard to use
7.uses memory(not to big of a prob)
8.only a "selling feature'
9. no or really limited support
10. last but not least IT DOESN'T WORK
the program is suppose to crash the pc when it hits a fsb that is unstable. but the program when up to 160mhz and closed the program(divider was set at 1/3, that a 53mhz pci bus, lets get real)
my system is a 800mhz duron with noname pc 100 ram(which cant run faster than 138) a original duron 800 with a fsb of 160 would run at 1280mhz my duron cant hit more than 1050mhz. If it was accually changing the fsb, run wpcuid beside it a refresh now and again, and you will notice that the speed of the cpu never changes. This may just be my board but there has been reports of this happening with other users of msi boards. Just use the bios, it has a cool overclocking protection that if the system doesnt boot it will restart with default bios setting so that you dont have to clear the cmos.
so try the prog and if it doesnt work dont be surprised and use the bios settings.
Hope this is what you wanted to know
btw i am using a msi k7t turbo limited edition(none raid) rev.3 board