WineHQ
Diablo II Lord of Destruction 1.x



Category: Main > Games > Role Playing Games > Diablo II > Lord of Destruction 1.x

NameDiablo II
VersionLord of Destruction 1.x
License Retail
URLhttp://us.blizzard.com/en-us/g...
Votes Marked as obsolete
RatingGold
Wine Version1.4
Amazon in Harrogath
View/Submit Screenshot
Maintainers of this version:
Description

Retail expansion and all updates.

  • Post results for the Downloader "here"
Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results (selected in 'Test Results' table below)

What works
Everything I tried worked flawlessly.


What does not
Nothing I could find.


What was not tested
Battle.net (normal multiplayer works well)


Additional Comments

It does not work well with Compiz/Unity (slow and laggy), so I made a script that I use to launch the game, then added a .desktop-file to ~/.local/share/applications/ and gave it a nice icon from the games image directory to make it show up in the dash. That works very well: (replace "Programfiler" with the correct one in your language)

#!/bin/sh
metacity --replace &
wine "~/.wine/drive_c/Programfiler/Diablo II/Game.exe"
unity --replace # perhaps compiz --replace would be better? 

I also had to enable emulated audio, presumably because of PulseAudio. 

In spite of these issues, I give it a Platinum rating. I played the entire game in hardcore mode, single player and local multiplayer. No complaints.

Admin note: rating changed to conform to the rating definitions.
Test Results
DistributionTest dateWine versionInstalls?Runs?RatingSubmitter
ShowArch Linux x86_64May 02 20121.5.2 Yes Yes Platinum an anonymous user 
ShowArch Linux x86_64Apr 22 20121.5.2 Yes Yes Platinum Chris Bacon 
ShowUbuntu 12.04 "Precise" x86_64 (+ variants like Kubuntu)Dec 23 20121.4 Yes Yes Gold MB 
ShowMac OS X 10.8 "Mountain Lion"Oct 29 20121.4 Yes Yes Gold Michael Barlow 
ShowGentoo Linux AMD64Feb 25 20121.4-rc3 Yes Yes Platinum Lukas Matousek 

Known bugs
Bug # Description Status Resolution Other apps affected
14348 Diablo 2: Unhandled Exception code c0000005 NEW View
14456 Diablo II hangs when it loses focus REOPENED View
16958 Exiting Diablo II running in windowed mode, resets xrandr display setup UNCONFIRMED View
20362 Diablo II: X11 mouse pointer shows over fullscreen window NEW View
28520 Diablo II: surface flips ignore vsync flags NEW View
28770 Diablo 2 - sound works in menu, stops after starting game UNCONFIRMED View
30867 Page fault / null pointer exception in ConvertPixelFormatGLXtoWGL when virtual desktop is enabled UNCONFIRMED View

 
WARNING

Copy Protection Final Word

Patch 1.12 from Blizzard disables the CD check.

If you ever get "Please insert disc", this is NOT a problem with detecting the CD. The protection system is probably still built into the game even though the CD check itself is disabled. Make sure you use version 1.12 or later. If you get this problem after having this version installed, you are likely suffering from a buggy video driver as this is the only known (and proven possible) cause at this point.

DO NOT USE NOCD PATCHES - They are pointless, and won't fix the real problem.

 
HOWTO: Blizzard Downloader

for wine versions 1.12 and earlier:

you need a native mshtml.dll and wininet.dll from ie6sp1 in ~/.wine/drive_c/system32

dont forget to set them as native in winecfg


 
Easy installation: digital download

If you own a legitimate copy of Diablo II, you can register it on battle.net with the serial key, and get a link to an installer (about 1.4GB).

This installer has less issues than the CD version, and is the recommended way to install Diablo II.  It works flawlessly (Platinum) from begining to end.


 
ALT+CLICK combination

Window managers often have the alt key bound to certain features, especially the alt-click. This is not a wine bug. If you have problems with the alt key in any way do not report it. Fix your window manager. I'm not going to list steps for every one because there are too many possibilites. Figure out yourself or ask in a help forum (here is okay... but be warned all I use is TWM). If you are desperate, turn off window manager managed windows in winecfg.

KDE

Go into KDE Control Center, expand Desktop, click window behavior, then click window actions tab. You can turn off the alt-combos. If you want to make window specific settings, click on window specific settings under window behavior on the side.

