guessed UDMA flowchart:

0)init
1)check soutbridge // if southbridge unknown, abort
2)do basic tests // if a test fails, abort
3)check for XMS // if fail, go to 5
4)do advanced tests // XMS required, if a test fails, abort
5)load UDMA-code/driver
6)crash if UDMA loaded high, but no VDS present // XMS-test should have been done and 
succeeded.
7)end

so a config.sys with only:
DEVICE=UDMA.SYS should work

and this works also
DEVICE=HIMEM.EXE
DEVICE=UDMA.SYS
DOS=HIGH

and this also
DEVICE=HIMEM.EXE
DEVICE=EMM386.EXE
DEVICE=UDMA.SYS
DOS=HIGH,UMB

and this probably crashes because of (lack of) VDS
(required for DMA-using drivers like network cards, disk controllers and caches?)
DEVICE=HIMEM.EXE
DEVICE=EMM386.EXE
DEVICEHIGH=UDMA.SYS
DOS=HIGH,UMB

this again works? no UMBs so no DEVICEHIGH, so UDMA does not need VDS
DEVICE=HIMEM.EXE
DEVICE=EMM386.EXE
DEVICEHIGH=UDMA.SYS
DOS=HIGH,NOUMB

I'll try DEVICEHIGH with EMM386.
didn't Tom implement a basic VDS option?
DEVICE=EMM386.EXE VDS

Bernd


------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to