Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

Possible fix for cwsdpmi trouble (Announce)

posted by RayeR Homepage, CZ, 08.11.2020, 17:39
(edited by RayeR on 09.11.2020, 01:23)

> Also, the cwsdpmi host can handle multiple clients, so nested execution
> probably don't needs additional extended memory.

Seems to not be problem for DPMI apps, maybe problem for other apps using XMS without DPMI. I tested some various combination of XMM/EMM/DPMI with 2 DJGPP apps nested call that reported avail phys mem and allocate 32MB for itself (4GB phys. RAM installed).


XMM   | EMM/V86MON  | DPMI server    | 1st client mem avail | 2nd nested client mem avail
-----------------------------------------------------------------------------------------
  -   |       -     |   CWSDPMI7     |       4066 MB        |          4066 MB
HIMEM |       -     |   CWSDPMI7     |       3506 MB        |          3506 MB
HIMEM |       -     |   HDPMI32      |       3509 MB        |          3476 MB
HIMEM |   EMM386*   |   CWSDPMI7     |         31 MB        |            31 MB
HIMEM |   EMM386*   | CWSDPMI7NOVCPI |       1453 MB        |          1452 MB
HIMEM |   EMM386*   |   HDPMI32      |        957 MB        |           924 MB
HIMEM |   JEMM386   |   CWSDPMI7     |        119 MB        |           119 MB
HIMEM |   JEMM386   | CWSDPMI7NOVCPI |       3506 MB        |          3506 MB
HIMEM |   JEMM386   |   HDPMI32      |       3509 MB        |          3476 MB
HIMEM |   WIN98SE   |   WIN98SE      |       1769 MB        |          1769 MB , can run DN
WINXP |   WINXP     |   WINXP        |       2047 MB        |          2047 MB , can run DN

* XMS for EMM386 was limited to 1GB to handle it

---
DOS gives me freedom to unlimited HW access.

 

Complete thread:

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