Identify the signal and hardware
Record the video card, output connector, monitor and any converter. A connector's resemblance to another standard does not establish compatible signals. Historical PC displays can require different scan rates and sync arrangements. Use the card and monitor manuals before choosing an adapter, particularly with an analogue display whose supported timing is limited.
Start with a known compatible text or graphics mode. Do not interpret a blank unsupported mode as a failed motherboard. For emulation, record the selected video adapter and display options. The 86Box project documentation describes emulated hardware; an emulated adapter choice is not a wiring guide for a physical socket.
Configure sound from the actual resources
Identify sound-card model, driver and configured I/O, interrupt and DMA resources where applicable. Keep jumper settings or configuration-program output in the machine record. Use values from that hardware, not a universal example copied from another PC. Resource conflicts can prevent sound even when a game appears to detect a card.
The DOSBox-X sound-card reference explains its emulated audio devices. The MIDI guide covers a separate music-output workflow. Digital effects, FM synthesis and MIDI music should be tested separately; enabling one does not guarantee the others use the same device or output path.
Use the game's configuration tool
- Read the game's supported video, audio and input requirements.
- Retain its existing configuration before changing settings.
- Select the actual or emulated sound device and resource values.
- Run available music and effects tests separately.
- Test gameplay after setup, not only the setup program.
- Record the working configuration with the game edition.
A game may use different music and effects devices. Keep those choices explicit. If sound works in setup but fails during gameplay, record the exact transition, memory configuration and driver arrangement. Do not replace a card simply because a title uses different resource expectations from another game.
Check input and timing independently
Identify the keyboard layout, mouse driver and joystick interface. Use the game's calibration routine where required. A USB controller working on a modern host does not prove that an original game port sees the same device. For emulation, preserve the host mapping and emulated device type separately.
CPU speed can affect software designed around historical timing. The DOSBox-X game guide includes troubleshooting for its environment. Begin with one recorded configuration and change one timing or compatibility option at a time. A game that needs a particular setting should have that setting documented rather than labeled generically compatible.
Preserve the working state
Keep driver versions, setup files, boot configuration and resource assignments with the game record. Recheck after a cold boot and test another application using the same device. Use a simple baseline before adding capture hardware, audio mixers or several adapters. See DOS setup for a controlled environment and software preservation for archiving dependencies.