Snes9x.com

this can happen if the save directory is unwritable by snes9x; this is more likely to happen if you put snes9x in Program Files. note that just because *you* have write access to a location, that doesn't mean that all programs do. try defining a save location that will definitely be writable by all ...

I had issues with the link upthread, but this link worked for me on Win10 x64 version 1803.

in SNES9X EX, SRAM and freeze files are stored in the ROM directory.

two requests for OV2:

• use YYYYMMDD for dates in your filenames so alphabetical sort is useful
• create a sticky with a link to your testbuilds

they're located in the same directory as the ROM image.

it may work if you use retroarch with the snes9x core (assuming retroarch hasn't reinvented the wheel when it comes to different cores' savestates). it can't hurt to try.

in general, though, you're better off using battery saves if you're moving between different emulators.

minor ux/ui issue in the Windows build, not sure if present in gtk. under File -> Load Game Position and File -> Save Game Position, the "Select File" options at the bottom of the list should be followed by an ellipsis ("Select File...") as choosing that option produces a dialog.

snes9x creates a savestate named [romname].oops when unloading a ROM (including during shutdown). if you: 1. closed snes9x or switched ROMs anytime between creating that savestate you accidentally loaded and actually reloading said savestate, and 2. HAVEN'T closed snes9x or switched ROMs after makin...

quite frankly, i was unaware that snes9x could use zipped sram; i was talking about the ROM image itself. if the sram is zipped, i would extract that as well. regardless, there's little practical reason to have everything zipped; this isn't 20 years ago where the amount of space taken by ROM images ...

it also sounds like it's a new lower-end laptop with a crappy keyboard and touchpad.

for all the hassle, you're better off just unzipping that rom file.

either:

• 1) the save path isn't what you think it is (and therefore the sram isn't where snes9x is looking)
  2) the rom is zipped, the rom filename and zip filename are not the same, but you renamed the sram to match the zip filename (meaning sram filename doesn't match rom)

So are you saying that if my save is called "NBA Live '96 (USA)," the corresponding game must also be called "NBA Live '96?" If the save is "NBA Live '96 (USA)" then the game must also be "NBA Live '96 (USA)" - keep in mind this is likely based on the ROM fil...

First, make sure your old save files are where snes9x expects them to be. Check the save path listed in snes9x under Emulation -> Settings.

Second, make sure your filenames match (e.g. if you're playing game.smc, the battery save file must be named game.srm).

do you have the BIOS file in the path defined under Settings?

look for your folder under /storage/emulated/0

in SNES9x EX (and many other apps), the internal storage shows up as /storage/emulated/0/

a physical SD card should also show up in /storage; on my tablet (using Nougat) it's listed by a 8 hex digit string in the format HHHH-HHHH.

so, your ROMS folder should be found at /storage/HHHH-HHHH/ROMS

don't add .00# to the end; replace .oops with .00# and then make sure the file is in the same folder as your other save states.

is your display set for a 50Hz refresh rate?

it won't be a BIOS file issue; the SNES has none.

fmod is an audio library; you won't hurt anything by trying to run snes9x without it. if snes9x fails or you have audio issues, grab a copy of the file from a previous release (which seems to be how everyone else has unintentionally done it, assuming we've been installing to the same location as a p...