Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

With DPMI into protect mode and back | physical memory (Developers)

posted by DOS386, 11.09.2010, 01:02

> abort the operation/process requiring physical memory and inform
> the user that he needs to configure his set-up to include an XMM

That's exactly how things should NOT be - user having to workaround application flaws coming from bad "standards" :-(

> (Sometimes using memory handled by DOS can solve this, as this should be
> mapped exactly to physical memory if there is no XMM/EMM.)

It works even with XMS host (and maybe even EMM386 ???), but there are only cca 1/2 MiB of low memory available, so it will work with "legacy" LDA sound cards, but not with HHDA (hyper high definition audio: 8 channels, 32 bits per channel sample, 196 KHz, see MPXPLAY forum ;-) ) because the 1:1-mapped low memory is not big enough :-( Another flaw: you can request neither a preferred address nor minimal alignment when hogging low memory. This means, that for a 64-KiB aligned 64 KiB buffer you must hog 128 KiB and "find" the buffer inside, the other 64 KiB are wasted. Not cool at all (consider the low-memory-wars about just a few 100 Byte's with German keyboard "drivers" :-D ).

> Not nice, but it's nothing critical.
> You didn't even mention that physical memory can't be allocated in NTVDM!
> Oh no!

:-P

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

 

Complete thread:

Back to the forum
Board view  Mix view
22758 Postings in 2121 Threads, 402 registered users (1 online)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum