May work on some systems, but on my one it installed an old version of Grub2 and failed to boot on the first harddrive to Linux on the second harddrive. There's no help provided when the distro boots up. Very little or no explanation of settings. If the author can set a up a safer and easier to understand set of steps then I'd love to support this as restoring boot functionality on Linux is abysmal and should not have to require complex shell commands. Hope the author can improve this.
"This kernel requires the following features not present on the CPU: pae Unable to boot - please use a kernel appropriate for you CPU." Downloaded 32bit as don't have 64 bit cpu, Turns out I can't use this anyway due kernel.
Rated at minimum because the 32-bit ISO is not useable on older hardware as a kernel is used requesting a PAE-CPU. I know .... this is a kernel-problem, but nevertheless it's getting really problematic especially because very often Linux is the way to go on older hardware. Really a bad move in kernel-development and as a result Linux gets a status "to be avoided on older hardware" Really a pitty !!!
boot-repair-disk 32 bit not support non pae machines?
Well the idea is wonderful, but the execution is somewhat flawed. The advanced section needs more options. Insisting to connect to the Internet with no explanation before hand is also NOT a good idea. At least let the user know why you want to connect. (It phones home and sends configuration data in case of a problem. In my case I have a laptop that has windows on the main drive. I wanted to have the os on a bootable USB external drive. Because Toshiba does things weird, this won't work. The main drive is sda, until the usb drive is inserted. Then it becomes sda! This totally confuses the installation, and so when you go to boot after all done, you can not boot. Your program in advanced would not give me the option of sda, so it would not work. I'm sure it will work for many. Oh, and most importantly... If you attempt to go back to "legacy grub" you go to the trouble of telling us to chroot along with the command of "dpkg". Don't you think you should include that? Since the it is not, it fails! Bug