No Such Interface Supported
 

On 2/27/19 4:23 PM, J. P. Gilliver (John) wrote:
Yes: when this problem manifests itself, I've found plugging in a USB
keyboard makes no difference - or even using the on-screen keyboard!
What's more, the problem/behaviour seems to have come across from my
WindowsÂ*XPÂ*machine!!

Was the old keyboard unplugged when you tested?

No Such Interface Supported
 

In message , T writes:
On 2/27/19 4:23 PM, J. P. Gilliver (John) wrote:
Yes: when this problem manifests itself, I've found plugging in a USB
keyboard makes no difference - or even using the on-screen keyboard!
What's more, the problem/behaviour seems to have come across from my
Windows*XP*machine!!

Was the old keyboard unplugged when you tested?

Both machines were/are laptops! (Well, the XP was a netbook.)
[]
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Never. For me, there has to be a meaning. There's not much meaning in eating
bugs. - Darcey Bussell (on whether she'd appear on /I'm a Celebrity/), in RT
2015/11/28-12/4

No Such Interface Supported
 

On 3/1/19 11:29 AM, J. P. Gilliver (John) wrote:
In message , T writes:
On 2/27/19 4:23 PM, J. P. Gilliver (John) wrote:
Yes: when this problem manifests itself, I've found plugging in a USB
keyboard makes no difference - or even using the on-screen keyboard!
What's more, the problem/behaviour seems to have come across from my
WindowsÂ*XPÂ*machine!!

Was the old keyboard unplugged when you tested?

Both machines were/are laptops! (Well, the XP was a netbook.)
[]

Try with a Live USB/CD/DVD. That will isolate software from hardware

https://spins.fedoraproject.org/xfce/

It can be cut with dd to a flash drive

No Such Interface Supported
 

In message , T writes:
On 3/1/19 11:29 AM, J. P. Gilliver (John) wrote:
In message , T writes:
On 2/27/19 4:23 PM, J. P. Gilliver (John) wrote:
Yes: when this problem manifests itself, I've found plugging in a
USB keyboard makes no difference - or even using the on-screen
keyboard! What's more, the problem/behaviour seems to have come
across from my Windows*XP*machine!!

Was the old keyboard unplugged when you tested?

Both machines were/are laptops! (Well, the XP was a netbook.)
[]

Try with a Live USB/CD/DVD. That will isolate software from hardware

https://spins.fedoraproject.org/xfce/

It can be cut with dd to a flash drive

I'm pretty sure it's not hardware - I can't think how _any_ hardware
fault would still manifest itself when I try to use the on-screen
"keyboard" (that you operate with the mouse).

Trying a Linux bootable wouldn't I don't think work - my problem only, I
think, manifests itself when I've been using the combination of Windows
softwares I normally use, for a while. And I think it's something I do
that triggers it - _something_ I think related to use of the Ctrl key,
but I'm not completely sure of that, and certainly don't know what. And
I don't know what makes it clear itself either, but again I think it's
an action or combination of actions I take.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Science fiction is escape into reality - Arthur C Clarke

No Such Interface Supported
 

On 3/1/19 3:15 PM, J. P. Gilliver (John) wrote:

I'm pretty sure it's not hardware - I can't think how _any_ hardware
fault would still manifest itself when I try to use the on-screen
"keyboard" (that you operate with the mouse).

Neither can I, but..

Trying a Linux bootable wouldn't I don't think work - my problem only, I
think, manifests itself when I've been using the combination of Windows
softwares I normally use, for a while. And I think it's something I do
that triggers it - _something_ I think related to use of the Ctrl key,
but I'm not completely sure of that, and certainly don't know what. And
I don't know what makes it clear itself either, but again I think it's
an action or combination of actions I take.

I would check anyway. I live for a cause effect problem. Most
of what I get called for has A affecting B affecting A. It
can take some multilevel thinking. The easy ones they fix
themselves. The hard ones, lets torture Todd! I can't help
it, I enjoy the puzzles. Its a living.

The worst one I fixed was A affecting B affecting C affecting D
affecting E affecting A. It took me two hours but I finally
conquered. They problem with these multilevel problems is
that I keep forgetting who did what to whom

If the Live USB shows it was software and you already knew
that, then you have a cool troubleshoot tool for use the
next time. I carry about eight of them for various things
around with me, alone with two Windows 10 PE flash drives.
Yes, some are labeled Window Nein.

No Such Interface Supported
 

In message , T writes:
On 3/1/19 3:15 PM, J. P. Gilliver (John) wrote:

