NO

  • Thread starter Thread starter nellie
  • Start date Start date
Re: NO

Nellie (if that is even who you are),
Nobody here is trying or wanting to hurt you, in fact, many have
made 'out-of-their-way' attempts to help you! I remind you that YOU did
your share of false accusations and name calling, so, let's just drop that
part.
Your last post displays progress, good for you. Whole words are
much easier to interpret. Now, release your CAPS lock and let's start
working on some punctuation to go along with the wonderful whole words that
we now know you are capable of!
If you truly want help, you must start by helping yourself......and
I am most serious about this! The first step for you will be to read and
comply with the 'rules of posting' that I have copied from the aumha.org
website, written by Mr. Jim Eshelman.
Jim is one of the best in the business. This forum has a large
number of very professional, knowledgeable, understanding, patient and
helpful people you will ever find in one place! You want help....this is
your help. Use it well, it is your key to all the help you will ever need
regarding computers.

Newgroup Rules:
a.. Do some research first...
a.. Consult the online Help and the manual.
b.. Search the Internet, put key words about the problem into a Search
Engine like DTS-L Fast Search.
c.. If you still can't find the answer, post to Microsoft Product
Support Newsgroups.
d.. First use the "Find" function on the newsreader to locate other
messages about the problem.
e.. Or use this Advanced Group Search Utility designed to filter the
vast amount of information found on the WWW.
b..
Decide where to post...
a.. Post to one general group if you are not sure which group applies,
ask where the best place is to ask your question.
c.. How to compose your post...
a.. Create a new message, don't post a question of your own in response
to another question.
b.. Make the "Subject line" a short, relevant synopsis of your problem.
c.. Before going into detail, clearly summarize the problem.
d.. Make a concise, clear description of the problem.
e.. Unless multiple problems seem related, do not mix them together,
make separate posts.
f.. If you are getting error messages, include the exact text in the
error message. If there is a "Details" button, click it and copy/paste the
error message itself into the post. If you are using Windows Millennium
Edition (Windows Me) press Atl+D to bring up the detailed error message. For
XP, if there is an Event ID and Source, include it as well.
g.. Tell if an error occurs when doing some action or using some
particular software.
h.. What changed in your system shortly before the problem occurred?
Knowing about a setting change or added software or hardware may be helpful
in solving the problem.
i.. Briefly describe your machine, video card, CPU, amount of RAM, hard
drive size and amount of free space.
j.. Identify clearly the steps and procedures you have already used to
try to fix the problem.
k.. Proof-read and spell-check the post before sending.
d.. After you post...
a.. Be patient waiting for a response, it may take a couple of days or
more before the right person sees the question.
b.. You should carefully assess any advice you get. If there is bad
information in a posted response, someone will almost always correct it. Ask
for clarification if you aren't certain.
c.. If you don't get a response, it is probably because either the
answer is unknown, perhaps your question was not understood or the
information originally provided was not clear enough. If this occurs,
posting an amended question could produce a better result.
d.. Once your problem is solved...
a.. It is useful to post back to the group afterwards, saying thanks
and that a suggestion worked (or not). That tells the group if it is a
useful solution.
e.. Survival Camp: posting errors to avoid...
a.. Don't ask for an email reply unless absolutely necessary, and then
follow up to the group with a summary.
b.. Avoid cross-posting, unless your problem clearly fits the category
of more than one group.
c.. Never post separate identical messages to several newsgroups. This
wastes respondents' time, and may result in you being ignored.
d.. Don't attach screen shots or files. If you believe a screen shot
or file is critical to understanding your problem, advise that it exists and
offer to send it.
e.. Don't post in ALL CAPITALS, it's too hard to read
f.. Remove unnecessary included text from replies.
g.. Use punctuation.
h.. Stick to plain text, use html format only if necessary to explain
your problem. The stationery groups are exceptions to this.
i.. Avoid poor subject lines like these:
a.. HEEEELLLLLLLPPPPPPPPP!!!!!!!!!!!!
b.. any experts around here?
c.. <Name of person> EMAIL ME!!!
d.. need help please
e.. Bill Gates is the Devil
f.. idontknowwhattodomycomputerquit
g.. Read the Microsoft Rules of Conduct
Heirloom, old and more than willing to help without hurt

