Jump to content











Photo
- - - - -

MakeIso


  • Please log in to reply
102 replies to this topic

#76 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 2 weeks ago

The file lba i.e where should the boot code (stage1?) look for for the rest of the booting code (stage2)?

 

You mean the:

bi_file: dd 0 ; LBA of boot file

 

That needs to be changed to where the image is written, but - again accordingly to what I found out at the time, the checksum should be excluding the first 64 bytes. :unsure:

http://www.msfn.org/...comment=1085390

 

Maybe that is the issue. :dubbio:

 

NO, wait, re-checking the bytes Ady posted I see that the bi_file: (offset 0x0C) is left to 0.

 

That is no good.

 

But then also the image checksum needs to be modified :dubbio:

 

:duff:

Wonko



#77 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted 2 weeks ago

You mean the:

bi_file: dd 0 ; LBA of boot file

 

That needs to be changed to where the image is written, but - again accordingly to what I found out at the time, the checksum should be excluding the first 64 bytes. :unsure:

http://www.msfn.org/...comment=1085390

 

Maybe that is the issue. :dubbio:

 

NO, wait, re-checking the bytes Ady posted I see that the bi_file: (offset 0x0C) is left to 0.

 

That is no good.

 

But then also the image checksum needs to be modified :dubbio:

 

:duff:

Wonko

 

That "boot table" or "not boot table" got my head dizzy  :crazy:

I'll drop it for now, get a good night of sleep over it (or several) and will review it from scratch.



#78 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted A week ago

Note that a new version has been uploaed.

1.0.0.8
windows 7 minimum
patch table as an option (right click on boot file button)


#79 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted A week ago

@Wonko, slightly deviating from the topic but I am struggling with mtools...

 

Trying to copy bootia32.efi within the floopy and on the fly create a \efi\boot folder.

Any idea?

 

So far I managed the below but the folder structure is wrong (obviously) in my floppy.

mformat -C -f 1440 -v GRUB2 -i GRUBi386.IMA ::
mcopy -i GRUBi386.IMA bootia32.efi ::


#80 Blackcrack

Blackcrack

    Frequent Member

  • Advanced user
  • 329 posts
  •  
    Germany

Posted A week ago

