Not this kind!

I got a tip in another post about this fantastical project, boxedwine!  It’s Wine + a 386 processor emulator, and it’s been targeted to SDL.  What does this mean? Wine on Windows!

Sim Earth for Windows 3.0

I went ahead with one of the oldest Windows games I have around, SimEarth, for Windows 3.0.  I don’t have Balance of Power, although I guess I may procure a copy one day.  Anyways it’s Windows in it’s 1990 glory 16bit, 286 protected mode, and sure as heck won’t run on Win64.  Oh sure you can run this on MS-DOS + Windows, but where is the fun in that?

Now that’s all good fun, sure Wine can run stuff, sure, but it’s still wine.  Well remember all that noise about android running Wine?  Yeah, well here we go.

Wine + x86 emulation +SDL in javascript!

Here we go.  Games, and the BoxedWine project page.   And yes, it can run stuff like Quake 2, and other far more intense applications.  Just like Wine.  It’s really great stuff, check it out, if only in a browser.

If you want to run ancient Win16 stuff in a pinch, it may actually run.  I had issues with win87em.dll stuff, but just like Wine it’s a moving window of compatibility.

Running MS SQL Server 4.21 on OS X.

Yes, you read that right.  Thanks to the power of Crossover (Wine) I’m running SQL 4.21 on OS X.  But the installation is *NOT* straightforward.  Actually it doesn’t install at all.  But you can ‘transport’ a working copy from a Windows machine into Wine, and it’ll run.

The first thing is, if you’ve ever dealt with MSSQL is that it is VERY picky about machine names.  So first install MS SQL 4.21 in a NT 3.1/3.5/3.51/4.0 VM with a name you like. Also remember to set the default client library to TCPIP. Then create a Wine instance on your target box.  Next you’ll need to make a few changes to the registry to force the machine name:










I called my machine MSDE, as I have no imagination.  With those keys in place the next thing to do is grab the service keys..




Then finally the MS SQL product key:


The final step was to copy over the c:\sql directory, and create icons for the SQL Server, and the management tool.

To run, start the server first (SQLSERVR.EXE) , then launch the admin tool (SQLADMIN.EXE), and you should (hopefully) be able to connect!

MS SQL Server 4.21 running on OS X

MS SQL Server 4.21 running on OS X

And there we go! Is it useful? Not really, but I mean it is cool! I haven’t tried this with 6.0 or 6.5 but I imagine they should work as well. 7.0 and beyond are more complicated to transpose as they require a great deal of COM integration. In theory they should work.