GNOME 2

The option to change the key binding is in System Menu -> Preferences Menu -> Windows.

 
HOWTO play without mounting a CD
­As of 1.12, it is possible to play without u­sing a CD.
The following is an excerpt from the patch changelog:­

­For users that originally performed a ‘Full Installation’ and wish to run without the CD, all ‘.mpq’ files should be copied from the Diablo 2 CDs to the Diablo 2 directory. Most users will only need to copy D2Music.mpq from the Diablo 2 Play CD and/or D2xMusic.mpq from the Lord of Destruction CD.

Anyone who did not perform a ‘Full Installation’ will need to  re-install from CD again to ultimate­ly play without the CD. In this case, a ‘Full Installation’ is required, followed by file copy step noted above.

 
How-to fix delay in sound

If your game is suffering from a slight delay in sound, then try following these steps:

  1. Open the Wine Configuration Application (Configure Wine)
  2. Click the "Add application..." button
  3. Browse to your Diablo II folder (usually Program Files/Diablo II)
  4. Click Diablo II.exe, and then Open
  5. Select Diablo II.exe from the list: it should turn blue
  6. Go to the Audio tab (it can take a while to load)
  7. Untick ALSA and tick OSS, and you're ready to go!

 
Installation using the CDs

Running Diablo 2 under Wine

by Jesse Allen the3dfxdude at gmail com

minor updates by Jasmine Iwanek

Last updated 2008-07-11 - wine-1.0.0/1.1.1

Before you get started

This HOWTO only lists information specific to this app. Please keep comments and test reports brief. Please don't post copies of wine logs here! If you have trouble, see other ways of getting help.

Wine+Diablo 2 Status

Generally perfect for Linux users since wine 0.9.12. FreeBSD kernel 6.2 might work, but copy protection will likely be broken.

Minimum Requirements

  • winecfg: A drive letter for your cdrom, and running as Win2k, XP or later.
  • Support for 640x480 and 800x600 video modes.
  • Correct network configuration for online play.
  • A REAL COPY OF THE GAME -- The game probably won't work right if you don't have a real copy.

Recommended Requirements

  • Wine 0.9.20 or later
  • Linux kernel 2.6.17+ OR FreeBSD 6.2
  • Video card and driver that supports hardware based acceleration with OpenGL.

**Bad Versions**

It's recommended to not use these versions of software because they break the game's copy protection:

  • Linux vanilla x86 kernel: 2.6.9, 2.6.10
  • Linux vanilla x86-64 kernel: 2.6.9-2.6.15
  • Linux kernel versions less than 2.6
  • Wine built with GCC 4.0.0-4.0.2
  • Native msvcrt.dll
  • Fedora core 6 modified linux kernel, unless updated to 2.6.18-1.2784.fc6 or later.
  • FreeBSD
  • Incorrectly installed video drivers

Additionally, FreeBSD kernels less than 6.2 might not work with current versions of wine at all.

Installing the Game

Launch winecfg to perform the following tasks:

  • Make sure the Windows version for Diablo 2 is NT 4.0, 2000, XP, or 2003 for correct copy protection support. Diablo 2 supports Win NT 4.0 or later.
  • Create a drive letter for your cdrom if you have not already. For each cdrom drive letter, click advanced, and set the drive type from automatic to cdrom.

It helps to add a device node symlink, so do the following. If your cd-rom drive letter in winecfg is d: and the corresponding device node to your mount point is /dev/hdc then run the following command:
$ ln -s /dev/hdc ~/.wine/dosdevices/d\:\:
Note, you *must* have two colons! You can tell what your device node is in /etc/fstab or viewing your boot-log.

For running the multi-disk install, it helps to run the install using the drive letter and to not switch your shell to the cdrom's path. For example:
~/.wine/drive_c$ wine "D:\setup.exe" (where D: is the assigned letter of your CD drive).
If you run while having a current working directory of /mnt/cdrom, for example, then you will lock the drive and you won't be able to eject the disk.

If during the game's install the progress bar stops, the game is probably prompting you for the next disc, but the dialog is under the installer's window. For full install, the order is Install Disc, Play Disc, then Cinematics Disc. Just swap discs and hit enter when the progress stops.

Running and Playing Diablo 2

Do not use the '-opengl' switch to run the game. Blizzard never completed OpenGL support so they removed it, but left the switch in. All you see when you run it is a badly initialized DDraw mode.

