Hello kind folks,

I have a weird problem that I've never experienced before and also couldn't find much info about in the net. The closest thing I could dig up is this thread, but it doesn't provide a solution for me.

Here's the problem:
I have a CD that contains a bunch of photos (regular JPG files) taken by other people during several school events. It was created by the school, presumably on a Windows machine, and handed out to the parents. The CD mounts under Linux with no problems, but alas appears to be completely empty. When I mounted the disc on a Windows box to double-check, the files showed up. Both Linux mount and Nero on Windows tell me that the CD holds a ISO9660 file system. Trying to mount the disc with different FS type (UDF) under Linux fails as expected. 'Properties' on Windows claim the FS to be 'cdfs', but AFAIK this is Windows-Lingo for any disc-bound file system.

Now for the question(s):
What's the problem, and how can I solve it? Anyone else experience this? It's unbearable that a Windows box should be able to do something that my Linux machines can't. :-)

Some more background, for what it's worth:
I'm using Slackware Linux 13.37 on several computers, all of which weren't able to read the disc's contents (hence assuming no hardware issue). The double-check was done on a Windows XP box.
The CD is a 700 MB disc (non RW), according to Nero it contains 1 Session with 1 Track, ISO 9660/Joliet (mode1).

Thanks for any hints, links or comments!

See this link, it show you hoe to mount a ISO9660 file system.

-->http://www.cyberciti.biz/tips/how-to...der-linux.html

Hope this helps.

In a terminal, after the disk in inserted and mounted, enter "mount". This tells us if it actually got mounted and where. Assuming it did, then cd to the mount point, and do "ls -al"
Post the results of both commands

Thanks for the quick replies!

Camorri, the linked article actually treats mounting of ISO image files, not optical media.

Pixellany, I should have written it more clearly in my first post: I've already done all the above on the command line. mount had no surprise for me as to the location of the mount point (/mnt/cdrom), and ls -alF gave me what it gave me all the while, which is an empty directory.
However! After work I had a closer look at the mount man page and fiddled around with some options. Turns out if I pass -o nojoliet to the mount command, the files show up, albeit with ISO9660's name length limitations.

This is weird nonetheless. I've had plenty of discs from all kinds of operating systems in this machine, mostly UDF, but also numerous ISO9660+Joliet media, and unless they were badly scratched or had soy sauce etched in them, they always worked. Did M$ change their Joliet stuff in recent Windows versions? Or could this be the work of a Mac, trying to undermine established standards?
Seriously interested if anyone has an idea.

As for this particular problem, it seems to be solved (kinda). But I'd really love to get to the bottom of this.
Thanks for any further insights!