Universal driver 4.7 upgrade (Network Product)
At 25 OCT 2012 06:18:32PM Martin Bell wrote:
We recently upgraded from Universal Driver 4.0 to 4.7. While running the Universal Driver Manager earlier today, I noticed that there was lock for the SYSLOGINS table for the 4.7 folder (UD_MANAGER) *and* a lock for the SYSLOGINS table for the 4.0 folder (LH MANAGER).
Although I went back to check the upgrade instructions, I don't see any mention of a de-install for 4.0. Should that folder and subfolders be deleted for 4.0? And why should there be a lock in both places, as in, what is looking in the 4.0 version? I confirmed that the Win2003 service is pointing to 4.7, and I did not see any entries in the server registry pointing at 4.0.
Any suggestions?
At 30 OCT 2012 05:39PM Jared Bratu wrote:
Martin, although we spoke regarding this issue I wanted to leave a response for everyone else.
There are no dependencies between the 4.0 and 4.7 versions. I suspect you may have accidentally clicked the icon for the 4.0 UD Manager and it tried to login. Regardless of how the lock came to display the manager is not closely tied to the LinearHash service and I don't see any negative impacts from this lock appearing.
To de-install a Universal Driver here are the steps:
[list=1]
Log everyone out
Open a command prompt in the directory where the lh40srvc.exe is installed.
Run the command lh40srvc.exe remove
Delete the registry HKLM\SOFTWARE\WOW6432Node\Revsoft\Revelation Universal Driver\4.0
Remove the folder where the lh40srvc.exe is installed
[/list]
Please let me know if you have any further questions.