> Thanks! So I wasn't neither paranoid nor drunk, when I thought there was strange
> behavior :)

Well..it happened because the clone was renamed, too....a bit complicated to go into details....I've fixed it by changing the behaviour of fixmissing (which is internally used for moving files). Fixmissing now checks all clones, even if the currentfile is a clone, too.

anyway...get 3.05a ;)

Roman Scherzer
ClrMamePro