Welcome, Guest. Please login or register.

Author Topic: WHDLoad saving problem  (Read 3365 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline koshmanTopic starter

  • Sr. Member
  • ****
  • Join Date: Nov 2009
  • Posts: 445
    • Show only replies by koshman
WHDLoad saving problem
« on: December 28, 2009, 09:45:15 PM »
Hi,
I have a problem with saving games in WHDload.I'm sorry if this has been already discussed, but I haven't been able to find the problem described anywhere.
Some games (UFO, SSI Gold Box - Pool of Radiance etc.) run okay, but when I try to save position it behaves strangely - the screen goes dark and then the game screen blinks back for a split second every ~5 seconds and this repeats for a minute or so - 5 seconds of dark screen, game screen blinks back, and immediately another 5 seconds of nothing over and over again. After the minute or more the game returns back to normal, the position is successfully saved and I can continue playing. I'm sure this behaviour is not standard or intended, waiting for a minute or two whenever I want to save is quite tiring. Am I doing something wrong?
My configuration is stock A4000 with A3640, 16MB RAM, CF card as a HDD and registered WHDload 16.8. I don't have any other problems with WHDLoad, e.g. instability or crashes, everything works fine.
Thanks.
- Radim
 
A600 - 68020/33, 10MB RAM, 3.1, 2GB SD
 

Offline Matt_H

Re: WHDLoad saving problem
« Reply #1 on: December 29, 2009, 05:38:43 AM »
That's normal. I think they call it an OS swap. I don't know the technical reason for it, but there is one. Ask the author of the install if there's anything that can be done  - I recall seeing entries in changelogs to that effect.
 

Offline countzero

  • Hero Member
  • *****
  • Join Date: Mar 2005
  • Posts: 1938
    • Show only replies by countzero
    • http://blog.coze.org
Re: WHDLoad saving problem
« Reply #2 on: December 29, 2009, 05:45:08 AM »
Quote from: koshman;535292
I'm sure this behaviour is not standard or intended, waiting for a minute or two whenever I want to save is quite tiring.

it's standard and intended. Your games can't access your HDD natively. WHDload scans their output and puts it into somekind of buffer. Then is switches to OS (to gain access to HDD) and write the buffer contents to HDD.

try running the games from ram:. at least it makes the writing go much faster.:afro:
I believe in mt. Fuji
 

Offline koshmanTopic starter

  • Sr. Member
  • ****
  • Join Date: Nov 2009
  • Posts: 445
    • Show only replies by koshman
Re: WHDLoad saving problem
« Reply #3 on: December 29, 2009, 06:10:03 AM »
Oh, thanks, who would've thought :) Is it because the games expect saving to a save game disk and not HDD?
- Radim
 
A600 - 68020/33, 10MB RAM, 3.1, 2GB SD
 

Offline Vairn

  • Newbie
  • *
  • Join Date: Jan 2008
  • Posts: 26
    • Show only replies by Vairn
Re: WHDLoad saving problem
« Reply #4 on: December 29, 2009, 08:57:03 AM »
Yup, it is the same reason games have the preload flag, otherwise you would get the same effect when it tries to read data from the harddisk. Flashy flash flash.  therefore, we tell it to load all game data into memory first.
 

Offline mailman

  • Full Member
  • ***
  • Join Date: Nov 2003
  • Posts: 109
    • Show only replies by mailman
    • http://www.ppa.pl
Re: WHDLoad saving problem
« Reply #5 on: December 29, 2009, 09:03:33 PM »
Good thing is that when the save file is being overwritten there are no OS swaps. In that situation a "real" file saving occurs after quitting the game.
 

Offline koshmanTopic starter

  • Sr. Member
  • ****
  • Join Date: Nov 2009
  • Posts: 445
    • Show only replies by koshman
Re: WHDLoad saving problem
« Reply #6 on: December 29, 2009, 10:37:38 PM »
Well, that would be nice, but unfortunately in my case (Pool of Radiance) the swapping still occurs even when I'm overwriting a previously saved game. Any ideas why it's so?
- Radim
 
A600 - 68020/33, 10MB RAM, 3.1, 2GB SD
 

Offline Matt_H

Re: WHDLoad saving problem
« Reply #7 on: December 29, 2009, 11:11:12 PM »
That's just the way it is, unfortunately. The author of the install might be able to optimize, but I don't think there's anything that can be done from the user side.