Jump to content











Photo
- - - - -

Grub4Dos boot Computerbild Notfall-DVD


  • Please log in to reply
17 replies to this topic

#1 nierewa

nierewa

    Frequent Member

  • Advanced user
  • 107 posts
  •  
    Germany

Posted 24 March 2019 - 10:53 AM

Hi,

 

I tried to boot Computerbild Notfall-DVD without success.

 

Inside iso is a grub.cfg file:

 

if loadfont /boot/grub/font.pf2 ; then
        set gfxmode=auto
        insmod efi_gop
        insmod efi_uga
        insmod gfxterm
        terminal_output gfxterm
fi

set menu_color_normal=white/black
set menu_color_highlight=black/light-gray

set timeout=30

menuentry "Notfall-DVD 10.0 Free starten" {
        set gfxmode=text
        set gfxpayload=keep
        linux   /boot/kernel/ldefsf pgcolor=31 memtest=4 security=none toramdirs=\|Anleitungen\|scancl\| skipcheck=1 lang=de xlocale=de_DE.UTF-8 nolangsel=1 ejectonumass=1 skipservices=\|installer\|xconfgui\|roothash\|firewall\|ssh\|mountdrives\| hwid=unknown laxsudo=1 optram=1 toram=1200000 uuid=all crypt=all blobsize=2048 swapsize=1024 homecont=0000-00000 loop.max_loop=32 console=tty2 quiet ultraquiet=3 
	initrd	/boot/kernel/initram.img /boot/kernel/idefsf.img
}

menuentry "Notfall-DVD 10.0 Free starten (abgesicherte Grafik)" {
        set gfxmode=text
        set gfxpayload=keep
        linux   /boot/kernel/ldefsf pgcolor=31 memtest=4 security=none toramdirs=\|Anleitungen\|scancl\| skipcheck=1 lang=de xlocale=de_DE.UTF-8 nolangsel=1 ejectonumass=1 skipservices=\|installer\|xconfgui\|roothash\|firewall\|ssh\|mountdrives\| hwid=unknown laxsudo=1 optram=1 toram=1200000 uuid=all crypt=all blobsize=2048 swapsize=1024 homecont=0000-00000 loop.max_loop=32 console=tty2 quiet ultraquiet=3 radeon.modeset=0 nouveau.modeset=0 nomodeset 
	initrd	/boot/kernel/initram.img /boot/kernel/idefsf.img
}

#menuentry "Arbeitsspeicher testen" {
#	linux /boot/kernel/memtest.bzi
#}

menuentry "Windows starten" {
	exit
}

First I triy to boot the iso in two different ways: menu.lst

title Notfall-DVD hd32
find --set-root /Notfall-DVD.iso
map --mem /Notfall-DVD.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)

title Notfall-DVD kernel
find --set-root /Notfall-DVD.iso
map /Notfall-DVD.iso (0xff)
map --hook
root (0xff)
kernel /boot/kernel/ldefsf pgcolor=31 memtest=4 security=none skipcheck=1 lang=de xlocale=de_DE.UTF-8 nolangsel=1 ejectonumass=1 skipservices=\|dhcpcd\|earlynet\|dhcpcd\|earlynet\|installer\|xconfgui\|roothash\|firewall\|ssh\|mountdrives\| hwid=unknown laxsudo=1 optram=1 toram=1200000 uuid=all crypt=all blobsize=2048 swapsize=1024 homecont=0000-00000 skipntfs=1 loop.max_loop=32 console=tty2 quiet ultraquiet=3
initrd /boot/kernel/initram.img /boot/kernel/idefsf.img

Nothing.

 

So I extract the iso: menu.lst

title Computerbild Notfall-DVD 13
kernel 	/Notfall-DVD/boot/kernel/ldefsf  boot=/Notfall-DVD/boot/kernel/ldefsf live-media-path=/Notfall-DVD cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid  quiet splash -- vga=791
initrd 	/Notfall-DVD/boot/kernel/initram.img /Notfall-DVD/boot/kernel/idefsf.img

But all end's up with: System nicht gefunden

 

