File names ending with "."

QNX Newsgroups (Archives) qdn.public.qnx4
1

A CD I create has files with names that do not have extensions (i.e.
hst). When I view this CD under QNX 4.25 the files have a period at the
end (i.e. hst.). If I view the CD under windows or OS/2 the trailing
period is not there. All other files are ok.

The CD is created as Joliet format since when I use Iso9660 format all
the files get converted to uppercase. (I need them to be lower case
file names.) I don’t know if this is supposed to work that way or not.
I was surprised that a Joliet format CD was readable by Iso9660fsys.

Does anyone know if this is a problem on the QNX side or my CD burning
software?

What other CD burning software do people use?

I’m using Easy CD Creator 3.5c, QNX 4.25 and Iso9660fsys 4.23D.

  • KenR
2

I see in the Patch D readme that Joliet support was just added. Could the
new support be adding the trailing period?

  • KenR

rectech wrote:

A CD I create has files with names that do not have extensions (i.e.
hst). When I view this CD under QNX 4.25 the files have a period at the
end (i.e. hst.). If I view the CD under windows or OS/2 the trailing
period is not there. All other files are ok.

The CD is created as Joliet format since when I use Iso9660 format all
the files get converted to uppercase. (I need them to be lower case
file names.) I don’t know if this is supposed to work that way or not.
I was surprised that a Joliet format CD was readable by Iso9660fsys.

Does anyone know if this is a problem on the QNX side or my CD burning
software?

What other CD burning software do people use?

I’m using Easy CD Creator 3.5c, QNX 4.25 and Iso9660fsys 4.23D.

  • KenR
3

We distrubute our software on CD and from QNX4.25D there is
no problem with ISO9660 format: no dots on end of extension-less
filenames and even others session than primary one operates.
In previous version of QNX there were dots and only primary
session was operational.

If you have earlier QNX than 4.25D, it is enough to take /bin/Iso9660fsys
from QNX4.25, it works well even under QNX4.24 and may be also 4.23

Andy

4

Well this is happening on a 4.25 Patch D system. Please check your
Is09660fsys file for me.

I have a Iso9660fsys 4.23D Mar 20, 2000 installed from the Patch D CD.

What format for the CD are you using? Joliet or Is09660 and what burning s/w
are you using?

Thanks,

  • Ken R

Andrej Lucny wrote:

We distrubute our software on CD and from QNX4.25D there is
no problem with ISO9660 format: no dots on end of extension-less
filenames and even others session than primary one operates.
In previous version of QNX there were dots and only primary
session was operational.

If you have earlier QNX than 4.25D, it is enough to take /bin/Iso9660fsys
from QNX4.25, it works well even under QNX4.24 and may be also 4.23

Andy

5

rectech <rectech@iname.com> wrote:

Well this is happening on a 4.25 Patch D system. Please check your
Is09660fsys file for me.

I have a Iso9660fsys 4.23D Mar 20, 2000 installed from the Patch D CD.

What format for the CD are you using? Joliet or Is09660 and what burning s/w
are you using?

//14/bin/Iso9660fsys Iso9660fsys 4.23D Mar 20 2000

-rwxrwxr-x 1 root root 31006 Mar 20 2000 /bin/Iso9660fsys

format Iso9660

Thanks,

  • Ken R

Andrej Lucny wrote:

We distrubute our software on CD and from QNX4.25D there is
no problem with ISO9660 format: no dots on end of extension-less
filenames and even others session than primary one operates.
In previous version of QNX there were dots and only primary
session was operational.

If you have earlier QNX than 4.25D, it is enough to take /bin/Iso9660fsys
from QNX4.25, it works well even under QNX4.24 and may be also 4.23

Andy

6

What software are you using to create the CD? The problem I have might be because
I’m using Joliet format. When I use Iso I get all uppercase file names - my
software doesn’t give me any choice in this area. I’ll look closer…

  • KenR

Andrej Lucny wrote:

rectech <> rectech@iname.com> > wrote:
Well this is happening on a 4.25 Patch D system. Please check your
Is09660fsys file for me.

I have a Iso9660fsys 4.23D Mar 20, 2000 installed from the Patch D CD.

What format for the CD are you using? Joliet or Is09660 and what burning s/w
are you using?

//14/bin/Iso9660fsys Iso9660fsys 4.23D Mar 20 2000

-rwxrwxr-x 1 root root 31006 Mar 20 2000 /bin/Iso9660fsys

format Iso9660

Thanks,

  • Ken R

Andrej Lucny wrote:

We distrubute our software on CD and from QNX4.25D there is
no problem with ISO9660 format: no dots on end of extension-less
filenames and even others session than primary one operates.
In previous version of QNX there were dots and only primary
session was operational.

If you have earlier QNX than 4.25D, it is enough to take /bin/Iso9660fsys
from QNX4.25, it works well even under QNX4.24 and may be also 4.23

Andy

7

Follow-up:

Are you using lowercase file names? (I need to.)

I found out the ISO9660 standard is for all uppercase file names so my burning
software is just enforcing that. I wonder if QNX (Iso9660fsys) really cares? I’m
looking for other CD burning software like mkisofs - again what s/w are you using?

Thanks,

  • KenR

rectech wrote:

What software are you using to create the CD? The problem I have might be because
I’m using Joliet format. When I use Iso I get all uppercase file names - my
software doesn’t give me any choice in this area. I’ll look closer…

  • KenR

Andrej Lucny wrote:

rectech <> rectech@iname.com> > wrote:
Well this is happening on a 4.25 Patch D system. Please check your
Is09660fsys file for me.

I have a Iso9660fsys 4.23D Mar 20, 2000 installed from the Patch D CD.

What format for the CD are you using? Joliet or Is09660 and what burning s/w
are you using?

//14/bin/Iso9660fsys Iso9660fsys 4.23D Mar 20 2000

-rwxrwxr-x 1 root root 31006 Mar 20 2000 /bin/Iso9660fsys

format Iso9660

Thanks,

  • Ken R

Andrej Lucny wrote:

We distrubute our software on CD and from QNX4.25D there is
no problem with ISO9660 format: no dots on end of extension-less
filenames and even others session than primary one operates.
In previous version of QNX there were dots and only primary
session was operational.

If you have earlier QNX than 4.25D, it is enough to take /bin/Iso9660fsys
from QNX4.25, it works well even under QNX4.24 and may be also 4.23

Andy

8

rectech <rectech@iname.com> wrote:

Follow-up:

Are you using lowercase file names? (I need to.)

I use lowercase letters only.

we prepare file structure, than we use tar to pack it,
we move it to Windows via ftp, unpack and create data CD.
I think we use CD Creator 4.0, I am not sure.
I am sorry for confusion if you had thought I use QNX
for burning.

I found out the ISO9660 standard is for all uppercase file names so my burning
software is just enforcing that. I wonder if QNX (Iso9660fsys) really cares? I’m
looking for other CD burning software like mkisofs - again what s/w are you using?

Thanks,

  • KenR

rectech wrote:

What software are you using to create the CD? The problem I have might be because
I’m using Joliet format. When I use Iso I get all uppercase file names - my
software doesn’t give me any choice in this area. I’ll look closer…

  • KenR

Andrej Lucny wrote:

rectech <> rectech@iname.com> > wrote:
Well this is happening on a 4.25 Patch D system. Please check your
Is09660fsys file for me.

I have a Iso9660fsys 4.23D Mar 20, 2000 installed from the Patch D CD.

What format for the CD are you using? Joliet or Is09660 and what burning s/w
are you using?

//14/bin/Iso9660fsys Iso9660fsys 4.23D Mar 20 2000

-rwxrwxr-x 1 root root 31006 Mar 20 2000 /bin/Iso9660fsys

format Iso9660

Thanks,

  • Ken R

Andrej Lucny wrote:

We distrubute our software on CD and from QNX4.25D there is
no problem with ISO9660 format: no dots on end of extension-less
filenames and even others session than primary one operates.
In previous version of QNX there were dots and only primary
session was operational.

If you have earlier QNX than 4.25D, it is enough to take /bin/Iso9660fsys
from QNX4.25, it works well even under QNX4.24 and may be also 4.23

Andy

9

Thanks for your input. I too am creating the CD under windows but the software that came
with the drive forces all filenames to uppercase when I use ISO9660 format (which is what
the standard is).

I downloaded mkisofs from QNX, configured it then created an iso file with it and then
transferred the file to the CD burning machine and volia I got the lowercase file (and
long) names I needed.

I still think there is something amiss with the joliet format and Iso9660fsys with
filenames without extensions. The original Joliet CD’s I created do not have the ‘.’ but
QNX shows one. Since I have a workable solution I’ll just note this and move on.

Any comments QNX?

  • KenR

Andrej Lucny wrote:

rectech <> rectech@iname.com> > wrote:
Follow-up:

Are you using lowercase file names? (I need to.)

I use lowercase letters only.

we prepare file structure, than we use tar to pack it,
we move it to Windows via ftp, unpack and create data CD.
I think we use CD Creator 4.0, I am not sure.
I am sorry for confusion if you had thought I use QNX
for burning.

I found out the ISO9660 standard is for all uppercase file names so my burning
software is just enforcing that. I wonder if QNX (Iso9660fsys) really cares? I’m
looking for other CD burning software like mkisofs - again what s/w are you using?

Thanks,

  • KenR

rectech wrote:

What software are you using to create the CD? The problem I have might be because
I’m using Joliet format. When I use Iso I get all uppercase file names - my
software doesn’t give me any choice in this area. I’ll look closer…

  • KenR

Andrej Lucny wrote:

rectech <> rectech@iname.com> > wrote:
Well this is happening on a 4.25 Patch D system. Please check your
Is09660fsys file for me.

I have a Iso9660fsys 4.23D Mar 20, 2000 installed from the Patch D CD.

What format for the CD are you using? Joliet or Is09660 and what burning s/w
are you using?

//14/bin/Iso9660fsys Iso9660fsys 4.23D Mar 20 2000

-rwxrwxr-x 1 root root 31006 Mar 20 2000 /bin/Iso9660fsys

format Iso9660

Thanks,

  • Ken R

Andrej Lucny wrote:

We distrubute our software on CD and from QNX4.25D there is
no problem with ISO9660 format: no dots on end of extension-less
filenames and even others session than primary one operates.
In previous version of QNX there were dots and only primary
session was operational.

If you have earlier QNX than 4.25D, it is enough to take /bin/Iso9660fsys
from QNX4.25, it works well even under QNX4.24 and may be also 4.23

Andy