Scp-ds-driver-package-1.2.0.160
| Sony Device Family | Minimum FW Version | Tested with 1.2.0.160 | |--------------------|--------------------|------------------------| | ODA G1 (ODS-D55U) | 1.20 | Yes (basic ops) | | ODA G2 (ODS-D77U) | 2.05 | Yes (full) | | ODA G3 (ODS-D280F) | 3.00 | Yes (recommended) | | PetaSite Optical Library | 4.10 | Limited – Use 1.1.x instead if issues arise |
| File/Component | Description |
|----------------|-------------|
| ScpDriver.exe | Installer/configuration utility |
| ScpVBus.sys | Virtual bus driver (creates Xbox 360 controller instances) |
| ScpControl.sys | Core filtering driver for HID communications |
| BthPS3.sys | Bluetooth stack patch for PS3 controller pairing |
| ScpService.exe | Background Windows service for continuous management |
Version 1.2.0.160 is considered the last stable release before the project’s gradual deprecation. It added preliminary support for Bluetooth dongles with the CSR8510 chipset and improved the handling of multiple connected controllers.
Because the driver is unsigned for newer Windows versions:
Level 4 approval is requested to attempt cross-testing scp-ds-driver-package-1.2.0.160 with SCP-914, SCP-261, and SCP-1471. Rationale: If the driver can treat anomalous objects as "peripherals," we might be able to uninstall certain threats.
O5-7 Note: Denied. We are not plugging that thing into a vending machine or a camera that looks back. Also, who keeps writing "IRQL_NOT_LESS_OR_EQUAL" on my office whiteboard every morning? Stop it.
The story of the SCP-DS-Driver-package-1.2.0.160 is a classic tale of early community-driven PC gaming solutions. It represents a critical bridge that allowed PlayStation controllers to work on Windows years before official support became standard. 1. The Origins: Filling a Void
Before Sony provided official Windows drivers for the DualShock 3 (DS3), PC gamers had to rely on third-party tools like MotioninJoy. However, MotioninJoy was notorious for being riddled with ads, requiring an internet connection, and having questionable stability. SCP (Scarlet.Crush Productions)
driver was born as an open-source, lightweight alternative. It worked by tricking Windows into thinking a DualShock controller was actually an Xbox 360 controller
—which has native XInput support—allowing it to work seamlessly with almost any modern PC game. 2. The Golden Era of Version 1.2.0.160
release became a "legendary" version in the community. While newer iterations like ScpToolkit
were eventually developed by others (notably Nefarius), many users found this specific legacy package to be the most stable for older hardware and specific Bluetooth dongles. Key features of this version included: Zadig Integration : It utilized a tool called
to "force" the replacement of standard Bluetooth or USB drivers with SCP-compatible ones. Bluetooth "Host" Mode scp-ds-driver-package-1.2.0.160
: It famously "claimed" a Bluetooth dongle entirely. Once the driver was installed, that dongle could
be used for DualShock controllers and nothing else (like mice or headphones). Zero Configuration
: Once set up, it ran as a Windows Service, meaning you could simply plug in your controller and play without opening an app. 3. The Troubleshooting Saga
The "story" for most users involved a specific ritual of trial and error: The Installation Ritual : Users would download the
archive, unblock the files in Windows properties, and run the ScpDriver.exe The Bluetooth Struggle
: Many found that their built-in laptop Bluetooth wouldn't work, leading to the common advice of buying a specific "CSR 4.0" USB dongle. The "Host Address" Fix
: A common plot point in this story was the "Host Address: Disconnected" error, which required users to manually use ScpPairTool
to hard-code the Bluetooth address of the dongle into the controller. 4. Legacy and Modern Successors
As Windows 10 and 11 evolved, the legacy SCP drivers began to cause "Blue Screen of Death" (BSOD) issues because they weren't designed for modern driver signatures. The story eventually shifted to its spiritual successors: ScpToolkit
: A more modern installer that expanded on version 1.2.0.160 but is now also considered deprecated/legacy BthPS3 & DsHidMini
: The current "gold standard" created by the same developer (Nefarius). These modern drivers allow your Bluetooth dongle to be used for both your controller and other devices simultaneously, finally solving the biggest drawback of the original SCP driver. SCP-DS-Driver-package-1.2.0.160
remains a nostalgic piece of software for retro gamers and those using legacy hardware who prefer its "set it and forget it" simplicity. installing this specific version, or are you looking for the modern equivalent for a current PC setup? Can't connect PS3 controller using Bluetooth #549 - GitHub | Sony Device Family | Minimum FW Version | Tested with 1
The SCP-DS-Driver-package-1.2.0.160 is a legacy software package designed to enable Sony DualShock 3 (DS3) and DualShock 4 (DS4) controllers to work on Windows systems by emulating an Xbox 360 controller. It is a precursor to the more modern ScpToolkit and was originally hosted on the PCSX2 forums. Core Functionality
XInput Wrapper: The primary purpose is to wrap the DirectInput signals from PlayStation controllers into XInput signals, making them compatible with modern PC games that natively support Xbox controllers.
Wired and Wireless Support: It supports both USB wired connections and wireless Bluetooth connections, though Bluetooth often requires a dedicated dongle and specific driver replacement.
Zadig Integration: This specific package version is frequently cited for its included Zadig utility, which is used to manually "force" the installation of compatible drivers for Bluetooth adapters that the standard installer might fail to recognize. Technical Components
ScpServer.exe: The application that manages the connection between the controller and the OS.
ScpService: A Windows service that runs in the background to handle the driver wrapper automatically.
Xinput1_3.dll: A critical file often placed in game directories to ensure the game recognizes the emulated controller. Common Use Cases & Tips
Legacy Hardware Support: It is still used by enthusiasts who prefer the lightweight nature of the older "ScarletCrush" versions over the heavier, later iterations of ScpToolkit.
Troubleshooting Bluetooth: If your Bluetooth adapter isn't showing up in modern tools, users on GitHub often recommend using the Zadig tool inside this package to load "Bluetooth" or "DualShock" presets.
Startup Configuration: For stable use, it is recommended to set the SCP DS3 Service to "Automatic (delayed start)" in the Windows Services panel (services.msc).
Note: This software is considered "end-of-life." For a more modern and actively maintained alternative, many users have transitioned to DsHidMini or BthPS3.
"This driver package is a Rosetta Stone for how our reality treats physical objects as peripherals. The scary part isn't that the driver works — it's that our universe has a driver stack. Who wrote the OS? And why is this driver version 1.2.0? What happened to 1.0? And what’s in build 161? Because the driver is unsigned for newer Windows
Also: Never, ever run
ds_uninstall.exe. We tried. We lost Site-19's entire breakroom to a bluescreen that read:PAGE_FAULT_IN_NONPAGED_AREA_OF_EXISTENCE."
scp-ds-driver-package-1.2.0.160 is a software driver suite for DirectStream (DS) peripheral architecture, versioned 1.2.0, build number 160. It is ostensibly designed to facilitate low-level I/O between an operating system kernel and hardware devices such as printers, scanners, audio interfaces, and removable media controllers. The package is 47.2 MB in size, digitally signed by a certificate that cryptographically resolves to "[DATA REDACTED] Industries, Hardware Division (Dissolved, 1987)".
The anomalous properties of the package manifest under three distinct conditions:
Let us assume, for the sake of documentation, that this package is genuine Foundation material.
From a purely technical standpoint, do not install this driver unless you are an O5 Council member or a suicidal sysadmin.
The mundane explanation—an industrial driver, a forgotten project, or an ARG—is comforting. But the precision of the naming, the versioning, and the sheer narrative gravity of the SCP Foundation universe suggest something more interesting. The fact that you are reading this article implies that the memetic pattern 1.2.0.160 has already propagated.
The question is not whether the driver exists. The question is: Is it already running in your kernel?
If you hear a faint whisper from your SSD saying "Containment breach in sector 160," do not reboot. Simply accept that reality, much like legacy hardware, requires a few anomalous drivers to keep running.
Addendum: As of this publication, no legitimate download link for scp-ds-driver-package-1.2.0.160 exists on the public internet. If you find one, do not download it. Do not checksum it. And for the love of all that is unholy, do not run pnputil /add-driver.
Stay safe. Stay amnesticized.
This article is a work of fiction and creative analysis inspired by the SCP Foundation collaborative writing universe. No actual anomalous drivers were harmed in its writing.