Sunday, February 29, 2004

, ,

File sharing & the law

What is the law regarding the sharing of copyright protected software?

By downloading and using commercial software you haven't paid for, you are breaking the law. It is as simple as that. To use retail software legally you must first purchase a license for it.

Incidentally, all software, retail or freeware, is copyright protected material - from the moment of its conception, software is protected by federal copyright law and hence cannot be legally reproduced without first obtaining permission from the author. Clearly if a piece of software has been released as freeware by its author, you are entitled to download and use it. That said, unless it has been designated as 'open source', you cannot modify and re-release it.

In the United States the use and distribution of computer software is governed by title 17 of the copyright act, which states that the author is granted exclusive rights to reproduce and distribute his or her creation. Anyone who violates the author's exclusive rights by making their work available to the public by whatever means, for free or in exchange for payment, is breaking the law, and if caught, can be prosecuted by imprisonment or fine.

But I'm allowed to duplicate my software if I've purchased it legitimately, right?

You are legally entitled to produce a single copy for backup purposes only, but no more than this. The software can only be installed and used on a single computer if you wish to remain within the confines of the law. This aspect of the copyright act is covered in section 117.

What exactly are the penalties for distributing copyright protected software?

The first thing which is likely to happen if you are caught is that any profits made from distributing the software and/or the equipment used to make duplications will be confiscated. You are also liable for compensating the author of the copyright protected work for any losses they may have sustained up to the value of $100,000 per title. In a worst case scenario you could be forced to pay a fine anywhere up to $250,000 or be ordered to serve a prison sentence of up to 5 years.

Doesn't the law state that I'm permitted to evaluate software for up to 24 hours if I delete it afterwards?

No, this is a myth circulated by file sharing webmasters who believe they can deflect liability for serving copyright protected software to the public. This nonsense is often written into disclaimers which must be agreed to before permitting visitors to enter a site, but doesn't provide any legal protection whatsoever.

Even if you delete the software having 'test driven' it, and subsequently purchase a legitimate copy, you could still face prosecution for infringing copyright laws as defined in section 501(a) of the copyright act.

Using and distributing abandonware is OK though, isn't it?

Nope, I'm afraid not. 'Expired copyright' software doesn't exist - the same rules which apply to 'liberated' commercial software also apply to abandonware - the law doesn't differentiate between the two forms of piracy.

The people who run abandonware sites get away with distributing old software titles simply because the software producers are no longer making any money out of them and so are reluctant to press charges. Fighting piracy is an expensive business; if there are no financial gains to be made from having these sites shut down, there is little incentive to do so.

No piece of computer software on the planet has been around long enough for its copyright to have expired. Any work created after 1978 is protected under section 302 of the US copyright act for the duration of the author's life plus an additional fifty years, or for seventy years following the creation of the software under European law.

I can't be prosecuted for merely linking to commercial software stored on other people's servers, which I personally did not upload, can I?

Yes, you could. You can be held accountable for doing anything contributing to the violation of copyright laws. This includes linking to files via direct download pages, facilitating engagement in criminal acts by way of advice, writing tutorials etc, posting eDonkey hash codes on web forums and so on. Prosecuting people for committing relatively modest misdemeanors such as these was at one time totally unheard of. In more recent times, however, now that anti-piracy groups are determined to make examples of anyone from 12 year old girls sharing a handful of files to career pirates, it is becoming much more common.

Friday, February 27, 2004

, ,

Windows updates made easy

If you are running Windows XP and are at all concerned about the security of your computer you will be well aware of how important it is to install all the critical updates made available by Microsoft. Every few months a new flaw is discovered in the code, which if not patched quickly could result in a malicious hacker gaining access to your system and wreaking havoc. One major bug which was unearthed recently meant that you could have your entire c: drive wiped out if you were unlucky enough to click on a specially formed URL. All I can say is ouch!

Normally you would plug the holes with these band aids in an incremental fashion as and when they are released using either Window's auto-update feature or by downloading the patches to your hard drive via the Windows download catalogue to be installed later. Nonetheless, every so often Microsoft gathers together all the patches they've released up until a specific cut off date and combines them into what is known as a service pack. These are single, self-contained files that can be downloaded free of charge from the Microsoft home page and installed in the same way as any other executable program.

Eventually there will come a time when it becomes necessary to make a fresh installation of your Windows operating system. This is the perfect opportunity to merge the service packs with your Windows installation files so that your operating system will be fully patched the first time you boot into Windows. This technique is known as 'slipstreaming' and the process, you'll be pleased to hear, is as simple as copying a few short commands into your run box.

In the following example I'll use service pack 1 to demonstrate the procedure. First of all, move the service pack to the root of your c: drive and create a new folder, again in the root of the c: drive, called SP1 - using this default arrangement will allow you to follow my directions exactly so there is no margin for error. You will now need to extract the contents of SP1 to this new folder. To do this, press your start button, select 'run' from the menu and type the following command into the dialog box...

C:\XPSP1_EN_X86.EXE -U -X:C:\XP1

Now create the folder C:\XP and copy the contents of your Windows XP installation CD to it. The next step is to combine the two folders together like so...


Once the XP1 files have been integrated with your Windows XP installation files you can proceed to re-install Windows using a DOS boot disk. You will find more information on how to go about this in my Ghost tutorial. Of utmost importance at this stage is to note down your serial number. You will be asked to enter this close to the end of the installation procedure - if you don't know what it is you will have to reboot to get access to it. Doing this obviously requires you to retrace your steps from the beginning, something I'm sure you'll want to avoid.

Thursday, February 26, 2004

Operation Buccaneer fallout continues

On 26th March, Sean Michael Breen, leader of prolific piracy group Razor 1911, will begin serving a 50 month prison sentence following his conviction for the crime of copyright infringement. It is thought that during his reign as the head honcho of the oldest internet piracy group, Breen was responsible for cracking and distributing half a million dollars worth of software. He is the last in a long line of prominent 'scene' members to suffer the backlash of Operation Buccaneer, the mother of all anti-piracy initiatives coordinated by US Customs and the Department of Justice.

Formed in October 1985 by three Norwegians, Razor 1911 initially focused their attention on releasing demos and cracking games for the *cough* Speccy was better *cough* Commodore 64.

As technology evolved, so did they; in 1988 the group adopted the legendary Amiga platform and the demos and cracked games continued to gush into the computing underworld in epic proportions.

Another technology shift in the early 90s sparked the group's transition to the PC scene where they specialised in the release of game rips, and later full CD images. Until recently they could be considered a runaway bootleg software-releasing juggernaut.

Of all those prosecuted as a consequence of the 14 month sting, Breen received the longest sentence, largely due to his involvement in a separate scam pertaining to the fraudulent acquisition of hardware. By impersonating the owner of a legitimate trading account, Breen was able to order over $690,000 worth of goods from Cisco Systems and have them delivered to the premises of a fictitious company. He may now regret flogging this computer kit on the grey market at knock-down prices bearing in mind that part of his recompense will entail reimbursing Cisco Systems for the full amount on his release from prison!

Breen was rumbled for his foremost transgression, the illegal distribution of retail software, on discovery that he had been posing as a reviewer for a non-existent online games magazine so as to procure pre-release titles.

A recent Game Spot article covering the outcome of Breen's trial asserts that he was convicted for illegally selling and distributing software, while other online news sites make no mention of money changing hands, at least where the software was concerned. This appears to be more of an assumption made on Game Spot's part than an undisputable fact, one likely to have arisen from the difficulty many people in the gaming industry have with believing that anyone would jeopardize their personal freedom to distribute software without garnering material gain.

Razor 1911 have always, at least in their release (aka nfo) 'broadcasts', urged end users to support software authors by buying their products. Nevertheless, whether or not they adhered to their own advice remains a hotly debated topic. Despite publicly condemning "those who would profit from the scene", namely ISO News in particular, Razor 1911 are known to have, in their early days, gladly accepted payment for access to their BBS sites and DAT tapes as well as selling group merchandise including t-shirts, so who knows what the truth is? It would seem odd to many that anyone would insist on upholding the scene 'code of conduct' while at the same time ripping off Cisco Systems for the tidy sum of $690,000. The plot thickens...

Monday, February 09, 2004


Forum construction by numbers