I'm pretty sure it's not hardware - I can't think how _any_ hardware
fault would still manifest itself when I try to use the on-screen
"keyboard" (that you operate with the mouse).

Neither can I, but..

Trying a Linux bootable wouldn't I don't think work - my problem
[]
I would check anyway. I live for a cause effect problem. Most
of what I get called for has A affecting B affecting A. It
can take some multilevel thinking. The easy ones they fix
themselves. The hard ones, lets torture Todd! I can't help
it, I enjoy the puzzles. Its a living.

The worst one I fixed was A affecting B affecting C affecting D
affecting E affecting A. It took me two hours but I finally
conquered. They problem with these multilevel problems is
that I keep forgetting who did what to whom

If the Live USB shows it was software and you already knew
that, then you have a cool troubleshoot tool for use the

Except it _wouldn't_, I think, show it was softwa at best, it would
show it isn't hardware, which I'm not convinced is the same thing. But
I'd have to be using my software combination, which would be difficult
under Linux - I think at least one of them (Turnpike) wouldn't work in
WINE. I have to be using them and actively using the keyboard for the
problem to show itself; I can (and do) leave the machine on overnight,
with my usual combination of prog.s loaded, and I don't think I've ever
come to the machine in the morning and found the problem present.

next time. I carry about eight of them for various things
around with me, alone with two Windows 10 PE flash drives.
Yes, some are labeled Window Nein.

(I have no intention of using Windows 10 either, but I don't think I'd
label anything Nein: I smiled the first two or three times I saw it, but
I think by now I'd be thoroughly fed up of having to explain int.)


--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

.... basically it's another language and unless you've studied it, it's
difficult to grasp. I know people get outraged at me saying it, but it's only
my opinion. I'm not telling people who adore Shakespeare to stop adoring it
this minute. - Jane Horrocks, in Radio Times 30 July - 5 August 2011

No Such Interface Supported
 

On 3/1/19 6:47 PM, J. P. Gilliver (John) wrote:
IfÂ*theÂ*LiveÂ*USBÂ*showsÂ*itÂ*wasÂ*softwareÂ*and *youÂ*alreadyÂ*knew
that,Â*thenÂ*youÂ*haveÂ*aÂ*coolÂ*troubleshootÂ*too lÂ*forÂ*useÂ*the

Except it _wouldn't_, I think, show it was softwa at best, it would
show it isn't hardware, which I'm not convinced is the same thing. But
I'd have to be using my software combination, which would be difficult
under Linux - I think at least one of them (Turnpike) wouldn't work in
WINE. I have to be using them and actively using the keyboard for the
problem to show itself; I can (and do) leave the machine on overnight,
with my usual combination of prog.s loaded, and I don't think I've ever
comeÂ*toÂ*theÂ*machineÂ*inÂ*theÂ*morningÂ*andÂ*fou ndÂ*theÂ*problemÂ*present.

The Live stick is removable. Just open a text editor and type away.
Wine is not installed on a Live USB anyway.

Do you have Fast Boot disabled?

Nine is still funny. :-)

No Such Interface Supported
 

On 3/1/19 6:47 PM, J. P. Gilliver (John) wrote:
In message , T writes:
On 3/1/19 3:15 PM, J. P. Gilliver (John) wrote:

I'm pretty sure it's not hardware - I can't think how _any_ hardware
fault would still manifest itself when I try to use the on-screen
"keyboard" (that you operate with the mouse).

Neither can I, but..

Trying a Linux bootable wouldn't I don't think work - my problem
[]
I would check anyway.Â* I live for a cause effect problem.Â* Most
of what I get called for has A affecting B affecting A.Â* It
can take some multilevel thinking.Â* The easy ones they fix
themselves.Â* The hard ones, lets torture Todd!Â* I can't help
it, I enjoy the puzzles.Â* Its a living.

The worst one I fixed was A affecting B affecting C affecting D
affecting E affecting A.Â* It took me two hours but I finally
conquered.Â* They problem with these multilevel problems is
that I keep forgetting who did what to whom

If the Live USB shows it was software and you already knew
that, then you have a cool troubleshoot tool for use the

Except it _wouldn't_, I think, show it was softwa at best, it would
show it isn't hardware, which I'm not convinced is the same thing. But
I'd have to be using my software combination, which would be difficult
under Linux - I think at least one of them (Turnpike) wouldn't work in
WINE. I have to be using them and actively using the keyboard for the
problem to show itself; I can (and do) leave the machine on overnight,
with my usual combination of prog.s loaded, and I don't think I've ever
come to the machine in the morning and found the problem present.

