Re: [ros-dev] New ideas added to GSoC Ideas list

[Can Tasan]

I also have some ideas here, not fully sure about their feasibility. Tried to be wise as much as I can.

-Continuing USB work that vardanm started. Yes, I know a developer is working on that. Another joining student would be great and speed up things.

-Continuing TCP/IP stack work if noone is working on rewrite.

-Working on DirectX support: bringing new features, fixing bugs, optimising, if possible fixing some driver issues...

-Fixing driver unloading/fallback problem (CORE-8294) I think it's a hurdle on our hardware compatibility, but not sure its priority.

-Would some kind of Win32 subsystem work be too hard?

-Implementing some missing things in shell.

-Implementing more user mode stuff, or is it enough for now?

-Extending printing support.

-Fixing current audio support, if our devs don't want to tinker with it.

-Implementing WoW16 support. I suppose that'll draw attention.

And as said before, proper application compatibility database. :) By the way, I'm too pleased to join and see you here all!

With my best regards,
Can Taşan

[Huw Campbell]

Hi all,

SMP or 64 bit processor support would be great. Too hard?

Cheers,
Huw

On Thu, Mar 16, 2017 at 7:28 AM, Can Tasan [e-mail] wrote:
> I also have some ideas here, not fully sure about their feasibility. Tried
> to be wise as much as I can.
>
> -Continuing USB work that vardanm started. Yes, I know a developer is
> working on that. Another joining student would be great and speed up things.
>
> -Continuing TCP/IP stack work if noone is working on rewrite.
>
> -Working on DirectX support: bringing new features, fixing bugs,
> optimising, if possible fixing some driver issues...
>
> -Fixing driver unloading/fallback problem (CORE-8294) I think it's a
> hurdle on our hardware compatibility, but not sure its priority.
>
> -Would some kind of Win32 subsystem work be too hard?
>
> -Implementing some missing things in shell.
>
> -Implementing more user mode stuff, or is it enough for now?
>
> -Extending printing support.
>
> -Fixing current audio support, if our devs don't want to tinker with it.
>
> -Implementing WoW16 support. I suppose that'll draw attention.
>
> And as said before, proper application compatibility database. :) By the
> way, I'm too pleased to join and see you here all!
>
> With my best regards,
> Can Taşan
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Colin Finck]

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 dev looking into these topics and giving a
rough overview what needs to be done and in what places. Then we can
have a roadmap and split the work up into smaller tasks that are even
doable by GSoC students.

If nobody makes this first step, we will never have SMP or x64 CPU
support. People also kept saying that full printer support is too much
for a 6-month bachelor thesis, and they were right, but nevertheless I
was able to build the foundations and documentation in that time.
And now I could guide everyone interested how to continue on achieving
full printing support.

- Colin

[Thomas Faber]

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 from broken spinlock usage

On March 16, 2017 5:50:39 AM EDT, Colin Finck [e-mail] wrote:
> 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 dev looking into these topics and giving a
> rough overview what needs to be done and in what places. Then we can
> have a roadmap and split the work up into smaller tasks that are even
> doable by GSoC students.
>
> If nobody makes this first step, we will never have SMP or x64 CPU
> support. People also kept saying that full printer support is too much
> for a 6-month bachelor thesis, and they were right, but nevertheless I
> was able to build the foundations and documentation in that time.
> And now I could guide everyone interested how to continue on achieving
> full printing support.
> Colin
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[Javier Agustìn Fernàndez Arroyo]

"-Implementing WoW16 support. I suppose that'll draw attention." --> NTVDM,
already done :)

"Working on DirectX support: bringing new features, fixing bugs,
optimising, if possible fixing some driver issues..." ---> ReactX, would be
great!

