|
|
|
|
#1 |
|
Junior Member
Join Date: Jun 2004
Posts: 19
|
short filenames in destination folder
I can't figure why this is happening, but I get short filenames in the destination folder field (of the MUI). For example, C:\PROGRA~1\TASKTR~1. Full filenames are only appearing after browsing for a folder. Script attached.
|
|
|
|
|
|
#2 |
|
M.I.A.
[NSIS Dev, Mod] Join Date: Oct 2001
Location: Israel
Posts: 11,343
|
The script you've attached is empty.
NSIS FAQ | NSIS Home Page | Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius |
|
|
|
|
|
#3 | |
|
Junior Member
|
Quote:
|
|
|
|
|
|
|
#4 |
|
Junior Member
Join Date: Jun 2004
Posts: 19
|
Let's try that again. But anyway, the issue is not present on another system, so maybe it's not NSIS-specific.
|
|
|
|
|
|
#5 |
|
M.I.A.
[NSIS Dev, Mod] Join Date: Oct 2001
Location: Israel
Posts: 11,343
|
Have you made sure this short name doesn't come from the installation directory registry key (HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths\TaskTracker.exe)?
NSIS FAQ | NSIS Home Page | Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius |
|
|
|
|
|
#6 |
|
Junior Member
Join Date: Jun 2004
Posts: 19
|
Maybe that was it. I can't say positively because the problem has gone away for now on the original system. I browsed to the directory, and this problably reset the key. It's correct now. If it recurs, I will check it again.
|
|
|
|
|
|
#7 |
|
Senior Member
Join Date: Jan 2004
Location: London, Ontario, Canada
Posts: 272
|
I know that on XP you can turn off the 8.3 filename support within the OS. It speeds up disk access considerably (almost 35%) since the OS doesn't have to create 8.3 filenames for each of the files it is writing to disk. Perhaps, on the system you are using the creation of 8.3 headers was disabled.
|
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|