#Trumpet winsock windows 3.1 download software#
#Trumpet winsock windows 3.1 download windows#

I played with it for a while, but I had no compelling reason to keep it.ДЄs I recall, Win2K was the point where I stopped using the Win9x branch.

#Trumpet winsock windows 3.1 download windows#

The UI was quite nicely designed, IMO better than Windows of the time. I tried OS/2 2.0, but when I installed it I found that my video card didn't work at high resolution. IMHO OS/2 and Windows NT were the real game changers on the personal computer platform. Windows 3.x never allowed me to multitask as well or as reliably as I'd come to expect from the mainframe and superminicomputer systems I worked with. I used OS/2 because of it's true multitasking and memory protection, then switched to Windows NT when it became available. Win 3.1 was first decent version of Windows, and it's successor, Win3.11 was the network capably version. Yes, this post brought back some memories. I believe 3.11 was code-named (or jokingly named) 'Visine', because it 'takes the red out' - NetWare's brand identity and packaging being pure red. Memory protection led to far more robust operating systems and Windows 3.11, which added networking, killed the all-dominant NetWare for that reason, despite delivering less peak performance, at least initially. In fact Windows/286 running in 286 protected mode has a better (finer grained, 16 bytes paragraph IIRC) memory protection scheme that caught more pointer bugs than 386 protected mode with (4K) page-based protection that's still in use today in Windows 10. I'm sure everyone remembers the Unrecoverable Application Errors, later renamed General Protection Faults, which resulted from process address space partitioning in Windows 3.0 and 3.1 already. rings a bell? DOS Protected Mode Interface? In fact Windows/286 and Windows/386, both in the Windows 2.x time frame, used some level of memory protection, while Windows 3.0 - and of course 3.1 and much later, Windows 95, were based on DPMI.ДЈ86 added paging and memory virtualization. Without protected mode memory addressing a badly behaved application could overwrite the memory in use by another application, or the operating system itself.ДЄhem.

#Trumpet winsock windows 3.1 download software#

hardware and software support for protected memory addressing was the critical step toward the robust systems we all came to love. But it was also available with OS/2 (late 1987). That came to Windows users with NT (1993). Win 3.1 and Win 95 didn't utilize the protected memory however.

That was supported by the Intel 80286 (circa 1984) and improved with the 80386 (late 1985).

And multi-tasking itself doesn't really require a whole lot of processing power. The big difference with OS/2 and NT, in addition to true memory protection, was the fact that multitasking was enforced by clock interrupts so that a single process couldn't monopolize the CPU, just like in 'real' multitasking operating systems.ДЄll of the computers we use today use still time-slicing. If an application went into a compute loop and didn't periodically invoke the special 'yield control' API call, then you ended up being locked out of your system.

The OS could then give control to a different application until it in turn had to wait.Д«ut that only worked as long as the applications played nicely. The difference is that in Windows 3.x systems concurrent execution was possible only because the OS got control back from the application each time the application asked for I/O or had to wait for the next user input event. What they really did was time-slice each application as processors didn't really have the power to support true multi-tasking with the apps live and processing in the background as we have today.ДЄbsolutely. Non of them really multi-tasked at that time, despite what the advertising said.