"nellie" <nellie@______.com> wrote in message
news:O0W$2sOgIHA.1184@TK2MSFTNGP04.phx.gbl...
> PLEASE STOP
> ALL I WANTED WAS YOUR HELP
> ENOUGH HURTING ME
>
>
>
>
>
 
Re: NO

Heirloom:

Can't you see this individual needs some serious, professional help, which
you can't give, obviously. Dave has the right idea with his 'pets', try to
'read' them correctly.
Maybe you know someone who can 'save' nellie? <H>.


"Heirloom" <nobodyhome@noplacelike.hom> wrote in message
news:Ox5udsTgIHA.4436@TK2MSFTNGP02.phx.gbl...
> Nellie (if that is even who you are),
> Nobody here is trying or wanting to hurt you, in fact, many have
> made 'out-of-their-way' attempts to help you! I remind you that YOU did
> your share of false accusations and name calling, so, let's just drop that
> part.
> Your last post displays progress, good for you. Whole words are
> much easier to interpret. Now, release your CAPS lock and let's start
> working on some punctuation to go along with the wonderful whole words
that
> we now know you are capable of!
> If you truly want help, you must start by helping
yourself......and
> I am most serious about this! The first step for you will be to read and
> comply with the 'rules of posting' that I have copied from the aumha.org
> website, written by Mr. Jim Eshelman.
> Jim is one of the best in the business. This forum has a large
> number of very professional, knowledgeable, understanding, patient and
> helpful people you will ever find in one place! You want help....this is
> your help. Use it well, it is your key to all the help you will ever need
> regarding computers.
>
> Newgroup Rules:
> a.. Do some research first...
> a.. Consult the online Help and the manual.
> b.. Search the Internet, put key words about the problem into a Search
> Engine like DTS-L Fast Search.
> c.. If you still can't find the answer, post to Microsoft Product
> Support Newsgroups.
> d.. First use the "Find" function on the newsreader to locate other
> messages about the problem.
> e.. Or use this Advanced Group Search Utility designed to filter the
> vast amount of information found on the WWW.
> b..
> Decide where to post...
> a.. Post to one general group if you are not sure which group applies,
> ask where the best place is to ask your question.
> c.. How to compose your post...
> a.. Create a new message, don't post a question of your own in
response
> to another question.
> b.. Make the "Subject line" a short, relevant synopsis of your
problem.
> c.. Before going into detail, clearly summarize the problem.
> d.. Make a concise, clear description of the problem.
> e.. Unless multiple problems seem related, do not mix them together,
> make separate posts.
> f.. If you are getting error messages, include the exact text in the
> error message. If there is a "Details" button, click it and copy/paste the
> error message itself into the post. If you are using Windows Millennium
> Edition (Windows Me) press Atl+D to bring up the detailed error message.
For
> XP, if there is an Event ID and Source, include it as well.
> g.. Tell if an error occurs when doing some action or using some
> particular software.
> h.. What changed in your system shortly before the problem occurred?
> Knowing about a setting change or added software or hardware may be
helpful
> in solving the problem.
> i.. Briefly describe your machine, video card, CPU, amount of RAM,
hard
> drive size and amount of free space.
> j.. Identify clearly the steps and procedures you have already used to
> try to fix the problem.
> k.. Proof-read and spell-check the post before sending.
> d.. After you post...
> a.. Be patient waiting for a response, it may take a couple of days or
> more before the right person sees the question.
> b.. You should carefully assess any advice you get. If there is bad
> information in a posted response, someone will almost always correct it.
Ask
> for clarification if you aren't certain.
> c.. If you don't get a response, it is probably because either the
> answer is unknown, perhaps your question was not understood or the
> information originally provided was not clear enough. If this occurs,
> posting an amended question could produce a better result.
> d.. Once your problem is solved...
> a.. It is useful to post back to the group afterwards, saying
thanks
> and that a suggestion worked (or not). That tells the group if it is a
> useful solution.
> e.. Survival Camp: posting errors to avoid...
> a.. Don't ask for an email reply unless absolutely necessary, and
then
> follow up to the group with a summary.
> b.. Avoid cross-posting, unless your problem clearly fits the
category
> of more than one group.
> c.. Never post separate identical messages to several newsgroups.
This
> wastes respondents' time, and may result in you being ignored.
> d.. Don't attach screen shots or files. If you believe a screen shot
> or file is critical to understanding your problem, advise that it exists
and
> offer to send it.
> e.. Don't post in ALL CAPITALS, it's too hard to read
> f.. Remove unnecessary included text from replies.
> g.. Use punctuation.
> h.. Stick to plain text, use html format only if necessary to
explain
> your problem. The stationery groups are exceptions to this.
> i.. Avoid poor subject lines like these:
> a.. HEEEELLLLLLLPPPPPPPPP!!!!!!!!!!!!
> b.. any experts around here?
> c.. <Name of person> EMAIL ME!!!
> d.. need help please
> e.. Bill Gates is the Devil
> f.. idontknowwhattodomycomputerquit
> g.. Read the Microsoft Rules of Conduct
> Heirloom, old and more than willing to help without hurt
>
> "nellie" <nellie@______.com> wrote in message
> news:O0W$2sOgIHA.1184@TK2MSFTNGP04.phx.gbl...
> > PLEASE STOP
> > ALL I WANTED WAS YOUR HELP
> > ENOUGH HURTING ME
> >
> >
> >
> >
> >
>
>
 
Re: NO

Colour me "cynical", but I don't think "Nellie" needs any mental help at
all. Simply a troll.....but keep on answering if you think otherwise.
I will just not bother reading the posts.

HF
"webster72n" <webster72n@gmail.com> wrote in message
news:uCRV9zUgIHA.4536@TK2MSFTNGP06.phx.gbl...
> Heirloom:
>
> Can't you see this individual needs some serious, professional help,
> which
> you can't give, obviously. Dave has the right idea with his 'pets',
> try to
> 'read' them correctly.
> Maybe you know someone who can 'save' nellie? <H>.
>
>
> "Heirloom" <nobodyhome@noplacelike.hom> wrote in message
> news:Ox5udsTgIHA.4436@TK2MSFTNGP02.phx.gbl...
>> Nellie (if that is even who you are),
>> Nobody here is trying or wanting to hurt you, in fact, many
>> have
>> made 'out-of-their-way' attempts to help you! I remind you that YOU
>> did
>> your share of false accusations and name calling, so, let's just drop
>> that
>> part.
>> Your last post displays progress, good for you. Whole words
>> are
>> much easier to interpret. Now, release your CAPS lock and let's
>> start
>> working on some punctuation to go along with the wonderful whole
>> words
> that
>> we now know you are capable of!
>> If you truly want help, you must start by helping
> yourself......and
>> I am most serious about this! The first step for you will be to read
>> and
>> comply with the 'rules of posting' that I have copied from the
>> aumha.org
>> website, written by Mr. Jim Eshelman.
>> Jim is one of the best in the business. This forum has a
>> large
>> number of very professional, knowledgeable, understanding, patient
>> and
>> helpful people you will ever find in one place! You want
>> help....this is
>> your help. Use it well, it is your key to all the help you will ever
>> need
>> regarding computers.
>>
>> Newgroup Rules:
>> a.. Do some research first...
>> a.. Consult the online Help and the manual.
>> b.. Search the Internet, put key words about the problem into a
>> Search
>> Engine like DTS-L Fast Search.
>> c.. If you still can't find the answer, post to Microsoft Product
>> Support Newsgroups.
>> d.. First use the "Find" function on the newsreader to locate
>> other
>> messages about the problem.
>> e.. Or use this Advanced Group Search Utility designed to filter
>> the
>> vast amount of information found on the WWW.
>> b..
>> Decide where to post...
>> a.. Post to one general group if you are not sure which group
>> applies,
>> ask where the best place is to ask your question.
>> c.. How to compose your post...
>> a.. Create a new message, don't post a question of your own in
> response
>> to another question.
>> b.. Make the "Subject line" a short, relevant synopsis of your
> problem.
>> c.. Before going into detail, clearly summarize the problem.
>> d.. Make a concise, clear description of the problem.
>> e.. Unless multiple problems seem related, do not mix them
>> together,
>> make separate posts.
>> f.. If you are getting error messages, include the exact text in
>> the
>> error message. If there is a "Details" button, click it and
>> copy/paste the
>> error message itself into the post. If you are using Windows
>> Millennium
>> Edition (Windows Me) press Atl+D to bring up the detailed error
>> message.
> For
>> XP, if there is an Event ID and Source, include it as well.
>> g.. Tell if an error occurs when doing some action or using some
>> particular software.
>> h.. What changed in your system shortly before the problem
>> occurred?
>> Knowing about a setting change or added software or hardware may be
> helpful
>> in solving the problem.
>> i.. Briefly describe your machine, video card, CPU, amount of
>> RAM,
> hard
>> drive size and amount of free space.
>> j.. Identify clearly the steps and procedures you have already
>> used to
>> try to fix the problem.
>> k.. Proof-read and spell-check the post before sending.
>> d.. After you post...
>> a.. Be patient waiting for a response, it may take a couple of
>> days or
>> more before the right person sees the question.
>> b.. You should carefully assess any advice you get. If there is
>> bad
>> information in a posted response, someone will almost always correct
>> it.
> Ask
>> for clarification if you aren't certain.
>> c.. If you don't get a response, it is probably because either
>> the
>> answer is unknown, perhaps your question was not understood or the
>> information originally provided was not clear enough. If this occurs,
>> posting an amended question could produce a better result.
>> d.. Once your problem is solved...
>> a.. It is useful to post back to the group afterwards, saying
> thanks
>> and that a suggestion worked (or not). That tells the group if it is
>> a
>> useful solution.
>> e.. Survival Camp: posting errors to avoid...
>> a.. Don't ask for an email reply unless absolutely necessary,
>> and
> then
>> follow up to the group with a summary.
>> b.. Avoid cross-posting, unless your problem clearly fits the
> category
>> of more than one group.
>> c.. Never post separate identical messages to several
>> newsgroups.
> This
>> wastes respondents' time, and may result in you being ignored.
>> d.. Don't attach screen shots or files. If you believe a screen
>> shot
>> or file is critical to understanding your problem, advise that it
>> exists
> and
>> offer to send it.
>> e.. Don't post in ALL CAPITALS, it's too hard to read
>> f.. Remove unnecessary included text from replies.
>> g.. Use punctuation.
>> h.. Stick to plain text, use html format only if necessary to
> explain
>> your problem. The stationery groups are exceptions to this.
>> i.. Avoid poor subject lines like these:
>> a.. HEEEELLLLLLLPPPPPPPPP!!!!!!!!!!!!
>> b.. any experts around here?
>> c.. <Name of person> EMAIL ME!!!
>> d.. need help please
>> e.. Bill Gates is the Devil
>> f.. idontknowwhattodomycomputerquit
>> g.. Read the Microsoft Rules of Conduct
>> Heirloom, old and more than willing to help without hurt
>>
>> "nellie" <nellie@______.com> wrote in message
>> news:O0W$2sOgIHA.1184@TK2MSFTNGP04.phx.gbl...
>> > PLEASE STOP
>> > ALL I WANTED WAS YOUR HELP
>> > ENOUGH HURTING ME
>> >
>> >
>> >
>> >
>> >
>>
>>
>
>
 
