ultimatefere.blogg.se - Trumpet winsock windows 3.1

#TRUMPET WINSOCK WINDOWS 3.1 INSTALL#
#TRUMPET WINSOCK WINDOWS 3.1 SOFTWARE#
#TRUMPET WINSOCK WINDOWS 3.1 PC#

Page Layout: Aldus PageMaker 4.0 (before Adobe bought it) Graphical Desktop over Windows 3.1: Calmira II (Windows 95 UI clone)

#TRUMPET WINSOCK WINDOWS 3.1 SOFTWARE#

I run all of the following software on both machines: Someone will ask why don't I just run these and other old OSs in virtual machines - I do, its just more fun to run them on native hardware I run dozens of vintage Windows 3.x programs software programs and suites (and some 32-bit ones with Win32s) on both the XT-486 and the Pentium system. Both systems are fully networked (10/100) via mTCP+Trumpet Winsock and both are enabled with sound and maximum rez graphics. Windows 3.11 runs like a rocket on that box. I also have a dual boot Pentium 4 2.8GHz system running both a modern OS one one partition and Windows 3.11 on the other (I use BootIt Bare Metal for partition management). The project is called The Big Blue Beast. Of course there is bound to be someone out there that won't believe that anyone could possibly run Windows 3.x on a PC/XT at all, let alone have an IBM 5160 running with its original 5160 motherboard with a 486DX CPU and run Windows 3.1 in protected mode with, 5MB of expanded RAM, removable solid state CF drives, and 8MB of expanded memory, but read the following link and you'll see how crazy some of us hardcore vintage computer folks are: I also run it with Calmira II as one of my favorite GUI overlays - a Win95 GUI clone.

#TRUMPET WINSOCK WINDOWS 3.1 PC#

I run PC DOS 2000 (7.1) and Windows 3.1 on an IBM PC/XT 486DX 33MHz.

Now verify that "C:\TWSKPPP\TWSK21F" is in your PATH.I am a major vintage computer geek.

Use the cursor keys to highlightĪlt-f again and select Exit to quit the editor. PATH = C:\TWSKPPP\TWSK21F C:\TWSKPPP\LWP\BIN C:\WINDOWS C:\WINDOWS\COMMAND

Your PATH statement should now look something like this:.

Be sure to put a semicolon between allĭirectory names in your PATH. If it is at the end of your PATH statement, try

If "C:\TWSKPPP\TWSK21F" is missing from your PATH statement, add.

PATH statement can be at most 128 characters long.) Trumpet WINSOCK, from Peter Tattam of Trumpet Software, was a shareware package that added dial-up TCP/IP connectivity with a Windows Sockets (Winsock 1.1). Or it might be at the end of a PATH statement that is too long. Normally, you willįind it at the end of the line. (This may be a very long line.)Ĭheck and see if it has "C:\TWSKPPP\TWSK21F" in it.

Look for a line in the autoexec.bat file that starts.

My favorite operating system of all time is Windows 2000 Professional. By the way: did anyone ever register Trumpet Winsock It was shareware, but no one ever seemed to care about that. If you wanted to get on the Internet with Windows 3.1 you had to get Trumpet Winsock. "C:\TWSKPPP\TKSK21" in the PATH, you need to add it. Imagine MP3s being limited to the 8+3 format: madonna1.mp3, madonna2.mp3, etc. In the above case, "C:\TWSKPPP\TWSK21F" is in the PATH, so the PATH is

PATH=C:\WINDOWS C:\WINDOWS\COMMAND C:\TWSKPPP\LWP\BIN C:\TWSKPPP\TWSK21F

You should see something like the following:.

Verifying that Trumpet Winsock is in the PATH The following commands at the DOS prompt: Winsock.dll file in the AOL25 directory, you would enter One in the C:\WINDOWS directory and one in the

In theĪbove example, there are two unneeded winsock.dll files, If your computer has unneeded winsock.dll files (i.e.,Ĭ:\TWSKPPP\TWSK21F), you need to rename them. Verifying that you have the correct winsock.dll This does not cover situations in which you cannot Winsock problems are a result of one of the reasons in the listĪbove. Note: The following text assumes that your Trumpet

#TRUMPET WINSOCK WINDOWS 3.1 INSTALL#

When you install Trumpet Winsock, the installer tries to copyĬ:\TWSKPPP\TWSK21F. In the PATH ahead of the correct winsock.dll.

There must not be another (wrong) winsock.dll file.

It has to be in the PATH variable (or in the same.

Winsock.dll file that comes with AOL software. Running Trumpet Winsock, you cannot, for example, use the The winsock.dll file must satisfy the following conditions: TCP/IP stack, which in turn talks to the modem. Winsock.dll, which communicates with the underlying These programs are written to interface with Information here may no longer be accurate, and links may no longer be available or reliable.Īpplications such as Netscape Navigator and Telnet Host This content has been archived, and is no longer maintained by Indiana University.