205

Latest

  • Garmin launches nuvi 2x5 series, complete with MSN Direct

    by 
    Darren Murph
    Darren Murph
    03.04.2008

    If you thought Garmin had exhausted all possible options at CES, you thought wrong. Here at CeBIT, the outfit has rolled out four new navigators for your routing pleasure, starting with the nüvi 205 (3.5-inch) and 205W (4.3-inch). These siblings both feature a 333MHz processor, Garmin's own HotFix technology to get your position on the double, the famed "Where Am I?" feature and the ability to snatch traffic information via MSN Direct when used with an optional receiver. Additionally, these two are set to include map choices such as the contiguous United States, Canada or regional sections of Europe. As for the higher-end 255 and 255W (pictured), they'll be all too similar save for the maps, which promise "comprehensive coverage of North America, Europe, Australia or New Zealand." For pricing and availability information, click on after the jump.[Via GPSReview]

  • 2.0.5 patch notes

    by 
    Eliah Hecht
    Eliah Hecht
    01.15.2007

    2.0.5 seems to have rolled out again, this time with fewer problems (I'm now on and playing, anyway). I doubt very many of you are reading from work (unless you're in Europe, I suppose), but here are the rather boring patch notes: World of Warcraft Client Patch 2.0.5 (01/14/2007) Increased the maximum number of realms that can be listed in the Realm List. Updated the Terms of Use. Created an option to disable UI Acceleration for users of select video cards experiencing graphical corruption of the User Interface. To utilize this option, enter the following line to the Config.wtf file, located in the WTF subfolder of the game: Set UIFaster "x" Where x equals: 0 - This turns off all UI acceleration 1 - For Internal Use Only - DO NOT USE! 2 - Enables partial UI acceleration only. 3 - Enables all UI acceleration. Example: Set UIFaster "2" Note: For users experiencing graphical corruption of the User Interface, it is recommended to try option 2 in order to correct the problem. If this does not solve the issue, then use option 0 to disable all UI Accleration.