There is previous mention of successfully booting a Boot It Bare Metal ISO in this thread, but I'm having a problem with this. Can anyone who is booting a BIBM ISO successfully please post their menu.lst entry for this ISO? I don't know if the menu.lst entry is the problem or if it's something with the ISO proper / interactions with my PCs. It does appear that the ISO is loading, but then I get a blank screen; it never gets to the BIBM GUI. I am able to boot from a dedicated UFD that BIBM's makedisk utility creates (when set to one of the partition options, though I think it has also worked in the past with the no partition option). I am working with the most recent BIBM release, 1.18. I am having success with a couple of other ISOs; I just starting trying out UFD multibooting and am using YUMI. Thank you. Doug
Initially, the only two issues that I had was not following these rules: 1. NO spaces allowed in the ISO file name. If you have any spaces in the ISO file name, the ISO will not boot. 2. The ISO file must be contiguous. If the ISO file is NOT contiguous, it must be defragmented in order for the ISO to boot. I use WinContig for defragmenting the ISO file.
No issues from these two perspectives. I also use wincontig, and I would have received an error message about the file being non-contiguous. Plus, I tried loading it into memory as well - no joy. Do I assume correctly that you just used the default menu.lst entry that YUMI created, as well as the file location to which YUMI copied the ISO (i.e., the ISOS directory)? If so, I suspect it's some sort of interaction with my PCs. It looks like BIBM is initializing, based on the message about the EMBR and something else that flashes quickly on the screen that looks like the message I get from installed BIBM when that loads from the HDD on my main PC. I also just tried an earlier version of BIBM, 1.10a, just to see if that affected anything. I also tried some alternate option values, such as no mouse, chipset video, and the "USB Hang" options. Still no luck. I'll try some more. Thanks for your help. Doug
Thanks for the update. Anybody using SIW2's PE iso in a multiboot stick? I can use Macrium on it but SIW2's PE on amutiboot through YUMI does not work..
Friends, I want to use yumi to boot an unlisted ISO 'Active@Disk' help me how to get that done. I have never been able to boot any of the 'Unlisted ISO's' as I don't know how to do it,as when I click the heading, it takes to a window I dont understand. Please help me with step by step tut, I hope some one will step up to help this novice. Atleast guideme to webpage if it is available. Thanking you all in advance. I do have latest yumi.
Once you select "Try an Unlisted ISO" you click Browse (step 3). Then you just select the ISO you want and press Create.
I am able to install the 'unlisted ISO' No Problem, but how do you run it? I mean when the Default menu of yumi is displayed, you have three options, Linux systems, Sytem, and the last for unlisted, when this is clicked, how do you boot that ISO? I think you got the point. For example I have "Active@Disk" in my ISOS folder, what are the steps to boot it? Help me with that, (In Yumi) Please!
When you get the YUMI menu, you first highlight the category (Linux systems, System, etc) you want (just use the up/down arrows) and press Enter. Now the menu shows you the ISOs you installed for that category so select the one you want and press Enter again to start it.
I Had done that, the ISO got listed the menu also gets displayed but the ISO won;t boot! Here is the menu.list for your perusal. # This Menu created with YUMI (Your Universal Multiboot Installer) http://www.pendrivelinux.com default 1 timeout 30 color NORMAL HIGHLIGHT HELPTEXT HEADING splashimage=/multiboot/menu/yumi.xpm.gz foreground=FFFFFF background=000000 title --- Directly Bootable ISOs + Windows XP --- root title <-- Back to Main Menu root (hd0,0) chainloader (hd0)+1 rootnoverify (hd0) # Modify the following memory based entry if it does not boot title Boot BootDisk.iso from Memory find --set-root --ignore-floppies --ignore-cd /multiboot/ISOS/BootDisk.iso map --heads=0 --sectors-per-track=0 --mem /multiboot/ISOS/BootDisk.iso (hd32) map --hook root (hd32) chainloader (hd32) Now tell me what needs to be modified? I have defraged the iso with 'wincontig' twice. So nothing known to me has been not done, still I am missing something as others were able to run, and not me. I do hope someone will find the exact error! Thanks for coping with my silliness though.
The other day I created two bootable ISOs on a 16GB flash drive from YUMI: Macrium Reflect Win PE and Windows 7 SP1. I never had a problem with the Win PE iso loading, but did with the Windows 7 one. I then followed their instructions to defrag the ISO due to the contiguous known issue. That enabled me to load the Windows 7 ISO, but shortly afterwards encountered an error about "Required CD/DVD drive device driver is missing". My Windows 7 ISO is legit and clean, which I verified against MS Technet's hash code and later successfully installed by burning to a DVD with ImgBurn (that program never fails me ). Maybe it's because I created the Win PE iso first, so any subsequent ISO isn't as reliable for some reason? Is there a more reliable alternative to YUMI that accommodates multiple ISOs? I would return to good old UNetbootin, but I think that only allows a single ISO per drive.
If I currently use YUMI-0.0.8.4.exe, do I need to update? At this point I can select on WinXP computer, XP or Mint v13 and these linuxmint-13-mate-dvd-32bit.iso linuxmint-13-cinnamon-dvd-32bit.iso ATI-10-4942.iso (Acronis v10 Boot disk)
I think that you only need to use a later version if YUMI-0.0.8.4 does not support the 'listed' ISO that you are trying to add.
the developer of XBOOT seems to have disappeared for well over a year now. i found out about this on the SARDU website as that developer claims SARDU is now the only good multiboot option available since XBOOT will no longer be updated. i guess he doesn't consider YUMI, MultiBootUSB, and MultiSystem as serious competitors to his adware bundled product.
+1 for YUMI, i made a nice rescue USB with everything i need to help me fix just about any computer os issue using YUMI, used it the other day to reset a windows password for one of my friends using a tool from the clean original last version of hirens, they were like how the heck. cool stuff