{
a sidekick suggestion/idea, for make an iso bootloader Menu,
where it is on focussing to make a folder on a usb-stick and usb-hdd by installing,
to put all iso files in, at next but, if not exist, or it's not the same iso's who be on last iso's
update the listing for "boot the iso's" and greate a Menu from the "dir /B ./iso-files".
Therewith it could be possible for create ever an an dynamic(autmatic a static) Menu of the names
from the iso's in ./iso-files if the listing not like the exist one.
on the 2nd step could if the listing the same lake before, maybe add (include) a destription
file of the "dir /B" file where overwrites the dir /B ./iso-files entrys [blabla1.iso] and [dootbla2.iso]
in "destription.txt" and replaced the directory entrys as example :

info:
MS WinNT "dir /B" it is in linux bashtools "ls -1"

if exist entrys in directory.txt and directory.txt == "dir /B ./iso-files" then use the file directory.txt,
else generate a directory.txt with entrys
[dir /B iso-files %1]
[dir /B iso-files %1]
[dir /B iso-files %1]
[dir /B iso-files %1]
 
if exist a menutitle.txt {the entrys of menutitle.txt == directory.txt } read the "$description"
of the menutitle.txt and put it in the menu
else create menutitle.txt
[dir /B iso-files %1] \n "dir /B iso-files %1"
[dir /B iso-files %1] \n "dir /B iso-files %1"
[dir /B iso-files %1] \n "dir /B iso-files %1"
[dir /B iso-files %1] \n "dir /B iso-files %1"
and put the "$description" in the menu
 
 
if exist the "menutitle.txt"
-------------------------------------------------------------------------------------------------------
[blabla1.iso]
"The Bootiso of Partitions Programm"
md5 423423423423423424 // (optional md5 for make it as "original")
[bootbla2.iso]
"Reactos trunk Bootiso Alpha Version xxxx of ypselon 650"
md5 97849347349048349343 // (optional md5 for make it as "original")
[installbla2.iso]
"Linux Distriebution developer version, Date 2014.04.23 32Bit"
md5 232348238239223402380  // (optional md5 for make it as "original")
[installbla264.iso]
"Linux Distribution developer version, Date 2014.04.23 64Bit"
md5 34234232374237423982389  // (optional md5 for make it as "original")
-------------------------------------------------------------------------------------------------------
else generate a menutitle.txt
[dir /B iso-files %1] \n "dir /B iso-files %1"
[dir /B iso-files %1] \n "dir /B iso-files %1"
[dir /B iso-files %1] \n "dir /B iso-files %1"
[dir /B iso-files %1] \n "dir /B iso-files %1"
and put the "$description" in the menu
 
 
have we a Clean menu or a menu from the files
 
Fresh Generate :
 
||======================================================||
||[_blabla1.iso_____________________________]
||  bootbla2.iso
||  installbla2.iso
||  installbla264.iso
||======================================================||
the next:
if exist a menutitle.txt  and the entrys exist [entry1] [entry2] replace the entrys with the "$description" of the entrys
else create a '$file(menutitle.txt)' with entrys and '$description(blabla1.iso)' and '$description(dootbla2.iso)'
 
or with rewrited menu Entrys from the Admin/Extended User on an usb-stick or to burning Blueray-iso-folder
if exist the "menutitle.txt"
-------------------------------------------------------------------------------------------------------
[blabla1.iso]
"The Bootiso of Partitions Programm"
md5 423423423423423424 // (optional md5 for make it as "original")
[bootbla2.iso]
"Reactos trunk Bootiso Alpha Version xxxx of ypselon 650"
md5 97849347349048349343 // (optional md5 for make it as "original")
[installbla2.iso]
"Linux Distriebution developer version, Date 2014.04.23 32Bit"
md5 232348238239223402380  // (optional md5 for make it as "original")
[installbla264.iso]
"Linux Distribution developer version, Date 2014.04.23 64Bit"
md5 34234232374237423982389  // (optional md5 for make it as "original")
-------------------------------------------------------------------------------------------------------
and the menu show's like this :
 
||=================================================================||
||[_The Bootiso of Linux Partitions Programm______________________]
||  Reactos trunk Bootiso Alpha Version xxxx of ypselon 650
||  Linux Distribution developer version, Date 2014.04.23 32Bit
||  Linux Distribution developer version, Date 2014.04.23 64Bit
||=================================================================||
therewith have we a automatic dynamical generate Menu for an bootmenu
with the possible for editing the menutitle.txt and changing the Entrys in the menu
if the files do not change via name.iso it is loading the files both files without changing
and create a well human reading Menu.
if the file nomore exist , can be the entry changing with "error file %1 not exist"
if the medium readonly -r (® works not) or optional otherwise wrong md5sum "wrong MD5 from file %1" in the Menu behind the burning
if it is burned on CD/DVD or Blueray ..
in the USB or USB-HDD can be this entry dynamical rewrite
and/or optional "wrong MD5 from file %1" in the Menu behind the burning
and save the file because usbstick or hdd data loss
(if there exist a possible (rw/r able))

the names and description base on the name of the iso's (not size or md5checksum)

therewith it is possible for create a usb-stick with a folder for iso-files
and the user can put easy the iso-files in ./iso-files and the menu it is dynamic
generate from the iso-file-name.iso if not change it is possible for change the description
in an human reading descrition like "This is the entry of the iso-file from March \n Version XX with own bootloader \n and Tools : one two tree"

this it is able to buring if all works on the usb-stick
to a DVD or a bueray with 50 Gigabyte and manny iso's with description,
because the user can create the directory.txt and menutitle.txt by self
and can add many iso's also where he can put into the ./iso-files .

this is also well for storing many different distribution's iso of linux
and other iso's on an Administration's blueray, as example..

a menu "bakery" out of the "ls -1" or "dir /B" in ./isofiles
with the possible if the name of the iso not change,
change/update the description manually to an human readable.
}

#81 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted A week ago

 

@Wonko, slightly deviating from the topic but I am struggling with mtools...

 

Trying to copy bootia32.efi within the floopy and on the fly create a \efi\boot folder.

Any idea?

 

So far I managed the below but the folder structure is wrong (obviously) in my floppy.



mformat -C -f 1440 -v GRUB2 -i GRUBi386.IMA ::
mcopy -i GRUBi386.IMA bootia32.efi ::

I am not sure to understand.

Meaning why do you want/need an efi\boot structure within the floppy?

 

I made a batch (for other uses) here:

http://reboot.pro/to...o-gpt/?p=193659

 

with parameters/commands explicited, the mtools do have some "quirk", but from what I found out at the time was the mdir that needed a .ini, the mmd should work normally. :unsure: , maybe you were fooled by th euse of *nix paths with forward slashes?

::The default target image is set to "HiddenGPT.img", you can change this name below:
IF NOT DEFINED ImgName SET ImgName=HiddenGPT.img



::Set Parameters for mformat
::This is not really *needed* but it makes easier to understand the parameters
::should they need to be changed or for future re-use

::Total image size 1985 given as 2047-63+1
SET ImgSize=-T 1985
::Standard 255/63 geometry
SET HSGeom=-h 255 -s 63
::Fixed Volume Serial Number, just for the fun of it
SET VolSerial=-N 66537457
::Arbitrary Label Note: if you want a simple (not VFAT) label the name must be all CAPITAL letters
::this is seemingly non-standard as FAT12 Labels should be ALL CAPITALS anyway 
SET Label=-v G4D_BIOSGPT
::Sectors Before 63
SET SectBefore=-H 63
::Cluster size, 512 bytes size=1 sector size
SET ClustSize=-c 1
:: Size for Root directory in sectors, 1 equates to 16 entries that should be enough
SET RootSize=-r 1
::Number of fats, usually 2, here set to 1 to spare as much sectors as possible
SET NumFats=-d 1
::Bootsector, the "standard" FAT12 bootsector, here with drive number pre-set to 80 because Mformat misses a way to set it
SET Bootsector=-B FAT12grldr.bss
::Media Type F8, hard disk volume
SET Mediatype=-m F8
::Target image
SET Target=-i %ImgName%

::Senseless But Sometimes Needed Double Colon, which means "the drive which is mapped from the image specified with -i"
SET SBSNDC=::

::SET path to Mtools.ini as an environment variable
::This is needed to have mdir work as expected
SET MTOOLSRC=Mtools.ini
IF NOT EXIST Mtools.ini ECHO MTOOLS_SKIP_CHECK=1 >Mtools.ini


::Run the actual format to Create the target image
mformat -C %ImgSize% %HSGeom% %Label% %SectBefore% %ClustSize% %RootSize% %NumFats% %Bootsector% %Mediatype% %VolSerial% %Target% %SBSNDC%

::create the same directory structure as the contents of the \root subdirectory ("root" being the name of a subdir of where the batch is)
::use some of the usual common sense, don't use paths with spaces, strange characters, stupidly long filenames/paths, etc.
::in theory using the mcopy with the -s switch (recursive) should need not these loops, but I cannot make it work in practice
SET SubDir=root



IF NOT EXIST %~dp0%SubDir% ECHO Nothing to copy, an empty image was created...&GOTO :Aborted

FOR /F "delims=" %%A IN ('DIR %~dp0%SubDir% /A:D /B /S') DO (
SET Reldir=%%A
SET Reldir=!Reldir:%~dp0%SubDir%\=!
SET Reldir=!Reldir:\=/!
ECHO mmd "!Reldir!" %Target%
mmd "!Reldir!" %Target%
)

FOR /F "delims=" %%A IN ('DIR %~dp0%SubDir% /A:-D /B /S') DO (
SET Relfile=%%A
SET Relfile=!Relfile:%~dp0%SubDir%\=!
SET Relfile=!Relfile:\=/!
ECHO mcopy "./root/!Relfile!" %Target% "%SBSNDC%!Relfile!"
mcopy "./root/!Relfile!" %Target% "%SBSNDC%!Relfile!"
)

mdir -/ %Target% |FIND /V "<DIR>" |FIND /V " files"
IF %ERRORLEVEL%==1 ECHO Oh, oh, an error occurred, no files in the image ...&GOTO :Aborted

