Long lines in the MimeMap file crash the filer

Not sure whether this is known about already but I have a very long Text &FFF line in my MimeMap file. I added an extra term and after issuing the readmimemap command the filer crashed with an error “Not a heap block”. I rebooted and the bootup crashed out with the same error leaving me with a crashed desktop and back at the supervisor prompt. Luckily I’d kept a copy of the old MimeMap file! This is with OS 5.16.

Jeff

Yes, this is obviously a bug.

However, it really shouldn’t be required to have lots of entries in MimeMap for Text. The reason is that if a program is not defaulting to fff for an unknown type, then is using non-de facto behaviour:

http://www.riscos.info/index.php/RISC_OS_Filename_Translation

Indeed, the MimeMap file is something which should be consistent across all systems except in the most unusual cases, and is an excellent example of something to be packaged because of this.

You’re dead right Peter. I was adding the .srt type (Media file subtitles). I used &FE4 as the default in FAT32fs to mimic the behavior of DOSFS. I’ve now taken the advice in your docs and changed Fat32Fs to default to &FFF rather than &FE4 for unknown files.