8 ms·
The vagaries of 1990s 32-bit Windows networking
- king_magic 5y agoI absolutely love hearing these kinds of historical tidbits. Had no idea NT had a built-in Prolog interpreter. Prolog was one of my favorite languages back in college, neat to see that it was used like this in Windows.
- lproven 5y ago[Blog post author here] Oh cool. Glad to hear it provided entertainment. :-) No, really. I have a day-job as a writer and if I thought I could have crow-barred that in there somehow, I'd have done so. But I could not find a citation for the 4-IP address thing. So, the result was purely for fun.
- SkeuomorphicBee 5y agoOn a sightly off-topic note, the last paragraph says: > Anyway: that was the sole significant improvement in networking in Win98 that I am aware of. The other thing 98 could do was drive multiple monitors, if you had the right — that is, from an extremely limited selection — graphics cards. Otherwise, it was just 95B with more drivers and the odious Active Desktop built in. Looking back I now see that the Windows 98's "Active Desktop" was the first "builtin bloat" to the Windows Family. That was the first step that started the long march to current hated things like Cortana.
- fredoralive 5y agoI'd argue Windows 95 also had some bloat, notably it bundled a client for MSN, in it's initial form as a walled garden AOL and Compuserve competitor. Excellently timed just for the internet to become a thing and make that style of service irrellevant.
- lproven 5y ago[Blog post author here] True enough, but I slightly disagree. I had an account on it and I used the MSN. It was pretty good for its time, and streets ahead of AOL or CompuServe. Eventually it devolved into being just an instant messenger and a news website, and now, the instant messenger is gone. Secondly, if you didn't use MSN, you could just totally ignore it and it imposed no system load. In that way, it's comparable to Windows Movie Maker in XP: totally pointless if you don't need that, and you can't remove it or choose not to install it, but doesn't actually do anything at all and can be ignored. Whereas Active Desktop could not be ignored or removed (except by doing a custom install with 98Lite, which is why I linked to it) and it was necessary to use it to use the OS at all.
- lproven 5y ago[Blog post author here] I agree. Um, perhaps I should have used a less obscure word than "odious"? :-) "arousing or deserving hatred or repugnance; hateful; an odious crime; a false and odious comparison." This does neglect the reason, which was well-known at the time and may be forgotten by now. MS was subject to a monopoly lawsuit by the US Department of Justice back then, and was trying to show that IE was an inextricable part of the Windows OS. If IE were just a web browser, you could remove it and the OS would still function just fine; but if it's also the desktop, you can't uninstall it without crippling the OS -- therefore, it's part of the OS and MS couldn't be told to remove it. And that's the only real reason. The slight side-note being that "Active Desktop" was multithreaded, like the MacOS 8 Finder. In Win95 or MacOS 7, if you started a file copy (for example), the whole desktop froze until the copy was done. You couldn't do anything else except sit there and watch the progress bar. In MacOS 8, the Finder (the program that drew the desktop) got multi-threading along with lots of other improvements (desktop drawers, an easily-customisable Apple menu, and more). Start a big file operation and you could go do something else while it sat there working away in the background. IE4's Active Desktop brought this to Win95 OSR3, Win98, and NT 4 if you installed IE4. But it was the only improvement. The rest was, as you say, bloat.
- Sesse__ 5y ago> In Win95 or MacOS 7, if you started a file copy (for example), the whole desktop froze until the copy was done. You couldn't do anything else except sit there and watch the progress bar. In Win95, the copy happened on the destination folder's thread. You could still open other windows and keep browsing around, but that specific window would be unresponsive.
- lproven 5y agoThat is not how I remember it, from *extensive* use at the time, but I would have to spin up a VM to try it. I don't think you're right. The OS was still running; you could switch to an app and keep working, for instance. But Explorer had only 1 thread, AFAICR, and a large file operation visibly locked that thread.
- ngcc_hk 5y agoI am not sure. Around that time, lotus notes and application run tcp/ip. Not sure it is Novell. As so many tcp/ip, we start to take courses on a new company called Cisco and it’s competitor. Sun, hp and we opt for aix. Synapse/power build but we use oracle, we opt for the disaster oracle form 4, … My master degree with term paper on ospf. It was all 1990s craziness. The only thing is that the network driver of windows is no good in win95. There are three and we used a place in Australia start with W. I can’t remember win98 helped that much. Far East perhaps. Yes home start struggle with 1200/2400 modem. But lease line is not that fast just more stable. And bi-directional.
- lproven 5y ago[Blog post author here] You are not sure about which bit? Lotus Notes became IBM. Nothing to do with Novell. Novell's equivalent was Groupwise. I used it until 2018. It was... not great. But it didn't depend on TCP/IP. I don't think Notes depended upon TCP/IP until Domino came along in a much later version (5? 6? No idea. Last used it in 2007 and didn't like it then.)
- tzs 5y agoOne I remember was a thing we hit with Netscape Navigator. One of our products was a web proxy that ran on localhost. You set your web browser to go through the proxy, and the proxy would cache and prefetch to try to make your browsing experience nicer. We found that with Navigator network performance through the proxy was completely terrible--unless you were waving the mouse around. If you were waving the mouse around then it was fine. I don't remember all the details, but I think it turned out that this only was the case when Navigator was going through a proxy on 127.0.0.1. If we changed it to use the host's external IP address then it worked fine regardless of what you were doing with the mouse. Internet Explorer did not have this issue. We had another thing we were working on that involved an email proxy, and no email clients we tried had any oddities with 127.0.0.1 proxies. Later, we switched away from explicitly configuring browsers to use the proxy. Instead we switched to an LSP [1]. 127.0.0.1 then worked fine on Navigator, so whatever the issue was it only happened when Navigator knew it was talking to 127.0.0.1. [1] https://en.wikipedia.org/wiki/Layered_Service_Provider https://en.wikipedia.org/wiki/Layered_Service_Provider
- jcims 5y agoOver the past ~30 years of internetting, I’ve developed a reflexive habit of wagging the mouse over the screen of anything that has stalled progress, particularly in web browsers. It clearly has some kind of impact at times and is always with a shot. I’m guessing it pings the application in some kind of ui event loop.
- pjc50 5y agoIt absolutely does - the app gets a bunch of Windows messages, and the Windows scheduler boosts the priority of whatever the foreground interactive process is. https://docs.microsoft.com/en-us/windows/win32/procthread/priority-boosts https://docs.microsoft.com/en-us/windows/win32/procthread/pr... "Fair" scheduling in these situations is a nightmare that I think I've only seen BeOS and the research OS Nemesis handle correctly.
- sumtechguy 5y ago
- chungy 5y ago> a deeply misguided comment on HN that claimed that Windows 98 was the beginning of integrated networking in Windows. I've noticed that younger crowds seem to treat Windows 98 as a big revolutionary release, attributing many features that were actually introduced in Windows 95 as being uniquely new to 98; rather than Windows 98 being a rather minor incremental upgrade to 95 as it actually was. Not really sure why this phenomenon has happened. Maybe people had glimpses of Windows 98 in childhood and don't know what the prior version was like? or that Windows 98 probably had a longer lifespan than 95 did? From the user perspective, almost the only differences are Active Desktop and titlebar gradients. FAT32 and USB are other tangible differences, though it's worth noting that 95B also had those features, it just wasn't available at retail.
- pjc50 5y agoYeah, most of the big differences happened between Win95B and A, which makes them hard to count properly. USB was an absolute game-changer, for example, released in a product minor version?
- chungy 5y agoI suppose the logic was that if you needed >2GB disks and/or USB, your prebuilt OEM would order the special version of Windows 95 that supported them (and in all practical purposes, I don't even recall OEMs still using 95 RTM or 95A after 95B was available... even if the machine lacked either of those properties). Of course people would build their own computers from scratch in those days too and pirating Windows 95B (later, 95C) would be fairly common. It had big benefits while any Windows 95 box at the store was only 95A.
- iso1631 5y ago98 was definitely an incremental update on 95. Plus and Win95 OSR2 had brought in most of the "new" features of 98, although 98 did tie them together. But even including those features, coming so soon off the heels of the 3.11->95 change, it certainly felt a minor change to me. That said, 98 was the last of the Dos era (the less said about ME the better), so it did persist until well into the 00s for people playing games. And of course you've got the other "grown up" line of NT 3.51>4.0>2000
- xanathar 5y ago> Anyway: that was the sole significant improvement in networking in Win98 that I am aware of. The other thing 98 could do was drive multiple monitors, if you had the right — that is, from an extremely limited selection — graphics cards. The selection included all common S3 models, and you just had to have one S3 graphic card to be compatible, and they were already dirt cheap. It was AMAZING. This was the real killer feature (most of the time I didn't even have one IP address because dial-up internet was expensive).
- pjc50 5y ago> The NT network stack is cleanly layered, supported multiple adaptor types and protocols and clients all in one, and was so complicated that up to NT 4, when you finished making changes to the networking configuration and clicked "OK", a tiny embedded Prolog interpreter fired up and ran a single embedded Prolog program, the only one in all of the DOS, OS/2 and Windows codebase that I'm aware of -- possibly the only one in any commercial OS anywhere. This Prolog code parsed your desired config, worked out how to interconnect all the layers of the NT network stack, and wrote the configuration file(s) and registry settings in order to give you what you wanted. Aargh. I don't think even the more advanced Linux distros have reached that level of complexity yet. Although I suppose Prolog is a natural solution for constraint solving .. why do you need a constraint solver anyway? (Linked deep dive https://web.archive.org/web/20040603192757/research.microsoft.com/research/dtg/davidhov/pap.htm https://web.archive.org/web/20040603192757/research.microsof... )
- MisterTea 5y ago> Aargh. I don't think even the more advanced Linux distros have reached that level of complexity yet. No, but they do have parallel config utilities fighting each other in the case of Linux mint. Took me a few hours to figure out why I was unable to switch from a static IP to DHCP.
- wokkel 5y ago> No, but they do have parallel config utilities fighting each other in the case of Linux mint. Took me a few hours to figure out why I was unable to switch from a static IP to DHCP. Windows 10 had this as as well: the new user friendly ui can show dhcp while the interface actually is statically assigned An ip address. Took me while. Seems they dropped not only any consistency but also the prolog part in the new ui.
- p_l 5y agoSaid prolog interpreter is also why Microsoft could easily boast that NT is much easier to configure networking on than UNIX systems of the day. There was more prolog hidden underneath network operating systems than people think, too.
- jedberg 5y agoThis article doesn't even touch on the best part of Windows networking -- until around 1997, the best networking stacks were made by 3rd party vendors. While Win95 technically had it built in, if you actually wanted a robust network stack, you installed a 3rd party stack, most likely Trumpet Winsock. Microsoft published the Winsock Spec/API up until 1997, when their stack finally got good enough to make the other apps obsolete. I think they still use the Winsock API to this day.
- donkarma 5y agothis killed my browser history, wtf?
- chungy 5y agoBasically why I always use the middle mouse button to open links ;)
- lproven 5y agoExactly so, yes!
- pjc50 5y agoLike many of the more "helpful" browser APIs, the ability to alter history is easily abused. It should never have been allowed to edit cross site history.
- comprambler 5y agoI had to go back 9 “pages” to get back to hn. I guess LJ is just trash now.
- mattowen_uk 5y agoNone of that happened to me. HN was one click on the back button. That said, agreed - LJ is trash.
- dan_linder 5y agoWhen I first saw the complaint about LJ, I first thought was "LinuxJournal" And I had to do a double take on the URL. This URL is "LiveJournal", for anyone coming across this thread later. Hijacking the back button is never a good idea...
- zerocount 5y agoI didn't know Livejournal was still around.
- mrlonglong 5y agoPing of death. What a time to be alive !