next time.Â* I carry about eight of them for various things
around with me, alone with two Windows 10 PE flash drives.
Yes, some are labeled Window Nein.

(I have no intention of using Windows 10 either, but I don't think I'd
label anything Nein: I smiled the first two or three times I saw it, but
I think by now I'd be thoroughly fed up of having to explain int.)



Hi John,

Think about your issue. Sounds like you are running it 24/7.
You can get away with that with Linux, sometimes Mac, but not
Windows.

Try this. Go into control panel, administrative setting, task
scheduler (I may have the names wrong) and set a task to
reboot your machine at 3:00 AM in the morning, every morning.

The command is

shutdown.exe /r /f /t 30

That will give you 30 seconds warning, is case yoy are pulling
an all-nighter

-T

No Such Interface Supported
 

In message , T writes:
[]
Think about your issue. Sounds like you are running it 24/7.

If by "your issue", you mean my keyboard funny, that comes and goes - as
I've said, I think it's some sequence of actions I do that triggers it
and clears it, but I haven't worked out what - whether the machine has
been running one day or several. Other than that funny, the machine
seems happy with the 24'7: I'm pretty sure I've had it do more than a
week, possibly getting on for two.

You can get away with that with Linux, sometimes Mac, but not
Windows.

I seem to.
[]
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Why doesn't DOS ever say "EXCELLENT command or filename!"

No Such Interface Supported
 

On 3/4/19 5:40 PM, J. P. Gilliver (John) wrote:
In message , T writes:
[]
Think about your issue.Â* Sounds like you are running it 24/7.

If by "your issue", you mean my keyboard funny, that comes and goes - as
I've said, I think it's some sequence of actions I do that triggers it
and clears it, but I haven't worked out what - whether the machine has
been running one day or several. Other than that funny, the machine
seems happy with the 24'7: I'm pretty sure I've had it do more than a
week, possibly getting on for two.

You can get away with that with Linux, sometimes Mac, but not
Windows.

I seem to.
[]

Hi John,

That is not what you are describing.

I see tons of Windows machines that have not been rebooted
in days having weird symptoms. What you describe it typically
one of the symptoms: keyboard acting weird.

For those that need to run 24/7, doing a reboot in the night
clears them up.

https://www.techsupportalert.com/con...-windows-7.htm

-T

No Such Interface Supported
 

On Mon, 04 Mar 2019 17:55:57 -0800, T wrote:

For those that need to run 24/7, doing a reboot in the night clears them
up.

Think about what you just wrote: "For those that need to run *24/7*,".
How does a reboot fit into that?

My computer has been running since the last neighborhood power failure, 67
days, 12 hours, 10 minutes ago.

No Such Interface Supported
 

On 3/4/19 6:38 PM, Sam Hill wrote:
On Mon, 04 Mar 2019 17:55:57 -0800, T wrote:

For those that need to run 24/7, doing a reboot in the night clears them
up.

Think about what you just wrote: "For those that need to run *24/7*,".
How does a reboot fit into that?

Who is processing something 100% of the time? You pick a stop
when nothing is expected to be happening, like when all the
remote loggers have finally gone to sleep, etc.. And just
let everyone know when the reboot will occure.


My computer has been running since the last neighborhood power failure, 67
days, 12 hours, 10 minutes ago.

A Windows machine?

That is the longest I have seen! 12 days and one customer could
not type, or send eMail, and Chrome's windows shimmered.

By change do your have hibernate/sleep set?

No Such Interface Supported
 

On Mon, 04 Mar 2019 19:11:45 -0800, T wrote:

On 3/4/19 6:38 PM, Sam Hill wrote:
On Mon, 04 Mar 2019 17:55:57 -0800, T wrote:
For those that need to run 24/7, doing a reboot in the night clears
them up.

Think about what you just wrote: "For those that need to run *24/7*,".
How does a reboot fit into that?

Who is processing something 100% of the time?

The remote server that sits waiting for world-wide salespersons to log
business transactions... Geez, think beyond the mom-n-pop people you serve
for once.

You pick a stop when
nothing is expected to be happening, like when all the remote loggers
have finally gone to sleep, etc.. And just let everyone know when the
reboot will occure.

What if the loggers are in Denver, Dubai, and Dingzhou?

My computer has been running since the last neighborhood power failure,
67 days, 12 hours, 10 minutes ago.

A Windows machine?

No. (Now you're going to complain that 'this is a Windows group' - just
know I was picking on your silly comment about what "24/7" is.)

That is the longest I have seen! 12 days and one customer could not
type, or send eMail, and Chrome's windows shimmered.

"A Windows machine?" g

Maybe it's okay in your little world that not being able to run more than
a few days is sufficient.

By change do your have hibernate/sleep set?

No Such Interface Supported
 

On 03/04/2019 9:11 PM, T wrote:
On 3/4/19 6:38 PM, Sam Hill wrote:
On Mon, 04 Mar 2019 17:55:57 -0800, T wrote:

For those that need to run 24/7, doing a reboot in the night clears them
up.

Think about what you just wrote:Â* "For those that need to run *24/7*,".
How does a reboot fit into that?

Who is processing something 100% of the time?Â* You pick a stop
when nothing is expected to be happening, like when all the
remote loggers have finally gone to sleep, etc..Â* And just
let everyone know when the reboot will occure.


My computer has been running since the last neighborhood power
failure, 67
days, 12 hours, 10 minutes ago.

A Windows machine?

That is the longest I have seen!Â*Â* 12 days and one customer could
not type, or send eMail, and Chrome's windows shimmered.

By change do your have hibernate/sleep set?





Baloney Todd, Last place I worked before I retired I had 2 windows
machines running for about two and a half years 24/7/365 with no shut
downs or reboots, They ran my security and door card reader systems and
where not allowed to shut down, they were critical systems. You are
spreading FUD, and its not appreciated.


Rene

No Such Interface Supported
 

Sam Hill wrote:
On Mon, 04 Mar 2019 19:11:45 -0800, T wrote:

On 3/4/19 6:38 PM, Sam Hill wrote:
On Mon, 04 Mar 2019 17:55:57 -0800, T wrote:
For those that need to run 24/7, doing a reboot in the night clears
them up.
Think about what you just wrote: "For those that need to run *24/7*,".
How does a reboot fit into that?
Who is processing something 100% of the time?

The remote server that sits waiting for world-wide salespersons to log
business transactions... Geez, think beyond the mom-n-pop people you serve
for once.

You pick a stop when
nothing is expected to be happening, like when all the remote loggers
have finally gone to sleep, etc.. And just let everyone know when the
reboot will occure.

What if the loggers are in Denver, Dubai, and Dingzhou?

My computer has been running since the last neighborhood power failure,
67 days, 12 hours, 10 minutes ago.
A Windows machine?

No. (Now you're going to complain that 'this is a Windows group' - just
know I was picking on your silly comment about what "24/7" is.)

That is the longest I have seen! 12 days and one customer could not
type, or send eMail, and Chrome's windows shimmered.

"A Windows machine?" g

Maybe it's okay in your little world that not being able to run more than
a few days is sufficient.

By change do your have hibernate/sleep set?

You'd be running a redundant system with some sort of
fail-over, such that with a pair of machines, one could
be rebooted while the other takes over.

The only problem with schemes like that, is when they
get into a loop. One evening at work, a "pair" like that,
swapped roles every 90 seconds, affecting service, so I
had to page the on-call IT guy to put a stop to it.

Char could probably tell you how to set something like that up.

And there have been implementations like that, which are
run by idiots. My old ISP insisted on some sort of brain-dead
DNS scheme, where about 30 pairs of machines provided DNS.
And they would *reboot both machines in a pair* on the
same minute at night, knocking out DNS service to the customers
on that particular pair, for around 15 minutes. Talk about
strange designs... Why have redundancy, then reboot both machines
in the pair at the same time ? Boggles the mind.

Why not have... ten machines in parallel, and boot all
ten at the same time :-/ You know ya wanna.

My current ISP has "a single pair", for which the provisioning
is all hidden. (You cannot discover there are 30 pairs of machines
over time, by studying the DNS addresses it hands out over DHCP.)
You cannot see what goes on, inside the ISP building. I suspect
a kind of "virtualized" DNS scheme, which presents two addresses,
but has some unknown level of "proper" redundancy that we cannot
see. That setup has *never* gone down, that I could detect.

The Space Shuttle had five computers, and majority voter logic.
It ran two sets of software. It had a pair of machines on
each software set. And the fifth machine was some sort of
tie breaker. So there are people who have made reliable
solutions before, that actually work... They obviously
didn't hire any staff from my old ISP. If my old ISP
was running the Shuttle, they'd pick the landing cycle
as the time to reboot all five of them.

Paul