257 replies to this topic

[crashnburn]

re. Clonezilla booting

Lots of examples of booting ISOs using grub4dos at www.rmprepusb.com

Or just use Easy2Boot or WinSetupFromUSB.

 

re. GRUB4DOS

1. Yes, name is a bit outdated, but at least it is consistent!

2. It can only be MBR-booted (like syslinux) but that doesn't mean you cannot UEFI-boot (see Easy2Boot)

3. There are front-end GUIs such as Easy2Boot (just drag-and-drop), WinSetupFromUSB, XBOOT, etc.

 

Would love to have some of your thoughts here  

 

http://reboot.pro/to...ay/#entry195299

[crashnburn]

re. Clonezilla booting

Lots of examples of booting ISOs using grub4dos at www.rmprepusb.com

Or just use Easy2Boot or WinSetupFromUSB.

 

re. GRUB4DOS

1. Yes, name is a bit outdated, but at least it is consistent!

2. It can only be MBR-booted (like syslinux) but that doesn't mean you cannot UEFI-boot (see Easy2Boot)

3. There are front-end GUIs such as Easy2Boot (just drag-and-drop), WinSetupFromUSB, XBOOT, etc.

 

Would love to have some of your thoughts here on this thread   given your experience with RMPREP & VHD booting

 

http://reboot.pro/to...ay/#entry195299

Edited by crashnburn, 11 September 2015 - 01:28 PM.

[alacran]

re. Clonezilla booting

Lots of examples of booting ISOs using grub4dos at www.rmprepusb.com

Or just use Easy2Boot or WinSetupFromUSB.

 

steve6375

 

I read all info you have in your site about clonezilla, some are old (Win98), other is to make an image of first partition, and newest is using Easy2Boot, any way none is about what I would like to do.

What i am trying is to boot clonezilla from an Iso located on a partition on my HDD

 

I tried this in my menu.lst, First one works great for al WinPE's I have, but clonezilla is Linux and obviously diferent, using syslinux as boot manager:

title Boot clonezilla-live-20150805-vivid-amd64.iso\nRun clonezilla-live-20150805-vivid-amd64.iso from HDD
##ISO file must be contiguous on disk in this case, use Wincontig
find --set-root /Isos
map /Isos/clonezilla-live-20150805-vivid-amd64.iso (0xFF)
map --hook
chainloader (0xFF)

title Boot clonezilla-live-20150805-vivid-amd64.iso\nRun clonezilla-live-20150805-vivid-amd64.iso in RAM
find --set-root /Isos
map --mem /Isos/clonezilla-live-20150805-vivid-amd64.iso (0xFF)
map --hook
chainloader (0xFF)
 

Both ways I can see the first screen, then selecting any option it does not go after first line, it says a file is not found, I think it do not see the content of the Iso, even if it is loaded in RAM, (second option posted).

 

Any ideas?, maybe use a *.img instead of Iso?

 

alacran

[Wonko the Sane]

I read all info you have in your site about clonezilla, some are old (Win98), other is to make an image of first partition, and newest is using Easy2Boot, any way none is about what I would like to do.

What i am trying is to boot clonezilla from an Iso located on a partition on my HDD

 
Read this:
http://reboot.pro/to...all-iso-images/
and this:
http://reboot.pro/to...os-isohybrided/
starting from here:
http://reboot.pro/to...brided/?p=88531

AND contents of the .mnu file provided here:
http://www.rmprepusb.com/tutorials/118

You should get the idea about what the issue is and how it has been solved specifically, in a nutshell:
1) NOT *all* ,iso's will boot when "simply mapped" to (0xFF) of (hd32)
2) in some cases you need to map the .iso to a partition table entry
3) generally speaking when booting a Linux based .iso it is easier to boot it by-passing the bootloader/bootmanager on the .iso and directly chainload the kernel and initrd because this way it is faster and allows to provide parameters or "cheatcodes" (that may be needed for booting from .iso)


Wonko

[steve6375]

If you type

 

help find

 

in the grub4dos console, you will see that the command requires a FILENAME

 

e.g.

find --set-root /Isos/clonezilla-live-20150805-vivid-amd64.iso

P.S. You might also like to read my blog post here

[alacran]

I think, I already read that some time ago, and that is why steve6275 uses partimage partnew and fourth partiction table of USB sticks or USB HDD's to load some Linux Isos.

 

Anyway I will read that againg, perhaps It can give me new ideas.

 

Thanks Wonko

 

EDIT: It is partnew in this case, just corrected my mistake

Edited by alacran, 12 September 2015 - 09:07 AM.

[alacran]

If you type

 

help find

 

in the grub4dos console, you will see that the command requires a FILENAME

 

e.g.

find --set-root /Isos/clonezilla-live-20150805-vivid-amd64.iso

P.S. You might also like to read my blog post here

 

In no way I'm trying to contradict the expert, but try my way with a known to boot PE.iso and you can see it works too.

 

I'll read your info, thanks steve

[steve6375]

Easy2Boot contains a grub4dos batch file called isoboot.g4b. This uses cheat codes to directly boot from different ISOs.

Here is the code it uses for Ubuntu which I have converted into a menu for you...

title clonezilla-live-20150805-vivid-amd64.iso\nRun clonezilla-live-20150805-vivid-amd64.iso from HDD
##ISO file must be contiguous on disk in this case, use Wincontig
set ISOSCAN=/ISOs/clonezilla-live-20150805-vivid-amd64.iso

find --set-root %ISOSCAN%
map  %ISOSCAN% (0xFF)
map --hook
root (0xff)
set try=/casper/vmlinuz
if exist %try% set kernel=%try%
set try=/casper/vmlinuz.efi
if exist %try% set kernel=%try%
set try=/casper/vmlinux.efi
if exist %try% set kernel=%try%
set try=/casper/initrd.lz
if exist %try% set initrd=%try%
echo kernel %kernel%         file=/cdrom/preseed/ubuntu.seed    noprompt      boot=casper  iso-scan/filename=%ISOSCAN% locale=en_US.UTF-8  splash -- > (md)0x220+1
echo initrd %initrd% >> (md)0x220+1
configfile (md)0x220+1

[steve6375]

P.S.  yes,

find --set-root /ISOs

does set the root drive to the correct partition too.

[cdob]

Clonezilla uses parameter findiso to serach the ISO file.
http://sourceforge.n...hread/306ef542/

Ubuntu uses iso-scan/filename.

Simple approach: set both, the init routine will use the correct one and ignore the other one
 

title Clonezilla live 2015 amd64 (Default settings, VGA 1024x768)
set ISOfile=/clonezilla-live-20150805-vivid-amd64.iso
cat --length=0 %ISOfile% > nul || find --set-root --devices=h %ISOfile%
map %ISOfile% (0xff)
map --hook
root (0xff)
kernel /live/vmlinuz boot=live union=overlay username=user hostname=vivid config quiet components noswap edd=on nomodeset nodmraid noeject locales= keyboard-layouts= ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_batch=no vga=791 ip= net.ifnames=0  splash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.enable_fbdev=1 findiso=%ISOfile% iso-scan/filename=%ISOfile%
initrd /live/initrd.img

[alacran]

Steve

 

I read the info in your link in post #230, it is all clear to me now, basically parnew and fourth entry in partition table are the best way (when it is available, very usefull on USB sticks), but not in my case on internal HDD.

 

Also I saw your post:

 

 

Easy2Boot contains a grub4dos batch file called isoboot.g4b. This uses cheat codes to directly boot from different ISOs.

Here is the code it uses for Ubuntu which I have converted into a menu for you...

 

It is great, this is going to let me boot not only clonezilla, also Ubuntu, I liked a lot the use of the alias (new for me):

 

set ISOSCAN=/ISOs/clonezilla-live-20150805-vivid-amd64.iso

find --set-root %ISOSCAN%

 

About this:

 

 

P.S.  yes,

find --set-root /ISOs

does set the root drive to the correct partition too.

 

I found it when I forgot to put the file name some time ago, and it worked fine, so I use it that way since then.

 

Thanks to you very much for all this.

 

Best Regards

 

alacran

[alacran]

Clonezilla uses parameter findiso to serach the ISO file.
http://sourceforge.n...hread/306ef542/

Ubuntu uses iso-scan/filename.

Simple approach: set both, the init routine will use the correct one and ignore the other one

 

Good info and nice approach, I like your idea.

 

Best Regards

 

alacran

[steve6375]

duh! Sorry Alacran - I need more coffee this morning as I am obviously not yet awake yet!! Somehow I confused clonezilla with ubuntu!

[alacran]

Well this  version we have been talking about is based in Ubuntu, as they say in their page.

 

But using cdob approach we cover both possible ways because there are other builds based on Debian, and every body happy.

 

Anyway AFAIR Ubuntu is based on Debian, but I don't know anything more than this about Ubuntu.

 

alacran

[alacran]

@ steve6375

 

