Hacker News new | ask | show | jobs
by exitcode00 2677 days ago
Wow, I checked but apparently the Pi 3 DOES meet the Windows 10 system requirements just barely. I wonder how fast the UI and Cortana run...

Win 10 Specs: Processor: 1 gigahertz (GHz) or faster processor or SoC. RAM: 1 gigabyte (GB) for 32-bit or 2 GB for 64-bit. Hard disk space: 16 GB for 32-bit OS 20 GB for 64-bit OS. Graphics card: DirectX 9 or later with WDDM 1.0 driver. Display: 800x600

Ras Pi 3: CPU: 4× ARM Cortex-A53, 1.2GHz. GPU: Broadcom VideoCore IV. RAM: 1GB LPDDR2 (900 MHz) Networking: 10/100 Ethernet, 2.4GHz 802.11n wireless. Bluetooth: Bluetooth 4.1 Classic, Bluetooth Low Energy. Storage: microSD.

5 comments

> Ras Pi 3: CPU: 4× ARM Cortex-A53, 1.2GHz. GPU: Broadcom VideoCore IV. RAM: 1GB LPDDR2 (900 MHz) Networking: 10/100 Ethernet, 2.4GHz 802.11n wireless. Bluetooth: Bluetooth 4.1 Classic, Bluetooth Low Energy. Storage: microSD.

That's Model B, the Model B+ specs are a little bit better. But still only 1GB of RAM which I suspect to be the biggest bottleneck here. Storage also maybe but the Pi can boot from USB nowadays which might bring it to a good enough level.

My first thought is that you might be able to boot Win10 with 1GB of RAM, but there won't be much of anything left for your applications. Swapping is on the slow CPU hungry SD card too. It's not going to be fun.
Windows 10 does have memory compression, so maybe that helps in low memory situations like this?
I have some HP Stream 7 tablets. 1GB RAM, shipped with a full Windows tablet/desktop setup. Windows 10 runs better than Windows 8 did.

Comparable to a Raspberry Pi 3, I believe.

broadcom wrote directx drivers ??
I wonder if this could be done with LTSB? It's definitely better-suited to applications such as rpi (embedded etc.).
I wonder if the server version would work better since it can be run without a GUI.
Windows Server doesn't support ARM, neither does Windows IoT Enterprise. The Nano Server install is strictly for virtualized use.

https://docs.microsoft.com/en-us/windows-server/get-started/...

https://docs.microsoft.com/en-us/windows-server/get-started/...

Windows 10 IoT Core has been an option for Raspberry Pi for a while. It's a mostly headless (just the bare amount of UWP GUI support, no Win32), desktop-less SKU intended for embedded installs.
I couldn't think of anything more horrible than running Windows without a GUI. Why not use Linux at that point?
It's the same concept. For linux you'd use SSH which gets you to a shell for remote administration, for Windows you use powershell via the Enter-PSSession command.
I wondered the same thing, I would expect performance to be not great
1 GHz on x86 != 1 GHz on ARM
If it allows Atoms, then most arm processors should be acceptable.
The IPC and architecture is obviously very important.
Even 1Ghz on one x86 != 1Ghz on a different x86 CPU.
And of course on a different ARM CPU.

Cortex-A53 is an ultra low power, tiny core. It's okay for an embedded toy, it's miserable for a real computer. You really really want at least a Cortex-A72.

Interesting -- can you elaborate a bit more?