Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsThe most reliable current setup for playing PC-98 games in Neko Project II is the Neko Project II Kai (NP2kai) core in RetroArch. Install that core, put the legally obtained PC-98 firmware in RetroArch’s system/np2kai directory, then load a disk image in a PC-98 format such as .d88, .fdi, .hdi or .nhd. The older Libretro Neko Project II core is documented as superseded by Kai, while the standalone NP2kai program uses different file locations and menu conventions.
This guide targets RetroArch’s Libretro build. If you are using a standalone NP2kai port, use its own documentation for paths and controls rather than copying RetroArch instructions literally.
As an Amazon Associate I earn from qualifying purchases.
What you need before configuring NP2kai
Prepare these items before opening a game:
- A current RetroArch installation compatible with the NP2kai Libretro core.
- The Neko Project II Kai core installed through RetroArch’s core downloader or your platform’s package method.
- PC-98 firmware files that you are legally entitled to use. NP2kai project documentation says BIOS files can be obtained from an actual PC-98 with the project’s GETBIOS tool; it does not authorize downloading copyrighted firmware from unlicensed sites.
- A disk image made for the PC-98 platform. A standard IBM PC/AT floppy image is not interchangeable with a PC-98 image.
- A keyboard for the initial setup. A mouse or gamepad can be configured later when a particular game needs one.
Keep the emulator, firmware and game images separate in your mind: firmware lets the emulated machine start, while a game image supplies the software it runs. A complete set of ROM files cannot substitute for a correctly formatted game disk.
Choose Kai instead of the older Libretro core
Libretro’s documentation describes its original Neko Project II core as superseded by Neko Project II Kai. For a new RetroArch installation, search for and install the core whose name identifies Neko Project II Kai (often displayed as NP2kai). Do not select the older core simply because its name appears first in a list or in an old tutorial.
#1 Best Overall
- 【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
| Choice | Use it when | Important difference |
|---|---|---|
| Neko Project II Kai Libretro core | You want to run PC-98 software inside RetroArch. | Firmware belongs in RetroArch’s system directory under np2kai; RetroArch controls core loading, input and disk operations. |
| Older Libretro Neko Project II core | Only when a legacy setup specifically requires it. | Its Libretro documentation says it has been superseded by Kai, so older instructions may not match current support. |
| Standalone NP2kai | You are running the emulator as its own application or a platform-specific port. | Configuration folders, firmware naming, menu shortcuts and disk-list support can differ from the Libretro build. |
The rest of this article assumes RetroArch with the Kai core. When a behavior comes from the NP2kai project’s standalone or port documentation, it is identified as a compatibility note rather than a universal RetroArch rule.
Install the core and locate RetroArch’s system directory
- Start RetroArch and open the menu used by your build to download or manage cores.
- Find Neko Project II Kai and install it. If several PC-98-related entries appear, verify that the selected entry explicitly says Kai.
- Open RetroArch’s Settings and its Directory settings, then note the path shown for System/BIOS. This is the frontend’s system directory; its exact location varies by operating system and package.
- Inside that directory, create a folder named
np2kai. Use lowercase spelling exactly as shown. Do not put the files only beside the game image unless your particular port’s documentation explicitly says otherwise.
Portable and console packages can place the system directory in different locations. The path displayed by RetroArch is authoritative for that installation, so use it instead of assuming a Windows, Linux or macOS default.
Install NP2kai firmware correctly
Libretro’s Kai documentation lists four required firmware items:
font.bmp(or the alternativeFONT.ROM)bios.romitf.romsound.rom
Place the files directly in system/np2kai, so the resulting layout resembles:
RetroArch system directory/
└── np2kai/
├── font.bmp (or FONT.ROM)
├── bios.rom
├── itf.rom
└── sound.romThe same documentation identifies bios9821.rom and d8000.rom as optional. They can be added to the same folder when a title or machine configuration needs them, but they are not part of the minimum required set. Optional YM2608 rhythm-sample WAV files can improve rhythm-channel playback in software that uses those samples; they are not needed to boot every game.
Firmware sourcing and file-name checks
The NP2kai project recommends extracting BIOS data from an actual PC-98 with GETBIOS. Use only firmware you have the legal right to use. Avoid renaming files casually: the core looks for the documented names, and a correct dump with an unexpected extension or capitalization may be treated as missing. If your package provides FONT.ROM rather than font.bmp, use the alternative documented by Libretro rather than adding both versions at random.
The NP2kai project documentation calls the original PC-98 font.rom the recommended font for NP2kai. Libretro’s Kai page also accepts font.bmp; which form is appropriate can depend on the core build. If Japanese characters are blank or replaced by blocks, check the font file, its spelling and the np2kai path before changing game settings.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #2
- ✔ Compatible with Windows98/ME/Vista/2000/2003/XP/7/8/8.1/10; Mac OS X and beyond ; Emulators ;Raspberry Pi ;Raspberry PI 2 model B ;Retro Pi OS; Retropi System.
- ✔ Simple USB plug and play, no drivers and software required. Note: If you have trouble with using this, make sure it is plugged in before starting your emulator. Also go into input settings and you may have to map the buttons.
- ✔ Work with any emulator you wish to download and use. Google S-N-E-S emulator and then the same for Roms. Way better than normal joypad and keyboard and mouse playing to really enjoy the emulator experience.
- ✔ Super sensitive buttons for precision control, Eight-way directional pad and six digital buttons. Play your favorite old school games with authentic retro feel. Arrowed D-pad, concave X and Y buttons, convex A and B buttons, rubber start and select buttons. Cord is approx. 5 ft. Long, providing a comfortable distance while playing.
- ✔ If you want to play S-N-E-S, N-E-S, PSX, Atari, Genesis, or any other types of this vintage of games... get this. You will not regret it. NOTE:Third party controller, not original S-N-E-S / N-E-S controller. But it works phenomenal with the Raspberry Pi game emulation and so on.
Load a PC-98 game image
With firmware in place, use RetroArch’s content-loading command to select the game image. Kai documents support for these common extensions:
| Extension | Typical role | What to check |
|---|---|---|
.d88 |
PC-98 floppy image, often used for one or more disks. | Confirm the image represents a PC-98 disk and not an IBM PC/AT disk. |
.fdi |
Floppy-disk image. | Use a dump with the correct PC-98 geometry. |
.hdm |
High-density floppy image. | Retain the original image structure; do not convert it to a generic PC format. |
.hdi |
Hard-disk image. | Load it as a hard disk when the game expects one. |
.cmd |
NP2kai command file that can describe mounted floppy, hard-disk or CD images. | Support varies between ports and builds. |
.nhd |
Hard-disk image. | Use the image type the game was authored for. |
.hdd |
Hard-disk image. | Some titles require a reset after changing this media. |
.zip |
Compressed image container accepted by the Kai core. | The archive still needs to contain a supported PC-98 image. |
PC-98 floppy media commonly uses PC-98 formats such as 720 KB 2DD and 1.23 MB 2HD. A floppy image formatted for an IBM-compatible PC/AT may open as a file but fail to boot because the sector layout and boot expectations are different. Select the image supplied for the PC-98 release of the game.
The “How many files (0-15)?” screen
If the emulator reaches a ROM BASIC prompt asking “How many files (0-15)?”, the firmware has probably been found, but the selected floppy or hard-disk image has not mounted as bootable media. This is not evidence that the BIOS is missing. Check that you loaded the intended image, that it is a supported extension, and that it is the PC-98 version. Then restart the core and try again.
Booting a game step by step
- Launch RetroArch and select the NP2kai core.
- Use Load Content to choose the game’s supported image file.
- Wait for the PC-98 startup sequence. The first boot can take longer if a hard-disk image is being initialized.
- If the game reaches its own title screen, keep a copy of the working firmware and image arrangement before changing options.
- If it stops at ROM BASIC, return to the image checks above rather than immediately changing CPU or sound settings.
Do not assume every game uses the same media. A floppy release may require disk swapping, while a hard-disk release may boot from one image and expect a reset after media changes.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteChange disks and mount multi-disk releases
NP2kai’s menu is the central control for virtual drives. Libretro documentation identifies F12 as the shortcut for opening the NP2 menu. The NP2kai project also describes F12, a mouse middle-button press or L2 on a libretro gamepad mapping for its libretro port. Which shortcut works depends on the frontend’s active keyboard and controller bindings.
Swapping a floppy in the NP2 menu
- Open the NP2 menu with F12, the middle mouse button or the mapped L2 control.
- Choose the floppy-drive operation and select the next disk image.
- Return to the emulation screen and follow the game’s own prompt to continue.
The same menu can change hard-disk images, but the NP2kai project warns that a hard-disk swap requires a reset. Save the game first when possible, select the replacement image, then reset the emulated machine.
Using RetroArch Disk Control
RetroArch also provides disk-management controls for cores that expose multiple disk images. The exact menu labels and hotkeys vary by version and platform. Add the next image to the disk list, select it, and use the core’s change-disk action only when the game requests it. If a disk appears in the frontend but the game does not advance, use the NP2 menu to verify that the correct virtual drive received the image.
Rank #3
- ✅【Compatibility】Compatible with Raspberry Pi, Windows PC, Linux ,Mac. Specifically designed for playing classic old school retro snes games on computer or laptop.This is the USB controller what has a USB plug for PC, NOT compatible for Original SNES super Nintendo console
- ✅ 【Ergonomic Design】Super precise cross key and function buttons,the cross direction key adopts frosted concave design,anti-sweat and anti-slip.The shape of the controller is designed to fit the contour of your hands,easy and comfortable to hold.
- ✅ 【Advanced Game Experience】PC running operating system:Windows 98/2000/ ME/XP/Vista/Win7/8/8.1/11 or later,or Mac running OS X 10.0/Mac OS X or above.It works with most of emulators you wish to download and use,such as VirtuaNES(PC),sens9x,Zsens,sensgt,Uosnesw,RetroArch,OpenEmu(MAC),NESEmu and Jnes etc.
- ✅ 【Wired USB Connection】Standard USB 2.0 port with a 1.5 meters (5ft) cable, don't need to install any drivers, you must manually set the buttons and directionals within the emulator you're using, and the controller not automatically assigns buttons/directional axes. Notice: please download the game emulator first before start the games, you can download the emulator “VirtuaNES” on PC and “OpenEmu”on MAC.
- ✅【Satisfaction】Third party controller(USB Version), not for original snes console and not support for switch. If there is an incompatibility on MAC or Raspberry Pi , please contact the seller for a support.
.m3u lists and .cmd files
The NP2kai project documents UTF-8 .m3u lists for floppy disks and .cmd files that can mount floppy, hard-disk and CD images. However, the project also notes that .m3u support was not present in its libretro core implementation. Therefore, do not assume a list that works in a standalone port will work in RetroArch.
Recommended Free Tools
For a RetroArch build, test the method your installed core actually supports: load individual images through Disk Control or use a documented .cmd workflow if that build exposes it. Keep filenames and paths simple, encode an .m3u file as UTF-8 when using a port that supports it, and verify support before reorganizing a large library.
Configure keyboard, mouse and gamepad controls
A keyboard is the safest baseline because many PC-98 games expect Japanese computer-keyboard commands, function keys or keypad input. Start the game with the default keyboard mapping, then add a controller only if it improves comfort.
Keyboard input and RetroArch hotkeys
RetroArch can reserve keys for frontend hotkeys. If a key works in menus but not inside the game, check whether an enable-hotkeys combination is required or whether game focus is disabled. The NP2kai project documents using the frontend’s enable-hotkeys and game-focus approaches to prevent RetroArch from intercepting keyboard commands.
Test one problematic key at a time: pause the frontend, toggle game focus if available, then press the game’s key again. Avoid disabling every hotkey permanently until you know which binding is interfering, because you may lose a convenient way to exit or open the NP2 menu.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Mouse-driven games
NP2kai exposes mouse input modes through its joypad configuration. If a game’s pointer is unresponsive, first select a mouse-oriented mapping and confirm that RetroArch is passing mouse input to the core. Then check the game’s or DOS environment’s mouse driver. The NP2kai project specifically advises checking whether the required driver is loaded from CONFIG.SYS.
A game can therefore fail for two separate reasons: the emulator may be in a keyboard or arrow mode, or the emulated DOS installation may not have loaded a mouse driver. Fix the mapping first, then inspect the boot files inside the game’s environment.
Rank #4
- 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.
Gamepad modes
NP2kai documents joypad modes for:
- Arrow-key emulation.
- Numeric-keypad emulation.
- Manual keyboard mappings.
- Mouse input.
Choose the mode that matches the game’s input method. A USB game controller is optional; compatibility depends on the device and the frontend’s mapping layer. If the game expects keyboard commands, a gamepad configured as a mouse may move a cursor but will not produce the required key presses. Conversely, an action game that reads mouse movement may feel wrong in arrow-key mode.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Adjust compatibility settings only when necessary
NP2kai’s core options expose several parts of the emulated PC-98 hardware:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Option area | Why it matters | Safe starting approach |
|---|---|---|
| PC model | Different PC-98 generations expose different hardware behavior. | Leave the default until a title’s requirements identify another model. |
| CPU base clock and multiplier | Changes emulated processor speed and can affect timing-sensitive software. | Use defaults first; change only for a documented game requirement. |
| RAM | Some software expects a particular memory size. | Start with the default amount and match the release’s requirements when known. |
| Graphics controller | Different display hardware can affect compatibility. | Keep the default unless the game specifies a controller. |
| Sound board or generator | Determines which PC-98 audio hardware is emulated. | Try the documented era-appropriate choice, then reset as required. |
Libretro and NP2kai documentation describe the YM2608/“26K” sound option as a fit for older games and the YM2203/“86” option as a fit for newer games. Treat that as a starting point, not proof that every title in an era uses the same board. A game may have its own hardware requirement or configuration utility.
Some option changes require a core restart, and changing the sound generator requires a reset. Save before experimenting, change one setting at a time, restart when RetroArch requests it, and record the combination that works. Changing several options together makes it difficult to identify which one fixed—or caused—the problem.
Standalone NP2kai versus RetroArch Kai
The emulator name does not guarantee identical behavior across ports. Standalone NP2kai builds can use their own configuration files, firmware directories and menu shortcuts. The project documentation mentions platform-specific font and firmware conventions, while Libretro’s documentation defines the system/np2kai layout for its core.
| Task | RetroArch/Libretro Kai | Standalone NP2kai |
|---|---|---|
| Firmware location | RetroArch system directory, inside np2kai. |
Port-specific location documented by that build. |
| Open emulator menu | F12 is documented; middle mouse or L2 may also be mapped. | Shortcut can follow the standalone port’s own configuration. |
| Multi-disk method | RetroArch Disk Control, NP2 menu, or a build-supported command/list method. | Project-documented .m3u and .cmd behavior may be available. |
| Input interception | RetroArch hotkeys and game-focus settings can affect keys. | Uses the standalone port’s input layer. |
If an instruction seems contradictory—for example, an .m3u list works in a standalone window but not in RetroArch—check the implementation rather than repeatedly rebuilding the file. The core and frontend combination determines which feature is available.
Free tools Windows power users keep installed
One-click scans. No signup required.
Troubleshooting checklist
| Symptom | Likely cause | Action |
|---|---|---|
| “How many files (0-15)?” appears | Firmware was found, but the game image did not mount. | Verify the selected image, extension, PC-98 format and virtual drive; restart the core. |
| Japanese text is missing | Font file is absent, misnamed or in the wrong directory. | Check font.bmp or FONT.ROM under system/np2kai; confirm which core and port is running. |
| The game boots but the mouse does nothing | Wrong joypad mode or missing DOS mouse driver. | Select mouse input, then check that the game’s or DOS driver loads through CONFIG.SYS. |
| A controller moves a cursor, but the game expects keys | Joypad is configured as mouse input. | Switch to arrows, keypad or manual keyboard mapping. |
| Keyboard commands are ignored | RetroArch hotkeys or game focus intercept the keys. | Review enable-hotkeys and game-focus behavior, then test the key inside the emulation window. |
| Sound or game behavior is wrong | Model, clock, RAM, graphics or sound-board mismatch. | Return to defaults, consult the title’s requirements, change one option, and reset or restart when required. |
| A second disk will not load | Unsupported list-file method or wrong virtual drive. | Use the NP2 menu or RetroArch Disk Control; verify whether your build supports the selected .m3u or .cmd workflow. |
| Hard-disk replacement appears ignored | The emulated machine was not reset after the swap. | Swap the image, then reset the machine as NP2kai documentation recommends. |
A reliable order for diagnosing a failed launch
- Confirm the core: make sure RetroArch is running Neko Project II Kai, not the superseded core.
- Confirm the path: verify the active System/BIOS directory and the
np2kaisubfolder. - Confirm the required files: check the four required firmware names and the font alternative.
- Confirm the media: use a supported PC-98 image and identify whether it is floppy, hard disk or CD media.
- Confirm mounting: open the NP2 menu and make sure the image is assigned to the drive the game expects.
- Confirm input: test keyboard first, then configure mouse or gamepad mode.
- Only then tune hardware: alter model, memory, clock, graphics or sound settings one at a time, observing reset requirements.
This order separates file and media errors from emulation-compatibility errors. It also preserves a known-good baseline, making later game-specific adjustments reversible.
Practical defaults for a first game
For a first launch, use the Kai core with the default PC model, clock, RAM, graphics and sound settings. Place the required firmware in system/np2kai, load one verified PC-98 floppy or hard-disk image, and use the keyboard. If the game starts, save that arrangement before trying a controller or performance tweak. Add optional BIOS files or rhythm samples only when a title needs them, and use the NP2 menu for disk changes rather than assuming a list-file feature is shared by every port.
Quick Recap
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.
