So, after the experience of receiving countless glitch reports on emulation of Ketsui/DOJBL, investigating them and then discovering that there is in fact no glitch, we will require the following procedure before any time is spent on any claim:
1. Get an MD5 checksum of the MAME binary you are using and attach it to your report. If you are not using the mainline MAME binary (even if you compile it yourself) or shmupsmame, the report will be ignored. You may use this program if you are running windows: http://www.pc-tools.net/win32/md5sums/.
2. Now clear your nvram by deleting the [rom].nv file in the nvram directory. This might reset the settings to none defaults, but won’t be a problem in the future.
3. Record a short run reproducing the bug using the INP recording facility.
4. Find a reference which has the PCB displaying the correct behaviour and attach to your report.
5. Finally, make sure you’re very specific when describing what is happening. The more time you spend carefully describing the putative glitch, the faster we can investigate it and fix it if it’s actually a glitch. A vague report like “teh inputz lagth” will be ignored.
These guidelines will apply to any other driver we work on in the future. That’s all. Enjoy yourselves!
Thanks for some quality points there. I am kind of new to online , so I printed this off to put in my file, any better way to go about keeping track of it then printing?
Comment by college scholarships — 2010/12/17 @ 08:21