mkisofs

mkisofs

Post by johnsut » Fri, 21 Jul 2006 10:42:00



I am trying to make a bootable CD image, but mkisofs is always unable to find
one of the files or directories I have specified, even though it sometimes
writes something to the specified output file.

I don't understand the instruction "The pathname must be relative to the source
path specified to mkisofs." I see no switch or instruction for specifying a
source (of what?) path.

Mkisofs.exe is not on the same partition as my image tree.

What have I overlooked?
 
 
 

mkisofs

Post by Steven Lev » Fri, 21 Jul 2006 13:32:44

In <c1.2c.31kf6c$ XXXX@XXXXX.COM >, on 07/20/2006
at 01:42 AM, XXXX@XXXXX.COM said:


You have a leading slash on some path or file name where mkisofs allows
only a relative path or file name. New users typically make this mistake
for the -b option.


You neglected to post the command line that is giving you trouble.

Regards,

Steven

--
--------------------------------------------------------------------------------------------
Steven Levine < XXXX@XXXXX.COM > MR2/ICE 2.67 #10183
Warp/eCS/DIY/14.103a_W4 www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
--------------------------------------------------------------------------------------------

 
 
 

mkisofs

Post by James J. W » Fri, 21 Jul 2006 15:39:43


mkisofs makes an image of an iso file system that can be written to a cd or dvd.
Now a cd or a dvd is treated as a drive and as such it has an unnamed root
directory which in turn can contain subdirectories a any depth.

So: create an any handy hard drive, say d, with enough space a directory called
(say) root. In that directory, place any files you want to go in the root of
the cd or dvd. Also in that directory, create any top level directories you
want to appear on the disk. Proceed to copy files to these directories and
create subdirectories and copy files until you have the complete contents of
your disk all *** off of the directory root.

Now, suppose you have put the boot floppy image in d:\root\bootstuff\image

Then your mkisofs2 command should look something like this:

mksiofs2 -V volid -b bootstuff\image ... -o x:\image.iso d:\root


d:\root is the source path, the dots represent any other options you need and
x:\image.iso will contain the iso image that you burn using cdrecord2.
 
 
 

mkisofs

Post by johnsut » Sat, 22 Jul 2006 17:24:21

In <44bf076c$2$fgrir53$ XXXX@XXXXX.COM >, Steven Levine < XXXX@XXXXX.COM > writes:

Here it is:-
g: is the virtual floppy
e: is the main partition
h: is for data files
h:\swc\iso is the root for the cd image
h:\swc\iso\bootimgs holds the boot diskette images

[H:\swc\iso]e:\accs\dskf\savedskf.exe g: h:\swc\iso\bootimgs\disk_0.img /D /A

100 percent saved

Disk saved to file successfully

[H:\swc\iso]e:\apps\cdr\cdr2\mkisofs.exe -V OS2_BOOT -b bootimgs\disk_0.img -o e
:\temp\image.iso h:\swc\iso
e:\apps\cdr\cdr2\mkisofs.exe: Uh oh, I cant find the boot image 'bootimgs\disk_0
img' !

[H:\swc\iso]
 
 
 

mkisofs

Post by Alex Taylo » Sat, 22 Jul 2006 23:21:04


^
Try changing this to a forward slash.

--
Alex Taylor
http://www.yqcomputer.com/ ~alex

Remove hat to reply (reply-to address).
 
 
 

mkisofs

Post by Steven Lev » Sun, 23 Jul 2006 02:28:08

In <44c0e222$0$26095$ XXXX@XXXXX.COM >, on 07/21/2006
at 09:21 AM, Alex Taylor < XXXX@XXXXX.COM > said:


That will help. In addition, change all the backslashes that occur in the
options or included files to forward slashes. Mkisofs has no specific
logic to support DOS style path separators.

Regards,

Steven

--
--------------------------------------------------------------------------------------------
Steven Levine < XXXX@XXXXX.COM > MR2/ICE 2.67 #10183
Warp/eCS/DIY/14.103a_W4 www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
--------------------------------------------------------------------------------------------
 
 
 

mkisofs

Post by johnsut » Sun, 23 Jul 2006 08:02:45

In <44c10ea8$1$fgrir53$ XXXX@XXXXX.COM >, Steven Levine < XXXX@XXXXX.COM > writes:

OS/2 Ctrl+Esc = Window List Type HELP = help

[H:\swc\iso\bootimgs]dir

The volume label in drive H is JFS.
The Volume Serial Number is D55C:15BF.
Directory of H:\swc\iso\bootimgs

22/07/06 9:03 <DIR> 477 .
20/07/06 9:57 <DIR> 388 ..
21/07/06 19:13 2949120 0 DISK_0.IMG
20/07/06 9:56 1884160 0 DISK_1.IMG
4 file(s) 4833280 bytes used
2987732 K bytes free

[H:\swc\iso\bootimgs]e:\apps\cdr\cdr2\mkisofs.exe -V BOOT_OS2 -b DISK_0.IMG -c B
OOT_CAT.BIN -o e:/temp/cd.iso h:/swc/iso
e:\apps\cdr\cdr2\mkisofs.exe: Uh oh, I cant find the boot image 'DISK_0.IMG' !

[H:\swc\iso\bootimgs]


Mkisofs is saying that it can't find a file in the current directory, yet it always manages to write a blank output file in the specified directory.

When viewing disk_0.img in an editor, I see the text messages and filenames that I expect to be there.
 
 
 

mkisofs

Post by Steven Lev » Sun, 23 Jul 2006 10:45:44

In <c1.2c.31lpgc$ XXXX@XXXXX.COM >, on 07/21/2006
at 11:02 PM, XXXX@XXXXX.COM said:





It is complaining about the other current directory. :-)

You told mkisofs to use the content of h:/swc/iso to build the iso. This
is the current directory for the purposes of forming the iso image.
DISK_0.IMG needs to be in a location relative to this current directory.
Copy the .IMG files to h:/swc/iso and the message will go away.

The reason it works this way is because the -b option only specifies the
name of the boot image file. The -b option does not copy anything to the
iso image so it's your job to make sure the named file exists.

Regards,

Steven

--
--------------------------------------------------------------------------------------------
Steven Levine < XXXX@XXXXX.COM > MR2/ICE 2.67 #10183
Warp/eCS/DIY/14.103a_W4 www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
--------------------------------------------------------------------------------------------
 
 
 

mkisofs

Post by johnsut » Tue, 25 Jul 2006 12:29:27

In <44c18348$2$fgrir53$ XXXX@XXXXX.COM >, Steven Levine < XXXX@XXXXX.COM > writes:

Yes, I failed to see that "current directory" is relative to the viewer, so we
can have simultaneous current directories.
 
 
 

mkisofs

Post by Steven Lev » Tue, 25 Jul 2006 15:20:47

In <c1.2c.31m1Gz$ XXXX@XXXXX.COM >, on 07/24/2006
at 03:29 AM, XXXX@XXXXX.COM said:


Yes this is true. Mkisofs has two current directories and is consistent
about which one you need to use. When specifying files to be copied to
the iso or the names of control files, the current directory is the
directory that mkisofs was started from. When specifying the names of
files within the iso image, the paths are relative to the root of the iso
image.

Multiple current directories happen all the time with disk volumes. Each
volume has a current directory. We just don't think about this all that
often.

Regards,

Steven

--
--------------------------------------------------------------------------------------------
Steven Levine < XXXX@XXXXX.COM > MR2/ICE 2.67 #10183
Warp/eCS/DIY/14.103a_W4 www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
--------------------------------------------------------------------------------------------