Your config in post #233 once every thing is changed to Ubuntu works great with it, I tried it with ubuntu-14.04.3-desktop-amd64.iso booting from internal HDD.

 

Best Regards

 

alacran

[Zoso]

hi all,

is it somehow possible with grub4dos to decompress a file in XP that was compressed in/by XP (ntfs)?


just crossed my mind. lol! actually, i do have a need for this. (ntldr is compressed boot error) thanks

[Wonko the Sane]

hi all,

is it somehow possible with grub4dos to decompress a file in XP that was compressed in/by XP (ntfs)?


just crossed my mind. lol! actually, i do have a need for this. (ntldr is compressed boot error) thanks

No, grub4dos won't, the NTLDR is compressed boot error usually it is connected with using NTFS compression on the WHOLE boot volume (without excluding  NTLDR, NTDETECT.COM and BOOT.INI), you need to boot an alternate windows OS and change those files to be not compressed.

 

Wonko

[Zoso]

No, grub4dos won't, the NTLDR is compressed boot error usually it is connected with using NTFS compression on the WHOLE boot volume (without excluding NTLDR, NTDETECT.COM and BOOT.INI), you need to boot an alternate windows OS and change those files to be not compressed.


Wonko

i had my hopes up that it could. is an alternate windows os absolutely required? looking for the smallest 'footprint' way to do this. I have a maintenance XP down to ~250mb that would work. just thought there might be an odd chance grub4dos could do this.

[Wonko the Sane]

Any PE would do it, it would be interesting (but I am not advising you to try it) to use the smallest possible XP for it:
http://reboot.pro/topic/16765-minixp/

 

Please understand how the compression in NTFS is a "feature" of the filesystem, so you will either need Explorer or use the command line tool compact.exe:
https://technet.micr...y/cc976800.aspx

 

Most probably current Linux distro's supporting NTFS can also expand compressed NTFS files, the traditional way was to copy it out of the volume and then copying it back:
http://serverfault.c...lume-from-linux

 

Wonko

[Zoso]

ive been wanting to try misty's mini..

something else just crossed my mind. what options are there if any to use grub4dos on a w98se system? is a way similar to boot.ini so to just place gldr and menu list in root of the hdd?

[Wonko the Sane]

ive been wanting to try misty's mini..

something else just crossed my mind. what options are there if any to use grub4dos on a w98se system? is a way similar to boot.ini so to just place gldr and menu list in root of the hdd?

Well you can boot to DOS (remming out the win.com from autoexec.bat) and run grub.exe or simply add it as an option in a modified autoexec.bat.

 

Wonko 

[Zoso]

Well you can boot to DOS (remming out the win.com from autoexec.bat) and run grub.exe or simply add it as an option in a modified autoexec.bat.


Wonko

that sounds like a good plan.. so ive searched here and elsewhere for the specifics but havnt found exact instructions on how to yet. would you please elaborate more about this?

ive recently pulled out some old equipment and im testing the electric current consumptions with different OSs installed on same hardware except the oldest laptop has only 64mb RAM so I dont have much choices yet except the W98 on it but this oldest laptop has the lowest power consumption of the laptops so far @ 16 watts while running the data logging software that i use to monitor small solar power generation stations.

this is why Im becoming more interested in older and custom OSs. the program for data logging is only available for windows OS however the hardware uses MODBUS for communications which is open source but ive got alot to learn before i can take advantage of that. a couple of folks have done the hardest part but to even pick it up from there is still beyond my skills so right now Im working with windows and misty's may be next to learn more about. i could probably get a homebrew XP down to only what is needed to run the data logging program and then later hopefully move on to the linux stuff for this. then I could probably get the data with mush less power, im guessing maybe down to 5 watts with some of these new hardwares available now. will require lots of time to learn how to make that happen on my equipment though.

thanks

[Wonko the Sane]

that sounds like a good plan.. so ive searched here and elsewhere for the specifics but havnt found exact instructions on how to yet. would you please elaborate more about this?
 

There is nothing to "elaborate".

1. Boot to DOS.
2. Run grub.exe. (optionally passing to it a config file or set of instructions[1])
3. Profit

 

Wonko

 

[1] Read the grub4dos readme (in the archive) and diddy's manual if needed.

[Bahram_Alinezhad]

We DO NOT support WAREZ on this board, see Rule #1:
http://www.boot-land...?act=boardrules
 

404 Page Not Found

It seems that the page you were trying to reach does not exist anymore, or maybe it has just moved. You can start again from the home or go back to previous page.