Jump to content











Photo
* * * * * 2 votes

post here anything that crosses your mind about grub4dos


  • Please log in to reply
257 replies to this topic

#251 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 16066 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 13 September 2016 - 01:06 PM

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.

 

Sure, that was 8 (eight) years ago and with a board and domain change in the middle, and then again those rules are not valid anymore, having been replaced by these ones (derived from those of Amnesty International, just for the record), actually "Site Policies":

http://reboot.pro/to...-site-policies/

 

(link is right bottom, as "Site Policies")

 

:duff:

Wonko



#252 xpt

xpt

    Frequent Member

  • Advanced user
  • 138 posts
  •  
    Canada

Posted 28 July 2019 - 08:12 PM

Alright, ever since tinybit's 1st post more than 10 years ago,

 

Ubuntu LiveCD.iso successfully booted from USB thumbdrive:
 

title Ubuntu LiveCD find --set-root /ubuntu-9.04-beta-desktop-i386.iso map /ubuntu-9.04-beta-desktop-i386.iso (0xff) map --hook root (0xff) kernel /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=/ubuntu-9.04-beta-desktop-i386.iso quiet splash locale=zh_CN.UTF-8 -- initrd /casper/initrd.gz boot
You may replace the Chinese locale "locale=zh_CN.UTF-8" with your own locale, or simply strip it out for the default English locale.

 

Ubuntu LiveCD.iso has been working, all the way  to [Ubuntu 18.04 ISO](https://ubuntuforums...d.php?t=2398574), however I found it doesn't work for me. 

 

I can see from the boot process, a printout indicating the ISO has been found, showing it is of type joite or something similar. Then an error message of file not found, and an url for the grub4dos home page. So I guess the error is still from within grub4dos. Not the iso itself. 

 

Again, here is the entry that I used:

title Ubuntu 18
find --set-root /iso/ubt1804.iso
map --heads=0 --sectors-per-track=0 /iso/ubt1804.iso (0xff)
map --hook
root (0xff)
kernel /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=/iso/ubt1804.iso splash
initrd /casper/initrd.lz


#253 xpt

xpt

    Frequent Member

  • Advanced user
  • 138 posts
  •  
    Canada

Posted 28 July 2019 - 08:16 PM

So what really worked in that thread might be the "map --mem /iso/ubt1804.iso (0xff)" part, not the "map --heads=0 --sectors-per-track=0 /iso/ubt1804.iso (0xff)" part. 

 

BTW, what's the difference between mapping to "(0xff) " and "(hd32) "?



#254 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 28 July 2019 - 08:24 PM

grub4dos usually displays the line that had the error?

 

The attached code works for me.

 

Most Ubuntu ISOs contain a loopback.cfg file. - check this for a clue to the correct syntax.

 

What version of grub4dos are you using?

Attached Thumbnails

  • ubu1804.JPG


#255 xpt

xpt

    Frequent Member

  • Advanced user
  • 138 posts
  •  
    Canada

Posted 28 July 2019 - 08:29 PM

I didn't get that far. I didn't see the "Booting..." line. 

 

Which version of g4d are you using? Mine is grub4dos-0.4.6a, of the latest download. 

 

The attached code works for me.

 

 

Thanks for the reply, can you post your menu entry please? 



#256 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 28 July 2019 - 08:35 PM

see https://www.rmprepus...utorials/ubuntu

Since it works for everyone else, can you post what line you get the grub4dos error on and  what version of grub4dos you are using (tip: It should be grub4dos 0.4.6a)

 

http://grub4dos.chenall.net/

 

I suggest this version http://dl.grub4dos.c...a-2019-06-17.7z  as there are a few bugs in the July 2017 version. Just replace the \grldr file.



#257 xpt

xpt

    Frequent Member

  • Advanced user
  • 138 posts
  •  
    Canada

Posted 28 July 2019 - 08:42 PM

I am using the http://dl.grub4dos.c...a-2019-06-17.7zone. 

However, I'm unable to capture thus post what line I get the grub4dos error for now, but hopefully I can get back to you shortly, since I'm prepare for my new machine... 



#258 tinybit

tinybit

    Gold Member

  • Developer
  • 1175 posts
  •  
    China

Posted 29 July 2019 - 11:32 AM

what's the difference between mapping to "(0xff) " and "(hd32) "?

 

mapping to (0xff) is for the DOS CDROM driver eltorito.sys.

 

If you are mapping an ISO, but will not start DOS, then you don't have to use (0xff).

 

If you are mapping an ISO and you will start DOS, but you don't use eltorito.sys in your CONFIG.SYS, then you don't have to use (0xff).

 

If you wish eltorito.sys to work fine with the virtual CDROM created by a grub4dos mapping, you should use the eltorito.sys file inside the grub4dos package, and must use virtual CDROM drive number 0xff for the mapping.

 

On other cases, (0xff) and (hd32), (hd33) ... all should work with no differences.



#259 Magnetic

Magnetic
  • Members
  • 0 posts
  •  
    Azerbaijan

Posted 10 January 2023 - 03:01 PM

Greetings to everyone! 

 

I’ve been trying to run a Linux distro (Mabox) from my multiboot (16Gb FAT32) usb stick. The usb stick has a few other Linux-based ISOs on it atm and I can run them with no problem at any time (those in use at the moment include Slax v11.3, Tails v5.8, Mint LMDE-5 Cinnamon and the latest Porteus KDE, let alone those tested in the past but not in use/erased - MX Linux, Refracta, and a few others, including even android based Remix OS). The usb stick has Grub4DOS v0.4.6a installed on both MBR and PBR and I have never experienced any issues with running Linux distros from it. Until I stumbled upon an Arch based (Manjaro based - to be exact) Mabox Linuxrolleyes.gif .

Long story short - when I try to run Mabox from the same usb stick - the grub4dos loader shows Mabox in the list of systems available for boot, but when I select it and hit enter - I end up with a “Welcome to GRUB!” message in the top left corner of my screen and inability to run any commands or quit. Not sure if the issue is related to grub4dos settings or to Mabox in particular. Does anyone have a clue how to get the grub4dos loader to boot Mabox or maybe make Mabox “more willing” to be bootable by grub4dos? I’m not a Linux kicking monster pro, no previous experience with Arch based systems (yet), so pls be patient. What I want is to get Mabox running on my multiboot usb stick (to minimize the number of usb drives needed for separate live mediums), so I’m just trying to figure out why Debian based distros (e.g. the latest Mint LMDE5 or Tails), Slackware based (Slax and the latest Porteus) and even Android based (Remix OS) - are all bootable from my multiboot usb pendrive, and why Manjaro (i.e. Arch) based Mabox does not boot Later I also downloaded the latest official Manjaro KDE ISO from their official webpage and the result was the same - "Welcome to Grub!" stall...

 

So the question is: Is there anything that makes Manjaro-based (and possibly other similar Arch based) ISO that "special" for Grub4Dos... and is there a way to circumvent/tweak some settings to make them bootable? Thanks in advance for any help! 






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users