Re: NO


Consider youself 'coloured', I just tried to keep H from 'exhausting'
himself.
There must be a way to get at this trolly 'nellie'.

Harry.


"Heather" <figgyd@nospam.invalid> wrote in message
news:eNKUy6VgIHA.6092@TK2MSFTNGP06.phx.gbl...
> Colour me "cynical", but I don't think "Nellie" needs any mental help at
> all. Simply a troll.....but keep on answering if you think otherwise.
> I will just not bother reading the posts.
>
> HF
> "webster72n" <webster72n@gmail.com> wrote in message
> news:uCRV9zUgIHA.4536@TK2MSFTNGP06.phx.gbl...
> > Heirloom:
> >
> > Can't you see this individual needs some serious, professional help,
> > which
> > you can't give, obviously. Dave has the right idea with his 'pets',
> > try to
> > 'read' them correctly.
> > Maybe you know someone who can 'save' nellie? <H>.
> >
> >
> > "Heirloom" <nobodyhome@noplacelike.hom> wrote in message
> > news:Ox5udsTgIHA.4436@TK2MSFTNGP02.phx.gbl...
> >> Nellie (if that is even who you are),
> >> Nobody here is trying or wanting to hurt you, in fact, many
> >> have
> >> made 'out-of-their-way' attempts to help you! I remind you that YOU
> >> did
> >> your share of false accusations and name calling, so, let's just drop
> >> that
> >> part.
> >> Your last post displays progress, good for you. Whole words
> >> are
> >> much easier to interpret. Now, release your CAPS lock and let's
> >> start
> >> working on some punctuation to go along with the wonderful whole
> >> words
> > that
> >> we now know you are capable of!
> >> If you truly want help, you must start by helping
> > yourself......and
> >> I am most serious about this! The first step for you will be to read
> >> and
> >> comply with the 'rules of posting' that I have copied from the
> >> aumha.org
> >> website, written by Mr. Jim Eshelman.
> >> Jim is one of the best in the business. This forum has a
> >> large
> >> number of very professional, knowledgeable, understanding, patient
> >> and
> >> helpful people you will ever find in one place! You want
> >> help....this is
> >> your help. Use it well, it is your key to all the help you will ever
> >> need
> >> regarding computers.
> >>
> >> Newgroup Rules:
> >> a.. Do some research first...
> >> a.. Consult the online Help and the manual.
> >> b.. Search the Internet, put key words about the problem into a
> >> Search
> >> Engine like DTS-L Fast Search.
> >> c.. If you still can't find the answer, post to Microsoft Product
> >> Support Newsgroups.
> >> d.. First use the "Find" function on the newsreader to locate
> >> other
> >> messages about the problem.
> >> e.. Or use this Advanced Group Search Utility designed to filter
> >> the
> >> vast amount of information found on the WWW.
> >> b..
> >> Decide where to post...
> >> a.. Post to one general group if you are not sure which group
> >> applies,
> >> ask where the best place is to ask your question.
> >> c.. How to compose your post...
> >> a.. Create a new message, don't post a question of your own in
> > response
> >> to another question.
> >> b.. Make the "Subject line" a short, relevant synopsis of your
> > problem.
> >> c.. Before going into detail, clearly summarize the problem.
> >> d.. Make a concise, clear description of the problem.
> >> e.. Unless multiple problems seem related, do not mix them
> >> together,
> >> make separate posts.
> >> f.. If you are getting error messages, include the exact text in
> >> the
> >> error message. If there is a "Details" button, click it and
> >> copy/paste the
> >> error message itself into the post. If you are using Windows
> >> Millennium
> >> Edition (Windows Me) press Atl+D to bring up the detailed error
> >> message.
> > For
> >> XP, if there is an Event ID and Source, include it as well.
> >> g.. Tell if an error occurs when doing some action or using some
> >> particular software.
> >> h.. What changed in your system shortly before the problem
> >> occurred?
> >> Knowing about a setting change or added software or hardware may be
> > helpful
> >> in solving the problem.
> >> i.. Briefly describe your machine, video card, CPU, amount of
> >> RAM,
> > hard
> >> drive size and amount of free space.
> >> j.. Identify clearly the steps and procedures you have already
> >> used to
> >> try to fix the problem.
> >> k.. Proof-read and spell-check the post before sending.
> >> d.. After you post...
> >> a.. Be patient waiting for a response, it may take a couple of
> >> days or
> >> more before the right person sees the question.
> >> b.. You should carefully assess any advice you get. If there is
> >> bad
> >> information in a posted response, someone will almost always correct
> >> it.
> > Ask
> >> for clarification if you aren't certain.
> >> c.. If you don't get a response, it is probably because either
> >> the
> >> answer is unknown, perhaps your question was not understood or the
> >> information originally provided was not clear enough. If this occurs,
> >> posting an amended question could produce a better result.
> >> d.. Once your problem is solved...
> >> a.. It is useful to post back to the group afterwards, saying
> > thanks
> >> and that a suggestion worked (or not). That tells the group if it is
> >> a
> >> useful solution.
> >> e.. Survival Camp: posting errors to avoid...
> >> a.. Don't ask for an email reply unless absolutely necessary,
> >> and
> > then
> >> follow up to the group with a summary.
> >> b.. Avoid cross-posting, unless your problem clearly fits the
> > category
> >> of more than one group.
> >> c.. Never post separate identical messages to several
> >> newsgroups.
> > This
> >> wastes respondents' time, and may result in you being ignored.
> >> d.. Don't attach screen shots or files. If you believe a screen
> >> shot
> >> or file is critical to understanding your problem, advise that it
> >> exists
> > and
> >> offer to send it.
> >> e.. Don't post in ALL CAPITALS, it's too hard to read
> >> f.. Remove unnecessary included text from replies.
> >> g.. Use punctuation.
> >> h.. Stick to plain text, use html format only if necessary to
> > explain
> >> your problem. The stationery groups are exceptions to this.
> >> i.. Avoid poor subject lines like these:
> >> a.. HEEEELLLLLLLPPPPPPPPP!!!!!!!!!!!!
> >> b.. any experts around here?
> >> c.. <Name of person> EMAIL ME!!!
> >> d.. need help please
> >> e.. Bill Gates is the Devil
> >> f.. idontknowwhattodomycomputerquit
> >> g.. Read the Microsoft Rules of Conduct
> >> Heirloom, old and more than willing to help without hurt
> >>
> >> "nellie" <nellie@______.com> wrote in message
> >> news:O0W$2sOgIHA.1184@TK2MSFTNGP04.phx.gbl...
> >> > PLEASE STOP
> >> > ALL I WANTED WAS YOUR HELP
> >> > ENOUGH HURTING ME
> >> >
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
>
>
 
