Odd 8.3 set and file name problem (Win2000)
Posted: Tue Oct 21, 2003 9:37 pm
V3 is wonderful and pretty stable, no problems or complaints there.
However, I am having some very odd problems when opening v2.0.3
sets and saving them in v3.
Basically, v3 seems to want to name things using 8.3. For instance
if I open a set "My Kool Set" it will show MYCOOL~1 in the title bar,
and if I render it to .wav it becomes MYCOOL~1.wav. Also, if I
create new clips by recording, a new folder gets created called
(wait for it) "MYCOOL~1 Sounds".
There's nothing fatal about this but it is annoying and inconvenient.
The funny thing is I've noticed no one else complaining about it
so I wonder if I am the only one seeing it.
The system is a 2GHz P4, 768MB RAM, Service Pack 4 installed.
The 2 60 GB hard drives are NTFS formatted.
Anyone else see this? Any ideas? Some setting in W2K I've never
seen before? I have read somewhere that there is a registry option
called "disable 8.3 names" but I have never tinkered with it...
Also, is there a single resource I can go to most of the frequently
reported bugs and feature requests are listed so I can make sure
I'm not reporting something that's been gone over before?
r
However, I am having some very odd problems when opening v2.0.3
sets and saving them in v3.
Basically, v3 seems to want to name things using 8.3. For instance
if I open a set "My Kool Set" it will show MYCOOL~1 in the title bar,
and if I render it to .wav it becomes MYCOOL~1.wav. Also, if I
create new clips by recording, a new folder gets created called
(wait for it) "MYCOOL~1 Sounds".
There's nothing fatal about this but it is annoying and inconvenient.
The funny thing is I've noticed no one else complaining about it
so I wonder if I am the only one seeing it.
The system is a 2GHz P4, 768MB RAM, Service Pack 4 installed.
The 2 60 GB hard drives are NTFS formatted.
Anyone else see this? Any ideas? Some setting in W2K I've never
seen before? I have read somewhere that there is a registry option
called "disable 8.3 names" but I have never tinkered with it...
Also, is there a single resource I can go to most of the frequently
reported bugs and feature requests are listed so I can make sure
I'm not reporting something that's been gone over before?
r