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

Lessmsi Explore Failure #100

Closed
computer-dave opened this issue Oct 17, 2017 · 5 comments
Closed

Lessmsi Explore Failure #100

computer-dave opened this issue Oct 17, 2017 · 5 comments

Comments

@computer-dave
Copy link

Hello, just installed lessmsi v1.6.1 using choco and ran into a bug. I ran lessmsi-gui, then went to Edit | Preferences and added the Shortcut Item(s) to Explorer. I then used Windows Explorer to navigate to the folder that was created when I unzipped a recent download, right-clicked on the msi file and selected Lessmsi Explore. What looked like a DOS window flashed on the screen briefly, then the gui was displayed, but it did not open the msi file. At the bottom of the window there was an error message indicating that the download folder did not exist (even though alt-tab switches right to it in an open Explorer window)...

The actual error message text displayed was

"ERROR:File "C:\Users\Username\Downloads!" does not exist."

It appears that LessMSI does not properly support long file names (i.e. embedded spaces), as the name of the folder containing the MSI I was trying to open is

"C:\Users\dllevine\Downloads! NEW (Unsorted)"

It's definitely the embedded space that's the issue - I moved the MSI file to a nice, sensibly-named folder, "c:\temp" and repeated the above steps and LessMSI was able to open the file without any issues.

I use various punctuation marks at the beginning of many of my folder names to ensure that they sort the way I want them to, (i.e. "!" sorts at the top of the list before "A"), and I also rename everything that I download with the actual application name and version (trying to decrypt 8.3 is so pre-Y2K... lol), so the name of pretty much any file that I might be inclined to browse with lessmsi is going to have at least one (though typically more) embedded space. When I go to extract any of the zip files I've downloaded, the folders that get created are names after the zip file, thus the spaces are in the folder names as well.

To use lessmsi as an example, before I installed it using choco, I downloaded the lessmsi zip file. When the download prompt asked me for a filename, it went something like this -
lessmsi was renamed from "lessmsi-v1.6.1.zip" to "LessMSI v1.6.1 (lessmsi-v1.6.1).zip"
this, in turn, created a folder named "LessMSI v1.6.1 (lessmsi-v1.6.1)" when it was extracted.

If there was an msi file in there that I wanted to look at, I'd hit an error there too. :(

Hopefully it won't be too difficult to fix this issue - I suspect that I can't be the only person who's encountered it.

Regards,

  • Dave
@activescott
Copy link
Owner

Thanks for the detailed notes Dave. I'll take a look as soon as I have a chance to spend some time on this project.

@activescott activescott added this to the vNext milestone Oct 17, 2017
@DarrenWhite99
Copy link

DarrenWhite99 commented Jul 19, 2018

I just had this same issue, but the space was in the filename. It reported that the file could not be found and displayed the name up to the space. The filename was like: "C:\users\me\downloads\agentinstall (1).msi" and it said that it could not open "C:\users\me\downloads\agentinstall".

Using LessMSI 1.6.1.0 (From the lessmsi-gui.exe "About" window)

@bhattumang7
Copy link

@activescott I have got a fix for this. Can you please make changes to allow me to push?

@activescott
Copy link
Owner

@DarrenWhite99 @bhattumang7 First, I believe this may have been addressed in released v1.6.2 released yesterday at https://github.com/activescott/lessmsi/releases/tag/v1.6.2 which included PR #86 from another contributor. Can you please confirm one way or the other?

@bhattumang7 I accept pull requests. To get your changes in, please submit a pull request (PR) and I'll be more than happy to review and accept it! More information about how to create a pull request is at https://help.github.com/articles/creating-a-pull-request/

@bhattumang7
Copy link

I agree. This bug is fixed in new release. We can close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants