Key points
- 20 FPS gameplay and 15 FPS videos without mods.[1]
General information
- Official Diablo Support
- Official Diablo Series Forum
- Unofficial Diablo Wiki
- GOG.com Community Discussions for game series
- GOG.com Support Page
Availability
Source |
DRM |
Notes |
Keys |
OS |
Retail |
|
DRM: Simple disc check, no physical copy protection. |
|
|
GOG.com |
|
Pre-patched with DirectX 1-7 wrapper |
|
|
- Later versions of the Diablo Battle Chest starting in 2007 no longer include the original Diablo.
DLC and expansion packs
Name |
Notes |
|
Hellfire |
Authorized third-party expansion. Cannot be played on Battle.net. |
|
Essential improvements
- IPXWrapper provides a workaround for Windows Vista and beyond not supporting IPX, used in multiplayer. Put ipxwrapper.dll, mswsock.dll, and wsock32.dll in the folder where Diablo.exe resides.[2][3]
Patches
- Battle.net's support section has the latest patches; spawn versions of the game require separate patches from the full versions. Battle.net will not connect without the latest patch.
Windows-Only Diablo Spawn Patch
Mods
- An unofficial single-player mod with a host of features including increased resolution and updated compatibility with modern Windows. Copy the contents to the Diablo folder and open Belzebub.exe to play.
- Allows running at up to 60 FPS, in windowed mode, in resolutions scaled up to 1024p and various non-scaled, fixes crashing and DirectDraw compatibility issues, multi-monitor compatibility, and continuous attacking with the left mouse button held down.
- Can't play the vanilla game without the added content, multi-player isn't currently available, and the viewing area is simply increased; sprites remain small at higher resolutions.
- An unofficial mod that requires the expansion Hellfire to run which has various additions such as new spells, makes the game considerably more difficult, and has a tool for running the game on modern Windows.
- Another unofficial mod that also requires the Hellfire expansion.
Play the game without the CD (retail)
Use Elisha's Windows 10 Patch[citation needed]
|
- Patch game to the latest version first.
- Download the Diablo Windows 10 Patch.
- Unzip the files to the installation folder.
- Copy
DIABDAT.MPQ from the CD to the installation folder.
|
Game data
Configuration file(s) location
System |
Location |
Windows |
HKEY_CURRENT_USER\SOFTWARE\Blizzard Entertainment\Diablo\ |
Mac OS (Classic) |
|
- Windows: Multiplayer chat hotkey macros are stored in
<path-to-game>\diablo.ini
.
Save game data location
Video settings
Diablo GOG.com DirectX configuration.
Selecting 320x240 in vidsize.exe (Windows) renders videos quarter size centered.
Template:Video settings
Input settings
Template:Input settings
Audio settings
Template:Audio settings
Localizations
Network
Multiplayer types
- Only up to 2 players are supported via modem.
Connection types
Ports
Protocol |
Port(s) and/or port range(s) |
TCP |
6112-6119 |
UDP |
6112-6119 |
- Universal Plug and Play (UPnP) support status is unknown.
Issues unresolved
Music doesn't play on the character and multiplayer selection screens
- The official patches introduced a behavior where music no longer plays on the character or multiplayer selection screens.
Reinstall version 1.0 and don't update the game[citation needed]
|
Notes
- Later physical disks come pre-patched with later versions which have this issue.
|
Game crashes when switching to another process
- The game crashes when switching to another process on modern Windows, typically done using Alt+Tab ↹ or through the lock screen using Ctrl+Alt+Delete.
Use DxWnd[citation needed]
|
Game locks up when returning to the main screen from multiplayer
- The game can lock up with a black screen when returning to the main menu from the multiplayer menu on modern Windows.
Incorrect ancillary text display when entering a character name
- When entering a character name on modern Windows other text around the text entry area that should be cleared remains and appears partially cut off.
Diablo.exe process doesn't end after quitting game
- When quitting the game the Diablo.exe process can remain indefinitely on modern Windows.
Title screen effects partially disappear
- Title screen effects such as the fire sometimes partially disappear on modern Windows.
Issues fixed
Rainbow or washed out colors on Windows
- Colors can appear washed out, appear as a rainbow, or simply white due to a DirectDraw compatibility issue in Windows XP, Vista, and 7, including running in compatibility mode for these versions.
Mark Diablo.exe for DirectDraw compatibility behavior in the registry[citation needed]
|
- Additional ways over rainbow color problems in older games to do this, which both have an identical effect in practice:
|
Periodic crashes
- The game can crash periodically with modern Windows, especially due to modern GPU drivers.
Run Diablo.exe in Windows XP compatibility mode[citation needed]
|
- Open
Diablo.exe compatibility settings.
- Enable Windows XP (SP3) compatibility mode.
|
Can't create character in multiplayer mode
- After entering a character name in multiplayer you can get an error due to Windows compatibility issues.
Update the game to the latest version[citation needed]
|
- See Patches.
|
Run Diablo.exe in Windows XP compatibility mode[citation needed]
|
- Open
Diablo.exe compatibility settings.
- Enable Windows XP (SP3) compatibility mode.
|
Can't connect to Battle.net
- You must be running the latest version and not have the Hellfire expansion installed.
Reinstall the game without Hellfire[citation needed]
|
Update the game to the latest version[citation needed]
|
- See Patches.
|
Other information
API
Technical specs |
Supported |
Notes |
DirectDraw |
3 |
|
Executable | PPC | 16-bit |
32-bit |
64-bit |
Notes |
Windows | | |
|
|
|
Mac OS (Classic) | | | |
|
|
Middleware
Continuous attacking with left mouse button held down
- Normally on left mouse button down it only attacks once even if held down. Later games in the Diablo series provide this capability.
Use an AutoHotkey script[citation needed]
|
- Here's a simple non-ideal example. Make a file with a .ahk extension and put the following in it, then run it followed by the game:
~+LButton::
Loop
{
Sleep 100
GetKeyState, LButtonState, LButton, P
if LButtonState = U
break
MouseClick, Left
}
return
LButton::
Loop
{
Sleep 100
GetKeyState, LButtonState, LButton, P
if LButtonState = U
break
MouseClick, Left
}
return
Notes
- Due to terms of use you wouldn't want to use this in battle.net multiplayer.[citation needed]
|
- A FOSS reimplementation of the Diablo engine currently in an alpha state; see the site for details.
System requirements
Windows |
|
Minimum |
Operating system (OS) |
95, NT 4.0 |
Processor (CPU) |
60 MHz Pentium or better |
System memory (RAM) |
8 MB 16 MB for multiplayer |
Hard disk drive (HDD) |
|
Video card (GPU) |
DirectX 3 compatible |
Other |
2x CD-ROM drive |
Mac OS |
|
Minimum |
Recommended |
Operating system (OS) |
7.5 | |
Processor (CPU) |
PowerPC | |
System memory (RAM) |
16 MB with virtual memory 32 MB with virtual memory for multiplayer |
32 MB with virtual memory |
Hard disk drive (HDD) |
| |
Video card (GPU) |
640x480 resolution and 256 color support | |
Other |
2x CD-ROM drive | |
Notes
References