A few people have found the previous versions of these useful so here are the Edgy x86 Ubuntu/Kubuntu/Xubuntu/Server floppies. If you can use another method to install (e.g. Mini ISO, tftp boot, etc) then try that first. These floppies are more of a special case get-out-jail free card for people without CD drives or CD burners. If anyone out there feels like mirroring 9mb of very low traffic files then I'd sure like you to get in touch (Most errors happen with people trying to put the image files back together).
Get 6 1.44mb good floppy disks. By good I don't mean the one you've been using as a coaster for the past year, I mean good enough that you can write to them without errors.
Get all the files I've posted on this thread.
NOTE: These are NOT zip files, they just have the .zip extension, do not attempt to extract them. The forum code won't allow me to upload something that's 1.44mb in size directly, however it will allow files with a .zip extension up to 920kb in size. Therefore I've split each disk into 2 parts and labelled them with a .zip extension. The disk parts are all labelled disk<disk>.<part>.zip. Don't let yourself get confused, don't believe the icons in your file manager, they are NOT zip files. Use the instructions to rebuild the disk images.
Thanks to me being forced into splitting the images you'll have to put them back together to get the real disk images. This is a very simple operation:
copy /b boot.1.zip+boot.2.zip boot.img
copy /b disk1.1.zip+disk1.2.zip disk1.img
cat boot.1.zip boot.2.zip > boot.img
cat disk1.1.zip disk1.2.zip > disk1.img
Now write the images onto your real floppy disks. It's probably a good plan to label the disks .
These are image files, they contain an image of the whole floppy disk, they must be written out to the disk (Similar to burning a CD from an ISO image).
Use the free utility RawWrite http://www.chrysocome.net/rawwrite
dd if=/path/to/image of=/dev/fd0
Set your computer to boot from a floppy drive in the BIOS. If you can't do this then you REALLY shouldn't be using this guide.
Insert the disk that has been written with boot.img and reboot. After a short delay you'll get asked to insert disk 1 and press a key, the disk will be read and you will be asked for disk 2, etc. After all disks are read the Ubuntu installer will start.
It's the text only installer so don't get scared when you see lots of kernel messages rushing by while it's booting. After answering a few questions and downloading the base system you will be given the option to install Ubuntu/Kubuntu/Xubuntu/Server/etc.
After selecting your preference do not panic when the progress bar stays at 6%. The installer must download a large number of files to your system before they can be installed. How long this takes will depend on your download speed (Around 1 hour at 255kb/s).
After installation be sure to remove all floppies and alter your BIOS to boot from the appropriate hard-drive.
This HOWTO uses modified GRUB code to support composing an initrd from multiple files. Do not complain to the GRUB devs about bugs.
This is a network install. No supported network card = no install. The supported hardware is the same as that for the Mini ISO.
The installer uses <space> to select an option (You'll need this when selecting video modes), the cursor keys for navigation and the enter key to hit a button.
These disks are effectively a floppy version of the Mini ISO install CD, the only difference being a smaller kernel image (I couldn't fit the Mini ISO one on one disk).
I don't take any credit for the excellent work someone else did putting together the Mini ISO system.
Treating these files as though they are zip archives. They aren't, they are just big blocks of data with filenames that happen to end in .zip.
Downloading the forum error page. The forum requires you to be logged in before you can download files. If you hit 'save as' and wind up with a file less than 720kb then this is probably the reason why.
Not being in the right directory when rebuilding. Usually this just affects folks that are unused to the command line. On Windows you can get a command prompt with Start->System->Accessories->Command prompt. Use the command 'cd directory' to change directory (No apostrophes, use the name of the directory you want to change to). 'dir' will give a list of files/directories in the current directory.
Copying the image files into a disk instead of writing them to the disk. In theory this shouldn't be possible (Unless you have some 2.88mb disks lying around), but if you find yourself getting a 'disk full' error then it's likely this is what you're trying to do.
Out of disk space. Usually only a problem when installing in a virtual machine. The install requires a minimum of 2.5gb disk space. You'll know when you run out because the installer will just hang there doing nothing, but ctrl-alt-f2 will still give you a busybox shell. Don't get confused with the "This thing has been sitting on 6% for hours" download part of the install.
Unsupported network card. The Mini-ISO (Which this guide copies) supports a nice range of cards, but by no means all the cards supported in a full install. If you're using exotic hardware or something that is only supported via the restricted modules then you're likely to be out of luck. If you're feeling really adventurous then you can try downloading the appropriate modules (Use modules built for 2.6.17-10-386), copy them to a floppy, press "Go Back" in the installer at some point (After the network configuration fails would be good ), start a shell, mount the disk, modprobe the modules, close the shell and restart network configuration (I believe you'll also want a lunar eclipse, 3 virgins and a live chicken).
Using the wrong disk. If GRUB gives tells you "Error 15: File not found" then chances are you've put the wrong disk in. You did label them...didn't you?
Using bad floppies or having a junked floppy drive. This is probably the number one thing that people have got caught out by in previous versions of this guide. Floppies are temperamental little things at the best of times, even after they've just been bought from the store. If you hear the disk drive grinding away when writing out the image then it might, I say might, be an indication of a bad floppy. If you have problems then try replacing the disk the install stops on and try again.