Gregory Haerr

Hello @toncho11 and @Mellvik, I agree with @Mellvik's line of questioning, and it seems we could be dealing with a NIC that is possibly not sending (or receiving) packets reliably,...

> Let's start with the original computer my Amstrad 1640. I need a 360kb ELKS with FAT and /bootopts configured for: IRQ = 3, 280, 0xd000 I can't fit the...

@toncho11, you might be able to do a `sys /dev/fd0` on to a 360k from your 386, then manually copy just the networking files you need, along with your same...

> is it possible that you gave me some custom image where for example some things are configured for QEMU? I saw some error messages related to QEMU. QEMU is...

Hello @Mellvik, > I've looked through the send side of the wd driver. It doesn't look good to be honest - there is a definite danger over overrunning the transmit...

Hello @Mellvik, Thanks for your shortlist. Here's some comments on them: - Enhance fsck to handle 64M minix filesystems This won't be possible unless we move to a disk buffering...

> Having uncheckable/unrepairable file systems is not acceptable in the long run Well, you make a pretty good point there for solving this problem. > it's probably better to restrict...

> I was under the impression that reducing the fs size to 32M would be sufficient to have fsck work OK? We should be able to check that quickly: run...

> No such luck: > mkfs /dev/hda4 32000 Good news: I have a faked-up version of fsck running that works for 65M disks. The max data allocation required turns out...

Hello @tyama501, Nice wish list! Here's my comments: > Detecting numbers of FD drives that actually connected to the PC. This can be done using system memory information. It sounds...