About This Site

This site documents one small Windows program, as accurately as we can manage.

That sounds like a modest goal. In this particular corner of the web it turns out to be an unusual one, which is the reason the site exists.

Why it exists

Because the software stopped being developed years ago, and the writing about it did not stop being copied.

When a program is no longer maintained, nobody corrects what is written about it. Descriptions drift. One person guesses at a detail and somebody quotes them. A few years later the same wrong sentence appears on a dozen pages, with growing confidence. Meanwhile the program sits there, unchanged, quietly disagreeing with all of it.

We found several examples while building this site. Interfaces described with buttons that do not exist. Keyboard shortcuts that do nothing. A download panel serving a different company's paid software under this program's name.

None of that required investigation. It required downloading the file and opening it.

Who writes here

Nathan Cole writes the pages on this site.

The short version, which appears at the bottom of every guide, is this: every version is downloaded, run on a clean Windows install and checksummed before anything is published about it.

That is a description of a method rather than a set of credentials, and that is deliberate. Credentials cannot be checked by you. The method can, because its results are on every page. The screenshots are of the actual program. The checksums can be reproduced on your own machine. The things we have not tested are labelled as untested.

You should judge this site by whether its claims hold up, not by anything claimed about the person writing them.

How a fact gets onto a page here

Four rules, applied to everything.

It gets verified before it is written, not after. If something cannot be confirmed while a page is being written, it stays out of that page. There is no list of things to check later. That list would never be finished.

Screenshots are of the real program on a real machine. No images taken from other sites, no mock-ups, no illustrations standing in for the interface.

Files are downloaded and hashed. Every file this site serves is measured and checksummed, and the checksum is published so you can reproduce it.

Anything unverified is labelled unverified, on the page. Several pages here say plainly that we have not tested something. Those sentences are not filler. They mark the boundary between what we know and what we would be guessing at. That boundary is often the most useful thing on the page.

What we will not publish

Five things, and each has cost us something.

Numbers we cannot source. Antivirus detection counts, memory figures, file size ranges for compiled output, download totals. These appear everywhere in this niche and none of them comes with a source.

Invented rankings. Where we have not tested tools ourselves, we group them by what they are for rather than scoring them. A ranked list would get more clicks and would be worthless.

Instructions for breaking rules. Nothing about automating games against their terms of service, nothing about avoiding detection, nothing about getting around controls that somebody else set on a device.

Any claim to be official. This site is independent and has no connection with the program's developer. It says so in the footer, on the download page, and on the disclaimer.

Files we cannot verify. If we cannot download something and compute its checksum, we do not host it. That rule is why the with editor downloads are described here but not served.

What we do host

Program downloads, each published with its exact size and checksum.

They are provided directly, without passing you through a chain of download portals. Their checksums let you verify them without taking our word for it.

If a checksum changes it is not published automatically, it is flagged for a person to look at. The versions page explains why that distinction matters on software that is no longer being built.

When we get something wrong

We will, and here is what happens then.

Corrections are made on the page rather than quietly. Where a claim has been reversed, the page says what changed and why. Several pages here already carry that history, because a reader who told us we were wrong was right.

That has happened during this site's own construction more than once. The most significant finding here came from somebody downloading a file and noticing it was not what the label said. We had looked at the same download and failed to open it.

If something here is wrong, tell us. A specific correction with something we can check is more valuable than any amount of praise.

How this site is paid for

Advertising. There are ad units on these pages and they are how the work is funded.

Advertisers have no say in what is written. Nothing here is sponsored. No product on this site was paid for by anyone, and we take nothing from any tool we name. Where we recommend something, it is because it fits the reader's problem.

Our position on trademarks, authorship and licensing is set out on the credits page.

Getting in touch

The contact page has a form and an address, along with how long a reply usually takes.

Corrections are the most useful thing you can send. Screenshots of behaviour that contradicts something written here are better still. Several pages on this site exist because somebody sent exactly that.