Hey guys, i'm pretty familiar with computers in general, mostly windows based stuff, but trying to move into Linux. I am having some issues with Linux (FC2) install. It's an old system, 333MHz with 64 MBs of RAM, but i hear linux should be able to run on slower systems. I bought a new hard drive (250 GBs) and installed it as the slave (the other dirve was a 6GB- Win98). When i tried install linux on it, it didn't recognize the drive at all. I then uninstalled the Win98 drive and kept the 250GB as the Master. Linux recognized it and i went thru the whole GUI installation procedure. It started installing, but just froze in it's tracks at the very beginning. Any ideas? Do i need more RAM? is the HD too big? Linux recognized it as a full 250GBs when it was installing...but i don't know if it's able to write to it.

hopefully i didn't put this in the wrong forum...

Thanks for any help!

Ack... ok you chose to move forums... the fedora forum would have been more suitable but never mind. please don't try to move threads though. If it's deeemed to be in the wrong forum a moderator will move it.

Are you sure that the machine's BIOS fully supports the new drive ? A 333MHz PC would predate the drive by several generations.

A 6 Gb drive would be enough, but 64Mb isn't sufficient for a standard graphical interface - GNOME and KDE require 128Mb to run.

I use Fedora 2 on a Pent.2 400mhz but with 256mb ram and it works well. Cobind is based on Fedora and will run on 64mb ram.

For whatever reason, Linux distributions don't seem to stress the CPU as newer versions of Windows do, so 300-400MHz CPU is feasible. The graphical interfaces are memory-hungry, as are Mozilla and OpenOffice. 128Mb RAM gives you a system that lags a bit, 256Mb is much better.

I think that CoBind only provides a command-line interface, which is fine on 64Mb RAM.

You can do a text-mode install if you think that the standard graphical install isn't workable for whatever reason but the fact that the installer stops dead writing the partitions or transferring files, rather than just going slowly, suggests to me that accessing the drive is the issue.

Cobind's GUI is XFce . It also uses the Firefox browser and AbiWord both of which are resource lean.