# Emulators on DevTerm and their issues

**URL:** <https://forum.clockworkpi.com/t/emulators-on-devterm-and-their-issues/8228>\
**Category:** Emulators\
**Created:** [March 26, 2022, 8:05am UTC](https://forum.clockworkpi.com/t/emulators-on-devterm-and-their-issues/8228 "2022-03-26T08:05:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sleeps\_darkly](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/sleeps_darkly/32/6150_2.png) [@sleeps\_darkly](https://forum.clockworkpi.com/u/sleeps_darkly)\
**Post date:** [March 26, 2022, 8:05am UTC](https://forum.clockworkpi.com/t/emulators-on-devterm-and-their-issues/8228/1 "2022-03-26T08:05:03Z")

</div>

So, I’ve been looking into the emulators on the stock A06 operating system and had the following findings.

At this moment repositories have two available aarch64 emulators, both quite outdated:

- RetroArch 1.9.3
- Mednafen 1.26.1

They basically run fine, but the main issue happens when trying to run SNES games on both: they both crash with `longjmp causes uninitialized stack frame` error. Of course, looking that both published aarch64 packages predate the DevTerm and A06 core, I compiled the [recent 1.29](https://mednafen.github.io/releases/) release, and it finally ran. It took almost 1.5 hours though.

But I’ve found an yet another problem with it.

I run DevTerm with 1.3x display scaling, because 1x scaling is too big and a lot of windows just don’t fit into standard 1280x480. However, 1.3x scaling causes issues with fullscreen scaling in both versions of Mednafen on any emulation core:

 ![IMG_7547](https://canada1.discourse-cdn.com/flex029/uploads/clockworkpi/original/2X/e/eeeaec5534414d411718ae9650252fae3da5e5e3.jpeg)

Dropping the scaling to 1x fixes the issue and fullscreen works good, however the desktop becomes uncomfortable to use due to windows being too big.

Any possible suggestions what I can use? I need a SNES emulator that I can use on DevTerm in fullscreen mode. I suppose I can try building latest Retroarch 1.10.2 because it will take care of issue there too, but it will also take _a lot_ of time…
