On 1 Jan 2020 at 17:19, Tom Ehlert wrote: > > in short: when debugging network problems, avoid EMM386/JEMMEX. > > HIMEM and friends should be fine, though. > Okay, I'll try to figure out my way through this...
I definitely do need something to load all the resident drivers "high" wherever possible, otherwise I'm out of conventional memory. AFAICT the XMS managers are okay for this (e.g. himem.sys). Next, I strongly prefer to stick to FreeDOS because some important scripts use features not supported by the MS-DOS command.com. So first I'll try MS himem.sys under FreeDOS. HimemX.sys did not seem to make a difference compared to JEMMEX... Makes me wonder if JEMMEX with NOEMS would have a chance of working = if NOEMS changes something relevant about the JEMM's "back end behavior", or just disables the EMS interface (front end). Maybe if I cannot get this to work in FreeDOS, I could try a very bare-bones setup in MS-DOS, with hard-coded drivers and their configs, just to see if I have a chance in MS-DOS (= if it makes sense to try to massage all the scripts into MS-DOS syntax / limitations). Thanks for your insight :-) I seem to recall trying to program something in DOS that needed more RAM, and I had a choice of XMS vs. EMS. I picked XMS, because it allowed me to allocate a large window of memory that I could just work with directly. Whereas EMS would swap 64k "pages" in and out of a single 64k window in the "conventional address space"... I really don't know how DOS drivers for PCI devices using MMIO would work without a memory manager / DOS extender (DPMI seems to spring to my mind as the way to have "physical to virtual" mappings established). I seem to recall that the 16bit PCI BIOS calls can arrange a number of things, but the memory mapping is not in its capabilities? Frank _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
