![]() ![]() *4) The ddraw.dll file in the directory shows the following information when you hold the mouse over it: Run this program in compatibility mode for: Windows XP (Service Pack 3) *3) Diablo has the following Compatibility options set, and no others (right click on it or its shortcut, then choose Properties and go to the Compatibility tab): *2) Diablo is not located anywhere inside a special Windows folder, such as Program Files, My Documents, or other user folders it should be in a path such as C:\Games or something else you created, so Windows won't restrict the game's folder from the game itself with weird UAC security policies ![]() ![]() *1) Diablo is patched to v1.09 (not sure how to tell when you can't start the game, normally it displays in the menu in the bottom left corner if you're not positive it is patched to the latest version, download the latest official patch from Blizzard here and make certain you right-click the patch and run it as an administrator - Blizzard has a v1.09b as well, which is fine, either version will do but the game will display v1.09 either way) So, assuming it is the same issue your laptop is having now, this is worth a test just to be sure. Not sure if a Windows update triggered it or what but it crashed on launch after that just like yours, until I found the wrapper you're having trouble with, which let Diablo and Hellfire run once again on it. At one point I had a similar issue where my installed & patched Diablo worked on Win 8 but stopped working spontaneously one day, and I hadn't done anything with the computer lately. I realize you probably checked/tried many of these already, but if you match all of this exactly I'm curious if it still doesn't work. Alright, here is virtually every relevant current condition that Diablo 1 is running on my seldom used Windows 8.1 laptop. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |