Bug in mkisofs with Joliet FS - missing files?
rs...@my-deja.com
cdrecord. The OS is OS2 Warp 3.0 (fixpack 40).
The root dir has some sub-directories. If some of the directories have
similar names (like abc_fff, abc_ggg, abc_hhh, abc_iii etc), the
files inside these subdirectories will not make it to the CD-RW.
If I look at the CD-RW after burning, I can still see the directories
but these directories will be empty.
The filenames are less than 64 characters long.
I move all these directories to another root directory, like
root_dir/all_other_sub_directories
root_dir2/abc_fff, abc_ggg, abc_hhh, abc_iii
Then I burn these two root directories to the same CD-RW, there is no
problem. All the files are there.
This problem only happens to certain directory name, not all- say
if I use efg_ as the base of those directories, there will be no
problem.
Did anyone else encounter this problem?
--
Regards,
Roger Shum
Sent via Deja.com http://www.deja.com/
Before you buy.
Jerry McBride
No. But just trying to understand the syntax of declaring what directory you
want copied and where-to is enough to make a guy drink. I undestand that these
utilities (mkisofs and cdrecod) are being ported from the unix world, but man
have a heart for us OS/2 users... :')
For instance, to backup a directory tree of: d:\files\os2 I have to use this
on a mkisofs command line: files/=d:\files\os2. Why not rearrange the input
parser to accept the more logical and more used: d:\files\os2 and create both
the "files" and "os2" directory? If you did like I did and used: /=d:\files\os2
during a mkisofs session, you end up with all the files at \files\os2 at the
root level on the cdrom... that, my friend... sucks... :')
Also, I've noticed strangeness when copying complete drives to rom. Using the
"os/2 logical" syntax of: /=c:\ does not work over here, you have to specify:
/=c:/ to get it all on cdrom correctly... What the??? Unix anyone? :')
All that goofyness aside, I use cdrecord and mkisofs FAR, FAR more regularly
than RJS or UNITEcd... In fact, since the "32" release of cdrecord, I don't
bother with either of the commercial apps. No if I can ONLY get multisession
support to work 100%, I'd be a totally happy camper...
--
*******************************************************************************
* OS/2 ???? *
* YOU AREN'T ALONE! *
* http://rover.wiesbaden.netsurf.de/~meile/los2cl.html *
*******************************************************************************
gzi...@attglobal.net
>mcbr...@erols.com (Jerry McBride) writes:
>
>> No. But just trying to understand the syntax of declaring what directory you
>> want copied and where-to is enough to make a guy drink. I undestand that these
>> utilities (mkisofs and cdrecod) are being ported from the unix world, but man
>> have a heart for us OS/2 users... :')
>Well, maybe one of the frontends would make it easier for you? I'm a
>Unix person, so I don't have a problem using mkisofs and cdrecord.
>
>For the original poster, there have been bugs in mkisofs concerning
>directories, but usually when making multi-session discs. I don't know
>what the problem is, but if you can make a specific example that the
>author (or the guy who ported it to OS/2) can duplicate it, it'll
>probably get fixed.
>Anssi Saari - a...@sci.fi
Jerry, I still haven't found the time to test out a multi-session CD, and I
will get back to you on that, however I do second Anssi 's suggestion.
Use Chris's wonderful front end, for what you are trying to do! I have
found it a breeze, and I'm a newbie to CD burning myself.
I printed out all the doc's from the UNIX port, and have done subsequent
research. For example, contrary to popular myth, the CDFS.IFS, that IBM
released with Warp 3 FP35, <fill in Warp 4 eqivalent> already introduced
HPFS long filenames, (for their Java development CD's), so you don't need
Rockridge, (for UNIX), nor Joilet, (Win 95/whatever), unless you intend to
deliver a CD for those specific platforms.
I basically just burn data CD's, and for me, it's simply a matter of dragging
the template from Chris's GUI front end, onto the hard drive where I have
sufficient space, drag the files to that template, and burn it. Nothing could
be easier. In the case where you have funny symbols, ie '~', (astergule) in
your files, add the -a, for all files in the mkisofs parmeters box provided. That
was the only gotcha I had in burning data CD's.
So, it is worthwhile to print out the UNIX docs, to a certain extent, just in
case you need to 'fine-tune' something. Also, I'm a command-line person
too, and don't take readily to 'front-ends', but in this case, where I am
a newbie, his front end does a fine job, all on it's own. Certainly print the
UNIX docs, in case you want to do something specific, but as this is a port,
I've found most of it to be non-relevant, unless I'm publishing something
for a specific non-OS/2 platform.
Chris's front end can be found at:
http://www.geocities.com/SiliconValley/Sector/5785/cdrecord/cdrecordmain.htm
and I've found his package to be very complete. The readcd.exe utility is
very useful if you've purchased a game CD, and want to beat your spouse
at pinball. <grin>.
Gail Zimmerman
gzi...@ibm.net