Want to play games on your Playstation but got a deadline for an exam or report that didn’t match your gaming ambitions?

Then you have come to the right place.

Send trashed files and blame your faulty computer, instead of confessing that you are a lazy bum who just wants to play videogames.

Launch of Webreakdigg!
July 26th, 2006

This is gonna be a piece of internet history. Why? because this post pens the very first page of Webreakdigg, the social news blog of 200 strong. What exactly is Webreakdigg. We are recruiting, yes, we are looking for 200 strong to join Webreakdigg blog network. Webreakdigg is conceived from the fact that Digg is broke. Why is Digg broke? Read here, here, here and here and you will know why.

So what has Digg gonna do with WebreakDigg, as the name implies, we are gonna break digg and in hope to bring a new wave of social news to the rest of the world that believes in what Digg do not believe in.

So how do I join the Webreakdigg network? Simple, you need to first of all have a blog, two, you need to sign up for a Digg account or if you have one already that’s fine. Wait a minute, I thought we are anti-digg? Nope, we are not anti-digg, we are only here for the rest of the world that do not believe in digg.

Welcome to the playground of one Mr Paul Neave, serial Flash fettler and interactive activist.

http://www.neave.com/

Dependency Walker is a free utility that scans any 32-bit or 64-bit Windows module (exe, dll, ocx, sys, etc.) and builds a hierarchical tree diagram of all dependent modules. For each module found, it lists all the functions that are exported by that module, and which of those functions are actually being called by other modules. Another view displays the minimum set of required files, along with detailed information about each file including a full path to the file, base address, version numbers, machine type, debug information, and more.

Dependency Walker is also very useful for troubleshooting system errors related to loading and executing modules. Dependency Walker detects many common application problems such as missing modules, invalid modules, import/export mismatches, circular dependency errors, mismatched machine types of modules, and module initialization failures.