How do computers *actually* work?

I understand turing machines, binary, storage, logic gates, the part that gets me is how does the system recognize different bits of code, how does it split 01010000010101010 into say 01010, 000010 and 101010?

Yes, this is known in the computer world as "words". 32-bit words on a 32-bit processor, 64-bit words for 64-bit, etc. Computers execute instructions word-by-word.

A word typically may contain instructions, memory addresses, or data. It could be representing a number, or an ASCII character, or a command to add the next two following words together. This is determined by the current "state" of what the system is doing at that moment and what it has been instructed to do next.

There are many different kinds of operations. They themselves can be combined in different ways for more complex operations, and so on and so forth.

So e.g. (and this is very simplistic), your chipset will have a queue of instructions (i.e. machine language):

In Memory location 005F01E3, add 300 to it.
In Memory location 168ED145, add 923 to it.
Is value in 005F01E3 bigger than value in 168ED145? Jump to instruction #123.

Hex code (1234567890ABCDEF) is just a shorter way of writing binary, i.e. "FF" in Hex = 1111 1111 in Binary = 255 in Decimal

Different architectures break down and execute "words" differently, there are several layers involved, binary -> groups of binary/flagging bits -> words -> instructions -> machine language -> compiler -> programming language -> user interface -> + more.

There is no "single way" computers break binary into their own functions, it depends on the architecture of the chipsets, cpus, and the way they are designed to execute functions (e.g. 486, RISC, etc).

I learned most of this in my final year in Comp.Sci degree, was a module called Advanced Computer Architecture. Was very interesting but immensely rich in material to learn. I haven't gone anywhere near scratching the surface in what I've mentioned above, and this was nearly 2 years ago so I'm a little rusty :p
 
Last edited:
Computers confuse the hell out of me. Truly alien devices that are made of the ghosts of times past.

I find it amusing that I have a much greater understanding of how a brain works, which is supposed to be infinitely more complicated, but it's the computer that has me boggled. It is my brain that cannot comprehend the computer :eek:

It's all done by the magic smoke held within the components, that's why when something burns out it stops working because the magic smoke escapes ;)

First the daddy PC and the mommy PC fall in love. Then they have a special grown up computer hug.

And thats how new PCs are born!

Lol some of the posts are hilarious:D:D:D:D. I would have thought that as being pc enthusiasts we would have in depth understanding of how computers work:p
 
For a question so open ended there is no good concise answer. You could do a degree in computer science and still want to know more.

My suggestion would be that if you want to get answers here you try and come with more specific questions for people to answer, or that you go and do some serious reading. Wikipedia might be good for starters but I think you'd quickly find yourself wanting some decent books.

The question is, which layer do you want to start looking at? Computer science is so deep a field that nobody would get anywhere if they tried to understand every part of a system all at once; they have to be viewed as layers of abstractions. At each layer you forget about the implementation of the layers above and below you and think only in terms of how they behave. If you want to go bottom up, take a look into digital electronics (try combinatorial and sequential logic, then look into functional units such as adders). From there you can get to the ideas behind the fundamentals of processor design. You could delve into a middle layer and have a look at some MIPs assembly code and perhaps try some with the PCSPIM simulator. A slightly higher level entry point that might be interesting is the Wikipedia article on call stacks: http://en.wikipedia.org/wiki/Call_stack. You're then getting to the point of wanting to look at operating system design, memory models, processor design, and more.

For the lower level layers you might be able to get away with learning through reading. Higher level stuff you really are best off learning about through doing (i.e. having a go at programming things to see that the layers fit together).

With regard to your question about displays and bits, you might find the Wikipedia article on the OSI layers informative: http://en.wikipedia.org/wiki/OSI_protocols.

Best answer so far .

On the hand , guys try explaining how a boeing 747 jumbo jet works as a system (cockpit electronics, air pressure exerted on the body, electro-mechanical systems, hydraulics, landing gear system, stress-strain on the material, propulsion technology, aircraft dynamics, vibrations, aerodynamics, manufacturing technologies involved etc);).

Now that will make computer technology look pale in comparison:cool:
 
Im pretty curious as to how computers work. I know what everything does and things like that, but how does it actually work. For example, how does the electricity completing the circuit of little bits of metal connect the hard drive which saves data in gigabytes which are just a sequence of 0 and 1s; how does that transfer to an image on the screen as each little pixel with different colours?

I know its fairly vague but im pretty curious. Its very confusing and im sure not many people know the answer.

OMG, seriously?
 
Im pretty curious as to how computers work. I know what everything does and things like that, but how does it actually work. For example, how does the electricity completing the circuit of little bits of metal connect the hard drive which saves data in gigabytes which are just a sequence of 0 and 1s; how does that transfer to an image on the screen as each little pixel with different colours?

I know its fairly vague but im pretty curious. Its very confusing and im sure not many people know the answer.

if you can't do a MEng in Computer Science, I recommend 'Structured Computer Organisation' by Tanenbaum. It's a crash course in 'modern' computing from gate level to operating systems.


Ooops, I linked to a competitor. It's available for £30 from the rainforest. ;)
 
Last edited:
some dude did.. lol
how the heck he managed it i have no idea... computers are confusing enough let alone with redstone.. lmao

a few people have harv is building one on the ocuk server when he gets back (programmable, and of different design than that guys).

also repeater blocks mean you can now make delay line memory :p.

I'm hoping to cobble together a collection of logic gates and adders to make a machine that will auto collect fuel and the requested type + quantity raw materials from the warehouse smelt/refine them and then collect them and put them back in their new place in the warehouse.
 
I've not really checked the entire thread properly but having scanned it, I've not seen any mention of the OSI model, a seriously important part.
 
Back
Top Bottom