first of all plz don't just give a link, I've been to all of them.
I mean WTF is happening to mame. I'm not a pro on this but I've tried to read every faq that I could download, so far so good but now I mean WTF I have to deal with the following.
I've downloaded.
mame Test Drivers v0.69u3.zip
mame069u3b.zip
mame069u3b_i686.zip
mame069u3s.zip
mame32 test drivers working.zip
mame32v69bb.zip
mame32v69u3b.zip
mame32v69u3b_i686.zip
mame69u3-thl.dat
rom0.69u3.zip
mame068b.zip
I downloaded some 200 roms with 69u3 in the subject for which only 3 work before and after building them with clrmame pro.
I've downloaded another different 100 roms and tried them in various MAME frontends and nothing.
So your a newbie and see this.
You have to deal with 0.69 to 0.69u3 update 0.69u3 new and changes 0.69u3 source and binaries 0.69u3 testdriver CMP Dat file 0.69u3 Testdrivers roms and 30 diff types of frontends and just now I saw some 0.70 beta roms. You have split sets, merged sets, you need to scan sets you need to rebuild sets, you have snapshots, cabinet files and mame titles and ect....
Someone asked.
> This is showing 173 roms not working. After I checked the Non working
> Roms list that Mame 32.69 shows I checked mame dk I compared the files
> and most of them are listed as not working on their list either. My
> question is how can they show them to be perfect files if they do not
> work?
>>Non working means exactly that, the emulation is not working correctly.
>>That doesn't mean the rom is incorrect in any way.
Well again, why put out an emulator that can't work ??
Ok for you pro's it's no problem but WTF does work ??? and what works with what. You say that "non working means exactly that, the emulation is not working" so what your posting roms or emulators that don't work ???
If your posting a 0.69u3 rom should it not work in mame32v69u3b.zip
I have access to mame32's and all the roms there are but what friggen works ? can someone give me a rundown on how this works.
I mean WTF is happening to mame. I'm not a pro on this but I've tried to read every faq that I could download, so far so good but now I mean WTF I have to deal with the following.
I've downloaded.
mame Test Drivers v0.69u3.zip
mame069u3b.zip
mame069u3b_i686.zip
mame069u3s.zip
mame32 test drivers working.zip
mame32v69bb.zip
mame32v69u3b.zip
mame32v69u3b_i686.zip
mame69u3-thl.dat
rom0.69u3.zip
mame068b.zip
I downloaded some 200 roms with 69u3 in the subject for which only 3 work before and after building them with clrmame pro.
I've downloaded another different 100 roms and tried them in various MAME frontends and nothing.
So your a newbie and see this.
You have to deal with 0.69 to 0.69u3 update 0.69u3 new and changes 0.69u3 source and binaries 0.69u3 testdriver CMP Dat file 0.69u3 Testdrivers roms and 30 diff types of frontends and just now I saw some 0.70 beta roms. You have split sets, merged sets, you need to scan sets you need to rebuild sets, you have snapshots, cabinet files and mame titles and ect....
Someone asked.
> This is showing 173 roms not working. After I checked the Non working
> Roms list that Mame 32.69 shows I checked mame dk I compared the files
> and most of them are listed as not working on their list either. My
> question is how can they show them to be perfect files if they do not
> work?
>>Non working means exactly that, the emulation is not working correctly.
>>That doesn't mean the rom is incorrect in any way.
Well again, why put out an emulator that can't work ??
Ok for you pro's it's no problem but WTF does work ??? and what works with what. You say that "non working means exactly that, the emulation is not working" so what your posting roms or emulators that don't work ???
If your posting a 0.69u3 rom should it not work in mame32v69u3b.zip
I have access to mame32's and all the roms there are but what friggen works ? can someone give me a rundown on how this works.