Can a 64-bit os run on a 32-bit machinery regardless of how slow, unsable and unresponssive it is?
when we try to run the 64-bit os it would give out 64-bit instructions to the processor and and then can't the 32b-t procesor process adjectives the 64-bit instructions in one go instead of two go's if please explain your answer i mean a few years ago when vista came out relations use to say it is mission impossibe to run vista on below 800 mhz and now i know several people who run vista ultimate on 500 mhz next to 512 mb ram it's incredibly slow but it still works then why can't a 64-bit os run on a 32-bit contraption think about it guys can't it purely work, thanks in finance.
Answers:
It's a completely different architecture. It's not newly speaking faster, it's speaking a different language.
Vista is available in 32 bit and 64 bit version. Unless I'm mistaken, 64 bit software will not even install on 32 bit hardware. It's not that it's too slow. It's that the instructions are written 64 bits in size. The 32 bit processor doesn't know what to do with them. The technology does not mesh.
The main problems are opcodes (operation codes or processor instructions), register sizes, and what registers are actually present.
All x86 programs lapse up putting data in registers (tiny blocks of remarkably temporary memory in the processor). The instructions (opcodes) needed to move background in and out and perform adjectives the necessary mathematical and logical operation on that data are given to the processor by the program that's running.
The problem is that registers are all unbelievably small, there are a very fixed number of them, and all programs need them for giving background to the processor for crunching. The largest registers in a 16-bit processor are 16 bits. That's considered the maximum 'word size' of the processor. That means that the biggest chunk of facts you can give to a 16-bit processor in a single register is 16-bits long. A 32-bit processor's maximum word size is 32 bits, but it also 16-bit registers for 16-bit words (and both can feel 8-bit words called bytes). Thus a 64-bit processor's maximum word size
is 64 bits, and it has 32 and 16-bit registers for dealing beside 32, 16, and 8-bit words.
A 64-bit program (OS or otherwise) would be feeding 64-bit words into 64-bit registers, which only a 64-bit processor will enjoy. So on a 32-bit processor you'd have a 64-bit program trying to put a piece of data that's too big for the processor to work on adjectives at once into a register that isn't even there, and that's leaving out the reality that the opcode to move a 64-bit word into a 64-bit register isn't part of a 32-bit processor's instruction set. The same is true for all numerical and logical operations performed on 64-bit information in 64-bit registers; a 32-bit processor doesn't have those instructions. It can't hold or work on 64-bit words.
A 64-bit OS would be speaking a expression the 32-bit processor doesn't understand and trying to use features it doesn't have. You can't break a 64-bit opcode into 2 separate 32-bit opcodes any; that changes the meaning. You closing stages up with 2 completely different instructions that very possible don't add up to what that single 64-bit instruction meant. Even if it could be done it would still be produce references to the 64-bit registers a 32-bit processor doesn't have.
In short, it wouldn't work at adjectives. Besides, most 64-bit OS installers check for supporting hardware before they'll let you get going installing. If they don't find a 64-bit processor they don't let you install.
No, because it was made for different machinery.
Related Questions:
Why are immense plant machinery other coloured ashen?
When I vote I hold to work beside big machinery what do you devise of?
Is it crooked for a company to do machinery looking after at an body private home next to no written contract?
Bally Manufacturing sent Intel Corporation an invoice for machinery next to a $24,800 register price?
Kill, verbs, or wreck machinery?
Answers:
It's a completely different architecture. It's not newly speaking faster, it's speaking a different language.
Vista is available in 32 bit and 64 bit version. Unless I'm mistaken, 64 bit software will not even install on 32 bit hardware. It's not that it's too slow. It's that the instructions are written 64 bits in size. The 32 bit processor doesn't know what to do with them. The technology does not mesh.
The main problems are opcodes (operation codes or processor instructions), register sizes, and what registers are actually present.
All x86 programs lapse up putting data in registers (tiny blocks of remarkably temporary memory in the processor). The instructions (opcodes) needed to move background in and out and perform adjectives the necessary mathematical and logical operation on that data are given to the processor by the program that's running.
The problem is that registers are all unbelievably small, there are a very fixed number of them, and all programs need them for giving background to the processor for crunching. The largest registers in a 16-bit processor are 16 bits. That's considered the maximum 'word size' of the processor. That means that the biggest chunk of facts you can give to a 16-bit processor in a single register is 16-bits long. A 32-bit processor's maximum word size is 32 bits, but it also 16-bit registers for 16-bit words (and both can feel 8-bit words called bytes). Thus a 64-bit processor's maximum word size
is 64 bits, and it has 32 and 16-bit registers for dealing beside 32, 16, and 8-bit words.
A 64-bit program (OS or otherwise) would be feeding 64-bit words into 64-bit registers, which only a 64-bit processor will enjoy. So on a 32-bit processor you'd have a 64-bit program trying to put a piece of data that's too big for the processor to work on adjectives at once into a register that isn't even there, and that's leaving out the reality that the opcode to move a 64-bit word into a 64-bit register isn't part of a 32-bit processor's instruction set. The same is true for all numerical and logical operations performed on 64-bit information in 64-bit registers; a 32-bit processor doesn't have those instructions. It can't hold or work on 64-bit words.
A 64-bit OS would be speaking a expression the 32-bit processor doesn't understand and trying to use features it doesn't have. You can't break a 64-bit opcode into 2 separate 32-bit opcodes any; that changes the meaning. You closing stages up with 2 completely different instructions that very possible don't add up to what that single 64-bit instruction meant. Even if it could be done it would still be produce references to the 64-bit registers a 32-bit processor doesn't have.
In short, it wouldn't work at adjectives. Besides, most 64-bit OS installers check for supporting hardware before they'll let you get going installing. If they don't find a 64-bit processor they don't let you install.
No, because it was made for different machinery.
Related Questions: