I've had issues with DEVLOAD refusing to load drivers in XMS-only
situation when using DEVLOAD's /H paramater (which is try UMBs first,
just like DEVICEHIGH/INSTALLHIGH/LOADHIGH).
Through some testing this has been narrowed down as a difference between
Devload 3.20 (works) and 3.21 (fails)
Configuration:
kernel 2040 + XMGR + FreeCOM + UIDE (so XMS-only, no UMBs)
Commandline:
DEVLOAD /H UIDE.SYS /H /D:FDCD0001 /S5
3.20 visual output:
Using UMB-first allocation
Filename: A:\DOS\UIDE.SYS
{lots of UIDE output}
1 char device installed.
Driver staying resident
result:
UIDE ending up in low memory if no UMBs.
(think it actually installs 2 char devices, being FDCD0001 and UIDE$,
but oh well)
3.21 visual output:
Trying to use UMB.
Error: Can't grab memory to load driver (0001h - File read error)
result:
Loading aborted
I'm able to email a 1.44MB bootdisk image if anyone wants to verify my
test setup and results.
So should I use/supply 3.20 instead of 3.21?
Was 3.21's intention to explicit fail instead of still load, if no UMBs
or too few UMBs? It's a valid decision, just prefer to know about it.
best regards,
Bernd
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
