The challenge is to configure and run a complete website from a standard 1.44mb floppy disk such that, if the floppy were inserted to a standard and untweaked O/S the complete website could be run entirely from floppy disk. Anyone want to take this idea up, make up some better rules and perhaps judge it??.

Outline rules - maybe someone might want to formalise these or do a better job?.

• The entire webserver, including webserver software, all pages, logs and cgi applications must fit on the floppy image
• It must run "live" from the floppy or floppy image
• Linux, Windows or any O/S are permitted but should not cheat by taking advantage of built-in O/S functionality
• The site should work fully if the floppy is inserted into any PC with an O/S not configured for a webserver/PHP/PERL
• The entire setup should be capable of running from a 1.44mb floppy disk (but can be emulated on a floppy image if desired)
• Any webserver can be used - eg. Tiny, Abyss, Xitami, Apache, Lunix!
• The only exceptions are DLLs which MUST go in the \windows directory and Windows O/S itself

Basic Features

• As many web-features as possible such as guestbook, page counters, ftp, contact email forms etc.
• It should be a real website - not just a "one-pager" - so it should have more than one page
• It should feature a photo/picture gallery with at least one image in it (extra points?)
• The site must have at least true one web page (index.htm*) and at least one graphic in the page
• Extra marks for getting PHP or PERL to run entirely off the same floppy image
• Lots of extra marks for getting Apache 1 or 2 to run (done it!)
• Extra marks for SMTP connectivity (e.g. SMTP "back end" to an app such as a guestbook or mail-form)
• The finished website to be put online and accessible, live from the net
• Suggested port to be port 88, 8800 or 8880 to avoid conflicting with port 80 of current sites on same IP

Logging

• Automatic logfile-pruning is permitted to avoid a "disk full" error or...
• Logging can be disabled, or...
• Logging CAN be redirected elsewhere since logging is not an essential part of the challenge

Compression, Images and Image Location

• To make it more difficult - disk compression is NOT allowed but exe compression is (if you can get it to work)
• Banning disk compression means any solution will work ok with Win9x/NT/2k/XP (no Floppy DriveSpace on XP!)
• A disk image such as VFDWin can be run from ramdisk on the demo server
• The demo site can be run from a 1.44mb ramdisk on the server emulated as drive A or B
• Many EXE files are already partially or fully compressed anyway
• Software must run from the floppy not unzipped from floppy into say a huge ramdisk then run

Modifications

• Stripping redundant files from an install is totally permitted and encouraged (pruning)

Ties

• Size to be declared and shortlist winners to declare a disk image to verify
• Overall winner to be the best set of functionality with smallest size
• In the event of a tie - smallest image size with the most features wins