Can someone help me?



#2 steve6375

steve6375

    Platinum Member

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

Posted 24 March 2019 - 02:15 PM

If you make a USB drive as they describe (direct write - I used RMPrepUSB - File>Drive button because the image writer app they provide failed with a write error) and boot it on a real system, it will take up to 20 minutes to partition and initialise the USB drive on first boot.
Presumable it is doing some quite hairy stuff and I guess the partition arrangement when booting from a different USB drive is not what it is expecting!

After the first boot the MBR is:

Partition 1   SIZE=21352MiB   Type: EF   *ACTIVE*
START POS   = CYL:335 HD:135 SEC:57	   END POS = CYL:1023 HD:254 SEC:63START (LBA) = 5,390,336 (00524000) SIZE (LBA) = 43,728,896 (029B4000) [End=49,119,231]
Partition 2   SIZE=0MiB   Type: 00	   
START POS   = CYL:0 HD:0 SEC:0	   END POS = CYL:0 HD:0 SEC:0START (LBA) = 0 (00000000) SIZE (LBA) = 0 (00000000)
Partition 3   SIZE=0MiB   Type: 00	   
START POS   = CYL:0 HD:0 SEC:0	   END POS = CYL:0 HD:0 SEC:0START (LBA) = 0 (00000000) SIZE (LBA) = 0 (00000000)
Partition 4   SIZE=0MiB   Type: 00	   
START POS   = CYL:0 HD:0 SEC:0	   END POS = CYL:0 HD:0 SEC:0START (LBA) = 0 (00000000) SIZE (LBA) = 0 (00000000)

P1   Start=5,390,336 (2,759,852,032 bytes) End=49,119,231 (25,149,046,272 bytes)

Transferring the files to another USB drive does not work. It recognises that the partition arrangement is different and gives a long message in German about using a DVD or making a USB drive correctly!
UEFI-booting gives the same issue.
Booting using E2B and the partnew technique doesn't work either.


Edited by steve6375, 24 March 2019 - 02:19 PM.


#3 nierewa

nierewa

    Frequent Member

  • Advanced user
  • 107 posts
  •  
    Germany

Posted 25 March 2019 - 12:59 PM

If you burn the iso to DVD it will also work without repartioning.

 

So I tried to use syslinux to boot the isolinux.cfg renamed to syslinux.cfg how descriped her: Method 2

 

First I got an error "Not a COM32R image" so I used syslinux 5.01
I got: Failed to load libcom32.c32 and COM32 file vesamenu.c3

 

So I downloaded Syslinux 6 and use the syslinux.exe in folder syslinux-6.03\bios\win32
Now I get no error message only boot: _                -> nothing happens



#4 steve6375

steve6375

    Platinum Member

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

Posted 25 March 2019 - 01:03 PM

I think that the kernel boots and then looks to see if the boot media is a usb flash drive.

If so it 'does something' to the drive (maybe uses the unused areas as swap space?).

 

I had no luck with syslinux either. 



#5 nierewa

nierewa

    Frequent Member

  • Advanced user
  • 107 posts
  •  
    Germany

Posted 25 March 2019 - 02:56 PM

 

I think that the kernel boots and then looks to see if the boot media is a usb flash drive.

I think you're right.

So all we have to do is "emulate" a dvd drive if its possible.

 

By the way I changed all *.cfg files and it booted but the same long message in German about using a DVD or making a USB drive correctly!



#6 nierewa

nierewa

    Frequent Member

  • Advanced user
  • 107 posts
  •  
    Germany

Posted 25 March 2019 - 05:53 PM

I found an option for Safe Boot which loads the DVD to RAM.
This work for an Stick build with LinuxLive USB Creator but not for the Multi USB Boot Stick.

 

Don't know why :unsure:
 



#7 nierewa

nierewa

    Frequent Member

  • Advanced user
  • 107 posts
  •  
    Germany

Posted 25 March 2019 - 08:05 PM

I've copied all files from the stick I've created with LinuxLive to the MultiUSB Stick.
With that and Syslinux (Post 3) it works.



