Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UXL Launcher might not work with Office 2010 Home and Student and Home and Business. #70

Closed
DrewNaylor opened this issue Mar 14, 2017 · 7 comments
Labels
app launch code basically closed Not ready to be actually closed yet, but it pretty much is closed. important issue known issue options and settings

Comments

@DrewNaylor
Copy link
Owner

DrewNaylor commented Mar 14, 2017

Office 2010 Home and Student and Home and Business use Click-to-Run like some other recent versions of Office, but the files are stored in a disk partition (drive Q:) that isn't accessible to users. This means UXL Launcher can't open the programs as expected with the current application launch code. However, it may be possible to directly launch the program's EXE file without specifying the path. This relies on Windows running the "WINWORD.EXE" file that the user expects when clicking the "Microsoft Word" button.

See this page for more info on Click-to-Run in Office 2010: https://support.office.com/en-us/article/Learn-more-about-Office-2010-Click-to-Run-9948b3a9-e3ef-4d73-b645-727bb2d9e365

I think I can just recommend to users to enable the Office 365 checkbox in the Options window by the Office 365 tooltip text if they use Office 2010 Home and Student or Home and Business. I also mentioned this with 2016 in Issue #69. That won't work, since the path can't be used in this situation. Maybe just have a "path bypass" checkbox instead.

@DrewNaylor
Copy link
Owner Author

Actually, the checkbox will soon be named "Compatibility Mode" and will be used if the user has any trouble and they set all the other settings to what they should be. See #75.

@DrewNaylor
Copy link
Owner Author

I guess I don't need this issue open anymore.

@DrewNaylor
Copy link
Owner Author

Actually, it looks like Office 2010's Click-to-Run used drive Q:\ instead of C:. I don't know if the Office drive location can be changed to "Q" instead of "C" to make these versions work.
https://support.microsoft.com/en-us/help/982434/an-overview-of-microsoft-office-click-to-run-for-office-2010

@DrewNaylor
Copy link
Owner Author

Actually, maybe this is important. Q:\ isn't accessible with Click-to-Run Office 2010.

@DrewNaylor DrewNaylor reopened this Apr 3, 2019
@DrewNaylor DrewNaylor pinned this issue Apr 3, 2019
@DrewNaylor DrewNaylor changed the title Office 2010 seems to use Click-to-Run for Office 2010 Home and Student and Home and Business. Office 2010 seems to use Click-to-Run for Office 2010 Home and Student and Home and Business. UXL Launcher might not work with this version of Office. Apr 3, 2019
@DrewNaylor DrewNaylor changed the title Office 2010 seems to use Click-to-Run for Office 2010 Home and Student and Home and Business. UXL Launcher might not work with this version of Office. UXL Launcher might not work with some versions of Office 2010 since it uses Click-to-Run for Office 2010 Home and Student and Home and Business. Apr 3, 2019
@DrewNaylor DrewNaylor changed the title UXL Launcher might not work with some versions of Office 2010 since it uses Click-to-Run for Office 2010 Home and Student and Home and Business. UXL Launcher might not work with Office 2010 Home and Student and Home and Business. Apr 3, 2019
@DrewNaylor
Copy link
Owner Author

As I mentioned in an edit of the original post, I might make a checkbox that completely bypasses the path for people who use Office 2010 versions with Click-to-Run due to Q:\ being inaccessible.

@DrewNaylor
Copy link
Owner Author

See #109 for how the configured path can be bypassed.

@DrewNaylor
Copy link
Owner Author

This is basically closed unless it turns out that the option to bypass configured location for all compatible apps doesn't help with Office 2010's implementation of Click-to-Run, in which case I don't know what to do. This'll be closed after UXL Launcher version 3.3 is out as stable.

@DrewNaylor DrewNaylor added the basically closed Not ready to be actually closed yet, but it pretty much is closed. label Apr 22, 2020
@DrewNaylor DrewNaylor unpinned this issue Jul 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app launch code basically closed Not ready to be actually closed yet, but it pretty much is closed. important issue known issue options and settings
Projects
None yet
Development

No branches or pull requests

1 participant