Microprocessors

1,000 bytes = 100 kilo bytes = 1 mega byte. So 510 kilo bytes is 5.1 megabytes.

matrix

There should be some process to stop the execution of a program.In microcontroller it is done by jumping to same location.

The operating frequency of 8085 is 3 mhz to 5 mhz

A Hz is a measure of cycles per second. 25 MHz is 25,000,000 Hz. So divide 1 second by 25,000,000 to find the length of a clock cycle. 1/25000000 = 4.0e-8 seconds / cycle

the FSB or Front Side Buss is the same on multi core [ dual ] ,[three] , or [quad] the speed can be higher or lower and it [ over the years ] has gone from 8 bits wide to now 64 bits wide , each bit would be like a lane on a highway ..... 8 lanes can take so much traffic but 16, 32, 64 increases the amount of data that can be moved at one time increasing efficiency and computing power dramatically . Intel uses a process that makes the FSB {data buss} think its running 4x faster than it really is making for a really fast way to move data around the computer

stepper motor

No. it is not a stepper. It is a Brushless DC (BLDC) motor. See related link for more information on this motor.

It will run, but very poorly. I recommend not using Windows 98. Windows 98 is very unsecured, incompatible, and very unreliable in todays computers.

The Ubuntu/Kubuntu kernel is configured to support 8 processors / cores in 32-bit and 64 processors / cores in 64-bit.

They are used on laptops just not anymore. On older laptops Pentium 4 and AMD FX processors where not used not because of size, because they could not develop a cost safe cooling system (a fan that spins fast enough) to keep the processors cool enough during peak performace. They started to use these when the technoligy was developed (out there) and fairly praced but was hardly used because core duo came out soon after and was expected to come even sooner therefor they stoped working with the single processors and starting using the cooling tech for duo but theres still alot with outhere with those processors just no longer manufactured.

It depends how many cores it has, according to the system requirements you need:
P4 3.2 GHz (single core) or any Dual Core processor

so if it has more than one core, you should be okay.

Absolutely not. Not only are you talking about something that's the physical size of a couple plant cells, you're talking about something hard-burnt deep in the depths of a processor's die. It cant' be accessed without destroying the chip unless you can work on the nano-scale. The L1 cache is small because it is expensive, increasing its size would slow it down, and increasing its size has very little effective change on the performance of the CPU.

0.2857 nano Seconds

As time goes onward, programs become...larger, and require more memory. 32-bit operating systems and processors are limited to a 4 GB address space, and only about 3 GB of this will typically be usable. Using 64-bit processors and operating systems will lift the 4 GB barrier and allow an astronomical amount of RAM to be usable. 64-bit operating systems and processors are readily available (if your computer is less than 4 years old, you very likely have a 64-bit processor already), and as memory manufacturing techniques improve, it will actually become more expensive to produce modules less than 4 GB in size.

Whether or not you currently need 4 GB or more of RAM is largely irrelevant; sooner or later, you will want to use a program that requires a larger amount of RAM, and even if that program uses less than 4 GB of RAM, more RAM will be needed to multitask effectively. Just as 64 MB of RAM is not enough to productively run most office software, even if that's all the program uses, one day 3 GB will not be enough.

All games do. It's not the game that decides how many cores it uses, it's the computer itself. The computer splits the workload up into two parts and then the two cores tackle one part each.
With a quad-core, there was (maybe still has) issues because the computer didn't split the processes properly. I think it's been ironed out by now though.

OS (Operating System): Which will be Windows 7 this is on almost every "new" computer on the market starting at very low prices.

Processors: (The 2nd Generation Intel I series)

I3 - Laptop Ranging from around £300 - £500

I5 - Laptop Ranging from around £400 - £800

I7 - Laptop Ranging from around £700 - £1200

Laptop Graphics Cards (NVidia GT/X m Ge Force Mobile series)

Laptop price when it comes to Graphics card depends on the other hardware inside. For example RAM and HDD space and transfer rates.

A Laptop with NVidia 240m could be £1200 as it has alot of HDD space and other good hardware

and a Laptop with NVidia 555m (Better than 240m) could be £700.00 because it has smaller HDD space and other hardware

Always go for good cheap brands. I tend to go with ASUS when it comes to Laptops.

I currently have the ASUS N55SF S2342V. It was at an amazing price with good hardware and not one problem yet.

To find out the time interval between two consecutive events using the 8086, or any other processor or programming language for that matter, you observe some time reference when you see the two events, and you subtract the time references from each other to calculate elapsed time.

Unfortunately, the 8086 does not have an interval timer, so you either have to program one using some kind of periodic clock, or you have to measure time using a hard coded loop.

Method One: Interrupts for both

The periodic clock, for instance running at 1 kHz, generates a 1 mS interrupt. In the interrupt service routine, you increment a variable that represents time in mS. The monitored event also generates an interrupt. On the first interrupt, you note the interval time so far. On the second interrupt, you note and compute the time difference. In this example, you have a resolution of 1 mS.

If you were to use an original IBM PC, you would have a clock interrupt available with a frequency of 55 Hz, giving you a resolution of about 18.2 mS.

Method Two: Interrupts for one

The periodic clock runs as an interrupt, as described before. In a loop, you monitor the event, noting the interval time between susequent events, and calculate the time difference. The loop consumes all CPU time while running, which might be a problem.

Method Three: External clock

You have an external counter, perhaps running at 1 mHz. Either hard coded or in an interrupt service routine, you monitor the event, read the clock twice, and calculate the time. In this example, you have a resolution of 1 uS.

Method Four: Brute force

You have a loop that counts iterations in some variable, noting how many iterations there are between events.

While this method requires the least amount of hardware, it is the poorest method, both from the standpoint of overall system threading, and from the standpoint of accuracy.

The loop consumes all processing time. You cannot do anything else during that time, otherwise the results will be wrong. If you are designing a system with multiple processes and threads, this will not work.

The loop also does not have an easily predictable period. Memory latency, cache hit/miss ratio, and other ongoing interrupts will disturb the results. In a single threaded system, and that includes whatever operating system you use, it can work, and it can have repeatable results - and you will need to spend some time calibrating it.

The Pentium II was first released on May 7, 1997.

CPU

main memory

The 32-bit Ubuntu desktop kernel is set to 8 cores. The rest are at 64 cores.

MHz

peripheral

yes..there is a cache which is present in the processor.

overclock the computer, ensure there is more than enough ram and that the GPU is more than suitable. Basically ensure that all the other components can support the CPU.