On Thu, Mar 16, 2017 at 2:28 PM, Thomas Faber [e-mail]
wrote:
> 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 from broken spinlock usage
>
> On March 16, 2017 5:50:39 AM EDT, Colin Finck [e-mail] wrote:
> > 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 dev looking into these topics and giving a
> > rough overview what needs to be done and in what places. Then we can
> > have a roadmap and split the work up into smaller tasks that are even
> > doable by GSoC students.
> >
> > If nobody makes this first step, we will never have SMP or x64 CPU
> > support. People also kept saying that full printer support is too much
> > for a 6-month bachelor thesis, and they were right, but nevertheless I
> > was able to build the foundations and documentation in that
> > time.
> > And now I could guide everyone interested how to continue on achieving
> > full printing support.
> > Colin
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[David Quintana (gigaherz)]

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 <[e-mail]
> wrote:
> "-Implementing WoW16 support. I suppose that'll draw attention." -->
> NTVDM, already done :)
>
> "Working on DirectX support: bringing new features, fixing bugs,
> optimising, if possible fixing some driver issues..." ---> ReactX, would be
> great!
>
> On Thu, Mar 16, 2017 at 2:28 PM, Thomas Faber [e-mail]
> wrote:
> > 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 from broken spinlock usage
> >
> > On March 16, 2017 5:50:39 AM EDT, Colin Finck [e-mail] wrote:
> > > 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 dev looking into these topics and giving a
> > > rough overview what needs to be done and in what places. Then we can
> > > have a roadmap and split the work up into smaller tasks that are even
> > > doable by GSoC students.
> > >
> > > If nobody makes this first step, we will never have SMP or x64 CPU
> > > support. People also kept saying that full printer support is too much
> > > for a 6-month bachelor thesis, and they were right, but nevertheless I
> > > was able to build the foundations and documentation in that
> > > time.
> > > And now I could guide everyone interested how to continue on achieving
> > > full printing support.
> > > Colin
> > >
> > > Ros-dev mailing list
> > > [e-mail]
> > > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> > --
> > Sent from my Android device with K-9 Mail. Please excuse my brevity.
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Hermès BÉLUSCA-MAÏTO]

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 corresponding 16-bit part), krnl386.exe (the “kernel” of Win 3.1) and the thunk dlls/exes user, gdi …

De : Ros-dev [mailto:[e-mail]] De la part de David Quintana (gigaherz)
Envoyé : jeudi 16 mars 2017 23:50
À : ReactOS Development List
Objet : Re: [ros-dev] New ideas added to GSoC Ideas list

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 [e-mail] wrote:

"-Implementing WoW16 support. I suppose that'll draw attention." --> NTVDM, already done :)

"Working on DirectX support: bringing new features, fixing bugs, optimising, if possible fixing some driver issues..." ---> ReactX, would be great!

On Thu, Mar 16, 2017 at 2:28 PM, Thomas Faber [e-mail] wrote:

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 from broken spinlock usage

On March 16, 2017 5:50:39 AM EDT, Colin Finck [e-mail] wrote:

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 dev looking into these topics and giving a
rough overview what needs to be done and in what places. Then we can
have a roadmap and split the work up into smaller tasks that are even
doable by GSoC students.

If nobody makes this first step, we will never have SMP or x64 CPU
support. People also kept saying that full printer support is too much
for a 6-month bachelor thesis, and they were right, but nevertheless I
was able to build the foundations and documentation in that
time.
And now I could guide everyone interested how to continue on achieving
full printing support.

- Colin

_____

Ros-dev mailing list
[e-mail]
http://www.reactos.org/mailman/listinfo/ros-dev
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.



_______________________________________________
Ros-dev mailing list
[e-mail]
http://www.reactos.org/mailman/listinfo/ros-dev




_______________________________________________
Ros-dev mailing list
[e-mail]
http://www.reactos.org/mailman/listinfo/ros-dev

