Win32 rename to ROS32

[davefilms]

Should ROS call it's Win32 ROS32?

[EmuandCo]

errr.... why??

[Lone_Rifle]

No.

[vicmarcal]

Well, in my blog i use two different terms:
Win32Ros: Actual Subsystem
Arwinss: Experimental Subsystem

I could call Win32Ros as just Win32 but Arwinss is also Win32, so i prefer to use the Win32Ros and Arwinss to clarify a little what i am talking about. Saying: "This app doesnt work in Win32 but does in Arwinss" is less clear that saying "This App doesnt work in Win32Ros but does in Arwinss". Soon i will introduce Yarotows too

[b4dc0d3r]

An interesting development will be when security companies name ReactOS or ROS/Windows viruses, like win32.klez - are we going to have ros32.klez? Or if the bugs are windows only, will they differentiate between MS win32 and ROS win32?

(lots of windows viruses won't work on ROS, but the ones inherent to the design rather than due to error might, especially as the number of unit tests passed increases. Also, different CVE numbers and all that, blah blah).

[RaptorEmperor]

If a program is looking for Win32 and sees ROS32 instead, could that cause software compatibility issues? I know that it's sloppy programming for a program to look for a directory by name like that, but hey, this is Windows.

What is Yarotows, anyway? I see it mentioned in CIA a lot, but I don't know what it is. Is it a branch of our current Win32? What's it for?

[Haos]

Yet Another Rewrite of the Old Windows Subsystem. Its an effort, led by Timo (Physicus) to rewrite few of the murkiest and mostly left alone reings of our Win32 subsystem. Partly a response to ARWINSS creation, one could see those as rival subprojects... Just a different aproach, if you ask me.

YAROTOWS has some successes, mostly with video driver compatibility, fixed GDI region leaks (try to run any installshield on trunk) and graphics mode change that doesnt require restart. Will be merged into the trunk when milestones are completed.

[RaptorEmperor]

Yet Another Rewrite of the Old Windows Subsystem. Its an effort, led by Timo (Physicus) to rewrite few of the murkiest and mostly left alone reings of our Win32 subsystem. Partly a response to ARWINSS creation, one could see those as rival subprojects... Just a different aproach, if you ask me.

YAROTOWS has some successes, mostly with video driver compatibility, fixed GDI region leaks (try to run any installshield on trunk) and graphics mode change that doesnt require restart. Will be merged into the trunk when milestones are completed.

...So basically YAROTOWS tries to fix the current Win32, while Arwinss starts from scratch using more Wine code? Sounds pretty cool. Will YAROTOWS be merged with trunk's Win32 and Arwinss, or just the current Win32?

[Haos]

It will be merged with trunk for sure, its only a matter of time and fixing remaining regressions in yarotows. I have no idea if it will of any use for arwinss. I think that not out of the box. Some code might be reused though.