If you use the window option "-w", the game will drop to ddraw mode no matter what.

Do not use virtual desktop with the game! It's not designed to be windowed like that! It still thinks it's full-screen!

If you have missing in-game speech, animation, videos, or crashes between acts, these problems are typically from using a modified executable. Install your game properly.

Multiplayer Setup

Make sure you have the correct ports open. Open outbound and inbound, TCP and UDP, port 6112 and 4000. More on Network Ports

If you are going to play a direct TCP/IP game and the game tells you that it could not detect a valid address, make sure about things:

  1. Have a valid internet addressible IP address for internet play or proper NAT forwarding.
  2. Have a hostname other than localhost.
  3. In /etc/hosts, have a valid hostname of your computer listed with your current IP address you want to use and do not have your hostname listed with 127.0.0.1. Do not have "localhost 127.0.0.1" listed first either.

 
Window losing focus

When running the game in Windowed mode (-w switch), if the DIablo II window loses focus, the game freezes. To unfreeze the game press Alt+Enter. So far this has been tested in:

  • Ubuntu "Hardy" 8.04.1 with Gnome

 
HOWTO fix the 'patch archive is corrupt' issue

I order to correct this issue Wine must run Diablo II from inside Diablo's installation directory.  Here is an example:

  1. Run a terminal
  2. Type:  cd ~/.wine/drive_c/Program\ Files/Diablo\ II/
  3. Type:  wine ./Game.exe

 

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Confused
by Tom Raate on Wednesday January 2nd 2013, 6:23
I have installed Diablo 2 via Playonlinux completely fine, patch works fine and everything . However when I try to install the expansion, it keeps telling me I must have the original game installed in order to continue . Any way to work around this ?

[post new] [reply to this]

Program would close after changing resolution.
by Lex on Thursday May 31st 2012, 14:53
Program will start, change the resolution to 640x480 and then would close before even starting the first video with the "Blizzard" logo.

Using the most recent Debian build on Mint Debian. Patch 1.13 installed.

[post new] [reply to this]

Mouse Jumps All Over...
by Jason Marty on Friday March 30th 2012, 23:49
Running wine 1.5 (and earlier), the mouse pointer jumps all over the place when in-game. No problems exist when using the menus, but when attempting to move the character the mouse cursor goes nuts. The pointing finger will literally jump all over the screen with even minor movements of the mouse. However, it seems the "actual" location of the pointer moves correctly, its just rendered wrong. Running an up-to-date version of Arch Linux with the latest wine. It seems this might be an issue with some other library/package, because even the version of Wine that use to work fine for me with this game no longer works. Here is my output when running the game from a terminal:

[ poeticrpm@geekdom games]$ sh diablo.sh
err:service:validate_service_config Service L"Bitolmgsvmmv" has an unknown service type (0x100)
err:service:scmdatabase_load_services Invalid configuration of service L"Bitolmgsvmmv" - skipping
fixme:service:scmdatabase_autostart_services Auto-start service L"dxregsvc" failed to start: 2
fixme:advapi:SetSecurityInfo stub
fixme:win:EnumDisplayDevicesW ((null),0,0x32f208,0x00000000), stub!
fixme:d3d_surface:wined3d_surface_flip Ignoring flags 0x1.
err:ddraw:ddraw_surface7_Flip Can't find a flip target
err:ddraw:ddraw_surface7_Flip Can't find a flip target
err:ddraw:ddraw_surface7_Flip Can't find a flip target
err:wgl:internal_SetPixelFormat Invalid operation on root_window

[post new] [reply to this]

Diablo 2 LOD 1.13c on Wine 1.3.23 (ubuntu 11.04 32) crashes after playing a few minutes.
by Daniel T. on Wednesday June 29th 2011, 13:44
Hi,

I experience a number of problems: Some tiles seem to be black where backgrounds should be, and after playing some time the game crashes.

Screenshots:
imgur.com/a/aWM29

Dump of the Console (crash is on line 49):
paste.ubuntu.com/635240/

Suggestions anyone?

[post new] [reply to this]

Installation workaround
by foxx on Thursday April 7th 2011, 23:18
I'm on Debian wheezy (64-bit) with wine 1.1.42 and experienced an issue getting the game installed. Mounting the CD-ROMs curiously were owned by a UID without a user assigned and the "dialout" group which naturally disallowed my user from reading the disks. This resulted in a "wine: Cannot find L"D:\\installer.exe."

