vi /etc/gateways

net default gateway 192.168.0.1 metric 1 active

of course replace 192.168.0.1 with your gateway

restatr routed and try

BTW: the command to create the dlink interface is not mkdev dlnk but mkdev dlk (typo above) … also after untarring the de200.img, one has to chmod +x /usr/lib/mkdev/dlk /usr/lib/mkdev/rmdlk /usr/lib/mkdev/tcp before being able to issue the mkdev dlk command … also note the inconsistencies in irq and iobase throught the text and pictures, and I had to use irq 5, as the others would end up with other vectors that did not work in my setup …

yeah someone managed to upload them.
https://github.com/retrohun/blog/issues/3

I didn’t think they had intelligent peripherals going back that far, network offload ones to boot!

Then agian by the time I was old enough to get into the Enterprise grade stuff it was all those Intel i860/i960’s that nobody wanted that were on so many SCSI and host adapters. Although I don’t recall protocol offload engines until the 00’s.

I guess it makes sense with the high speed serial adapters, as 165550’s just weren’t enough, you needed/wanted something that could basically DMA serial access, and handle all those IRQ’s.

Fun things indeed!

The Excelan network card wasn’t the only ‘smart’ communications device we used – there was also a 6-port serial card that ran in the servers we sold and supported. This was equipped with an 80286, and I’m sure that on one
customer site the 80286 in the comms card was running at a higher clock speed than the one in their 80286 equipped server.

There is also some Intel acceleration available for Qemu, it’s not 100% tied to KVM. Although considering the CPU doesn’t seem to be the lagging component it feels more in line with the video performance.

Overall I know that Qemu isn’t focused at all on being ‘correct’ or running anything legacy, rather it’s just an IO subsystem for KVM and running Linux.

PCem offeres a better solution with more vintage hardware support, enough to run legacy BIOS & chipset stuff to give a more authentic (painful) experience.

This is on a windows host, isn’t it? At least for neozeed.

I’m idly curious and wonder if once kvm acceleration became stable that the qemu devs simply optimized for kvm. In this case, meaning that they may have used kvm to make up for any slowdown -by offloading it to kvm.

Since windows doesn’t have that acceleration, then performance would naturally turn into a dog.

Unfortunately, I’m not sure if I could get older versions to compile in Ubuntu 18.04 and it’s doubtful how meaningful they’d be anyway (since this would be in vmware).

There is several TCP/IP kits on archive.org now so the emulation thing isn’t needed.