Forum > Windows (32/64)

Win 10 install gone bad

<< < (3/3)

rvk:

--- Quote from: Thaddy on January 26, 2022, 07:59:46 pm ---Then it becomes 'C:\PROGRA~1\ '. This is supported by Freepascal.

--- End quote ---
Or is it C:\PROGRA~2  :P

First check with dir /x
BTW. Not all Windows filesystems are configered to create shortnames. Does Windows still do this by default? Check with fsutil 8dot3name query [<volumepath>]

PascalDragon:

--- Quote from: Thaddy on January 26, 2022, 07:59:46 pm ---Long path names with spaces should always be surrounded by double quotes.'"c:\program files\*"' etc, note the single quotes around it to make it a Pascal string. So ', subsequently " obviously
--- End quote ---

The problem is that some Unix utilities (e.g. windres) did or do not handle such paths correctly no matter the quoting.


--- Quote from: Thaddy on January 26, 2022, 07:59:46 pm ---You can also use the shortpath API. Then it becomes 'C:\PROGRA~1\ '. This is supported by Freepascal.
https://www.freepascal.org/docs-html/rtl/sysutils/extractshortpathname.html
The UNC (canonical) API should also work indeed.

--- End quote ---

The question for both of these is whether the Unix utilities handle that correctly (the short names probably, as long as they're enabled for the file system as rvk mentioned), but UNC path is a different topic.

In any case: the problem aren't FPC or Lazarus themselves, but some of the third party tools used by them.

dbannon:
I suspect the space in "Program Files" was Microsoft's attempt to ensure incompatibility with Unix, they sure gave it a good old try !

Davo

Navigation

[0] Message Index

[*] Previous page

Go to full version