Page 2 of 5 FirstFirst 12345 LastLast
Results 21 to 40 of 86

Thread: PIR interfering with wireless network

  1. #21
    Peter Hucker
    Guest

    Re: PIR interfering with wireless network

    On Mon, 02 Feb 2009 23:33:13 -0000, ray <raymond.schmit@piscarlet.be> wrote:

    > "Peter Hucker" <none@spam.com> wrote in message
    > news:op.uoqtil1j4buhsv@fx62.mshome.net...
    >> On Sat, 31 Jan 2009 16:47:13 -0000, ray <raymond.schmit@piscarlet.be>
    >> wrote:
    >>
    >>> "Peter Hucker" <none@spam.com> wrote in message
    >>> news:op.uol90txg4buhsv@fx62.mshome.net...
    >>>> On Sat, 31 Jan 2009 04:00:27 -0000, Bob Fry <bobfry@mailinator.com>
    >>>> wrote:
    >>>>

    >>
    >>>>>
    >>>>> >> Doesn't your news client word wrap?
    >>>>>
    >>>>> PH> Doesn't yours? I can't predict what width your screen is.
    >>>>>
    >>>>> What an idiot.
    >>>>
    >>>> Are you a communist who thinks every machine and every person is the
    >>>> same?
    >>>> I don't want measly 80 character columns. I have a large screen for a
    >>>> reason.
    >>>>
    >>>> If you want 80 columns, then get your useless newsreader to wrap to
    >>>> window, then my text and everyone else's text will be 80 columns wide
    >>>> (or
    >>>> whatever the width of your window is) especially for you.
    >>>>
    >>>
    >>> Let the majority decide to *not* use line length > 80.
    >>> If you want it more .... it's up to you,
    >>> but please follow the usenet habits/etiquette !!!

    >>
    >> You've just contradicted yourself, you're saying people should not change
    >> but people should decide!
    >>
    >>> http://www.cs.tut.fi/~jkorpela/usenet/dont.html
    >>> say: line length under 80 (preferably under 72) characters;
    >>>
    >>> http://www.faqs.org/faqs/usenet/primer/part1/
    >>> say:
    >>> Try to keep your text in a generic format. Many (if not most) of
    >>> the people reading Usenet do so from 80 column terminals or from
    >>> workstations with 80 column terminal windows. Try to keep your
    >>> lines of text to less than 80 characters for optimal readability.
    >>> If people quote part of your article in a followup, short lines will
    >>> probably show up better, too.

    >>
    >> I'm using format flowed. It's a standard, live with it.
    >>

    >
    > You speak as microsoft claiming that the microsoft's standards is *the*
    > standard.
    > If you want to use Usenet (it's here) it's better to follow the Usenet's
    > standard.


    It's a new standard. And not that new either. Do you object to SATA because PATA is *the* standard?


    --
    http://www.petersparrots.com http://www.insanevideoclips.com http://www.petersphotos.com

    During a visit to the mental asylum, a visitor asked the Director what the criterion was which defined whether or not a patient should be institutionalized.
    "Well," said the Director, "we fill up a bathtub, then we offer a teaspoon, a teacup, and a bucket to the patient and ask him to empty the bathtub."
    "Oh, I understand," said the visitor. "A normal person would use the bucket, because it's bigger than the teaspoon or the teacup."
    "No," said the Director, "a normal person would pull the plug. Do you want a room with or without a view?"

  2. #22
    Peter Hucker
    Guest

    Re: PIR interfering with wireless network

    On Mon, 02 Feb 2009 23:37:13 -0000, ray <raymond.schmit@piscarlet.be> wrote:

    > "Peter Hucker" <none@spam.com> wrote in message
    > news:op.uoqtnsvf4buhsv@fx62.mshome.net...
    >> On Mon, 02 Feb 2009 18:11:01 -0000, Dave J. <requiem@freeuk.com> wrote:
    >>
    >>> In MsgID<zlh83z1g.fsf@mailinator.com> on Fri, 30 Jan 2009 20:00:27 -0800,
    >>> in comp.os.ms-windows.networking.misc, 'Bob Fry' wrote:
    >>>


    >>>>
    >>>> >> Doesn't your news client word wrap?
    >>>>
    >>>> PH> Doesn't yours? I can't predict what width your screen is.
    >>>>
    >>>>What an idiot.
    >>>
    >>> Not his fault if he can't spell RFC..

    >>
    >> Rules are for the obedience of fools and the guidance of wise men.

    >
    > And you are too important to follow any rules. ....


    I take them under consideration.


    --
    http://www.petersparrots.com http://www.insanevideoclips.com http://www.petersphotos.com

    __NNNNL_.
    JNNNNNNNNNNN.
    NNNNNNNNNNNNNN)
    JNNNNNNNNNNNNNNN.
    NNNNNNNNNNNNNNNN)
    NNNNNNNNNNNNNNNN)
    NNNN""NNNNF"4NNN)
    (NN NN) (NN
    4N. .NNL JN`
    NNNNNN(NNNNN)
    NNNNN (NNNN)
    "NNNNNNF`
    N.NNNN`N`
    (NL___NN
    _. `NNNNF
    (NNN. `NN` JNN
    (NNNNL .NNNN
    .NNNNNNNNL. .JNNNNNNL
    `NN" `"NNNNNL.JNNNN"` 4NN
    `4NNNNN"
    .JNNNNNNN.
    .NNNN" `NNNNL
    _NNNNNNN" `NNNNNNL.
    (NNNNNNF `NNNNNN
    4NNNNN (NNF"
    `" ``

  3. #23
    Peter Hucker
    Guest

    Re: PIR interfering with wireless network

    On Tue, 03 Feb 2009 20:14:08 -0000, Dave J. <requiem@freeuk.com> wrote:

    > In MsgID<op.uoqtnsvf4buhsv@fx62.mshome.net> on Mon, 02 Feb 2009 21:22:30
    > -0000, in comp.os.ms-windows.networking.misc, 'Peter Hucker' wrote:
    >
    >>>>What an idiot.
    >>>
    >>> Not his fault if he can't spell RFC..

    >>
    >>Rules are for the obedience of fools and the guidance of wise men.

    >
    > It's not a rule, it's a standard. There's no obligation to follow it, it's
    > just there in case you want to cooperate with the majority.


    There are two standards.

    --
    http://www.petersparrots.com http://www.insanevideoclips.com http://www.petersphotos.com

    Rather bad pigeon English from an ad for a Yamaha Motorcycle:

    Specify that, Yamaha YZF-R1 specification table
    Engine form: Four flushes the water cooling DOHC 20 live petalscompound 4 cylinders cylinder bore x stroke: 77.0mm x 53.6mm
    Transmission system wet type multi- pieces in front of 6 fast
    Fuel supply Mikuni double oil valve electron fuel oil system
    (R): 24
    The towing is apart from (T): 97mm
    system: 43mm stands upside down the drive pipe frontfork, the entire function accent compares the 120mm travellingschedule
    Latter suspension system: The single barrel flowing tubinghead pressure evades shakes, the entire function accent compares the130mm travelling schedule
    Tire (front): 120,/70 - ZR17
    After tire (): 190,/50 - ZR17
    The first brake moves the system: 2 x 320mm x vehicle smalldish emanant 4 pistons to approach
    The latter brake moves the system: 220mm Shan Diepei singlepiston
    Long x is extravagant high x: 2,065 x 720 x 1105mm
    Spread of axies: 1395mm
    Lowly takeoffs is apart from 135mm
    Place high: 835mm

  4. #24
    Les Cargill
    Guest

    Re: PIR interfering with wireless network

    Peter Hucker wrote:
    > On Tue, 03 Feb 2009 20:14:08 -0000, Dave J. <requiem@freeuk.com> wrote:
    >
    >> In MsgID<op.uoqtnsvf4buhsv@fx62.mshome.net> on Mon, 02 Feb 2009 21:22:30
    >> -0000, in comp.os.ms-windows.networking.misc, 'Peter Hucker' wrote:
    >>
    >>>>> What an idiot.
    >>>> Not his fault if he can't spell RFC..
    >>> Rules are for the obedience of fools and the guidance of wise men.

    >> It's not a rule, it's a standard. There's no obligation to follow it, it's
    >> just there in case you want to cooperate with the majority.

    >
    > There are two standards.
    >


    Not really.

    Here's old and weary standard RFC 977:

    "...Text is sent as a series of
    successive lines of textual matter, each terminated with CR-LF pair."

    http://www.faqs.org/rfcs/rfc977.html

    Section 2.4.1

    So if you expect people to see things in lines, you're on
    the hook to add the carriage returns/line feeds. If you don't
    some boogerhead might complain about it :)

    Debate-fun is what it is, but ... your position isn't
    that tenable. "Be liberal in what you accept, and
    conservative in what you send." - Jon Postrel,
    RFC760/RFC1122 .

    (All this noise is simply here to inform, not to score
    points or something. It should be merely interesting.)

    --
    Les Cargill

  5. #25
    ray
    Guest

    Re: PIR interfering with wireless network

    "Peter Hucker" <none@spam.com> wrote in message
    news:op.uoug5awt4buhsv@fx62.mshome.net...
    > On Mon, 02 Feb 2009 23:33:13 -0000, ray <raymond.schmit@piscarlet.be>
    > wrote:
    >
    >> "Peter Hucker" <none@spam.com> wrote in message
    >> news:op.uoqtil1j4buhsv@fx62.mshome.net...
    >>> On Sat, 31 Jan 2009 16:47:13 -0000, ray <raymond.schmit@piscarlet.be>
    >>> wrote:
    >>>
    >>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>> news:op.uol90txg4buhsv@fx62.mshome.net...
    >>>>> On Sat, 31 Jan 2009 04:00:27 -0000, Bob Fry <bobfry@mailinator.com>
    >>>>> wrote:
    >>>>>
    >>>
    >>>>>>
    >>>>>> >> Doesn't your news client word wrap?
    >>>>>>
    >>>>>> PH> Doesn't yours? I can't predict what width your screen is.
    >>>>>>
    >>>>>> What an idiot.
    >>>>>
    >>>>> Are you a communist who thinks every machine and every person is the
    >>>>> same?
    >>>>> I don't want measly 80 character columns. I have a large screen for a
    >>>>> reason.
    >>>>>
    >>>>> If you want 80 columns, then get your useless newsreader to wrap to
    >>>>> window, then my text and everyone else's text will be 80 columns wide
    >>>>> (or
    >>>>> whatever the width of your window is) especially for you.
    >>>>>
    >>>>
    >>>> Let the majority decide to *not* use line length > 80.
    >>>> If you want it more .... it's up to you,
    >>>> but please follow the usenet habits/etiquette !!!
    >>>
    >>> You've just contradicted yourself, you're saying people should not
    >>> change
    >>> but people should decide!
    >>>
    >>>> http://www.cs.tut.fi/~jkorpela/usenet/dont.html
    >>>> say: line length under 80 (preferably under 72) characters;
    >>>>
    >>>> http://www.faqs.org/faqs/usenet/primer/part1/
    >>>> say:
    >>>> Try to keep your text in a generic format. Many (if not most) of
    >>>> the people reading Usenet do so from 80 column terminals or from
    >>>> workstations with 80 column terminal windows. Try to keep your
    >>>> lines of text to less than 80 characters for optimal readability.
    >>>> If people quote part of your article in a followup, short lines will
    >>>> probably show up better, too.
    >>>
    >>> I'm using format flowed. It's a standard, live with it.
    >>>

    >>
    >> You speak as microsoft claiming that the microsoft's standards is *the*
    >> standard.
    >> If you want to use Usenet (it's here) it's better to follow the Usenet's
    >> standard.

    >
    > It's a new standard. And not that new either. Do you object to SATA
    > because PATA is *the* standard?



    Where did you find that usenet must follow your standard ?



  6. #26
    Peter Hucker
    Guest

    Re: PIR interfering with wireless network

    On Wed, 04 Feb 2009 21:28:19 -0000, Les Cargill <lcargill@cfl.rr.com> wrote:

    > Peter Hucker wrote:
    >> On Tue, 03 Feb 2009 20:14:08 -0000, Dave J. <requiem@freeuk.com> wrote:
    >>
    >>> In MsgID<op.uoqtnsvf4buhsv@fx62.mshome.net> on Mon, 02 Feb 2009 21:22:30
    >>> -0000, in comp.os.ms-windows.networking.misc, 'Peter Hucker' wrote:
    >>>
    >>>>>> What an idiot.
    >>>>> Not his fault if he can't spell RFC..
    >>>> Rules are for the obedience of fools and the guidance of wise men.
    >>> It's not a rule, it's a standard. There's no obligation to follow it, it's
    >>> just there in case you want to cooperate with the majority.

    >>
    >> There are two standards.

    >
    > Not really.
    >
    > Here's old and weary standard RFC 977:
    >
    > "...Text is sent as a series of
    > successive lines of textual matter, each terminated with CR-LF pair."
    >
    > http://www.faqs.org/rfcs/rfc977.html
    >
    > Section 2.4.1
    >
    > So if you expect people to see things in lines, you're on
    > the hook to add the carriage returns/line feeds. If you don't
    > some boogerhead might complain about it :)
    >
    > Debate-fun is what it is, but ... your position isn't
    > that tenable. "Be liberal in what you accept, and
    > conservative in what you send." - Jon Postrel,
    > RFC760/RFC1122 .
    >
    > (All this noise is simply here to inform, not to score
    > points or something. It should be merely interesting.)


    But there is also this (which ties in with the more advanced auto-wrapping capablities of every word processor):
    http://joeclark.org/ffaq.html

    --
    http://www.petersparrots.com http://www.insanevideoclips.com http://www.petersphotos.com

    Whatever hits the fan will not be evenly distributed.

  7. #27
    Peter Hucker
    Guest

    Re: PIR interfering with wireless network

    On Wed, 04 Feb 2009 21:31:34 -0000, ray <raymond.schmit@piscarlet.be> wrote:

    > "Peter Hucker" <none@spam.com> wrote in message
    > news:op.uoug5awt4buhsv@fx62.mshome.net...
    >> On Mon, 02 Feb 2009 23:33:13 -0000, ray <raymond.schmit@piscarlet.be>
    >> wrote:
    >>
    >>> "Peter Hucker" <none@spam.com> wrote in message
    >>> news:op.uoqtil1j4buhsv@fx62.mshome.net...
    >>>> On Sat, 31 Jan 2009 16:47:13 -0000, ray <raymond.schmit@piscarlet.be>
    >>>> wrote:
    >>>>
    >>>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>>> news:op.uol90txg4buhsv@fx62.mshome.net...
    >>>>>> On Sat, 31 Jan 2009 04:00:27 -0000, Bob Fry <bobfry@mailinator.com>
    >>>>>> wrote:
    >>>>>>
    >>>>
    >>>>>>>
    >>>>>>> >> Doesn't your news client word wrap?
    >>>>>>>
    >>>>>>> PH> Doesn't yours? I can't predict what width your screen is.
    >>>>>>>
    >>>>>>> What an idiot.
    >>>>>>
    >>>>>> Are you a communist who thinks every machine and every person is the
    >>>>>> same?
    >>>>>> I don't want measly 80 character columns. I have a large screen for a
    >>>>>> reason.
    >>>>>>
    >>>>>> If you want 80 columns, then get your useless newsreader to wrap to
    >>>>>> window, then my text and everyone else's text will be 80 columns wide
    >>>>>> (or
    >>>>>> whatever the width of your window is) especially for you.
    >>>>>>
    >>>>>
    >>>>> Let the majority decide to *not* use line length > 80.
    >>>>> If you want it more .... it's up to you,
    >>>>> but please follow the usenet habits/etiquette !!!
    >>>>
    >>>> You've just contradicted yourself, you're saying people should not
    >>>> change
    >>>> but people should decide!
    >>>>
    >>>>> http://www.cs.tut.fi/~jkorpela/usenet/dont.html
    >>>>> say: line length under 80 (preferably under 72) characters;
    >>>>>
    >>>>> http://www.faqs.org/faqs/usenet/primer/part1/
    >>>>> say:
    >>>>> Try to keep your text in a generic format. Many (if not most) of
    >>>>> the people reading Usenet do so from 80 column terminals or from
    >>>>> workstations with 80 column terminal windows. Try to keep your
    >>>>> lines of text to less than 80 characters for optimal readability.
    >>>>> If people quote part of your article in a followup, short lines will
    >>>>> probably show up better, too.
    >>>>
    >>>> I'm using format flowed. It's a standard, live with it.
    >>>>
    >>>
    >>> You speak as microsoft claiming that the microsoft's standards is *the*
    >>> standard.
    >>> If you want to use Usenet (it's here) it's better to follow the Usenet's
    >>> standard.

    >>
    >> It's a new standard. And not that new either. Do you object to SATA
    >> because PATA is *the* standard?

    >
    >
    > Where did you find that usenet must follow your standard ?


    I did not invent this standard.


    --
    http://www.petersparrots.com http://www.insanevideoclips.com http://www.petersphotos.com

    Depression is merely anger without enthusiasm.

  8. #28
    ray
    Guest

    Re: PIR interfering with wireless network

    "Peter Hucker" <none@spam.com> wrote in message
    news:op.uov9u8qj4buhsv@fx62.mshome.net...
    > On Wed, 04 Feb 2009 21:31:34 -0000, ray <raymond.schmit@piscarlet.be>
    > wrote:
    >
    >> "Peter Hucker" <none@spam.com> wrote in message
    >> news:op.uoug5awt4buhsv@fx62.mshome.net...
    >>> On Mon, 02 Feb 2009 23:33:13 -0000, ray <raymond.schmit@piscarlet.be>
    >>> wrote:
    >>>
    >>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>> news:op.uoqtil1j4buhsv@fx62.mshome.net...
    >>>>> On Sat, 31 Jan 2009 16:47:13 -0000, ray <raymond.schmit@piscarlet.be>
    >>>>> wrote:
    >>>>>
    >>>>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>>>> news:op.uol90txg4buhsv@fx62.mshome.net...
    >>>>>>> On Sat, 31 Jan 2009 04:00:27 -0000, Bob Fry <bobfry@mailinator.com>
    >>>>>>> wrote:
    >>>>>>>
    >>>>>
    >>>>>>>>
    >>>>>>>> >> Doesn't your news client word wrap?
    >>>>>>>>
    >>>>>>>> PH> Doesn't yours? I can't predict what width your screen is.
    >>>>>>>>
    >>>>>>>> What an idiot.
    >>>>>>>
    >>>>>>> Are you a communist who thinks every machine and every person is the
    >>>>>>> same?
    >>>>>>> I don't want measly 80 character columns. I have a large screen for
    >>>>>>> a
    >>>>>>> reason.
    >>>>>>>
    >>>>>>> If you want 80 columns, then get your useless newsreader to wrap to
    >>>>>>> window, then my text and everyone else's text will be 80 columns
    >>>>>>> wide
    >>>>>>> (or
    >>>>>>> whatever the width of your window is) especially for you.
    >>>>>>>
    >>>>>>
    >>>>>> Let the majority decide to *not* use line length > 80.
    >>>>>> If you want it more .... it's up to you,
    >>>>>> but please follow the usenet habits/etiquette !!!
    >>>>>
    >>>>> You've just contradicted yourself, you're saying people should not
    >>>>> change
    >>>>> but people should decide!
    >>>>>
    >>>>>> http://www.cs.tut.fi/~jkorpela/usenet/dont.html
    >>>>>> say: line length under 80 (preferably under 72) characters;
    >>>>>>
    >>>>>> http://www.faqs.org/faqs/usenet/primer/part1/
    >>>>>> say:
    >>>>>> Try to keep your text in a generic format. Many (if not most) of
    >>>>>> the people reading Usenet do so from 80 column terminals or from
    >>>>>> workstations with 80 column terminal windows. Try to keep your
    >>>>>> lines of text to less than 80 characters for optimal readability.
    >>>>>> If people quote part of your article in a followup, short lines
    >>>>>> will
    >>>>>> probably show up better, too.
    >>>>>
    >>>>> I'm using format flowed. It's a standard, live with it.
    >>>>>
    >>>>
    >>>> You speak as microsoft claiming that the microsoft's standards is *the*
    >>>> standard.
    >>>> If you want to use Usenet (it's here) it's better to follow the
    >>>> Usenet's
    >>>> standard.
    >>>
    >>> It's a new standard. And not that new either. Do you object to SATA
    >>> because PATA is *the* standard?

    >>
    >>
    >> Where did you find that usenet must follow your standard ?

    >
    > I did not invent this standard.


    Everybody knows that - you did not answer the question ...



  9. #29
    ray
    Guest

    Re: PIR interfering with wireless network

    "Peter Hucker" <none@spam.com> wrote in message
    news:op.uov9uvpn4buhsv@fx62.mshome.net...
    > On Wed, 04 Feb 2009 21:28:19 -0000, Les Cargill <lcargill@cfl.rr.com>
    > wrote:
    >
    >> Peter Hucker wrote:
    >>> On Tue, 03 Feb 2009 20:14:08 -0000, Dave J. <requiem@freeuk.com> wrote:
    >>>
    >>>> In MsgID<op.uoqtnsvf4buhsv@fx62.mshome.net> on Mon, 02 Feb 2009
    >>>> 21:22:30
    >>>> -0000, in comp.os.ms-windows.networking.misc, 'Peter Hucker' wrote:
    >>>>
    >>>>>>> What an idiot.
    >>>>>> Not his fault if he can't spell RFC..
    >>>>> Rules are for the obedience of fools and the guidance of wise men.
    >>>> It's not a rule, it's a standard. There's no obligation to follow it,
    >>>> it's
    >>>> just there in case you want to cooperate with the majority.
    >>>
    >>> There are two standards.

    >>
    >> Not really.
    >>
    >> Here's old and weary standard RFC 977:
    >>
    >> "...Text is sent as a series of
    >> successive lines of textual matter, each terminated with CR-LF pair."
    >>
    >> http://www.faqs.org/rfcs/rfc977.html
    >>
    >> Section 2.4.1
    >>
    >> So if you expect people to see things in lines, you're on
    >> the hook to add the carriage returns/line feeds. If you don't
    >> some boogerhead might complain about it :)
    >>
    >> Debate-fun is what it is, but ... your position isn't
    >> that tenable. "Be liberal in what you accept, and
    >> conservative in what you send." - Jon Postrel,
    >> RFC760/RFC1122 .
    >>
    >> (All this noise is simply here to inform, not to score
    >> points or something. It should be merely interesting.)

    >
    > But there is also this (which ties in with the more advanced auto-wrapping
    > capablities of every word processor):
    > http://joeclark.org/ffaq.html
    >



    Usenet have nothing to do with a "word processor" ...



  10. #30
    Peter Hucker
    Guest

    Re: PIR interfering with wireless network

    On Thu, 05 Feb 2009 22:21:11 -0000, ray <raymond.schmit@piscarlet.be> wrote:

    > "Peter Hucker" <none@spam.com> wrote in message
    > news:op.uov9u8qj4buhsv@fx62.mshome.net...
    >> On Wed, 04 Feb 2009 21:31:34 -0000, ray <raymond.schmit@piscarlet.be>
    >> wrote:
    >>
    >>> "Peter Hucker" <none@spam.com> wrote in message
    >>> news:op.uoug5awt4buhsv@fx62.mshome.net...
    >>>> On Mon, 02 Feb 2009 23:33:13 -0000, ray <raymond.schmit@piscarlet.be>
    >>>> wrote:
    >>>>
    >>>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>>> news:op.uoqtil1j4buhsv@fx62.mshome.net...
    >>>>>> On Sat, 31 Jan 2009 16:47:13 -0000, ray <raymond.schmit@piscarlet.be>
    >>>>>> wrote:
    >>>>>>
    >>>>>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>>>>> news:op.uol90txg4buhsv@fx62.mshome.net...


    >>>>>>


    >>>>>>>
    >>>>>>> Let the majority decide to *not* use line length > 80.
    >>>>>>> If you want it more .... it's up to you,
    >>>>>>> but please follow the usenet habits/etiquette !!!
    >>>>>>
    >>>>>> You've just contradicted yourself, you're saying people should not
    >>>>>> change
    >>>>>> but people should decide!
    >>>>>>
    >>>>>>> http://www.cs.tut.fi/~jkorpela/usenet/dont.html
    >>>>>>> say: line length under 80 (preferably under 72) characters;
    >>>>>>>
    >>>>>>> http://www.faqs.org/faqs/usenet/primer/part1/
    >>>>>>> say:
    >>>>>>> Try to keep your text in a generic format. Many (if not most) of
    >>>>>>> the people reading Usenet do so from 80 column terminals or from
    >>>>>>> workstations with 80 column terminal windows. Try to keep your
    >>>>>>> lines of text to less than 80 characters for optimal readability.
    >>>>>>> If people quote part of your article in a followup, short lines
    >>>>>>> will
    >>>>>>> probably show up better, too.
    >>>>>>
    >>>>>> I'm using format flowed. It's a standard, live with it.
    >>>>>>
    >>>>>
    >>>>> You speak as microsoft claiming that the microsoft's standards is *the*
    >>>>> standard.
    >>>>> If you want to use Usenet (it's here) it's better to follow the
    >>>>> Usenet's
    >>>>> standard.
    >>>>
    >>>> It's a new standard. And not that new either. Do you object to SATA
    >>>> because PATA is *the* standard?
    >>>
    >>>
    >>> Where did you find that usenet must follow your standard ?

    >>
    >> I did not invent this standard.

    >
    > Everybody knows that - you did not answer the question ...


    How can I answer a question that is incorrect?

    What would you answer to "Have you stopped beating your wife yet?"


    --
    http://www.petersparrots.com http://www.insanevideoclips.com http://www.petersphotos.com

    Bikini e pareo, camicia di pizzo e shorts, top e gonna di crochet!

  11. #31
    Peter Hucker
    Guest

    Re: PIR interfering with wireless network

    On Thu, 05 Feb 2009 22:23:15 -0000, ray <raymond.schmit@piscarlet.be> wrote:

    > "Peter Hucker" <none@spam.com> wrote in message
    > news:op.uov9uvpn4buhsv@fx62.mshome.net...
    >> On Wed, 04 Feb 2009 21:28:19 -0000, Les Cargill <lcargill@cfl.rr.com>
    >> wrote:
    >>
    >>> Peter Hucker wrote:
    >>>> On Tue, 03 Feb 2009 20:14:08 -0000, Dave J. <requiem@freeuk.com> wrote:
    >>>>
    >>>>> In MsgID<op.uoqtnsvf4buhsv@fx62.mshome.net> on Mon, 02 Feb 2009
    >>>>> 21:22:30
    >>>>> -0000, in comp.os.ms-windows.networking.misc, 'Peter Hucker' wrote:
    >>>>>


    >>>>>>> Not his fault if he can't spell RFC..
    >>>>>> Rules are for the obedience of fools and the guidance of wise men.
    >>>>> It's not a rule, it's a standard. There's no obligation to follow it,
    >>>>> it's
    >>>>> just there in case you want to cooperate with the majority.
    >>>>
    >>>> There are two standards.
    >>>
    >>> Not really.
    >>>
    >>> Here's old and weary standard RFC 977:
    >>>
    >>> "...Text is sent as a series of
    >>> successive lines of textual matter, each terminated with CR-LF pair."
    >>>
    >>> http://www.faqs.org/rfcs/rfc977.html
    >>>
    >>> Section 2.4.1
    >>>
    >>> So if you expect people to see things in lines, you're on
    >>> the hook to add the carriage returns/line feeds. If you don't
    >>> some boogerhead might complain about it :)
    >>>
    >>> Debate-fun is what it is, but ... your position isn't
    >>> that tenable. "Be liberal in what you accept, and
    >>> conservative in what you send." - Jon Postrel,
    >>> RFC760/RFC1122 .
    >>>
    >>> (All this noise is simply here to inform, not to score
    >>> points or something. It should be merely interesting.)

    >>
    >> But there is also this (which ties in with the more advanced auto-wrapping
    >> capablities of every word processor):
    >> http://joeclark.org/ffaq.html
    >>

    >
    >
    > Usenet have nothing to do with a "word processor" ...


    Both display paragraphs of text on your screen. Why should the display engine be different?


    --
    http://www.petersparrots.com http://www.insanevideoclips.com http://www.petersphotos.com

    In a long line of people, one guy suddenly starts massaging the back of the person in front of him, the person turned and asked, what the hell you are doing?
    "Well," said the guy massaging the back, "you see I'm a chiropractor and I can't help massaging your back. I can't help practicing my art."
    "Are you crazy?" the other guy said, "Look, I'm a lawyer. Am I ****ing the guy in front of me?"

  12. #32
    ray
    Guest

    Re: PIR interfering with wireless network

    "Peter Hucker" <none@spam.com> wrote in message
    news:op.uox2v0xq4buhsv@fx62.mshome.net...
    > On Thu, 05 Feb 2009 22:21:11 -0000, ray <raymond.schmit@piscarlet.be>
    > wrote:
    >
    >> "Peter Hucker" <none@spam.com> wrote in message
    >> news:op.uov9u8qj4buhsv@fx62.mshome.net...
    >>> On Wed, 04 Feb 2009 21:31:34 -0000, ray <raymond.schmit@piscarlet.be>
    >>> wrote:
    >>>
    >>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>> news:op.uoug5awt4buhsv@fx62.mshome.net...
    >>>>> On Mon, 02 Feb 2009 23:33:13 -0000, ray <raymond.schmit@piscarlet.be>
    >>>>> wrote:
    >>>>>
    >>>>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>>>> news:op.uoqtil1j4buhsv@fx62.mshome.net...
    >>>>>>> On Sat, 31 Jan 2009 16:47:13 -0000, ray
    >>>>>>> <raymond.schmit@piscarlet.be>
    >>>>>>> wrote:
    >>>>>>>
    >>>>>>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>>>>>> news:op.uol90txg4buhsv@fx62.mshome.net...

    >
    >>>>>>>

    >
    >>>>>>>>
    >>>>>>>> Let the majority decide to *not* use line length > 80.
    >>>>>>>> If you want it more .... it's up to you,
    >>>>>>>> but please follow the usenet habits/etiquette !!!
    >>>>>>>
    >>>>>>> You've just contradicted yourself, you're saying people should not
    >>>>>>> change
    >>>>>>> but people should decide!
    >>>>>>>
    >>>>>>>> http://www.cs.tut.fi/~jkorpela/usenet/dont.html
    >>>>>>>> say: line length under 80 (preferably under 72) characters;
    >>>>>>>>
    >>>>>>>> http://www.faqs.org/faqs/usenet/primer/part1/
    >>>>>>>> say:
    >>>>>>>> Try to keep your text in a generic format. Many (if not most) of
    >>>>>>>> the people reading Usenet do so from 80 column terminals or from
    >>>>>>>> workstations with 80 column terminal windows. Try to keep your
    >>>>>>>> lines of text to less than 80 characters for optimal readability.
    >>>>>>>> If people quote part of your article in a followup, short lines
    >>>>>>>> will
    >>>>>>>> probably show up better, too.
    >>>>>>>
    >>>>>>> I'm using format flowed. It's a standard, live with it.
    >>>>>>>
    >>>>>>
    >>>>>> You speak as microsoft claiming that the microsoft's standards is
    >>>>>> *the*
    >>>>>> standard.
    >>>>>> If you want to use Usenet (it's here) it's better to follow the
    >>>>>> Usenet's
    >>>>>> standard.
    >>>>>
    >>>>> It's a new standard. And not that new either. Do you object to SATA
    >>>>> because PATA is *the* standard?
    >>>>
    >>>>
    >>>> Where did you find that usenet must follow your standard ?
    >>>
    >>> I did not invent this standard.

    >>
    >> Everybody knows that - you did not answer the question ...

    >
    > How can I answer a question that is incorrect?
    >
    > What would you answer to "Have you stopped beating your wife yet?"


    The question i asked was: "Where did you find that usenet must follow your
    standard ?"
    The question is not incorrect, because you said that usenet must use
    line-length > 80 chars because long lines is a "standard" ....
    I rephrase the question:
    Where did you find that usenet must use long lines ?



  13. #33
    ray
    Guest

    Re: PIR interfering with wireless network

    "Peter Hucker" <none@spam.com> wrote in message
    news:op.uox2ypww4buhsv@fx62.mshome.net...
    > On Thu, 05 Feb 2009 22:23:15 -0000, ray <raymond.schmit@piscarlet.be>
    > wrote:
    >
    >> "Peter Hucker" <none@spam.com> wrote in message
    >> news:op.uov9uvpn4buhsv@fx62.mshome.net...
    >>> On Wed, 04 Feb 2009 21:28:19 -0000, Les Cargill <lcargill@cfl.rr.com>
    >>> wrote:
    >>>
    >>>> Peter Hucker wrote:
    >>>>> On Tue, 03 Feb 2009 20:14:08 -0000, Dave J. <requiem@freeuk.com>
    >>>>> wrote:
    >>>>>
    >>>>>> In MsgID<op.uoqtnsvf4buhsv@fx62.mshome.net> on Mon, 02 Feb 2009
    >>>>>> 21:22:30
    >>>>>> -0000, in comp.os.ms-windows.networking.misc, 'Peter Hucker' wrote:
    >>>>>>

    >
    >>>>>>>> Not his fault if he can't spell RFC..
    >>>>>>> Rules are for the obedience of fools and the guidance of wise men.
    >>>>>> It's not a rule, it's a standard. There's no obligation to follow it,
    >>>>>> it's
    >>>>>> just there in case you want to cooperate with the majority.
    >>>>>
    >>>>> There are two standards.
    >>>>
    >>>> Not really.
    >>>>
    >>>> Here's old and weary standard RFC 977:
    >>>>
    >>>> "...Text is sent as a series of
    >>>> successive lines of textual matter, each terminated with CR-LF pair."
    >>>>
    >>>> http://www.faqs.org/rfcs/rfc977.html
    >>>>
    >>>> Section 2.4.1
    >>>>
    >>>> So if you expect people to see things in lines, you're on
    >>>> the hook to add the carriage returns/line feeds. If you don't
    >>>> some boogerhead might complain about it :)
    >>>>
    >>>> Debate-fun is what it is, but ... your position isn't
    >>>> that tenable. "Be liberal in what you accept, and
    >>>> conservative in what you send." - Jon Postrel,
    >>>> RFC760/RFC1122 .
    >>>>
    >>>> (All this noise is simply here to inform, not to score
    >>>> points or something. It should be merely interesting.)
    >>>
    >>> But there is also this (which ties in with the more advanced
    >>> auto-wrapping
    >>> capablities of every word processor):
    >>> http://joeclark.org/ffaq.html
    >>>

    >>
    >>
    >> Usenet have nothing to do with a "word processor" ...

    >
    > Both display paragraphs of text on your screen. Why should the display
    > engine be different?


    Usenet is *not* a display engine - it's a way for communicating with a
    maximum of persons using a lot of different usenet-clients. Politely i'ts
    better to permit every body to read your text, so the limit of 80 chars is a
    good idea - specially when some usenet-client truncate long lines rending
    your text unreadable.



  14. #34
    Gerhard Fiedler
    Guest

    Re: PIR interfering with wireless network

    Les Cargill wrote:

    > http://www.faqs.org/rfcs/rfc977.html
    > [...]
    > (All this noise is simply here to inform, not to score
    > points or something. It should be merely interesting.)


    Right. There's also <http://www.ietf.org/rfc/rfc3676.txt>

    Gerhard

  15. #35
    Peter Hucker
    Guest

    Re: PIR interfering with wireless network

    On Fri, 06 Feb 2009 20:46:30 -0000, ray <raymond.schmit@piscarlet.be> wrote:

    > "Peter Hucker" <none@spam.com> wrote in message
    > news:op.uox2v0xq4buhsv@fx62.mshome.net...
    >> On Thu, 05 Feb 2009 22:21:11 -0000, ray <raymond.schmit@piscarlet.be>
    >> wrote:
    >>
    >>> "Peter Hucker" <none@spam.com> wrote in message
    >>> news:op.uov9u8qj4buhsv@fx62.mshome.net...
    >>>> On Wed, 04 Feb 2009 21:31:34 -0000, ray <raymond.schmit@piscarlet.be>
    >>>> wrote:
    >>>>
    >>>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>>> news:op.uoug5awt4buhsv@fx62.mshome.net...
    >>>>>> On Mon, 02 Feb 2009 23:33:13 -0000, ray <raymond.schmit@piscarlet.be>
    >>>>>> wrote:
    >>>>>>
    >>>>>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>>>>> news:op.uoqtil1j4buhsv@fx62.mshome.net...


    >>


    >>


    >>>>>>>
    >>>>>>> You speak as microsoft claiming that the microsoft's standards is
    >>>>>>> *the*
    >>>>>>> standard.
    >>>>>>> If you want to use Usenet (it's here) it's better to follow the
    >>>>>>> Usenet's
    >>>>>>> standard.
    >>>>>>
    >>>>>> It's a new standard. And not that new either. Do you object to SATA
    >>>>>> because PATA is *the* standard?
    >>>>>
    >>>>>
    >>>>> Where did you find that usenet must follow your standard ?
    >>>>
    >>>> I did not invent this standard.
    >>>
    >>> Everybody knows that - you did not answer the question ...

    >>
    >> How can I answer a question that is incorrect?
    >>
    >> What would you answer to "Have you stopped beating your wife yet?"

    >
    > The question i asked was: "Where did you find that usenet must follow your
    > standard ?"
    > The question is not incorrect, because you said that usenet must use
    > line-length > 80 chars because long lines is a "standard" ....
    > I rephrase the question:
    > Where did you find that usenet must use long lines ?


    That makes more sense. It was "YOUR standard" which was illogical.

    It's still wrong though, they are not long lines. They are the length of your screen. Unless your "newsreader" can't do word wrap.


    --
    http://www.petersparrots.com http://www.insanevideoclips.com http://www.petersphotos.com

    A very loud, unattractive, mean-acting woman walks into Wal-Mart with her two kids in tow, screaming obscenities at them all the way through the entrance.
    The Wal-Mart Greeter says, "Good morning and welcome to Wal-Mart.... Nice children you've got there - are they twins?"
    The ugly woman stops screaming long enough to say, "Hell no they ain't, the oldest one, he's 9 and the younger one, she's 7.
    Why the hell would you think they're twins?........ Do you really think they look alike?"
    "No", replies the greeter, "I just couldn't believe you got laid twice!"

  16. #36
    Peter Hucker
    Guest

    Re: PIR interfering with wireless network

    On Fri, 06 Feb 2009 20:51:06 -0000, ray <raymond.schmit@piscarlet.be> wrote:

    > "Peter Hucker" <none@spam.com> wrote in message
    > news:op.uox2ypww4buhsv@fx62.mshome.net...
    >> On Thu, 05 Feb 2009 22:23:15 -0000, ray <raymond.schmit@piscarlet.be>
    >> wrote:
    >>
    >>> "Peter Hucker" <none@spam.com> wrote in message
    >>> news:op.uov9uvpn4buhsv@fx62.mshome.net...
    >>>> On Wed, 04 Feb 2009 21:28:19 -0000, Les Cargill <lcargill@cfl.rr.com>
    >>>> wrote:
    >>>>
    >>>>> Peter Hucker wrote:
    >>>>>> On Tue, 03 Feb 2009 20:14:08 -0000, Dave J. <requiem@freeuk.com>
    >>>>>> wrote:
    >>>>>>
    >>>>>>> In MsgID<op.uoqtnsvf4buhsv@fx62.mshome.net> on Mon, 02 Feb 2009
    >>>>>>> 21:22:30
    >>>>>>> -0000, in comp.os.ms-windows.networking.misc, 'Peter Hucker' wrote:
    >>>>>>>

    >>


    >>>>>>> It's not a rule, it's a standard. There's no obligation to follow it,
    >>>>>>> it's
    >>>>>>> just there in case you want to cooperate with the majority.
    >>>>>>
    >>>>>> There are two standards.
    >>>>>
    >>>>> Not really.
    >>>>>
    >>>>> Here's old and weary standard RFC 977:
    >>>>>
    >>>>> "...Text is sent as a series of
    >>>>> successive lines of textual matter, each terminated with CR-LF pair."
    >>>>>
    >>>>> http://www.faqs.org/rfcs/rfc977.html
    >>>>>
    >>>>> Section 2.4.1
    >>>>>
    >>>>> So if you expect people to see things in lines, you're on
    >>>>> the hook to add the carriage returns/line feeds. If you don't
    >>>>> some boogerhead might complain about it :)
    >>>>>
    >>>>> Debate-fun is what it is, but ... your position isn't
    >>>>> that tenable. "Be liberal in what you accept, and
    >>>>> conservative in what you send." - Jon Postrel,
    >>>>> RFC760/RFC1122 .
    >>>>>
    >>>>> (All this noise is simply here to inform, not to score
    >>>>> points or something. It should be merely interesting.)
    >>>>
    >>>> But there is also this (which ties in with the more advanced
    >>>> auto-wrapping
    >>>> capablities of every word processor):
    >>>> http://joeclark.org/ffaq.html
    >>>>
    >>>
    >>>
    >>> Usenet have nothing to do with a "word processor" ...

    >>
    >> Both display paragraphs of text on your screen. Why should the display
    >> engine be different?

    >
    > Usenet is *not* a display engine - it's a way for communicating with a
    > maximum of persons using a lot of different usenet-clients. Politely i'ts
    > better to permit every body to read your text, so the limit of 80 chars is a
    > good idea - specially when some usenet-client truncate long lines rending
    > your text unreadable.


    Why should I cater for people with out of date shite?

    --
    http://www.petersparrots.com http://www.insanevideoclips.com http://www.petersphotos.com

    An elderly couple were on a cruise and it was really stormy. They were standing on the back of the boat watching the moon, when a wave came up and washed the old woman overboard. They searched for days and couldn't find her, so the captain sent the old man back to shore with the promise that he would notify him as soon as they found something. Three weeks went by and finally the old man got a fax from the boat. It read: 'Sir, sorry to inform you, we found your wife dead at the bottom of the ocean. We hauled her up to the deck and attached to her butt was an oyster and in it was a pearl worth $50,000 . Please advise.' The old man faxed back: 'Send me the pearl and re-bait the trap.'

  17. #37
    ray
    Guest

    Re: PIR interfering with wireless network

    "Peter Hucker" <none@spam.com> wrote in message
    news:op.uoydnkkh4buhsv@fx62.mshome.net...
    > On Fri, 06 Feb 2009 20:46:30 -0000, ray <raymond.schmit@piscarlet.be>
    > wrote:
    >
    >> "Peter Hucker" <none@spam.com> wrote in message
    >> news:op.uox2v0xq4buhsv@fx62.mshome.net...
    >>> On Thu, 05 Feb 2009 22:21:11 -0000, ray <raymond.schmit@piscarlet.be>
    >>> wrote:
    >>>
    >>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>> news:op.uov9u8qj4buhsv@fx62.mshome.net...
    >>>>> On Wed, 04 Feb 2009 21:31:34 -0000, ray <raymond.schmit@piscarlet.be>
    >>>>> wrote:
    >>>>>
    >>>>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>>>> news:op.uoug5awt4buhsv@fx62.mshome.net...
    >>>>>>> On Mon, 02 Feb 2009 23:33:13 -0000, ray
    >>>>>>> <raymond.schmit@piscarlet.be>
    >>>>>>> wrote:
    >>>>>>>
    >>>>>>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>>>>>> news:op.uoqtil1j4buhsv@fx62.mshome.net...

    >
    >>>

    >
    >>>

    >
    >>>>>>>>
    >>>>>>>> You speak as microsoft claiming that the microsoft's standards is
    >>>>>>>> *the*
    >>>>>>>> standard.
    >>>>>>>> If you want to use Usenet (it's here) it's better to follow the
    >>>>>>>> Usenet's
    >>>>>>>> standard.
    >>>>>>>
    >>>>>>> It's a new standard. And not that new either. Do you object to
    >>>>>>> SATA
    >>>>>>> because PATA is *the* standard?
    >>>>>>
    >>>>>>
    >>>>>> Where did you find that usenet must follow your standard ?
    >>>>>
    >>>>> I did not invent this standard.
    >>>>
    >>>> Everybody knows that - you did not answer the question ...
    >>>
    >>> How can I answer a question that is incorrect?
    >>>
    >>> What would you answer to "Have you stopped beating your wife yet?"

    >>
    >> The question i asked was: "Where did you find that usenet must follow
    >> your
    >> standard ?"
    >> The question is not incorrect, because you said that usenet must use
    >> line-length > 80 chars because long lines is a "standard" ....
    >> I rephrase the question:
    >> Where did you find that usenet must use long lines ?

    >
    > That makes more sense. It was "YOUR standard" which was illogical.


    This is not MY standard, i have no standard ... i just follow the RFC ...and
    this his logical, because you expect that everybody have your
    material/configuration/visual acuity/etc....


    > It's still wrong though, they are not long lines. They are the length of
    > your screen. Unless your "newsreader" can't do word wrap.


    This is really long lines .. perhaps you don't know what a line length is
    ....



  18. #38
    ray
    Guest

    Re: PIR interfering with wireless network

    "Peter Hucker" <none@spam.com> wrote in message
    news:op.uoydn9q14buhsv@fx62.mshome.net...
    > On Fri, 06 Feb 2009 20:51:06 -0000, ray <raymond.schmit@piscarlet.be>
    > wrote:
    >
    >> "Peter Hucker" <none@spam.com> wrote in message
    >> news:op.uox2ypww4buhsv@fx62.mshome.net...
    >>> On Thu, 05 Feb 2009 22:23:15 -0000, ray <raymond.schmit@piscarlet.be>
    >>> wrote:
    >>>
    >>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>> news:op.uov9uvpn4buhsv@fx62.mshome.net...
    >>>>> On Wed, 04 Feb 2009 21:28:19 -0000, Les Cargill <lcargill@cfl.rr.com>
    >>>>> wrote:
    >>>>>
    >>>>>> Peter Hucker wrote:
    >>>>>>> On Tue, 03 Feb 2009 20:14:08 -0000, Dave J. <requiem@freeuk.com>
    >>>>>>> wrote:
    >>>>>>>
    >>>>>>>> In MsgID<op.uoqtnsvf4buhsv@fx62.mshome.net> on Mon, 02 Feb 2009
    >>>>>>>> 21:22:30
    >>>>>>>> -0000, in comp.os.ms-windows.networking.misc, 'Peter Hucker' wrote:
    >>>>>>>>
    >>>

    >
    >>>>>>>> It's not a rule, it's a standard. There's no obligation to follow
    >>>>>>>> it,
    >>>>>>>> it's
    >>>>>>>> just there in case you want to cooperate with the majority.
    >>>>>>>
    >>>>>>> There are two standards.
    >>>>>>
    >>>>>> Not really.
    >>>>>>
    >>>>>> Here's old and weary standard RFC 977:
    >>>>>>
    >>>>>> "...Text is sent as a series of
    >>>>>> successive lines of textual matter, each terminated with CR-LF pair."
    >>>>>>
    >>>>>> http://www.faqs.org/rfcs/rfc977.html
    >>>>>>
    >>>>>> Section 2.4.1
    >>>>>>
    >>>>>> So if you expect people to see things in lines, you're on
    >>>>>> the hook to add the carriage returns/line feeds. If you don't
    >>>>>> some boogerhead might complain about it :)
    >>>>>>
    >>>>>> Debate-fun is what it is, but ... your position isn't
    >>>>>> that tenable. "Be liberal in what you accept, and
    >>>>>> conservative in what you send." - Jon Postrel,
    >>>>>> RFC760/RFC1122 .
    >>>>>>
    >>>>>> (All this noise is simply here to inform, not to score
    >>>>>> points or something. It should be merely interesting.)
    >>>>>
    >>>>> But there is also this (which ties in with the more advanced
    >>>>> auto-wrapping
    >>>>> capablities of every word processor):
    >>>>> http://joeclark.org/ffaq.html
    >>>>>
    >>>>
    >>>>
    >>>> Usenet have nothing to do with a "word processor" ...
    >>>
    >>> Both display paragraphs of text on your screen. Why should the display
    >>> engine be different?

    >>
    >> Usenet is *not* a display engine - it's a way for communicating with a
    >> maximum of persons using a lot of different usenet-clients. Politely i'ts
    >> better to permit every body to read your text, so the limit of 80 chars
    >> is a
    >> good idea - specially when some usenet-client truncate long lines rending
    >> your text unreadable.

    >
    > Why should I cater for people with out of date shite?
    >

    This is exactly the reason why i wrote "Politely"....



  19. #39
    ray
    Guest

    Re: PIR interfering with wireless network

    "Gerhard Fiedler" <gelists@gmail.com> wrote in message
    news:1n6b3ult87w2f.dlg@gelists.gmail.com...
    > Les Cargill wrote:
    >
    >> http://www.faqs.org/rfcs/rfc977.html
    >> [...]
    >> (All this noise is simply here to inform, not to score
    >> points or something. It should be merely interesting.)

    >
    > Right. There's also <http://www.ietf.org/rfc/rfc3676.txt>
    >

    Very interesting, but he said:
    "Why should I cater for people ...."



  20. #40
    Peter Hucker
    Guest

    Re: PIR interfering with wireless network

    On Sat, 07 Feb 2009 16:26:55 -0000, ray <raymond.schmit@piscarlet.be> wrote:

    > "Peter Hucker" <none@spam.com> wrote in message
    > news:op.uoydnkkh4buhsv@fx62.mshome.net...
    >> On Fri, 06 Feb 2009 20:46:30 -0000, ray <raymond.schmit@piscarlet.be>
    >> wrote:
    >>
    >>> "Peter Hucker" <none@spam.com> wrote in message
    >>> news:op.uox2v0xq4buhsv@fx62.mshome.net...
    >>>> On Thu, 05 Feb 2009 22:21:11 -0000, ray <raymond.schmit@piscarlet.be>
    >>>> wrote:
    >>>>
    >>>>> "Peter Hucker" <none@spam.com> wrote in message
    >>>>> news:op.uov9u8qj4buhsv@fx62.mshome.net...
    >>>>>> On Wed, 04 Feb 2009 21:31:34 -0000, ray <raymond.schmit@piscarlet.be>
    >>>>>> wrote:
    >>>>>>
    >>>>>>> Where did you find that usenet must follow your standard ?
    >>>>>>
    >>>>>> I did not invent this standard.
    >>>>>
    >>>>> Everybody knows that - you did not answer the question ...
    >>>>
    >>>> How can I answer a question that is incorrect?
    >>>>
    >>>> What would you answer to "Have you stopped beating your wife yet?"
    >>>
    >>> The question i asked was: "Where did you find that usenet must follow
    >>> your
    >>> standard ?"
    >>> The question is not incorrect, because you said that usenet must use
    >>> line-length > 80 chars because long lines is a "standard" ....
    >>> I rephrase the question:
    >>> Where did you find that usenet must use long lines ?

    >>
    >> That makes more sense. It was "YOUR standard" which was illogical.

    >
    > This is not MY standard, i have no standard ...


    I was quoting you, so "YOUR" referred to me. This is beginning to sound like something from Alice in Wonderland.

    > i just follow the RFC ...and
    > this his logical, because you expect that everybody have your
    > material/configuration/visual acuity/etc....


    I expect people to be able to view my text at their screen width by simply wrapping it.

    >> It's still wrong though, they are not long lines. They are the length of
    >> your screen. Unless your "newsreader" can't do word wrap.

    >
    > This is really long lines .. perhaps you don't know what a line length is
    > ...


    What?

    --
    http://www.petersparrots.com http://www.insanevideoclips.com http://www.petersphotos.com

    Stress is the conflict which occurs when your mind prevents your body from beating the living daylights out of whoever got in your way.

Similar Threads

  1. major problem creating wireless network with toucan
    By chelsea86 in forum General Broadband Forum
    Replies: 1
    Last Post: 10-07-08, 10:12 AM
  2. Wireless network to ethernet lan
    By samerking in forum Wireless Networks & Routers
    Replies: 0
    Last Post: 06-30-07, 11:27 AM
  3. Because of my wireless card or the wireless network??
    By Mahalo in forum Wireless Networks & Routers
    Replies: 3
    Last Post: 04-17-07, 02:23 PM
  4. Mixing a wireless router and an ethernet switch. How?
    By jb22 in forum Networking Forum
    Replies: 4
    Last Post: 03-06-07, 04:57 PM
  5. I need help with my wireless network...lost and stuck!
    By insuranceman in forum Wireless Networks & Routers
    Replies: 2
    Last Post: 02-07-07, 02:10 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •