[Coco] Mame on debian wheezy

[Joel Rees]

2018年10月3日(水) 8:34 Christopher R. Hawks <chawks at dls.net>:

> On Tue, 2 Oct 2018 22:48:09 +0900
> Joel Rees <joel.rees at gmail.com> wrote:
>
> > 2018年9月30日(日) 10:30 Christopher R. Hawks <chawks at dls.net>:
> >
> > > On Sun, 30 Sep 2018 09:01:24 +0900
> > > Joel Rees <joel.rees at gmail.com> wrote:
> > >
> > > > 2018年9月30日(日) 7:48 Christopher R. Hawks <chawks at dls.net>:
> > > > [...]
> >
> > > > Joel (and all):
> > > > >
> > > > >     You did run 'mame -cc' in your $HOME/.mame directory to
> > > > > create the initial config files?
> > > > >
> > > > >     Oh, and it's $HOME/.mame not $HOME/mame (on linux anyway).
> > > > >
> > > >
> > > > Well, I did a -createconfig, but not actually in ~/.mame .
> > > >
> > > > But I just tried -cc in ~/.mame, and, while it does leave a
> > > > mame.ini in the directory, nothing else changes. Still get the
> > > > unknown system errors on "mame coco3", etc.
> > > >
> > > > Is there something in mame.ini that needs to be set to something
> > > > other than default?
> > > >
> > > > >
> > > >
> > >
> > >     Don't remember what the defaults were.
> > > All the xxxxpath and xxx_directory options (except homepath) start
> > > with $HOME/.mame like this:
> > >
> > > homepath                  .
> > > rompath                   $HOME/.mame/roms
> > > hashpath                  $HOME/.mame/hash
> > >
> >
> > The mame.ini that mame -cc created for me has those all set to
> > $HOME/mame/whatever
> >
> > Is there some sort of extra parameter for mame -cc?
> >
> > And do we need hash values in $HOME/.mame/hash?
> >
>
>     Mine doesn't have a hash sub-dir. Don't know of any params to
> "mame -cc'
>
>     Can you run mame from within the .mame directory? Or the roms
> sub-dir? That would mean that it is a path thing...
>

Teied that long ago. Same results.

I'm thinking the Debian distro team removed all the hashes, and maybe
something else, in their entusiasm for modularization. I should take this
to the Debian list.

>