Hi again,
first: What makes you think the Book8088 supports UMB?
I think that USE!UMBS driver should test memory areas
BEFORE it tries to put UMB there :-p
LTEMM is the driver for the new EMS card i have
https://www.lo-tech.co.uk/wiki/Lo-tech_2MB_EMS_Board
this is the card
As said, your mainboard already has EMS built in. So you
could use some of your 16 MB of RAM as EMS directly with
the right driver for your mainboard. Of course 16 MB on
the mainboard plus 2 MB on the LT board is even more :-p
EXP16 is the packet driver for the
https://theretroweb.com/expansioncards/s/intel-etherexpress-16-isa-tp-aui
I assume the 82586 controller has to reserve some memory
above 640k as I/O buffer. If you use the network while
you try to use exactly the same area as UMB, the contents
of your UMB will be overwritten by network stuff :-p
Apparently the chip starts by expecting config data at
the end of the first 16 MB, which can contain pointers
to buffers anywhere, but control data has to be bundled
in some 64 kB zone somewhere and for DOS drivers this
somewhere could have easily been designed to be < 1 MB.
https://theretroweb.com/chips/7791#docs
Do UMB work with DR DOS? If yes, in which memory areas? Which
options or parameters do you use for the UMB and EMS drivers?
CA00-CFFF and E600-E7FF
the EMS driver is set to D000 - DFFF page frame
let me give you my configs for both kernels
https://github.com/user-attachments/files/20191174/cherry4.zip
Let me check... What is that OTRI driver with the many options?
Did SEEMSG2, MM, EMM286 work for you? What is ASPIPPM1?
FreeDOS:
lastdrive=m, buffers=16, files=12, dosdata=umb, dos=high, dos=umb
and depending on boot choice some of:
ltemm /p:d000 /i:260 /h:128
fdxms286 (without options)
use!umbs e600-e7ff
nnansi.com (why .com?)
shellhigh is 4dos with 1kb environment size.
You could use LASTDRIVEHIGH, BUFFERSHIGH and FILESHIGH with UMB.
In Autoexec, you invoke DRV, HW, CDROM, FDNET, FDASSIST and
WELCOME batches and load FDAPM APMDOS. Probably some kind of
extremely complex hardware autodetecting default config :-o
SvarDOS DR-DOS:
lastdrive=z, buffers=16, files=12, dos=high, dos=umb, dosdata=umb
and then always, all as devicehigh:
ltemm /p:d000 /i:260 /h:128
fdxms286 (without options)
use!umbs ca00-cfff e600-e7ff
nnansi.com (why .com?)
shellhigh again is 4dos with 1kb environment size.
This is similar to the FreeDOS case, but you tell USE!UMBs to
allocate more UMB space here. Also, note that you cannot really
load drivers with DEVICEHIGH before you have UMB drivers loaded,
so those will just fall back to acting like normal DEVICE lines.
So you basically can only load NNANSI and 4DOS high. Maybe you
can also load LTEMM high. FDXMS286 must load before USE!UMBS.
Autoexec is pretty much the same, but in FreeDOS, you use
command /c ... fdnet ... start
while in SvarDOS DR-DOS, you use
call ... fdnet ... start
https://retrocmp.de/hardware/above-plus/use!umbs.txt
This says:
If you want to find out whether you have UMBs, run the program
TEST!UMB.EXE. This program will run through the upper memory
and try if it can write information there. [...]
The locations where TEST!UMB can succesfully change values are
RAM locations. It will display a table with its findings, sta-
ting:
"None at paragraphs xxxx until xxxx" or
"Found RAM at paragraphs xxxx until xxxx"
What does TEST!UMB say on your computer when you run it
AFTER loading all other drivers but WITHOUT loading USE!UMBS?
Note that this version did not take command line arguments,
you had to patch the binary to select which UMB areas to use.
https://www.vogons.org/viewtopic.php?t=83477 links the newer
variant of USE!UMBS which does take command line arguments.
This might also be worth reading:
https://forum.vcfed.org/index.php?threads/loading-dos-high-on-a-xt.32320/
Regards, Eric
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
