Re: Creating a CD with Long Filenames

From: Joerg Schilling (js_at_cs.tu-berlin.de)
Date: 08/22/03


Date: 22 Aug 2003 07:46:20 GMT

In article <1joakv81qctfrptdli850sqgqunegic0bq@4ax.com>,
P12 <nomail@all.com> wrote:
>On 21 Aug 2003 14:10:37 GMT, js@cs.tu-berlin.de (Joerg Schilling)
>wrote:
>
>>A quote from a stone age version!
>>
>>Why don't you eread my posying and fetch a recent version?
>
>O.K. I downloaded and compiled 2.01a18 which is exactly the same man
>page as in 2.00.3. The quotes I posted where from the man page link

You should start to learn how to do solid work....

diff /tmp/cdrtools-2.00.3/mkisofs/mkisofs.8 cdrtools-2.01/mkisofs/mkisofs.8 |count
   lines words chars linelen
     143 1008 5417 86 stdin

diff /tmp/cdrtools-2.00.3/mkisofs/mkisofs.8 cdrtools-2.01/mkisofs/mkisofs.8 |count
< .\" @(#)mkisofs.8 1.89 02/12/24 joerg

---
> .\" @(#)mkisofs.8     1.97 03/07/11 joerg
18c18
< .TH MKISOFS 8 "24 Dec 2002" "Version 2.0"
---
> .TH MKISOFS 8 "14 Feb 2003" "Version 2.01"
442a443,444
> Note that the sorting only works if the DVD-Video filenames include upper case
> characters only.
568,575d569
< .B \-l
< Allow full 31 character filenames.  Normally the ISO9660 filename will be in 
an
< 8.3 format which is compatible with MS-DOS, even though the ISO9660 standard
< allows filenames of up to 31 characters.  If you use this option, the disc may
< be difficult to use on a MS-DOS system, but this comes in handy on some other
< systems (such as the Amiga).
< Use with caution.
< .TP
598c592
< Set the iso9660 conformance level. Valid numbers are 1..3.
---
> Set the iso9660 conformance level. Valid numbers are 1..3 and 4.
605c599
< With level 3, no restrictions apply.
---
> With level 3, no restrictions (other than ISO-9660:1988) do apply.
607c601
< With all iso9660 levels all filenames are restricted to upper
---
> With all iso9660 levels from 1..3, all filenames are restricted to upper
610a605,627
....
>of the web page you pointed me too.  It appears to be the same one as
>in these downloads.   I  thought the 2.00.3 was the logical choice
>since you say it is the most recent "stable" version.   
If you have more than one version available you need to learn how
to distinct between the different versions.
It does not make sense to post confused things that are a result
of the fact that you don't even know which version you did use for a test.
>These version don't appear to work any different than the 1.11 I have
>been using for several years now.  I ran the exe with a -help and did
>not find any additional options which might.   I actually spent the
>afternoon trying to resolve this.  But I guess I give up.   I  must be
>too stupid to figure it out.  
>From the way you post, it is highly probable that you always tested/used 1.11.
2.01a18 is light years away from 1.11
-- 
EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
      js@cs.tu-berlin.de		(uni)  If you don't have iso-8859-1
      schilling@fokus.fraunhofer.de	(work) chars I am J"org Schilling
URL:  http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily


Relevant Pages

  • Re: Why cant file name end in a period?
    ... You can have filenames in XP with no extension also. ... File names in Windows XP can be up to 255 characters and can contain spaces, ...
    (microsoft.public.windowsxp.basics)
  • Re: spaces in filenames ?
    ... an assumption about the characters allowed in a filename. ... filenames don't contain newline characters (but beware that once ... IFS=" ...
    (comp.unix.questions)
  • Re: Mac file NAMING that doesnt work on PCs
    ... Mac documents folder to that server once and was rejected because my ... several characters which have special meanings on Windows and therefore ... Colon separates the drive letter from the rest of the pathname. ... Quotes are used to delimit filenames containing spaces. ...
    (comp.sys.mac.system)
  • Re: FTPFindFirstFile unicode
    ... window; the hex for the text in the lower window appears below that window. ... be encoded using 520 characters in UTF-8, and this might be where the problem is. ... It works fine for filenames that have english ...
    (microsoft.public.vc.mfc)
  • Re: FTPFindFirstFile unicode
    ... you should see "readable" characters for the UTF-8 ... window; the hex for the text in the lower window appears below that window. ... It works fine for filenames that have english ...
    (microsoft.public.vc.mfc)