Not so far fetched - I've seen them used in commercial software

As for on the desktop - yes very bad practice if intended,
and even worse if mis-laid there.

But are you sure the name was randomly generated
rather than being intentionally given that name, but the creator couldn't be
bothered to document,
or that 'marketing didn't remove the documentation as being liable to
confuse the user, and stop them using the premium rate phone support
and if it was marketing, then:
They'd probably forget to document the support number as well
(Or as in the case of one IBM release - print a support contact number in
the documentation, but release the number to be re-assigned by the Telco to
an unsuspecting 'non-business user'.)

Yes a zero byte file can be re-created, but if this file is a header for
multiple streams, then what about the stuff in those other streams
Delete the header, and all the streams go as well - one of the wonders of
the 'feature rich' Microsoft Windows

JimB.

----- Original Message ----- 
From: "Carl Houseman" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, November 30, 2005 11:08 PM
Subject: Re: Subject: Re: What is cavag7bp ?


> Interesting points.  I probably missed several other far-fetched
> possibilities.
>
> Any software that puts an important file on the desktop, sets system
> attributes on it and gives it a randomly generated name... is just plain
> offensive.  The desktop is not the place for such things.
>
> A zero byte file can be re-created easily enough.  If necessary, it can be
> recreated with the same date stamps.
>
> Carl
>
> -----Original Message-----
> From: Windows Home/SOHO [mailto:[EMAIL PROTECTED] On Behalf
Of
> James Button
> Sent: Wednesday, November 30, 2005 5:43 PM
> To: [email protected]
> Subject: Re: Subject: Re: What is cavag7bp ?

--
                ----------------------------------------
The WIN-HOME mailing list is powered by L-Soft's renowned
LISTSERV(R) list management software. For more information, go to:
http://www.lsoft.com/LISTSERV-powered.html

Reply via email to