| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 07208 | Multisession | Critical (emulation) | Always | Jan 19, 2019, 16:02 | Sep 8, 2025, 02:51 |
| Tester | -Misc Reporters- | View Status | Public | Platform | MAME (Official Binary) |
| Assigned To | Resolution | Open | OS | Windows Vista/7/8 (64-bit) | |
| Status [?] | Confirmed | Driver | |||
| Version | 0.205 | Fixed in Version | Build | 64-bit | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 07208: kof2001, kof2002: Starting KOF2002 after running KOF2001 causes machine malfunction | ||||
| Description | Starting KOF2002 after running KOF2001 causes machine malfunction. | ||||
| Steps To Reproduce |
From original reporter Kataninja: https://github.com/mamedev/mame/issues/4531 - mame64 kof2001 - After the attract mode start TAB > Select New Machine > kof2002 - The machine get in to an infinite reset loop. This doesn't happen to other machines tested so far, only with neogeo. |
||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | 0.188 | ||||
| Affected Sets / Systems | kof2001, kof2002 | ||||
|
Attached Files
|
 Screenshot (793).png (729,913 bytes) Sep 6, 2025, 21:29 Uploaded by hap | ||||
 No.16137
Robbbert Moderator
Feb 12, 2019, 23:33
|
The problem becomes more obvious if you run kof2001 then mslug3 - it will crash, revealing the fact that the decryption routines for kof2001 are still in effect. Strangely, the problem doesn't occur when using MAMEUI or ARCADE - only when using MAME's inbuilt UI or the Tab menu. |
|---|---|
|
No.16146
Robbbert Moderator
Feb 15, 2019, 11:31
|
Some dumps and other examples in https://github.com/mamedev/mame/issues/4520 |
 No.23645
M.A.S.H. Senior Tester
Sep 6, 2025, 17:34
|
Has anyone found out what this strange error is? Start with: mame kof2001 After "Loading Complete" Press Menu - "Select New System" Type kof2002 + ENTER "Select System BIOS" + ENTER MAME only shows crap... |
 No.23646
hap Developer
Sep 6, 2025, 20:09
edited on: Sep 6, 2025, 22:46
|
mame-170624-4a4883dd6504c7172a9ad62eebc123c1389ca347 = ok mame-170625-fb61e98cc5b4dca8282c7388a00106f330851171 = bug None of the commits between those 2 touches anything directly related to neogeo. Probably this commit: https://github.com/mamedev/mame/commit/b193e05cd7c8456a2648d43854645da84f56ddbd I suspect MAME remembers the slot device option since it thinks it's loading the same romset (neogeo in this case, which is actually a BIOS set). |
 No.23661
cuavas Administrator
Sep 8, 2025, 02:51
|
Yes, I know exactly what causes it. It’s because there’s no way to “peel off” a layer of options. It’s the same thing that causes BIOS settings to leak across sessions, etc. The options system needs another rewrite. |