OK, so you've got you're own web site, but how do you get people to keep coming back to it, or in web lingo how do you make your site 'sticky'? One of the best ways perhaps is to create your own community bulletin board where people can gather together and discuss whatever is on their minds. Providing your visitors contribute to it, your site will always have new content and this will give people a reason to check in on a regular basis.

Building such a community presence doesn't have to be a difficult or costly affair. If you haven't got much time to spare, or you aren't feeling particularly adventurous you can have a customised ezboard up and running in under ten minutes. These are designed for people who haven't got a server of their own or don't want the hassle and expense of finding a virtual host from which to run their board. They are also a good option if you haven't got the technical know-how necessary to set up a completely 'do it yourself' board such as Ultimate Bulletin Board or vBulletin. If you're going to go down this route, open up the home page in a new window and click on the 'create your own community' button to get started. Once you have chosen a username and password, the obligatory name, address and phone number nags will surface. Quickly fill in the blank fields with the first thing that comes to mind. Mickey Mouse at Disney Land will do if you're stuck for ideas. Fill in the rest of your details and click on the 'create my community' button. There really isn't much more to it than that!

In a similar vein, you could pay Forum Co a visit and let them set up a remotely hosted version of Snitz for you. This is a lesser known, though a very well designed forum which normally has to be set up manually if you download it from the creator's home page. This is one forum script I wouldn't advise you to attempt to run from a free server, not because it's difficult to set up, but because dependable, free ASP hosts are so difficult to find. If when you see Snitz in action it's love at first sight, either let Forum Co. host and manage it for you or bite the bullet and pay for a real host. If your heart is set on using a remotely hosted board, the best place to survey the options available to you is the remotely hosted bulletin board section of

Searching for a host and other considerations

On the contrary, if you're confident that you have the ability to set up what the BB connoisseurs would call a real board, you can begin exploring the various hosting options available to you. This being a freebie web resource site you wouldn't expect me to espouse the merits of finding a paid host, yet in this instance you really do get what you pay for. As with anything on the net, if you look hard enough, you can find it for free, nevertheless, just because something is free it doesn't necessarily mean you're getting a good deal. Free hosts are fine for running very small, low traffic boards with just a handful of members, but as soon as your board takes off, you will find that the services on offer are too restrictive to allow your board to reach its full potential. A good place to weigh up all the available options and read impartial customer testimonials is the Web Hosting Talk forum. If you need convincing further that paid hosting is the way to go, visit the home page of a free host and see what is on offer, then compare these features with the ones provided by a paid host. I think you'll agree that the extra expense is worthwhile in the end.

When you're looking for a host to store the HTML files of your web site, pretty much anything will do, however, when you're looking for a home for your bulletin board you have to be a bit more selective. Your requirements will vary depending on which board you have chosen to set up so make sure you have made this decision before going host hunting (see below for my advice). For example, UBB and Ikonboard consist of CGI code, vBulletin is written in PHP, whereas Snitz is coded in ASP. It isn't really necessary to know anything about these different scripting languages at this stage, just keep in mind that to run a CGI board you will need a host that supports CGI scripts, to run a PHP board you will need a host that supports PHP, and so on. Don't worry, you don't have to be Sherlock Holmes to find out exactly which script languages your host supports. This information will always be displayed in a prominent position on host home pages since they are such highly sought after features.

As I said earlier though, before doing anything, your first step is to decide which board you are going to use since this will determine the type of host you require. The great divide between the various options is culminated primarily by your finances. Some boards are completely free; Snitz, YABB and Ikonboard for example, yet the license for others will cost you anywhere in the region of ten dollars to thousands of dollars.

Obtaining illegal versions of commercial forum software is child's play - even so, I wouldn't advocate their use. I stand by my belief that fairly-priced, quality software should be paid for in support of the hard-working and talented developers. I can't stress enough that if you're determined not to have to pay for your forum script, look into the free alternatives linked above rather than resorting to piracy. Moral issues aside, if you use stolen scripts, unless you're going to hide them away under a shroud of private login screens, sooner or later someone is going to find out what you're up to and notify the relevant authorities. If you get caught using a board without a license, the FBI aren't going to come knocking at your door with a warrant for your arrest. Still, what the authors of the forum software can do is contact your host and have your account terminated. Bye-bye posts, member profiles, templates, settings and so on.

