I would like a lot to create a multiboot DVD (and USB too, if possible) that includes Hirens, Active Boot Disk and Kaspersky Rescue Disk... anyone already tried this combination?
You can put almost anything on YUMI, but make sure that your ISO doesn't contain spaces. For example an ISO called, Macrium Reflect should be MacriumReflect. Learned hard way! Also, you can use XBoot, and it allows spaces. I use both. I have two USBs ready, one with YUMI and one with XBoot. Best regards,
Thanks for the tip on naming files without spaces. I also came across a problem with a couple of my iso files that were fragmented and had to use WinContig to fix the problem.
YUMI: How do you manually remove the Run as unlisted ISO entries from the YUMI boot Menu? Basically how do you uninstall an installed unlisted ISO? I see where you can just delete the ISO file, but I do not know how to get rid of the boot Menu listing for the uninstalled ISO. Thanks in Advance.
I'm trying XBoot right now to create a DVD (at the moment i don't have a free Pendrive to try YUMI). I'll follow your advice about the spaces!
If I want to upgrade an unlisted ISO, can I just make sure that the updated ISO has exactly the same name as the existing ISO, delete the existing ISO and then copy the updated ISO to the same folder where the existing ISO was? This should make it where I do not have to edit the menu.lst. I guess that I may have to do a defrag of the updated ISO to make sure that it is not fragmented.
I know it doesn't work with XBoot. For this reason I was trying to switch to YUMI. Can someone confirm the above? Best regards,
Yesterday, for my first time ever, I edited the YUMI menu.lst file using Windows Notepad. I added an unlisted ISO with filename IFLCUI and tested that it would boot the ISO. Then I changed the name of the ISO form IFLCUI to IFLCUI273 and then edited the three menu.lst entries from IFLCUI to IFLCUI273. I successfully booted IFLCUI273.
I just manually updated BootIt Bare Metal 1.10 to BootIt Bare Metal 1.10a. I deleted the BootItBareMetal110 ISO from the ISOS folder and then copied the BootItBareMetal110a ISO to the ISOS folder. Using Notepad, I edited the three file names in the menu.lst file from BootItBareMetal110 to BootItBareMetal110a. and saved the changes. BootIt Bare Metal 1.10a successfully booted. It is noted that the ISO file size change was insignificant, because it was a minor bug fix upgrade. I did not degragment the upgraded ISO file.
Dearest Kid7, Thanks for the above information. What would happen if you had kept the ISO name the same and just copied the new ISO on the USB, without messing with the menus? Best regards, Mohamed
It should work as long as the new ISO did not get fragmented when it was copied to the USB Flash Drive. If the new ISO got fragmented you would need to defragment it. The only reason that I changed the ISO file name was to remind me of what ISO version was installed on the USB Flash Drive.
YUMI: Does any know when you would use the "Try Unlisted ISO (Run from RAM)" option instead of the "Try Unlisted ISO" option? YUMI Unlisted ISO Options: Try Unlisted ISO Try Unlisted ISO (Run from RAM)
i could be wrong but i think the 'Run from RAM' option copies the ISO into ram before loading it and the standard option runs the ISO without loading it into the RAM first
I found the answers: Use Run from RAM when you wish to have the entire system loaded to, and Run from RAM, rather than the USB device. Comments: 1. A possible scenario could be when you want to boot several systems using the same preloaded USB device. 2. Access is also quicker via system memory than USB. Limitations and drawbacks: 1. ISO must be smaller in size than available system memory. 2. Reduces available system memory that remains for use within the Operating System.
Release a new version of SARDU: 2.0.5 final Code: Replaced support to Microsoft Security Sistem to Windows Defender Offline Fixed error with photorec /testdisk/lilopwd Fixed error with Ophcrack Fixed manage Blacklist Fixed Graphical errors (Thanks to Marco Cristini) Fixed Remove Opendiasgnostic (Thanks to Marco Cristini) Fixed error with Fedora (Thanks to Marco Cristini) Fixed Errors with presence of card reader recognizing USB Fixed check for space of USB Added Support to NTFS on USB memory Added Support to QEMU for test USB and ISOs without external software Added Ability to Hide Hard Disks Added Support to Windows Eight (only for fat 32) Added Barrosu function for support the installer of Vista AND Seven AND Eight in the same USB FAT32 Added Androis x86 Added check for space in the home of SARDU Added function for the check of integrity for ISOs Added ability to set or disable boot timeout Improved download of ISO with check of integrity Improved Installer of Windows XP Changed boot of Kaspersky Updated Chinese language (thanks to Danfong Hsieh) Updated all links to download (Thanks to Marco Cristini) Upgraded 7z to 9.20 version Updated grub4dos to 0.4.5c-2012-06-19.7z Updated Cygwinn dll for recognition of burners Rewrited all function of Windows PE >2 Rewrited all function of Installer of Windows Vista and Seven Rewrited the function to make bootable the USB Others minor fix Various graphic changes
YUMI-0.0.6.6 was released on August 2, 2012. Changelog: Added Ubuntu 12.10 Daily Build. Removed Internal Format Option (not necessary). Fix Linux Mint 13 Cinnamon removal bug.
For anyone who has trouble getting ISOs to load via YUMI... I've previously used YUMI with no problems but recently I bought a new 32GB Transcend drive and after creating a multiboot I noticed that some ISOs wouldn't load. I checked the existing multiboot drive still worked and tried to boot the new drive using other PCs with no joy, so decided to format it. I formatted (tried FAT32 and NTFS) it in Windows but it still wouldn't work. Just before I gave up I decided to look at it in GParted. I wiped and created a FAT32 system in GParted and now it works with any ISO from YUMI. So, if you are having problems with YUMI, don't use Windows to format. A few things to note: (I think) It was only ISOs that used GRUB not syslinux that stalled. The latest version (0.0.6.6) doesn't have the option to format the drive.
