Hello, dancingdog777,
Interesting that the one you condemn is associated with what you have repeatedly been told is a non-standard version. I'm not attacking you over this observation, my friend.
My success has been 100% on many many installations of standard official releases, from 2.00 through to 2.17, using the standard settings in the standard installer.
Even on the distribution in question with the standard
Ver 2.15ce which is what actually installs before you do surgery on the file system to accomodates ecomoney's modifications. (I have yet to do the latter, to prove that I can safely put that download on line as working)
Perhaps you are confusing Grub not booting what menu item you have selected with the actual installation not starting up. The installer advises you to check the
/boot/grub/menu.lst for its assumption that
vmlinuz and
initrd are where it thinks they should be, because it doesn't carry out a search when writing that statement... it expects you to do that, and the installer script advises you to do that, while you are still running in
Live Mode.
If it doesn't boot, then restart in Live Mode and go and check out
/boot/grub/menu.lst comparing it with the actual locations of those files.
If it still doesn't work after that check, then maybe, depending on what doesn't run, you have a bad downloaded
ISO or the burn wasn't good. Many an installation of many Linuxes have been branded as "won't work" because of a badly burned CD (burned too fast perhaps) or a corrupt
iso file that was burned.
If all four of your bad installations have been from the same CD burned from the same iso, then that is likely your common factor, not the product.
There are two stages of booting, my friend. And yes, I like PCLinuxOS also, it's a ripper. But a ripper for a different purpose
First stage uses the
Initialise Ramdisk (initrd) which sets up the ramdisk and copies loading files there. If that works, then the next stage is where those files unzip the compressed linux kernel (which is why it's named
vmlinuz - the z on the end points to that.
If that works fine the next step is to see if it gets a
Graphical User Interface. That is where the first time it asks you to configure the X-Server which most associate with just the Screen... but it also configures other external peripherals such as pointer (mouse, tablet or pen), keyboard et cetera.
If you already knew all this stuff, please pardon my assumption that you didn't because your comments came across as someone who expected full automation. And no, from experience, even your and my beloved PCLinuxOS requires user input at several times during the process.
The only times the standard puppy installer hasn't worked with me are
1- with incorporating grafpup (which is a different product, based on puppy, but employing slight variations in the filesystem tree), and
2- when adding extra lines to
menu.lst for extra boot choices and making a typo with the partition identification on multiple booting scenarii.
Seriously, the installer that we've used for a while, has done a sterling job of getting it right.
Don't think I'm a guru either. My writing perspective has always been
KISS, aka
Keep it Simple, Stupid which can tend towards verbosity if you set out to avoid long words. I used to write specifically for non-computer-literate draughtsmen who had been dragged screaming into the world of
Computer Aided Design and Draughting in what was then Australia's best CAD monthly.
If you are genuinely having all manner of problems running the installer, you may care to PM one of us with exact details.
BTW my four failed attempts had nothing to do with installing. They were
download failures - a different ballgame in a different ballpark. Web server bandwidth hiccups in all probability.
[i]Have you noticed editing is always needed for the inevitable typos that weren't there when you hit the "post" button?[/i]
[img]http://micro-hard.dreamhosters.com/416434.png[/img]