[SOLVED] Can I run docker and windows 64 OS on Pentium 4 511 proccesor?

[arttss]

I have old single core Pentium 4 511 processor yet, on Windows 7 in recent years, indeed it was frequently overheated above 70 grades. https://ark.intel.com/content/www/u...essor-511-1m-cache-2-80a-ghz-533-mhz-fsb.html I have read user reviews and ones say it supports 64-OS, the others - does not work with it. Indeed this official specification shows processor support Intel 64, and 64-bit instruction set. I want to know what it means exactly - what is peculiarities of 64-bit Windows OS installation and work on this generally 32-bit processor? And the next question is whether I can use docker on this processor in 64-bit Windows OS (7,8)? If not how to resolve this inconsistency in Windows OS? And can I use Docker with Linux-64 OS on this processor and how smoothly it could work?

 

[kanewolf]

I have old single core Pentium 4 511 processor yet, on Windows 7 in recent years, indeed it was frequently overheated above 70 grades. https://ark.intel.com/content/www/u...essor-511-1m-cache-2-80a-ghz-533-mhz-fsb.html I have read user reviews and ones say it supports 64-OS, the others - does not work with it. Indeed this official specification shows processor support Intel 64, and 64-bit instruction set. I want to know what it means exactly - what is peculiarities of 64-bit Windows OS installation and work on this generally 32-bit processor? And the next question is whether I can use docker on this processor in 64-bit Windows OS (7,8)? If not how to resolve this inconsistency in Windows OS? And can I use Docker with Linux-64 OS on this processor and how smoothly it could work?

I think the answer on Docker is NO. Your Intel ARK page shows that the 511 doesn't support VX-t. This Docker support page -- https://docs.docker.com/desktop/windows/install/ says that SLAT is required -- https://en.wikipedia.org/wiki/Second_Level_Address_Translation That page says that SLAT was introduced in Nehalem architecture -- https://en.wikipedia.org/wiki/Nehalem_(microarchitecture) Which was introduced in 2008. The Intel ARK says your processor is a Prescott -- https://en.wikipedia.org/wiki/Pentium_4#Prescott Which is 4 years TOO old.

 

[Mr.Spock]

in 64-bit Windows maybe not, the benefit is address space of 4GB+

however 64-bit Linux will run on Prescott so Docker should run ok, it runs even on mobile J-series Celerons (used in NAS boxes), the caveat would be the RAM capacity of the motherboard as you may be dependent on disk for virtual memory.

I have old single core Pentium 4 511 processor yet, on Windows 7 in recent years, indeed it was frequently overheated above 70 grades. https://ark.intel.com/content/www/u...essor-511-1m-cache-2-80a-ghz-533-mhz-fsb.html I have read user reviews and ones say it supports 64-OS, the others - does not work with it. Indeed this official specification shows processor support Intel 64, and 64-bit instruction set. I want to know what it means exactly - what is peculiarities of 64-bit Windows OS installation and work on this generally 32-bit processor? And the next question is whether I can use docker on this processor in 64-bit Windows OS (7,8)? If not how to resolve this inconsistency in Windows OS? And can I use Docker with Linux-64 OS on this processor and how smoothly it could work?

 

[arttss]

I have seen that vt-x virtualuzation is absent here. There is no virtualization option in bios. Indeed for 15 years, I used VirtualBox and Parralels long time ago with Ubuntu, Fedora, and another Windows on my old Windows XP that is farther installed in initial physical disk I do not use now. Can I use some additional soft to enable docker in Windows without virtualization support? Anyway I need third hard disk as two are full for another 64-bit OS. I can even buy cheap old Pentium4 D with virtualization support probably but I do not want change processor as cooler fastening to main board is always issue. Moreover 2.85v instead of 3.3v I recently see on Asus Probe MB utility app. But as Linux Docker could work on this processor should it mean that it supports Linux Virtualization or virtualuzation is built inside this OS?

 

[arttss]

The another nuance is how Windows 64-bit OS can work for itself on this 32-bit processor? Indeed it has 64-bit architecture. I checked in cmd prompt with special command. I even found special architechture property (like enum) in some .Net class - that show that value 9 -means 64-bit. But it seems it works by 32-bit bus. That is also inherent property of this proc. So what would be difference in work of Windows 64-bit OS on this 32-bit bus proc, in comparison with 64-bit bus processor such like as almost all later pentium 64-bit processors? Just use 64-bit OS for more operative memory is not justified as I use 2 gb with 4 memory sticks, and if would use 4 one gb ddr1 memory planks - it just can be doubled to 4gb, not more. Here 64-bit OS would not allow to overcame 4gb limitation in practice, as there is no larger than 1gb ddr1 stick. Indeed if 32-bit OS even lessen 4gb to 3gb practically, maybe even full 4gb could be some rationale.

 

[Karadjgne]

x86 OS had a 3.5Gb limitation, so ram usage was done in specific ways and used programs that did not use high amounts of ram. x64 OS don't have those ram limits, so use ram as needed. What you'll find is that having an x86, 32bit motherboard with its physical ram limits, and then using an x64 OS without ram limits means you'll be constantly running into ram issues. Win10 basically soaks up @ 1.5Gb ± of ram by itself, so any further apps will be limited by the amount of physical ram your board can deal with. Meaning if you only have 4Gb of ram, by the time you get to 3Gb+ of usage, Windows will start using pagefile.sys to alleviate any perceived or potential system shortages or blockages.

Which will put any potential gains of using a x64 OS in the toilet and severely slowing down processing ability, on an already slow cpu.