How Quake.exe got its TCP/IP stack

Post by justsomehnguy » Fri, Nov 21, 2025, 1:20 AM UTC

fredoralive wrote: post #127

justsomehnguy wrote: post #104

Earlier quoted context omitted.

I still don't quite get how you should had communicate with the other systems over the network with STREAMS. With IP you have an address and the means to route the data to that address and back, with TCP/UDP sockets you have the address:port endpoint so the recipient doesn't need to pass a received packet to the all processes on the system, asking "is that yours". So if there is already some network stack providing b…

STREAMS isn’t a networking protocol, it’s an internal data routing thing some UNIXes use locally, and amongst other things to implement the network stack in it. You’d still be talking of stuff like IP addresses and the like with it. Probably with the XTI API instead of BSD sockets, which is a bit more complex but you need the flexibility to handle different network stacks than just TCP/IP, like erm…

Post by maybewhenthesun » Sat, Nov 22, 2025, 4:15 PM UTC

db48x wrote: post #126

maybewhenthesun wrote: post #14

Earlier quoted context omitted.

Amen to that! I think I remember there was some communication between ID and Charles Sandmann about CWSDPMI, so even though it's worded a bit strange for an open source project there's probably some thruth in it? Also a bit strange how the author is surprised about Quake running in a 'VM', apparently they don't really know about VM86 mode in x86 processors...

Is the author surprised by that, or did you just misread it? The only relevant quote on that page that I see is “It is impressive to see Quake run at full speed knowing that Windows 95 runs DOS executable in a virtual machine.” He is perhaps surprised that it runs _at speed_ in the VM, not that it runs in the VM which he already knows about.

Post by kelnos » Mon, Nov 24, 2025, 6:38 AM UTC

eknkc wrote: post #16

skrebbel wrote: post #13

Random drive-by nitpick: > From the beginning of the development, id had requested from djgpp engineers that their DPMI client would be able to run on djgpp's DPMI server but also Windows 95 DPMI server. I'm pretty sure that "DJGPP engineers" is just one guy, DJ Delorie. DJGPP was always open source so I bet he got some contributors, but if the rest of this sentence is true that "id has requested from djgpp engineers…

Completely off topic; So I just took a look at DJ’s website and he has a college transcript there. Something looked interesting. Apparently he passed a marksmanship PE course at the first year. Is that a thing in US? I don’t know, maybe its common and I have no idea. I’d love to have a marksmanship course while studying computer science though.

Post by blackcatsec » Mon, Nov 24, 2025, 4:40 PM UTC

sempron64 wrote: post #105

blackcatsec wrote: post #61

Earlier quoted context omitted.

Quite literally folks have done this for decades using Hamachi.

Hamachi and STUN were what I was thinking of when I referred to user-unfriendly NAT busting. It's true that these are not much harder to get working than a modem, but they don't match up with modern consumer expectations of ease-of-use and reliability on firewalled networks. It would be nice if Internet standards could keep up with industry so that these expectations could be met. It's totally understandable where we…