i've been using magiciso and ultraiso to make ISO's for a while now and been getting the weirdest errors... sometimes when one OS works, the other fails... when i compile again, the failed one works but some other OS fails... i'm sure now that magiciso and ultraiso are the root of all my problems...
heres the list of OS in one dvd i've made ready...
1) Win 98 SE
2) Win ME
3) Win 2000
4) Win XP Pro SP2
5) win XP Pro SP2 PE
6) Win XP Pro SP3 lite
7) Windows Server 2003
8) Dammn Small Linux 4.4.1
9) Gparted
0) Knoppix
A) BackTrack 2 Final
could someone plot out the required/necessary MKISOFS commands to make a 100% working ISO plz...
i've never used mkisofs and i'm afraid that i might fu@k up the whole ISO if i do for the first time and i've already put a lot of work into compiling these OS's...
could anybody assist me here plz... my boot loader is in boot\loader.bin
Full Version: MKISOFS syntax needed
It's not so easy. 
The most "controversial" or "conflicting" settings are "isolevel 3" vs. "isolevel 4":
http://www.911cd.net/forums//index.php?showtopic=18088
and joliet extensions vs. Rock Ridge ones:
http://www.911cd.net/forums//index.php?showtopic=10950
You may also want to use The_GUI initially:
http://www.911cd.net/forums//index.php?showtopic=16997
Moreover when doing a DVD, it is possible that some needed files are written to the disc "beyond reach" of the bootloader (either the CD one or of the specific OS loader like setupldr.bin)
http://www.911cd.net/forums//index.php?showtopic=20248
Base start from here:
http://www.msfn.org/board/Super-Disc-Multi...-Us-t94398.html
jaclaz
The most "controversial" or "conflicting" settings are "isolevel 3" vs. "isolevel 4":
http://www.911cd.net/forums//index.php?showtopic=18088
and joliet extensions vs. Rock Ridge ones:
http://www.911cd.net/forums//index.php?showtopic=10950
You may also want to use The_GUI initially:
http://www.911cd.net/forums//index.php?showtopic=16997
Moreover when doing a DVD, it is possible that some needed files are written to the disc "beyond reach" of the bootloader (either the CD one or of the specific OS loader like setupldr.bin)
http://www.911cd.net/forums//index.php?showtopic=20248
Base start from here:
http://www.msfn.org/board/Super-Disc-Multi...-Us-t94398.html
jaclaz
oh man...
i gotta read all those... i get bored just watching it... anyways, i'll start later today and in the mean time if anyone here has a ready made code to include iso and rock ridges and other things then plz post a code...
i gotta read all those... i get bored just watching it... anyways, i'll start later today and in the mean time if anyone here has a ready made code to include iso and rock ridges and other things then plz post a code...
hey,
i've generated the following code via gui...
it gives me these following warnings...
i can't make out which ones to ignore and which ones to take seriously... can some one explain me here...
and could someone PM me the latest version of mkisofs.exe cause i read somewhere that the latest version may solve removing some warnings...
i've generated the following code via gui...
QUOTE
F:\The_GUI_v2>"F:\The_GUI_v2\mkisofs.exe" -joliet-long -max-iso9660-filenames -r -iso-level 4 -N -d -boot-info-table -boot-load-size 4 -o "F:/AIO-DVD" -b "BOOT/loader.bin" -no-emul-boot -p "AIODVD" "F:/AIO-DVD/"
it gives me these following warnings...
QUOTE
Warning: creating filesystem that does not conform to ISO-9660.
Warning: Creating ISO-9660:1999 (version 2) filesystem.
Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.
Warning: Creating ISO-9660:1999 (version 2) filesystem.
Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.
i can't make out which ones to ignore and which ones to take seriously... can some one explain me here...
and could someone PM me the latest version of mkisofs.exe cause i read somewhere that the latest version may solve removing some warnings...
Latest version is here:
Mingw32:
http://fy.chalmers.se/~appro/linux/DVD+RW/tools/win32/
Cygwin:
http://www.student.tugraz.at/thomas.plank/
The Cygwin version should be better/more up to date.
http://www.911cd.net/forums//index.php?showtopic=20988
You can ignore all warnings, but the Windows 98 won't work if you use MSCDEX to access the DVD, you need to use SHSUCDX:
http://www.geocities.com/jadoxa/shsucdx/index.html
(MSCDEX can read isolevel 3 but NOT isolevel 4 - read iso9660:2):
the -max-iso9660-filenames should not be needed
jaclaz
Mingw32:
http://fy.chalmers.se/~appro/linux/DVD+RW/tools/win32/
Cygwin:
http://www.student.tugraz.at/thomas.plank/
The Cygwin version should be better/more up to date.
http://www.911cd.net/forums//index.php?showtopic=20988
You can ignore all warnings, but the Windows 98 won't work if you use MSCDEX to access the DVD, you need to use SHSUCDX:
http://www.geocities.com/jadoxa/shsucdx/index.html
(MSCDEX can read isolevel 3 but NOT isolevel 4 - read iso9660:2):
QUOTE
With all iso9660 levels from 1..3, all filenames are restricted
to upper case letters, numbers and the underscore (_). The maxi-
mum filename length is restricted to 31 characters, the direc-
tory nesting level is restricted to 8 and the maximum path
length is limited to 255 characters.
Level 4 officially does not exists but mkisofs maps it to
ISO-9660:1999 which is ISO-9660 version 2.
With level 4, an enhanced volume descriptor with version number
and file structure version number set to 2 is emitted. There
may be more than 8 levels of directory nesting, there is no need
for a file to contain a dot and the dot has no more special
meaning, file names do not have version numbers, the maximum
length for files and directory is raised to 207. If Rock Ridge
is used, the maximum ISO-9660 name length is reduced to 197.
to upper case letters, numbers and the underscore (_). The maxi-
mum filename length is restricted to 31 characters, the direc-
tory nesting level is restricted to 8 and the maximum path
length is limited to 255 characters.
Level 4 officially does not exists but mkisofs maps it to
ISO-9660:1999 which is ISO-9660 version 2.
With level 4, an enhanced volume descriptor with version number
and file structure version number set to 2 is emitted. There
may be more than 8 levels of directory nesting, there is no need
for a file to contain a dot and the dot has no more special
meaning, file names do not have version numbers, the maximum
length for files and directory is raised to 207. If Rock Ridge
is used, the maximum ISO-9660 name length is reduced to 197.
the -max-iso9660-filenames should not be needed
jaclaz
hey thanks jo, i'll check it out...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.