Build Your Own Arcade Controls Forum

Main => Software Forum => Topic started by: BORIStheBLADE on December 28, 2007, 08:38:23 pm

Title: Rom extension id question
Post by: BORIStheBLADE on December 28, 2007, 08:38:23 pm
SO looking at some SNES roms I notice at the ending of the rom name there is a (j), (e), (u), [!] and etc . Could someone let me know what these mean.

Thanks.
Title: Re: Rom extension id question
Post by: gonzo90017 on December 28, 2007, 09:18:17 pm
(j) = japan
(e) = europe
(U) = us
(!) = known good dump
Title: Re: Rom extension id question
Post by: Turnarcades on December 28, 2007, 09:50:55 pm
If you are looking to filter them down, keep the best one of each rom (eg if you are in the UK, keep the (E) roms).
Title: Re: Rom extension id question
Post by: BORIStheBLADE on December 28, 2007, 09:58:57 pm
ok, I'm in the us so I'll keep those. Is there a symbol for a bad/non working rom?
Title: Re: Rom extension id question
Post by: unclet on December 28, 2007, 10:57:12 pm
Here you go ....

http://www.mameworld.net/easyemu/gtguide.htm#section5

Title: Re: Rom extension id question
Post by: BORIStheBLADE on December 29, 2007, 10:08:16 am
Thanks for the info guys. I got one more, I have N64 roms with a .V64, .Z64 and .n64. Do they all work? Or should I only keep one kind?
Title: Re: Rom extension id question
Post by: unclet on December 29, 2007, 10:51:06 am
I use the Project64 emulator for my Nintendo64 Roms, although all of my N64 rom files are in ZIP format.   I looked in about 15 ROM files I have and all of them are "z64", although Porject64 might be able to handle other extensions ..... not sure.

Why are your ROM files not ZIP'd?
Title: Re: Rom extension id question
Post by: BORIStheBLADE on December 29, 2007, 11:30:55 am
well... I unzipped them because I saw multiples in the zip. Like (j), (e) and (u) versions.
Title: Re: Rom extension id question
Post by: unclet on December 29, 2007, 12:27:52 pm
Well, my ROM files have the (U)! symbol in the "filename.ZIP" name and they only contain a z64 extension file inside.