SCO XENIX db_alloc() question.

[Huver]

This one got me, machine: SCO XENIX/386 2.3.2 with "Development System"
2.3.0f (I don't see how dev sys has anything to do with the problem).

Does anyone know what the story is on the Driver support function
db_alloc()?  The doc says it can be used to get up to 30 blocks of
contiguous memory, but then promptly goes to show an example of allocating
some 240 blocks.

I can't get it to work for allocating 512 bytes, 1024 bytes, or 2048 bytes;
db_alloc() always returns zero.  I only need space for 512 bytes of physical
memory (at anywhere, it's not a memory mapped case); any more will be a
total waste of resources (right now I am getting by with memget(), a HUGE
waste of 4K space).  Even if due to 386 paging it really does not get any
less than 4K per allocation, can't db_alloc() just pretend that I got my
512 bytes?  The memget() functions does.

Other than db_alloc(), what method exists to get 512 bytes of physical
(and contiguous) memory, not mapped to any particular address?

Any helpful info will be greatly appreciated.


-huver  ...!uunet!amgraf!huver  -or-  huver%amgraf at uunet.uu.net
-- 
-----
20th century miracle:
"A disk dos not have to be inserted to be examined by DISKED." -- AmigaDOS
Technical Reference Manual, 1 & 2ed.