How Giorgio Cappello Di Paglia Tests Gaming Like It Is 1997 on ZimaBoard 2

Thank you to Giorgio Cappello Di Paglia for using a ZimaBoard 2 retro-gaming build to explore a more interesting question than frame rates alone: could players accustomed to modern guidance still understand and enjoy a game designed like it was 1997?

Games released in the late 1990s did not all follow the same design rules, but many expected the player to pay closer attention, experiment, read manuals, remember routes, manage save points, and accept failure as part of learning.

Modern games often provide a different experience. Objective markers, minimaps, checkpoints, contextual prompts, autosaves, difficulty options, and accessibility settings reduce the chance that a player becomes permanently stuck.

Giorgio’s experiment is not an argument that every old game was better or that modern assistance makes games worse. It examines how the relationship between player and game has changed—and whether older design assumptions still feel natural today.

Watch before reading: The original Italian-language video develops the comparison between 1997 and modern game design before showing ZimaBoard 2 running a Batocera retro-gaming library on a television.

Disclosure: Giorgio identifies the video as a collaboration with Zima and IceWhale. Its description also contains an affiliate link through which he may receive a commission. This article reorganizes the ideas and hardware demonstration presented in his original video while keeping the commercial relationship visible.

This is primarily a game-design discussion and a practical Batocera demonstration. It is not a controlled emulator benchmark, compatibility database, or promise that every console, game, controller, and graphics setting will work identically.

Giorgio frames the project around player expectations: have modern interface conventions changed how we approach older games?

What Playing a Game in 1997 Often Expected From You

Game design in 1997 varied widely across platforms and genres. PC adventures, console role-playing games, first-person shooters, survival horror, racing games, and strategy titles all taught players differently.

However, several expectations appeared more frequently than they do in many current mainstream games:

• Read the printed manual before or while playing
• Listen closely to dialogue for directions
• Remember landmarks instead of following a permanent route marker
• Draw a map or write down codes, puzzles, and objectives
• Save manually or reach a designated save point
• Replay sections after failure
• Experiment with controls and game systems
• Accept that some information would remain unexplained

A player could miss one sentence, enter the wrong room, use an important item too early, or forget to save and lose meaningful progress. The game might provide enough information to continue, but that information was not always repeated or placed permanently on the screen.

This created a stronger demand for observation and memory. It also produced unnecessary frustration when unclear design, poor translation, technical limitations, or inadequate documentation made the intended solution difficult to understand.

Why Older Games Often Provided Less Guidance

The difference was not only philosophical. Hardware and storage limitations shaped what developers could include.

Older consoles and PCs operated with less memory, slower processors, smaller storage media, and lower display resolutions. Developers had less space for spoken tutorials, animated demonstrations, dynamic hint systems, or large collections of interface assets.

Printed manuals therefore carried information that would now appear inside the game. A manual might explain controls, character abilities, inventory rules, background stories, maps, and basic strategies before the player reached the first level.

Developers also designed around an audience familiar with repeated attempts. Arcade traditions, limited lives, passwords, high difficulty, and score-based progression still influenced home games. Replaying a section was frequently part of the expected experience rather than evidence that the game had failed to guide the player.

Modern Players Have Learned a Different Interface Language

Players do not approach a game with no prior knowledge. Years of experience create expectations about how objectives, maps, health, inventory, checkpoints, and interactions should behave.

A modern player may reasonably expect:

• An objective marker pointing toward the next location
• A minimap showing nearby paths and activities
• Highlighted objects that can be collected or activated
• A prompt showing which button performs an action
• An autosave before a dangerous section
• A checkpoint after completing an objective
• A quest log that repeats important dialogue
• A hint system that reacts when progress stops

These features can make complicated games easier to learn and reduce the amount of repeated content. They also make games accessible to players who have limited time, different physical abilities, difficulty reading small environmental details, or trouble remembering information delivered hours earlier.

The tradeoff appears when guidance becomes so persistent that the player no longer needs to study the environment, test ideas, or decide where to go. The interface can begin solving the game before the player has an opportunity to do so.

ZimaBoard 2 Becomes the Platform for the Experiment

Giorgio uses ZimaBoard 2 Mini Home Server to bring the older games into a modern living-room setup.

Its Intel x86 architecture allows it to run operating systems and software designed for conventional PCs. Direct display output connects it to a television or monitor, USB supports compatible controllers, and SATA provides room for a larger local game library.

The same hardware also includes:

• An Intel N150 processor with integrated Intel graphics
• LPDDR5 memory in different configurations
• Onboard eMMC system storage
• Two SATA 3.0 connections
• Two 2.5GbE network interfaces
• Two USB 3 ports
• Mini DisplayPort video output
• PCIe 3.0 ×4 expansion

Those interfaces mean the board does not need to remain a dedicated retro console. The operating system or storage device can be changed, and the same system can return to home-server duties after the gaming experiment.

-15% OFF

ZimaBoard 2 - Mini Home Server for Your Big Idea

Single board computer zimaboard2

$339.00 - $519.00

Buy Now

Retro Gaming Is Only One Possible ZimaBoard 2 Role

Giorgio emphasizes that Batocera represents one project rather than the board’s only purpose. The combination of x86 software compatibility, storage interfaces, networking, and PCIe expansion supports a broader range of builds.

Giorgio presents retro gaming as one branch of a wider platform that can also support storage, media, networking, development, Docker, backup, and alternative operating systems.

This flexibility separates the project from a fixed retro mini console. A dedicated console performs one role well; an expandable x86 server can be reconfigured as the owner’s interests and infrastructure change.

1997 Design and Modern Design Ask Different Questions

Giorgio’s visual comparison summarizes how the relationship between player and game has changed.

The comparison contrasts a player interpreting the game with a modern interface that continuously identifies objectives, routes, actions, and progress.

A 1997-style game often asks, “Did you understand what the world told you?” A modern guided game is more likely to ask, “Can you execute the next objective using the information displayed?”

Neither column describes every game from its period. Some older titles included maps and generous saves, while some modern games deliberately remove objective markers and demand careful exploration. The comparison describes changing conventions rather than an absolute rule.

Modern Assistance Is Not Automatically Bad Design

It is easy to turn this discussion into nostalgia: older games respected players, while modern games explain too much. That conclusion ignores the genuine benefits of current design.

Autosaves protect progress when work, school, family responsibilities, or technical problems interrupt a session. Remappable controls and accessibility settings allow more people to play. Quest logs help when someone returns after several weeks. Optional hints can prevent one unclear puzzle from blocking the rest of a game.

The more useful question is whether the assistance supports the player or replaces the player’s decisions.

Good guidance can be layered:

• The environment provides the first clue.
• Dialogue or a journal preserves important context.
• An optional hint appears only after the player struggles.
• Accessibility settings let the user choose stronger visual guidance.
• Objective markers can be disabled by players who want more exploration.

This gives new players an entry point while allowing experienced players to retain uncertainty, discovery, and problem-solving.

Batocera Turns the Board Into a Living-Room Retro Console

Giorgio uses Batocera, an open-source Linux distribution built around emulation and a controller-friendly game library.

Instead of opening a desktop and launching each emulator manually, Batocera presents supported platforms and games through a unified television interface. Once configured, the system can boot directly into the library and operate primarily from a game controller.

Batocera organizes multiple retro systems and game collections in an interface designed for television and controller use.

Users can follow the official ZimaBoard Batocera arcade setup guide for the current installation workflow. The broader Batocera installation documentation explains supported images, target storage, first boot, and platform-specific requirements.

Game and BIOS Files Remain the User’s Responsibility

Batocera does not provide permission to download commercial games from unauthorized sources. Emulator software, console BIOS files, game ROMs, disc images, artwork, and media metadata have different licensing and copyright conditions.

Users should only add games and system files they are legally entitled to use. Availability on a random download site does not establish that a file is licensed for redistribution.

The official Batocera game and BIOS guide explains where compatible files belong without supplying copyrighted commercial content.

What Performance Should a Retro-Gaming Build Deliver?

Games released around 1997 usually place modest demands on a current Intel N150 system, but emulation performance is not determined by original game age alone.

Each platform requires different emulator behavior. Results can change with:

• The console or computer being emulated
• The selected emulator and emulator core
• Rendering resolution and scaling
• Shaders, filters and visual enhancements
• Controller and audio latency
• BIOS and game-region compatibility
• The accuracy requirements of an individual title
• Background services and thermal conditions

Early cartridge and disc systems are generally more realistic targets than recent consoles. One game launching successfully does not prove that an entire platform’s library will behave identically.

The related ZimaBoard 2 gaming limits across Windows and Linux provide additional context on the Intel N150 integrated graphics without shifting attention away from Giorgio’s retro-game design experiment.

A Simple Living-Room Setup

