| カテゴリ | 重要度 | ステータス | 解決状況 | 登録日時 | 最終更新 |
|---|---|---|---|---|---|
| 重要 (ゲーム) | 認証済み | 未処理 | 2025-05-12 19:54 | 2025-05-13 21:23 | |
| テスター | jeff0811 | 担当者 | ソース | nintendo/nes.cpp | |
| バージョン | 0.277 | 発生バージョン | 修正バージョン | ||
| 修正コミット | プルリク | ||||
| フラグ | |||||
| セット | fds, famitwin | ||||
| セット詳細 |
 famitwin - ツインファミコンfds - ファミリーコンピュータディスクシステム | ||||
| 概 要 | ディスク書き込みが失敗する。 | ||||
| 詳 細 | 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. | ||||
| 再現手順 | 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. | ||||
| 追加情報 | - 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. | ||||
| 添付ファイル |  zeldaa.png (2025-05-13 21:20) | ||||
| zeldaa2.png (2025-05-13 21:23) | |||||