v1.40 - Maintenance Release Feed-back Thread - UVLoD mod for Diablo II: Lord of Destruction

Greetings,

Feed-back is needed on v1.40 new Installer:

This is a maintenance release that only fixes bugs in 1.39, but includes the installer from 2.0 series.
I need to test out the new installer and get feedback before deploying 2.0 series.

If you encounter an issue, please indicate what OS your using and type (32 or 64 bit). Post a screen shot with the error message in this thread: You can upload the screen shot to your profile & paste it in an image. like so.

Tested So far

XP 32Bit
Win7 64 Bit
-Win10 64 Bit
-Win7 32 Bit in Virtual PC
-Win7 32 Bit in Virtualbox

Edited by: devurandom96

Alright so, on Windows10, I restored my D2 install to its original state (stock Patch_D2.mpq, D2_Win.dll and delete UVLoD.dll) in 1.13d

And I ran the installed, it seems it worked well. I've chosen the closed mpq option. Can you confirm you did not update the version number on the bottom-left of the home menu? My game still shows uv139, so it's somewhat confusing. Maybe I've forgot some files from the previous 1.39 install?

Also, I update my GoMuleX using your script, if I select the 3rd choice (v200uv) it seems to break my gomulex stash. If i come back to the 2nd choice (v138-199) it works again.

I'll do a few runs to see if everything works as before!

PS: the 1.39 nodropmod, how do I install it now? I suppose I can't just copy the D2_Patch.mpq, can I?

Hey,

Yes.. there is a mistake in the version number it should be 1.40.. will upload again later today to fix that.
v200UV is not released yet it supports stackable Pandemonium Keys.

Also The installer will detect if your running a patched D2win.dll from previous versions of UVLoD and replace it with a clean copy.

1.39 nodropmod is quite similar to the vanilla mpq except it is closed txt. Yes you can just copy the Patch_D2.mpq into where ever your Diablo II is installed.

Are you running win10 32 or 64?

Thanks!

Edited by: devurandom96

Hey, Windows 10 x64

First time I used the new installer I used it on a clean 1.13d backup. Installed without a problem, uninstall worked good too.

2nd time I tried to overwrite UVLoD 1.39 on 1.13d, also worked as intended.

So far from playing characters from 1.39 and a new test one from 1.40 everything seems fine. If anything else comes up I'll post, but it seems good so far.

Edited by: aledar4

Hey Aledar4,

Awesome..Thank you for the report Good to hear.. we can check win10x64 on the list!

:)

Alright, so everything worked perfectly here as well then! I am using Win10 x64 as well

Ok.. good to hear.. I think we're probably good on all versions x64.. Hope to hear from people with x32 on vista and above. install path detection routine, and fixing permissions issues is slightly different for those versions.

Edited by: devurandom96

Installed x32 Vista SP2 on a VM today. Path detection works fine, permissions does not however. Had to manually run it as administrator to get the game start.

Thanks for testing this. Did the installer print any error message related to permissions, or just the usual "set/fixed permissions"?

The usual one. Nothing wrong on the log either.

Edit: Okay, this is weird. While checking the registry, I've noticed that there was no entry on HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers, nor on the HKEY_LOCAL_MACHINE. AFAIK they are the places for the compatibility/permissions flags.

Edited by: imert95

Those are the keys it should update in the registry. The installer only updates one of those keys to set permissions on the shortcut for ALLUSERS.
Strange thing is that it uses the same routine to open the InstallPath key as it uses to update permissions for x32.

If you don't mind me asking.. which VM do you use?

Edited by: devurandom96

I'm using Oracle Virtualbox.

Thanks for testing and info. I may have to install win7 x32 in VM to see what it does.

EDIT:

Installed in Microsoft Virtual PC Win7x32 permissions work as expected for that particular VM, but it looks like I'll have to adjust path detection for Hero Editor in vista, win7 to find the VirtualStore.

Still need to test in Virtual Box to see whats going on there.

EDIT2:

1.40.3 fixes issues:

- Installer: checks if GoMule has not been updated to GoMuleX
- Installer: Hero Editor.ini path detection for non admin installs in Vista, Win7 etc.

Was able to repeat the issue that Imert96 pointed out on VirtualBox, and I'll fix it as soon as I can.
Thanks!!!

1.40.4 should fix Virtualbox permissions.

Edited by: devurandom96