1 reply to this topic

[nguyenthu012]

This thread is to discuss how the Easy2Boot (as it is currently called) grub4dos multiboot USB drive project can be developed, enhanced and improved.
The idea (from sambul61) is to create a multiboot USB drive to which the novice user can easily and quickly add any boot image he or she wants to their multiboot USB drive.
All that is needed is the correct grub4dos menu mnu file and the 'payload' file (an ISO in most cases). We, at reboot.pro can easily provide the required grub4dos menu file (called xxxxx.mnu for Easy2Boot) and so can provide a bank of these mnu files which can be kept up to date.

This project is similar to the grub4dos grub4dos, .iso images and (hd32) or (0xFF) mapping topic, but Easy2Boot will apply to any type of bootable binary that can be booted via grub4dos (or possible from grub4dos via syslinux) and will provide a .mnu file which the user simply copies to his Easy2Boot USB drive (no editing of their menu.lst required).
The user can delete the 'payload' files and leave the mnu files on the drive - the relevant menu entries will NOT appear on the user menu until the user chooses to add back on the payload file.

[Wonko the Sane]

This thread is to 
discuss how the Easy2Boot (as it is currently called) grub4dos multiboot USB drive project can be developed, enhanced and improved.
The idea (from sambul61) is to create a multiboot USB drive to which the novice user can easily and quickly add any boot image he or she wants to their multiboot USB drive.
All that is needed is the correct grub4dos menu mnu file and the 'payload' file (an ISO in most cases). We, at reboot.pro can easily provide the required grub4dos menu file (called xxxxx.mnu for Easy2Boot) and so can provide a bank of these mnu files which can be kept up to date.
This project is similar to the grub4dos grub4dos, .iso images and (hd32) or (0xFF) mapping [/b] topic, but Easy2Boot will apply to any  type of bootable binary that can be booted via grub4dos (or possible from grub4dos via syslinux) and will provide a .mnu file which the user simply copies to his Easy2Boot USB drive (no editing of their menu.lst required).
The user can delete the 'payload' files and leave the mnu files on the drive - the relevant menu entries will NOT appear on the user menu until the user chooses to add back on the payload file.

 


I don't get it . (but maybe it is just me )
There is nothing to discuss.
And there is nothing in common with the original "grub4dos, .iso images and (hd32) or (0xFF) mapping" topic (I do know about it because I actually started it ).

That topic (now titled "post here anything that crosses your mind about grub4dos" thanks to the good members of the forum that insisted on posting there unrelated things):
 
 
 

This thread is reserved for people reporting their success using newish releases of grub4dos that allow for direct booting to a .iso imaging through mappig the ISO image to (hd32).

Ideally, any user who had some success with this way of booting can post here reporting what he succeeded with and how he did it, links to other boards, tutorials guides related to the matter are also welcome.

PLEASE NO request for help here, post them in the grub4dos forum.

PLEASE NO "Nice, thank you!" kind of posts.

PLEASE NO "Ha, this is not useful!" type of comments.

This thread should become simply a list of working setups, no more, no less.

Thanks for cooperation.

jaclaz

was meant to collect from people having succesfully tested/booted something their menu.lst entries (i.e. in that thread there was a call for the - specific - experience from non-novice users in order to allow other non-novice users to need not to do experiments already performed successfully).
 
Easy2boot (partially thanks to that and other threads, but much more due to the persistence and abilities of Steve6375  ) ALREADY supports countless OS's/Distro's/whatever.
 
Any (senceful) novice user can use it "as is", choosing among the vast "catalogue" of already available "booting targets" BEFORE learning how the tool works in order to boot something very peculiar not already listed (an by that time he/she won't be a novice user anymore).

The reference topic (by Sambul61) is this one:
http://reboot.pro/to...u-want-to-boot/
which turned out - as often happens - as a generic support topic for Easy2boot and/or grub4dos.
 
So WHAT EXACTLY are you proposing?
1) a "Hey, novice user ask here for a .mnu file for a never heard before and used by noone OS" kind of thread (this would actually be loosely similar to the above "Easy2Boot - post link to ANY live ISO or Floppy you want to boot" topic) kind of thread
2) a "Hey, not-novice user share here .mnu files for a never heard before and used by noone OS you succeeded with" (this would actually be loosely similar to the original "grub4dos, .iso images and (hd32) or (0xFF) mapping" topic) kind of thread
3) something else (please describe)




Wonko