While we're on the subject of being rumbled for using an unlicensed board, being caught isn't simply a matter of waiting for some busybody with too much time on his or her hands to come along and report you. Script writers are now taking a much more proactive approach to fighting piracy and often incorporate 'phone-home' code into their scripts to help monitor their use. For instance, some unlicensed scripts on first being installed automatically fire off an email to the script creator's piracy department to inform them of your misdemeanor. Nevertheless, determined not to be outwitted, pirate release groups painstakingly analyze this code for any phone-home references and strip them out before releasing their own doctored version of the script to the public; a process akin to cracking a game or application.

What I've come to realise is that you don't always get what you pay for in the world of bulletin boards. For instance, UBB will set you back $250 plus annual renewal fees and yet is extremely basic when viewed alongside Ikonboard for example, which is free. With UBB you really are buying the bare bones of a bulletin board. If you want to add the simplest of features to it such as the 'last post by...' message, for instance, you have to do it yourself by editing the CGI files (known as hacking). This isn't a complicated procedure, but is quite time consuming and for $250 you would expect these features to come as standard.

On the other foot (I've run out of hands now!), Ikonboard, YABB and Open BB, for instance, are completely free and can do everything that some of the more expensive boards can and more besides. phpBB and Snitz are also freebies, but you're going to have a much tougher time trying to find a reliable, free host that supports boards coded in PHP or ASP. You will find that many ASP hosts, for example, won't support FTP (which is an absolute necessity in my opinion), will have limited web space available and will suffer ridiculous amounts of downtime.

If you want my advice, Invision Power Board is the star pupil amongst the free boards so grab that instead. If money isn't an issue, however, or you have plenty of loyal members who would be willing to make a donation towards the cost of purchasing a professional, commercial script, vBulletin is the only one worth considering. It is far more reasonably priced than UBB, is backed by an extremely progressive development team and a support network which is second to none.

To download a free bulletin board (or at least the set up files), all you have to do is find the download section of the home page and click on the compressed archive file (in most cases it will be smaller than 1mb so you won't have too long to wait). Downloading a commercial script obviously will not be possible until you have been granted member status and this will inevitably involve submitting your credit card details.

If you can't afford to pay for a real host (or you're just a big cheapskate!), the best place to find a free host for any purpose is always, so make your way over there now. OK, click on the 'advanced search' button and tick the relevant boxes as you did in the preceding web design tutorial. Let's assume we're throwing together a CGI board. In this scenario, the fundamental option is going to be CGI support so tick this box first. If you were setting up an ASP or a PHP board you would need to look for a host, which in addition to supporting these file types, also supports MySQL (or one of the lesser known) databases. There is no 'database' tick box at FWS so you will have to gather this information yourself from the host home pages instead.

When you require more advanced hosting features such as these, you can't afford to be as fussy as we were in the web design section so don't automatically assume that you will be able to find a bannerless host that also supports FTP. What is more important is server reliability and the number of megabytes of web space a host has to offer. Anything less than twenty and you would be better off looking elsewhere. The installation files of the board will occupy minimal space, but a reasonably active board can soon expand and get out of control if not regularly pruned. You don't want to have to uproot the whole thing when you realise you haven't given yourself amble breathing space so make sure you pick the host with the most (megabytes that is) from the outset, all else being equal of course. In the usual way, follow the links, compare all the offers until you find the one that suits you best and sign up for a free account.

When you've made your choice, the next thing you need to do is find out whether your host is using Unix or NT servers - this information will often have to be added to various setup files before you can proceed any further. You can find this information by either browsing through your host's FAQs or you can visit and perform a 'Who Is' lookup (click on the 'what's that site running?' button, type in the web site address of your host and make a mental note of the result).


Now find the compressed archive file you downloaded earlier and extract it using the 'extract with full path' parameter. This ensures that all the files arrive safely in the correct folders. Find the readme or install file and open it; this will give you step by step instructions for setting up your bulletin board. These will be specific to your chosen board, but will share many common features. For a start they will all require you to upload the files contained within the compressed archive to specific directories using either an FTP client or your web browser. To make things simpler for yourself I would recommend that you use the folder names suggested in the readme file. For a CGI board, for example, the files with a CGI extension need to go in your 'cgi-bin' directory (if it isn't already there you will need to create one) and everything else usually goes in the 'non-cgi' directory (or equivalent). It isn't essential that you use these folder names - as long as you 'tell' your board where you've put everything later on, it will run fine wherever you store it, nevertheless it is much simpler to stick to the default settings.

You must upload graphics files in BINARY mode and everything else in ASCII mode. To change these settings look for a 'transfer mode' option in the menu bars of your FTP client and click on either the A or the B button before beginning any transfers. Note that sticking with the 'automatic' option doesn't always get the job done. If once you have installed your board, the graphics look distorted or the script files (the ones with CGI, ASP or PHP extensions) fail to appear in your browser, more than likely you will have uploaded them using the wrong transfer mode. If so you will have to re-upload them and try again. Just a quick note regarding web based uploaders/file managers before we move on - if you are setting up a CGI board and your online uploader won't allow you to predetermine the transfer mode or change the CHMOD settings of your files you're not going to be able to proceed, in which case you will have to find a more flexible host, or even better, one that provides a real FTP account.

Another aspect of installing a bulletin board which is common to all CGI (but not all ASP or PHP) varieties is setting the CHMOD or permission settings. Again this is essential so make sure you pay attention to what the readme file instructs you to do. Once set, these either restrict or permit remote or local access to the files and folders on your server. This can be done using any FTP client and the procedure is as follows: login to your FTP account and highlight the files or folders you wish to modify. Now right click somewhere in the selected area and find the 'change permission attributes' option. After clicking on it, a menu will appear containing six tick boxes, a single dialogue box containing a three digit number or both. As you put a tick in the boxes notice that the number in the dialogue box (if there is one) changes. This is because you can set your CHMOD settings using either method. For example, ticking all six boxes is the equivalent of entering 777 into the dialogue box.

Now you are aware of this, you will soon get to know which tick configurations produce which three digit codes. You will find that any files or folders which need to be writable from your (and your visitor's) web browser should be set to either 755 or 777, but again refer to the specific instructions for your board. The reason these changes weren't necessary when you set up your main web site is because more than likely it contains no dynamic content and therefore doesn't need to be remotely modified. A web page is only dynamic if it allows you or your visitors to contribute to its content using a web browser. A few examples include guest books, free for all links pages, shout boxes, polls, and bulletin boards of course.

Assuming all your files have been uploaded to the correct locations and have been CHMOD-ed properly (for CGI boards) you can disconnect from the FTP server and run your board's installation file from your web browser (this will usually be called install.cgi, install.php or install.asp). If at this stage your browser displays an 'internal server error' message you will have to check your permission settings and make sure you have uploaded your files using the correct transfer mode and try again. If everything goes according to plan you will be whisked away to your admin centre where you will be prompted to choose an administrator username and password - this is the account you will use to make any changes to the board from your web browser. Before being allowed to create any forums or categories for your board you will have to provide a few details regarding the configuration of your server. For CGI boards, the first of these is likely to be the absolute path to your server's Perl scripts. Perl isn't something you yourself have to install. It will already be there, ready and waiting to jump into action providing you have chosen an appropriate host. Your task is simply to find out where they are located. Very often the install file will guess this information correctly, but if not you will have to ask your host to help you or read through the FAQs on their home page. Note that absolute paths do not contain an HTTP or a WWW prefix - you are dealing with plain directories here, not web site addresses. The next question will probably be "is your host using a UNIX or an NT server?". If you were paying attention earlier you will already have this information to hand. If not, shame on you! - go and stand in the corner and put the dunce hat on your head. You will also need to set the location of your cgi-bin and non-cgi folders as well as some of the files contained within them. Just follow the instructions to the letter and you can't go far wrong.

When setting up a PHP or an ASP board many of the same principles apply, yet certain other idiosyncrasies are clearly evident. As I mentioned earlier, a prerequisite of setting up PHP (and most ASP) boards is that you find a host which supports MySQL or an equivalent database. Don't worry if this term is unfamiliar to you, all you need to know at this stage is that a database is where all your board's configuration details, posts and member profiles will be stored on your server. This is the most salient feature of most PHP and ASP boards; they use databases as opposed to the flat file systems utilised by the vast majority of CGI boards. With flat file boards, all the board's files are stored in directories which are easily accessible via an FTP client. In contrast, to access the data of a board which uses a database 'backend' you have to login to a server-side GUI and browse through the tables using a script known as phpMyAdmin (other interfaces are sometimes used in its place, though this one remains the most popular). Although there are many differences between the two systems, the most noticeable one is the time it takes to load threads, post messages, search the board and so on. In this department, boards which use a database backend tend to be much faster than the more traditional, outdated even, flat file boards. Any Perl expert will tell you that a CGI board, if well written, should be just as fast as its PHP equivalent, nonetheless in reality this rarely seems to be the case. I'll let you conduct your own research to discover the remaining, less subtle differences.

To get started you will usually have to make a few changes to your config.php or config.asp file. As with CGI files these can simply be opened using any old basic text editor (Notepad will do the job very nicely). Before proceeding any further you will be required to add or modify such entries as the location and name of your database and the username and password used to access it. Once executed, the config file will attempt to connect to the database and make the necessary changes. If it is unable to do this you will have to ascertain whether or not you have permission to access the database on your server and that you have modified the config file correctly. If everything goes according to plan, however, you should be greeted by a welcome screen from which you can proceed to set up your board. When you are happy with your board's fundamental settings, before doing anything else, make sure you delete the installation file from your server so that it cannot be tampered with by malicious users. The same goes for any upgrade script files you may have uploaded along with the rest of the package.

Getting back to files and folders though, don't be too concerned with getting these locations wrong at first as you can always go back and correct them later. More than likely you will be alerted to any mistakes so that you can put them right. When your board's setup routine is satisfied that you know where everything is stored it will let you proceed to the forum control area where the customisation work begins. For now, making it look pretty isn't crucial. The first thing to do is to create a few forums to see if they are writable. OK, done that? Great, now open your board in a new browser window, login using your username and password and try to submit a new thread. If you are able to post, you must be doing something right. If not, check those permission settings again... and again and again (is there an echo in here?) until your board does what it's told.

Customizing your forum

When your new creation is behaving itself, the final stage is to personalise it, give it a splash of paint, add some hacks and generally spruce it up until it starts to resemble something vaguely like a bulletin board.To implement hacks you will need to visit a hacks/mods repository. These are specific to your particular board so any old hacks site won't do. The best UBB hacking site is the UBB Developer's Network, is the numero uno place to track down hacks for vBulletin, while IB Supported is your best bet for their Ikonboard counterparts. If Invision Power Board is your forum script of choice and you intend to install a hack or three, Invisionize is worth a look. More of a phpBB nut? Check out phpBB Hacks.

The concept behind board hacking is very simple; it involves finding a new feature you're interested in adding to your board and then modifying your script files, templates or database to accommodate the changes. Hacks can consist of either an instructional text file plus some extra library or script files or just the text file on its own. While hacks are straightforward to implement, what you have to remember is that you can only install a particular hack if it was designed to work with the board version you are currently using. For instance, a hack written to work with Any-Old BB 1.0 will not necessarily work with Any-Old BB 2.0 because numerous code rewrites will very likely have taken place during the migration from one version to the next. For this reason it is essential that you check that the hack you wish to use is compatible with the board you are running before continuing any further. You can find out which version you are using by looking at the copyright information at the bottom of your board (known as the footer).

Once you have downloaded a hack, the first thing you will need to do is upload any additional files to your web server. The next step is to edit the original script files which you should be maintaining copies of on your local hard drive. I would strongly advise you not to use your usual HTML editor for this task because many of them assume they know best and will add inappropriate or superfluous code to the scripts, only to give you headaches later on. Instead use Notepad, Wordpad or another non-intrusive, plain text editor. When you're all set to make the changes, open the readme file which came with your hack and follow the instructions. Some of these will direct you to find certain lines of code and substitute them for modified variants, whereas others will require you to leave the existing code alone, but append extra code before or after it. A quick way to locate particular portions of code is to use the 'find' option of your text editor, which you can access by pressing 'control' and 'f' simultaneously.

With the script file alterations taken care of you may now be required to make changes to your templates. These can be accessed using your admin control panel - if you're lucky your forum script will include a template search engine to make finding the relevant code easier. Templates, being constructed using plain text, can be modified using the same techniques outlined above.

More complex, 'major addition' hacks may require you to modify your database. This is carried out by running SQL queries from within your phpMyAdmin GUI. It sounds more complicated than it is - really what it amounts to is copying and pasting commands into a dialog box and pressing the submit button to action the changes.

After completing all the stages listed in the readme file, retrace your steps to make sure you've followed the instructions down to the last letter. When you're satisfied that you've carried out all the required stages correctly, save your modified files, re-upload them using your FTP client and visit your board to check if the changes have been implemented correctly. If things start to go haywire you will have to replace the modified files with the original ones or revert the templates you have edited and go back to the drawing board.

I strongly recommend that you keep a log of exactly which files, templates and database tables you have modified so you will be able to reverse the changes later if you decide to uninstall the hacks or re-apply new versions of them. If you don't you could end up with the kind of mess the Windows registry gets into when useless entries are left behind. Worse still, previous code modifications you have long since forgotten about could conflict with new ones you wish to make.

If after all this tweaking you still don't like the way your creation looks remember that you can replace any of the default graphics with ones of your own. You can find bulletin board icons, buttons, avatars and logos in the same places as the hacks we discussed earlier. All you have to do to make the switch is right click on a picture you would like to change and make a note of its filename. Now get the graphic you want to replace it with, rename it accordingly and overwrite the old file on your server. The next time you refresh the page your newly customised board will be unveiled.

Backing up your forum - better safe than sorry

When your lust for BB eye candy has been satiated, a good idea is to backup your whole board in case it is lost due to server errors, hackers, account deletions etc. This couldn't be easier; if you're using a flat file database system, create a new folder on your hard drive and name it appropriately, the label 'BB Backup' or similar will do nicely. Now login to your FTP server, highlight all the files and folders and download them to your new local folder.

Alternatively, if you're using a board with a MySQL or equivalent database you will have to login to your phpMyAdmin account or Telnet into your server and 'dump' (yes, that's a technical term) the database into a file on your web server. This can subsequently be transferred to your own computer using a download manager and stored in a safe place. If in the future your board requires emergency resuscitation you can re-upload the files or import your database and be all set to continue where you left off, whether it be from the same hosting account or on a different server entirely.

While it is possible to make a forum backup using PHP scripts such as phpMyAdmin, doing it this way isn't recommended for larger databases. This is because, for security reasons, the execution of PHP scripts are set to timeout after a pre-defined number of seconds. If dumping your database takes longer than is permitted by this timeout setting, your backup will be cut short and you will be left with an incomplete, useless file. In the absence of any notification to the contrary, it may seem like everything has gone according to plan. However, opening the file in a text editor can reveal that its size falls well short of what you would expect judging by the reported size of the database in your control panel.

The most reliable means of making a database backup is to use an SSH client such as PuTTY to securely access the remote computer where your forum is hosted and issue the mysqldump command via a console. This takes longer to describe than to actually carry out. The procedure is as follows:-

1. Download PuTTY from the home page linked above.

2. Double-click on its icon to open the GUI.

3. Click on the SSH radio button to place a dot inside the circle (if your host doesn't offer secure shell connections, Telnet will have to do instead).

4. Enter your site's FTP or IP address in the box provided.

5. Use your forum administrator's control panel to close your forum to prevent new information being added to your database.

6. Click on the 'open' button to open a new console window.

7. Enter your FTP password when prompted.

8. Use your FTP client to create a new folder above your publicly accessible folder to store the backup in. If you place it in the public_html folder there is a chance someone could download it and gain access to confidential information or re-use your database without your permission.

9. Type the command...

mysqldump --opt -uusername -ppassword database_name > backupfolder/name_of_backup.sql

...into the command window and press enter. Yes, you are supposed to include a 'u' before the username and a 'p' before the password, these aren't typos.

10. Wait a few seconds until the command prompt becomes available again and then use your FTP client to check that the new file has appeared in your backup folder.

11. Re-open your forum to allow posting to resume.

That's all there is to it. Once you've established which details go where within the above command you can type them into a text file and save it for future use - PuTTY supports the copying and pasting of commands so this should eliminate the possibility of typing errors.

To restore a database you would login to phpMyAdmin, drop (delete) the database you wish to replace (if one exists) and then use PuTTY to issue the command...

mysql -uusername -ppassword database_name < backupfolder/name_of_backup.sql

And now at last the moment you've all been patiently waiting for - go forth and multi... erm, I mean spread the word. Good luck everyone.

Still looking for more bulletin board scripts or resources? Have a look here...

Avatar Vault | AvatarsX | Romany's Realm of Avatars - Avatar's galore!

Big Boards - Ranked listings of the most active forums on the web. Can be re-ordered using criteria such forum script utilized, subject matter covered, number of posts or number of members etc.

Burning Board - Extremely feature packed, free, DIY bulletin board written in PHP. Looks suspiciously like vBulletin. I hope for their sake the code is original!

Brinkster - One of the most reliable and feature packed ASP hosts you're likely to find. Note that Brinkster's free hosting package is only really any use for low traffic sites. They won't place any banners, pop-ups or adverts on your site, but are hampered by a lack of FTP access.

Board Mod - An automated hack integration tool for YABB.

Cute Cast - Free DIY, Perl bulletin board. An excellent choice for those of you without access to a database of any kind as it makes use of a flat file system.

Easy Forum - The best no frills forum script I've ever seen. Perfect for those of you wishing to keep things simple, yet professional. No MySQL database required.

Flame Warriors - Can you resist the temptation to match these stereotypes with your fellow forum members?

Forum Images - Images for ...erm forums. Well I had to fill this space with something.

Forum Insider - I expect you can hazard a guess as to the concept behind this one.

Hot Scripts - Searchable script database. Lists scripts coded in all languages including remotely hosted alternatives.

Ideal Bulletin Board - Self assembly ASP/SQL discussion forum. Pricing structure is laughable - it's great to have faith in your own products, but come on guys let's get real shall we? Remotely hosted option is also in the pipeline. Maybe you could sell a kidney to raise the required funds? :D

Invision Power Board - Certainly one of the forum software front-runners. Written in PHP and utilizes your choice of three of the most popular database systems. Despite appearances, there is a free version available to download. This has been re-branded as a 'free trial' in order to raise the profile of their premium support, licensed alternative yet remains a fully functional forum script. A spin doctor's work is never done, bless 'em. :p

My Smilies - The largest collection of free smilies available on the web.

Open BB - Free, destroy it yourself, PHP bulletin board. Formerly known as Blazeboard.

PHP BB - Free, do it yourself, PHP bulletin board backed by a thriving community and development team. One of vBulletin's most worthy rivals.

Simple Business Machines - Another solid, PHP, do it yourself freebie. Maintained by a talented development team and supported by a substantial user base of loyal fans. Began life as the PHP/MySQL off-shoot of YABB.

Smilies Unlimited - A well organised list of every smilie known to man (or woman). Note that they're of the symbolic text variety, :) for example.

The Admin Zone - Forum administrators unite to discuss how to successfully manage web forums. Full marks for not using the slogan "the bulletin board resource site for admins by admins". ;)

The ASP Resource Index - Searchable ASP script database. Includes descriptions, reviews, ratings etc.

The CGI Resource Index - Searchable CGI script database. Includes descriptions, reviews, ratings etc.

The Perl Archive - Pretty much offers the same features as above, except it's all carried out with much more style and sophistication.

The PHP Resource Index - Searchable PHP script database. Includes descriptions, reviews, ratings etc.

UBB Threads - PHP do-it-yourself bulletin board. Free, limited features demo available. Used to be an independent project known as WWW Threads before being acquired by Infopop. It might be OK, who knows? What I can be certain of is that with Infopop calling the shots I don't want to know.

vB Templates - One of the select few official vBulletin affiliate sites. Caters for custom graphics, styles and template modifications.

XMB Forum - A relatively new, PHP do-it-yourself board.