Path syntax issue with ▮ sign for EXE files

Discussion, questions and support.
Post Reply
Message
Author
User avatar
Forez
Posts: 1335
Joined: 30.01.2016, 12:05
Location: In front of a PC monitor

Path syntax issue with ▮ sign for EXE files

#1 Post by Forez » 30.08.2021, 15:48

If the folder has

Code: Select all

sign in its name, then executable files residing in it will not run themselves. Instead of that they will spit an error saying
The filename, directory name, or volume label syntax is incorrect
And as this is both true for FreeCommander and Windows Explorer [and other software of that type] then I guess this is a not a bug but proper / default behavior. But can it be changed with an FC update - or will it e pretty much impossible because it is just how Windows 10 works? Or maybe it can be somehow workaround with some Registry hack?


I use this sign [and a set of two of them] to mark certain folders - so that the clearly stand out when I am navigating through sub-folders. This helps me a lot in my day-to-day tasks as I can see them clearly - but on the other hand that inability to run EXE files from them is counterproductive

horst.epp
Posts: 464
Joined: 15.11.2008, 20:18

Re: Path syntax issue with ▮ sign for EXE files

#2 Post by horst.epp » 31.08.2021, 13:05

Look at the Windows definitions of legal file and directory names.
You will find that it is not included.
So why should any update resolve your self produced problem ?
There are legal ways to assign icons or colours to a directory.
Windows 11 Home x64 Version 23H2 (OS Build 22631.3447)
Everything Version 1.5.0.1372a (x64), Everything Toolbar 1.3.3, Listary Pro 6.3.0.73
FreeCommander XE 2024 Build 906 64-bit donor

Post Reply

Who is online

Users browsing this forum: No registered users and 57 guests