I don’t know why I never tried it before, but it actually works! And it’ll even spawn out to a window two. Although without share/record locking it’ll end up being a world of pain, I suspect. Maybe vDOS/vDosPlus will work? I know it’ll work fine if you boot MS-DOS inside of DOSBox, but for some reason I never actually tried to stress the v86 mode of DOSBox from within Windows.
In this case, I’m looking at the ultra popular Sim series, and their Windows releases. While I was a big fan of SimCity, especially having played it on an Amiga, when I found out that there was a Commodore 64 version I had bought it immediately as I wanted to play it at home. And let me tell you, it was a severely underwhelming experience.
From the logo it’s all down hill. I know that SimCity is actually from 1985, and as the first version, the Commodore 64 version is basically the prototype.
Which was just graphically underwhelming, but I still played the hell out of it. And then I saw the Spectrum 48k version. Yes the blocks are ‘buildings’ as the units fill up they will turn into black with only the letter remaining. Despite the ultra minimal graphics, the game play is there. And once you get used to the bizarre combination keyboard+joystick controls it is addictive. I mean it is SimCity!
But going to the PC, I kind of grew out of SimCity. DooM was the hot game, and the whole immersive 3d thing. And of course during that era being on the PC I only knew of the MS-DOS version. While there was a version for OS/2 Warp released much much later, and by then if I felt the urge there was SimCity 2000 for Windows.
But after getting the kick for SimEarth, and finding the Windows 3.0 version, I was much surprised to find out that there was a version of SimCity of Windows 3.0 as well!
And I can see why I never had seen this for retail, or knew anyone who had it.
That’s right in the included form, the price was $59.95. And SimEarth was $69.95! To put that in perspective that would be now $107.17, and $125.04 respectively. And people think $60 for a game today is expensive!
To get the full experience I went ahead and loaded up PCem, with a 386 and EGA graphics to get that original feel.
Since this requires Windows 3.0, with either EGA or VGA graphics, and 2MB of RAM, I figured I would go with a ‘top of the line’ souped up 386DX. I tried to load it up with the Wyse700 driver, and the game fails to load resources. I don’t know if its even possible to make black and white or four colour resources, as I live in the future, and I have millions of colours!
That said, I tested and it has no issues with 8bit depths either.
Installation is pretty smooth, the game is shipped on either two 360k 5 1/4″ diskettes, or a single 720kb diskette. While modern games have so much more, there is many things this game is lacking. But Maxine isn’t one of them.
No really, she is listed as a feature.
The music is through the PC speaker. Just like the sound effects. Multimedia integration with Windows that we take for granted today just wasn’t a thing back then. The version I have is 1.0, Although a pirated version 1.1 that was sent in actually includes WAV sound effects, and a single midi track. However it doesn’t run on Windows 3.0. So lucky me!
Ah the UAE, the bane of Windows 3.0. They were so unpopular that Microsoft had to rename the dialog.
Living in the constraints of EGA feel absolutely claustrophobic in today’s world. 640×350 just isn’t enough screen rel estate. Even 640×480 is far far too small. And that lead to one issue I found
While using a SVGA driver so I can get that impossible to afford experience of 1280×1024 in 256 colours, but the application was never meant to run in something that wide. You can easily put child windows ‘behind’ the dead space, and you can never recover them. You have to save and re-launch. bummer.
Which leads me to perhaps the most famous reputation of SimCity for Windows. As mentioned on Joe’s site, there was a massive struggle to get games like SimCity running on Windows 95. As Raymond Chen says:
If any application failed to run on Windows 95, I took it as a personal failure. I spent many sleepless nights fixing bugs in third-party programs just so they could keep running on Windows 95. (Games were the worst. Often the game vendor didn’t even care that their program didn’t run on Windows 95!)
Yes, they basically knew it had problems. In the box they even had this cute flyer:
And yes, rest assured it actually does work. It even works on Windows 3.00a under Citrix MULTIUSER 2.0. Pointless as there is no way to have remote graphical displays but nice to see it work.
So what went wrong? Where was all the follow up games for Windows? Obviously the hardware needed was incredibly expensive. A 386 or even a 286 with a few megabytes of RAM was expensive. VGA or EGA monitors were also very expensive. Even mice were expensive! Putting together a low end PC basically barred you from this high end premier experience. I can’t imagine that Maxis sold many copies of this. As mentioned above I’m pretty sure there is a reason why I never saw this in the wild.
Spending $3000 in early 1992, which is $5197.95 in today’s money. I can’t even begin to imagine spending over $5,000 to play a game. It’s no wonder when older machines show up on eBay people want far too much for them.
In a strange way I like to watch SimCity animate in the background. It’s like a fish tank, or staring out into a busy street. With the advantage that I can summon a giant lizard to destroy it at my whim.
I found this kind of interesting, a breakdown from the original guy behind the once popular After Dark screen saver.
- UX lessons from the Magic of Screensavers (part I)
- UX lessons from designing After Dark (screensavers II)
As it started as an experiment on Windows 2, it became a product on it’s own, and launched an entire industry, along with being copied by every major OS vendor. In the 90’s having a screen saver was key, just as having simple games like solitaire, especially a broken shuffle one where the user wins most of the time led to Windows being heavily favored in the work space.
So for the heck of it, I figured I’d check it out, and as always thanks to Jason Scott, there is a copy of 1.02 on cd.textfiles.com And as reported it’s basically the ‘mystify your mind’ screen saver.
The runaway hit Magic Screensaver became After Dark, which then had several licensed addons like the Simpsons, Star Wars etc. Back then themes for Windows were popular along with sound effects. A lot of the functionality is still in Windows, although most people prefer that their machines are silent, only making audible alerts if there really is something wrong. But back in the day a ‘multimedia desktop’ was a $5,000 noise maker, and not many offices were impressed. Which of course gave rise to the ‘office sound card’
Naturally under Windows there were virtual device drivers to emulate a sound blaster, as people still wanted to game with this cheaper ‘business audio’ card, although with the rise of Windows 95/Direct X gaming under Windows finally became a thing making Sound Blaster compatibility a thing of the past.
But going back to After Dark, they made a fatal error of teaming up with Berkeley Systems, who eventually started to make their own releases pushing the original team out of their own product.
The toasters became focal in a few lawsuits, namely the Jefferson Airplane album, although it was dismissed as the artwork for the album had not been trademarked! And they were able to force the Opus ‘n Bill screen saver where Opus shoots the toasters. Late they changed the toasters to have propellers to avoid being too similar.
Oddly stuff like screen savers too have largely fallen out of fashion with the rise of power saving monitors that just turn themselves off either from a lack of new images, or a signal from the OS.
One of those weird legacy things that in today’s world really doesn’t have that much meaning, but a scant 20 years ago was a major industry.
So I’ve always heard about the incompatibility, and I thought I’d give it a try in PCem. I know I used to run DR-DOS 5.00 and Windows 3.0 (because of the CGA driver) and it worked fine.
So just to prove it works, here I am installing Windows 3.0 on DR-DOS 5
And even better, running Word 2.0! Although I did install a whopping 4MB of ram on this virtual 286.
And to make it all the better, I changed to a 386, and re-installed Windows 3.0 and yes it runs in enhanced mode. And I can run DR-DOS in a windows.
Of course there was the AARD code, in the Windows 3.1 betas, but as far as I know that didn’t make it to release. I was able to upgrade to a virtual VGA adapter, and update to Windows 3.1 in standard mode on a 286, just fine
And DR-DOS worked through the standard mode task swapper
But Windows 3.1 in enhanced mode always locked up during setup. Maybe a PCem bug? I’m not sure. But Windows 3.0 works great.
Well from popular request I finally got around to loading this up. I went ahead with my favourite retro emulator, PCem for this, as it can nicely emulate an EGA display, unlike most emulators which do VGA, however when it comes to older versions of Microsoft products they really can detect the difference between EGA and VGA.
So to start off, I downloaded from the project page, this version of PCem, compiled it, and installed MS-DOS 4.01 , from April of 1989. The Windows 3.0 Debug Release 1.14 itself is dated from February 22nd, 1989. Which I figured is close enough to the time period. I’m using the 486SX2/50 because I’m too impatient for the 386 speeds, but it does work fine on 386 or higher emulators. It does NOT work with any 286 emulation. I’m also using the HIMEM.SYS from MS-DOS 4.01 vs the one with the Windows 3.0 (Alpha? Beta? Technical Preview?) since it is slightly newer.
There is no setup program per say, rather it just xcopies all the files to a directory, and from there you run ‘d.bat’ and away you go. This version is hard coded to an EGA display, which again is the reason I went with PCem. Once you start it up, you are greeted with:
And it identifies itself as Windows Version 2.1
And first thing to notice is that on my setup with 8MB of ram, I have over 6MB of RAM free. Compare this to regular Windows 2.1 which gives me 399Kb of ram in my current setup.
And with Windows/386 Version 2.1 it provides 383Kb of real memory, along with 6.7MB of EMS memory, as the Windows/386 Hypervisor includes EMS emulation.
Of course the major limitation of Windows 2 is that it runs in real mode, or in the case of Windows/386 an 8086VM. As I mentioned a while back in a post about Windows 3.0, This was game changing.
As now with Windows running in protected mode, all the memory in my PC is available to Windows, and I am using MS-DOS, with nothing special.
Besides the limitation of being EGA only, the Debug version of 3.0 is that there is no support for MS-DOS applications, as WINOLDAP.MOD is missing.
This is clearly an interim build of Windows 3.0 as mentioned in Murray Sargent’s MSDN blog Saving Windows from the OS/2 Bulldozer. As mentioned from the article they began their work in the summer of 1988, so considering this is early 1989 it shows just how much progress they had made in getting Windows 2 to run in protected mode. Along with Larry Osterman’s MSDN blog post Farewell to one of the great ones, which details how the Windows 3.0 skunkworks project was writing the new improved 386 hypervisor, and how Windows 3.0 got the green light, and changed the direction of not only Microsoft but the entire software industry.
I’ve been able to run most of the Windows 2.1 applets, however I’ve not been able to run Excel 2, or Word 1. I suspect at this point that only small memory model stuff from Windows 1 or 2 is capable of running. Although at the same time, when 3.0 did ship, you really needed updated versions of Word 2 and Excel 3 to operate correctly.
The applets from Windows 2.1 seem to work a LOT better than the one from Windows/386 2.1 if that helps any.
This is an interesting peek at an exceptionally early build of Microsoft Windows.
So with all the excitement with jsDOSBox it was about time I tried to get something from my old java dosbox stuff running again.
As a quick note, as of right now, you cannot boot into a disk image… Nor can you really run bat files, or any kind of drivers beforehand. It’s basically either use a script that adds files one by one, or use an image file which gets mounted, and you run your exe/com file from that.
So here we go, back again is the old Fortran Dungeon (zork) compiled with QuickC for Windows, running on the working model version of Windows 3.0.
This was the first version of Watcom that included the much beloved DOS4/GW dos extender. Funny enough it doesn’t bind in a stub for running DOS4/GW by itself, you have to do it manually or I guess write the stub for yourself. Another fun feature of Watcom C/386 8.5 is that it includes the win386 windows extender.
Basically it does to Windows 3.0 what DOS4/GW does to MS-DOS. Now I’ve never messed around with win386 that much because by the time I did have a 386sx processor with more than 1MB of ram, Win32s & OS/2 2.1 were all the rage. But in the world of VM’s I thought I’d give it a shot.
The default example is the game of life. It compiles trivially, but the moment you got to run it you get this fine error:
It turns out that it is a timing loop error, and effects of all things Microsoft FoxPro! The solution is provided by Microsoft, in the form of IPatchFP.exe. Naturally it is a console Win32 executable. But with enough of the HX DOS Extender‘s runtime I can run the patch inside of MS-DOS.
With my executable all patched up, I can now run the game of life!
Which is all very exciting.
Win386 was very cool for the time, taking the Win16 API and making their own Win32 set out of it. Another cool thing is that there wasn’t a separate runtime to repackage, as Win386 was just bound to the executable. I’m sure it didn’t fall on deaf ears at Redmond with the disillusion of Cruiser, that Win16 could have a brave new future in Win32.
And I should mention I’ve gone over a lot of the Win32s versions here.
I don’t think it’ll do anyone any good, but for some reason I’ve gotten two requests since I’ve mentioned that I’ve got a PS/1 and if I could dump all the weird software that it comes with…
Not that prodigy even exists anymore, or there is anything you can do with it, so I figured I’d just add it in with jdosbox, and you can just click along..
I guess it was unique at the time when most OEMs just slapped together some stuff and shipped without going that extra crazy mile of doing some custom programs, or even trying to foster their own online community even if it was just too forward looking, and too much of an Island for 1991.
There is some very 90’s feeling Learning Windows that also came with the system.. I’ve never heard of it before. What is more interesting is that it is a Windows program, unlike the later introduction/tutors for Windows that were MS-DOS programs. It’ll even run in real mode, which makes me wonder was it just such a major pain to put together that they swore to never do again, or was it specially made for IBM?
At any rate most of the programs are MS-DOS based, there is a version of AOL that sits in between the time of Quantium Link & AOL called Promenade. Again since the service is dead there isn’t much you can do with the dialer software. It does use GEOS like the later AOL software, but its skinned to look like Windows (SAA?).
Oh well its a look at a distant OEM past, now IBM doesn’t make PC’s and I would almost guess that OEM’s would be forbidden or heavily shunned to make their own online social type thing, as of course everyone would be on face book ….
At any rate, I’ve upgraded mine with a semi compatible sound blaster, and a network card.. With rlfossil an Conex, its a nice BBS terminal, with good ansi support. Sadly the bigger DJGPP stuff won’t run as I don’t have a math coprocessor, and I’m just not going to go through the motion of finding an 80387sx .. Assuming the PS/1 even has a socket for one (I haven’t seen it, but I didn’t look too hard). But I’ve found it good with old era games, as there is some things that just don’t seem to cooperate just right with emulation.. And sometimes it is nice to have some real machines… Sometimes.
I forget how I got linked back to this, but I figured in the new year vogue, I’d make a video to show how … convaluted it is to build dungeon via f2c.
As you can see, first I have to compile f2c as a Windows QuickWin exe as the MS-DOS version just runs out of memory without some kind of DOS Extender, and Windows 3.0 makes a suitable extender..
Next, I had to make a ‘list’ program that then exectued f2c against the Fortran converting them to C. Then finally I just compile the libf2c components, then statically add in the Dungeon source that was just converted. There is some ‘out of range’ case statement, not sure why, but it works… as you can see.
It builds/runs in 286 enhanced mode and beyond.. Obviously the more memory the better.
This was on Qemu 0.15.0 with MS-DOS 4.01 & Windows 3.0
So while I was playing around with the idea of a Windows 3.0 powered (lol) BBS I ran into one weird thing with it swapping like crazy, and eventually depleting all my disk space!
Well when I actually used Windows 3.0 back in the day, I had a 286 so I never got to play with virtual memory. By the time I got a 386, I was using Windows 3.11 & OS/2 which in Windows you configure it with the 386 icon in the control panel. On OS/2 it’s a line in the config.sys.
But for Windows 3.0 it’s a standalone program, swapfile.exe. And the best part is that you cannot run it in 386 Enhanced mode, nor in standard (286) mode. You have to first start Windows in realmode.