As we’re still waiting with our new Raspberry PI 2 for Windows 10 to be released, why not run a slightly older version of Windows in the meantime? Here’s a guide to setup Windows 3.x on your Raspberry PI B2. Please note that you will need Windows 3.x for this. If you have a MSDN subscription you can download it from Microsoft. Bing or Google might be able to help you further when you do not have an MSDN subscription. Let’s get starting with getting Windows on Raspberry PI
Before starting with getting Windows on Raspberry PI, we assume you have the following hardware:
- Raspberry PI 2 model B (with cable/Wi-Fi network connection)
- Micro SD card (big enough to run Raspbian)
Also you have installed on your PC:
And you have the following files ready:
- Raspbian image
- Windows 3.x setup files
Preparing Windows 3.x
When you have the original Windows 3.1 or 3.11 from MSDN, you have downloaded a self-extracting executable. I have no idea why this is since you need Windows to run the executable…
- Run the executable on your PC and extract the files to a new folder. The result should be somewhere around 612 files (386MAX.VX_, 8514.DR_, 8514FIX.FO_, etc. etc.).
- Place all the files in a compressed zip file. In my case I called it “win.zip”.
- Upload this zip file to your OneDrive, email it to your webmail or place it somewhere else where you can access it from the internet. You’ll need to obtain it later on your Raspberry.
Setting up Raspbian
- Insert your Micro SD card in your PC and format it as FAT32.
- Use Win32DiskImager to write the Raspbian image to your SD card.
- Insert your Micro SD card in your Raspberry, connect network, a HDMImonitor, keyboard and mouse to it and finally attach the power source. If it all went well you will see Linux booting up and open up a BIOS like configuration screen.
- In the menu first choose “Expand Filesystem”. This makes Raspbian look what disk space is available besides from the size of the image that we wrote to the SD card.
- Then choose the third option, “Enable Boot to Desktop/Scratch”. Set it to boot to the desktop, this is the easiest location to get Windows to run.
- Optionally you can explore the other options like setting your localization right, enabling the camera, overclocking etc. When done select “” to close the configuration tool and reboot the PI.
- In the Desktop environment we start by opening an LXTerminal window (the icon that looks like a monitor).
- In LXTerminal enter the following command to make sure your OS is fully up to date:
- Then install DOSBox with the following command:
- After DOSBox is installed the next step is to transfer Windows to your Raspberry. You can download the file we prepared before with the Epiphany web browser.
- Now we go back to the terminal window to create a dos/windows location and extract the zip file: (replace the filename “win.zip” by the name of your downloaded zip and mind the capital D in Downloads)
- That was enough Linux stuff, open the menu, click on games, DOSBox
- We now need to mount (last Linux command, I promise) a C:\ drive with the following command:
- Now the Dos folder is our C: drive!
Start the windows setup by entering:
- Windows will now start the installation 🙂
You will now have Windows on Raspberry PI, We want to thank Ruben Middel for this awesome guest post on WindowsInstructed on how to get Windows on Raspberry PI!
looks a good idea…….
I have ALL versions of DOS from 1.2 upwards and ALL windows fro v2 onwards with 3 and 3.1 and 3.11 on original disks and CDs….. why?????
It will be good to try out (not now as I’m ill) as I also have OrCad and Autocad that run on DOS 5 upwards inc win 3 to 98 (but not newer)…. it would be perfect if Iit could emulate the TSENG3000 graphics card as well.. but thats asking Toooo much (wouldn’t it)
I hate to be the bearer of bad news but you’ve got your commands mixed up. OS is updated with the “sudo apt-get update” command, not the win3.x setup program. dosbox is installed with “sudo apt-get install dosbox” whereas you have its mount C drive command listed. Mounting a C drive inside of dosbox also is not a linux command, and lastly windows setup is started with “C:\cd winstall setup”.
Just thought i’d clarify this a little bit because the commands you listed are all over the joint and definitely not in proper order of events. it was quite confusing to read.
Thanks for your comment, I will inform the orginal writer to take a look and correct it if it indeed is wrong.