Still, since you use a "simple" floppy image, if Extract cannot do what is needed, you can probably use good ol' BFI:

https://web.archive....p://nu2.nu/bfi/

 

Otherwise, the mtools (I know, I know) here:

https://web.archive....~fys/mtools.htm

 

May be still simpler than the mtools:

@echo off
SET Imaname=test144.ima
if exist %Imaname% del %Imaname%
imginit -fat12 %Imaname%
imgcpy .\bootia32.efi %Imaname%=a:\bootia32.efi
imgcpy %Imaname%=a:\efi
imgcpy %Imaname%=a:\efi\boot

And since the source is available (and to my unexperienced eyes simple enough), maybe you can re-assemble a monolithic executable.

 

In the meantime I'll make a couple tests with the "official" mtools :).

 

:duff:

Wonko



#82 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted A week ago

@Wonko

 

I want to build a floppy image which has the following folder/file structure : \efi\boot\bootia32.efi.

 

I tried mcopy ./efi/boot/bootia32.efi -i GRUBi386.IMA :: but it does not create the folder structure and simply puts bootia32.efi at the root of the floppy.



#83 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted A week ago

@Blackcrack

 

Thanks for the idea.

 

Do you mean generating a menu (menu.lst? isolinux.cfg) for a bootloader? isolinux? grub4dos?

 

I am not too good with scripting but I'll be more than happy to include your batch/script in makeiso zip file (with proper credits, etc).

 

Regards,

Erwan

 

EDIT : posted edited with the right nickname...


  • Blackcrack likes this

#84 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted A week ago

@Wonko

Tried the "old" mtools (which looked simpler to use).

Unfortunately, does not work on my x64 system (has been compiled for win32 only).

I could either recompile it or look at the code but I'll wait to see what you can do with the "newer" mtools.

I feel it is a "simple" syntax issue but still too "complex" for my scripting/bash skills...



#85 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted A week ago

This should do:

@ECHO OFF
SETLOCAL

::The default target image is set to "test288.ima", you can change this name below:
IF NOT DEFINED ImaName SET ImaName=test288.ima

::Set Parameters for mformat
::This is not really *needed* but it makes easier to understand the parameters
::should they need to be changed or for future re-use

::Total image size 5760
SET ImgSize=-T 5760
::Standard 36/2 geometry
SET HSGeom=-h 2 -s 36
::Fixed Volume Serial Number, just for the fun of it
SET VolSerial=-N 66537457
::Arbitrary Label Note: if you want a simple (not VFAT) label the name must be all CAPITAL letters
::this is seemingly non-standard as FAT12 Labels should be ALL CAPITALS anyway 
SET Label=-v A288FLOPPY
::Sectors Before 0
SET SectBefore=-H 0
::Cluster size, 1024 bytes size=2 sector size
SET ClustSize=-c 2
:: Size for Root directory in sectors, 1 equates to 16 entries, we want 240 here for the "standard" 2.88 floppy
SET RootSize=-r 15
::Number of fats, usually 2
SET NumFats=-d 2

::Bootsector, not used
::SET Bootsector=-B FAT12grldr.bss

::Media Type F0, 2.88 mb floppy
SET Mediatype=-m F0
::Target image
SET Target=-i %ImaName%

::Senseless But Sometimes Needed Double Colon, which means "the drive which is mapped from the image specified with -i"
SET SBSNDC=::

::Run the actual format to Create the target image
ECHO mformat -C %ImgSize% %HSGeom% %Label% %SectBefore% %ClustSize% %RootSize% %NumFats% %Bootsector% %Mediatype% %VolSerial% %Target% %SBSNDC%

mformat -C %ImgSize% %HSGeom% %Label% %SectBefore% %ClustSize% %RootSize% %NumFats% %Bootsector% %Mediatype% %VolSerial% %Target% %SBSNDC%



::create the \efi\boot directory structure
SET Reldir=./efi
ECHO mmd "%Reldir%" %Target%
mmd "%Reldir%" %Target%

SET Reldir=./efi/boot
ECHO mmd "%Reldir%" %Target%
mmd "%Reldir%" %Target%

::copy the file bootia32.efi to the folder
SET Relfile=bootia32.efi

