Helge Skrivervik

@toncho11, yes, this seems time consuming. But regardless of how we decide to move forward, we need to determine - or rather - eliminate the chance that something in your...

Thanks for the links, @toncho11 The 8bit one is a very old version of yours - but I did find a writeup from SMC on the jumper settings and I...

Hi @ghaerr - > > 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...

Thank you @toncho11, this was very helpful indeed. It turns out we're back to exactly where we started: Your interface is not generating receive interrupts, quite possibly not interrupts at...

@toncho11, the IRQ is the '5' in the sequence and there is nothing wrong with the way it's being used, as evidenced by the BOOT message. If there is a...

@toncho11 - I just received the WD8003E card, which turns out to work great 'out of the box' with the current driver. Surprisingly well actually - the speed this 8bit...

@toncho11, I recently wasted a lot of time trying to get IRQ5 to work on a 386(SX) - first with a serial line, then with a NIC. I never found...

@toncho11 - per https://github.com/jbruchon/elks/issues/1371#issuecomment-1192332285 you either have to free up IRQ3 on your 386 or set the soft config jumper and get a DOS config utility in which you can...

Thank you @ghaerr!! > Enhance fsck to handle 64M minix filesystems > This won't be possible unless we move to a disk buffering scheme for reading and writing inode data...

Thanks @ghaerr, this is fast progress! > > > Having uncheckable/unrepairable file systems is not acceptable in the long run > > Well, you make a pretty good point there...