Rescatux 0.30.2 released

Download, Rescatux, Rescatux Stable

Rescatux 0.30.2 has been released.
A major bug concerning the Kernel selection on boot (64bit or 32bit) has been fixed in this release. If you have Rescatux 0.30 or Rescatux 0.30rc1 please check Rescatux 0.30 64bit kernel not being select ok Bug for a way of workarounding the bug without having to download again the iso.

Downloads:

Rescatux 0.30.2 size is about 372 Megabytes.

27 thoughts on “Rescatux 0.30.2 released”

  4. Thanks for the update! I’ve been using grub long enough to know that I need to have a backup plan in place should it ever go south, and this is a good insurance plan should I ever need it.

    Reply

  5. I tried loading the ISO onto my USB drive which tries to load whole ISO files using grub4dos. I tried several configurations but without much luck. Anyone have this working via Grub4Dos? Or do I have to use syslinux via YUMI or something like that?

    Reply

  10. hi, i get error: could not find kernal image:/ syslinux/vesamenu.c32
    boot:
    how do i solve the problem,i am trying to fix my grub by using the rescatux 0.30.2. please help

    Reply

  11. @kb: Either make a direct cd / usb. Or use USB. Check the md5sum of downloaded files to make sure that they didn’t get corrupted when downloaded.

    Reply

  14. Tho it is not considered good Latin to be critical of other commenters, I herewith LAMBAST the bulk of above commenters as well as Rescataux/ Supergrub for NOT reigning morons! Alternatively (RE Rescataux/ Supergrub), for not setting up a 1-Click Thumbs-Up/-Down for those whose “Comment/ Reply” is the equivalent of a “thumb” (such as “Thx!”, “A live-saver”, “Rescataux for President!”, etc.). On to what is missing here, causing non-Linux folk to view Linux folk, STILL, as 17-year-old, pimply-faced NERDS…

    In Linux, there are two main “architectures” corresponding to 32-bit and 64-bit. These are i386 (32-bit) and x86_64 (64-bit). In the Sourceforge download link above, one sees “x86” listed (as well as “amd64”), yet when one clicks on the link, all reference to “x86” (or x86_64) disappears, while “i386” and “486” DO appear. Since Sourceforge’s regular grub repair utility, Boot-Repair-Disk comes in both a 32-bit and a 64-bit version, it is A SIN OF NERDY OMISSION -n o t- to be DEMYSTIFYINGLY EXPLICIT about the naming of the file one is to download!

    I am confident that 17-year-old, pimply-faced NERDY types will brush off my criticism… this explains why Linux continues to DISAPPEAL to folk who are NOT of the 17-year-old, pimply-faced NERDY type! [I downloaded the Boot-Repair-Disk in the 32-bit version the first time, from a 32-bit-only Sourceforge site, not knowing that I SHOULD be expecting a choice (as in “you don’t know what you don’t know” or “… what you WOULD know if you were a 17-year-old, pimply-faced NERD like us!”)].

    I also eventually found, and downloaded and burned, the 64-bit version, but it is as useless for repairing Grub2 as the Live CD itself (which Grub2 distinction I knew nothing about, until Boot-Repair-Disk, 64-bit version, also proved to be a flop… again, only 17-year-old, pimply-faced NERDS keep their cards so close to their chest that this excludes all but “in the know”, 17-year-old, pimply-faced NERDY types – which surely makes the latter feel superior to Windows users, which, in turn, ensures that Linux will continue to be a self-aggrandizement project for “in the know”, 17-year-old, pimply-faced NERDS!).

    Additionally, ALL of the Supergrub files on this page (https://www.supergrubdisk.org/) are “candidates for release”, not “stable releases” (all are designated “rc[X]”, and, semantically speaking in any case, a “release candidate” is NOT a stable release!).

    All in all, I am very DISIMPRESSED with Linux in general – too many Indians/pissants; no Chief/lion ANYWHERE IN SIGHT, there on the plains/savannah!

    I’ll download the file linked to above and give it a whirl, then come back here to let users of my mentality know, EXPLICITLY, whether this GRUB repair solution worked on my x86_64 (openSUSE) architecture.

    George

    Reply

    1. Not only does repeating the same phrase “17-year-old, pimply-faced NERDS” a total of seven times in your insignificant rant make you seems extremely unintelligent, but it saddens me to think that you’re genuinely upset over a few short comments that thank the creators of Rescatux.

      Ultimately, you should keep your sad opinions to yourself and refrain from ranting on about not naming files specifically (which is quite easy to fix so a simple “hey the file names don’t specify the architecture” would suffice.)

      Oh and
      1. It’s unimpressed, not disimpressed.
      2. Architectures is the correct word, why the quotes.
      3. Continues to not appeal*…
      4. Don’t download something without understanding how it works. Reading is vital to knowing about computers/programs/operating systems.

      Reply

      1. I am not native English but I re-read his message three times and I think he was complaining about boot-repair system and not about Rescatux itself but… Why did you think that he was talking about Rescatux?

        Reply

    2. dude, go buy an apple product if you are so apathetic to research. you get what you pay for. so if incredible service and someone licking your ass is what your looking for. keep looking… linux is not for you

      Reply

      1. Dear Adrian!
        You’ve been doing a great job that has hugely helped the community.
        Please don’t stop. 🙂

        Reply

    1. Well that’s an interesting comment. My machine is at least 7 years old and it’s 64 bit – and I’m getting ready to replace it because it’s on its last legs. Just how old is your machine?

      Reply

  18. Thanks a lot. With rescatux on my side, I have rescued my laptop and desktop computer a number of times. As a multiple distro lover, I would suggest everyone to have rescatux on a USB flash drive. It is a life saver. My sincere gratitude to the creators of rescatux.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *