Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesMost PC-98 problems in emulation come from using the wrong machine profile, an unsuitable font or video mode, a title-specific sound BIOS requirement, or a host-key mapping that does not match the game. Start by recording your emulator and version, the game title, and the exact symptom. The steps below use DOSBox-X because its PC-98 settings are documented; an original NEC PC-9800 computer needs different hardware-level diagnosis.
Start by identifying the layer that is failing
PC-98 troubleshooting is easier when you separate three layers: the emulated computer, the game’s own hardware expectations, and your host keyboard or controller. A setting that fixes one layer can leave another untouched. For example, changing a keyboard binding cannot repair missing FM audio, and loading a Japanese font will not correct a bad graphics clock.
As an Amazon Associate I earn from qualifying purchases.
- Emulator layer: machine type, ROMs, video timing, sound device, keyboard layout and mapper bindings.
- Game layer: the title’s expected PC-98 generation, sound board, display mode, timer behavior and control scheme.
- Host layer: your physical keyboard, operating-system layout, joystick or gamepad and the keys assigned by the mapper.
Write down the emulator name and version, the game title and disk-image format, and whether the symptom is no sound, incorrect sound, corrupted graphics, unreadable Japanese text, misplaced keys or completely unresponsive controls. DOSBox-X documentation is strongest for DOSBox-X itself; options and defaults can differ in other emulators and in different DOSBox-X releases.
Free tools Windows power users keep installed
One-click scans. No signup required.
Confirm PC-98 mode before changing anything else
DOSBox-X does not use PC-98 hardware by default. The IBM-compatible DOS profile and the PC-98 profile emulate different machines, so generic DOSBox advice—especially Sound Blaster instructions—may be wrong for a PC-98 title.
#1 Best Overall
- With broad game support, the Logitech Gamepad F310 works with old standbys to today's biggest titles, so it's easy to set up and use with your favorite games.
- Profiler software allows the gamepad to be programmed to perform keyboard and mouse commands for games without gamepad support.* * Requires software installation.
- A familiar control layout that doesn't require a learning curve to be able to use, with all the same buttons as on an Xbox 360.
- The unique floating D-pad rests on four switches-instead of a single pivot point-making it responsive to quick changes in direction.
- The six-foot cord lets you lean back and play a comfortable distance from your PC monitor.
Set the machine type
- Open the DOSBox-X configuration file used for the game, or start DOSBox-X with a temporary configuration you can inspect.
- In the machine setting, select
machine=pc98. DOSBox-X also documentspc9801andpc9821as aliases. - Restart DOSBox-X after saving the change. A machine-type change affects the emulated BIOS and hardware, so changing it during a running session is not a reliable test.
Once PC-98 mode is active, use the image format expected by the title. DOSBox-X’s PC-98 guidance commonly refers to hard-disk images such as HDI and floppy images such as FDD. An IMG file made for ordinary IBM-PC emulation is not automatically the right image for a PC-98 game. Mount the image using the method documented for your DOSBox-X release, then verify that the game starts before diagnosing audio or graphics.
Do not mix profiles while testing
Change one relevant setting at a time and restart the game after each change. If you switch the machine type, sound device, font and video mode together, a successful launch will not tell you which change mattered, and a new failure will be difficult to undo. Keep a copy of the original configuration so you can return to known defaults.
Why is there no sound in my PC-98 game?
PC-98 audio is not one universal device. A title may use PC-98-specific BIOS behavior, an FM sound board, the PC-98 Sound Blaster 16 emulation, or the PC speaker. DOSBox-X therefore exposes PC-98 options that do not map directly to the settings used by an IBM-compatible DOS game.
Try the PC-98 sound BIOS option
- With
machine=pc98confirmed, open the PC-98 sound settings in DOSBox-X. - Locate the
pc-98 sound biosoption and enable it as a targeted test when a game has no sound or initializes its audio incorrectly. - If you have a legitimate dump from an actual PC-98 system, configure the documented
SOUND.ROMfile and restart the emulator. - Test the same scene or sound check in the game. If nothing changes, restore the previous value before trying a different device or timer setting.
DOSBox-X documents these as compatibility checks, not requirements for every game. A missing SOUND.ROM is not proof that the emulator is broken, and enabling the BIOS option cannot make a title use a sound board it was never written to support.
Rank #2
- Wide Compatibility: VOYEE wired 360 controller compatible with Microsoft Xbox 360 & Slim/ PC (Windows 11/10/8.1/8/7). Just plug and play, not for FPS games
- Enhanced Game Controller: Upgraded PC 360 controller with new left and right trigger buttons and more sensitive joysticks and buttons - Respond quickly to player commands without delay
- Astonishing Gaming Experience: VOYEE wired pc controller provides rumble control and according to the game automatic vibration feedback to enhanced game experience and match your personal preference
- Ergonomic Design: Grips's contours have been designed to fit your hands more comfortably to hold for a long time and 7.2ft cord allows greater
- What You Get: VOYEE wired 360/PC Controller, 45 Days Money Back, 365 Days Guarantee Against quality defect and 24 Hours Friendly Customer Support
Check the device the game actually expects
If the title specifically offers PC-98 Sound Blaster 16 support, use the PC-98 address range documented by DOSBox-X: I/O addresses from D2h through DEh. The same documentation explains that an IRQ value of 0 represents IRQ5 in PC-98 mode. Enter the values expected by the game’s setup program rather than copying an IBM-PC Sound Blaster address and IRQ.
This branch applies only when the game uses that emulated device. Changing to Sound Blaster 16 will not repair audio generated by an FM board, and forcing an address that the title does not expect can remove sound that previously worked. If the game has a hardware-selection screen, note the selected board and use that information when choosing DOSBox-X’s device.
Use the timer option only for a title-specific symptom
DOSBox-X’s full configuration reference includes pc-98 timer always cycles. It selects behavior resembling a PC-9801 or a PC-9821, and some older games require the PC-9801-like behavior. Treat this as an advanced check for timing-sensitive audio, speaker behavior or a game that hangs while initializing sound—not as the first general audio fix.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Confirm that the game is old enough or documented as requiring PC-9801-style timing.
- Change only the timer option.
- Restart the game and test the same audio event.
- Return to the prior value if the title becomes less stable or the symptom is unchanged.
Separate emulator audio from game audio
- Confirm that your operating system is sending sound from DOSBox-X to the intended output device.
- Check whether the game has its own volume, mute or hardware-selection menu.
- Test a second known audio event in the same title. A silent opening scene may be normal, while a sound-test menu should produce a repeatable result.
- Do not infer that a working MIDI or PC-speaker effect proves the FM or Sound Blaster device is configured correctly; they are different paths.
Why are the graphics corrupt, blank or the wrong size?
First decide whether the problem is character rendering or the graphical display mode. Japanese Kana/Kanji that appear as blocks, empty boxes or unreadable symbols usually indicate a font problem. Missing sprites, wrong colors, a blank screen or a distorted picture point more often to a video mode, timing or title-specific hardware quirk.
Rank #3
- 【Supported Operating System】The Game Controller is specifically designed for playing classic old school retro snes games on computer or laptop. Compatible with Windows 98 / ME / Vista / 2000/2003 / XP / 7 / 8 / 8.1 / 10/11, Mac OS X/ OS X 10.0 and beyond, Raspberry Pi, Raspberry PI 2 model B,Model A, Raspberry Pi 1 Model B+, Raspberry Pi 2,Raspberry Pi OS, Raspberry Pi 3 Model B+, Raspberry Pi 3, Raspberry Pi Zero.
- 【Simple USB Plug and Play】If your program or application accepts USB controller input, this classic game controller do not need install drivers or patches. 1.5 meter external cable(approx. 5 ft. Long). Notice: Please download the game emulator first before start the games, and then you must manually set the buttons and directionals within the emulator you're using, and the controller not automatically assigns buttons/directional axes. If on the Steam platform, you need to first enable Steam's "Universal Controller Configuration Support" and then restart Steam. After entering the game, you also need to manually bind key positions in the game
- 【High Sensitivity without Delay】Super sensitive buttons for precision control: 6 fire buttons, a 'Start' button and a 'Select' button, motion control cross. Play your favorite old school games with classic retro feel. Fits perfectly in the hand and also perfect for two player action.Note: Not applicable to Switch/PS games. Not Compatible with TV/ TV Box, third Mini Games Box and Tesla Model 3
- 【Supported Game Emulators】The game controller works with most emulators. Download any emulator you wish to download and use from Google and do the same with ROMS. Notice:Third party controller, not original controller. But it works phenomenal with the Raspberry Pi game emulation and so on
- 【Product Service】If you have any problem during use, send message to us and we will help you to solve the problem soon
Install and select a suitable PC-98 font
- Check whether the game displays Japanese text correctly in menus, not just whether the title screen appears.
- If characters are missing or illegible, configure a PC-98 font file in DOSBox-X. The PC-98 guide documents
FONT.ROMand other supported font formats. - Use a font intended for PC-98 text rather than assuming a modern system font is interchangeable.
- Restart DOSBox-X and test a menu containing both Kana and Kanji.
A font file fixes character glyphs; it does not repair a broken graphics mode. Keep those tests separate so that you know whether the remaining defect is text rendering or video hardware emulation.
Begin with the documented video defaults
DOSBox-X documents 24 kHz as the best-supported PC-98 video mode. It says that 15 kHz is not implemented and that 31 kHz is experimental. If a title displays a blank screen or unstable output, start from the default rather than forcing an experimental frequency. The support status is important: an option being present in a configuration reference does not mean every game or host display will handle it identically.
| Video mode | Documented status | How to use the information |
|---|---|---|
| 24 kHz | Best-supported default | Use as the baseline when diagnosing a game-specific display problem. |
| 15 kHz | Not implemented | Do not select it as a repair for a title that expects this hardware mode. |
| 31 kHz | Experimental | Try only when the game or a known configuration calls for it, and record that the result may vary. |
Check GRCG, EGC and GDC behavior
PC-98 games can use specialized graphics hardware. DOSBox-X documents GRCG and EGC support and says their default settings are enabled. It also provides a GDC clock option: some games may need 2.5 MHz behavior, while few require 5 MHz. Because the required value is title-specific, do not disable or change both chips and the clock at once.
- Restore GRCG and EGC to their documented defaults.
- Find out, from the title’s setup notes or compatibility information, whether it expects a particular GDC clock.
- Change only the clock setting if there is evidence for 2.5 MHz or 5 MHz behavior.
- Retest the same screen, animation or transition that exposed the glitch.
Allow for hardware quirks in older titles
DOSBox-X’s reference explains that graphics are nominally documented for two display partitions, while some games depend on hardware flaws that effectively allowed four. That behavior is a compatibility issue rather than a setting that can be prescribed for every game. If only one title has a reproducible corruption while other PC-98 software is correct, record its generation, display mode and exact scene before changing broad emulator defaults.
Rank #4
- Universal Multi-Platform Compatibility: Works seamlessly with Windows PC, Switch/Switch 2, Android, and iOS via USB-C, 2.4G wireless (1000Hz), or Bluetooth (125Hz). Note: Not compatible with X-box, Play-Station, Luna, or GeForce
- Ultra-Quiet Silent Gaming: Silicone-damped buttons for whisper-quiet operation. Perfect for late-night gaming without disturbing family or roommates. All buttons redesigned for silent play—ABXY, D-pad, triggers, and function keys
- Hall Effect Precision Technology: Drift-free 11-bit Hall Effect joysticks with 1000Hz polling rate in wired/2.4G modes for ultra-fast competitive response. Bluetooth mode offers 125Hz for mobile gaming. Long-lasting durability guaranteed
- Advanced Trigger & Programmability: Dual-stage adjustable triggers with 2+2 rumble motors for realistic feedback. Two top-mounted programmable buttons avoid accidental presses—solving common back-paddle issues for competitive advantage
- Ergonomic Comfort & Endurance: Sweat-resistant silicone grip for marathon sessions. 1000mAh rechargeable battery for extended play. Upgraded 8-way D-pad with dome switches delivers precise diagonal control for fighting and retro games
Why is Japanese text wrong even though the graphics work?
Text and graphics can fail independently. A game may draw sprites and backgrounds correctly while Kana or Kanji is missing because no suitable PC-98 font is loaded. Conversely, a correct font cannot fix a blank screen caused by an unsupported video frequency.
Use a symptom checklist
- Only Japanese characters are wrong: inspect the font file and font format.
- Menus and sprites are both corrupted: investigate video mode, GRCG/EGC and GDC settings.
- Text is shifted or clipped after changing frequency: restore 24 kHz and retest before touching font settings.
- One title fails while another uses the same font: treat the game’s display mode or generation as the likely difference.
Why do my keyboard controls not match?
A key can be misplaced for two different reasons: DOSBox-X may be interpreting the host keyboard with a different layout, or the emulator may receive the key correctly while the game expects another control. Diagnose layout first, then inspect the mapper.
Check Japanese versus U.S. keyboard layout
DOSBox-X can detect Japanese and U.S. layouts. Its current guide describes forcing an IBM/U.S. layout when required and notes that this works only with software that reads the keyboard through the BIOS. Older DOSBox-X versions defaulted to a Japanese layout, so the behavior you see can depend on the installed release.
- Identify the physical keyboard layout you are using.
- Check DOSBox-X’s detected layout and the setting that forces an IBM/U.S. layout.
- Apply the layout change only if the game’s keys are shifted—for example, punctuation or symbol keys produce the wrong DOS character.
- Restart the game and test the title’s own key-display or control screen.
If a game reads hardware directly instead of using the BIOS, forcing the layout may have no effect. That result points to a game-specific input scheme, not necessarily a failed keyboard.
Best Value
- Platform Compatibility: This PC controller is designed for Windows PC, Steam, Switch, Android, and iOS. Xbox-style asymmetric stick layout for PC gamers. Three modes cover all your devices. Please check your device compatibility before purchase
- Three Connection Modes: 2.4G wireless, Bluetooth, wired USB-C. PC gets native XInput/DirectInput. Switch pairs via Bluetooth, no adapter. This gaming PC controller switches devices seamlessly. Stable wireless minimizes random disconnects during gaming
- Hall Effect Precision: Hall effect joysticks and triggers eliminate stick drift. This gaming controller for PC delivers smooth, responsive input with no dead zones. Built for FPS, racing, and action games. Long-term precision for competitive PC gaming
- Back Buttons & Battery: Two programmable back buttons map combos and shortcuts. Textured grips with dual vibration. 1000mAh battery delivers up to 20H playtime. RGB can be turned off. A solid PC controller for gaming with custom back buttons
- ABXY Layout Switch: Press B + Minus + Plus to swap between PC and Switch modes. Features: 1000Hz polling rate, RGB lighting, turbo. Note: designed without mic jack or gyro sensor
Inspect bindings in the mapper editor
When a host key reaches DOSBox-X but triggers the wrong action, open the mapper editor and inspect the event. DOSBox-X supports bindings for physical keyboard keys and for joystick buttons, axes and hats.
- Open the mapper editor from DOSBox-X’s configured mapper command or interface.
- Select the DOS application event that should move, fire, open a menu or confirm an action.
- Check which host key or controller input is bound to that event.
- Add a binding for the desired key, or delete the binding that causes an unintended action.
- Save the mapper configuration, close the editor and test the game from a clean launch.
An event with no binding cannot be triggered by the associated host input. Conversely, a host key that is bound to a different event can appear to be ignored when it is actually performing another command. Test one action at a time rather than remapping the entire keyboard.
Do not assume a gamepad is supported
A USB gamepad is optional and useful only when the title supports joystick input or when its joystick events can be mapped to controls the game already understands. Mapping a button cannot create joystick support in software that accepts keyboard input only.
- Check the game’s control menu or documentation for joystick support.
- Map buttons, axes or hats to the game’s existing DOS events in the mapper editor.
- Keep a keyboard binding for menus and text entry unless the title clearly supports those actions on a joystick.
- If the game has no joystick path, solve the issue with keyboard layout or key bindings instead of buying additional hardware.
A symptom-led decision table
| Symptom | First check | Next targeted check | Do not assume |
|---|---|---|---|
| No sound at all | PC-98 machine type and game audio settings | PC-98 sound BIOS and, if available, a legitimate SOUND.ROM |
That an IBM Sound Blaster default applies |
| Sound setup detects no device | The title’s selected sound board | PC-98 Sound Blaster 16 addresses D2h–DEh and IRQ behavior when that device is supported | That changing devices will fix FM-board audio |
| Timing-sensitive speaker or audio failure | Whether the title is known to need PC-9801 behavior | pc-98 timer always cycles |
That the timer option is a universal sound fix |
| Japanese text is unreadable | PC-98 font configuration | FONT.ROM or another documented font format |
That a font change repairs sprites or video timing |
| Blank or unstable display | Return to the 24 kHz baseline | Title-specific GRCG, EGC, GDC clock or generation requirements | That 15 kHz is available or 31 kHz is stable for every title |
| Keys produce the wrong symbols | Japanese versus U.S. layout detection | Force IBM/U.S. layout when BIOS-based software needs it | That layout forcing affects direct hardware keyboard reads |
| A key does nothing | Mapper event and binding | Add or remove a keyboard or joystick binding | That a gamepad can add unsupported game logic |
How to make a useful compatibility report
When a setting does not solve the problem, capture enough detail for someone else to reproduce the branch rather than reporting only “PC-98 audio is broken.” Include:
- DOSBox-X version and operating system.
- The exact game title, release or disk image, and whether it is HDI, FDD or another format.
- The configured machine value, including whether you used
pc98,pc9801orpc9821. - The selected sound device, any
SOUND.ROMfile, and the point at which audio fails. - The font file and video settings, including frequency, GRCG/EGC state and GDC clock if changed.
- The host keyboard layout, mapper bindings and whether a joystick or USB gamepad is involved.
- The exact screen, command or game event that reproduces the failure.
This information distinguishes a configuration error from a title that depends on an undocumented hardware quirk. It also prevents advice for another emulator or release from being applied as if it were a DOSBox-X rule.
When these steps do not apply
The procedure is for emulation, with DOSBox-X as the documented example. Neko Project II, RetroArch cores and other emulators may expose different names, defaults and ROM requirements. An original PC-9800 computer has physical sound boards, CRT timing, keyboard circuitry and disk hardware that must be diagnosed at the hardware level; changing DOSBox-X settings cannot repair it.
Even within DOSBox-X, no available documentation provides a complete game-by-game compatibility matrix or guarantees which sound board, graphics mode or input device every title uses. The full configuration reference is maintained on the project’s mutable master branch, so compare its options with the reference for your installed release before assuming that a setting exists or has the same default.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
A safe order of operations
- Record the emulator, version, game and exact symptom.
- Confirm
machine=pc98and mount a PC-98 image format appropriate to the title. - For silence, test the PC-98 sound BIOS and then the title’s documented sound device; use
SOUND.ROMonly when you have an appropriate file. - For unreadable Japanese, configure a PC-98 font independently of video tests.
- For corrupt graphics, restore defaults, use 24 kHz as the baseline and investigate GRCG, EGC, GDC clock and title-specific mode requirements one at a time.
- For wrong keys, check layout detection and then inspect mapper events and bindings.
- Consider a USB gamepad only after confirming joystick support in the game.
- Keep the working configuration and document every change that affected the result.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