ECHO mcopy "./%Relfile%" %Target% "%SBSNDC%%Reldir%/%Relfile%"
mcopy "./%Relfile%" %Target% "%SBSNDC%%Reldir%/%Relfile%"

ECHO Optional check of contents written
PAUSE

mdir -/ %Target% 
ECHO Done.
PAUSE
GOTO :EOF

Of course at the end of the day you can use only the three four command ECHOed.

 

The parameters provided are for a 2.88 Mb image, but of course you can (should) try with a smaller one.

 

This said, It makes (to me) little sense to have three or four files  74 kb each to create a "standard" image.

 

It would be IMHO easier to create an empty image (that compressed would take near to no space) with already the \efi\boot directory structure and just inject in it the bootia32.efi (or the bootx64.efi, or both)

 

By the same reasoning, the package containing the whole bloat of the GRUB2 thingy, some 12 Mb to generate three files, totaling 600Kb or so makes little sense to the "final" user, it would make sense to provide a "user" package with an already built set of bootia32.efi, bootx64.efi and grub.img (easier, smaller) and a "developer" edition where the few, advanced users affected by releasitis (another common affection that most Linux/*nix users have, consisting in always wanting to senselessly build themselves the latest version of *whatever*) can have their fun.

 

Personally I insist on trusting more the developer with working builds and on using builds that have been tested before resorting to self-build, let alone self-compile.

 

 

@Alacran

 

Thanks for the idea.

 

Do you mean generating a menu (menu.lst? isolinux.cfg) for a bootloader? isolinux? grub4dos?

 

I am not too good with scripting but I'll be more than happy to include your batch/script in makeiso zip file (with proper credits, etc).

 

Regards,

Erwan

 

Alacran ? :w00t:

Besides the user name, did you manage to understand - even partially - what Blackcrack wrote? :dubbio:

 

@Blackcrack

Really, I cannot make head or tail of what you were suggesting, I lost you at the second line, maybe you can try explaining it in plainer English?

 

:duff:

Wonko



#86 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted A week ago


Alacran ? :w00t:

Besides the user name, did you manage to understand - even partially - what Blackcrack wrote? :dubbio:

 

@Blackcrack

Really, I cannot make head or tail of what you were suggesting, I lost you at the second line, maybe you can try explaining it in plainer English?

 

:duff:

Wonko

 

Stupid me...

Doing several times in parallel (i like to multi task) but then confused a few opened posts in my browser...

fixing it...



#87 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted A week ago

@Wonko.

 

Script now works nice, thanks a lot for this.

Indeed, including the whole grub2 is a bit overkill as I could included only the built boot loaders.

I may trim the zip files later on.

 

My script JFYI.

grub-mkimage.exe -o grub.bin --format=i386-pc-eltorito --prefix="(cd)/boot/grub" multiboot part_msdos iso9660 biosdisk
grub-mkimage.exe -o bootia32.efi --format=i386-efi --prefix="(cd0)/boot/grub" multiboot fat part_msdos iso9660 part_gpt
grub-mkimage.exe -o bootx64.efi --format=x86_64-efi --prefix="(cd0)/boot/grub" multiboot fat part_msdos iso9660 part_gpt
rem efi images
SETLOCAL
rem x32
IF NOT DEFINED ImaName SET ImaName=grubia32.ima
::Target image
SET Target=-i %ImaName%
::Senseless But Sometimes Needed Double Colon, which means "the drive which is mapped from the image specified with -i"
SET SBSNDC=::
::Run the actual format to Create the target image
mformat -C -f 1440 -v GRUB2 %Target% %SBSNDC%
::create the \efi\boot directory structure
SET Reldir=./efi
mmd "%Reldir%" %Target%
SET Reldir=./efi/boot
mmd "%Reldir%" %Target%
::copy the file bootia32.efi to the folder
SET Relfile=bootia32.efi
mcopy "./%Relfile%" %Target% "%SBSNDC%%Reldir%/%Relfile%"
mdir -/ %Target% 
rem x64
SET ImaName=grubx64.ima
::Target image
SET Target=-i %ImaName%
::Senseless But Sometimes Needed Double Colon, which means "the drive which is mapped from the image specified with -i"
SET SBSNDC=::
::Run the actual format to Create the target image
mformat -C -f 1440 -v GRUB2 %Target% %SBSNDC%
::create the \efi\boot directory structure
SET Reldir=./efi
mmd "%Reldir%" %Target%
SET Reldir=./efi/boot
mmd "%Reldir%" %Target%
::copy the file bootx64.efi to the folder
SET Relfile=bootx64.efi
mcopy "./%Relfile%" %Target% "%SBSNDC%%Reldir%/%Relfile%"
mdir -/ %Target% 


#88 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted A week ago

I will (try to) create a new topic and merge the last posts of this thread.



#89 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted A week ago

Isolinux discussion (incorrect boot table checksum field) moved here.

 

My first post/introduced got smashed when I moved all post from here to there.

 

Tring to insert a topic #1 now ... if anyone knows how to do it ...

 

EDIT : got it sorted... obviously, posts are sorted by time so insert a topic #1 today but dated 3 days ago a bit challenging (to me at least).



#90 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted A week ago

New version uploaded.

1.0.0.9
xpsp2 (+WindowsXP-KB932716-v2) supported

Although Wonko might be the last person on our planet using WinXP, I have enabled support for XP SP2 (and up) :)

No multiboot thus for now on XP SP2 - could be done but not sure it is worth the hassle.



#91 misty

misty

    Silver Member

  • Developer
  • 781 posts
  •  
    United Kingdom

Posted A week ago

Although Wonko might be the last person on our planet using WinXP, I have enabled support for XP SP2 (and up) :)

Although times may have changed, I seem to recall the forum's resident grumpy old b@st@rd avoiding XP with any service packs - something to do with WinSxS :whistling:

I could be wrong though, as I'm getting old (and grumpy) myself, and my memory is not what it was.

:cheers:

Misty

#92 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted A week ago

@erwan.l

It seems to run.

Still when opening the default dir is C: 

This is STRONGLY NOT advised, if you want to default it to the folder where makeiso is, considering it a sort of "relative root", then fine, but having the "real" (usually main/system) volume root  :w00t: :ph34r:

 

@Misty

Yes, no, no.

You are getting old.

You still are anyway a young padawan when it comes to grumpyness and bastardness.

 

:duff:

Wonko



#93 ady

ady

    Frequent Member

  • Advanced user
  • 154 posts

Posted A week ago

I tested MakeIso 1.0.0.9 with ISO9660 (only) and with several isolinux.bin versions (and no UEFI boot image).

A_ In MakeIso 1.0.0.9, the default setting is to _not_ patch the boot info table. With this default setting, the resulting ISO image booting by means of isolinux.bin (4.00-6.04-pre1) will fail. Considering our recent discussions and tests (about isolinux.bin, its checksum and the boot info table), this is not a surprise.

B_ Same tests as case "A" but manually activating the "patch boot info table" setting in MakeIso, the same versions of isolinux.bin will successfully boot.

C_ Testing a new isolinux.bin (+ ldlinux.c32) that was (were) built with a proposed patch for '.lzo/prepcode.c' (in  the source code of Syslinux) will successfully boot (when using the simplified settings I described above). Whether the boot info table setting in MakeIso 1.0.0.9 was active, or inactive (its default), this new (yet unofficial) isolinux.bin (+ldlinux.c32) successfully boots.

I would suggest that the "patch boot info table" setting should default to being "active" in future versions of MakeIso, at least when the bootloader for BIOS is recognized as some version of ISOLINUX. Whether this setting should be active by default independently of the kind of bootloader being chosen by the user (IOW, always active by default), I do not know.

I have not tested MakeIso with UEFI bootloaders, so I don't know whether the "patch boot info table" should or should not be active by default for UEFI.



#94 Blackcrack

Blackcrack

    Frequent Member

  • Advanced user
  • 329 posts
  •  
    Germany

Posted A week ago

@Blackcrack
 
Thanks for the idea.
 
Do you mean generating a menu (menu.lst? isolinux.cfg) for a bootloader? isolinux? grub4dos?
 
I am not too good with scripting but I'll be more than happy to include your batch/script in makeiso zip file (with proper credits, etc).
 
Regards,
Erwan
 
EDIT : posted edited with the right nickname...


exactly to have a possible for let automatic generate some files who it is fully file-name related and
therewith the possible for let create automatic/dynamical a file-listing menu with a possible to reedit
the description of the iso files with the possible of is/should and recreate entry and
if exist a filename123aesou.iso to overlay a description if the filename the same like into the folder.
and it is a new entry with filename only, it's possible to reedit the entry of themen.. and the good it is,
in the entry it is write the default file name what it is fresh in the iso-folder and therewith it's
more better possible to find,and more easy changeable the Menuentry, because before is generate the
entry from the filename the "Filename123aesou.iso" on it and is faster findable .

With it is more easy easy kick in at the ./bootiso the iso, like 'fedora 32Bit 27 from 2017-10-28.iso'
and 'fedora x86_64 27 from 2017-10-28.iso' in the ./bootiso folder and by next boot it is the name
with .iso (or without ".iso" extension) in the Menuentry generate by start of the Bootloader.

therewith it is possible on an usb-stick to create a well technical iso-boot
with different iso's in one boot-slip to have a menu where it is created with
the name of the iso's.Or the possible for reedit the Filedescription and therewith the overlay
and have a more detailed description like
[fedora x86_64 27 from 2017-10-28.iso] \n "fedora x86_64 27 from 2017-10-28.iso"
later manual edited
[fedora x86_64 27 from 2017-10-28.iso] \n "The fedora x86_64 Version 27 from 2017.10.28"

and in any case it is show and not confusingly a Description once
as file name(or the name of the file auto generate) or the
more enhanced Description edited from the "Administrator"/User of the Stick
who can add more information of the iso like
[fedora 27 x86_64 2017-10-28.iso]
"The fedora x86_64 Version 27 from 2017.10.28 with (\n autowarp) Libreoffice and Partitionsmanager"
or
[fedora 27 x86_64 liveiso 2017-10-28.iso]
"The fedora Liveiso x86_64 Version 27 from 2017.10.28 with (\n autowarp) Libreoffice and Partitionsmanager"
[fedora 27 x86_64 net 2017-10-28.iso]
"The fedora Networkinstall x86_64 Version 27 from 2017.10.28 (\n autowarp) short Start and install"

or be first start
[fedora 27 x86_64 net 2017-10-28.iso] // this name is use as comparative possibility, because no change
"fedora 27 x86_64 net 2017-10-28.iso" // this is shown in the bootmenu and generate by fist start

exist the "comparative possibility" no more in the ./bootiso in the folder by dir/B entrys
be automatic removed the fully [blabla.iso] \n "The fully name or description of the filename"

and add the new entry if a new 'isonameabcde12345 andnew.iso' iso exist in the folder.
(specially explained extra for wonko.. if you it not understand, don't ask.. and forget it*s* ;))

this """script""" in direction of php/batch mix could you implement in your programming language
i have only type it in this direction for understand what i did meant.
and maybe could make a plugin for grub2 or other to initial a
filenameread-compare-create-menu-ifentrynotexist-removeitif-notexist-generator with the possible to
add an md5-compare as option if exist an md5= entry
by start of the/a bootloader .. something in this direction. to have a possible
for easy put the iso in the isofolder ..


@wonko, i am not fully technical, but i know how i can convey erwan.l
(so an nonfulltechnical.. like me but he can programming) the knowing what i meant.
The right persons must it understand.. more not ;) *giggle*

best regards
Blacky :))

#95 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 6 days ago

@ady

No, that's fine, the UEFI loads the whole FAT image and looks for bootia32.efi or bootx64.efi no isolinux.bin or boot info table is used (or harmed) in the making.

I am not even sure that Syslinux.efi can be used on bootable CD/DVD's :unsure:

 

@blackcrack

No worry :), from time to time attempts at Vogon Poetry are just fine.

 

I thought yours were not intentional, but now that you confirmed explicitly that you write this way on purpose and (assertedly) knowing what you are doing, it is therewith OK.

 

I will gladly take may hat off :hi: to erwan.l and his linguistic capabilities when (if :dubbio:) he will have acknowledged a wholesome (or even partial but substantial enough) comprehension of your posts.

 

:duff:

Wonko



#96 ady

ady

    Frequent Member

  • Advanced user
  • 154 posts

Posted 6 days ago

@ady
No, that's fine, the UEFI loads the whole FAT image and looks for bootia32.efi or bootx64.efi no isolinux.bin or boot info table is used (or harmed) in the making.

Yes, that's correct (at least in theory). My focus in this topic is, still, Erwan's MakeIso, and since I haven't tested its UEFI behavior yet, I was only stating this as part of my report to him (so this time my test could be reproduced by others, and my report/results and suggestion could be confirmed/reproduced, or not).
 

I am not even sure that Syslinux.efi can be used on bootable CD/DVD's


It could, by cheating a little "bit", which is where Erwan's MakeIso can be of help. I might try syslinux.efi and report my results later.

#97 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted 6 days ago

I tested MakeIso 1.0.0.9 with ISO9660 (only) and with several isolinux.bin versions (and no UEFI boot image).

A_ In MakeIso 1.0.0.9, the default setting is to _not_ patch the boot info table. With this default setting, the resulting ISO image booting by means of isolinux.bin (4.00-6.04-pre1) will fail. Considering our recent discussions and tests (about isolinux.bin, its checksum and the boot info table), this is not a surprise.

B_ Same tests as case "A" but manually activating the "patch boot info table" setting in MakeIso, the same versions of isolinux.bin will successfully boot.

C_ Testing a new isolinux.bin (+ ldlinux.c32) that was (were) built with a proposed patch for '.lzo/prepcode.c' (in  the source code of Syslinux) will successfully boot (when using the simplified settings I described above). Whether the boot info table setting in MakeIso 1.0.0.9 was active, or inactive (its default), this new (yet unofficial) isolinux.bin (+ldlinux.c32) successfully boots.

I would suggest that the "patch boot info table" setting should default to being "active" in future versions of MakeIso, at least when the bootloader for BIOS is recognized as some version of ISOLINUX. Whether this setting should be active by default independently of the kind of bootloader being chosen by the user (IOW, always active by default), I do not know.

I have not tested MakeIso with UEFI bootloaders, so I don't know whether the "patch boot info table" should or should not be active by default for UEFI.

 

Excellent reporting, thanks.

Case A : all expected.

Case B : all expected.

Case C : very good news, any URL we can look at to follow the discussion with the Syslinux team?

 

About the "patch boot table" option : 

-i would leave it optional as not all boot loaders support it (like the MS one) thus I could add an autodetection for Isolinux.

-EFI is irrelevant (as explained by Wonko in this post)



#98 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted 6 days ago

It could, by cheating a little "bit", which is where Erwan's MakeIso can be of help. I might try syslinux.efi and report my results later.

 

I tried but failed so far.

If you have any more details, would be interested to revive my testing.

 

Edit :

-seems syslinux.efi may not support iso9660 FS

-seems using an HDD image may be a workaround but will still not be able to see your iso9660 FS



#99 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2106 posts
  • Location:Nantes - France
  •  
    France

Posted 6 days ago

@erwan.l

It seems to run.

Still when opening the default dir is C: 

This is STRONGLY NOT advised, if you want to default it to the folder where makeiso is, considering it a sort of "relative root", then fine, but having the "real" (usually main/system) volume root  :w00t: :ph34r:

 

Fair point.

Actually, based on a previous comment of yours, I had already made it so that when you browse for the source folder, you are in the makeiso current folder.

I have take your comment on board : the text field now points directly at the makeiso current folder.

Will be there in next release.



#100 IAmTheTrueMeaningOfCovfefe

IAmTheTrueMeaningOfCovfefe

    Silver Member

  • Advanced user
  • 589 posts
  • Location:In hiding
  • Interests:An investigation is underway to determine whether Trump has any ties to America.
  •  
    United States

Posted 6 days ago

@erwan.l: There are like a gazillion softwares out there that can create an ISO. So I really have to ask:

 

Why another? What makes your program unique/special? What does it do better than the rest?

 

I just don't see a need in flooding the software market with yet another whatever that does pretty much the same thing that others already do perfectly fine. Unless, of course, there is something better about yours.

 

Just asking.....






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users