3 ms·
Although I started working with computers in the days of DOS and before Windows, I never did much networking so can't say I'm too familiar with this stuff; but
by userbinator 6y ago
Although I started working with computers in the days of DOS and before Windows, I never did much networking so can't say I'm too familiar with this stuff; but with the binaries being in the kilobytes range instead of megabytes, and correspondingly simpler abstraction layers, it probably wouldn't be too difficult to track down the packet loss bug even without any source code. My random-but-somewhat-educated guess is that certain sizes of packets are lining up with frame boundaries and causing something to think it has already sent a packet when it hasn't yet done so.
- axiolite 6y agoThe author, Michal Necasek, is certainly an expert on decompiling old binaries. He has reverse-engineered old copy protection system, patches old operating systems to run on modern systems or emulators, patches together broken installation disk images to make them work again, is frequently disassembling old programs to find out why they worked on older hardware and broke on newer ones, and more. Doesn't take long reading his site to find articles with such things.
- EvanAnderson 6y agoI used the MSNet client on real physical hardware back in the mid-90s. I don't remember seeing the terrible write speeds depicted in the article. The DOS machines I'm thinking about targeted Windows NT 3.51 as the server. I wonder about the behavior being introduced due to higher CPU speeds. Slowing the VM down to the speed of a machine contemporaneous to the code might yield some insights.