Newest version of this popular tool. *editing SubSystem ID and SubVendor ID; *support Radeon X300, X600 and initial for X800 (for X800 it works only first laying); *the incorrect determination of frequencies in certain cases, for example, in the case of SDR of memory; *they are transferred into read only) the nekotrye "uninteresting" parameters of the controller of memory (' Write Latency ', ' Command Latency ', ' Strobe Latency '); it is not possible to edit them now, however, in the ravine they there is; *several new parameters of the controller of memory R300, which relate to signal Out Enable (' Shift of OE signal for WRITE Data ', ' Shift of OE signal for WRITE Data Strobe '), which can a little increase productivity; *the editing of the parameter ' Memory Refresh Rate '; *support to the fact WinXP; *the editing of the size of the memory (it is required testing); *log is now painted according to the semantic content. download thanks sergy
Double post! S'ok though. Here How to use it? I've been using it since the first version released. It's just timings editing. Basically lower = better performance. You can also increase the latencies for some more overclocking headroom. Some settings are similar to typical BIOS settings for memory and those are what give the real performance increases. I gained about 100 3Dmarks out of it. Not much, but meh.
Yeah i also like to play with timing but how it works? i have to download a bios for my card or look for it in my system...?
Use flashrom or ATIFlash and save your BIOS. Then open it with the utility and then you can adjust the timings. ATIflash -s 0 <name of file>.bin saves the BIOS
Hmm When I load a ROM image and (without changing parameters) save to a file, the resulting file is identical to the original source. Nice to know it isn't screwing with anything under our noses. Now when I load a ROM image and bump the core and memory clocks 1 notch up, and then bring them back to the original setting, I notice that the resulting file has differences from the original source. I conclude that v1.3 avoids the problem of changing ROM contents by making the slider less sensitive to changes. I would understand changes due to parameters and also checksum, but what causes the ROM image to change when clock modifications are returned to previous default?
u can (and i recommend it) use the built in AtiTray timing changer, this little thing can let you see what can happen if u chnage one timming setting on ur card, it works on windows so u dont have to reboot to see chnages, and if somethen went wrong changing the timings (like total screwed up display) u just hit alt+r and it will restore to normal, its pretty useful to find what can u chnage and what not and then use those parameters in rabit to get a full timing optimize ^^ i did this and hell, it works so good, gained like 2-3fps on farcry, which helps a lot ^^
1. Load a ROM image ( e.g. Samsung25_GeCube.bin ) 2. Go to Device Clocks tab 3. Bump up Core clock speed from 499.50MHz to a higher speed, say 513.00MHz 4. Now revert it back to 499.50MHz 5. Save the file to test-3.rom 6. Open an MS-DOS window, and go to the saved directory, and do a file compare: fc /b Samsung25_GeCube.bin test-3.rom The results: Comparing files Samsung25_GeCube.bin and TEST-3.ROM 000001A4: F2 63 000001A5: DF DE 000001A6: 27 7F 000001A7: 29 28 000001AC: 30 AE 000001AD: BD BC 000001AE: 00 01 000001AF: 00 02 000001C4: F2 63 000001C5: DF DE 000001C6: 27 7F 000001C7: 29 28 000001CC: 30 AE 000001CD: BD BC 0000097E: B8 1C 0000097F: 88 89 00000980: 50 1E 0000098C: 40 4D 0000098D: 9C D0 0000CFFF: FF 00 Question is, why the ROM changes when the clock was reverted back to original setting?
Hypothesis Hmm - I think I know now why there are numerous byte changes. Take a look at the ATi BIOS info: Core clock & Memory clock have two reported figures: bios: and hw: Note how in standard firmwares, bios: is always reported as a nice round figure (e.g. 500.00MHz and 350.00MHz) but hw: is more precise at 499.50MHz and 351.00 MHz? However, when you "touch" the sliders, both bios: and hw: figures exactly match. This does not happen to the other tweaks because they probably have no equivalent bios: value. Question is, does reporting non-standard bios: figures affect any of the drivers (i.e. why did ATi need to put separate figures - is it just cosmetic?)
Nice ATITray tool ShadowLady, thank you very much. I was hesitant on using the RaBiT tuner as I don't have a PCI video card handy, but this tool is great! I couldn't drop my timings too far but the +5fps or so and general smoothness in vietnam is really nice!