#8 steve6375

steve6375

    Platinum Member

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

Posted 25 March 2019 - 08:07 PM

Safe boot or default boot?

Can you give step-by-step outline please?



#9 nierewa

nierewa

    Frequent Member

  • Advanced user
  • 107 posts
  •  
    Germany

Posted 27 March 2019 - 11:31 AM

Both is working.

 

I have an Mutiboot USB Stick created with AIO.

 

1. Create an other USB Stick with LinuxLive USB Creator.

 

LiLi.png

 

2. On Multiboot USB Stick created with AIO install Syslinux explained here in Method 2

    Be Sure you have Downloaded the newest Syslinux.exe (6.03) from here.
    You found the syslinux.exe in /bios/win32

3. Copy the whole LiLi USB Stick to the root of the Multiboot Stick

4. Add to e.g. Linux.lst in /AIO/File chainloader /syslinux.bin

5. You can choose what you want

 

VirtualBox_USB%20Boot_27_03_2019_11_55_5

VirtualBox_USB%20Boot_27_03_2019_11_58_2

VirtualBox_USB%20Boot_27_03_2019_11_58_3

VirtualBox_USB%20Boot_27_03_2019_12_00_1

That's it

 

The only thing that irritates me is the statement: Computerbild Notfall-DVD 10



#10 steve6375

steve6375

    Platinum Member

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

Posted 27 March 2019 - 12:15 PM

Do you mean

Step 1 - create a USB stick

Step 1a - boot from it and allow it to get to the Desktop

Step 1b - shutdown

Step 2...

 

???

[Edit] No, he means just use the ISO files without booting it first![/Edit]


Edited by steve6375, 27 March 2019 - 07:46 PM.


#11 nierewa

nierewa

    Frequent Member

  • Advanced user
  • 107 posts
  •  
    Germany

Posted 27 March 2019 - 02:51 PM

Hmm. If I remember correctly, I tried to boot in VirtualBox.
But it didn't work.



#12 steve6375

steve6375

    Platinum Member

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

Posted 27 March 2019 - 03:47 PM

OK - I have it working now in E2B, thanks.

I was using the Notfall USB flash drive which I had already booted as the 'Master'.

But this doesn't work.

Actually, for E2B it is quite simple.

Just convert the ISO to a FAT32 .imgPTN file using MakePartImage!



#13 steve6375

steve6375

    Platinum Member

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

Posted 27 March 2019 - 07:41 PM

P.S. ISO boots fine too with E2B - just add it to the E2B menu folder.

If using VBox, use the Safe Boot 1024x768 (old PCs) boot option.



#14 nierewa

nierewa

    Frequent Member

  • Advanced user
  • 107 posts
  •  
    Germany

Posted 28 March 2019 - 03:36 PM

Cool.

 

I use AIO because the simply UEFI support.

 

Can I boot the converted ISO to a FAT32 .imgPTN file using MakePartImage! also with this one?



#15 steve6375

steve6375

    Platinum Member

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

Posted 28 March 2019 - 03:43 PM

Yes, but you may need to use the latest Beta of MPI Tool Kit to get the UEFI boot files in the image.

 



#16 steve6375

steve6375

    Platinum Member

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

Posted 28 March 2019 - 03:45 PM

P.S. The latest Beta of MPI can also add rEFInd and a WinPE image.

This means you can UEFI-boot and change to another .imgPTN file without needing to MBR-boot or use another Windows system.

See blog post.



#17 nierewa

nierewa

    Frequent Member

  • Advanced user
  • 107 posts
  •  
    Germany

Posted 28 March 2019 - 05:22 PM

Ok. I've downloaded the package MPI_Tool_Pack_Plus_CloverLite_093v7.zip

 

May you give me an outline how to create and boot  a FAT32 .imgPTN file?
Am I using grub4dos or syslinux?



#18 steve6375

steve6375

    Platinum Member

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

Posted 28 March 2019 - 05:44 PM

See blog post link here!


Edited by steve6375, 28 March 2019 - 05:45 PM.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users