Why the ISO file isn't same between linux and windows!
 

I got a iso file,but it isn't the same between windows and linux.I mount it inwindows and found it's the iso9660/joliet format using nero6 and winiso5.3,I mount it in suse 8.2 and found it is a "trans.tbl" file in each directory ,the file isn't found in windows.I want to know why it is and whether the file is right and the format of the file.Thanks!
Is the file made in linux?
Does the "-r "and "-j" can be used at the same time in the mkisofs? Is windows only support joliet format and linux support both joliet and rock ridge format?
Thanks!

that file is a file that tells the os where stuff is on the iso, when making an iso you have to specify it is hidden for all os's to hide it, otherwise windows is the only one to hide it. also you need to have joliet enabled in your kernel

Thanks!
But I double in you answer.I think the trans.tbl is used to get the long filename when the os isn't support the long filename.
The trans.tbl is created by "mkisofs -T ......",and I can find the file in many linux distribution disc under the windows.
I have a new problem,I burn a disc in the window2000 using the nero 5.5.9.8, the soure filenames have captial and small letter,but it has only small letter in the linux and captial letter in the windows2000.Is it the bug of nero?But why small letter in the linux and captial letter in the windows2000>

I think that is because windows will, by default, capitalise all leading letters for all filenames regardless of how you typed them in. Therefore, windows files can actually be stored on the disc in lower case but displayed in upper case.

Another reason that could cause this would be that mayber the iso9660 filesystem might not support capitals (although I think it does).

I think the root of the problem is likely that linux sees capital and lowercase as different and windows sees them as the same, for instance I had 2 files once: Somefile and somefile each in the same directory, one cap, one not. I tried to copy it into windows and it gave me errors and overwrite prompts. despite all the work done, at there bases linux and windows have nothing in common. linux takes user input and makes use of it, windows takes it and f-cks it up.

Thanks exodist and adz.

I still double that the iso files have "TRANS.TBL" files in the linux but not in the windows,the files are down from "http://darkstar.ist.utl.pt/openbsd/3.3/openbsd-i386-3.3-packages1.iso & http://darkstar.ist.utl.pt/openbsd/3...-packages2.iso".Other iso files have "TRANS.TBL" files both in the linux and the windows.

version of mkisofs I bet

But " http://darkstar.ist.utl.pt/openbsd/3...6-3.3-mini.iso & http://darkstar.ist.utl.pt/openbsd/3...d-i386-3.3.iso" is normal.They may be made by the same version. Is it possible that the files are too large,and incompatible with windows?

with windows anything bad is possible, but I doubt it.

Thanks in any case!

I have got the answer!
I use "isobuster" in the windows,then find there are three filesystem(iso9660,rock ridge,joliet) under the track 01. " http://darkstar.ist.utl.pt/openbsd/...86-3.3-mini.iso"has the "TRANS.TBL" in the three filesystem,but " http://darkstar.ist.utl.pt/openbsd/3...-packages1.iso"has the "TRANS.TBL" in the iso9660 and rock ridge,not in the joliet.
I want to know how to make the file like http://darkstar.ist.utl.pt/openbsd/3...packages1.iso?
Thanks!

do a "man mkisofs" then look for the flags.

I can know from man page that "mkisofs -J -r -T -o filename.iso directory" can make a file format like " http://darkstar.ist.utl.pt/openbsd/...86-3.3-mini.iso" ,but the man page cann't tell me how to make a iso with different content in different filesystem.

i think I follow, but then again you have the question so I do not need to follow :-P