Overunity.com Archives is Temporarily on Read Mode Only!



Free Energy will change the World - Free Energy will stop Climate Change - Free Energy will give us hope
and we will not surrender until free energy will be enabled all over the world, to power planes, cars, ships and trains.
Free energy will help the poor to become independent of needing expensive fuels.
So all in all Free energy will bring far more peace to the world than any other invention has already brought to the world.
Those beautiful words were written by Stefan Hartmann/Owner/Admin at overunity.com
Unfortunately now, Stefan Hartmann is very ill and He needs our help
Stefan wanted that I have all these massive data to get it back online
even being as ill as Stefan is, he transferred all databases and folders
that without his help, this Forum Archives would have never been published here
so, please, as the Webmaster and Creator of these Archives, I am asking that you help him
by making a donation on the Paypal Button above.
You can visit us or register at my main site at:
Overunity Machines Forum



Partnered Output Coils - Free Energy

Started by EMJunkie, January 16, 2015, 12:08:38 AM

Previous topic - Next topic

0 Members and 11 Guests are viewing this topic.

seychelles

HI SAND GROPPER TINMAN AM I CORRECT TO GUESS THAT YOU ARE USING A TRIAC AS THE SWITCHING CIRCUIT FOR SHORTING THE COIL? GREAT WORK THERE OZZI OY OY..

MileHigh

Just a little off-topic comment that some may find interesting.

I have a Windows 7 computer, first-generation quad core.  For some reason just about every computer I have ever had randomly "eats keyboard characters" when I am typing.  It drives me nuts sometimes.  There is some unknown process that somehow kills characters that should be going into the keyboard buffer.  And the keyboard buffer is pretty much independent from other things going on in the computer which makes it that much harder to explain.  It seems like I have never been able to escape this problem.

Sometimes the "character eating" will remove a full word like "the" or "scope."  It all depends on how fast I can type and how long the "blackout" is.

When you read text, for the average person you read in short complete clumps of words at a time.  The problem when you read back prose that you just composed is that it's also automatically playing back in your head from memory, like a tape recorder.  That can override what you are actually reading.

What can happen is that when you proof read your own text you literally can't see your mistakes, like you are blind.  Between the "reading clumps of words at a time" and the "tape recorder playback" your brain simply fills in the missing words.  Sentences are compromised because whole words are missing but are usually still understandable.  It's a real pain in the butt.

Twice today I had to add missing words to my long posting because I simply could not see the mistakes first go round.  It's very frustrating sometimes because to an outsider you can look grammatically or logically challenged because of course they see all of the mistakes.

Having a keyboard/computer that doesn't eat characters would help.  For me it's like I have to wait about 24 hours to see some errors because I have to substantially forget exactly what I wrote so the "tape recorder playback" is shut off.   So I apologize for the strange looking sentences or other typos, sometime I literally can't see them.

MileHigh

MarkE

It could be your web browser.  Or it could be that you have a lot of open programs.  I see similar input hangs from time to time but mostly only in the web browser.

EMJunkie

Quote from: MileHigh on June 22, 2015, 10:59:29 PM
Just a little off-topic comment that some my find interesting.

I have a Windows 7 computer, first-generation quad core.  For some reason just about every computer I have ever had randomly "eats keyboard characters" when I am typing.  It drives me nuts sometimes.  There is some unknown process that somehow kills characters that should be going into the keyboard buffer.  And the keyboard buffer is pretty much independent from other things going on in the computer which makes it that much harder to explain.  It seems like I have never been able to escape this problem.

Sometimes the "character eating" will remove a full word like "the" or "scope."  It all depends on how fast I can type and how long the "blackout" is.

When you read text, for the average person you read in short complete clumps of words at a time.  The problem when you read back prose that you just composed is that it's also automatically playing back in your head from memory, like a tape recorder.  That can override what you are actually reading.

What can happen is that when you proof read your own text you literally can't see your mistakes, like you are blind.  Between the "reading clumps of words at a time" and the "tape recorder playback" your brain simply fills in the missing words.  Sentences are compromised because whole words are missing but are usually still understandable.  It's a real pain in the butt.

Twice today I had to add missing words to my long posting because I simply could not see the mistakes first go round.  It's very frustrating sometimes because to an outsider you can look grammatically or logically challenged because of course they see all of the mistakes.

Having a keyboard/computer that doesn't eat characters would help.  For me it's like I have to wait about 24 hours to see some errors because I have to substantially forget exactly what I wrote so the "tape recorder playback" is shut off.   So I apologize for the strange looking sentences or other typos, sometime I literally can't see them.

MileHigh


@MileHigh,

We all make mistakes and are often prone to missing something that we expect that we did when in-fact we didn't.

You have a serious issue, possible IRQ Conflict: http://www.webopedia.com/quick_ref/IRQnumbers.asp

Quote

This interrupt is reserved for the keyboard controller. Even on devices without a keyboard, this interrupt is exclusively for keyboard input.


Lookout for old 1970's Dot Matrix Printers, they will try to share IRQ1 - Hahaha - Possible Hardware Conflict or PEBCAK Error...

Mind you, when an error like this follows, even after replacing Hardware, and the PEBCAK Error has been eliminated then only one FINAL result must be possible.

It seems, through process of elimination, that some Computers will, for ever more, randomly "eat keyboard characters" no matter how much the PEBCAK on the other end tries to eliminate a clearly obvious error.

Many an ID10T has tried to ignore it, but this just is not dealing with the issue at hand!

   Chris Sykes
       hyiq.org

MileHigh

Ha ha, the error you have to worry about is the $B0ZO error.