• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

MSI Afterburner 2.0.0 Beta 7

Soldato
Joined
24 Jan 2007
Posts
14,063
Location
.
http://forums.guru3d.com/showthread.php?t=327806

Download: http://event.msi.com/vga/afterburner...up200Beta7.zip

[Changelog]

- Added optional data filtering mode for all hardware monitoring graphs. Now it is possible to enable special math data filtering algorithm independently for each hardware monitoring graph to reject misreading spikes caused by sensor access conflicts when running multiple hardware monitoring tools at the same time
- Fixed videomemory usage monitoring for non-primary NVIDIA graphics cards
- Application restart is no longer required to apply new user interface language Signed/scanned extending agreement is also in the attachment.
 
Cheers Gareth, Beta 6 just expired today and had to go back to 1.6, really don't know why Unwinder has such short expiry dates on the software.
 
Yeah booted up at 7am and bang it's expired, didn't expect a new beta today going by what Unwinder was saying on the forum but glad it's here anyway, easily the best overclocking app out there.
 
i just dowmloaded this one, whats the difference between this and 1.6 ?

Here you go, list of fixes from 1.6 up until version 2.0 beta 6, apply the beta 7 changelog to the below list as well.

Changelog
- Voltage control layer has been seriously revamped to give additional freedom to extreme overclockers with new custom design MSI graphics cards. Now MSI Afterburner is able to control up to 3 voltages on custom design MSI Fermi and other future custom design MSI graphics cards. New adjustable voltages include memory voltage and special multi-purpose auxiliary voltage feeding either memory bus (also known as VDDCI on AMD graphics cards) or PCIE bus and crystal (PEXVDD on NVIDIA graphics cards)
- Added core, memory and auxiliary PEXVDD voltage control for custom design MSI N480GTX Lighning series graphics cards with uP6225+uP6262 voltage regulators
- Added core, memory and auxiliary PEXVDD voltage control for custom design MSI N470GTX Twin Frozr II OV3 series graphics cards with uP6218+uP6262 voltage regulators
- Added core, memory and auxiliary PEXVDD voltage control for custom design MSI MSI N460GTX Hawk series graphics cards with uP6262 voltage regulators
- Added core voltage control for custom design MSI N460GTX Cyclone series graphics cards
- Added auxiliary VDDCI voltage control for reference design AMD RADEON HD 5870 series graphics cards
- Added fan tachometer monitoring for NVIDIA graphics cards. Please take a note that not all graphics cards are tachometer reading capable. So depending on graphics card and cooling system fan tachometer monitoring can be unavailable
- Optimized NVIDIA driver-level clock frequency monitoring codepath
- Minimum clock limits for all graphics cards have been reduced from 75% to 50%
- Dynamic overclocking, voltage and fan speed limits. MSI Afterburner no longer uses static slider limits calibration and adjusts the limits dynamically when some external factors affect it (e.g. Overdrive clock limits on AMD cards or VGA BIOS fan speed and voltage limits on NVIDIA GeForce GTX 400 cards)
- New temperature hysteresis settings for software automatic fan control mode gives you additional way to improve cooling system thermal and acoustic parameters
- Now fan speed limits (i.e. minimum and maximum fan speeds accepted by VGA BIOS and display driver) are displayed in custom fan speed curve editor window
- Built-in skin sizes have been reduced due to optimized internal skin panels representation and optimized compiled bitmap cache
- Optional skin compression ability in the built-in skin compiler. Skin format reference documentation has been updated to document new compression options
- Minor built-in skins appearance tweaks
- Now MSI Afterburner uses previously undocumented power user oriented startup mode via the task scheduler under Windows Vista / Windows 7. MSI Afterburner launch no longer requires UAC confirmation at Windows startup. Please take a note that Microsoft Visual C++ 2008 runtime libraries must be installed to get new startup mode working
- Now MSI Afterburner automatically fixes startup link if <Start with Windows> or <Apply overclocking at system startup> is enabled but the registry or task scheduler startup entry is missing
- Startup profile is now displayed in <Apply at Windows startup> option floating tooltip instead of the main window
- Now power users can enable optional DirectInput based hotkeys handler via the configuration file. DirectInput based hotkeys processing can seriously reduce hotkey response time in the applications heavily loading CPU (mostly 3D games) and leaving not enough time for processing standard keyboard input message queues. Please take a note that enabling such sophisticated hotkeys handling mode can cause some system security applications (e.g. pro-active application behavior analysis module of KIS) to warn you about possible keylogging threat
- Improved skin engine, now skinned controls support horizontal and/or vertical centering. Skin format reference guide has been updated to document these new alignment modes
- MSI On-Screen Display server has been upgraded to version 3.7.2. New version gives you the following improvements:
- Now screen capture events are identified visually by text message flashing in On-Screen Display during 0.25s
- Built-in skin sizes have been reduced due to optimized compiled bitmap cache
- Added On-Screen Display profile for Startcraft II : Wings of Liberty
- Added configuration file switch allowing sending MSI Afterburner to system tray instead of closing on <Close> button click
- <Start the task only when computer is running on AC power> option is no longer set in the startup task settings to allow automatically starting application via the task scheduler on laptops or on some UPS models
- Added Korean localization
 
Last edited:
Sticking with the non-beta... infact if anyone made a decent program that could control voltage on 400 series cards I'd use that... time limit on non-commercial beta programs = epic fail.
 
Sticking with the non-beta... infact if anyone made a decent program that could control voltage on 400 series cards I'd use that... time limit on non-commercial beta programs = epic fail.

What's the time limit on these? I haven't really read anything before installing.
 
Basically the beta versions have a 1 week time limit - after that it just gives you some vague message about the program being unable to work any more and quits. I mean come on... it doesn't even tell you its expired because its a beta it gives you some vague error - you only know its supposed to happen if you religiously follow the forum threads. Your supposed to update to the next beta version then........... if it was a closed beta I could understand it.


(Yes I think the programmer is retarded and feel like ranting).
 
Last edited:
Unwinder, the greatest mind behind ATI/nvidia overclocking software is retarded, I think not. Yes the beta does expire but he will have the next beta out in time for you to update the expired one, he needs testers to jump form one beta to the next and not sit back on old builds, all for feedback purposes.
 
(Yes I think the programmer is retarded and feel like ranting).

i agree he's retarded, i mean, rivatuner was SO much more flexible and now he can't be arsed with it cos he's making a few quid from MSI...

fair play to him but wish he'd make rivatuner work with this gen of cards as it works so much better than AB imo
 
Unwinder, the greatest mind behind ATI/nvidia overclocking software is retarded, I think not. Yes the beta does expire but he will have the next beta out in time for you to update the expired one, he needs testers to jump form one beta to the next and not sit back on old builds, all for feedback purposes.

As a generalisation no... in this particular decision yes - tho as a software developer I all too aware of the last point - but thats why we have a private/closed testing program.
 
Back
Top Bottom