Re: NO

nellie wrote:
> PLEASE STOP
> ALL I WANTED WAS YOUR HELP
> ENOUGH HURTING ME
>
>
>
>
>
"There must be a way to get at this trolly 'nellie'."

That would be to ignore her/him completely, no?
 
Re: NO


"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:%23DBEmaWgIHA.1184@TK2MSFTNGP04.phx.gbl...
> From: "webster72n" <webster72n@gmail.com>
>
> | Heirloom:
> |
> | Can't you see this individual needs some serious, professional help,
> which
> | you can't give, obviously. Dave has the right idea with his 'pets',
> try to
> | 'read' them correctly.
> | Maybe you know someone who can 'save' nellie? <H>.
> |
>
> I love my pets indeed.
>
Let me see if I can incorporate this one.....or perhaps you have it. I
could rename it to "Harry"....LOL.

Figgs
 
Re: NO

Maybe mine was a feeble and useless attempt and the body is not worth trying
to redeem. I'll call this my last shot. If I hit the mark, fine, if I
don't, nothing wasted except a little time and finger action.....which I
will change to a 'single digit' for the latter. :-)
Heirloom, old and must have something to
add....let's pick a winner


"richard" <rmk@wonderland.net> wrote in message
news:%23pJU9XWgIHA.5624@TK2MSFTNGP02.phx.gbl...
> nellie wrote:
>> PLEASE STOP
>> ALL I WANTED WAS YOUR HELP
>> ENOUGH HURTING ME
>>
>>
>>
>>
>>
> "There must be a way to get at this trolly 'nellie'."
>
> That would be to ignore her/him completely, no?
>
 
