[Openmsx-bugs] [ openmsx-Bugs-1188581 ] Debian 305991: write SRAM files synchronously (no buffering)

[SourceForge.net <no...@so...>]

Bugs item #1188581, was opened at 2005-04-23 15:52
Message generated for change (Comment added) made by manuelbi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=421861&aid=1188581&group_id=38274

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General/misc
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Manuel Bilderbeek (manuelbi)
Assigned to: Wouter Vermaelen (m9710797)
Summary: Debian 305991: write SRAM files synchronously (no buffering)

Initial Comment:
See this bug report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=305991

Additionally: the same goes for the printerlogger. If
it is output directly to the file, it is much more
usable (e.g. when exporting MSX Basic programs to the
host OS via LLIST).

----------------------------------------------------------------------

>Comment By: Manuel Bilderbeek (manuelbi)
Date: 2005-06-20 23:14

Message:
Logged In: YES 
user_id=78178

This is implemented now. Thanks Wouter!

----------------------------------------------------------------------

Comment By: Manuel Bilderbeek (manuelbi)
Date: 2005-06-19 17:11

Message:
Logged In: YES 
user_id=78178

SRAM syncing is implemented by Wouter. It syncs after
maximum 5 seconds after the last write.

The printer logger does not sync yet. I'm leaving it open
for that.

----------------------------------------------------------------------

Comment By: Patrick van Arkel (vampier)
Date: 2005-05-07 22:55

Message:
Logged In: YES 
user_id=887021

Write S-RAM to disk

proc save_game_master2_sram {filename} {
set chan [open $filename w]
  set mem [debug read_block Konami's\ Game\ Master\ 2\ 
SRAM 0 0x1000]
	puts $chan $mem
  close $chan
}

I guess i could use the debugable too to put it back into the s-
ram. Even an [after time X [event]] could be used to output it 
every second or so.

The best solution would be save states ;) 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=421861&aid=1188581&group_id=38274