| Re: c64_fcc ? |
E. Nygma & Sons, LLC |
| Zaghadka (zaghadka@hotmail.com) |
2019/05/31 23:59 |
Xref: news.nzbot.com alt.binaries.emulators.mame:4451
Path: news.nzbot.com!3.us.feeder.erje.net!4.us.feeder.erje.net!2.eu.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!goblin1!goblin2!goblin.stu.neva.ru!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!85.12.16.68.MISMATCH!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.am4!peer.am4.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx24.iad.POSTED!not-for-mail
From: Zaghadka <zaghadka@hotmail.com>
Newsgroups: alt.binaries.emulators.mame
Subject: Re: c64_fcc ?
Organization: E. Nygma & Sons, LLC
Reply-To: zaghadka@hotmail.com
Message-ID: <hq44fe5eqr0t23t75al663ibaqcr3mdtfs@4ax.com>
References: <1p31fepoj1ea9ko4telmv3n254meqc12kp@4ax.com> <f6h1fepqkdmnbjaue6n38qtr6cvjfdnttm@4ax.com> <g3v3fel40gv17khcar78bc6ul57oeunit3@4ax.com>
X-Newsreader: Forte Agent 3.3/32.846
X-No-Archive: yes
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 52
X-Complaints-To: abuse@easynews.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Sat, 01 Jun 2019 00:59:37 -0500
X-Received-Bytes: 2943
X-Received-Body-CRC: 776106501
On Fri, 31 May 2019 23:34:26 -0500, in alt.binaries.emulators.mame,
Zaghadka wrote:
>On Fri, 31 May 2019 01:09:15 -0500, in alt.binaries.emulators.mame, Larry
>Laffer wrote:
>
>>Did you get your .dat file from an external source or did you have
>>your mame executable generate it?
>>
>>I don't have the file in my set and my CMP is not complaining that
>>it's missing.
>>
>>My .dat file was generated from the mame executable that I compiled
>>from the release source code.
>>
>>On Thu, 30 May 2019 21:20:59 -0500, Zaghadka <zaghadka@hotmail.com>
>>wrote:
>>
>>>Anybody know what the story is with c64_fcc.zip? CMPro's automatically
>>>generated .dat file doesn't seem to know what to do with it.
>>>
>>>It claims it's a 0 byte file, and that the actual file is unnecessary.
>>>
>>>Once it deletes the file, it complains that the set is gone.
>>>
>>>Is there some trick here?
>
>I had MAME generate it. PD says that there are problems with -listxml and
>that you should use their .dat file, but when I tried it, waaaay to many
>errors came up. I got scared and stopped scanning. I did try it because
>generating the .dat from MAME caused this problem with c64_fcc.
>
>MAME itself reports no unavailable sets, so I don't know what's up with
>PD's list. I just told CMPro it to keep the zip file until next release.
Okay, so just deleting c64_fcc.zip manually was better than letting CMPro
do it on its own, because it didn't crop up an error once it was gone
that way.
I just discovered that the .dats generated from the MAME executable in
CLRMamePro aren't worth much, though. I ran the full directory through
PD's .dat file, and it removed about a gig of garbage that didn't need to
be in the sets.
So I'm switching over to PD's .dats. Generating a .dat file from the
executable doesn't work right.
--
Zag
No one ever said on their deathbed, 'Gee, I wish I had
spent more time alone with my computer.' ~Dan(i) Bunten
|
|
|