To get around this copy the contents of all installer disks into a local directory and change the ownership of the files therein to your own user (i.e. "sudo cp /media/cdrom0/* /home/myuser/Desktop/alldisks/" for each disk, then "sudo chown myuser *" within that directory).

The installer only cares about the "installer tome" MPQ files and will *not* prompt for disks for installation if all MPQ files are in the same directory as the installer.exe.

[post new] [reply to this]

Fullscreen mode fixed for patch 1.13
by Jeremy on Wednesday January 26th 2011, 21:44
I discovered a fix to a common graphics issue. I was initially experiencing a bug in which fullscreen did not work. I saw a fix below in which the program is run in windowed mode, but I just found an alternative for Ubuntu users that lets you run it just fine in fullscreen: I'm running Wine in Ubuntu 10.04. For me, in the GUI I went to System > Preferences > Appearance > Visual Effects and selected "None". I can now run Diablo II normally in fullscreen mode as opposed to windowed.

[post new] [reply to this]

d2multires mod
by Chauncellor on Monday November 29th 2010, 19:03
The hi-resolution mod that allows more than the meager 640x480 or 800x600 resolutions does not work with the latest patch (1.13). You need to patch Diablo 2 only to 1.12 in order for the mod to work.

If you do have 1.13 installed it supports a hideous scaling mode. If you start Diablo 2 in windowed mode (i.e. 'wine game.exe -w' and then maximize the window it will be more usable (albeit grossly unappealing)

[post new] [reply to this]

Diablo 2 Lord of Destruction cd not detected
by Logan Abney on Friday July 23rd 2010, 19:38
System: Ubuntu 10.04
Wine Version: 1.2

So, I'm running out of things to try, and I wanted to post this here, in case this was a regression or something, though I doubt it.

I seem to be one of the first people to run into this, and I can't establish why it won't work. I'm willing to try anything, but I am a new user, only installing Ubuntu 10.04 about a week or two ago. I managed to get Wine configurated and working following the instructions, although there are graphical errors, may or may not be from full screen, whatever, haven't tried. I'm now onto the expansion CD, only, it's telling me it isn't detected, which is strange, because the physical CD is in the drive. Checked it out, as it's an original copy from release, and no scratches or dings. Any tips?

I've tried mounting an .iso copy, but I think the .iso was bad, wouldn't mount. I can do it again, but I'd like to fix it from a system point of view.

[post new] [reply to this]

X Mouse Cursor on Top of Diablo Cursor
by Jason Marty on Friday May 14th 2010, 7:22
Diablo 2 LOD V1.12
Arch Linux x86_64
Nvidia 195.36.24
Occurs on: Wine 1.1.44
Does NOT occur on: Wine 1.1.41

When playing Diablo 2, everything else seems to work fine: gameplay is smooth, items can be picked up, and mouse functions as normal. However, the X mouse cursor (whatever one used in your X environment) is on top of the glove/finger in-game cursor of Diablo 2 at all times, even as you move the mouse.

On Wine 1.1.41 the issue is not present and everything seems to work fine. I do not have versions 1.1.42 and 1.1.43 available for testing, although I could probably edit a pkgbuild if necessary to do regression testing. Dont want to give it such a review if its only on my machine- Anyone else having this issue?

[post new] [reply to this]

D2 Minimizes to Desktop Icon & How do I constrict the mouse?
by Loafers on Thursday March 11th 2010, 0:05
Hi,

I'm running wine-1.1.39 under Arch Linux with Openbox as my standalone window manager. Whenever I switch desktops or minimize the game, D2 never minimizes to the taskbar, instead it creates a Desktop icon that is superimposed over everything...

Also, is there a way to constrict the mouse inside Diablo 2 Window Mode?

Regards,
Loafers

[post new] [reply to this]

D2X on Debian Lenny working flawlessly
by RJ Trenchard on Monday March 8th 2010, 19:37
wine version 1.0.1 (whatever came with apt)

I had issues at first because I installed from windows, and then figured i would give it a shot on linux - which took a great deal of time

first things first, Diablo 2 needs write access to the working directory for bnet access or you will get frequent disconnects when it tries to.

The MPQ files must be in the original install directory (or whatever d2x thinks is the original install directory) for the sound to work, it will work at first by the active directory, if the mpq files are there, but when you switch to multiplayer or exit out of singleplayer it will try to load from the directory it thinks it was installed in. (in my case D2X was installed to /media/ntfs/DiabloII/ but the MPQ files are doubly located in ~/.wine/drive_c/DiabloII/, i lacked for foresight to set Drive C to my NTFS partition, but in the end its probably better that i didnt)

had to switch off the window manager options under the Graphics tab in winecfg, and while i was messing with the audio drivers, the prepackaged ALSA drivers actually worked perfectly (as all the sound issues was caused by problems loading missing mpq files)

finally, and a given, do not run as super user - as it seems to mess up the CD Key check. I did it because I thought that maybe it was, somehow, the cause of my sound issues. thankfully it wasnt.

Computer model: HP Pavilion DV8000 Laptop
2.4 GhZ AMD64 CPU, 1GB memory, 256MB embedded ATI video, generic Conexant Audio.

[post new] [reply to this]

Available Video Modes: DirectDraw or FORCING D3D.
by Hack-a-matic on Thursday December 3rd 2009, 2:26
I dont know if anyone would need that, but anyway this is how to force Direct3D. Look at the end if you dont want to read much. You need 3 minutes time.

If you have a modern nvidia card and get message about only DirectDraw being possible. It seems a bug in diablo2 detector.

You can either install and use Glide wrapper, which would give you more resolutions and enable perspective support as well.

But I found out glide wrapper uses very much resources(Athlon xp 3200+, gf6800, Xorg uses 80%). Slowdown was noticeable especially in kurast docks.

Or you can manually force d2 to use Direct3D. It is possible.
Note I had Glide wrapper previously installed, but never the less it won't be used; so if it doesn't work, dont hestate to report.

FORCING direct3d IN DIABLO II:

0) Open terminal
1) $wine regedit
(if you use Playonlinux or if you have it installed in separate prefix, the command would be "$WINEPREFIX= wine regedit", in case of POL: "$WINEPREFIX=~/.Playonlinux/wineprefix/ wine regedit"
2) in regedit window, navigate to: HKEY_LOCAL_MACHINE/Software/Blizzard Entertainment/Diablo II/VideoConfig
3) set DeviceDDraw to 0(0x00000000).
4) set DirectDrawDevice0 to 1(0x00000001).
5) set DeviceName0 to "DirectDraw HAL"
6) set DeviceName (without 0) to "Direct3D"
-) you would probably benefit, if you set VidTestRequired to "false"
-) also, I have Render set to 3(0x00000003), no idea why.

