Difference between revisions of "Diablo"
From PCGamingWiki, the wiki about fixing PC games
m (updated template usage) |
m (updated template usage) |
||
Line 220: | Line 220: | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Reinstall version 1.0 and don't update the game}} | + | {{Fixbox/fix|Reinstall version 1.0 and don't update the game|ref={{cn|date=July 2016}}}} |
+ | |||
'''Notes''' | '''Notes''' | ||
{{ii}} Later physical disks come pre-patched with later versions which have this issue. | {{ii}} Later physical disks come pre-patched with later versions which have this issue. | ||
Line 229: | Line 230: | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Use [[#DxWnd|DxWnd]]}} | + | {{Fixbox/fix|Use [[#DxWnd|DxWnd]]|ref={{cn|date=July 2016}}}} |
}} | }} | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Use [[#Diablo 1 HD|Diablo 1 HD]]}} | + | {{Fixbox/fix|Use [[#Diablo 1 HD|Diablo 1 HD]]|ref={{cn|date=July 2016}}}} |
}} | }} | ||
Line 239: | Line 240: | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Use [[#Diablo 1 HD|Diablo 1 HD]]}} | + | {{Fixbox/fix|Use [[#Diablo 1 HD|Diablo 1 HD]]|ref={{cn|date=July 2016}}}} |
}} | }} | ||
Line 246: | Line 247: | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Use [[#Diablo 1 HD|Diablo 1 HD]]}} | + | {{Fixbox/fix|Use [[#Diablo 1 HD|Diablo 1 HD]]|ref={{cn|date=July 2016}}}} |
}} | }} | ||
Line 253: | Line 254: | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Use [[#Diablo 1 HD|Diablo 1 HD]]}} | + | {{Fixbox/fix|Use [[#Diablo 1 HD|Diablo 1 HD]]|ref={{cn|date=July 2016}}}} |
}} | }} | ||
Line 260: | Line 261: | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Use [[#Diablo 1 HD|Diablo 1 HD]]}} | + | {{Fixbox/fix|Use [[#Diablo 1 HD|Diablo 1 HD]]|ref={{cn|date=July 2016}}}} |
}} | }} | ||
Line 268: | Line 269: | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Mark Diablo.exe for DirectDraw compatibility behavior in the registry}} | + | {{Fixbox/fix|Mark Diablo.exe for DirectDraw compatibility behavior in the registry|ref={{cn|date=July 2016}}}} |
{{ii}} Additional ways over [[rainbow color problems in older games]] to do this, which both have an identical effect in practice: | {{ii}} Additional ways over [[rainbow color problems in older games]] to do this, which both have an identical effect in practice: | ||
* Use [http://www.mediafire.com/download/i1alox2bl2z387h/DirectDrawFix.exe DirectDrawFix.exe] and select Diablo.exe. | * Use [http://www.mediafire.com/download/i1alox2bl2z387h/DirectDrawFix.exe DirectDrawFix.exe] and select Diablo.exe. | ||
Line 278: | Line 279: | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Run Diablo.exe in Windows XP compatibility mode}} | + | {{Fixbox/fix|Run Diablo.exe in Windows XP compatibility mode|ref={{cn|date=July 2016}}}} |
# Right-click Diablo.exe and select "Properties". | # Right-click Diablo.exe and select "Properties". | ||
# Under "Compatibility mode" in the "Compatibility" tab ensure "Run this program in compatibility mode for:" is enabled, and select the bottom-most mode starting with "Windows XP" from the drop-down. | # Under "Compatibility mode" in the "Compatibility" tab ensure "Run this program in compatibility mode for:" is enabled, and select the bottom-most mode starting with "Windows XP" from the drop-down. | ||
Line 285: | Line 286: | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Kill explorer.exe before launch and relaunch it afterwards}} | + | {{Fixbox/fix|Kill explorer.exe before launch and relaunch it afterwards|ref={{cn|date=July 2016}}}} |
{{ii}} Typically this is done with a batch file; make a file with a .bat extension with the following content and use it to launch Diablo instead of Diablo.exe directly: | {{ii}} Typically this is done with a batch file; make a file with a .bat extension with the following content and use it to launch Diablo instead of Diablo.exe directly: | ||
<pre> | <pre> | ||
Line 301: | Line 302: | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Update the game to the latest version}} | + | {{Fixbox/fix|Update the game to the latest version|ref={{cn|date=July 2016}}}} |
{{ii}} See [[#Patches|patches]]. | {{ii}} See [[#Patches|patches]]. | ||
}} | }} | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Run Diablo.exe in Windows XP compatibility mode}} | + | {{Fixbox/fix|Run Diablo.exe in Windows XP compatibility mode|ref={{cn|date=July 2016}}}} |
{{ii}} See the matching fix in the [[#Periodic crashes|periodic crashes]] section for details. | {{ii}} See the matching fix in the [[#Periodic crashes|periodic crashes]] section for details. | ||
}} | }} | ||
Line 314: | Line 315: | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Reinstall the game without Hellfire}} | + | {{Fixbox/fix|Reinstall the game without Hellfire|ref={{cn|date=July 2016}}}} |
}} | }} | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Update the game to the latest version}} | + | {{Fixbox/fix|Update the game to the latest version|ref={{cn|date=July 2016}}}} |
{{ii}} See [[#Patches|patches]]. | {{ii}} See [[#Patches|patches]]. | ||
}} | }} | ||
Line 367: | Line 368: | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Use [[#Diablo 1 HD|Diablo 1 HD]]}} | + | {{Fixbox/fix|Use [[#Diablo 1 HD|Diablo 1 HD]]|ref={{cn|date=July 2016}}}} |
}} | }} | ||
{{Fixbox|1= | {{Fixbox|1= | ||
− | {{Fixbox/fix|Use an [http://www.autohotkey.com AutoHotkey] script}} | + | {{Fixbox/fix|Use an [http://www.autohotkey.com AutoHotkey] script|ref={{cn|date=July 2016}}}} |
{{ii}} 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: | {{ii}} 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: | ||
<pre> | <pre> | ||
Line 397: | Line 398: | ||
'''Notes''' | '''Notes''' | ||
− | {{ii}} | + | {{ii}} Due to terms of use you wouldn't want to use this in battle.net multiplayer.{{cn|date=July 2016}} |
}} | }} | ||
− | ===[http://freeablo.org | + | ===[http://freeablo.org Freeablo]=== |
{{ii}} A FOSS reimplementation of the Diablo engine currently in an alpha state; see the site for details. | {{ii}} A FOSS reimplementation of the Diablo engine currently in an alpha state; see the site for details. | ||
Revision as of 10:09, 7 July 2016
Developers | |
---|---|
Blizzard North | |
Publishers | |
Blizzard Entertainment | |
Release dates | |
Windows | December 31, 1996 |
Mac OS (Classic) | May 8, 1998 |
Diablo | |
---|---|
Diablo | 1997 |
Diablo II | 2000 |
Diablo III | 2012 |
Diablo II: Resurrected | 2021 |
Diablo Immortal | 2022 |
Diablo IV | 2023 |
Key points
- 20 FPS gameplay and 15 FPS videos without mods.[1]
General information
Availability
Source | DRM | Notes | Keys | OS |
---|---|---|---|---|
Retail | DRM: Simple disk check, no physical copy protection. | |||
Amazon.com | ||||
Amazon.com | Old version of the Diablo Battle Chest. | |||
Amazon.com | Bundled with the Hellfire expansion. | |||
Amazon.com | Hellfire expansion only. |
- Not available via digital distribution.
- Later versions of the Diablo Battle Chest 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
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.
IPXWrapper
- 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 directory where Diablo.exe resides.[2][3]
DxWnd
- Allows running Diablo in windowed mode; not needed with Diablo 1 HD. To get started open the app and select File->Import ... from the menu bar, go to the exports directory and select Diablo.dxw. Right-click Diablo in the window and select Run.[4]
Mods
Diablo 1 HD
- An unofficial mod, also known as "Belzebub", in beta state for single player (only) with a host of features including increased resolution and updated compatibility with modern Windows. Copy the contents to the Diablo directory 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.
The Hell
- 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.
The Awakening
- Another unofficial mod that also requires the Hellfire expansion.
Game data
Configuration file(s) location
- Windows: Multiplayer chat hotkey macros are stored in
<path-to-game>\diablo.ini
.
Save game data location
Video settings
Input settings
Audio settings
Localizations
Language | UI | Audio | Sub | Notes |
---|---|---|---|---|
English |
Network
Multiplayer types
Type | Native | Players | Notes | |
---|---|---|---|---|
LAN play | 4 | Co-op |
||
Online play | 4 | Co-op |
- Only up to 2 players are supported via modem.
Connection types
Type | Native | Notes |
---|---|---|
Matchmaking | ||
Peer-to-peer | ||
Dedicated | ||
Self-hosting | ||
Direct IP |
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.
Instructions |
---|
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.
Instructions |
---|
Instructions |
---|
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.
Instructions |
---|
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.
Instructions |
---|
Diablo.exe process doesn't end after quitting game
- When quitting the game the Diablo.exe process can remain indefinitely on modern Windows.
Instructions |
---|
Title screen effects partially disappear
- Title screen effects such as the fire sometimes partially disappear on modern Windows.
Instructions |
---|
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. See rainbow color problems in older games for fixes.
Instructions |
---|
Periodic crashes
- The game can crash periodically with modern Windows, especially due to modern GPU drivers.
Instructions |
---|
Instructions |
---|
Can't create character in multiplayer mode
- After entering a character name in multiplayer you can get an error due to Windows compatibility issues.
Instructions |
---|
Instructions |
---|
Can't connect to Battle.net
- You must be running the latest version and not have the Hellfire expansion installed.
Instructions |
---|
Instructions |
---|
Other information
API
Technical specs | Supported | Notes |
---|---|---|
DirectDraw | 3 |
Executable | PPC | 16-bit | 32-bit | 64-bit | Notes |
---|---|---|---|---|---|
Windows | |||||
Mac OS (Classic) |
Middleware
Middleware | Notes | |
---|---|---|
Cutscenes | Smacker Video Technology | |
Multiplayer | Battle.net |
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.
Instructions |
---|
Instructions |
---|
Freeablo
- 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 |
References
- ↑ Cite error: Invalid
<ref>
tag; no text was provided for refs namedFPStest
- ↑ Diablo I (yes, Diablo 1) LAN play on Vista or Windows 7
- ↑ Diablo 1 - Windows Vista / 7 Color and LAN Issues RESOLVED
- ↑ Play Old PC Games :: Using DXWnd