Mkisofs warning
#1
Posted 11 October 2008 - 10:52 AM
When I try to create the file.iso with mkisofs, mkisofs version 2.01 (i686-pc-cygwin)
These warning appears:
Scanning D: \ Grub/ i386/WINNTUPG/SRVINF
Using SYST000.WEB.SECURITY.SINGLES.DL; 1 for D: \ Grub/NT_1/SYSTEM.WEB.SECURITY.SI
NGLESIGNON.PERMISSIONS.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PARTIALTRUST.DLL)
what options should I use with mkisofs
to make them disappear?
Thank you
Regards
z900
#2
Posted 11 October 2008 - 12:21 PM
D:\>mkisofs -version
mkisofs 2.01 (i686-pc-cygwin)
mkisofs -R -b grldr -no-emul-boot -boot-load-size 4 -o Grub2.iso D:\Grub
Scanning D:\Grub/NT_1/WINNTUPG/SRVINF
Using SYST000.WEB.SECURITY.SINGLES.DL;1 for D:\Grub/NT_1/SYSTEM.WEB.SECURITY.SI
NGLESIGNON.PERMISSIONS.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PARTIALTRUST.DLL)
Writing: Initial Padblock Start Block 0
Done with: Initial Padblock Block(s) 16
Writing: Primary Volume Descriptor Start Block 16
Done with: Primary Volume Descriptor Block(s) 1
Writing: Eltorito Volume Descriptor Start Block 17
Size of boot image is 4 sectors -> No emulation
................................................................................
.....................................
D:\>mkisofs -R -b grldr -no-emul-boot -boot-load-size 4 -o Grub2.iso D:\Grub
Using SYSTE000.DLL;1 for D:\Grub/i386/SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSI
ONS.RESOURCES.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSIONS.DLL)
Using SYSTE001.DLL;1 for D:\Grub/i386/SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSI
ONS.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PARTIALTRUST.DLL)
Using KNR2E000.TXT;1 for D:\Grub/i386/KNR2EULA_RETAIL.TXT (KNR2EULA_OEM.TXT)
Using KNR2E001.TXT;1 for D:\Grub/i386/KNR2EULA_OEM.TXT (KNR2EULA_EVAL.TXT)
................................................................................
.....................................
D:\>mkisofs -R -b grldr -no-emul-boot -boot-load-seg 0x1000 -volid "Grub" -o Gru
b2.iso D:\Grub
Using SYSTE000.DLL;1 for D:\Grub/i386/SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSI
ONS.RESOURCES.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSIONS.DLL)
Using SYSTE001.DLL;1 for D:\Grub/i386/SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSI
ONS.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PARTIALTRUST.DLL)
Using KNR2E000.TXT;1 for D:\Grub/i386/KNR2EULA_RETAIL.TXT (KNR2EULA_OEM.TXT)
Using KNR2E001.TXT;1 for D:\Grub/i386/KNR2EULA_OEM.TXT (KNR2EULA_EVAL.TXT)
Size of boot image is 384 sectors -> No emulation
................................................................................
.....................................
D:\>mkisofs -R -b grldr -no-emul-boot -boot-load-size 4 -volid "gru" -o Grub2.is
o D:\Grub
Using SYSTE000.DLL;1 for D:\Grub/i386/SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSI
ONS.RESOURCES.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSIONS.DLL)
Using SYSTE001.DLL;1 for D:\Grub/i386/SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSI
ONS.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PARTIALTRUST.DLL)
Using KNR2E000.TXT;1 for D:\Grub/i386/KNR2EULA_RETAIL.TXT (KNR2EULA_OEM.TXT)
Using KNR2E001.TXT;1 for D:\Grub/i386/KNR2EULA_OEM.TXT (KNR2EULA_EVAL.TXT)
Size of boot image is 4 sectors -> No emulation
1.67% done, estimate finish Sat Oct 11 14:01:12 2008
Regards
z900
#3
Posted 11 October 2008 - 12:55 PM
mkisofs -v -iso-level 4 -l -D -d -J -joliet-long -R -volid "GRLDR" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-seg 0x1000 -allow-multidot -hide boot.catalog -o Grub2.iso D:\Grub
or this:
mkisofs -v -iso-level 4 -l -D -d -J -joliet-long -R -volid "GRLDR" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-size 4 -allow-multidot -hide boot.catalog -o Grub2.iso D:\Grub
As I already told you twice via PM, you have LONG filenames and MULTIDOT ones, thus you need (besides searching and reading mkisofs documentation/MAN page):
-iso-level 4 -J -joliet-long -allow-multidotor at least some of those.
jaclaz
#4
Posted 11 October 2008 - 01:25 PM
verification of the hardware configuration in progress: NTDETECT failed.
with the options that I sent during the installation appeared that some msg
file.inf of you were not found, and asked to press ESC to continue.
Regards
z900
#5
Posted 11 October 2008 - 01:51 PM
This is NOT understandable:
with the options that I sent during the installation appeared that some msg
file.inf of you were not found, and asked to press ESC to continue.
If you get an error message, if you want to get help you need to post:
1) a description of what the heck you are trying to do
2) the exact error message you get
3) ALL the exact steps you took before/what you did
Please RE-READ the Common Sense Advice" within Rules:
http://www.boot-land...?act=boardrules
and try helping us helping you.
In the meantime, you could get my standard reply #32:
http://www.boot-land...?showtopic=2587
jaclaz
#6
Posted 11 October 2008 - 02:12 PM
D:\>mkisofs -version
mkisofs 2.01 (i686-pc-cygwin)
mkisofs -R -b grldr -no-emul-boot -boot-load-size 4 -o Grub2.iso D:\Grub
Scanning D:\Grub/NT_1/WINNTUPG/SRVINF
Using SYST000.WEB.SECURITY.SINGLES.DL;1 for D:\Grub/NT_1/SYSTEM.WEB.SECURITY.SI
NGLESIGNON.PERMISSIONS.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PARTIALTRUST.DLL)
Writing: Initial Padblock Start Block 0
Done with: Initial Padblock Block(s) 16
Writing: Primary Volume Descriptor Start Block 16
Done with: Primary Volume Descriptor Block(s) 1
Writing: Eltorito Volume Descriptor Start Block 17
Size of boot image is 4 sectors -> No emulation
D:\>mkisofs -R -b grldr -no-emul-boot -boot-load-size 4 -o Grub2.iso D:\Grub
Using SYSTE000.DLL;1 for D:\Grub/i386/SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSI
ONS.RESOURCES.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSIONS.DLL)
Using SYSTE001.DLL;1 for D:\Grub/i386/SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSI
ONS.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PARTIALTRUST.DLL)
Using KNR2E000.TXT;1 for D:\Grub/i386/KNR2EULA_RETAIL.TXT (KNR2EULA_OEM.TXT)
Using KNR2E001.TXT;1 for D:\Grub/i386/KNR2EULA_OEM.TXT (KNR2EULA_EVAL.TXT)
appears message of warning, but the iso file is creating.
In the Vmware appears warning message that some inf file
is not found, but installation of Windows is accomplished.
with the mkisofs options that you have posted in
the forum not appear alerts.
not appears alert when creating iso file as before.
but with vmware appears at this error message:
verification of the hardware configuration in progress: NTDETECT failed.
Regards
z900
but with vmware appears at this error message:
#7
Posted 11 October 2008 - 04:08 PM
Try ALL of these, one by one:
It does not work, OK.mkisofs -v -iso-level 4 -l -D -d -J -joliet-long -R -volid "GRLDR" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-size 4 -allow-multidot -hide boot.catalog -o Grub2.iso D:\Grub
ISOLEVEL 4:
mkisofs -v -iso-level 4 -l -D -d -J -joliet-long -volid "GRLDR" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-size 4 -allow-multidot -hide boot.catalog -o Grub2.iso D:\Grub
mkisofs -v -iso-level 4 -l -D -d -J -R -volid "GRLDR" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-size 4 -allow-multidot -hide boot.catalog -o Grub2.iso D:\Grub
mkisofs -v -iso-level 4 -l -D -d -R -volid "GRLDR" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-size 4 -allow-multidot -hide boot.catalog -o Grub2.iso D:\Grub
mkisofs -v -iso-level 4 -l -D -d -R -volid "GRLDR" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-size 4 -hide boot.catalog -o Grub2.iso D:\Grub
ISOLEVEL3:
mkisofs -v -iso-level 3 -l -D -d -J -joliet-long -R -volid "GRLDR" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-size 4 -allow-multidot -hide boot.catalog -o Grub2.iso D:\Grub
mkisofs -v -iso-level 3 -l -D -d -J -joliet-long -volid "GRLDR" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-size 4 -allow-multidot -hide boot.catalog -o Grub2.iso D:\Grub
mkisofs -v -iso-level 3 -l -D -d -J -R -volid "GRLDR" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-size 4 -allow-multidot -hide boot.catalog -o Grub2.iso D:\Grub
mkisofs -v -iso-level 3 -l -D -d -R -volid "GRLDR" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-size 4 -allow-multidot -hide boot.catalog -o Grub2.iso D:\Grub
mkisofs -v -iso-level 3 -l -D -d -R -volid "GRLDR" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-size 4 -hide boot.catalog -o Grub2.iso D:\Grub
You can omit these, they are commands to set correct labels to the CD/DVD:
-volid "GRLDR" -A GRLDR/MKISOFS -sysid "Win32"
If ANY of the above don't work, try some other permutations, like
ormkisofs -relaxed-filenames -d -D -J -b grldr -no-emul-boot -boot-load-size 4 -o Grub2.iso D:\Grub
ormkisofs.exe -iso-level 4 -force-uppercase -R grldr -no-emul-boot -boot-load-size 4 -o Grub2.iso D:\Grub
mkisofs -relaxed-filenames -iso-level 4 -force-uppercase -R -b grldr -no-emul-boot -boot-load-size 4 -o Grub2.iso D:\Grub
Otherwise, you need to find out what the heck are the files like:
"/NT_1/SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSIONS.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PARTIALTRUST.DLL)"
"/i386/SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSIONS.RESOURCES.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSIONS.DLL)
"/i386/SYSTEM.WEB.SECURITY.SINGLESIGNON.PERMISSIONS.DLL (SYSTEM.WEB.SECURITY.SINGLESIGNON.PARTIALTRUST.DLL)"
"/i386/KNR2EULA_RETAIL.TXT (KNR2EULA_OEM.TXT)"
"/i386/KNR2EULA_OEM.TXT (KNR2EULA_EVAL.TXT)"
needed for, and see if there is a way to rename it to something "decent" or to remove them alltogether.
The above files have SEVERAL "non-basic" characteristics:
1) they are not in 8.3 format
2) they contain more than one dot
3) they contain a space
4) they contain brackets/parentheses
5) they are longer than 16 characters
6) some of them are longer than 32 characters
God only (and maybe cdob ) knows which of the different possible combination of switches may accept all of those particularities, each appears to be infringing one or more "standards";
Joliet -> -J
Joliet with Long filenames -> -joliet-long
ISO9660:1999 -> -iso-level 4
RockRidge -> -R
thus you may need some "extra" like:
but this may conflict with the other switches....it's a hit and miss game, at least AFAIK.-relaxed-filenames
-allow-multidot
WHICH .inf file(s)?In the Vmware appears warning message that some inf file
is not found, but installation of Windows is accomplished.
Post the EXACT error message.
How big is the .iso?
Forget about the multiversion, just find the commands needed to build succesfully and with NO errors of ANY kind during installation the "standard" \I386.
Only once you have succeeded in this, re-add the other(s) version(s).
If you use similar versions, using additionally to the command line that you will find to be the right one, add this:
as it may save you lots of space (smaller size of the .iso).-duplicates-once
jaclaz
#8
Posted 11 October 2008 - 05:43 PM
#9
Posted 11 October 2008 - 06:22 PM
the file.inf are:
cyclad-z.inf
cyclom-y.inf
notes.txt
680x64_base_1.2.7.0_logo.zip /*is driver for card raid pci ide Silicon ImageSil680 for winx64*/
bio-00680a-x10_3308.zip /*bios for card scsi raid pci ide Silicon Image Sil680 */
installiicfg.exe /*program for update Silicon Image Sil680*/
siflashtool.zip
updflash_v336.zip
_innodesc.xml /* file creating the maxdriver of Innovative-sol.com*/
oem_no_drivermax.inf /*file inf create of Maxdriver of Innovative-sol.com*/
other same file with the same name but in folders
several, created bymaxdriver Innovative-sol.com
this Windows is update with nLitewith Sp2+ driver + driver folder
creating othe maxdriver of Innovative-sol.com.
Thanks
Regards
z900
#10
Posted 11 October 2008 - 06:56 PM
Actually there is not a single answer, there are different possiblities.
Which data do you like to add to DVD?
There is a classic approach: file system relaxed ISO9660 Level 1 and file system Joliet
mkisofs -relaxed-filenames -d -D -N -joliet-long -b grldr -no-emul-boot -boot-load-size 4 -hide boot.catalog -o Grub2.iso D:\GrubThere is a warning about file name length still.
However most likely you may ignore this now.
Another approach, if you need long names: use file system ISO9660:1999
There are lower case allowed at ISO9660:1999.
Contrary XP setup require some uppercased files, e.g. \I386\NTDETECT.COM. Hence the ntdetect failed.
Uppercase file names at hard disk first: filecase.exe /u /h /d /s D:\Grub
There is filecase.exe http://stevemiller.net/apps/
mkisofs -iso-level 4 -D -b GRLDR -no-emul-boot -boot-load-size 4 -hide boot.catalog -o Grub2.iso D:\GrubThere is another warning about file name length. However that's because adding long names.
This refers to old applications like mscdex.exe from DOS. Ingnore this warning.
And if you like to add some Linux parts: add file extension RockRige
mkisofs -iso-level 4 -D -r -b GRLDR -no-emul-boot -boot-load-size 4 -hide boot.catalog -o Grub2.iso D:\Grub
Missing inf files may have different reasons.
This may cause the missing files.this Windows is update with nLitewith Sp2+ driver + driver folder
creating othe maxdriver of Innovative-sol.com.
First try plain windows files. Do you use 2003 source files?
Create a multi boot environment. Does this boot?
Change one part, e.g. add drivers and test again.
Maxdriver won't add a Silicon ImageSil680 for textmode installation.
Add drivers from manufacturer, you need a file txtsetup.oem for textmode part.
Start again at nlite, integrate drivers only. Don't delete files.
@jaclaz
There is neither -duplicates-once nor -force-uppercase at mkisofs 2.01 (i686-pc-cygwin)
#11
Posted 11 October 2008 - 07:26 PM
Regards
z900
#12
Posted 11 October 2008 - 09:26 PM
No, you don't have to change version. You may use another version.I have to change the version of mkisofs?
In addion to last message:
Grldr search file menu.lst, not MENU.LST at ISO9660.
Use lower case name menu.lst.
#13
Posted 11 October 2008 - 09:52 PM
No, you don't have to change version. You may use another version.
what other version?
In addion to last message:
Grldr search file menu.lst, not MENU.LST at ISO9660.
Use lower case name menu.lst.
D:\Grub\menu.lst , is lower case name
Regards
z900
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users