> > > Hello!
> > >
> > > Using the newest 3.63b with 94u3, I consistently get a lockup of the entire
> > > computer when scanning. It happens when a .dat is created with either
> Mame/Win
> > > or Mame32, but never on the same rom. Any ideas what the problem could be?
> >
> >
> > Random freezes are caused by hardware problems. This could be (but don't have
> to
> > be) one of these:
> >
> > - bad IDE cable
> > - bad RAM or bad RAM timing (esp. on overclocked systems)
> > - buggy VIA chipsets
> > - bad harddisk
> >
> >
> > maybe it's just a weird virusscanner interfearing when accessing a zip.
> >
> > Roman Scherzer
> > ClrMamePro
> >
>
> Roman,
>
> Thanks for the quick response.
>
> First, let me say that it is a lockup of ClrMame, not the computer. Normally, I
> would say the same thing regarding what the problem could be, except that every
> component is the same that has been successfully scanning for the last year or
> more. I have also turned off virus scanning during ClrMame scanning.
>
> The only difference is the Mame executable itself. I was just hoping that there
> was a change in Mame you knew about that caused this. Needless to say, I am
> mildly frustrated...


Turn on settings->zipsettings->full structure scan.
...or maybe it found a large file somewhere in your rompaths and it calculates checksums for it. But that would happen at the same point every time.
I still assume it's a timing issue. Maybe the cpu gets too hot ;). People underestimate the resourceusage from the scanner/rebuilder. It causes immense traffic on the IDE controller / RAM.
You can play a bit with disabling systems or sets to lower the number of sets to scan.

Roman Scherzer
ClrMamePro