ZSNES 1.42: Save slots INOP

gauveldt · Post by **gauveldt** » Tue Jun 27, 2006 8:17 pm

[I've posted this here because the bugzilla site doesn't seem to be able to send me email so I can't open an account there.]

Save slots do not seem to be working:

1. Select any save slot >0 (F3) and snapshot (F2) the game.

2. Use key shortcuts or the dialog to change the save slot
to 0 (F3) and save the game in a different place.

3. Move somewhere else in the game different from the saves in steps 1 and 2 above.

4. Go back to the slot used in step 1 above and load the state (F4). Game loads state saved in slot 0.

I think the slot number is being ignored. :(

Also saving in slots >0 does not turn the background behind the slot saved to orange in the Slot Select menu (F3).

Game used at time of discovery:
TOP ENGLISH (C) DEJA
TYPE:NORMAL
INTERLEAVED:NO
BANK:EHI
CHKSUM:OK
VIDEO: NTSC
CRC32:14612848

My system:
AMD AthlonXP 2900
1GB SDRAM
Linux nall 2.6.8-2-k7 #1
Tue Aug 16 14:00:15 UTC 2005 i686
GNU/Linux
Debian SARGE Linux

build: ZSNES V1.42 (2006.06.21)

output (when not run as: zsnes ... &>/dev/null &)
ZSNES v1.42 (c) 1997-2005, ZSNES Team

Be sure to check http://www.zsnes.com/ for the latest version.
Please report crashes to zsnes-devel@lists.sourceforge.net.

ZSNES is written by the ZSNES Team (See AUTHORS.TXT)
ZSNES comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions;
please read 'LICENSE' thoroughly before doing so.

Use ZSNES -? for command line definitions.

MMX support found and enabled.

File opened successfully!
ZSNES could not find any joysticks.

spoon0042 · Post by **spoon0042** » Tue Jun 27, 2006 8:49 pm

Things tend to break when you load a rom from the command line.

Try not doing that (use Game -> Load instead). Also try a WIP or SVN build.

gauveldt · Post by **gauveldt** » Tue Jun 27, 2006 11:37 pm

spoon0042 wrote:Things tend to break when you load a rom from the command line.

Try not doing that (use Game -> Load instead). Also try a WIP or SVN build.

Wouldn't that, too, be a bug and not a feature?

Post by **grinvader** » Wed Jun 28, 2006 9:17 am

Bug reports from a 18-month-old version aren't considered, especially since we're almost done fixing the directory hell.

gauveldt · Post by **gauveldt** » Fri Jun 30, 2006 9:30 pm

grinvader wrote:Bug reports from a 18-month-old version aren't considered, especially since we're almost done fixing the directory hell.

There is still issues when the ROM is specified on the command line
This is a real bummer since KDE can only run associations by passing the file over the command line.

gauveldt · Post by **gauveldt** » Fri Jun 30, 2006 9:32 pm

gauveldt wrote:
grinvader wrote:Bug reports from a 18-month-old version aren't considered, especially since we're almost done fixing the directory hell.
There is still issues when the ROM is specified on the command line
This is a real bummer since KDE can only run associations by passing the file over the command line.

PS: Using SVN Revision 3415

Deathlike2 · Post by **Deathlike2** » Fri Jun 30, 2006 10:17 pm

Until we say it is fixed.. it's not fixed yet.

gauveldt · Post by **gauveldt** » Fri Jun 30, 2006 10:40 pm

Deathlike2 wrote:Until we say it is fixed.. it's not fixed yet.

So the above is a known and still-open bug then?

Deathlike2 · Post by **Deathlike2** » Fri Jun 30, 2006 10:49 pm

Obviously.. if you didn't figure it out sooner.

gauveldt · Post by **gauveldt** » Fri Jun 30, 2006 10:56 pm

Deathlike2 wrote:Obviously.. if you didn't figure it out sooner.

grinvader's response left me unsure

Deathlike2 · Post by **Deathlike2** » Fri Jun 30, 2006 11:10 pm

Please reread what he said. What he meant was that it is almost fixed.

gauveldt · Post by **gauveldt** » Fri Jun 30, 2006 11:45 pm

Deathlike2 wrote:Please reread what he said. What he meant was that it is almost fixed.

I was more referring to the part about the report not being considered, which was why I checked out from SVN and when I still had the problem I posted updated information so that I wasn't using "an 18-month old version".

I understand that the problem is not fixed and I only ammended the report to indicate the indicated SVN revision still had the issue only to address the "using an 18-month old version" point.

Actually it's worse in that the cursor boxes on the pick state window draw out of the window and other nonsense occurs when the ROM is specified on the command line. Are there like some unchecked pointers going on when the ROM is specified on the command line (perhaps becuase the GUI doesn't get a chance to start up). The uninitialization thing is speculation but there are some real wierd stuff going on in ZSNES when the ROM is on the command line.

Maybe the GUI should activate momentarily, then the config loaded and the command line options parsed?

Post by **grinvader** » Tue Jul 04, 2006 11:38 am

gauveldt wrote:Maybe the GUI should activate momentarily, then the config loaded and the command line options parsed?

Not possible, since a command line param disables the gui altogether.