PlayStation BB Navigator

From PCSX2 Wiki
Revision as of 15:40, 22 August 2022 by DarkSolidSnake (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
PlayStation BB Navigator
PlayStation BB Navigator.jpg
Game general and emulation properties:
Game supports harddrive
Languages supported:
Japanese: SCPN-60101 & SCPN-60130& SCPN-60140 & SCPN-60160 & SCPN-60107
Region NTSC-J/C/K:
Serial numbers: SCPN-60101 (0.10, Prerelease)
SCPN-60103 (0.10, Prerelease Disc 2)
SCPN-60107 (0.10, Prerelease Disc 2)
SCPN-60111 (0.10, Prerelease Disc 2?)
SCPN-60130 (0.20)
SCPN-60140 (0.30)
SCPN-60150 (0.31)
SCPN-60160 (0.32)
Release date: 2002
Windows Status: Broken
Linux Status: ?
Mac Status: ?

Genre: Tools
Wikipedia: Link
Game description: Japanese utility discs for HDD formatting and manipulation

Winlogo.png Test configurations on Windows:

Environment Configurations Comments Tester
Region OS CPU/GPU Revision Graphics Sound/Pad
NTSC-J (0.30) Microsoft Windows 10, 64-bit
  • intergrated
  • intergrated
v1.7.0 (dev-2204) GSdx (build-in)
  • SPU2-X (build-in)
  • LilyPad (build-in)
BIOS: Japan v1.00, Preset: 2 (Safe). Upon startup the game immediately throws up a bunch of TLB Miss errors and causes the emulator to crash. This may be due to MagicGate emulation DarkSolidSnake


  • Original name: プレイステーション BB ナビゲーター Version 0.10 プレリリース版 (SCPN-60101) & (SCPN-60103) & (SCPN-60107) & (SCPN-60111), プレイステーション BB ナビゲーター Version 0.20 (SCPN-60130), プレイステーション BB ナビゲーター Version 0.30 (SCPN-60140), プレイステーション BB ナビゲーター Version 0.31 (SCPN-60150), プレイステーション BB ナビゲーター Version 0.32 (SCPN-60160)

Known Issues

TLB Misses, Emulator crashes

  • Status: Active
  • Type: Major
  • Description: Upon startup, the game immediately throws up a bunch of TLB Miss errors and causes the emulator to crash. The console log shows the following:
(EE pc:00000000) TLB Miss, addr=0x0 [load]
(EE pc:00000000) TLB Miss, addr=0x0 [load]
(EE pc:00000004) TLB Miss, addr=0x70032fcb [store]
  • Workaround: There is no known workaround