| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 09171 | Media Support | Critical (emulation) | Always | 1 day ago | 9 hours ago |
| Tester | jeff0811 | View Status | Public | Platform | MAME (Official Binary) |
| Assigned To | Resolution | Open | OS | Windows 10/11 (64-bit) | |
| Status [?] | Confirmed | Driver | |||
| Version | 0.277 | Fixed in Version | Build | 64-bit | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 09171: fds, famitwin: DISK SYSTEM disk write failure. | ||||
| Description |
FDS and Twin Famicom Drivers: Save Write Corrupts .fds Files in Nazo no Murasame, Zelda no Densetsu, and Akumajou Dracula Saving in FDS and Twin Famicom drivers corrupts .fds files, causing crashes, infinite waits, or stuck saving screens, severely impacting gameplay. The issue affects multiple games and drivers, suggesting a bug in the shared FDS emulation core (src/mame/nintendo/fds.cpp). - In `nazomura` (`fds`/`famitwin`): Saving (e.g., name registration) crashes the game, corrupts .fds. - In `zelda` (`fds`/`famitwin`): Name registration causes infinite wait, reset shows ERROR 23 (disk error), corrupts .fds. - In `dracula` (`fds`/`famitwin`): Initial saves (e.g., name registration) do not write to disk and work fine. Saving after Game Over (selecting "Save") hangs on "NOW SAVING" (tested for 5 minutes), reset shows ERROR 23, corrupts .fds. - Corrupted .fds files are invalid in SMYnes and VirtuaNES (format error). In FCEUX 2.2.2, `nazo no murasame` and `zelda` saves are readable (e.g., progress 000000), but `akumajou dracula` only shows old save data, not latest progress. - No NVRAM files created (`nvram` folder empty); MAME writes directly to .fds. - Logs show identical errors in both drivers: `unmapped program memory read` (4002/4003/4006/4007/400A/400B) and `PPU read past chip` (offsets 262/1540/1d09/1e09). - Related to bug #06321 (Confirmed, 0.174, nazomura black screen), but expanded with .fds corruption, Twin Famicom, additional games, and new evidence. - Workaround: Hacked .fds files with pre-existing saves (common in early piracy) and MAME's RTS (Save State) avoid save writes but deviate from authentic emulation. |
||||
| Steps To Reproduce |
1. Run `mame fds nazomura -log`, `mame fds zelda -log`, or `mame fds akumajob -log`. 2. For `nazomura`: Trigger save (e.g., name registration). Observe crash. 3. For `zelda`: Enter name, select END. Observe infinite wait, reset for ERROR 23. 4. For `akumajob`: Play until Game Over, select "Save". Observe "NOW SAVING" hang (wait 5 minutes), reset for ERROR 23. 5. Repeat with `famitwin` driver (`nazomura`, `zelda`, `akumajob`). Observe identical issues. 6. Check .fds: - Invalid in smynes/VirtuaNES. - In FCEUX, `nazomura`/`zelda` saves readable; `dracula` shows old save only. 7. Check `nvram` folder: Empty. 8. Review logs for `unmapped program memory read` and `PPU read past chip` errors. |
||||
| Additional Information |
- Related to bug #06321 (Confirmed, 0.174, nazomura black screen). - Tested with original .fds files (No-Intro DAT). - Hacked .fds files (pre-existing saves) work in FCEUX, smynes, VirtuaNES, and MAME, bypassing save writes. - RTS (Save State) is non-authentic but functional. - FCEUX reads corrupted `nazomura`/`zelda` saves but fails for `akumajob` latest progress, indicating severe corruption. - No NVRAM usage suggests direct .fds writes. - Identical `fds`/`famitwin` errors point to shared FDS code bug. - `akumajob`’s initial saves not writing to disk isolates issue to save writes. - Suggest checking disk controller (2C33) write logic. |
||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | fds, famitwin | ||||
|
Attached Files
|
ZELDA Register Complete
| ||||
Endless waiting.
| |||||
 No.23280
Robbbert Moderator
11 hours ago
|
Some mistakes with this report. 1. nazomura is being referred to as murasame which doesn't exist. 2. when entering name in for zelda, there is no END, so stuck at name entering screen However I can confirm there are issues, so the status has been set accordingly. |
|---|---|
 No.23281
jeff0811 Tester
9 hours ago
edited on: 9 hours ago
|
Subject: Clarification and Correction for Bug Report #09171 (FDS Save Issues) Dear Moderators and Developers, Thank you for reviewing and confirming the issues in bug report #09171. I apologize for the errors in the original report and would like to provide the following corrections and clarifications to assist with further investigation: Typo Correction (Nazomura, not Murasame): The report incorrectly referred to the FDS game Nazomura (なぞむら) as "murasame." This was a typo; Clarification on Zelda no Densetsu Issue: The bug in Zelda no Densetsu does not involve a missing "END" option in the name entry screen, as I may have implied. Instead, the issue occurs when selecting トウロク オワル (Touroku Owaru, "Register Complete") after entering a name. Upon clicking this option, the game hangs or fails to save properly, potentially tied to the broader FDS save issue (e.g., disk write failure). I’ve attached a screenshot (zeldaa.png), Thank you for your time and effort in addressing this critical issue. Please let me know if further information or testing is required. Best regards, |