Home All Groups Group Topic Archive Search About

Re: Problem with Direct Sound / VB6

Author
15 Aug 2010 10:56 PM
cphx
The Error is raised when i try to set the Direct Sound Buffer.

Author
15 Aug 2010 11:16 PM
Nobody
Your original post didn't appear in MS News Server because it contains an
outlawed sequence of characters:

_P_e_r_S_

Also, anyone who replies to your post and include these characters will have
their post auto deleted from MS News Server, but would appear in other
server. Try editing your code, and post it again. See these links to see
which server shows your post:

news://msnews.microsoft.com/microsoft.public.vb.general.discussion
news://news.aioe.org/microsoft.public.vb.general.discussion
Author
17 Aug 2010 8:33 AM
Dee Earley
On 16/08/2010 00:16, Nobody wrote:
> Your original post didn't appear in MS News Server because it contains an
> outlawed sequence of characters:
>
> _P_e_r_S_

Err, out of interest, any idea why??
Google doesn't seem to return anything relevant...

--
Dee Earley (dee.ear***@icode.co.uk)
i-Catcher Development Team

iCode Systems

(Replies direct to my email address will be ignored.
Please reply to the group.)
Author
17 Aug 2010 11:53 AM
Mike Williams
"Dee Earley" <dee.ear***@icode.co.uk> wrote in message
news:eSiJbdePLHA.2068@TK2MSFTNGP05.phx.gbl...
> On 16/08/2010 00:16, Nobody wrote:
>> Your original post didn't appear in MS News Server
>> because it contains an outlawed sequence of characters:
>>
>> _P_e_r_S_
>
> Err, out of interest, any idea why??
> Google doesn't seem to return anything relevant...

No idea. In fact (as far as I know) the fact that the specific sequence of
characters mentioned fails MS news filters was first noticed by me when I
posted some code (I can't remember exactly what that code was) which
contained a variable having the following name (without the underscores of
course):

    S_a_m_p_l_e_s_P_e_r_S_e_c_o_n_d

It was a very long message as I recall and I had to spend some time
repeatedly doing a "binary chop" of its contents and sending the message
parts individually until I finally discovered what the problem piece of text
was. Then a bit later I tested to find which specific part of the word the
MS servers objected to (the _p_e_r_s_ as I recall). I've no idea what the MS
filters objected to about that sequence of characters, and as far as I know
it has no rude or offensive translation in any language. The more suspicious
amongst us (myself included!) guessed that any variable with a name that
indicated it might be used to hold the result of a speed test, possibly
comparing VB6 to VB.Net, might be frowned upon my MS ;-)

Mike
Author
3 Sep 2010 10:16 PM
Karl E. Peterson
Mike Williams presented the following explanation :
> servers objected to (the _p_e_r_s_ as I recall). I've no idea what the MS
> filters objected to about that sequence of characters, and as far as I know
> it has no rude or offensive translation in any language.

Well, to the Teabaggers over here, PERS equates to Public Employees
Retirement System, which they find offensive in the extreme.  ;-)

--
..NET: It's About Trust!
http://vfred.mvps.org
Author
17 Aug 2010 1:09 PM
Nobody
"Dee Earley" <dee.ear***@icode.co.uk> wrote in message
news:eSiJbdePLHA.2068@TK2MSFTNGP05.phx.gbl...
> On 16/08/2010 00:16, Nobody wrote:
>> Your original post didn't appear in MS News Server because it contains an
>> outlawed sequence of characters:
>>
>> _P_e_r_S_
>
> Err, out of interest, any idea why??
> Google doesn't seem to return anything relevant...

Google without the extra characters:

Microsoft .Net b_e_n_c_h_m_a_r_k_s

It was not allowed to do the "B" word above in early EULA.
Author
17 Aug 2010 2:36 PM
Nobody
Show quote Hide quote
"Nobody" <nob***@nobody.com> wrote in message
news:i4e1nv$3o3$1@speranza.aioe.org...
> "Dee Earley" <dee.ear***@icode.co.uk> wrote in message
> news:eSiJbdePLHA.2068@TK2MSFTNGP05.phx.gbl...
>> On 16/08/2010 00:16, Nobody wrote:
>>> Your original post didn't appear in MS News Server because it contains
>>> an
>>> outlawed sequence of characters:
>>>
>>> _P_e_r_S_
>>
>> Err, out of interest, any idea why??
>> Google doesn't seem to return anything relevant...
>
> Google without the extra characters:
>
> Microsoft .Net b_e_n_c_h_m_a_r_k_s
>
> It was not allowed to do the "B" word above in early EULA.
>

P.S. The B word was allowed in dotnet groups, not in this VB Classic group.
I guess they know which is best!
Author
17 Aug 2010 2:41 PM
Dee Earley
On 17/08/2010 15:36, Nobody wrote:
Show quoteHide quote
> "Nobody"<nob***@nobody.com>  wrote in message
> news:i4e1nv$3o3$1@speranza.aioe.org...
>> "Dee Earley"<dee.ear***@icode.co.uk>  wrote in message
>> news:eSiJbdePLHA.2068@TK2MSFTNGP05.phx.gbl...
>>> On 16/08/2010 00:16, Nobody wrote:
>>>> Your original post didn't appear in MS News Server because it contains
>>>> an
>>>> outlawed sequence of characters:
>>>>
>>>> _P_e_r_S_
>>>
>>> Err, out of interest, any idea why??
>>> Google doesn't seem to return anything relevant...
>>
>> Google without the extra characters:
>>
>> Microsoft .Net b_e_n_c_h_m_a_r_k_s
>>
>> It was not allowed to do the "B" word above in early EULA.
>>
>
> P.S. The B word was allowed in dotnet groups, not in this VB Classic group.
> I guess they know which is best!

Seems incredibly stupid to blanket ban that word, especially in a
programming channel when people may want help speed testing something
completely unrelated to .net...

--
Dee Earley (dee.ear***@icode.co.uk)
i-Catcher Development Team

iCode Systems

(Replies direct to my email address will be ignored.
Please reply to the group.)
Author
17 Aug 2010 4:40 PM
Dee Earley
On 17/08/2010 15:41, Dee Earley wrote:
Show quoteHide quote
> On 17/08/2010 15:36, Nobody wrote:
>> "Nobody"<nob***@nobody.com> wrote in message
>> news:i4e1nv$3o3$1@speranza.aioe.org...
>>> "Dee Earley"<dee.ear***@icode.co.uk> wrote in message
>>> news:eSiJbdePLHA.2068@TK2MSFTNGP05.phx.gbl...
>>>> On 16/08/2010 00:16, Nobody wrote:
>>>>> Your original post didn't appear in MS News Server because it contains
>>>>> an
>>>>> outlawed sequence of characters:
>>>>>
>>>>> _P_e_r_S_
>>>>
>>>> Err, out of interest, any idea why??
>>>> Google doesn't seem to return anything relevant...
>>>
>>> Google without the extra characters:
>>>
>>> Microsoft .Net b_e_n_c_h_m_a_r_k_s
>>>
>>> It was not allowed to do the "B" word above in early EULA.
>>>
>>
>> P.S. The B word was allowed in dotnet groups, not in this VB Classic
>> group.
>> I guess they know which is best!
>
> Seems incredibly stupid to blanket ban that word, especially in a
> programming channel when people may want help speed testing something
> completely unrelated to .net...

So I won't be allowed to discuss me frames_p_e_r_second calculation in
my video/cctv app?  :)

--
Dee Earley (dee.ear***@icode.co.uk)
i-Catcher Development Team

iCode Systems

(Replies direct to my email address will be ignored.
Please reply to the group.)