People were excited, but then kind of dismayed as they couldn’t really do much with it. Oddly enough the source code release really didn’t have any notes on how to build it, although everything needed is included. I went looking for information on how to build Word to see why it keeps doing weird things on WineVDM, and I came across this thread on betaarchive:
Special props to yksoft1 for getting it to build in the first place, and Ringding for noticing that the OS/2 supplied compiler binaries can be re-bound to run under MS-DOS using a MS-DOS Extender.
So I went ahead and fired up Qemu and within an hour I had done it!
Well this is great fun, and all, but there isn’t a heck of a lof of people with Windows 2.x around anymore. And of course Word 1.1a really wanted to have 2.11 or higher. It has some hooks for what would be Windows 3.0 although I think it was much more. Although it certainly doesn’t want to run (unmodified) under debug release 1.14.
So now that the world has gone beyond Win16 OS’s what can you do?
Well the tip of WineVDM will run it!
So now there is some new life for this old word processor.
Another fun thing in Word 1.1a is that it has an early implementation of MDI letting you view and work with several documents at once. Naturally you would need a massive monitor, which we all have today. Although people tend to just launch more than one copy of Word to accomplish this.
So now on my 64bit machine I can not only play with the source to Word, but I can run it at unimaginable resolutions on my modern machine!
I was able to port over some trivial stuff, the usual things like hello world, Infocom Interpreter, a f2c build of Dungeon, then I went with something I’d been messing around an old GDI driver for WinQuake that builds with the NT 3.5 SDK (finally got it!). So with a few minor tweeks here it is cross compiled from my x86_64 to the surface.
Last time I talked about the Surface was nearly 6 years ago… The platform’s fate was pretty much sealed on day one. With no open Win32 API it shunned traditional devs, and with some completely new and insane model it was such a hurdle for new devs, why put so much effort into such an old tired company like Microsoft?
I figured for the price of a good lunch it’d be a fun toy.
Too bad the speakers don’t work though.
I know the window on Windows 8.1 apps is closing soon. I should put something together for the dead platform. Maybe for phone too. But for tonight, it was kinda fun doing a copy/paste attack to then run unsigned EXE’s on the device.
I might upload the tool chain later, but at the moment getting Visual Studio 2012 Ultimate is a breeze.
So as part of my fun day job stuff involves moving data around and from time to time, there is that proverbial server in the corner (in this case it’s even physical!) and in this case I needed to move stuff into an old version of SQL Server as I needed to remember how to use the older BCP syntax. Obviously I guess I could have just installed 6.5 into a VM, did the SQL transfer, then the whole upgrade to 7/2000 and up to something modern, but per requirements I needed to check data in the middle, so the quickest way is to just BCP it out into something human readable, and BCP it into something new.
So it turns out the books are easily copied off the install CD, and just run the viewer application directly. And even better the ‘massive and optional’ install of all the online documentation turns out to be absolutely trivial by modern standards.
As you can see it’s really not that much in the world of terabyte disks. Anyways just copy out all the SQLBOOKS* files and then from the binn directory grab the INFOVIEW program. To view the books just run “INFOVIEW SQLBOOKS.MVB” and you’ll be set!
Some of the other older tools like Visual C++ 4.x also use this InfoViewer format, and you can copy all the other associated files, in the off chance you want to keep this ancient stuff handy.
I picked this 20 disc set recently and ugh the cringe is just… insane. And yes, that is Bill Nye…
STUDS from Microsoft . (Video in MPEG-1/Audio MPEG-2 care of JSMpeg).
I had this ages ago, although I couldn't remember if the NT 3.5 SDK/DDK had shown up at this point, but it's only the Japanese version in this set. Since I'm having such a PITA in tracking down a 3.5 set, and I'm not sitting on this, I may as well archive it.
So you too can find the early Video for Windows, and all kinds of other things from the mid '90's on archive.org.
Or Wallpapers like this 'puppy' from the Japanese version of Windows 3.1
While messing around with Windows/386 and talking to others going through their old stuff, I’d forgotten that in the box was a working model of Excel. Since I only have the physical diskettes for 2.03, I did dump the disks for 2.11 when I had that.
At this time in history the big spreadsheet that defined the PC was 1-2-3 which took the spreadsheet mantle away from the CP/M spreadsheet who in turn took it away from the progenitor VisiCalc on the Apple II. And this was the chance to define the new spreadsheet for a whole new platform.
Excel started out on the Macintosh, but with version 2 it was time to come to the PC for the new and exciting Windows 2 platoform. And to get people to try it out the key was free working demos.
I thought it was interesting that it comes with a demo showing off the ability to take data from several spreadsheets and make a 3rd with data. Oh what an exciting world 1989 was!
Oddly enough I couldn’t directly import text (csv) data into XL, but I could use Excel 3 to create a version 2 xls with my current top blog stats and then create some graphs.
I stumbled onto these three disks, seemingly out of place in history. Windows/386 version 2.0 is a strange one in that it shipped to OEM’s in late 1987, making it & Xenix part of the initial 386 wave of Operating Systems/Environments and beating out not only the OS/2 launch in 1988, but taking advantage of the 80386’s v86 mode, something that OS/2 wouldn’t be able to do in a shipping product until 1992.
This version itself appears to be a retail version of Windows/386 lacking any clear OEM identification that was so prevalent for the era. Indeed setting it up it offers a few interesting platforms:
Getting this to run was a little bit of a challenge as much as I prefer Qemu, these older 2.0x versions of Windows/386 have a BIOS/disk incompatibility with the hypervisor resulting in errors reading the hard disk. Although PCem/86Box have no such issues. I think it’ll run off floppy/CD-ROM/Network without any issue though.
The PCjs version of 2.03 has 138 setup files (not counting the PIFs), compared to the eBay’s 141, while the PCjs 2.01 has 59 files.
That said, well it’s Windows/386 mostly from 1987 with slightly updated EGA/CGA VMM drivers from early 1988 that just didn’t quite make the cut. To me what is confusing, is that it identifies as 2.03 while it’s closer to 2.01 in file count and functionality, unlike 2.03 it really ought to have been a 2.02, if there even was such a thing.
Otherwise it’s really not all that interesting short of the timestamp. It’ll run on CGA/EGA *IF* you have the proper adapter in place, although VGA is compatible, the environment will detect that it’s not actually the proper card and refuse to run. I tried to put in the 2.01 CGA/EGA drivers, but that resulted in an OS version mismatch (I didn’t check if 2.01 was locked to the Compaq OEM of MS-DOS)
I installed the infamous pair Word & Excel. Despite Word 1.1a demanding at least Windows 2.11, it appears to run okay. Excel 2.1d loaded without complaining. There isn’t very much convential memory for either, but they both can use expanded memory, which the hypervisor can create and share out without any emm386 or any equivalent driver. I can only imagine the incompatibles of trying to balance these drivers at the time, and how much the coming DPMI specification was needed.
And as the old saying goes the three top problems in Windows version 2 is memory, memory and memory. Trying to run anything graphical will exhaust convential ram, forcing you to single task anything graphical which kind of defeats the whole point of Windows. You go from this:
Oh well it’s 1987, and users were kind of used to being disappointed as such. It’s really no wonder why Windows 3.0 became the smash it it was.
And of course you can't talk about Windows/386 without this gem. (Video in MPEG-1/Audio MPEG-2 care of JSMpeg).