I got an entry for an EXE based dat in the Profiler. It's for MESS. I just got version 0.80 and wanted to run a new scan with teh new version, but everytime it wants to create the new cachefile I get the error "\temp\_tempdat is used by a different program". And when I end CMP and want to delete the file it isn't possible, because someone still accesses the file.
CMP creates a working MESS cache file, but it tries to read it again everytime I chose the MESS dat and I get the same error everytime.

> I got an entry for an EXE based dat in the Profiler. It's for MESS. I just got
> version 0.80 and wanted to run a new scan with teh new version, but everytime it
> wants to create the new cachefile I get the error "\temp\_tempdat is used by a
> different program". And when I end CMP and want to delete the file it isn't
> possible, because someone still accesses the file.
> CMP creates a working MESS cache file, but it tries to read it again everytime I
> chose the MESS dat and I get the same error everytime.
>


Get a better OS or a better compiler. 8)
The issue is based on a weird combination of the mingw compiler and some older OSes. Some of these compiled binaries lock all redirected output so no other process can access it. Not a cmpro issue.

Roman Scherzer
ClrMamePro

> > I got an entry for an EXE based dat in the Profiler. It's for MESS. I just got
> > version 0.80 and wanted to run a new scan with teh new version, but everytime
> it
> > wants to create the new cachefile I get the error "\temp\_tempdat is used by a
> > different program". And when I end CMP and want to delete the file it isn't
> > possible, because someone still accesses the file.
> > CMP creates a working MESS cache file, but it tries to read it again everytime
> I
> > chose the MESS dat and I get the same error everytime.
> >
>
>
> Get a better OS or a better compiler. 8)
> The issue is based on a weird combination of the mingw compiler and some older
> OSes. Some of these compiled binaries lock all redirected output so no other
> process can access it. Not a cmpro issue.
>
Well..it never happened before with an of MAME or MESS. And it's the binar distributed by the page. I don't compile MESS myself.

> > > I got an entry for an EXE based dat in the Profiler. It's for MESS. I just
> got
> > > version 0.80 and wanted to run a new scan with teh new version, but
> everytime
> > it
> > > wants to create the new cachefile I get the error "\temp\_tempdat is used by
> a
> > > different program". And when I end CMP and want to delete the file it isn't
> > > possible, because someone still accesses the file.
> > > CMP creates a working MESS cache file, but it tries to read it again
> everytime
> > I
> > > chose the MESS dat and I get the same error everytime.
> > >
> >
> >
> > Get a better OS or a better compiler. 8)
> > The issue is based on a weird combination of the mingw compiler and some older
> > OSes. Some of these compiled binaries lock all redirected output so no other
> > process can access it. Not a cmpro issue.
> >
> Well..it never happened before with an of MAME or MESS. And it's the binar
> distributed by the page. I don't compile MESS myself.
>

Win9x/ME possibly? Well...Tough luck....it's a known mingw issue discussed several times on the mamemsgboard.

Roman Scherzer
ClrMamePro

If I remember correctly, if you run the emulator first (play a game) before doing listinfo the files won't be locked.