Wine still maintains and even improves Windows 3.x support! I hope they don't
give up!
Can we use Wine code while implementing WoW16?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
Wine still maintains and even improves Windows 3.x support! I hope they don't
give up!
Can we use Wine code while implementing WoW16?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
That second Windows should have been ros.
On 17 March 2017 at 01:25, David Quintana (gigaherz)
wrote:
> Running windows inside a vdm window isn't the same as running the apps
> directly in windows, as if they were native apps.
>
> On 17 March 2017 at 01:07, Javier Agustìn
Running windows inside a vdm window isn't the same as running the apps
directly in windows, as if they were native apps.
On 17 March 2017 at 01:07, Javier Agustìn Fernàndez Arroyo wrote:
> some people have had success in running Win 3.1 under ReactOS thanks to
> NTDVM, so
some people have had success in running Win 3.1 under ReactOS thanks to
NTDVM, so win3.1 apps can be run too :)
On Thu, Mar 16, 2017 at 11:49 PM, David Quintana (gigaherz) <
gigah...@gmail.com> wrote:
> That's not true. NTVDM is not WoW16. NTVDM is just DOS support. In order
> to support 16bit
To be the most accurate, WoW16 is an addition to NTVDM. NTVDM alone provides
16-bit emulation plus DOS support. WoW16 adds on top of that, Win 3.1 support
(which is also 16-bit). WoW16 is implemented using wow32.dll (the 32-bit part
that interfaces directly with NTVDM), wowexec.exe (the
That's not true. NTVDM is not WoW16. NTVDM is just DOS support. In order to
support 16bit (windows 3.1) applications, a whole other system is needed.
On 16 March 2017 at 23:37, Javier Agustìn Fernàndez Arroyo wrote:
> "-Implementing WoW16 support. I suppose that'll draw
I can tell you some possible next steps:
- x64: implement PAE support in the 32 bit kernel
- SMP: Implement resource translators and arbiters (I have some initial work
for this somewhere)
- Also SMP: build a CONFIG_SMP kernel (with some hack to use the regular HAL)
and debug any issues coming
No worries. Getting the thing setup correctly is worth any wait.
On 16 March 2017 at 10:39, Colin Finck wrote:
> Hi again!
>
> Mark's commit yesterday has revealed a misconfiguration of the FishEye
> indexing. Namely it only indexed source code files up to 100 KB and his
>
Am 16.03.2017 um 00:03 schrieb Huw Campbell:
> SMP or 64 bit processor support would be great. Too hard?
I think that's too much for a single GSoC student. But we also keep
saying this for a long time... The result is that everybody is afraid of
those "big topics".
What we need is some kernel
Hi again!
Mark's commit yesterday has revealed a misconfiguration of the FishEye
indexing. Namely it only indexed source code files up to 100 KB and his
edited freetype.c was 136 KB. Looking into our repository, we have
source code files up to 1 MB.
Unfortunately, the only way to fix this is
11 matches
Mail list logo