[Javier Agustìn Fernàndez Arroyo]

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) <
[e-mail]> wrote:
> 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 <
> [e-mail]> wrote:
> > "-Implementing WoW16 support. I suppose that'll draw attention." -->
> > NTVDM, already done :)
> >
> > "Working on DirectX support: bringing new features, fixing bugs,
> > optimising, if possible fixing some driver issues..." ---> ReactX, would be
> > great!
> >
> > On Thu, Mar 16, 2017 at 2:28 PM, Thomas Faber [e-mail]
> > wrote:
> > > 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 from broken spinlock usage
> > >
> > > On March 16, 2017 5:50:39 AM EDT, Colin Finck [e-mail] wrote:
> > > > 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 dev looking into these topics and giving a
> > > > rough overview what needs to be done and in what places. Then we can
> > > > have a roadmap and split the work up into smaller tasks that are even
> > > > doable by GSoC students.
> > > >
> > > > If nobody makes this first step, we will never have SMP or x64 CPU
> > > > support. People also kept saying that full printer support is too much
> > > > for a 6-month bachelor thesis, and they were right, but nevertheless I
> > > > was able to build the foundations and documentation in that
> > > > time.
> > > > And now I could guide everyone interested how to continue on achieving
> > > > full printing support.
> > > > Colin
> > > >
> > > > Ros-dev mailing list
> > > > [e-mail]
> > > > http://www.reactos.org/mailman/listinfo/ros-dev
> > >
> > > --
> > > Sent from my Android device with K-9 Mail. Please excuse my brevity.
> > >
> > > Ros-dev mailing list
> > > [e-mail]
> > > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[David Quintana (gigaherz)]

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 <[e-mail]
> wrote:
> 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) <
> [e-mail]> wrote:
> > 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 <
> > [e-mail]> wrote:
> > > "-Implementing WoW16 support. I suppose that'll draw attention." -->
> > > NTVDM, already done :)
> > >
> > > "Working on DirectX support: bringing new features, fixing bugs,
> > > optimising, if possible fixing some driver issues..." ---> ReactX, would be
> > > great!
> > >
> > > On Thu, Mar 16, 2017 at 2:28 PM, Thomas Faber [e-mail]
> > > wrote:
> > > > 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 from broken spinlock usage
> > > >
> > > > On March 16, 2017 5:50:39 AM EDT, Colin Finck [e-mail]
> > > > wrote:
> > > > > 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 dev looking into these topics and giving a
> > > > > rough overview what needs to be done and in what places. Then we can
> > > > > have a roadmap and split the work up into smaller tasks that are even
> > > > > doable by GSoC students.
> > > > >
> > > > > If nobody makes this first step, we will never have SMP or x64 CPU
> > > > > support. People also kept saying that full printer support is too much
> > > > > for a 6-month bachelor thesis, and they were right, but nevertheless I
> > > > > was able to build the foundations and documentation in that
> > > > > time.
> > > > > And now I could guide everyone interested how to continue on achieving
> > > > > full printing support.
> > > > > Colin
> > > > >
> > > > > Ros-dev mailing list
> > > > > [e-mail]
> > > > > http://www.reactos.org/mailman/listinfo/ros-dev
> > > >
> > > > --
> > > > Sent from my Android device with K-9 Mail. Please excuse my brevity.
> > > >
> > > > Ros-dev mailing list
> > > > [e-mail]
> > > > http://www.reactos.org/mailman/listinfo/ros-dev
> > >
> > > Ros-dev mailing list
> > > [e-mail]
> > > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[David Quintana (gigaherz)]

That second Windows should have been ros.

On 17 March 2017 at 01:25, David Quintana (gigaherz) [e-mail]
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 Fernàndez Arroyo <
> [e-mail]> wrote:
> > 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) <
> > [e-mail]> wrote:
> > > 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 <
> > > [e-mail]> wrote:
> > > > "-Implementing WoW16 support. I suppose that'll draw attention." -->
> > > > NTVDM, already done :)
> > > >
> > > > "Working on DirectX support: bringing new features, fixing bugs,
> > > > optimising, if possible fixing some driver issues..." ---> ReactX, would be
> > > > great!
> > > >
> > > > On Thu, Mar 16, 2017 at 2:28 PM, Thomas Faber <[e-mail]
> > > > > wrote:
> > > > > 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 from broken spinlock usage
> > > > >
> > > > > On March 16, 2017 5:50:39 AM EDT, Colin Finck [e-mail]
> > > > > wrote:
> > > > > > 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 dev looking into these topics and giving a
> > > > > > rough overview what needs to be done and in what places. Then we can
> > > > > > have a roadmap and split the work up into smaller tasks that are even
> > > > > > doable by GSoC students.
> > > > > >
> > > > > > If nobody makes this first step, we will never have SMP or x64 CPU
> > > > > > support. People also kept saying that full printer support is too much
> > > > > > for a 6-month bachelor thesis, and they were right, but nevertheless I
> > > > > > was able to build the foundations and documentation in that
> > > > > > time.
> > > > > > And now I could guide everyone interested how to continue on achieving
> > > > > > full printing support.
> > > > > > Colin
> > > > > >
> > > > > > Ros-dev mailing list
> > > > > > [e-mail]
> > > > > > http://www.reactos.org/mailman/listinfo/ros-dev
> > > > >
> > > > > --
> > > > > Sent from my Android device with K-9 Mail. Please excuse my brevity.
> > > > >
> > > > > Ros-dev mailing list
> > > > > [e-mail]
> > > > > http://www.reactos.org/mailman/listinfo/ros-dev
> > > >
> > > > Ros-dev mailing list
> > > > [e-mail]
> > > > http://www.reactos.org/mailman/listinfo/ros-dev
> > >
> > > Ros-dev mailing list
> > > [e-mail]
> > > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev