Just curious: I wonder if Grub4Dos will be designed to use multiple CPUs/cores in the near future...
Why would you need more CPU power for grub4dos? Are you writing a code cracking algorithm in a grub4dos batch file?
Posted 02 July 2014 - 08:04 AM
Just curious: I wonder if Grub4Dos will be designed to use multiple CPUs/cores in the near future...
Why would you need more CPU power for grub4dos? Are you writing a code cracking algorithm in a grub4dos batch file?
Posted 02 July 2014 - 09:47 AM
Why would you need more CPU power for grub4dos? Are you writing a code cracking algorithm in a grub4dos batch file?
No.
But in some situations more CPU power will speed up the booting a bit.
Posted 02 July 2014 - 10:22 AM
No.
But in some situations more CPU power will speed up the booting a bit.
Really?
In the grub4dos part of the booting?
How many nanoseconds do you expect to gain by running a STRICTLY SEQUENTIAL set of instructions (like booting is) on multiple cores?
Wonko
Posted 02 July 2014 - 10:53 AM
Hi, Wonko
Good to see you again.
I'm not sure, 3 or 4 nanoseconds
When I was speaking of "boot time" I meant the hole "process" (so loading/processing of grub4dos scripts as well). Sorry for not being more specific about that. Thank you for showing me this
Most of the time is wasted when reading from media (HDD, USB, CDROM and so on). But in some situations a parallel processing of the code from the scripts would help.
Posted 02 July 2014 - 12:09 PM
No.
But in some situations more CPU power will speed up the booting a bit.
Hi, Wonko
Good to see you again.
I'm not sure, 3 or 4 nanoseconds
When I was speaking of "boot time" I meant the hole "process" (so loading/processing of grub4dos scripts as well). Sorry for not being more specific about that. Thank you for showing me this
Most of the time is wasted when reading from media (HDD, USB, CDROM and so on). But in some situations a parallel processing of the code from the scripts would help.
Care to share with us WHICH situations?
Wonko
Posted 02 July 2014 - 12:37 PM
Okey dokey
For example when you have to process some configuration/boot files from an OS, so you could find HOW to start it.
You load the files in memory and start searching in them. You have some idea about how the required data might look but can't be 100% sure about its exact format and about its location (for good reasons).
This takes some CPU time. Not a lot when you compare it with the time wasted to load the files in memory but it counts.
Posted 02 July 2014 - 03:24 PM
And again instead of a vague example, if you could provide a specific one that would probably help.
If you are doing the whatever processing through grub4dos batches, long before abusing of multi-core CPU's you will have a measurable increase of performance by writing a grub4dos (compiled) program.
Still, if the "general idea" is "going through a lot of files to find something" the process tends to be single threaded as long as the "area" to search is a single one (I presume the boot device) and the advantage might be when there are several areas to look into (let's say one thread for floppy devices, one thread for hard disk like devices and one thread for optical devices, roughly corresponding to the (fd) (hd) and (cd) devices in grub4dos).
All in all (and with all due and even some undue respect) something that I would put on number #12478 on the priority list of future desired grub4dos enhancements (right before #12479 which is "Interfacing with an external controller capable of dispensing aromas and oils to the effect of holistically completing the grub4dos booting experience, providing means for integration into a wider therapeutic context suitable to allergy suffering users") .
Wonko
Posted 08 July 2014 - 01:49 PM
Can you be more precise? Do you mean RouterOS? Which version? What CPU? etc.
Hi steve6375
Yes i mean RouterOS
version 2.9.27
this is link to ISO
I try this commands in menu.lst
1- map (0xff)
find --set-root /ISO/Mikrotik.iso
map /ISO/Mikrotik.iso (0xff)
map --hook
chainloader (0xff)
2- memdisk
kernel /ISO/memdisk iso
initrd /ISO/Mikrotik.iso
3- extract ISO content
all of them boot Mikrotik setup correctly
then i get no packed found
Posted 09 July 2014 - 11:21 AM
..(ignore)
Posted 09 July 2014 - 01:58 PM
I don't understand
what is the exactly meaning of ..(ignore)
Posted 09 July 2014 - 02:02 PM
ignore = do not pay any attention to this post - i.e. I posted by mistake!
Posted 09 July 2014 - 03:00 PM
yes I see it before but
when i download It
I see that there is .mnu to support the iso
Edited by memoarfaa, 09 July 2014 - 03:00 PM.
Posted 09 July 2014 - 03:37 PM
where?
Posted 02 December 2014 - 10:11 PM
timeout 0 title MicronSSD Firmware Update (ISO)\nMicronSSD firmware update via ISO. find --set-root /realssd.iso map --mem /realssd.iso (0xff) map --hook chainloader (0xff)
Posted 26 May 2015 - 12:36 AM
I am trying to boot to Bitedender-rescue-cd.iso the is on the root of my usb drive. I have made the following boot string to my menu.lst. It boots all of the way to the splash screen then askes for the path to /rescue/livecdsquashfs.
I need to add a boot loop to point back to this file. Can anyone help me?
Thanks
Carfan
title Boot from Bitdefender Recsue CD
find --set-root /bitdefender.iso
map --heads=0 --sectors-per-track=0 /bitdefender.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)
loopback loop /bitfefender.iso
/rescue/livecd.squashfs isoloop=/bitdefender.iso
Posted 09 September 2015 - 11:55 PM
Is it possible to boot clonezilla-live-20150805-vivid-amd64.iso or clonezilla-live-20150805-vivid-i386.iso from a partition in HDD using grubfordos?
alacran
Posted 10 September 2015 - 12:18 PM
Is it possible to boot clonezilla-live-20150805-vivid-amd64.iso or clonezilla-live-20150805-vivid-i386.iso from a partition in HDD using grubfordos?
alacran
yes
Posted 10 September 2015 - 09:25 PM
yes
Good, Can you post the required config to put in menu.lst?
I tried this:
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.
alacran
Posted 11 September 2015 - 02:33 AM
1. The name. GRUB4DOS seems like an outdated name. Especially the "DOS" part. Might have been suitable way back then but not now. DOS is an outdated OS.
2. Not UEFI-compatible(?)
3. Need to edit text files to configure it. Not necessarily bad but I'd prefer to configure something via commands or a GUI.
Posted 11 September 2015 - 09:15 AM
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.
Posted 11 September 2015 - 01:10 PM
FWIW, (I'm not sure what you meant, but) Syslinux has "gptmbr.bin", so it _can_ be used in BIOS systems with GPT, and there is syslinux.efi for UEFI systems (with GPT too).2. It can only be MBR-booted (like syslinux)
Posted 11 September 2015 - 01:27 PM
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
0 members, 1 guests, 0 anonymous users