T
txgeek
unable to logon. did not forget PW. sometimes I can retype PW 50+
times and then it will logon. but somedays NO.
any hints?
thanx
times and then it will logon. but somedays NO.
any hints?
thanx
H
h.stroph
In news:uoIHlp8BJHA.1224@TK2MSFTNGP02.phx.gbl,
txgeek <anon> typed:
> unable to logon. did not forget PW. sometimes I can retype PW 50+
> times and then it will logon. but somedays NO.
>
> any hints?
slow down with the typing
txgeek <anon> typed:
> unable to logon. did not forget PW. sometimes I can retype PW 50+
> times and then it will logon. but somedays NO.
>
> any hints?
slow down with the typing
B
Ben Myers
"txgeek" <anon> wrote in message news:uoIHlp8BJHA.1224@TK2MSFTNGP02.phx.gbl...
> unable to logon. did not forget PW. sometimes I can retype PW 50+
> times and then it will logon. but somedays NO.
> any hints?
Make sure "Caps Lock" and "Num Lock" are set correctly.
If the password is all lower case, "Caps Lock" should
be off and if it contains numbers, "Num Lock" should be on.
Ben
> unable to logon. did not forget PW. sometimes I can retype PW 50+
> times and then it will logon. but somedays NO.
> any hints?
Make sure "Caps Lock" and "Num Lock" are set correctly.
If the password is all lower case, "Caps Lock" should
be off and if it contains numbers, "Num Lock" should be on.
Ben
T
txgeek
yes, of course. both the obvious are not the problem.
are there known hiccups in 2000 that might cause this?
thanx
Ben Myers wrote:
> "txgeek" <anon> wrote in message news:uoIHlp8BJHA.1224@TK2MSFTNGP02.phx.gbl...
>
>>unable to logon. did not forget PW. sometimes I can retype PW 50+
>>times and then it will logon. but somedays NO.
>>any hints?
>
>
> Make sure "Caps Lock" and "Num Lock" are set correctly.
> If the password is all lower case, "Caps Lock" should
> be off and if it contains numbers, "Num Lock" should be on.
>
> Ben
are there known hiccups in 2000 that might cause this?
thanx
Ben Myers wrote:
> "txgeek" <anon> wrote in message news:uoIHlp8BJHA.1224@TK2MSFTNGP02.phx.gbl...
>
>>unable to logon. did not forget PW. sometimes I can retype PW 50+
>>times and then it will logon. but somedays NO.
>>any hints?
>
>
> Make sure "Caps Lock" and "Num Lock" are set correctly.
> If the password is all lower case, "Caps Lock" should
> be off and if it contains numbers, "Num Lock" should be on.
>
> Ben
S
Sid Elbow
I would think that if there were "known hiccups in 2000 that would cause
this", even MS would have had to fix it by now.
Perhaps as "obvious" as the previous response, but have you tried
another keyboard? A flakey keyboard or single key is about the most
likely think I can think of. Or keyboard cable/connector.
If you use a wireless keyboard, try a wired kind and see if the problem
goes away.
txgeek wrote:
> yes, of course. both the obvious are not the problem.
>
>
> are there known hiccups in 2000 that might cause this?
>
> thanx
>
>
>
> Ben Myers wrote:
>> "txgeek" <anon> wrote in message
>> news:uoIHlp8BJHA.1224@TK2MSFTNGP02.phx.gbl...
>>
>>> unable to logon. did not forget PW. sometimes I can retype PW 50+
>>> times and then it will logon. but somedays NO.
>>> any hints?
>>
>>
>> Make sure "Caps Lock" and "Num Lock" are set correctly.
>> If the password is all lower case, "Caps Lock" should
>> be off and if it contains numbers, "Num Lock" should be on.
>>
>> Ben
this", even MS would have had to fix it by now.
Perhaps as "obvious" as the previous response, but have you tried
another keyboard? A flakey keyboard or single key is about the most
likely think I can think of. Or keyboard cable/connector.
If you use a wireless keyboard, try a wired kind and see if the problem
goes away.
txgeek wrote:
> yes, of course. both the obvious are not the problem.
>
>
> are there known hiccups in 2000 that might cause this?
>
> thanx
>
>
>
> Ben Myers wrote:
>> "txgeek" <anon> wrote in message
>> news:uoIHlp8BJHA.1224@TK2MSFTNGP02.phx.gbl...
>>
>>> unable to logon. did not forget PW. sometimes I can retype PW 50+
>>> times and then it will logon. but somedays NO.
>>> any hints?
>>
>>
>> Make sure "Caps Lock" and "Num Lock" are set correctly.
>> If the password is all lower case, "Caps Lock" should
>> be off and if it contains numbers, "Num Lock" should be on.
>>
>> Ben
T
txgeek
your confidence in MS is misplaced, ere there would be no need for
these noozgroops.
thx for 0.
have a great holiday wknd.
Sid Elbow wrote:
> I would think that if there were "known hiccups in 2000 that would cause
> this", even MS would have had to fix it by now.
>
> Perhaps as "obvious" as the previous response, but have you tried
> another keyboard? A flakey keyboard or single key is about the most
> likely think I can think of. Or keyboard cable/connector.
>
> If you use a wireless keyboard, try a wired kind and see if the problem
> goes away.
>
>
>
>
> txgeek wrote:
>
>> yes, of course. both the obvious are not the problem.
>>
>>
>> are there known hiccups in 2000 that might cause this?
>>
>> thanx
>>
>>
>>
>> Ben Myers wrote:
>>
>>> "txgeek" <anon> wrote in message
>>> news:uoIHlp8BJHA.1224@TK2MSFTNGP02.phx.gbl...
>>>
>>>> unable to logon. did not forget PW. sometimes I can retype PW 50+
>>>> times and then it will logon. but somedays NO.
>>>> any hints?
>>>
>>>
>>>
>>> Make sure "Caps Lock" and "Num Lock" are set correctly.
>>> If the password is all lower case, "Caps Lock" should
>>> be off and if it contains numbers, "Num Lock" should be on.
>>>
>>> Ben
these noozgroops.
thx for 0.
have a great holiday wknd.
Sid Elbow wrote:
> I would think that if there were "known hiccups in 2000 that would cause
> this", even MS would have had to fix it by now.
>
> Perhaps as "obvious" as the previous response, but have you tried
> another keyboard? A flakey keyboard or single key is about the most
> likely think I can think of. Or keyboard cable/connector.
>
> If you use a wireless keyboard, try a wired kind and see if the problem
> goes away.
>
>
>
>
> txgeek wrote:
>
>> yes, of course. both the obvious are not the problem.
>>
>>
>> are there known hiccups in 2000 that might cause this?
>>
>> thanx
>>
>>
>>
>> Ben Myers wrote:
>>
>>> "txgeek" <anon> wrote in message
>>> news:uoIHlp8BJHA.1224@TK2MSFTNGP02.phx.gbl...
>>>
>>>> unable to logon. did not forget PW. sometimes I can retype PW 50+
>>>> times and then it will logon. but somedays NO.
>>>> any hints?
>>>
>>>
>>>
>>> Make sure "Caps Lock" and "Num Lock" are set correctly.
>>> If the password is all lower case, "Caps Lock" should
>>> be off and if it contains numbers, "Num Lock" should be on.
>>>
>>> Ben
P
Pegasus \(MVP\)
Sid gave you a few common sense suggestions. I think you should try them,
then acknowledge Sid's reply with something other than your terse note
below. Furthermore, the odds of your problem being caused by a bug are
overwhelmingly against you. Win2000 is installed on several million machines
and we would have heard about this "bug" a long time ago if it existed. This
is one of the benefits of newsgroups: When there is something wrong with an
OS or with an application then word gets around very, very quickly.
Now let's try a different keyboard, preferably on a different input port
(USB if you're currently using PS/2, or vice versa).
"txgeek" <anon> wrote in message
news:OPLlcveCJHA.2480@TK2MSFTNGP02.phx.gbl...
> your confidence in MS is misplaced, ere there would be no need for these
> noozgroops.
>
> thx for 0.
>
> have a great holiday wknd.
then acknowledge Sid's reply with something other than your terse note
below. Furthermore, the odds of your problem being caused by a bug are
overwhelmingly against you. Win2000 is installed on several million machines
and we would have heard about this "bug" a long time ago if it existed. This
is one of the benefits of newsgroups: When there is something wrong with an
OS or with an application then word gets around very, very quickly.
Now let's try a different keyboard, preferably on a different input port
(USB if you're currently using PS/2, or vice versa).
"txgeek" <anon> wrote in message
news:OPLlcveCJHA.2480@TK2MSFTNGP02.phx.gbl...
> your confidence in MS is misplaced, ere there would be no need for these
> noozgroops.
>
> thx for 0.
>
> have a great holiday wknd.
S
Sid Elbow
txgeek wrote:
> your confidence in MS is misplaced, ere there would be no need for these
> noozgroops.
Not confidence really ... just that if your problem were the least bit
common there would have been multiple reports here (and other places)
and, given the nature of it's severity and impact, MS could hardly have
ignored it (as they have done for some minor bugs).
> thx for 0.
Nice. I assume that means you had previously eliminated the keyboard and
associated hardware as the source of the problem (or you otherwise know
"off the top of your head" that it's not the source). Pity you didn't
say so when you initially stated the problem. It would have saved me,
and others, spending the time trying to find an answer to the problem
that *you asked* for assistance on.
> have a great holiday wknd.
Oh I intend to. Perhaps you should get out and relax too. You obviously
can't spend much time at the computer
> your confidence in MS is misplaced, ere there would be no need for these
> noozgroops.
Not confidence really ... just that if your problem were the least bit
common there would have been multiple reports here (and other places)
and, given the nature of it's severity and impact, MS could hardly have
ignored it (as they have done for some minor bugs).
> thx for 0.
Nice. I assume that means you had previously eliminated the keyboard and
associated hardware as the source of the problem (or you otherwise know
"off the top of your head" that it's not the source). Pity you didn't
say so when you initially stated the problem. It would have saved me,
and others, spending the time trying to find an answer to the problem
that *you asked* for assistance on.
> have a great holiday wknd.
Oh I intend to. Perhaps you should get out and relax too. You obviously
can't spend much time at the computer
J
John John (MVP)
Imagine, a "bug" that prevents users from loging on (read "using") the
operating system and no one has ever heard about it! This wouldn't be
an obscure bug encountered by someone who uses a scarcely known function
hidden deep inside the operating system, this would be a bug at the very
first step necessary for using the operating system, something that
every one needs to do whenever they start Windows 2000, something that
has been done on a daily basis since 1999, something done by hundreds of
millions of users billions of times... and you have discovered a Windows
2000 logon "hiccup"... Possible? Yes, but not plausible, it is highly
unlikely that there is a logon bug.
John
txgeek wrote:
> your confidence in MS is misplaced, ere there would be no need for these
> noozgroops.
>
> thx for 0.
>
> have a great holiday wknd.
>
> Sid Elbow wrote:
>
>> I would think that if there were "known hiccups in 2000 that would
>> cause this", even MS would have had to fix it by now.
>>
>> Perhaps as "obvious" as the previous response, but have you tried
>> another keyboard? A flakey keyboard or single key is about the most
>> likely think I can think of. Or keyboard cable/connector.
>>
>> If you use a wireless keyboard, try a wired kind and see if the
>> problem goes away.
>>
>>
>>
>>
>> txgeek wrote:
>>
>>> yes, of course. both the obvious are not the problem.
>>>
>>>
>>> are there known hiccups in 2000 that might cause this?
>>>
>>> thanx
>>>
>>>
>>>
>>> Ben Myers wrote:
>>>
>>>> "txgeek" <anon> wrote in message
>>>> news:uoIHlp8BJHA.1224@TK2MSFTNGP02.phx.gbl...
>>>>
>>>>> unable to logon. did not forget PW. sometimes I can retype PW 50+
>>>>> times and then it will logon. but somedays NO.
>>>>> any hints?
>>>>
>>>>
>>>>
>>>>
>>>> Make sure "Caps Lock" and "Num Lock" are set correctly.
>>>> If the password is all lower case, "Caps Lock" should
>>>> be off and if it contains numbers, "Num Lock" should be on.
>>>>
>>>> Ben
operating system and no one has ever heard about it! This wouldn't be
an obscure bug encountered by someone who uses a scarcely known function
hidden deep inside the operating system, this would be a bug at the very
first step necessary for using the operating system, something that
every one needs to do whenever they start Windows 2000, something that
has been done on a daily basis since 1999, something done by hundreds of
millions of users billions of times... and you have discovered a Windows
2000 logon "hiccup"... Possible? Yes, but not plausible, it is highly
unlikely that there is a logon bug.
John
txgeek wrote:
> your confidence in MS is misplaced, ere there would be no need for these
> noozgroops.
>
> thx for 0.
>
> have a great holiday wknd.
>
> Sid Elbow wrote:
>
>> I would think that if there were "known hiccups in 2000 that would
>> cause this", even MS would have had to fix it by now.
>>
>> Perhaps as "obvious" as the previous response, but have you tried
>> another keyboard? A flakey keyboard or single key is about the most
>> likely think I can think of. Or keyboard cable/connector.
>>
>> If you use a wireless keyboard, try a wired kind and see if the
>> problem goes away.
>>
>>
>>
>>
>> txgeek wrote:
>>
>>> yes, of course. both the obvious are not the problem.
>>>
>>>
>>> are there known hiccups in 2000 that might cause this?
>>>
>>> thanx
>>>
>>>
>>>
>>> Ben Myers wrote:
>>>
>>>> "txgeek" <anon> wrote in message
>>>> news:uoIHlp8BJHA.1224@TK2MSFTNGP02.phx.gbl...
>>>>
>>>>> unable to logon. did not forget PW. sometimes I can retype PW 50+
>>>>> times and then it will logon. but somedays NO.
>>>>> any hints?
>>>>
>>>>
>>>>
>>>>
>>>> Make sure "Caps Lock" and "Num Lock" are set correctly.
>>>> If the password is all lower case, "Caps Lock" should
>>>> be off and if it contains numbers, "Num Lock" should be on.
>>>>
>>>> Ben
T
txgeek
terse notes are verboten? OK, I will get longwinded.
It was the "slow down typing" that pissed me off.
I am sorry I didn't elaborate all the common sense things I tried.
yes, KB changeout. retry PWs in CAPS, etc.
the PWs are good, since they will finally 'take' after how many
retries. Just a real pain in the butt. and no other artifacts of
corruption anywhere else in the system.
there are 3 PWs, all admin, and all 3 exhibit this quirk.
????
thx
Pegasus (MVP) wrote:
> Sid gave you a few common sense suggestions. I think you should try them,
> then acknowledge Sid's reply with something other than your terse note
> below. Furthermore, the odds of your problem being caused by a bug are
> overwhelmingly against you. Win2000 is installed on several million machines
> and we would have heard about this "bug" a long time ago if it existed. This
> is one of the benefits of newsgroups: When there is something wrong with an
> OS or with an application then word gets around very, very quickly.
>
> Now let's try a different keyboard, preferably on a different input port
> (USB if you're currently using PS/2, or vice versa).
>
> "txgeek" <anon> wrote in message
> news:OPLlcveCJHA.2480@TK2MSFTNGP02.phx.gbl...
>
>>your confidence in MS is misplaced, ere there would be no need for these
>>noozgroops.
>>
>>thx for 0.
>>
>>have a great holiday wknd.
>
>
>
It was the "slow down typing" that pissed me off.
I am sorry I didn't elaborate all the common sense things I tried.
yes, KB changeout. retry PWs in CAPS, etc.
the PWs are good, since they will finally 'take' after how many
retries. Just a real pain in the butt. and no other artifacts of
corruption anywhere else in the system.
there are 3 PWs, all admin, and all 3 exhibit this quirk.
????
thx
Pegasus (MVP) wrote:
> Sid gave you a few common sense suggestions. I think you should try them,
> then acknowledge Sid's reply with something other than your terse note
> below. Furthermore, the odds of your problem being caused by a bug are
> overwhelmingly against you. Win2000 is installed on several million machines
> and we would have heard about this "bug" a long time ago if it existed. This
> is one of the benefits of newsgroups: When there is something wrong with an
> OS or with an application then word gets around very, very quickly.
>
> Now let's try a different keyboard, preferably on a different input port
> (USB if you're currently using PS/2, or vice versa).
>
> "txgeek" <anon> wrote in message
> news:OPLlcveCJHA.2480@TK2MSFTNGP02.phx.gbl...
>
>>your confidence in MS is misplaced, ere there would be no need for these
>>noozgroops.
>>
>>thx for 0.
>>
>>have a great holiday wknd.
>
>
>
P
Pegasus \(MVP\)
"txgeek" <anon> wrote in message
news:O3dhUOhCJHA.5196@TK2MSFTNGP04.phx.gbl...
> terse notes are verboten?
There is nothing wrong with terse notes. However, when a total stranger
makes an effort to write three paragraphs with helpful hints in response to
your request for help then it is IMHO rude to reply "thx for 0". A phrase
such as "Thank you but sorry, it made no difference" would have been far
more appropriate.
news:O3dhUOhCJHA.5196@TK2MSFTNGP04.phx.gbl...
> terse notes are verboten?
There is nothing wrong with terse notes. However, when a total stranger
makes an effort to write three paragraphs with helpful hints in response to
your request for help then it is IMHO rude to reply "thx for 0". A phrase
such as "Thank you but sorry, it made no difference" would have been far
more appropriate.