11-16-2016, 10:59 PM
(This post was last modified: 11-16-2016, 11:00 PM by Red Hairdo.)
Just posting a little update: I succeeded in patching with versions 1.03 and 1.04. I was required to make the Drive letter of my CD Drive match with whatever the patch executables were expecting, so for this purpose I temporarily changed the drive letter (which in this case was D), by doing the following, in case this helps anyone else someday:
Right-Click on Computer > Manage > Disk Management > Right-Click on the Drive whose letter needs to be changed > Change Drive Letter and Paths... > Change... > Select the correct letter on the dropdown box to the right (if you don't know the letter, try them all, although I suggest D and up.)
No luck whatsoever with version 1.02, however. I have no idea why it keeps telling me my diabdat.mpq file is not valid. (Nor why that particular patch expected a completely different drive letter, but that shouldn't matter.) I even tried another Diablo CD, the one that comes with the game files both for Mac and Windows (the one which comes pre-patched with v1.04 on Mac and provides separately the v1.04 patch for Windows), but no luck. Same issue.
I pretty much feel I ran out of options. The only thing I can think of right now is booting up a Windows 95 Virtual Machine just to try patching it there.
Right-Click on Computer > Manage > Disk Management > Right-Click on the Drive whose letter needs to be changed > Change Drive Letter and Paths... > Change... > Select the correct letter on the dropdown box to the right (if you don't know the letter, try them all, although I suggest D and up.)
No luck whatsoever with version 1.02, however. I have no idea why it keeps telling me my diabdat.mpq file is not valid. (Nor why that particular patch expected a completely different drive letter, but that shouldn't matter.) I even tried another Diablo CD, the one that comes with the game files both for Mac and Windows (the one which comes pre-patched with v1.04 on Mac and provides separately the v1.04 patch for Windows), but no luck. Same issue.
I pretty much feel I ran out of options. The only thing I can think of right now is booting up a Windows 95 Virtual Machine just to try patching it there.