Re: NO


"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:eF4jcRXgIHA.5036@TK2MSFTNGP06.phx.gbl...
> From: "Heather" <figgyd@nospam.invalid>
>
>
> | Let me see if I can incorporate this one.....or perhaps you have it. I
> | could rename it to "Harry"....LOL.
> |
> | Figgs
> |
>
> :-)

.......so am I, only for a different reason....

>
> --
> Dave
> http://www.claymania.com/removal-trojan-adware.html
> Multi-AV - http://www.pctipp.ch/downloads/dl/35905.asp
>
>
>
 
Re: NO

Heirloom <nobodyhome@noplacelike.hom> wrote:

> Maybe mine was a feeble and useless attempt and the body is not worth
> trying to redeem. I'll call this my last shot. If I hit the mark,
> fine, if I don't, nothing wasted except a little time and finger
> action.....which I will change to a 'single digit' for the latter. :-)
> Heirloom, old and must have something to
> add....let's pick a winner

As if I care! <vbg>

Mike
 
Re: NO


"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:OEHCIWYgIHA.3400@TK2MSFTNGP03.phx.gbl...
> Heirloom <nobodyhome@noplacelike.hom> wrote:
>
>> Maybe mine was a feeble and useless attempt and the body is not worth
>> trying to redeem. I'll call this my last shot. If I hit the mark,
>> fine, if I don't, nothing wasted except a little time and finger
>> action.....which I will change to a 'single digit' for the latter.
>> :-)
>> Heirloom, old and must have something to
>> add....let's pick a winner
>
> As if I care! <vbg>
>
LOL....I am adding to my collection!!
 