Exit and launch game. It should be now set to d3d. You DONT need directx override, just vanilla wine. Dont launch VidSet again. Exit if you did. Otherwise you need to manually reset that again.

[post new] [reply to this]

WooHOO!
by inop on Sunday September 20th 2009, 8:12
I didn't even have to install a 2nd copy on my linux partition, it worked Platinum from my Windows drive! :) Everything, including D2Multires (www.widescreengamingforum.com/forum/viewtopic.php?t=16131), saved games, and even LAN play! I didn't try battle.net, not good enough to hang in "real" multiplayer ;P All I had to do was winecfg and point a drive letter to my windows install dir. Between this and Fallout 3 working in Linux, I am /this/ close to ditching windows all together!

[post new] [reply to this]

Regarding running without CD
by Bryan DeLuca on Thursday August 6th 2009, 16:14
The necessary files that need to be in the Diablo2 directory are as follows.

From the Original Diablo 2 Install discs

D2MUSIC.MPQ

From the Expansion discs:

D2XMUSIC.MPQ and D2XVIDEO.MPQ

[post new] [reply to this]

Running with a parameter
by Asteroth on Saturday July 4th 2009, 16:33
I need to run Diablo with a -direct parameter. No matter how I try to place it in the shortcut it does not work. The -w parameter works fine though.
I tried also typing in the terminal:
asteroth@skyeye:~$ env WINEPREFIX="/home/asteroth/.wine" wine C:\Diablo II\diablo2\game.exe -direct

If I run wineconsole cmd, cd into Diablo directory and type
game.exe -direct
Everything works like it should

[post new] [reply to this]

