In message <3852ffe04e.Alan.Adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx> Alan Adams <alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > Generally you want notypes set to no. > > However, if > 1 you want to use the files from both RISC OS and Windows > and > 2 you have given file extensions (e.g. /TXT) to all relevant files > and > 3 you haven't got correct definitions for ALL PC filetypes inside > Lanman98 > then you might want to turn notypes on. > > The reason is that files without extensions which also don't pick up a > type from the mappings file will gain a ,nnn tail, which Windows > doesn't like. In what way? Windows is perfectly happy with ,xxx extensions. Those are only given to files that do not have a mapping, so they are likely to be RISC OS specific files, with which Windows cannot do much anyway. But even with the ,nnn extension you can load the files in a Windows editor, for instance. I find it very difficult to imagine any kind of circumstances where setting Notypes to Y makes much sense. With RISC OS ,xxx extensions enabled (i.e., Notypes=N) all the cross-platform files that you might want to use under Windows as well can be mapped to a proper extension and all the rest is of no interest to the Windows side anyway. So you do not lose anything by having the RISC OS ,xxx extensions. Martin -- --------------------------------------------------------------------- Martin Wuerthner MW Software martin@xxxxxxxxxxxxxxx ---------------------------------------------------------------------