Re: NO


"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:%23FtFeQYgIHA.1184@TK2MSFTNGP04.phx.gbl...
> From: "webster72n" <webster72n@gmail.com>
>
>
> |
> | ......so am I, only for a different reason....
> |
>
> You are OK Harry.

I just don't care for "attachments", they can mean 'a lot of trouble'!
<H>.

>
> Keep smiling. :-)
>
> --
> Dave
> http://www.claymania.com/removal-trojan-adware.html
> Multi-AV - http://www.pctipp.ch/downloads/dl/35905.asp
>
>
 
Re: NO


"webster72n" <webster72n@gmail.com> wrote in message
news:u6fVnuYgIHA.3400@TK2MSFTNGP03.phx.gbl...
|
| "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
| news:%23FtFeQYgIHA.1184@TK2MSFTNGP04.phx.gbl...
| > From: "webster72n" <webster72n@gmail.com>
| >
| >
| > |
| > | ......so am I, only for a different reason....
| > |
| >
| > You are OK Harry.
|
| I just don't care for "attachments", they can mean 'a lot of trouble'!
| <H>.

Normal for Windows :-)
 
Re: NO

<lol> What a wonderful way to spend my Sunday morning, trying to see what
I'm doing through the tears of laughter with all these little pets coming to
call <g>
Keep up the good work I'm loving it <g>
Joan

"Heather" <figgyd@nospam.invalid> wrote in message
news:ucNCWoYgIHA.4140@TK2MSFTNGP04.phx.gbl...
>
> "Mike M" <No_Spam@Corned_Beef.Only> wrote in message
> news:OEHCIWYgIHA.3400@TK2MSFTNGP03.phx.gbl...
>> Heirloom <nobodyhome@noplacelike.hom> wrote:
>>
>>> Maybe mine was a feeble and useless attempt and the body is not worth
>>> trying to redeem. I'll call this my last shot. If I hit the mark,
>>> fine, if I don't, nothing wasted except a little time and finger
>>> action.....which I will change to a 'single digit' for the latter. :-)
>>> Heirloom, old and must have something to
>>> add....let's pick a winner
>>
>> As if I care! <vbg>
>>
> LOL....I am adding to my collection!!
>
>
>
 

Similar threads

AWS
Downtime
Replies
0
Views
53
AWS
AWS
AWS
Site Upgraded
Replies
1
Views
31
Cloaked
Cloaked
F
Menu drop down appears at top left of screen
Replies
0
Views
75
FrankieQ
F
onmy
Computer Security
Replies
0
Views
264
onmy
onmy
J
Creating a Tree data structure
Replies
0
Views
59
Jalil Sear [MCPD SharePoint]
J
Back
Top