Reclaiming the libronixdls protocol

Some of you have run the scripts to download your L4 books into Libronix or have installed Libronix after Logos 4 and have found your hyperlinks opening Libronix and not Logos 4.

This can be fixed with a registry edit.

http://wiki.logos.com/Hyperlinks has instructions, if you are interested and are adventerous enough to look at the registry.

Find more posts tagged with

Comments

Alan

Thanks Kevin. Now to find a a way to get the LibronixDLS.LbxApplication to work so I can get all my MS Word macros up and running.

Rosie Perera

Some of you have run the scripts to download your L4 books into Libronix or have installed Libronix after Logos 4 and have found your hyperlinks opening Libronix and not Logos 4.

This can be fixed with a registry edit.

http://wiki.logos.com/Hyperlinks has instructions, if you are interested and are adventerous enough to look at the registry.

Kevin, you might need to clarify your instructions a tiny bit. The libronixdls key appears in up to six places in the registry (at least in 64-bit Vista; I'm not sure the Wow6432Node nodes appear for others), and you might need to change it in more than one place.

HKEY_CLASSES_ROOT\libronixdls
HKEY_CLASSES_ROOT\Wow6432Node\libronixdls - same as above
HKEY_CURRENT_USER\Software\Classes\libronixdls
HKEY_CURRENT_USER\Software\Wow6432Node\Classes\libronixdls
HKEY_LOCAL_MACHINE\Software\Classes\libronixdls
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Classes\libronixdls

I think some of these affect others if you change them (e.g., changes in HKCR affect HKCU), but on my machine the first four were pointing to L4, whereas the last two were still pointing to L3, until I fixed them. But I only had to edit one of the last two and the other one changed.

Kevin Becker

https://community.logos.com/discussion/comment/58417#Comment_58417

Rosie,

I walked someone through changing just one key earlier and it worked in restoring the use of Logos 4 with the libronixdls hyperlinks. Registry hacks are a little out of my comfort zone and I only put this on the wiki because it worked for him ( http://community.logos.com/forums/p/7242/58117.aspx ). I personally haven't had this problem.

I've been scanning my registry for the keys you mentioned (I'm Win 7 64 bit)

HKEY_CLASSES_ROOT\libronixdls - Present, one advising people to change on the wiki
HKEY_CLASSES_ROOT\Wow6432Node\libronixdls - same as above - Not on my machine
HKEY_CURRENT_USER\Software\Classes\libronixdls - Present, but still points to LDLSExec.exe
HKEY_CURRENT_USER\Software\Wow6432Node\Classes\libronixdls - Not present
HKEY_LOCAL_MACHINE\Software\Classes\libronixdls - Present, but key value not set
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Classes\libronixdls - Not present on my maching

I found two different ones on my machine:

HKEY_USERS\S-1-5-21-1076116825-4290941683-1299585774-1001\Software\Classes\libronixdls - Still points to LDLSExec.exe
HKEY_USERS\S-1-5-21-1076116825-4290941683-1299585774-1001_Classes\libronixdls - Still points to LDLSExec.exe

So, it appears that the keys on my machine that still point to LDLSExec.exe don't matter when it comes to the hyperlink working properly. I've gone ahead and put some extra language on the wiki to allow for the need to edit multiple keys, but from my experience, it looks like you don't have to. Thoughts?

Rosie Perera

https://community.logos.com/discussion/comment/58448#Comment_58448

I think it depends on who you log in as. If you only ever log in to your Windows machine under one profile, then this should be fine. If you have more than one (for yourself, not for other members of your family, that is), then I think you'd need to change the other registry keys. HKEY_CURRENT_USER affects only the user who is logged in now. HKEY_USERS has a unique id for each user who can log on. I'm not sure about HKEY_LOCAL_MACHINE.

On the other hand, you might want to keep a separate Windows login for L3 as long as you're still using it, especially if you're playing around with the beta of 4.0a -- just in case it messes something up in your Windows installation. Not likely at this point, but you never know.

Dave Hooton

https://community.logos.com/discussion/comment/58483#Comment_58483

HKCU normally points to Logos 4 (because it installs per-user).
However, running the 3.0g update overwrites this value to point back to
LDLS3, which stops links opening in Logos 4.
HKCR is not its own storage location, but simply a unified view of HKLM\SOFTWARE\Classes and HKCU\Software\Classes.

To fix the problem, open Registry Editor, navigate to
HKEY_CURRENT_USER\Software\Classes\libronixdls\shell\open\command, and
change the (Default) value to:
"C:\Users\USERNAME\AppData\Local\Logos4\Logos4.exe" %1

where HKCR = HKEY_CLASSES_ROOT, HKCU = HKEY_CURRENT_USER

So it appears that only the one key need be changed as Logos4 installs in a user account, and the wiki should reflect this.

Rosie Perera

https://community.logos.com/discussion/comment/58495#Comment_58495

HKCU normally points to Logos 4 (because it installs per-user). However, running the 3.0g update overwrites this value to point back to LDLS3, which stops links opening in Logos 4.
HKCR is not its own storage location, but simply a unified view of HKLM\SOFTWARE\Classes and HKCU\Software\Classes.

To fix the problem, open Registry Editor, navigate to HKEY_CURRENT_USER\Software\Classes\libronixdls\shell\open\command, and change the (Default) value to:
"C:\Users\USERNAME\AppData\Local\Logos4\Logos4.exe" %1

where HKCR = HKEY_CLASSES_ROOT, HKCU = HKEY_CURRENT_USER

So it appears that only the one key need be changed as Logos4 installs in a user account, and the wiki should reflect this.

If that's the case, then Kevin, maybe you need to redo your screen shot with HKEY_CURRENT_USER\Software\Classes\libronix as the selected key, and fix the instructions to make sure users find this specific instance.

I'm not a great fan of registry hacking either (or at least explaining to others how to do it), because of the risks involved, but I do it myself all the time.

Kevin Becker

https://community.logos.com/discussion/comment/58498#Comment_58498

Rosie, Dave,

Thanks for your input. I discovered that my SR-7 account was broken, but my Beta installation on another User Account wasn't (go figure). I've updated the wiki, with screenshots of me fixing my registry. It works! Let me know if you think it needs improvements (or feel free to make them yourselves).

Dave, thanks for hunting down Bradley's post on this, I had missed that one.

all this registry hacking reminds me I have another one to do... gotta stop those annoying security alerts when I click on my libronixdls hyperlinks in Office....

Dave Hooton

https://community.logos.com/discussion/comment/58753#Comment_58753

Thanks for your input. I discovered that my SR-7 account was broken, but my Beta installation on another User Account wasn't (go figure). I've updated the wiki, with screenshots of me fixing my registry. It works! Let me know if you think it needs improvements (or feel free to make them yourselves).

Looks good, Kevin. Covers all the bases.

Rosie Perera

https://community.logos.com/discussion/comment/58800#Comment_58800

Argggh! I had fixed this and it was working fine, but I've been back to using Logos 3 for a couple of things recently and it grabbed the libronixdls protocol back again. I don't want to have to keep editing it back to point to Logos 4. Any way I can lock it down so Logos 3 won't steal it back again? Or any idea what to avoid doing in L3 that would steal it back again? The things I've done have been: downloaded and ran the "Update Notes Now" script (required to run in order to import notes into L3); installed and ran the "Resource ID Report" script written by Karl Jones. Generated a bibliography. Nothing else major.