
<?phpxml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
>
<channel>
<title>Haaze.com / zmmerictrvbp / All</title>
<link>http://www.haaze.com</link>
<description>Test Web 2.0 Content Management System</description>
<pubDate>Wed, 30 Mar 2011 07:10:36 +0000</pubDate>
<language>en</language>
<item>
<title><![CDATA[How to detect and remove StarLogger]]></title>
<link>http://www.haaze.com/story.php?title=how-to-detect-and-remove-starlogger</link>
<comments>http://www.haaze.com/story.php?title=how-to-detect-and-remove-starlogger</comments>
<pubDate>Wed, 30 Mar 2011 07:10:36 +0000</pubDate>
<dc:creator>zmmerictrvbp</dc:creator>
<category>Technology</category>
<guid>http://www.haaze.com/story.php?title=how-to-detect-and-remove-starlogger</guid>
<description><![CDATA[A security researcher revealed today that he had purchased two new laptops from Samsung, and discovered both of them to be infected with the StarLogger (download) keystroke-recording program. While there's very little that can be done about keystrokes already recorded, checking your own laptop for such software is actually quite simple--if you're familiar with mucking about in your system directories and Registry.Note that the researcher only reported StarLogger on two models, a Samsung R525 and a Samsung R540. CNET examined another new Samsung laptop, the Samsung Series 9, and did not find a keylogger installed.Because it's a keylogger, most often used for spying on employees and children, StarLogger cannot be accessed from your Start menu. (Or at least, it shouldn't be accessible there. If it is, whoever installed it did a poor job.)The easiest way to find StarLogger is to look for its Registry key, which is used to load it when Windows is started. To see if this has occurred, open a command prompt and type &quot;Run Regedit&quot;. Then go to the Menu bar, select Edit and then Find. You want to search for &quot;winsl&quot;, without the quotes. If it's installed, you should see a Registry key that looks like this:HKEY_LOCAL_MACHINEsoftwaremicrosoftwindowscurrentversionunwinslYou can also look for the following files on your hard drive, although keyloggers are designed to hide themselves. Open Windows Explorer, and then hit the Alt key to bring up the Menu bar. Go to Tools, Folder Options, and View. Under Advanced Settings, you'll see an option for Hidden Files and Folders. Make sure that Show is checked.If you have StarLogger, its files will be located in your Windows root directory, in a subdirectory labeled &quot;SL&quot;. A list of files you can expect to see is below:iv.iniWinSL.datWinSL.exeWinSLH.dllImgView.exeSL-Test.txtunins000.datunins000.exeStarLogger.urlWinSLManager.exeStarLogger.urlUninstall StarLogger.lnkStarLogger.lnkStarLogger on the Web.lnkWinSLManager.exeWinSLH.dllWinSLYou can also check your Task Manager for WinSLManager.exe.How to remove itFirst, make sure that your antivirus program is up-to-date. It's entirely possible that your antivirus will detect and remove it if you run a full scan. However, there is a manual method you can use, too.The first step is to stop the StarLogger process by going to the Processes tab in the Task Manager, right-clicking on WinSLManager.exe, and clicking on End Process. If that doesn't work, you will have to end the process by booting into Safe Mode, tracking down the precise location of WinSLManager.exe, and deleting it there.The second step is a bit trickier and involves unregistering the StarLogger DLL file. Open a command prompt and navigate to the folder containing WinSLH.dll. Then type &quot;regsvr32 /u WinSLH.dll&quot; without the quotes, and you should see a pop-up window telling you that the file has been successfully unregistered.Third, go back to the Registry and locate the Registry key for StarLogger, as was done above. Right-click on it and select Delete. Last, manually delete all the files that you discovered in the SL directory, and remove the directory itself.Actually, that's the second-to-last thing you have to do. The final step is to send a letter of complaint to Samsung and ask for your money back.<br/><br/>0 Vote(s) ]]></description>
</item>

<item>
<title><![CDATA[CES: Microsoft press event Wednesday at CES 2011 (live blog)]]></title>
<link>http://www.haaze.com/story.php?title=ces-microsoft-press-event-wednesday-at-ces-2011-live-blog</link>
<comments>http://www.haaze.com/story.php?title=ces-microsoft-press-event-wednesday-at-ces-2011-live-blog</comments>
<pubDate>Tue, 04 Jan 2011 08:10:05 +0000</pubDate>
<dc:creator>zmmerictrvbp</dc:creator>
<category>Mobile &amp; Electronics</category>
<guid>http://www.haaze.com/story.php?title=ces-microsoft-press-event-wednesday-at-ces-2011-live-blog</guid>
<description><![CDATA[Join us tomorrow at 1 p.m. Pacific for Microsoft's afternoon press event at CES 2011. Please note this event is separate from the CES keynote address taking place at 6:30 p.m. that day and headed by Microsoft's CEO Steve Ballmer. As for what to expect, high-level rumors from both The New York Times and The Wall Street Journal have pointed to Microsoft unveiling a version of Windows that runs on ARM processing technology. That information could be saved for the company's CES kickoff keynote speech, though a more intimate venue would offer the company a chance to bring in additional partners for demos, as well as field questions from the press. To watch our live blog, which will include text and photos from the event, you can either bookmark this page and come back to it, or sign up for a reminder in the Cover it Live module below. Microsoft CES afternoon press event<br/><br/>0 Vote(s) ]]></description>
</item>

<item>
<title><![CDATA[Google on Web video formats: Wea4a4re at an impasse]]></title>
<link>http://www.haaze.com/story.php?title=google-on-web-video-formats-weâÂ€Â™re-at-an-impasse</link>
<comments>http://www.haaze.com/story.php?title=google-on-web-video-formats-weâÂ€Â™re-at-an-impasse</comments>
<pubDate>Mon, 30 Nov -001 00:00:00 +0000</pubDate>
<dc:creator>zmmerictrvbp</dc:creator>
<category>Latest News</category>
<guid>http://www.haaze.com/story.php?title=google-on-web-video-formats-weâÂ€Â™re-at-an-impasse</guid>
<description><![CDATA[Google has been trying to quell some of the controversy that it stirred up earlier this week when it announced that it would limit support for the H.264 video codec in its Chrome browser. Today the search giant published a blog post laying out a longer explanation for the decision.If, like me, you dona4a4t spend that much time thinking about video formats, this may seem like an arcane point. But Google framed the move as a step forward for openness on the Web, so there have been articles endorsing Googlea4a4s viewpoint and others arguing that ita4a4s actually a step backward (more on both arguments in a second).In todaya4a4s post, Google says the organizations working on HTML5, the latest version of the basic language of the Web, had reached a4Aan impassea4 over the &amp;''video&amp;'' tag, which should allow browsers to play video without installing a plugin like Flash. Microsofta4a4s Internet Explorer and Applea4a4s Safari support H.264 as the a4Abaselinea4 video codec for HTML5, while Mozilla and Opera do not. Google says it ultimately decided to join Mozilla and Opera because a4Awe genuinely believe that core web technologies need to be open and community developeda4, so  ita4a4s throwing its weight behind the WebM format:We acknowledge that H.264 has broader support in the publisher, developer, and hardware community today (though support across the ecosystem for WebM is growing rapidly). However, as stated above, there will not be agreement to make it the baseline in the HTML video standard due to its licensing requirements. To use and distribute H.264, browser and OS vendors, hardware manufacturers, and publishers who charge for content must pay significant royaltiesa4&quot;with no guarantee the fees wona4a4t increase in the future. To companies like Google, the license fees may not be material, but to the next great video startup and those in emerging markets these fees stifle innovation.In other words, Google is saying: &amp;''Man, those royalties on H.264 are a drag. I mean, not for us. Wea4a4ve got boatloads of money. But for other people.&amp;''Which may be true. As Google itself notes, as the owner of YouTube, the company is a4Aamong the largest publishers of video content in the worlda4, but YouTube&amp;'s other infrastructure costs may dwarf the licensing fees. In fact, ZDNeta4a4s Jason Perlow argued earlier that the decision is related to YouTube, but not to the licensing fee. He says that in order to control YouTube&amp;'s expenses, Google needs to consolidate the videos into a single format. So why not make that single format one that it controlsBut will the move actually work As TechCruncha4a4s MG Siegler notes, the ultimate result is a fragmented video landscape, and one whose demand for plugins seems to defeat one of the main advantages of HTML5. Want to watch an H.264-encoded video in Chrome Youa4a4ll need Flash. Want to watch a WebM video in Internet Explorer Youa4a4ll need some plug-in from WebM thata4a4s been promised for the future.Google&amp;'s blog post does tackle the fragmentation question, but the answer (that the landscape was fragmented already) isna4a4t very satisfying:Our choice was to make a decision today and invest in open technology to move the platform forward, or to accept the status quo of a fragmented platform where the pace of innovation may be clouded by the interests of those collecting royalties. Seen in this light, we are choosing to bet on the open web and are confident this decision will spur innovation that benefits users and the industry.[image via Flickr/Chris Ingrassia]Next Story: Deals &amp;038' More: Scenechronize scores $5M to streamline film production, GlobalTranz raises $10M to optimize the flow of merchandise Previous Story: Can Boingo IPO before 4G and free Wi-fi make it pointlessPrintEmailTwitterFacebookGoogle BuzzLinkedIn      DiggStumbleUponRedditDeliciousGoogleMore&amp;8230'          Tags: codecs, H.264, web video, WebMCompanies: Google          Tags: codecs, H.264, web video, WebMCompanies: GoogleAnthony is a senior editor at VentureBeat, as well as its reporter on media, advertising, and social networks. Before joining the site in 2008, Anthony worked at the Hollister Free Lance, where he won awards from the California Newspaper Publishers Association for breaking news coverage and writing. He attended Stanford University and now lives in San Francisco. Reach him at anthony@venturebeat.com. (All story pitches should also be sent to tips@venturebeat.com) You can also follow Anthony on Twitter.VentureBeat has new weekly email newsletters.  Stay on top of the news, and don't miss a beat.<br/><br/>0 Vote(s) ]]></description>
</item>

</channel>
</rss>
