|
| My Izzi Pro claims in the System control panel app that it has an MIPS 3000 CPU. However, when I installed some Plus apps from Microsoft, I could only install the cab files marked 4000, not 3000. What's the deal? | |
| |
Administrator H/PC Oracle Posts: | 17,990 |
Location: | United Kingdom | Status: | |
| MIPS code is usually backwards compatible between the 3000, 4000, 4100 and 4200. It's nothing to worry about.
A specific build for 3000 just provided certain optimisations on the mips cpu archetecture | |
| |
| But the strange thing is that the 3000 build doesn't want to be installed. If I double-click on a cab file with the r3000 suffix, I get "the application cannot run on this device type." The r4100 files install fine, though.
Besides, to me "backward compatibility" means that 3000 code will run on 4000, not vice versa -- unless the 3000 is newer than the 4000. | |
| |
Administrator H/PC Oracle Posts: | 17,990 |
Location: | United Kingdom | Status: | |
| Ah I follow you now.
MIPS 3900 CPU's will actually go for the 4000 cab as a matter of course. When ActiveSync detects the CPU it automatically routes the 4000 cab up to the device. | |
| |
| A document on the Toshiba site calls this "R3000A upward compatible instruction set". I guess it's this "upward compatibility" that makes it be detected as an R4000 CPU. I don't really know what this means, but I guess that some R4000 features were added to the R3000 core. | |
| |
Administrator H/PC Oracle Posts: | 17,990 |
Location: | United Kingdom | Status: | |
| I imagine its just implying that the base spec for code instruction is 3000A. Just like that of the x86-32 core is 386DX / 486DX. | |
|
Seconds to generate: 0.125 - Cached queries : 63 - Executed queries : 9
| | |
|