With DPMI into protect mode and back - EDIT: example (Developers)
> > The only way is just to terminate the application.
> Correct.
Not that much.
> > terminate it. Maybe is possible to run some child process but I don't
> > want to call any external EXE file
> This is correct too. To accomplish this without relying on files, create a
> fake process. You can do this manually, then set the PSP with Int21.50 or
> use Int21.26 or Int21.55.
Right. You exposed a big advantage of DOS compared to Windows:
In DOS there is a (hacky, as usual) way to brew a separate process without brewing a file. In Windaube this is impossible to accomplish (except very aggressive kernel intrusion at least):
> The name of the module to be executed. This module can be a 
> Windows-based application. It can be some other type of 
> module (for example, MS-DOS or OS/2
> process in RM. Worked in NTVDM after
WtF ??? 
Works for me in FreeDOS and EDR-DOS (my own, not example above).
BTW, I prefer INC CR0 from DPMI 
---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***
Complete thread:
- With DPMI into protect mode and back - Laaca, 13.08.2010, 10:36 ![Open in board view [Board]](img/board_d.gif) ![Open in mix view [Mix]](img/mix_d.gif) - With DPMI into protect mode and back - EDIT: example - ecm, 13.08.2010, 14:30- With DPMI into protect mode and back - EDIT: example - DOS386, 26.08.2010, 09:18- With DPMI into protect mode and back - EDIT: example - ecm, 26.08.2010, 14:35- With DPMI into protect mode and back - EDIT: example - DOS386, 27.08.2010, 03:33- With DPMI into protect mode and back - EDIT: example - ecm, 30.08.2010, 21:51- With DPMI into protect mode and back | physical memory - DOS386, 06.09.2010, 20:08- With DPMI into protect mode and back | physical memory - ecm, 07.09.2010, 17:04- With DPMI into protect mode and back | physical memory - DOS386, 08.09.2010, 00:51- With DPMI into protect mode and back | physical memory - ecm, 08.09.2010, 20:53- With DPMI into protect mode and back | physical memory - DOS386, 11.09.2010, 01:02- With DPMI into protect mode and back | physical memory - ecm, 11.09.2010, 01:25
 
 
- With DPMI into protect mode and back | physical memory - DOS386, 11.09.2010, 01:02
 
- With DPMI into protect mode and back | physical memory - ecm, 08.09.2010, 20:53
 
- With DPMI into protect mode and back | physical memory - DOS386, 08.09.2010, 00:51
 
- With DPMI into protect mode and back | physical memory - ecm, 07.09.2010, 17:04
 
- With DPMI into protect mode and back | physical memory - DOS386, 06.09.2010, 20:08
 
- With DPMI into protect mode and back - EDIT: example - ecm, 30.08.2010, 21:51
 
- With DPMI into protect mode and back - EDIT: example - DOS386, 27.08.2010, 03:33
 
- With DPMI into protect mode and back - EDIT: example - ecm, 26.08.2010, 14:35
 
- With DPMI into protect mode and back - EDIT: example - DOS386, 26.08.2010, 09:18
- With DPMI into protect mode and back - Japheth, 18.08.2010, 08:04- With DPMI into protect mode and back - Japheth, 18.10.2010, 11:17- With DPMI into protect mode and back - Rugxulo, 18.10.2010, 23:07- With DPMI into protect mode and back - Japheth, 19.10.2010, 09:58- With DPMI into protect mode and back - Rugxulo, 19.10.2010, 10:09- With DPMI into protect mode and back - Japheth, 19.10.2010, 10:20
 
- Possible CWSDPMI design flaw - Japheth, 19.10.2010, 17:59
 
- With DPMI into protect mode and back - Rugxulo, 19.10.2010, 10:09
 
- With DPMI into protect mode and back - Japheth, 19.10.2010, 09:58
 
- With DPMI into protect mode and back - Rugxulo, 18.10.2010, 23:07
 
- With DPMI into protect mode and back - Japheth, 18.10.2010, 11:17
 
- With DPMI into protect mode and back - EDIT: example - ecm, 13.08.2010, 14:30
 Board view
Board view Mix view
Mix view