jmon wrote: ↑
Sun Sep 20, 2020 7:24 pm
I had a CHD-converted ROM working fine on my MAME .224 *STABLE* release, but then it just stopped working.
There has not been an upgrade past my Win 10 20H release... nor should there of been any updates since I froze their update service until Tuesday, the 22nd.
no, I don't know of any recent emergency security updates that Microsoft would shove down my throat since I installed original MAME installation.
After three hours of trying to figure out what's changed, I reinstalled MAME from scratch, EXCEPT preserving customized segacd.xml hash file I got from jmonlive (to include rom also given to me by my friend as part of his appended-to software list), customized cheat.7z, and cut'n'paste ROMS directory from old installation and added DAT directory's MAMEINFO.DAT from there as well.
Am I stupid?
Is the proper directory for Sega CD ROM the "segacd" subdirectory under MAMEUI's ROMs directory or was I just almost correct in syntax, but just slightly off?
Are you having issues with other games for SegaCD or just a particular one? Any machine you use, provided you don't change the binary, should function the same way each time. Given the fact that your are using a CHD that was made by you and isn't supported by MAME makes it quite hard to diagnose. Assuming your are running a SEGACD game in MAME and assuming C:\ROMS
is your normal rompath, C:\ROMS\SEGACD
would be the valid default location for software, with the CHD named as the software lists expects, as well as in a FOLDER matching the shortname, against referenced in the softwarelist.
The following example, you want to run the software list game from the segacd.xml, Sonic the Hedgehog CD (USA)
which has the shortname soniccd
. The CHD should be located in C:\ROMS\SEGACD\SONICCD\SONIC CD(USA).chd
. It is important, too, that the actual filename matches what the softlist.xml expects or else it will not load at all or not be found.
A few versions back, loading of images was streamlined and fixed but this also fixed peoples' poor use of the loading mechanism as they never put the romset in a .zip of folder needed. Not sure if this is your case, but it did happen and you need to be fully compliant with your directory structures now.