Fuse Emulator - Saving Snapshots

[PeterJ]

Hi,

I'm often (but not always) getting this message when saving Snapshots in Fuse:



I'm unable to load these files back into Fuse.

On the occasions I can save snapshots without errors, whilst I can load them back into Fuse, when I try and load them into Spectaculator I get this:



Any idea what I'm doing wrong? I'm using machine type Spectrum 128K.

Thanks

[djnzx48]

Do you have any peripherals attached? And are you using .szx format for saving?

[PeterJ]

Do you have any peripherals attached? And are you using .szx format for saving?

Hi,

Hi, no peripherals, and just .sna

Peter

[djnzx48]

If there isn't any particular reason you need snapshots in .sna format, I would try .szx instead. The .sna format is probably too limited for the machine configuration you're using.

[Guesser]

Any idea what I'm doing wrong? I'm using machine type Spectrum 128K.

The sna format doesn't officially support the Spectrum 128

[Pegaz]

It also supports Pentagon 128k.

[PeterJ]

Thanks [mention]Guesser[/mention] and [mention]djnzx48[/mention]. Just out for walk, will try when I get home.

[PeterJ]

Thanks! That resolved the issue.

[Seven.FFF]

I was curious about this, so I looked it up in the Fuse source.

It automatically emits this warning when you snapshot a +2A, +3, Pentagon, TC2048 or TC2068 model. 16K, 48K, toastrack and +2 grey don't get the warning. So you may not have been in the model you thought you were.

The warning is correct - all those models have features that aren't part of the SNA specification. Although Pentagon is a grey area, as there are several paging schemes and this snapshot code doesn't distinguish between them.

But for most games we're concerned with the +2A and +3 far more than the other models. The only thing really not snapshottable for +2A and +3 is the All-RAM mode, which almost no commercial software uses. So in the vast majority of cases, the snapshots should load and run fine.

[PeterJ]

[mention]Seven.FFF[/mention],

Thanks for testing. I double checked and I'm most definitely on Spectrum 128K. That is the one I always used.

Please see below when saving as .sna




Peter

[dfzx]

Fuse (well, libspectrum) spits out that error from this switch:

Code: Select all

  case LIBSPECTRUM_MACHINE_128:
  case LIBSPECTRUM_MACHINE_128E:
  case LIBSPECTRUM_MACHINE_PENT512:
  case LIBSPECTRUM_MACHINE_PENT1024:
  case LIBSPECTRUM_MACHINE_PLUS2:
  case LIBSPECTRUM_MACHINE_PLUS2A:
  case LIBSPECTRUM_MACHINE_PLUS3:
  case LIBSPECTRUM_MACHINE_PLUS3E:
  case LIBSPECTRUM_MACHINE_SCORP:
  case LIBSPECTRUM_MACHINE_SE:
    *out_flags |= LIBSPECTRUM_FLAG_SNAPSHOT_MAJOR_INFO_LOSS;

So the 128K machine will definitely produce it.

There's a lot of peripherals and other stuff checked too, so a lot of hardware emulation permutations will result in it as well.

[Seven.FFF]

Ha, I was looking at a different version of the code.

Code: Select all

   case LIBSPECTRUM_MACHINE_TC2048:
   case LIBSPECTRUM_MACHINE_TC2068:
     *out_flags |= LIBSPECTRUM_FLAG_SNAPSHOT_MAJOR_INFO_LOSS;
     /* Fall through */
   case LIBSPECTRUM_MACHINE_16:
   case LIBSPECTRUM_MACHINE_48:
     error = write_48k_sna( buffer, &ptr, length, sp, snap );
     break;
     
   case LIBSPECTRUM_MACHINE_PLUS2A:
   case LIBSPECTRUM_MACHINE_PLUS3:
   case LIBSPECTRUM_MACHINE_PENT:
     *out_flags |= LIBSPECTRUM_FLAG_SNAPSHOT_MAJOR_INFO_LOSS;
     /* Fall through */
   case LIBSPECTRUM_MACHINE_PLUS2:
   case LIBSPECTRUM_MACHINE_128:
     error = write_128k_sna( buffer, &ptr, length, snap );
     break;

[Spezzi63]

I'm often (but not always) getting this message when saving Snapshots in Fuse:



I'm unable to load these files back into Fuse.

Hi,
you should save the snap file without extension.
Fuse should be able to load this file using drag and drop.
You can also add the extension by renaming it if you want.
greetings

[zxcygnus]

you should save the snap file without extension.
Fuse should be able to load this file using drag and drop.
You can also add the extension by renaming it if you want.
greetings

I am using Fuse-emulator in Linux console and sometimes is drag&drop really inconvenient (because window manager or because i just don't have opened window with some "explorer" equivalent in right folder, i rather work with mc in text console than any clickable file browser).

Mostly i am using built in file browser in Fuse itself. But if i save snapshot without extension, it will be saved without extension on hard drive too (in format ZXST). So it will not be in list of supported files in open dialog when i am trying open snapshot. Even more weird is, Fuse is not displaying snapshots with zxst extension too. I must always select "all files" instead "supported files" which is kinda annoying.

I don't understand - sna files are in open dialog visible, but sna files are not able store perfect snapshot. Zxst are not visible, but works better and are default/recomended.

Does it mean i should use another extension for ZXST files? Or is it bug in Fuse?

I know about this problem long time and even latest SVN version does it (r5829-trunk).

[Ast A. Moore]

Does it mean i should use another extension for ZXST files? Or is it bug in Fuse?

I don’t know if Fuse uses different extension under Linux, but the proper snapshot file extension is szx, not zxst.

[zxcygnus]

Does it mean i should use another extension for ZXST files? Or is it bug in Fuse?

I don’t know if Fuse uses different extension under Linux, but the proper snapshot file extension is szx, not zxst.

Fuse doesn't use different extension, but it didn't adding extensions automatically either. Which is confusing. I just tried guess it from first four letters in snapshot. I think, bug is - Fuse emulator should add default extension if not specified by user, or display all files by default. Otherwise saved snapshots just are not visible (both - with wrong extension or without it).