From: "Geo" 

"Peter Sawatzki"  wrote in message
news:MPG.1c49e9be8ff695a0989743{at}news.barkto.com...
> In article , georger{at}nls.net says...
> > How many problems did MS cause by naming a folder "Program
Files" with
that
> > stupid space in there? You know, I see things like that show up in NT
and I
> > just cringe knowing they have someone on the NT team who should not be
in
> > charge of making those decisions..
>
> But I saw this as a good opportunity to make sure all programs a really
> (!) aware of long file names.

And the fix for the ones that weren't and aren't being maintained anymore is?

See I have a problem with that sort of thinking. I believe it's the right
thing to do if you are going to gain something valuable, for example
programs that cheated and tried to manipulate the hardware directly thus
causing system crashes I had no problem weeding those out because they
wouldn't run on NT because there was a huge value to system integrity in
doing so. But what's the value of weeding out programs that can't use a
space in a directory name? Is that something valuable to system integrity
or does the value of that only affect the one program? If so then is it
worth breaking the program simply because the program has a flaw that only
affects itself? I think not.

It would have been just as proper to call the directory
"Programs" instead of "Program Files".

Geo.

--- BBBS/NT v4.01 Flag-5