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

PATH too long #46

Open
mycall opened this issue Nov 30, 2017 · 10 comments
Open

PATH too long #46

mycall opened this issue Nov 30, 2017 · 10 comments

Comments

@mycall
Copy link

mycall commented Nov 30, 2017

I've had success in using this PowerShell script to pack the PATH environment variable, in order to support more directories, and thought I would share it.

clear
write-host "Reading..."
write-host

$fso = New-Object -ComObject "Scripting.FileSystemObject"
$shortpaths = @();
$originalPaths = [environment]::GetEnvironmentVariable("path", "Machine").Split(";")

foreach ($path in $originalPaths) {
$fpath = [System.IO.Path]::GetFullPath("$path");
$fspath = $fso.GetFolder("$fpath").ShortPath;
$foundIdx = $shortpaths.IndexOf($fspath);
if ($foundIdx -gt -1) { continue; }
write-host $fpath --> $fspath;
$shortpaths += $fspath;
}
write-host
write-host "Packing..."
write-host
$env:Path = $($shortpaths -join ";");
write-host $env:Path
write-host
write-host "Done."
write-host

@gvanem
Copy link

gvanem commented Dec 14, 2017

Maybe related, but I get the below Warning using this installer: PothosSDR-2017.11.26-vc14-x64.exe:

pothos-2017-install

@nlhnt
Copy link

nlhnt commented Apr 3, 2020

Any news on that?
I got the same error during the installation.
When I manually added C:\Program Files\PothosSDR\bin to my PATH variable it kind of turned Pothos Flow on, but all the GNURadio blocks I put down are read.

@einthecorgi2
Copy link

Same problem

@vbursucianu
Copy link

Got this issue too

@n3rdx
Copy link

n3rdx commented Feb 27, 2021

yes, I installed the latest I think (PothosSDR-2021.01.28-vc16-x64) today and got the same scary error. I will attempt to re-install it with a slightly shorter (but by how much) pathname. Just thought I would record this on Windows 10. I can install all commercial programs ... UPDATE: I de-installed and then re-installed with a C:\Program Files\PSDR directory location, (shorter path name) and so far it hasn't complained and just finished installing. However the de-installation process (UNINSTALL) was not smooth, and I had to restart the computer/use CCleaner/clean registry before I could get the entry removed from the Windows app registry which then would allow me to install once again. Otherwise, I was getting a notice that the App was already installed, thus it couldn't be installed again, even if I chose to install over the current installation (which was empty BTW). Bug?

@guruofquality
Copy link
Contributor

I wonder if this will fix it: https://docs.python.org/3/using/windows.html#removing-the-max-path-limitation

Windows historically has limited path lengths to 260 characters. This meant that paths longer than this would not resolve and errors would result.
In the latest versions of Windows, this limitation can be expanded to approximately 32,000 characters. Your administrator will need to activate the “Enable Win32 long paths” group policy, or set LongPathsEnabled to 1 in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem.

@Skinner927
Copy link

FWIW, enabling long paths did not change anything.
I have tried installing in c:\psdr, but I still get the path error.

It seems to have something to do with adding user or system's PATH environment variable rather than file path because if I turn that setting off in the installer, the error goes away.

@ratzrattillo
Copy link

Experienced the same issue. Is this being worked on?
Please inform us, if there is a workaround, or how this is planned to be fixed!

@habub
Copy link

habub commented Oct 23, 2022

This issue was opened in 2017, now it's 2022, I also have this same issue (2021.07.25-vc16-x64).
Any resolution I missed?

@nikstp
Copy link

nikstp commented Nov 1, 2022

I also got that error during the first install. I've had no issues (re)installing the software without adding the folder to the path automatically and instead adding it manually; I'd count that as a workaround for now.

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

No branches or pull requests

12 participants