Jump to content

Invalid Romset! No matching gfx-files found!


Recommended Posts

Before anything else, i would like to thank the guys who helped me out on my samsho5.zip issue. :) (Agozer & Robbert)

 

Now, my problem is, I have another rom named kof2003.zip

The size is 38.9mb. When i start neorage or whenever i press import,

the rom is not recognized.

 

although the components inside was named

 

271-_ _ _.rom

271-_ _ _.bin

 

I did tried to rename them to something like

 

kof2003- _ _ _.rom

 

and the.bin was replaced with.rom

 

but when i tried to run the program,

neorage displays a message that says,

 

Invalid Romset! No matching gfx-files found!

 

Why is it so?

Link to comment
Share on other sites

NRX only recognizes .rom files.

 

The .bin ones might be encrypted.

 

This is what I've got in my set

 

size-------crc------name

16777216 c29acd28 271-c1.rom

16777216 328e80b1 271-c2.rom

16777216 020a11f1 271-c3.rom

16777216 991b5ed2 271-c4.rom

524288 0e86af8f 271-m1.rom

8388608 57a1981d 271-p1.rom

131072 df422440 271-s1.rom

16777216 2058ec5e 271-v1.rom

 

That's all you need.

Link to comment
Share on other sites

I think that EGCG NRX recognizes bin files as well, but remaing everything to rom avoid any problems.

 

Post your file and CRC info of the files and I'll see how they match mine.

Link to comment
Share on other sites

Hope this might help...

#  Archive C:\Downloads\kof2003.zip
2004-01-13 23:14       4194304       3297579  ddbbb199  271-v3d.rom
2004-01-13 23:14       4194304       3338699  01b90c4f  271-v4d.rom
2004-01-13 23:11       8388608       3535693  e42fc226  271-c1d.rom
2004-01-13 23:11       8388608       2432822  1b5e3b58  271-c2d.rom
2004-01-13 23:11       8388608       4069714  d334fdd9  271-c3d.rom
2004-01-13 23:11       8388608       2873757  0d457699  271-c4d.rom
2004-01-13 23:12       8388608       3918191  8a91aae4  271-c5d.rom
2004-01-13 23:13       8388608       2522893  9f8674b8  271-c6d.rom
2004-01-13 23:12       8388608       3471707  374ea523  271-c7d.rom
2004-01-13 23:13       8388608       2281068  75211f4d  271-c8d.rom
2003-12-14 19:27        524288        231438  0e86af8f  271-m1d.bin
2003-07-29 00:16       4194304       1228590  92ed6ee3  271-p1.bin
2003-07-29 01:09       4194304        754027  5d3d8bb3  271-p2.bin
2004-01-08 17:40        131072         10907  c47f8ac3  271-s1.rom
2004-01-13 23:14       4194304       3462014  d2b8aa5e  271-v1d.rom
2004-01-13 23:14       4194304       3388141  71956ee2  271-v2d.rom
#
# Total                   Size        Packed            Files
#                     92930048      40817240            16

Edited by KyoKusanagi
Link to comment
Share on other sites

Hope this might help...

#  Archive C:\Downloads\kof2003.zip
2004-01-13 23:14       4194304       3297579  ddbbb199  271-v3d.rom
2004-01-13 23:14       4194304       3338699  01b90c4f  271-v4d.rom
2004-01-13 23:11       8388608       3535693  e42fc226  271-c1d.rom
2004-01-13 23:11       8388608       2432822  1b5e3b58  271-c2d.rom
2004-01-13 23:11       8388608       4069714  d334fdd9  271-c3d.rom
2004-01-13 23:11       8388608       2873757  0d457699  271-c4d.rom
2004-01-13 23:12       8388608       3918191  8a91aae4  271-c5d.rom
2004-01-13 23:13       8388608       2522893  9f8674b8  271-c6d.rom
2004-01-13 23:12       8388608       3471707  374ea523  271-c7d.rom
2004-01-13 23:13       8388608       2281068  75211f4d  271-c8d.rom
2003-12-14 19:27        524288        231438  0e86af8f  271-m1d.bin
2003-07-29 00:16       4194304       1228590  92ed6ee3  271-p1.bin
2003-07-29 01:09       4194304        754027  5d3d8bb3  271-p2.bin
2004-01-08 17:40        131072         10907  c47f8ac3  271-s1.rom
2004-01-13 23:14       4194304       3462014  d2b8aa5e  271-v1d.rom
2004-01-13 23:14       4194304       3388141  71956ee2  271-v2d.rom
#
# Total                   Size        Packed            Files
#                     92930048      40817240            16

 

I only have the P and M roms of that lot so I must guess a bit.

 

The P roms are encrypted (from kof2003b) and cannot be used with NRX. The others might be alright as long as you rename them thus:

 

271-c6d.rom -> 271-c6.rom (remove the d).

 

The 271-s1.rom might already be ok.

 

The 271-m1d is ok as long as you rename it as above.

Link to comment
Share on other sites

It doesn't really matter if the d is there in the filename. If NRX doesn't recognize a game that usually means that either the P1 rom or the M1 rom are encrypted, or simply incompatible with NRX.

 

The P roms are encrypted, and won't work with NRX. Same thing with the M1 I suppose. I have a single P1 rom (B87049F2), M1 (396E17CD) and S1 (DF422440).

Link to comment
Share on other sites

It doesn't really matter if the d is there in the filename. If NRX doesn't recognize a game that usually means that either the P1 rom or the M1 rom are encrypted, or simply incompatible with NRX.

 

The P roms are encrypted, and won't work with NRX. Same thing with the M1 I suppose. I have a single P1 rom (B87049F2), M1 (396E17CD) and S1 (DF422440).

わるいです。。。 :cry:

So what'll be the remedy? :huh:

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...