I had an old RTL8139 lying around so I switched of the internal LAN controller. Put this in the slot. Did the steps here: https://help.fdos.org/en/hhstndrd/network/ndis_ins.htm
works like a charm. And maybe... once upon a time in the future I might look into getting the other controller toe work. Now let's see if I can connect to my NAS 😊. Thank you all for the ideas. Nico Netherlands -----Original Message----- From: Frantisek Rysanek via Freedos-user <freedos-user@lists.sourceforge.net> Sent: Thursday, September 12, 2024 12:07 PM To: freedos-user@lists.sourceforge.net Cc: Frantisek Rysanek <frantisek.rysa...@post.cz> Subject: Re: [Freedos-user] Networking on a Pentium 4 > Load the “lsl.com ”driver by running the command Load the > “e1000odi.com” driver by running the command ... > Many folks use DHCP and mTCP on FreeDOS. I believe that for M.Brutman's software, you need the CRYNWR "packet driver" interface. You have loaded two low-level elements of the driver stack needed for Novell networking. If you don't really mean to follow up with more Novell stuff, but instead want to try CRYNWR-based apps, there's the option to add odipkt.com on top, and *then* set up M.Brutman's TCP/IP stuff. Another way would be, to get a native packet driver for the Intel e1000 series. I'd say E1000PKT.COM. https://packetdriversdos.net/ https://github.com/ulrich-hansen/E1000PKT Appears to be a 3rd-party open-source driver, not Intel's in-house software. Chances are, that if Intel's own ODI driver breaks the SATA controller's interrupt service (due to a shared IRQ), the open-source E1000 packet driver still has a chance of working fine. (Being a whole different codebase, may be more sensitive about hooking the ISR vector, may have a different memory footprint and whatnot). Also, if the OP is using the disk controller via the stock BIOS routines (which may use UDMA on their own, which is generally allright), and he suspects that loading an Ethernet driver breaks disk access, he should try loading a dedicated driver for the IDE Controller - which will take over the disk service from the BIOS, and may be more tolerant to shared PCI IRQ handling quirks than the stock BIOS routines. Perhaps the most up-to-date "alternative IDE driver for DOS" is Japheth's XDMA32.DLL, companion/addon to his JEMM386. https://github.com/Baron-von-Riedesel/Jemm To download the current binaries in a ZIP archive, click the link to the current release on the right (v5.84 at the moment). Use the JLOAD tool to load the XDMA32.DLL. When trying to solve an IRQ conflict where disk access gets jammed, you probably want to load the disk controller driver before you load a driver for your NIC. Wouldn't work the other way around :-) Or maybe, set up a RAM disk, load everything you need into the RAM disk, then you can shrug your shoulders about the HDD, and load your NIC driver... Frank _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
