<?xml version="1.0"?>
<rss version="2.0">
    <channel>
        <title>OpenRCE: Blog</title>
        <link>http://www.openrce.org/rss/feeds/blog</link>
        <description>OpenRCE: The Open Reverse Code Engineering Community</description>
                <item>
            <title>The OllyDbg 100 percent CPU problem - and its solution</title>
                            <pubDate>Mon, 11 Feb 2008 15:11:52 -0600</pubDate>
                                        <link>https://www.openrce.org/blog/view/1057/The_OllyDbg_100_percent_CPU_problem_-_and_its_solution</link>
                                        <author>dELTA &lt;email-suppressed@example.com&gt;</author>
                                                    <description>A problem in OllyDbg 1.10 is that it takes up 100% CPU as soon as it's debugging a target and the target is running on its own (i.e. after pressing F9 in OllyDbg at some point).&lt;br /&gt;
&lt;br /&gt;
If nothing else, it causes any laptop that you might be reversing on to lose much more battery life than necessary, and also to sound like a jet plane due to constant maximum fan rotation.&lt;br /&gt;
&lt;br /&gt;
The problem was discussed, analyzed, found and solved (by means of an OllyDbg patch) over at the RCE Forums earlier today, and I can recommend at least anyone who normally reverses on a laptop to take a look at it:&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://www.woodmann.com/forum/showthread.php?t=11302&quot;&gt;http://www.woodmann.com/forum/showthread.php?t=11302&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
The solution has also already been packaged into an OllyDbg plugin (by blurcode), which you can find in the Collaborative RCE Tool Library, at:&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://www.woodmann.com/collaborative/tools/index.php/CPU_Initialization_Patch&quot;&gt;http://www.woodmann.com/collaborative/tools/index.php/CPU_Initialization_Patch&lt;/a&gt;</description>
                    </item>
                <item>
            <title>PaiMei tutorials for those interested</title>
                            <pubDate>Fri, 04 Jan 2008 04:31:58 -0600</pubDate>
                                        <link>https://www.openrce.org/blog/view/1014/PaiMei_tutorials_for_those_interested</link>
                                        <author>dELTA &lt;email-suppressed@example.com&gt;</author>
                                                    <description>For those interested in getting kick-started with PaiMei, Ricardo Narvaja has recently written a series of tutorials for it, which are all available here:&lt;br /&gt;
&lt;br /&gt;
http://www.woodmann.com/forum/showthread.php?t=10851&lt;br /&gt;
&lt;br /&gt;
They are sadly only available in Spanish, so if anyone would have the possibility to translate them, they would become useful to even more people.&lt;br /&gt;
&lt;br /&gt;
Does anyone know of any other good PaiMei tutorials or information in addition to the rather small amount of documentation that is officially available by the way?</description>
                    </item>
                <item>
            <title>A very special xmas present for the RCE community: The Collaborative RCE Tool Library</title>
                            <pubDate>Mon, 24 Dec 2007 20:39:51 -0600</pubDate>
                                        <link>https://www.openrce.org/blog/view/1005/A_very_special_xmas_present_for_the_RCE_community:_The_Collaborative_RCE_Tool_Library</link>
                                        <author>dELTA &lt;email-suppressed@example.com&gt;</author>
                                                    <description>Today, on christmas eve/day (depending on where in the world you are located) of 2007, the RCE forums community and the Woodmann crew present a &lt;b&gt;very&lt;/b&gt; special christmas present for the entire RCE community world wide, which will hopefully from now on be a great addition in the arsenal of every reverser.&lt;br /&gt;
&lt;br /&gt;
Allow me to present, the precious labor of my hard work during most of my spare time throughout the larger parts of this past year:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Collaborative RCE Tool Library&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://www.woodmann.com/collaborative/tools&quot;&gt;http://www.woodmann.com/collaborative/tools&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
So, what is it? Its goal is to be the end of all other tool libraries, the only tool library any reverser will ever need, and also &lt;b&gt;the&lt;/b&gt; tool library that &lt;b&gt;all&lt;/b&gt; reversers will collaboratively help to populate, maintain and refine, continuously. Its goal is to always contain &lt;b&gt;all&lt;/b&gt; interesting and useful RCE tools, in a highly organized and categorized fashion, where the tool you need for the moment is never more than the traversal of a category tree away.&lt;br /&gt;
&lt;br /&gt;
Not only this, but for each tool, &lt;b&gt;everyone&lt;/b&gt; is able to contribute with tips about usage, other resources, rare inside information, gossip, and &lt;b&gt;anything&lt;/b&gt; else that may be of value to the community or anyone else interested in RCE tools. And the main feature, which is of course also exactly what will make this so good, is that &lt;b&gt;everyone&lt;/b&gt; will be able to help, &lt;b&gt;in a very simple and efficient way&lt;/b&gt;!&lt;br /&gt;
&lt;br /&gt;
Allow me next to quote some further descriptive text from the main page of the Collaborative RCE Tool Library itself, in order to shed some more light on just exactly what it is:&lt;br /&gt;
&lt;br /&gt;
--------------------------------------------------&lt;br /&gt;
In the Collaborative RCE Tool Library, anyone can instantly add, edit or update information about all their favorite tools (and under some conditions even upload the tools themselves). All with the personal and highly useful goal of being able to easily find these tools whenever they may come in handy in the future.&lt;br /&gt;
&lt;br /&gt;
The advantage of the collaborative nature of the library is of course that if lots of people update the information about their personal favorite tools whenever they hear about an important update to any of these, everyone else will also be able to benefit from this information when they come here looking for information about good tools for any specific purpose.&lt;br /&gt;
&lt;br /&gt;
Add to this a highly granular and efficiently hierarchicalized structure of &amp;quot;category tags&amp;quot; (a tool can be tagged into arbitrarily many such categories, where the category hierarchy itself is controlled by administrators, but is still highly influenced by user suggestions through the Needs New Category category), and you have the recipe for what we believe is the future of information collection, archival and indexing, and the ultimate way to maintain updated information about any certain isolated field of interest (in this case RCE tools). If you would give the whole concept a fancy name, it would probably be something like &amp;quot;a Collaborative Strictly Hierarchical Just-Enough-Moderated Semantic Information Library&amp;quot;, where the &amp;quot;Strictly Hierarchical&amp;quot; and &amp;quot;Semantic&amp;quot; parts are what separates it most from a common wiki, in addition to the drastically improved ease of use and contribution.&lt;br /&gt;
--------------------------------------------------&lt;br /&gt;
&lt;br /&gt;
So please, go take a look, read through the information on the main page, explore the library, populate it with any tools that aren't already there, rate all the tools you have personal experience with, subscribe to the RSS feeds of all categories that may interest you (or why not the RSS feed for the entire library!) and enjoy the benefits that the library and the collaborative work of the entire RCE community can bring you from now on!&lt;br /&gt;
&lt;br /&gt;
Regards,&lt;br /&gt;
dELTA&lt;br /&gt;
&lt;br /&gt;
PS.&lt;br /&gt;
Since the search feature of the library is Google based, it will not work well until after a few days/weeks from now, since the project has been held a secret until today, and thus Google hasn't been able to index it yet.</description>
                    </item>
            </channel>
</rss>
