View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0003887 | DungeonMaster | [All Projects] General | public | 2018-05-31 09:34 | 2022-12-29 17:56 | ||||||||
Reporter | rubin | ||||||||||||
Assigned To | JOTD | Project Info | Dungeon Master (FTL/Software Heaven) http://www.whdload.de/games/DungeonMaster.html | ||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||||
Status | closed | Resolution | no change required | ||||||||||
Summary | 0003887: Dungeon Master starts fine. When you enter the first level (The Hall of | ||||||||||||
Description | GameVersion: Dungeon Master, english,pal,2 disks (main and save). SlaveVersion: Not sure, It's a prebuilt based on the latest whdload install. Dungeon Master starts fine. When you enter the first level (The Hall of Champions) and pick any champion you gain the ability to save the game. When you do so, you notice that you can format a new gamesave disk or save the game directly without having to actually insert a disk in df1 (as the game initially requests of you - you just press ok and the disk is magically there). When you then quit to the title screen of the game, you can click on resume and the game is loaded. All good so far. However, when you quit Dungeon Master to workbench (for example by resetting the system) and start the game anew, you cannot resume the game. The game will keep asking for a save disk to be inserted into df1. The end result is you cannot save your game, a somewhat limiting feature for this kind of game. Note: I looked at the disk.2 file before and after the save action. The sha1sum for it stayed the same, indicating the disk.2 file was not changed which I think would mean the save data actually does not go onto that disk.2 image. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Machine | A500 | ||||||||||||
CPU | 68000 | ||||||||||||
CPUSpeed | 7 | ||||||||||||
ChipSet | OCS | ||||||||||||
GFXCard | None | ||||||||||||
ChipMem | 1 MB | ||||||||||||
FastMem | 1 MB | ||||||||||||
Workbench | OS 3.1 | ||||||||||||
KickROM | 40 - Kick 3.1 | ||||||||||||
KickSoft | Other | ||||||||||||
WHDLoad | 18.3 | ||||||||||||
imported | yes | ||||||||||||
Attached Files |
|
Notes | |
Wepl (manager) 2018-05-31 17:05 |
WHDLoad will normally defers writes to the normal exit. If you reset the Amiga before nothing gets written. So quit using the QuitKey to retry. |
rubin (reporter) 2018-06-04 10:47 |
You are right: quiting using the quit key syncs the cached memory to disk.2. Curious: is it possible to tell whdload to make this kind of access non-cached / synchronuous? |
Wepl (manager) 2018-06-04 10:54 |
Yes, you can use NoWriteCache for this (http://whdload.de/docs/en/opt.html#NoWriteCache) |
Issue History | |||
Date Modified | Username | Field | Change |
---|---|---|---|
2018-05-31 09:34 | administrator | New Issue | |
2018-05-31 09:34 | administrator | Status | new => assigned |
2018-05-31 09:34 | administrator | Assigned To | => JOTD |
2018-05-31 17:05 | Wepl | Note Added: 0006216 | |
2018-06-04 10:47 | rubin | Note Added: 0006217 | |
2018-06-04 10:54 | Wepl | Note Added: 0006218 | |
2018-12-25 22:47 | JOTD | Status | assigned => acknowledged |
2022-12-29 17:56 | JOTD | Status | acknowledged => closed |
2022-12-29 17:56 | JOTD | Resolution | open => no change required |