Some time ago I posted an issue with long files names on
Windows 2000 Pro SP1.
My system could not load the DirectX Audio plug-ins.
I was checking my system and found the following:
The entry "NtfsDisable8dot3NameCreation" on the Windows
registry was set to 1. I changed this entry before because
I read that this will speed file management since W2000
will not have to deal with the long file name
(example. "C:\PROGRAM FILES\SONIC FOUNDRY") and the short
file name (example. "C:\PROGRA~1\SONIC~1") at the same time.
As I posted before, I have other programs that can load the
Plug-ins with this setting, so I think that VV and SF are
still dealing with short names (8.3).
After changing this setting
to "NtfsDisable8dot3NameCreation=0", VV and SF started to
read the plug-ins.
The other way is to install to "C:\VEGAS" instead
of "C:\PROGRAM FILES\SONIC FOUNDRY".
I have read several posts about loading the plug-ins, but
beside this issue, every thing works fine.
Hope this can help someone.
Teo.
Windows 2000 Pro SP1.
My system could not load the DirectX Audio plug-ins.
I was checking my system and found the following:
The entry "NtfsDisable8dot3NameCreation" on the Windows
registry was set to 1. I changed this entry before because
I read that this will speed file management since W2000
will not have to deal with the long file name
(example. "C:\PROGRAM FILES\SONIC FOUNDRY") and the short
file name (example. "C:\PROGRA~1\SONIC~1") at the same time.
As I posted before, I have other programs that can load the
Plug-ins with this setting, so I think that VV and SF are
still dealing with short names (8.3).
After changing this setting
to "NtfsDisable8dot3NameCreation=0", VV and SF started to
read the plug-ins.
The other way is to install to "C:\VEGAS" instead
of "C:\PROGRAM FILES\SONIC FOUNDRY".
I have read several posts about loading the plug-ins, but
beside this issue, every thing works fine.
Hope this can help someone.
Teo.