Browsed by
Month: May 2014

sd2snes in heat

sd2snes in heat

Just a little fun post inbetween. Ingo Korb of sd2iec fame (that’s the project that got me started on sd2snes in the first place!) had the chance to take thermal images of a running SNES+sd2snes. Some people, including myself, found that the sd2snes gets quite hot in the SNES. However the heat actually comes from outside the sd2snes, that is from inside the cart slot! The SNES’s linear voltage regulator produces a lot of heat that gets radiated into the cartridge slot (among other places).

thermal image of an SNES+sd2snes - top view
Top view – SNES cauldron!
thermal image of an SNES+sd2snes - rear view
Rear view

These images illustrate it quite nicely. There are little hotspots where the chip dice are but most of the heat comes from below / behind.

Database creation and file browsing – Request for comments

Database creation and file browsing – Request for comments

This is a little call for feedback. In order to simplify the general usage of file lists – such as ROM lists, cheat lists, skin lists… – in terms of programming I would like to generalize directory access.

The sd2snes currently scans the entire card on startup and rebuilds an internal database if any change to relevant card contents is detected. This takes place so the file browser can always show the current state on card. Said database contains the entire directory structure and takes up quite some “ROM” space. I would like to replace this “deep scanning” by a simple “list a single directory” function which can also be used to list other kinds of files under different circumstances. This would mean that a folder will be loaded on the fly when you open it, instead of all folders being preloaded at startup.

The current state of implementation has one advantage: browsing the card is fast. There are no delays when changing directories.
The downside is that you have quite a lengthy “Loading …” screen at bootup because of the full card scan. And if something is added/removed/renamed the database rebuild can take a long time.

The advantage of proposed on-the-fly file list creation is that there is almost no loading time at startup. I could even ax the “Loading …” screen altogether. There will be no lengthy “rebuilding database …” either every time you change something on card. Files could easily be manipulated on the fly, too – some people asked for a file deletion feature – without having to rebuild the entire database. Also the database creation code is a complex mess and I want to get rid of it… ;)
The disadvantage is that there will be slight delays while browsing (as a folder is read and sorted on demand) – if a single folder contains several thousand files this can amount to a few seconds.

So um, would you mind if I changed file handling to the latter?

This site uses cookies. You need to accept cookies to use the comment feature and view embedded media. See Privacy Policy for more details.

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.