HellasVagabond
New Member
- Joined
- Jan 19, 2007
- Messages
- 3,376 (0.52/day)
- Location
- Athens , GREECE
System Name | SECONDARY RIG / PRIMARY RIG / THIRD RIG |
---|---|
Processor | i920@3.6GHz / i920@4GHz / AMD Phenom II 955 |
Motherboard | Gigabyte EX58-UD4P / Gigabyte EX58-UD7 / ASRock 890GX3 |
Cooling | CoolIT Domino ALC / Thermalright Silver Arrow / Thermalright VenomousX |
Memory | 12GB DDR3 @ 1800MHZ / 6GB DDR3 @ 2250MHZ / 4GB DDR3 @ 1600MHZ |
Video Card(s) | XFX ATI RADEON 5970 / GAINWARD NVIDIA GTX 580 / 2xGEFORCE GTX295 |
Storage | 1550GB / 6TB SAS - SSD / 160GB SSD |
Display(s) | NEC 26WUXi2 / NEC 3090WQXi / SONY 55A2000 (1080P 55inch) |
Case | COOLER MASTER HAF 932 / COOLER MASTER ATCS 840 / ANTEC DARKFLEET DF85 |
Audio Device(s) | Soundblaster X-Fi Xtreme Music / SoundBlaster X-Fi Fatal1ty Pro / Realtek Onboard |
Power Supply | CWT 1200W / Enermax Revolution 85+ 1250W / Ikonik Vulcan 1200W |
Software | Windows 7 x64 / Windows 7 x64 / Windows 7 x64 |
An exploitable bug in Mozilla Firefox discovered earlier this month was first believed to have been caused by Internet Explorer 7 but soon after that Mozilla was forced to admit that it was Firefox that could trigger the bug as well. Today however that bug has apparently been traced back to a Windows API function. However Mozilla seems to have fixed the bug in their latest Firefox 2.0.0.6 version.
View at TechPowerUp Main Site
View at TechPowerUp Main Site
Last edited by a moderator: