If you search the web you’ll find a lot statements that the installation of Windows Millennium or Windows ME on Dosbox is just not possible, that it will not work, that it will not even complete setup, no matter what.
I wouldn’t be writing this if I hadn’t found differently. Nowadays it is indeed possible to run Windows ME on Dosbox and, even though it’s not supported, it is fairly stable. At least more stable than I expected and a lot more stable than Windows 98SE on the same environment.
Now the question is “Why? Why would anyone want to install an OS that was (and still is) considered the second most horrible operating system ever released by Microsoft? (The first most hated is Windows Vista) The answer to that is simple: Because people said it could not be done while there is no logical reason for this not to work. Also I never developed a bias against it as I didn’t use it at the time. I had a dual-boot Windows 98SE/Windows 2000 workstation and before I finally got around installing ME, Windows XP was launched.
Anyway, below a quick and dirty video of Dune 2000 on Windows Millennium running on a Raspberry Pi4b with Dosbian 1.5 install. One of these days I’ll modify this post with a how-to installing Windows ME on Dosbox.
Tag: Games
Command & Conquer – Play in Dosbox
When Command & Conquer was released in 1995 and its companion with a different tone Command & Conquer: Red Alert in 1996, it was something of a revolution in the RTS game play. Of course Dune II had been released a few years before, also developed by Westwood studios, setting the tone for many RTS games that followed in the years to come. (This includes Warcraft, which eventually let to World of Warcraft, DOTA and many others that a lot of people still play daily nowadays)
Now that the remastered edition is announced for 2020, the 25th anniversary of the game, I got interested again in the original Dos game. Since the original is 2CD’s (GDI and NOD) and later an expansion was added named: Command & Conquer: The Covert Operations, I thought it was time to create a quick batch file to load which ever disk instead of having to type the commands in Dosbox every single time.
Batch files are the reason that I’m using non-standard commands and add-ons to Dosbox, so here the bat-file that I’ve written for C&C:
:menu
echo 1) C&C: GDI
echo 2) C&C: NOD
echo 3) C&C: Covert Operations
echo 4) Exit to Dos
choice /C:1234 /N Option:
if errorlevel = 1 goto GDI
if errorlevel = 2 goto NOD
if errorlevel = 3 goto COVERT
if errorlevel = 4 goto EXIT
:GDI
imgmount d “c:\temp\dosbox\e\cd\C&C\C&C-CD1.iso” “c:\temp\dosbox\e\cd\C&C\C&C-CD2.iso” “c:\temp\dosbox\e\cd\C&C\C&C-Cov.iso” -t cdrom
d:\C&C
goto menu
:NOD
imgmount d “c:\temp\dosbox\e\cd\C&C\C&C-CD2.iso” “c:\temp\dosbox\e\cd\C&C\C&C-CD1.iso” “c:\temp\dosbox\e\cd\C&C\C&C-Cov.iso” -t cdrom
d:\C&C
goto menu
:COVERT
imgmount d “c:\temp\dosbox\e\cd\C&C\C&C-Cov.iso” “c:\temp\dosbox\e\cd\C&C\C&C-CD1.iso” “c:\temp\dosbox\e\cd\C&C\C&C-CD2.iso” -t cdrom
d:\C&C
goto menu
:EXIT
exit
The CD’s can be cycled with CTRL-F4 if C&C asks for it.
Caesar IV – Runtime error on Windows 10
When trying to run the Steam version of Caesar IV on Windows 10, a runtime error will pop up and will close the game.

The Eventlog gives this:

Before immediately going for the refund, there are a few things that can be done to get this working. (this does not have to be done in this specific order, as long as it’s done before running the game again)
- In the folder “C:\Program Files (x86)\Steam\steamapps\common\Caesar 4\C4” right-click on the file: “RegisterDLL.bat” and select “Run as administrator”
- In the same folder, “C:\Program Files (x86)\Steam\steamapps\common\Caesar 4\C4” right-click on the file: “CaesarIV.exe”, click on Properties, there click on the “Compatibility” tab and select: “Run this program in compatibility mode for: Windows XP (Service Pack 2)” and “Run this program as administrator” and click the Apply button.

3. Download and install “DirectX End-User Runtimes (June 2010)” from the Microsoft page: https://www.microsoft.com/en-us/download/details.aspx?id=8109
The system does not have to be rebooted.
Note: This was tested on various versions of Windows 10 up to 20H2 fully patched until January 2021.
Updated on the 27th of January 2021