AW: [ros-kernel] 16-bit dos

[Michael]

The filesystem isn't really a big problem, as we can mount all drives
under the emulator as under the real hardware

The clipboard can be shared too, as VMware does, with a little program.
Registry could be done the same way, too.

What about a DDE-Gateway? Is that doable?

How important are other api-functions for communicating? Perhaps sharing
the msg-queue? If we really need this, we could change the api-functions
a little bit and add a gateway in the emulator.

And, a working emulator with sharing the filesystem and the clipboard
should be enough for over 99% of the cases, or? It is certainly better
than nothing and it should be much easier then using the ntvdm thing.

For DOS apps only the filesystem should be shared, so there should be
much less problems.

-----Ursprungliche Nachricht-----
Von: ros-kernel-bounces at reactos.com
[mailto:ros-kernel-bounces at reactos.com] Im Auftrag von Skywing
Gesendet: Samstag, 27. Marz 2004 20:38
An: 'ReactOS Kernel List'
Betreff: RE: [ros-kernel] 16-bit dos

Note that Win16 apps can communicate with Win32 apps (on NT and 9x).
Just
sticking them in a plain emulator isn't good enough (which seems to be
approximately like coLinux - zero interaction between emulated and
native
programs).

-----Original Message-----
From: ros-kernel-bounces at reactos.com
[mailto:ros-kernel-bounces at reactos.com]
On Behalf Of Michael
Sent: Thursday, March 25, 2004 12:26 PM
To: 'ReactOS Kernel List'
Subject: AW: [ros-kernel] 16-bit dos

What about using Dosbox? It should be quietly simply to look whether if
it's a DOS-App and then load a simple version of Dosbox without its
shell.
Dosbox is already almost running, but it has problems with OpenGL.

And for the 16bit-Header from some Apps, especially installers, I think
that wine has a workaround for it.

And for 16bit-Windows apps we could use an old 16 bit wine, perhaps even
usable in Dosbox or with Cgywin (or coLinux)?