There is a Win3.x copy of Trumpet (iirc), as well as the DOS one (likely what you tried) that should work, but I have no idea what apps are available.
Hi,
This has already been pointed out, but just to make sure it is clear ..
The best way to look at mTCP is as a collection of TCP/IP enabled applications. Each application (FTP, Telnet, Netcat, Ping, etc.) is a stand-alone program designed to run under DOS. The TCP/IP stack is built into the program - it gets loaded with the program, and it is only available while the program is running. It is designed for DOS only.
For Windows you want a TCP/IP stack that adds TCP/IP to windows for all applications to use. This means that each application can reuse the one DLL or loaded piece of code, instead of each application having their own copy of the TCP/IP code. That makes it an extension of the OS, just just part of a single problem.
For DOS the closest you can get to a reusable TCP/IP stack would be a TSR that programs can access via a software interrupt. The TCP/IP code gets loaded once into memory, and then the applications use the copy in memory. The applications know how to call the TCP/IP TSR and they don't include a copy of the TCP/IP code themselves. Trumpet (NTCPDRV) does this, but it is a difficult to make this code bug proof and high performance.
Two examples:
- My IRC client uses my TCP/IP code, and has it built into the program. After you load the packet driver you load the IRC client, and off you go ..
- Mike Chamber's IRC client doesn't have TCP/IP built into it, but it expects to find the Trumpet TCP/IP TSR in memory. You load the packet driver and Trumpet, and then run Mike's program.
With Windows 2000, XP and probably later versions you can use a special build of "DOSbox" to run mTCP programs under Windows. It's just emulating a DOS machine, and the mTCP code thinks that it is on a real machine. DOXbox emulates a machine with an NE2000 card, and routes the NE2000 traffic through whatever network adapter you actually have. In this setup the DOSbox gets it's own IP address and simulated MAC address, and it is essentially a separate machine.
Under Windows 95/98/Me you can also run this code - there is a piece of code out there that resembles a packet driver, but instead of sending packets out to a real Ethernet device it uses the existing operating system TCP/IP stack to send and receive the packets. This allows you to run DOS apps that use a packet driver, funneling the traffic through the standard TCP/IP stack on the system. It is not a separate emulated machine like DOSBox, so you get to share the same IP address as the main OS. Fred Macall (of DosLynx fame, http://www.users.ohiohills.com/fmacall/ ) pointed this code out to me.
It seems to me that if it's for a photoshoot all you need is a picture viewer. You can show a .png of any screen you like. HeheI've no intention of "using" (that is, applying a functional use) the machine on the internet. I just want it connected for a photoshoot, and crappy antique browsers are half the fun.
It is _supposed_ to create clean and valid semantically correct XHTML-compliant pages which is supposed to mean the a browser which reads HTML won't know the difference.kishy: Since PHP is handled server-side, won't even the oldest browsers get along with it, assuming the code being sent back to the browser is old enough?
It is _supposed_ to create clean and valid semantically correct XHTML-compliant pages which is supposed to mean the a browser which reads HTML won't know the difference.
As for Cello, having been locked away in a box for 16 years, when you open the door to the modern web, will probably pee itself when it sees what's there now. Haha. I guess you'll be the one to tell us if it works.
It just occurred to me that Simtel might be a good place to look for "antique" windows stuff. I only go there for DOS, but try their Windows 3.x winsock collection:
http://www.eunet.bg/simtel.net/win3/winsock-pre.html
or even their Windows 3.x internet collection:
http://www.eunet.bg/simtel.net/win3/inet-pre.html
Edit: I see they have both trumpet winsock, and the alternative twinsock.
I don't understand what you're talking about. Valid HTML is what you want because it is backwards compatible. I spend a lot of time in DOS and often use a simple renderer from the earliest days of markup, and it works just fine on "modern" code.That'd be the problem lol, I don't want it to be spitting out valid current HTML. It needs to spit out 15-or-so year old HTML if it's going to work.
To me those are very different protocols serving different purposes. Some browsers under current development don't do all those. Web pages can look unrecognisably different in different browsers because it is, by definition, up to the client to chose what information it wants to use and how it want to show it. Anyway, we still need to get an internet connection before any of that comes into play.Well to be clear, in a modern context, I'd think it's implied that "HTML" emcompasses HTML, CSS, and perhaps JS and of course PHP. Anything a browser is likely to run across in the course of daily internet travels, is what I had meant.
I think this is your problem.I have a 286
On a 286? Sorry, but I can only laugh at this idea :mrgreen:Opera 3.62, Netscape 4, IE3, IE5
On a 286? Sorry, but I can only laugh at this idea :mrgreen:
If there is any chance of running TCP/IP with 286 Windows, you need the really early stuff. I've found some such stuff here:
http://www.vectorbd.com/bfd/winsock/index.html
Start with "winsock.zip 120569 bytes Peter Tattam's Trumpet Winsock ver 1.0" - this is the oldest Winsock implementation I managed to find. If it works, then start trying applications like ftp, telnet, and so on...
But don't expect much, back then modern Windows software usually required 386 Enhanced Mode.