Out of range
by Casey Schellhorn on Tuesday May 12th 2009, 21:05
When I try do run LoD i get a black screen with a message from my monitor that says "out of range". The opening videos work just fine but the main main screen does not. Any help is appreciated.

[post new] [reply to this]

alt-enter no longer works in 1.1.20
by Twig on Monday April 27th 2009, 16:13
Hi,

Just wanted to let people know that, following the patch to fix hanging on losing focus in the recent 1.1.20 version, it is no longer possible (in Ubuntu at least) to press alt-enter to resume play.

It is possible to click the minimise all windows and show the desktop button and then click Diablo 2 from the task bar in order for the program to start responding again. However, on my system this leaves the task bar still visible in full screen mode.

Hope this helps,
Twig.

[post new] [reply to this]

RE: Available Video Modes: DirectDraw
by HAARP on Sunday March 8th 2009, 8:15
Then post and vote for bug 17503. Only if devs see that people care about this bug will it get fixed.

[post new] [reply to this]

Problem with fullscreen.
by Gordon Stephens on Wednesday February 18th 2009, 19:18
Hey.

I had everything working fine with this, in both fullscreen and windowed, but today I turn my computer on, and can't run Diablo in fullscreen.

If I run in windowed:

gordon@gordon-desktop:~/.wine/drive_c/Program Files/Diablo II$ wine Game.exe -w
fixme:advapi:SetSecurityInfo stub

Works fine, loads up in a window.

But if I try to run in fullscreen, I get:

gordon@gordon-desktop:~/.wine/drive_c/Program Files/Diablo II$ wine Game.exe
fixme:advapi:SetSecurityInfo stub
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 159 (GLX)
Minor opcode of failed request: 19 (X_GLXQueryServerString)
Serial number of failed request: 25627
Current serial number in output stream: 25627
gordon@gordon-desktop:~/.wine/drive_c/Program Files/Diablo II$

It was working fine yesterday, I havent changed anything relevant, to the best of my knowledge.

I upgraded to wine x.15, but problem remains the same.

Ideas?

[post new] [reply to this]

RE: Available Video Modes: DirectDraw
by João on Thursday January 8th 2009, 10:55
Another with this problem..

I'm using Ubuntu Intrepid with Wine 1.1.12 and a GeForce 9500GS with the Nvidia proprietary drivers

[post new] [reply to this]

RE: Available Video Modes: DirectDraw
by Peter Henriksson on Monday January 5th 2009, 11:37
Same thing here.
With a GeForce 8800 GTS and the binary Nvidia driver.

[post new] [reply to this]

With regards to people having windowed mode problems
by Tapan Oza on Saturday December 20th 2008, 15:47
Although I havent tried using the -w command I would think that this work around be satisfactory to most:

run winecfg. Select emulate a virtual desktop and enter the resolution that you are playing diablo 2 at.

[post new] [reply to this]

bad/static/unsynced sound
by ken on Monday November 3rd 2008, 2:37
when i upgraded to wine 1.1.7 from 1.1.1, i had horrible sound. after much searching i found an old solution that worked with wine 1.1.7:
ubuntuforums.org/archive/index.php/t-422646.html
should i submit this as a bug?

[post new] [reply to this]

Improved GFX (REMEMBER THIS)
by HoodedMan on Sunday August 3rd 2008, 10:00
To get higher resolutions and somewhat better GFX you can download the Glide3 to OpenGL wrapper at www.svenswrapper.de/english/index.html

Unzip the download and move the dll and exe into the Diablo 2 directory.
Now run the executeable "D2VidTst.exe" which runs the video test again. Because of the wrapper, you can now use the glide-renderer -- do this!

Now you can configure the glide wrapper through "glide-init.exe".

For me, Diablo 2 fullscreen did not work until I got this, ran glide-init.exe and selected "Desktop resolution" under "Settings".

This means that the game will take your native resolution, so if you run 1280x1050 then Diablo2 will run in 1280x1050 glory :P

If you have a widescreen, like 1280x800, 1440x900, 1680x1050, 1920x1200 or otherwise, Diablo 2 will run with the maximum 4:3 window it can fit inside of that widescreen, meaning you'll have some black bars on either side.

But the higher resolution is still there so you have a much better view of the game world. It's absolutely awesome ! :)

[post new] [reply to this]




   << Back

Page loaded in 0.18055 seconds.