Forums  ›  Romz  ›  InSearchOf
 

MAME 0.262 SL/CHD sooner requests

As usual because RR does not provide SL

Use his thread for added SL/CHD stuff (from official 0.261 to the next official release 0.262)

Don't search/post here stuff that is already added to 0.261 or earlier!

https://mega.nz/folder/nQ11zAaJ#2HwFVwaGJd6RTqvOoJnZWg

Mame .262,  After auditing my roms, there seems to be a problem still.

Is anyone else having this issue?

 

Super Nova (Novag, v1.05) [folder: nsnova - size: 67kb]
missing rom: nvip.svg [size: 35502] [CRC32: 3e520357] [SHA1: f6188bcff8995e84ea28f641cfbd755139498d76]

Super VIP (v3.7) [folder: nsvip - size: 83kb]
missing rom: nvip.svg [size: 35502] [CRC32: 3e520357] [SHA1: f6188bcff8995e84ea28f641cfbd755139498d76]

Supremo [folder: supremo - size: 67kb]
missing rom: nvip.svg [size: 35502] [CRC32: 3e520357] [SHA1: f6188bcff8995e84ea28f641cfbd755139498d76]

Mame 0.262 isn't released, yet.

That SVG got changed a week ago.

https://github.com/mamedev/mame/commit/07b461affedccf427f4df1c6ea41c01b61ef030a#diff-60a20dadc709521f57d5204959581179e9b78832b73371e27c86df46f175e551

 

 
 

His issue is likely that the MameUI "Classic" is listed as 0.261.2 and was compiled with that changed nvip.svg file in those 3 ROMs so you get 3 missing ROMs after a full rebuild/scan.

Mame 0.262 isn't released, yet.

That SVG got changed a week ago. 

 

Thank you for the detailed and prompt reply.

Is it safe to assume that when MameUI Classic 0.262 is complied it should fix this issue?

This update folder is work in progress until the official 0.262 MAME is published. All items could change within an update period several time. I'm updating this folder when I have compiled a new builds and verified the roms/set. Please keep also in mind that those are "update" roms/set, it needs to be rebuild to a full set.

If you are using own versions or unofficial one I can not give support for them, sorry.

some md and coleco roms: https://workupload.com/archive/2j6k9U45ZB 

At the moment I have problem to upload the second LD CHD to BDA ......its on MEGA, but keep in mind that it is a problem with a free account to download it. Use the MEGA-Client ....

i have this fix for mame 0.262 and for the tame pool 10 i have this message when i want to launch

 

fix arcade 0.262.dat2.8K2 downloads

Hello folks,

PSR540.zip is missing these two files:

psr540      : xw25410.ic210 (4194304 bytes) - NOT FOUND
psr540      : xw25520.ic220 (2097152 bytes) - NOT FOUND

Or maybe there is something I don't get :)

Thanks for letting me know how could I fix this.

 

 

PSR540

 http://90.230.15.34/Arcade/MAME/psr540.7z

 

i have this fix for mame 0.262 and for the tame pool 10 i have this message when i want to launch

 

 http://90.230.15.34/Arcade/MAME/pool10.7z

Hey guys. Currently clrmamepro only complains about dlair.chd. I have 2 versions, both are refused. Should I use chdman with some command to make it accepted?

 

First dlair.chd

Size: 12296654098

CRC32: 9975f5e3

MD5: 442bf793e59883c6541a5e077c33b1d3

SHA1: ddb266fefc9829b246cd22bd01cac0867749a3d3

 

Second dlair.chd

Size: 12296654098

CRC32: 99f29438

MD5: aff2157d982bbf4e40e2a840000f5292

SHA1: 4908e21cb83093004c36da1d417b4fce5b80bade

 

The second came from the link posted in this thread.

Keep in mind that we are now with 0.264

The one we have on RR is correct, no idea where your checksum comes from 

check it with chdman.exe before downloading it again or from somewhere else ;-)

Yes, I do know that current MAME version is 0.264. I came to this thread because it's the one when the latest dlair.chd was released. I used chdman on the file I downloaded from Mega (link provided on the first post) and its SHA1 checks: "SHA1: c3ee2e27aa4847bf3884fc0d18f26f315456aa9e"

To answer your question, the CRC32, MD5 and SHA1 info I posted came from clrmamepro's built-in checksum calculator. Maybe there is a bug in this software that noone noticed yet? I have version 4.048d and it keeps putting dlair.chd in backup folder.

D:\mame>mame dlair -verifyroms

romset dlair is good

1 romsets found, 1 were OK.

Keep in mind that we are now with 0.264

The one we have on RR is correct, no idea where your checksum comes from

Funny, after I put it back on roms folder, clrmamepro didn't complain about it again. Not sure what to think, I guess that has something to do with a recent upgrade I did on this software. Anyway, all is good now. Thanks.

Forums  ›  Romz  ›  InSearchOf