Discussion on:

Windows 3.1 experiment hits a wall

I mentioned a couple of weeks ago that I was going to try to see if it was possible to still run old technology in 2008. To start off, I was going to try running for a week or more doing real work with Windows 3.1. However, poor Windows 3.x can't even get out of the starting gate as I mention in Classics Rock:

http://blogs.techrepublic.com.com/classic-tech/?p=157

Part of the problem was the Virtual PC environment I chose, but even after those problems, Windows 3.x is outdated enough that you can't get a Web browser that will surf the Web reliably. In and of itself that practically precludes Windows from being serviceable.

I still have a copy of Office 4.2 to install along with a 16 bit version of Outlook, but I think it's going to be a complete lost cause.

Any recommendations about how to get it working or what to do next?

Use DOSBox. It runs Windows 3.11 with minimal fuss, and has emulated support for IPX.

Let us know if this works for you.

Hmmm... that's a thought. I've heard of it, but havent had the chance to actually play with it.

I assume you mean TCP/IP support and not emulated IPX support. As much as I like Netware, IPX is pretty useless today.

Quite correct. Not only IPX emulation, but DOSbox emulates a modem too.

From what I have read on the DOSBox forums, the latest version simply requires that you load netbios.exe for IPX to work. YMMV.

I've actually been looking for a way to get the VMware emulated NIC and TCP/IP supported through the Dos VM in my collection.

When 3.11 was viable for internet connectivity, it was through a modem dialer that provided the interface for browser, gopher and what limited other programs where available in the Windows world.

The install of my Dos VM went clean but hit a dead end right there where I couldn't transfer anything more too it without emulating sneaker-net connections.

Microsoft has a TCP/IP stack for Windows 3.11. The link to the download is in the main posting in the blog. It uses the NDIS2 driver of the emulated network card. It binds and will allow Internet access without needing a modem, although IE 5.01 still acts as if it needs a modem.

There are a few DOS TCP/IP stacks around. I dont have any right now, but I'll see if I can find one.

It was one of those posting before reading the original article moments.

The primary issues I see are a network card driver or sorts for Dos to interface with VMware by and the tcp/ip stack.

(Then there is the issue of how many of my win3.11 install diskettes have rotted but I have ways around that one.)

I'll see what that links has to offer though if you spot any other dos tcp/ip in passing I'd be interested to look at them also.

What will happen in the next 5 years? Is XP, 2000 going to be out of date also?
Will we be able to keep up with the changes that are coming?
How can we keep up to speed?

Can't recall the exact reasons, but we never used SX chips. It may have been that the AMD 386/486 DX chips were faster or the fact that all machines had to have the '87 coprocessor fitted because they were doing spreadsheet & database work.

In those days we were using WFW 3.1 & 'Dos for Workgroups' to network 286, 386 & 486 machines many of which had internet access. The net access was handled by a separate modem for each machine. Many of the 486 DX 2/4 66 machines were still in using WFW 3.1 when we rolled out Win98. The last of the DOS for Workgroups 286 machines were pensioned off in mid '95, I believe that all 386 machines had been Chip upgraded to AMD 486 & so continued for some time after that date.

All 486 machines had at least 8MB RAM, some had 16 (4 x 4). Everything possible was shadowed, we made extensive use of RAM drive configs. This configuration would have facilitated the winsock/tcpip stack setup. We also made extensive use of RISC based Graphics Accelerator cards.

In most cases our WFW networks co-exited alongside Novell.

In the time before WWW the internet tools were Telnet & Gopher clients. Once the WEB arrived I recall using pre 1.0 versions of Netscape ( beta 0.73 rings a bell).

As to MS Office. The preferred word version was Word for Windows 2.1 - can't remember the Excel version but I do recall that these preferences were related to resource demand.

If you want a test site for browsing with such a machine today you might try gutenberg.org as many of their pages are designed for a high level of backward compatibility.

Hope this provide some insights that will help you climb the "Wall".

Cheers

I remember I used Trumpet WinSock to dial a modem and access Internet under Win3.1. Trumpet needs a lot of parameters tweaking in order to run optimally. Netscape was in their glory days. Seems since Netscape v3.x they supports JavaScript, but I don't know if it's still could render the modern web sites properly...

Your first problem is that windows 3.1 sees a year of 00 as 1900 and not 2000. In short you can't boot a system on 3.1 in the 21st century. You've fallen at the 1st hurdle.

Windows 3.x perfectly well understands the difference between 2008 and 1908. I could post a screen shot of Schedule + under Windows 3.x to show this if you'd like.

Second of all, Windows 3.x doesn't 'boot' like Windows XP does. You first boot DOS and then load Windows 3.x on top of it. It's DOS that has the problem with dates after 1999, but even that has nothing to do with booting the OS. It more relates to how the files are saved.

If you do a DIR at a DOS prompt, it would display today's date as 08-06-08, which does look like 1908. Open File Manager in Windows 3.x and it displays the date as 08-06-:8. The : is the Y2k goofup with Windows 3.x

But... Windows 3.x runs perfectly well in the 21st century and knows that it's 2008 and not 1908.

DOS never had that problem. The date was ALWAYS stored internally as 4 digits. Only the output of the DIR command showed 2 because it was assumed humans would be able to figure it out. It was the application programs that had the problem.

John,

Can you post another link to the file for the soundblaster? That web site has no links, just the title of the file. I can't download the one you used.

Kevin

http://lmgtfy.com/?q=sound+blaster+16+driver

Of course, you could always try Creative itself. (You can probably still get the apps there as well.)
http://support.creative.com/Products/product_list.aspx?catID=1&CatName=Sound+Blaster#

I will try this driver and thanks a lot, but it's not really a Win 3.1 driver, it's a DOS driver. It contains none of the Win 3.1 apps that come with the SB16 driver I did find that doesn't work.

Win 3.1 is just a graphical shell that rides on top of DOS. The driver will work, you just won't have the graphical apps to run in Win 3.1.

Pick the correct one from the list at Creative. I found several valid drivers straight from the internet search as well.

The apps were frequently separate - apps aren't drivers, and they aren't necessarily packaged together.

Tell you what - tell me the exact driver & apps you want.

Which exact 16-bit card is it? (name & model # - [CT-xxxx])
You want Windows 3.1, yes?
Do you want DOS & Win3.1 & Win9x as well?

Not only can I find them on the net, but I have originals, a card, book, and older updates I got from Creative years ago.

Terrorists hit computers and software with this driver and codec stuff.

Excellent

Your an open source fan then?

Balthor is an open horizons kind of guy/girl. The time and space continuum are but a minor hindrance to Balthor!

As soon as I read Balthor's post, my first thought was "Balthor Strikes Again".

"Growl for me. Let me know you still care."