The final physical arrangement is compact. ZimaBoard 2 sits near the television with power, Ethernet, and display cables attached, while Batocera provides the on-screen game library.

The completed system places the compact ZimaBoard 2 beside the television as a controller-friendly Batocera console.

The Ethernet connection can support game-library management, metadata downloads, updates, and network file transfers. The attached storage can hold the Batocera system and game data, while USB ports connect compatible controllers or other accessories.

A permanent setup should provide open space around the aluminum heatsink. It should also prevent cable tension from pulling the board or attached storage from the shelf.

Can We Still Play Like It Is 1997?

Giorgio’s question is ultimately about learned habits rather than lost ability. Modern players can still understand games built around observation, memory, experimentation, and manual saving. They may simply need time to stop waiting for the interface to provide the next instruction.

The first adjustment is accepting uncertainty. Not knowing where to go immediately is sometimes the intended state. A locked door may be information rather than a barrier. An apparently unimportant conversation may contain the next objective. Failure may reveal how a system works.

The second adjustment is changing how progress is recorded:

• Take brief notes when a character mentions a location or item.
• Check whether the game saves manually, automatically, or only at fixed points.
• Learn the controller layout before entering a difficult section.
• Observe repeated visual and audio cues.
• Use a manual when it was part of the original game experience.
• Allow time for experimentation before searching for a walkthrough.

The difficulty is not always mechanical. The real challenge can be recovering a style of attention that modern interface conventions rarely require.

Who Would Enjoy This ZimaBoard 2 Project?

• Retro-game enthusiasts can centralize several systems in one television-friendly interface.
• Players interested in game design can compare how different generations communicate rules and objectives.
• Families can introduce older games without maintaining several original consoles beside the television.
• Collectors can create a convenient access system for legally preserved personal game libraries.
• Homelab builders can repurpose the same hardware for storage, media, Docker, or networking projects.
• Developers can study how tutorials, checkpoints, maps, and feedback affect player behavior.

Someone interested only in the most demanding modern PC games should choose hardware designed around current gaming performance. This build is more valuable as a flexible retro platform and an exploration of game history.

What Giorgio’s Experiment Demonstrates

Retro Gaming Becomes a Way to Study How Games Teach Us

Giorgio’s project succeeds because it uses old games for more than nostalgia. Playing through Batocera on ZimaBoard 2 creates an opportunity to examine what games expect from their players and how those expectations have changed.

A 1997 game may ask the player to remember, experiment, fail, and try again. A modern game may preserve momentum through checkpoints, markers, contextual prompts, and adaptive assistance. Both approaches can produce meaningful experiences when their guidance matches the intended design.

ZimaBoard 2 makes moving between these generations convenient, while its x86 architecture, SATA storage, networking, and PCIe expansion prevent the hardware from being locked permanently into one entertainment role.

Watch Giorgio’s complete experiment for the original comparison between past and present game design and the final Batocera setup.

If you are building a retro console, testing Batocera, or repurposing ZimaBoard 2 between gaming and home-server workloads, join the ZimaSpace community to share your configuration and compatibility findings.

FAQ

Can ZimaBoard 2 run Batocera?

Yes. Its x86 architecture and direct display output make it suitable for a Batocera-based retro-gaming setup. The installation image, target storage, controller, and emulator configuration must still be compatible.

Can Batocera run games released in 1997?

Many games from that period can run through supported emulators, ports, or compatible PC-game layers. Compatibility depends on the original platform, emulator, required BIOS files, and individual game.

Does Batocera include commercial retro games?

No assumption should be made that commercial game files are included or licensed for free distribution. Users are responsible for obtaining and using games and BIOS files legally.

Can ZimaBoard 2 replace every retro console?

No emulator provides perfect compatibility with every title and peripheral. Original hardware, FPGA systems, or platform-specific emulators may still provide better results for unusual games and accessories.

Can the same ZimaBoard 2 also work as a NAS?

Yes. Its SATA, dual 2.5GbE and PCIe interfaces support storage projects. Users may keep gaming and server environments on separate drives or reconfigure the system, but should back up data before changing operating systems.

Were all games in 1997 difficult and poorly explained?

No. Design varied considerably. Some games included detailed tutorials, maps, difficulty settings, and generous saving systems. Giorgio’s comparison describes broader conventions rather than every release from that year.

Have modern games become too easy?

Not necessarily. Modern guidance can improve accessibility and reduce repetitive frustration without removing mechanical challenge. The effect depends on whether assistance supports player decisions or replaces them.