BUG: Certain shortcuts do not launch program after dragging to L5 Shortcut bar
I have an old installation of Zondervan Bible Software on Win 7x64 (so old that I had to install XP Mode and install into that because certain installed files were 16-bit). It works perfectly now though.
But there's a problem - I created a Windows shortcut file to launch the main Zondervan executable (ZRS32.EXE) and load a workspace file in a single action.
If I double click this shortcut in Explorer, everything works as expected - ZRS32.EXE loads and then loads up the workspace file, but when I first drag the same Windows shortcut onto the L5 shortcut bar then click it, nothing happens.
Comments
-
I can't reproduce this, but I do know we don't actually support Zondervan software. My first guess would be that since the program requires XP mode to run, and Logos 5 doesn't support XP, that's the conflict. If you experience this with shortcuts for other, more modern programs, let us know.
0 -
Just to clarify ... I can run ZRS32.EXE just fine in Windows 7. It was only the setup process that required XP mode - normal operation is fully 32 bit so works fine.
Also, if I drag ZRS32.EXE onto the L5 shortcut bar and click it, Zondervan will run. The problem only occurs when I supply the workspace .SES file as a command line parameter in the shortcut.
0 -
Sorry, what I meant by "don't support" doesn't mean that the program won't run, it means that we don't plan to implement around it. The simple thing would just be to tab out of Logos and run it via Windows. I apologize that this isn't ideal.
0 -
Yes, I shouldn't have mentioned XP Mode at all as it isn't relevant to the running of the software. The installed software runs fine in Win 7x64, so any conflict causing the shortcut not to work has nothing to do with XP mode at all.
It's easy enough to work around but I'm interested about why the shortcut doesn't work, and if it's part of a wider issue about L5's ability to launch other software from the shortcut bar. For example, does this mean that no standard Windows shortcuts will work if they contain command line parameters?
Thanks
Richard0 -
I have tested several shortcuts with command line parameters and they seem to work just fine, so I would assume its the association with the .SES filetype that is unsupported. I'll double check with a developer and update this thread if it's something that will be fixed, but since we don't directly support other programs like that, it will likely remain as is.
0 -
OK thanks - not a big thing. Just one extra click to get it going.
0
