[ros-dev] AC97 VBox audio is working!

[Javier Agustìn Fernàndez Arroyo]

Keep up the good work! :)
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] My problems with github.

[Javier Agustìn Fernàndez Arroyo]

He, i hay same concerns not so long ago.
I recommend to install GitHub Desktop app. It is an intuitive GUI for
Windows, but it has a Linux version too.
Basically, you must fork ReactOS repo into your profile (in GitHub). Then,
you will Link GD to that fork, NOT TO MASTER. And at last, you will
download source code from YOUR FORK. Obviously, you will have to sync fork
and main repo later, but its easy to do that via github website

El lun, 28 mar 2022 22:55, Raymond Czerny  escribió:

> Hello,
>
> my experience with git so far boils down to a 1:1 relationship of the
> repositories.
>
> - Global repository on the company's MS TFS.
> - Local repository on my development machines.
>
> Now I'm dealing with a 3 relationship.
>
> - Project repository (Reactos) on Github.
> - Developer repository (fork / /reactos) on Github.
> - Local repository on my development machine.
>
> I still need to learn how to use this feature.
>
> Please be patient.
>
> Greetings
> Raymond
>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] (no subject)

[Javier Agustìn Fernàndez Arroyo]

hello guys,
just detected a typo in HEAD, in device manager

"HAR DDISK" instead of "HARD DISK"

As this is a very stupid "bug"... should i send a report about it?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] The situation with version 0.4.14

[Javier Agustìn Fernàndez Arroyo]

Sooo... what about this, guys? 0.4.13 is ancient... is there any blocker
issue yet?

On Sun, Feb 21, 2021 at 5:40 PM George Bişoc 
wrote:

> I'd also vote for the 1st point and ultimately list the current
> regressions in the press release. After all the remaining regressions can
> be fixed and further regression testing be continued in the next release as
> usual. Most of the regressions which belong within user mode aren't huge
> stop-blockers so I see no point in delaying the release much.
>
>
> Victor Perevertkin  wrote on Tue,
> February 9th, 2021, 4:47 PM:
> > Hello!
> >
> > It seems for me that it's time to bring up the topic about our RC
> > version - 0.4.14.
> >
> > Our current "stable", 0.4.13 was branched on 30 September, 2019
> > (remember those peacefull pre-COVID times :D)
> > That's quite some time, but not the main issue I'd like to discuss.
> >
> > 0.4.14 was branched on 24 April, 2020. That's almost a year already.
> > And we're in a difficult situation here - there are regressions, but
> > nobody fixed them within this long time.
> > According to https://reactos.org/wiki/Tests_for_0.4.14, there are 29
> > unfixed regressions found for this release. I'd like to point out: most
> > of them are among usermode and non-kernel/driver functionality, and as
> > our development is mostly focused in the kernel right now, it's
> > unexpected for them to be fixed unless a volunteer comes up.
> >
> > A quick reminder. Our "releases" mechanism is useful for finding
> > regressions in the first place, there is no that much benefit for users
> > here, because we're still a "deep" alpha. Correct me if I'm wrong.
> > Joakim made a great job finding all regressions, and this work won't be
> > lost in any case.
> >
> > We can't wait forever and I think it's time to resolve this situation
> > somehow. I see two options:
> > 1. Release 0.4.14 as-is. There were a lot more buggy releases, nobody
> > dies from this.
> > 2. Skip 0.4.14. This already happened once in the history of the
> > project - 0.3.2 was skipped. I wasn't around at the time, but I may
> > guess that reasons were similar to what we have today.
> > (3.) Fix the bugs quickly. I don't expect this to happen, but who
> > knows, maybe a volunteer appears :)
> >
> > Let's vote. This seem to be the only way for us to decide on things.
> > Votes from the team members will be collected until 1 March.
> >
> > ===
> >
> > I personally vote for skipping the release. The work on finding
> > regressions is already done, so the most important part of a release
> > cycle for us is there (thanks Joakim!)
> > If we do a release now, all the stuff we were writing in news reports
> > for the last 6 month would be missing from it. That would cause (as I
> > think) a lot of confusion to people. Moreover 0.4.14 is not that
> > featureful release itself (compared to 0.4.13, which brought the new
> > USB stack)
> > So I suggest to move on and start checking 0.4.15 for regressions. I
> > expect quite some of them to appear and we need time for fixing.
> >
> >
> > Cheers,
> > Victor
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Current votes on the situation with the 0.4.14 release

[Javier Agustìn Fernàndez Arroyo]

Also, hasn´t he been fixing lots of those regressions?

On Sun, Mar 7, 2021 at 4:23 PM Mark Jansen  wrote:

> As noted in mattermost,
> I'd like to at least consider what Joachim has to say about this,
> considering the amount of work he spends on releases.
>
> Regards,
> Mark
>
> PS:
> Oleg Dubinskiy's vote is not empty, he simply sent it as html so it is
> not nicely displayed in the mailing list.
>
> On 07-Mar-21 11:18, George Bişoc wrote:
> > During the last days of February of this year some team members have
> participated in a vote concerning the delay of 0.4.14 release due to the
> amount of regressions making it not eligible to be released as per the
> release engineering guidelines. As 1st of March has already passed, this is
> the current situation with the votes as they stand out for the moment in
> the following order.
> >
> > 1. Release 0.4.14 as-is (with its known regressions as of now)
> > =====
> > * Javier Agustìn Fernàndez Arroyo
> > * Stanislav Motylkov
> > * Hermès BÉLUSCA-MAÏTO
> > * Alexander Rechitskiy
> > * George Bişoc
> >
> > 2. Skip 0.4.14
> > =
> > * Victor Perevertkin
> > * Joshua Rice (non team member)
> >
> > 3. Fix the bugs as soon as possible
> > =
> > None
> >
> > Oleg Dubinskiy's vote is not counted because his mail is apparently
> empty (???). Considering the collected votes, should we extend the period
> of voting for a few days so that the other team members can have an opinion
> too regard the matter or shall we conclude the voting as is and proceed
> further with releasing 0.4.14?
> >
> > Regards,
> > George
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://reactos.org/mailman/listinfo/ros-dev
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] The situation with version 0.4.14

[Javier Agustìn Fernàndez Arroyo]

there have been many fixes recently. But, as i have already said, i see no
point on no releasing a new alpha build. It´s still alpha, not stable.
Crashes and bugs are expected.

On Tue, Feb 9, 2021 at 5:35 PM Colin Finck  wrote:

> This is not the kind of participation that has any place on the mailing
> list of an open-source project.
> Unsubscribed and blocked that person.
>
> Colin
>
>
> Am 09.02.2021 um 17:26 schrieb Dick:
> >
> >
> > Hi,
> > as a potential user this project makes me extremely tired. in 2000 or
> > something like that i was excited because  afvree windows replacement
> > would be there.. it is 221!!! years later and there is.. still
> > nothing, jst deep alpha as stated in last email. and 0.14 woudl have
> > even regressions for 0.4.13. wouldnt it be more smart to finally build a
> > timeline for this all? or to discuss the fact if this project makes any
> > sense yet, it seems just a waste of time this way.
> > when things go on this slow when will reactos 1.0 finally be there? in
> > 2050? who cna tell if we even run software on a laptop or pc than, if
> > there is even a device available on which this will runn at all or if
> > there would be one singel user wanting to use something not totlaly
> > ai-driven?
> > reactos was ment as a user-project, like ubuntu for many users as their
> > desktop os. now it is just some fun for a few devs resulting in nothing
> > usable after 20 years. what is the idea behind this? if i was the
> > maintainer of this project i would state this:
> > we can do 2 things: 1. work hard and build version 1.0 in 5 years from
> now
> > or 2. stoop this waste of time of running behind the facts and having to
> > rebuild it everytime agian because the project goes to slow for hardware
> > it is written for to end up in a museum before somethign happens.
> > as an end-user i am highly disappointed in this project.
> >
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://reactos.org/mailman/listinfo/ros-dev
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Sad news

[Javier Agustìn Fernàndez Arroyo]

Hello guys,
I have just read at Facebook that Andrew Greenwood's father (andrew's nick
is *silverblade* at ReactOS) passed away last night due to CoVid19.
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] FOSDEM online

[Javier Agustìn Fernàndez Arroyo]

I can visit the stand, but i cant guarantee that i will be online for all
the event

El mar., 15 dic. 2020 20:47, Mark Jansen  escribió:

> Hello,
>
> This year FOSDEM is going to be an online event:
> https://fosdem.org/2021/news/2020-12-11-stands-cfp/
>
> Are there volunteers for an online ReactOS stand?
>
> We would need some short video's for introduction and demonstration
> purposes,
> as well as some people active in a chat room answering questions.
>
> Regards,
>
> Mark
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (November 2020)

[Javier Agustìn Fernàndez Arroyo]

hello,
As you know i am not a developer, so please do not take my words very
seriously

afaik VS2010 is not open source and in my opinion ReactOS, as an open
source project, should be compiled using open source tools

On Tue, Dec 1, 2020 at 1:33 PM Олег Дубінський 
wrote:

> Hi all.
>
> I'm agreed with Hermes too and voting for restoring VS2010 support, at
> least because:
> 1. Visual Studio 2010 is the last version that works (or almost works) on
> ReactOS (for now), and it's the only one app which allows compile MSVC
> build of ROS (a. will MSVC compiler work propely without VS2010 command
> prompt?; b. using MSVC instead of GCC is badly required in some cases, e.
> g., for finding build-specific regressions), so by dropping the VS2010
> support, it is not possible anymore to build MSVC ROS on ROS (and as I
> know, current RosBE doesn't support MSVC compiler out of the box, if it
> does support that at all).
> 2. Dropping useful features is not really a good idea at all.
>
> That's my arguments for restoring VS2010 support in ReactOS.
> I can't say anything more.
>
> Best regards,
>
> Oleg Dubinskiy.
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] sumatraPDF

[Javier Agustìn Fernàndez Arroyo]

my point is, to allow them to still support XP/2003 systems (and, of
course,ReactOS :) )

On Fri, May 1, 2020 at 4:16 PM M. Ziggyesque  wrote:

> They have to commit to build/sln configurations based on VS2010-17 in
> parallel with current VS2019 config, it appears, before it is a candidate
> for ROS to support as part of the rosapp collection. While some support for
> mingw builds is present, it is considered unsuitable for doing release
> builds. Due to these full RosBE integration seems implausible for Windows
> and ROS versions to stay in synch.
>
> --
> *From:* Ros-dev  on behalf of Javier Agustìn
> Fernàndez Arroyo 
> *Sent:* Friday, May 1, 2020, 8:56 AM
> *To:* ReactOS Development List
> *Subject:* Re: [ros-dev] sumatraPDF
>
> No, the answer is "if sumatraPDF compiles in ROS, we may support it"
>
> lets check it in ROS then xD
>
> "for them to support reactos, would be to support older windows versions"
> why? ROS is (more or less) XP :)
>
> On Fri, May 1, 2020 at 2:21 PM Magnus Johnsson 
> wrote:
>
>> Essentially the answer is 'patches are welcome'? :')
>> And anyway, for them to support reactos, would be to support older
>> windows versions. Then it's reactos's job to support *it*.
>>
>> Den fre 1 maj 2020 kl 13:14 skrev Javier Agustìn Fernàndez Arroyo <
>> elh...@gmail.com>:
>>
>>> check this link guys! :)
>>>
>>> (yes, i am the poster) :)
>>>
>>> https://forum.sumatrapdfreader.org/t/support-reactos/2921
>>> ___
>>> Ros-dev mailing list
>>> Ros-dev@reactos.org
>>> http://reactos.org/mailman/listinfo/ros-dev
>>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://reactos.org/mailman/listinfo/ros-dev
>>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] sumatraPDF

[Javier Agustìn Fernàndez Arroyo]

No, the answer is "if sumatraPDF compiles in ROS, we may support it"

lets check it in ROS then xD

"for them to support reactos, would be to support older windows versions"
why? ROS is (more or less) XP :)

On Fri, May 1, 2020 at 2:21 PM Magnus Johnsson  wrote:

> Essentially the answer is 'patches are welcome'? :')
> And anyway, for them to support reactos, would be to support older windows
> versions. Then it's reactos's job to support *it*.
>
> Den fre 1 maj 2020 kl 13:14 skrev Javier Agustìn Fernàndez Arroyo <
> elh...@gmail.com>:
>
>> check this link guys! :)
>>
>> (yes, i am the poster) :)
>>
>> https://forum.sumatrapdfreader.org/t/support-reactos/2921
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://reactos.org/mailman/listinfo/ros-dev
>>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] sumatraPDF

[Javier Agustìn Fernàndez Arroyo]

check this link guys! :)

(yes, i am the poster) :)

https://forum.sumatrapdfreader.org/t/support-reactos/2921
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] covid-19

[Javier Agustìn Fernàndez Arroyo]

Hi all,

This is just to ask for best wishes to all of you. I hope you are all ok
and safe.
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] 32-bit hosts virtualbox EOL

[Javier Agustìn Fernàndez Arroyo]

"Please also use version 5.2 if you still need support for 32-bit hosts, as
this has been discontinued in 6.0. Version 5.2 will remain supported until
July 2020."

FYI

That means, ROS will still be usable as guest, but not as host
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Reinstating the ReactOS Meetings

[Javier Agustìn Fernàndez Arroyo]

I think itś not the first time someone points this, but i think it's
important for ReactOS to rise

We (team, both devs and testers) should really consider improve real
hardware support. Latter releases have been focused on user experience
(icons, text layouts), and its important... but it just allow system to
be usable on VM's

On Tue, Jan 28, 2020 at 1:15 PM Colin Finck  wrote:

> This is a reminder about the upcoming meeting taking place this Thursday.
>
> The updated agenda:
> * Our GSoC 2020 Application (deadline is 5th February)
> * RosBE 2.2 and what's blocking it
> * ReactOS 0.4.13 and what's blocking it
> * For the FOSDEM attendees: Planning for the upcoming weekend in Brussels
>
> Colin
>
>
> Am 12.12.2019 um 22:30 schrieb Colin Finck:
> > Hi all!
> >
> > We had our annual General Assembly of ReactOS Deutschland e.V. today.
> > Many things were discussed which are better discussed with the entire
> > ReactOS Team, which is why all of us agreed on reinstating the recurring
> > ReactOS Meetings we had until February 2019.
> > Let's try out a bi-monthly schedule, with the first meeting happening on
> >
> > Thursday, January 30, 2020
> > 19:00 UTC
> > Mattermost private channel "Meeting"
> >
> > If you're currently not part of this channel, but think you should be,
> > please contact me.
> >
> > I'm already announcing this, so we can collect topics for the meeting.
> > Current points on the agenda:
> >
> > * Compiling an up-to-date list of tasks to work on, for newcomers, GSoC
> > candidates, and developers to hire.
> > Can already be started now by taking
> > https://reactos.org/wiki/Google_Summer_of_Code_2019_Ideas, copying it to
> > "Google Summer of Code 2020", cleaning it up and adding new stuff. Maybe
> > we also need to manage that with JIRA in the future.
> >
> > * RosBE 2.2, and what's blocking it, if it hasn't happened by then
> > * ReactOS 0.4.13, and what's blocking it, if it hasn't happened by then
> >
> > Just reply if you have anything to add.
> >
> >
> > Cheers,
> >
> > Colin
> >
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://reactos.org/mailman/listinfo/ros-dev
> >
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] wined3d, Mesa for Windows

[Javier Agustìn Fernàndez Arroyo]

We all LOVE you, Magnus :)

El mar., 14 ene. 2020 11:00, Aleksey Bragin  escribió:

> And still speaking GreatLordish! :-)
>
> On 1/14/2020 12:54 PM, gedmurphy.mailli...@gmail.com wrote:
>
> Greatlord, still lurking in the shadows 
>
> :waves:
>
>
>
>
>
> *From:* Ros-dev 
>  *On Behalf Of *Magnus Olsen
> *Sent:* 13 January 2020 21:27
> *To:* ReactOS Development List  
> *Subject:* Re: [ros-dev] wined3d, Mesa for Windows
>
>
>
> Hi
>
> I was the one 2003 started opengl and driectx support in ReactOS, at 2007
> i did have full working directx support with ms own dxg.sys from windows
> xp, i never finish all thuse part but most are in place after me, next
> issue i did look into opnengl support hw as well i never look into how
> exacly opengl work, reactos did not have any hw accertiion support for
> opengl only software with mesa, today i do not known how the status of the
> dx a d opengl support works,  before me no doc was fund in msdn and so how
> it works, ms did release the doc after my implation of what i doc in the
> code and the wiki
>
>
>
> Den sön 12 jan. 2020 19:38Victor Perevertkin 
> skrev:
>
> If somebody will do it, these projects can be used :)
>
> But AFAIK nobody is going to work on graphics anytime soon
>
>
>
> On Sat, Jan 11, 2020 at 10:52 AM Javier Agustìn Fernàndez Arroyo <
> elh...@gmail.com> wrote:
>
> Hello guys,
>
>
>
> Please have a look at this website!
> https://fdossena.com/?p=articles.php?s=1
>
>
>
> Maybe ReactOS can use any of these pieces of FOSS
>
>
>
> what do you think?
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
>
> ___
> Ros-dev mailing 
> listRos-dev@reactos.orghttp://reactos.org/mailman/listinfo/ros-dev
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] wined3d, Mesa for Windows

[Javier Agustìn Fernàndez Arroyo]

Hello guys,

Please have a look at this website! https://fdossena.com/?p=articles.php?s=1

Maybe ReactOS can use any of these pieces of FOSS

what do you think?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] ReactOS 0.4.11 to be released tomorrow, March 4, 2019 - Press Kit is online!

[Javier Agustìn Fernàndez Arroyo]

Who!
Go go go!

El dom., 3 mar. 2019 16:03, Colin Finck  escribió:

> Hi all!
>
> ReactOS 0.4.11 is going to be released tomorrow, Monday, March 4, 2019.
> The download will be officially available around noon (CEST).
>
> A Press Kit for the ReactOS 0.4.11 release is already available:
>
> https://download.reactos.org/reactos/ReactOS/0.4.11/ReactOS-0.4.11-PressKit.zip
> Feel free to send it to interested parties to let them know about the
> upcoming release in advance.
>
>
> Best regards,
>
> Colin Finck
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Fwd: [ReactOS Chat] Notification in ReactOS on March 1, 2019

[Javier Agustìn Fernàndez Arroyo]

They do!

-- Forwarded message -
From: 
Date: vie., 1 mar. 2019 18:30
Subject: [ReactOS Chat] Notification in ReactOS on March 1, 2019
To: 


You have a new notification.

Channel: Town Square
@Colin Finck - 17:30 UTC, March 1

@all Mattermost E-Mail notifications should finally work now :)

Go To Post 
Any questions at all, mail us any time: feedb...@mattermost.com
Best wishes,
The ReactOS Chat Team


To change your notification preferences, log in to your team site and go to
Account Settings > Notifications.
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] CORE-15474 - Make modern BSOD in ReactOS

[Javier Agustìn Fernàndez Arroyo]

Please no... i love NT5 style BSoD
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] CORE-15467 - 1st stage setup freezes when the expected file is missing

[Javier Agustìn Fernàndez Arroyo]

" The freezing you encounter "

well, not me actually. I´m not the informer :). But yeah i agree

On Wed, Dec 19, 2018 at 8:49 PM  wrote:

> ‌Hi,
>
> There is in principle (almost) all the infrastructure to implement the
> Retry/Skip/Abort dialog in usetup.
> The freezing you encounter is however a bug I should investigate.
>
> Cheers,
> Hermes
> De : "Javier Agustìn Fernàndez Arroyo"
> A : "ReactOS Development List"
> Envoyé: mercredi 19 décembre 2018 20:17
> Objet : [ros-dev] CORE-15467 - 1st stage setup freezes when the expected
> file is missing
>
> An idea,
>
> I don´t think its a good idea to "skip" a file during 1st stage, specially
> core files (in 2nd stage it might be acceptable for some device drivers,
> for example)
>
> So, if "cloning" the Win2k3 behavior, i would set only 2 options: retry or
> abort installation and reboot.
>
> what do you guys think?
>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] CORE-15467 - 1st stage setup freezes when the expected file is missing

[Javier Agustìn Fernàndez Arroyo]

An idea,

I don´t think its a good idea to "skip" a file during 1st stage, specially
core files (in 2nd stage it might be acceptable for some device drivers,
for example)

So, if "cloning" the Win2k3 behavior, i would set only 2 options: retry or
abort installation and reboot.

what do you guys think?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] USB meta bug

[Javier Agustìn Fernàndez Arroyo]

hello all,

There are lots of USB related reports, and i´m about creating a master one,
which blocks all of those... what do you think?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] "[shell32] Shell dialog issues" .- CORE-10481

[Javier Agustìn Fernàndez Arroyo]

Are you sure its better to follow Win behavior on this?

I think its a enhancement, specially if there are many open windows at a
given time

it saves time!
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] ReactOS 0.5 Planning

[Javier Agustìn Fernàndez Arroyo]

Before setting 0.5 goals we should finally answer the question: will be 0.5
a beta release?

El vie., 30 nov. 2018 9:30, Colin Finck  escribió:

> Hi all!
>
> Planning the ReactOS 0.5 release and establishing a new roadmap was one
> of the points on the agenda of yesterday's meeting. This is still an
> ongoing process.
>
> Please make up your minds about what a ReactOS 0.5 release must offer in
> your opinion and write it down to https://reactos.org/wiki/0.5.0
>
> To get a realistic roadmap, it is important that we define a responsible
> person for each task. It should be the person having the most in-depth
> knowledge about the status of the affected ReactOS components.
> Don't worry, we won't put any pressure on you to complete the task soon.
> But we need someone who can give a detailed report about the current
> status.
>
> If nobody can be the responsible person for a certain task, having it
> for 0.5 is not realistic and it eventually needs to be removed from the
> roadmap.
> But that's for later! Let's first add all points we consider important
> until the end of the year. If you can already add yourself as the
> responsible person, even better! :)
>
>
> Cheers,
>
> Colin
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Google Summer of Code 2019

[Javier Agustìn Fernàndez Arroyo]

Please, remind me how can I connect to the meeting via web  I'm at work
and I can't use IRC clients here

Thanks

El jue., 29 nov. 2018 17:51,  escribió:

> Hi,
>
> sadly I can't mentor it, but getting the demo Laptop (the Dell D531)
> finally completely running would be _very_ helpfull. I think getting the
> GPU completely running will be a could candidate for GSoC (The drivers
> are already working in a very rough shape). To my last information, the
> driver is blocked by an PnP issue
> (https://jira.reactos.org/browse/CORE-14464) .
>
> There are rather many bug reports of graphic driver problems, so the
> GSoC project could be extended in any way - be it more ATI GPU, trying
> AMD (thus newer) GPUs, or give Intel drivers a try to get the vast
> majority working. NVivida could be worth a try as well.
>
> Best regards,
> Michael Fritscher
>
> P.S. Or should I try to add it to the wiki even despite the fact I will
> not be able to mentor it (because of lack of knowledge) ?
>
> P.P.S. Another idea could be a OS AC97/HDA audio driver or network
> drivers for broadcom/intel/realtek (the latest still existing in a way).
>
> Am 2018-11-29 11:01, schrieb Colin Finck:
> > Hi all!
> >
> > While there is still some time until the February 6, 2019 application
> > deadline for projects, we should already begin planning our GSoC
> > participation now!
> >
> > As today's meeting already has a long agenda, I delibereately didn't
> > add
> > GSoC to it. But I've already created
> > https://reactos.org/wiki/Google_Summer_of_Code_2019 and
> > https://reactos.org/wiki/Google_Summer_of_Code_2019_Ideas
> >
> > Please decide whether you want to be a GSoC org admin or mentor and add
> > your ideas to the list or remove deprecated ones.
> > My experience from the Mentor Summit tells me that proper planning and
> > advertising can make a huge difference for our 2019 participation and
> > will certainly get us more students :)
> >
> >
> > Cheers,
> >
> > Colin
> >
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://reactos.org/mailman/listinfo/ros-dev
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (November 2018)

[Javier Agustìn Fernàndez Arroyo]

let me add a last topic: website translations

Old website could be translated, current one can not. And i think its good
for the final user to see the webpage in his/her own language...

On Thu, Nov 29, 2018 at 10:40 AM Colin Finck  wrote:

> Am 29.11.2018 um 10:28 schrieb Colin Finck:
> > 2. Web and Infrastructure Projects (Victor P. and Colin)
> >=
>
> Addendum to these:
>
>   - Community.ReactOS.org (Colin)
>   - Doxygen (Colin)
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (November 2018)

[Javier Agustìn Fernàndez Arroyo]

i still think a proper driver management is required for beta stage... And
i mean, successful driver installation via installers, and not only via
.inf files

On Wed, Nov 28, 2018 at 6:02 PM Ged Murphy 
wrote:

> The link between 0.5 and beta was an old statement we used to have on our
> website, I’m not sure why that relationship existed other than a splitting
> an integer in half and assigning 0.5 to each stage.
>
> I’m more of the opinion that beta products are close to release, so 0.8+
> would be more suitable.
>
>
>
> Anyway, it’s a conversation to be had internally.
>
>
>
> Ged.
>
>
>
> *From:* Ros-dev  *On Behalf Of *
> hermes.belu...@sfr.fr
> *Sent:* Wednesday, 28 November 2018 16:51
> *To:* ReactOS Development List 
> *Subject:* Re: [ros-dev] Status Meeting (November 2018)
>
>
>
> ‌Hi!
>
> Usually when we talk about ReactOS 0.5, we implicitly think that it will
> enter beta state there.
> So unless you consider this to not completely hold anymore, we can look at
> what remains to be done/fixed (importantly) so that we may qualify as going
> into beta state.
> (And yes, USB and storage sound strongly as prerequisites for 0.5 in my
> opinion).
>
> Best,
> Hermes
>
> De : "Ged Murphy"
> A : "'ReactOS Development List'"
> Envoyé: mercredi 28 novembre 2018 17:42
> Objet : Re: [ros-dev] Status Meeting (November 2018)
>
>
> Some potential talking points:
>
>
>
>- Selecting a new coordinator
>- Version bump to 0.5
>- USB / Storage (perhaps linked to a 0.5 release)
>- Mattermost
>- New website progress
>
>
>
>
>
> *From:* Ros-dev  *On Behalf Of *Mark Jansen
> *Sent:* Wednesday, 28 November 2018 16:13
> *To:* ReactOS Development List 
> *Subject:* Re: [ros-dev] Status Meeting (November 2018)
>
>
>
> We can discuss this if you are present, but I don't see the value in
> discussing it without you.
>
> We have seen before that something discussed without the initiator being
> present is time not well spent, since it is a bit hard to argue with only
> one side of the argument present
>
>
>
>
>
>
>
> Op 26 nov. 2018 12:15 schreef hermes.belu...@sfr.fr:
>
> Hello,
>
> I may not be available as it's the day when I'm going somewhere for a
> conference; it just depends at which time I arrive at destination.
>
> For the meeting we may talk about the best way we can move to delivering
> all-in-one ReactOS ISOs (containing livecd + installation in both text and
> GUI modes), and which changes this could imply for our infrastructure
> (buildbots/website...).
>
> Best regards,
> Hermes
>
> De : "Javier Agustìn Fernàndez Arroyo"
> A : "ReactOS Development List"
> Envoyé: samedi 24 novembre 2018 22:06
> Objet : Re: [ros-dev] Status Meeting (November 2018)
>
>
> I'm at work but I will do my best to attend!
>
>
>
> El sáb., 24 nov. 2018 21:38, Colin Finck  escribió:
>
> Hi all!
>
> Let me invite you to the November 2018 meeting, taking place next
> Thursday, November 29, 2018 at 19:00 UTC.
> Invited members will again receive their credentials shortly before the
> meeting.
>
> This will be the first meeting since August and I hope we get some more
> topics than just the obligatory Status Reports. Please send your
> proposals by replying to this mail.
>
>
> Best regards,
>
> Colin
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
>
>
>
>
>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (November 2018)

[Javier Agustìn Fernàndez Arroyo]

I'm at work but I will do my best to attend!

El sáb., 24 nov. 2018 21:38, Colin Finck  escribió:

> Hi all!
>
> Let me invite you to the November 2018 meeting, taking place next
> Thursday, November 29, 2018 at 19:00 UTC.
> Invited members will again receive their credentials shortly before the
> meeting.
>
> This will be the first meeting since August and I hope we get some more
> topics than just the obligatory Status Reports. Please send your
> proposals by replying to this mail.
>
>
> Best regards,
>
> Colin
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] no replies about making reactos accessible for the blind

[Javier Agustìn Fernàndez Arroyo]

This is not Linux, Windows software can NOT run with no graphics ;)

El mié., 14 nov. 2018 17:36, Dick  escribió:

> of course, you are right. but like in linux, much software can be ran
> headless without graphics.
>
> On Wed, 14 Nov 2018, Erkin Alp Güney wrote:
>
> >> the main problem of screenreaders is they have to find out what
> >> developers had done to make an app accessible. for example, when a
> >> screenreader give access to firefox version 40 that same version will
> >> probably run into problems when running version 60, the screen reader
> >> needs to be updated and adjusted to the changes made in the app.
> >> Reactos is an os built from the ground. what i think would be helpfull
> >> is to do it the other way this time: built functionality into the os
> >> to display just text on braille displays instead of graphics for
> >> example. when the accessibility is fully built into the os updated
> >> apps will have much less influence because the os itself is doing the
> >> tasks needed to make everythign accessible. I think it is a much
> >> harder job to build this into a fully finished os than to include such
> >> features in an os that is still in heavy development.
> >
> > Some software will not work that way because they supply UI not text,
> > just images. That kind of software will not work with screenreaders nor
> > hi-contrast unless it is explicitly programmed for.
> >
> >
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] reactos & debug mode issue

[Javier Agustìn Fernàndez Arroyo]

Hello all,

I have just noticed that ReactOS, when in debug configuration, will only
boot if an output console is set up.

Won't boot if minicom (for example) is not running...

Is that expected?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] reports about Win7+ apps

[Javier Agustìn Fernàndez Arroyo]

@Dick,

Windows XP/2003 is a great target, those were very stable systems, and
ReactOS can perfectly replace them. Software companies dont support them
because lack of maintenance. But ReactOS has that :)



On Mon, Nov 5, 2018 at 1:59 PM Dick  wrote:

> When will reactos be usable for daily use? I think reactos shoulld support
> also windows 7/10 programs, because when it only supports older
> windows-versions you all are in fact building history, something that will
> never be usable for new computers with new software so it would never be
> able to replace windows. I realy hoep the day this project is suitable for
> daily use comes ever, about 20 yers of work without a full functional
> versoin makes me doubt reactos will ever become a fully workign
> replacement for windows. Who knows, maybe everybody had forgoten windows
> in 10 years and everybody uses chrome os. so i hope there is a plan,
> somethign users can expect. a first beta release for example.
> best regards, Dick
>
> On Mon, 5 Nov 2018, David Quintana (gigaherz) wrote:
>
> > Our compatibility layer is very WIP, so reports about those apps would
> be a
> > lot of noise with low value
> >
> > On Mon, 5 Nov 2018, 13:32 Javier Agustìn Fernàndez Arroyo <
> elh...@gmail.com
> > wrote:
> >   hello all,
> > im planning to use ReactOS at a foundation here in Madrid, which is
> > dedicated to people with intellectual disabilities
> >
> > he point is, they are using mostly Windows 10, so they are using Win10
> > apps
> >
> > are bug reports about Win10 apps acceptable?
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> >
> >___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Unused bandwidth at home

[Javier Agustìn Fernàndez Arroyo]

Hello all,

I have just set optical fiber up at my home. The thing is, im completely
sure it will be infra-used

Is there anything in ROS i might do for help with that?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Win8 theme for ReactOS?

[Javier Agustìn Fernàndez Arroyo]

What about a unity-like desktop theme?

El dom., 9 sept. 2018 10:55, Colin Finck  escribió:

> While Hermès' answer is totally correct, let me outline our reasons for
> that.
>
> First of all, you are right that ReactOS needs to work on its outer
> appearance. Many ReactOS developers agree with that and this is also
> what the press criticizes first on each ReactOS release.
>
> However, that problem isn't solved by simply ripping off the Windows 8
> look & feel and violating Microsoft's copyrights in the process.
> ReactOS needs a distinct theme to be memorized as a unique operating
> system and not just a poor copy of Windows.
>
> Besides, GreenteaOS has imported their theme without any information
> about sources and copyrights
> (
> https://github.com/GreenteaOS/Deprecated/commit/1a75a25554427dc79a87a718ac674090bb605523
> )
> and apparently wants no association with ReactOS
> (
> https://github.com/GreenteaOS/Deprecated/commit/74db330786c0ee27bd76cf34a3156cb6b972311e
> ).
> Therefore, the only safe thing for us is staying away from any
> GreenteaOS files as well.
>
> Cheers,
>
> Colin
>
>
> Am 08.09.2018 um 23:58 schrieb Hermès BÉLUSCA-MAÏTO:
> > Please don't include any "GreenteaOS" stuff in ReactOS!!
> >
> > Hermès.
> >
> >> -Message d'origine-
> >> De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de
> theUser BL
> >> Envoyé : samedi 8 septembre 2018 16:54
> >> À : ros-dev@reactos.org
> >> Objet : [ros-dev] Win8 theme for ReactOS?
> >>
> >> A while ago I have asked in the forum, if the modified Lautus-theme of
> >> GreenteaOS could beintegrated in ReactOS
> >> https://www.reactos.org/forum/viewtopic.php?f=2=16788
> >> Sadly the theme is called in GreenteaOS Lautus, too. Here the source of
> it
> >> https://github.com/GreenteaOS/Deprecated/tree/master/third-
> >> party/reactos/media/themes/lautus.msstyles
> >> But it looks like Windows 8.
> >>
> >> Here a screenshot of the Greentea Windows 8 like theme on ReactOS.
> Choose
> >> one link. I have uploaded it multiple times on multiple places, because
> some
> >> picture-uploading-sides delete its files from time to time
> >>
> >> https://image.ibb.co/gTsPkU/Virtual_Box_React_OS_0_4_9_08_09_2018_16_2
> >> 2_18.png
> >> http://img4host.net/upload/081642005b93dfb8c233a.png
> >>
> https://img3.picload.org/image/dlpgdlow/virtualbox_reactos0.4.9_08_09_.png
> >> https://cdn3.imggmi.com/uploads/2018/9/8/e016c5a6842640ac5f7436ee2e9b
> >> 04e7-full.png
> >> https://i.imgur.com/mCUvsLy.png
> >>
> >> EmuandCo is against the integration of the Win8-theme in ReactOS. But
> he is
> >> the only ReactOS-developer in the ReactOS-forum. So I now also ask
> here, what
> >> the other developers thinking about it.
> >>
> >> Greetings
> >> theuserbl
> >> ___
> >> Ros-dev mailing list
> >> Ros-dev@reactos.org
> >> http://www.reactos.org/mailman/listinfo/ros-dev
> >
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Virtual consoles using ntvdm

[Javier Agustìn Fernàndez Arroyo]

A crazy idea ..


What about implementing some kind of virtual consoles, just like Linux? The
point is, using ntvdm subsystem, we could allow only console (DOS) apps to
run in there. And some kind of "you are running a console. Switch to
desktop to run this app!" Message is anyone tried to run another stuff

What do you think?

A side effect could be, allow remote connections, etc ... :)
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Valve support for ReactOS?

[Javier Agustìn Fernàndez Arroyo]

well, yeah, but Wine is user mode. Might Valve help us with our kernel mode
stuff?

On Thu, Aug 30, 2018 at 11:24 AM Robert Naumann  wrote:

> I think that they already have a suitable solution with Wine, spent time
> and money there and their efforts will indirect influence ros with our
> winesyncs
>
> Javier Agustìn Fernàndez Arroyo  schrieb am Do., 30.
> Aug. 2018, 09:20:
>
>> i was thinking about Valve's Linux support (Steam play) and i was
>> wondering about asking them to support ReactOS via development...
>>
>> Since Windows XP/2k3 are being abandoned, maybe ReactOS could still run
>> Steam games... if they support it.
>>
>> what do you think?
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Valve support for ReactOS?

[Javier Agustìn Fernàndez Arroyo]

i was thinking about Valve's Linux support (Steam play) and i was wondering
about asking them to support ReactOS via development...

Since Windows XP/2k3 are being abandoned, maybe ReactOS could still run
Steam games... if they support it.

what do you think?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Discussions on ENIW

[Javier Agustìn Fernàndez Arroyo]

Hell, no! That is a monster, not ReactOS!

El mar., 21 ago. 2018 17:59, Erkin Alp Güney 
escribió:

> Yay, ENIW+ARWINSS would be a great combo? What about GUI programs using
> Wayland?
>
>
> 21-08-2018 18:54 tarihinde Javier Agustìn Fernàndez Arroyo yazdı:
> > And of course, I must remind team about ARWINSS ;)
> >
> > El mar., 21 ago. 2018 17:52, Erkin Alp Güney  > <mailto:erkinalp9...@gmail.com>> escribió:
> >
> > WSL is an optional component, so will ENIW. It will not affect rest
> of
> > ReactOS.
> >
> >
> > 21-08-2018 18:48 tarihinde Javier Agustìn Fernàndez Arroyo yazdı:
> > > Would this break binary compatibility with MS OSes?
> > >
> > Yours, faithfully
> > Erkin Alp
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org <mailto:Ros-dev@reactos.org>
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> >
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Discussions on ENIW

[Javier Agustìn Fernàndez Arroyo]

And of course, I must remind team about ARWINSS ;)

El mar., 21 ago. 2018 17:52, Erkin Alp Güney 
escribió:

> WSL is an optional component, so will ENIW. It will not affect rest of
> ReactOS.
>
>
> 21-08-2018 18:48 tarihinde Javier Agustìn Fernàndez Arroyo yazdı:
> > Would this break binary compatibility with MS OSes?
> >
> Yours, faithfully
> Erkin Alp
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Discussions on ENIW

[Javier Agustìn Fernàndez Arroyo]

I remember an old discussion about porting alsa drivers to ROS, but that
would be a monster xd and project ains to "clone" every single Win
behaviours

El mar., 21 ago. 2018 17:48, Javier Agustìn Fernàndez Arroyo <
elh...@gmail.com> escribió:

> Would this break binary compatibility with MS OSes?
>
> El mar., 21 ago. 2018 17:46, Erkin Alp Güney 
> escribió:
>
>> |My proposed architecture diagram for ENIW: Linux app systemd <>
>> systemd2svchost Windows userland -- User-mode Linux kernel ---
>> SVCHOST Windows services ENIW.SYS Windows personalities Kernel-mode
>> drivers for everything -- NTOSKRNL.EXE
>> --- ENIW is a component to implement
>> WSL-like functionality named after WINE and its bacronym is ENIW never
>> imitated WSL. systemd2svchost is a service translator to run systemd
>> units as svchost services. Forum thread:
>> <https://www.reactos.org/forum/viewtopic.php?f=9=17434> JIRA ticket:
>> <https://jira.reactos.org/browse/CORE-13613> Yours, faihfully Erkin Alp |
>>
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Discussions on ENIW

[Javier Agustìn Fernàndez Arroyo]

Would this break binary compatibility with MS OSes?

El mar., 21 ago. 2018 17:46, Erkin Alp Güney 
escribió:

> |My proposed architecture diagram for ENIW: Linux app systemd <>
> systemd2svchost Windows userland -- User-mode Linux kernel ---
> SVCHOST Windows services ENIW.SYS Windows personalities Kernel-mode
> drivers for everything -- NTOSKRNL.EXE
> --- ENIW is a component to implement
> WSL-like functionality named after WINE and its bacronym is ENIW never
> imitated WSL. systemd2svchost is a service translator to run systemd
> units as svchost services. Forum thread:
>  JIRA ticket:
>  Yours, faihfully Erkin Alp |
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (June 2018)

[Javier Agustìn Fernàndez Arroyo]

Err... Do you know any Android irc client?

El jue., 28 jun. 2018 18:32, Colin Finck  escribió:

> Credentials have been sent, please check your inboxes!
>
> Colin
>
>
> Am 24.06.2018 um 10:59 schrieb Colin Finck:
> > Hi all!
> >
> > Let me invite you to the June 2018 meeting, taking place this Thursday,
> > June 28, 2018 at 19:00 UTC.
> > Invited members will again receive their credentials shortly before the
> > meeting.
> >
> > The current agenda is:
> >
> >1. Status Reports
> >2. ReactOS Hackfest on August 16 - 21
> >3. 0.4.9 release on July 14
> >
> > I'm open for additional proposals.
> >
> > Best regards,
> >
> > Colin
> >
> >
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Announcing the ReactOS Hackfest 2018 in Berlin

[Javier Agustìn Fernàndez Arroyo]

i got a wedding these dates :(
shit!

On Wed, Jun 6, 2018 at 12:24 PM, Colin Finck  wrote:

> Hi all!
>
> It's official now! The ReactOS Hackfest 2018 will take place from
> Thursday, 16th August 2018 to Tuesday, 21st August 2018 in Berlin, Germany.
>
> Thanks to Thomas, the event location is already checked out ("definitely
> more space than in Cologne") and he has found a hostel nearby.
> All information can be found at
> https://reactos.org/wiki/ReactOS_Hackfest_2018, with the lists for
> registering yourself and collecting ideas at
> https://reactos.org/wiki/ReactOS_Hackfest_2018/Lists
>
> Hope to see you in August!
>
>
> Cheers,
>
> Colin
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Microsoft acquires GitHub

[Javier Agustìn Fernàndez Arroyo]

i'm thinking on setting some server up at my home if you need anything,
tell me :)

On Tue, Jun 5, 2018 at 10:02 PM, Oleksandr Shaposhnikov <
sanch...@reactos.org> wrote:

> > Plus, like people said, its decentralized. If they suddenly go nuts and
> > delete everything, you can just, though its a major PITA, just upload a
> > copy of the repo to a new server and change url's. If you want to be
> > paranoid about it, have a domain name that just aliases to github and
> then
> > if shit hits the fan point it elsewhere.
>
> Do you know we have git.reactos.org?
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Microsoft acquires GitHub

[Javier Agustìn Fernàndez Arroyo]

great! :)

On Tue, Jun 5, 2018 at 10:34 AM, Thomas Faber 
wrote:

> To elaborate, we're not dependent on GitHub in any significant way. It's
> just convenient. But if it stops being so, it's easy to go elsewhere.
> That's a key part of Git, being a "distributed" VCS.
>
>
> On 2018-06-05 10:31, Oleksandr Shaposhnikov wrote:
> > No it may not.
> >
> > 5 черв. 2018 р. 11:24 Javier Agustìn Fernàndez Arroyo 
> пише:
> >
> >  May this affect ReactOS?
> >
> >  https://blogs.microsoft.com/blog/2018/06/04/microsoft-
> github-empowering-developers/
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Microsoft acquires GitHub

[Javier Agustìn Fernàndez Arroyo]

May this affect ReactOS?

https://blogs.microsoft.com/blog/2018/06/04/microsoft-github-empowering-developers/
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] "Note: LibreOffice 5.4 will be the last codeline tosupport Windows XP or Vista"

[Javier Agustìn Fernàndez Arroyo]

hello again guys,

What if we get latest NT5 libreoffice version (5.4.6 as of now, and
5.4.7-rc1 is out) just for testing purposes? i guess it will be dropped
from official website, andi don´t know if it will be still available in any
way..

On Sat, Jul 1, 2017 at 9:29 AM, Michael Fritscher <mich...@fritscher.net>
wrote:

> Hi,
>
> is there a list which need to be done to get the basic NT6 architecture
> just to get feeling how much work it is? Sadly, I'm afraid that we'll
> need a proper NT6 architecture to get modern drivers running, won't we?
>
> Best regards,
> Michael Fritscher
>
> On 30.06.2017 11:46, Ged Murphy wrote:
> > That’s what’s currently being worked on.
> >
> > The kernel still closely follows the NT5.2 architecture, but user mode
> will have NT6+ compatibility shims to allow modern applications to run
> correctly.
> >
> >
> >
> > From: Ros-dev [mailto:ros-dev-boun...@reactos.org] On Behalf Of
> ajac...@yahoo.es
> > Sent: 30 June 2017 05:47
> > To: ReactOS Development List <ros-dev@reactos.org>
> > Subject: Re: [ros-dev] "Note: LibreOffice 5.4 will be the last codeline
> tosupport Windows XP or Vista"
> >
> >
> >
> > I think it’s no neccesary to implement NT6, only to avoid the
> compatibility tests to NT6 and implement only the characteristics that the
> most of the programs uses.
> >
> >
> >
> > Best regards
> >
> > Antonio J. Arrieta Cuartero
> >
> >
> >
> > Enviado desde mi Lumia 635 con Windows 10 Mobile
> >
> >
> >
> > De: Riccardo Paolo Bestetti <mailto:riccardo.kyo...@live.it>
> > Enviado: jueves, 29 de junio de 2017 22:11
> > Para: ReactOS Development List <mailto:ros-dev@reactos.org>
> > Asunto: Re: [ros-dev] "Note: LibreOffice 5.4 will be the last codeline
> tosupport Windows XP or Vista"
> >
> >
> >
> > Hello Colin,
> >
> > As this definitely wasn't the predominant thinking the last time this
> same discussion took place, Hermès' email scared me a bit. Thank you so
> much for clarifying.
> >
> >
> >
> > Best regards,
> >
> > Riccardo Paolo Bestetti
> >
> >
> >
> > -Original Message-
> >
> > From: Ros-dev [mailto:ros-dev-boun...@reactos.org] On Behalf Of Colin
> Finck
> >
> > Sent: giovedì 29 giugno 2017 20:00
> >
> > To: ros-dev@reactos.org <mailto:ros-dev@reactos.org>
> >
> > Subject: Re: [ros-dev] "Note: LibreOffice 5.4 will be the last codeline
> to support Windows XP or Vista"
> >
> >
> >
> > Rest assured, we know that ReactOS won't be of much use if we stay
> NT5-only. Work is underway to provide a seamless support of NT6
> applications on top of the existing codebase.
> >
> > Also the majority of developers should be using an NT6 platform
> themselves, so they certainly aim for support for NT6 applications.
> >
> > Finally, applications compiled by modern versions of Visual Studio are
> NT6-only by default, so supporting this platform is unavoidable.
> >
> >
> >
> > Just my two cents, as the previous replies could lead you to believe
> we're failing the reality check.
> >
> >
> >
> > Cheers,
> >
> >
> >
> > Colin
> >
> >
> >
> >
> >
> > Am 29.06.2017 um 18:54 schrieb Riccardo Paolo Bestetti:
> >
> >> I’m just gonna snap in for my yearly IT guy NT6 rant: this mindset is
> >
> >> going to kill the project by making it useless whenever it reaches a
> >
> >> usable state.
> >
> >>
> >
> >> Windows XP/Server 2003 use is **already** marginal as of today, and
> >
> >> it’s only gonna get “worse” as more and more networks get infected by
> >
> >> ransomware and institutions all over the world wake up and update (and
> >
> >> as time passes of course). It’s not a matter of “fancy”, it is a
> >
> >> matter of what people use on their computers. With that argument you
> >
> >> may as well advocate for DOS.
> >
> >>
> >
> >>
> >
> >>
> >
> >> Please don’t be offended, as always this is only intended as a reality
> >
> >> check.
> >
> >>
> >
> >>
> >
> >>
> >
> >> Best regards,
> >
> >>
> >
> >> Riccardo Paolo Bestetti
> >
> >>
> >
> >>
> >
> >>
> >
> >> *From:*Ros-dev [mail

[ros-dev] logon sound remaked

[Javier Agustìn Fernàndez Arroyo]

did you guys hear this? :)

https://www.youtube.com/watch?v=xO5T5d4AmYo
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Making bluescreens more useful

[Javier Agustìn Fernàndez Arroyo]

i like the QR thing. But, take in mind that we will need some kind of
decoder into JIRA, website, or wherever, so that they are easily
uploadable/reportable

On Sat, Jan 13, 2018 at 12:41 PM, Amine Khaldi 
wrote:

> I like it. I recently thought about another possibility to make the BSOD
>> more useful: A QR code.
>> A QR code can contain up to almost 3 KB of arbitrary data or 4 KB text.
>>
> As our friends at Haiku have already implemented something like this ages
> ago, it would be nice to finally have this in ReactOS too :)
>
> https://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output/
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] First NT6+ application support in ReactOS

[Javier Agustìn Fernàndez Arroyo]

errr... sorry, but ReactOS is still barely installable on Real
Hardware, with (i would say) a great lack on driver support... and you´re
thinking about NT6+???

Yes, its good news, no doubt about it! but... is it a priority?

Now you can ban me if you wish :P

On Wed, Jan 10, 2018 at 11:01 AM, 7th Element <7elem...@mail.bg> wrote:

> Wow,
>
> Awesome work!!!
> Keep up the good work and give us more news like this!
>
> BR,
> Peter
>
> > On 10 Jan 2018, at 11:05, Colin Finck  wrote:
> >
> > Hi all!
> >
> > Starting with build 0.4.8-dev-655-g63a3a2c, ReactOS has first support
> > for NT6+ applications (aka programs written for Windows Vista, Windows
> > 7, etc.). Please retest such applications under ReactOS!
> >
> > As newer Windows APIs are still missing in ReactOS, I would be surprised
> > if a high number of NT6+ applications suddenly works.
> > However, many applications may just be compiled by a new Visual Studio
> > without using any modern APIs. They could work now.
> >
> > My "Hello World" compiled by VS 2017 v141 toolchain printed many
> > messages about missing apiset DLLs in the debug log, but otherwise works
> > well. So the next step should obviously be finishing and integrating
> > Mark's work on the apiset DLLs in
> > https://github.com/learn-more/reactos/commits/apisets
> > But interestingly, the build produced by the v141_xp toolchain also
> > looks for these apiset DLLs. Therefore, it would be possible that an
> > application expects a full NT6 system when finding them. Consequently,
> > application compatibility could be compromised if we just dump all
> > apiset DLLs into ReactOS, applications now expect NT6, but the OS
> > continues to behave like NT5 by default.
> >
> > This is why I suggest detecting an NT6+ application in ntdll to have it
> > auto-apply a shim that lets ReactOS behave like an NT6 OS. The apiset
> > DLLs should only be available in this mode, but not for the NT5
> > personality of ReactOS. Let's not import the apisets before the ntdll
> > shim work is done in order to preserve our existing application
> > compatibility.
> >
> >
> > Cheers,
> >
> > Colin
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Creative sound cards drivers

[Javier Agustìn Fernàndez Arroyo]

hwy guys, did you hear about this? Maybe toese can be included with
ReactOS, they are open source!

https://github.com/kxproject

http://kxproject.com/index.php?language=en
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Project-tools repository converted to Git - Welcome our 18 new repos!

[Javier Agustìn Fernàndez Arroyo]

Happy new year to you everyone!

El 31 dic. 2017 19:31, "Javier Agustìn Fernàndez Arroyo" <elh...@gmail.com>
escribió:

> GitHub is going to Drive me crazy lol
>
> El 31 dic. 2017 18:46, "David Quintana (gigaherz)" <gigah...@gmail.com>
> escribió:
>
>> Really nice way to end the year :D
>>
>> On 31 December 2017 at 18:11, Colin Finck <co...@reactos.org> wrote:
>>
>>> Hi all,
>>>
>>> I just finished converting our "project-tools" SVN repo to Git and
>>> splitting it up into individual repositories in the process.
>>> These repos have already been uploaded to GitHub
>>> (https://github.com/reactos), so you can have a look and comment easily.
>>> Welcome these 18 new repositories:
>>>
>>> * ahk_tests
>>> * buildbot_config
>>> * git-tools
>>> * irc
>>> * Message_Translator
>>> * monitoring
>>> * packmgr (Archived)
>>> * project-tools-archive (Archived)
>>> * Qemu_GUI
>>> * reactosdbg
>>> * Release_Engineering
>>> * RosBE
>>> * rosev_ircsystem
>>> * rosev_jameicaplugin
>>> * RosTE
>>> * sysreg2
>>> * sysreg3 (Archived)
>>> * vmwaregateway
>>>
>>> I haven't given anyone write access yet. I think this is acceptable for
>>> the moment while we check if there are any outstanding issues with the
>>> conversion.
>>> Please let me know until January 7. If everything is okay by then, I
>>> will add write access again and officially move development away from
>>> the project-tools SVN repo.
>>>
>>>
>>> Have a good start into 2018!
>>>
>>> Colin
>>>
>>> ___
>>> Ros-dev mailing list
>>> Ros-dev@reactos.org
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>>
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Project-tools repository converted to Git - Welcome our 18 new repos!

[Javier Agustìn Fernàndez Arroyo]

GitHub is going to Drive me crazy lol

El 31 dic. 2017 18:46, "David Quintana (gigaherz)" 
escribió:

> Really nice way to end the year :D
>
> On 31 December 2017 at 18:11, Colin Finck  wrote:
>
>> Hi all,
>>
>> I just finished converting our "project-tools" SVN repo to Git and
>> splitting it up into individual repositories in the process.
>> These repos have already been uploaded to GitHub
>> (https://github.com/reactos), so you can have a look and comment easily.
>> Welcome these 18 new repositories:
>>
>> * ahk_tests
>> * buildbot_config
>> * git-tools
>> * irc
>> * Message_Translator
>> * monitoring
>> * packmgr (Archived)
>> * project-tools-archive (Archived)
>> * Qemu_GUI
>> * reactosdbg
>> * Release_Engineering
>> * RosBE
>> * rosev_ircsystem
>> * rosev_jameicaplugin
>> * RosTE
>> * sysreg2
>> * sysreg3 (Archived)
>> * vmwaregateway
>>
>> I haven't given anyone write access yet. I think this is acceptable for
>> the moment while we check if there are any outstanding issues with the
>> conversion.
>> Please let me know until January 7. If everything is okay by then, I
>> will add write access again and officially move development away from
>> the project-tools SVN repo.
>>
>>
>> Have a good start into 2018!
>>
>> Colin
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [reactos] 01/01: [SETUP] Remove FSDs which have broken dismount implementation. This avoids issues when these partitions are formatted to FAT for setup.

[Javier Agustìn Fernàndez Arroyo]

7h Element,

Re-read yourself ;)

" for all supported FSs"

Of course. But, according to subject, these are not fully supported, as
they has "issues when these partitions are formatted to FAT for setup"

:)

On Mon, Dec 18, 2017 at 3:19 PM, 7th Element <7elem...@mail.bg> wrote:

> Btrfs is quite active as a project and limiting 1st stage to be able to
> handle only FAT is not OK from my PoV.
> My personal opinion is that we should allow read for all supported FSs for
> reading files (in 1st stage setup) and _definately_ include all FSs that
> support writing and formatting (like btrfs and extX).
> I understand the reasons for the change, I just don’t like the way it is
> handled.
> Pierre is quite experience developer and I just wanted to ask if he
> thought of all implications of the change, nothing else.
> We all sometimes make a change without looking at all angles.
> Hope this doesn’t offend anyone.
>
> BR,
> Peter
>
> On 18 Dec 2017, at 12:57, David Quintana (gigaherz) <gigah...@gmail.com>
> wrote:
>
> That's exactly what this does: it disables them from the cd, but not from
> the final installation. The drivers are still included in reactos!
>
> On 18 December 2017 at 11:53, Javier Agustìn Fernàndez Arroyo <
> elh...@gmail.com> wrote:
>
>> isn´t better just disable them instead of remove?
>>
>> On Mon, Dec 18, 2017 at 10:30 AM, David Quintana (gigaherz) <
>> gigah...@gmail.com> wrote:
>>
>>> So in the future, when we DO want to support them in the setup program,
>>> we'll need to implement dismounting in those drivers, and then they can be
>>> added back to the cd.
>>>
>>> On 18 December 2017 at 10:25, 7th Element <7elem...@mail.bg> wrote:
>>>
>>>> We don’t have them at the moment, but we hope for the future. This will
>>>> also limit formatting partitions. If you want to setup your hdd with
>>>> several FSs (like you usually do on Linux for example) and then install on
>>>> one of them, or want to read some files (drivers) from such supported 
>>>> FSs...
>>>>
>>>> BR,
>>>> Peter
>>>>
>>>> On 18 Dec 2017, at 11:08, David Quintana (gigaherz) <gigah...@gmail.com>
>>>> wrote:
>>>>
>>>> We can't boot from those FSs either way, since we don't have boot
>>>> sectors for them. This only affects the ability for the setup program to
>>>> access those partitions and format them.
>>>>
>>>> On 18 December 2017 at 10:02, 7th Element <7elem...@mail.bg> wrote:
>>>>
>>>>> Hi Pierre,
>>>>>
>>>>> Isn’t this change going to remove ability to boot from those FSs?
>>>>>
>>>>> BR,
>>>>> Peter
>>>>>
>>>>> > On 18 Dec 2017, at 0:16, Pierre Schweitzer <pie...@reactos.org>
>>>>> wrote:
>>>>> >
>>>>> > https://git.reactos.org/?p=reactos.git;a=commitdiff;h=806cd1
>>>>> 6328799771b89397f5c51a3d46884bce0a
>>>>> >
>>>>> > commit 806cd16328799771b89397f5c51a3d46884bce0a
>>>>> > Author: Pierre Schweitzer <pie...@reactos.org>
>>>>> > AuthorDate: Sun Dec 17 23:13:56 2017 +0100
>>>>> >
>>>>> >[SETUP] Remove FSDs which have broken dismount implementation.
>>>>> >This avoids issues when these partitions are formatted to FAT for
>>>>> setup.
>>>>> >
>>>>> >For now, this commit doesn't change anything, but once
>>>>> IopParseDevice hack
>>>>> >gets removed, this will make a difference!
>>>>> >
>>>>> >CORE-6305
>>>>> > ---
>>>>> > boot/bootdata/txtsetup.sif   | 2 --
>>>>> > drivers/filesystems/btrfs/CMakeLists.txt | 2 +-
>>>>> > drivers/filesystems/ntfs/CMakeLists.txt  | 2 +-
>>>>> > 3 files changed, 2 insertions(+), 4 deletions(-)
>>>>> >
>>>>> > diff --git a/boot/bootdata/txtsetup.sif b/boot/bootdata/txtsetup.sif
>>>>> > index 3ea62974b5..822c19c8c8 100644
>>>>> > --- a/boot/bootdata/txtsetup.sif
>>>>> > +++ b/boot/bootdata/txtsetup.sif
>>>>> > @@ -52,7 +52,6 @@ usbstor.sys=,,x,,4
>>>>> > kbdhid.sys=4
>>>>> > kbdclass.sys=,,x,,4
>>>>> > l_intl.nls=2

Re: [ros-dev] [ros-diffs] [reactos] 01/01: [SETUP] Remove FSDs which have broken dismount implementation. This avoids issues when these partitions are formatted to FAT for setup.

[Javier Agustìn Fernàndez Arroyo]

isn´t better just disable them instead of remove?

On Mon, Dec 18, 2017 at 10:30 AM, David Quintana (gigaherz) <
gigah...@gmail.com> wrote:

> So in the future, when we DO want to support them in the setup program,
> we'll need to implement dismounting in those drivers, and then they can be
> added back to the cd.
>
> On 18 December 2017 at 10:25, 7th Element <7elem...@mail.bg> wrote:
>
>> We don’t have them at the moment, but we hope for the future. This will
>> also limit formatting partitions. If you want to setup your hdd with
>> several FSs (like you usually do on Linux for example) and then install on
>> one of them, or want to read some files (drivers) from such supported FSs...
>>
>> BR,
>> Peter
>>
>> On 18 Dec 2017, at 11:08, David Quintana (gigaherz) 
>> wrote:
>>
>> We can't boot from those FSs either way, since we don't have boot sectors
>> for them. This only affects the ability for the setup program to access
>> those partitions and format them.
>>
>> On 18 December 2017 at 10:02, 7th Element <7elem...@mail.bg> wrote:
>>
>>> Hi Pierre,
>>>
>>> Isn’t this change going to remove ability to boot from those FSs?
>>>
>>> BR,
>>> Peter
>>>
>>> > On 18 Dec 2017, at 0:16, Pierre Schweitzer  wrote:
>>> >
>>> > https://git.reactos.org/?p=reactos.git;a=commitdiff;h=806cd1
>>> 6328799771b89397f5c51a3d46884bce0a
>>> >
>>> > commit 806cd16328799771b89397f5c51a3d46884bce0a
>>> > Author: Pierre Schweitzer 
>>> > AuthorDate: Sun Dec 17 23:13:56 2017 +0100
>>> >
>>> >[SETUP] Remove FSDs which have broken dismount implementation.
>>> >This avoids issues when these partitions are formatted to FAT for
>>> setup.
>>> >
>>> >For now, this commit doesn't change anything, but once
>>> IopParseDevice hack
>>> >gets removed, this will make a difference!
>>> >
>>> >CORE-6305
>>> > ---
>>> > boot/bootdata/txtsetup.sif   | 2 --
>>> > drivers/filesystems/btrfs/CMakeLists.txt | 2 +-
>>> > drivers/filesystems/ntfs/CMakeLists.txt  | 2 +-
>>> > 3 files changed, 2 insertions(+), 4 deletions(-)
>>> >
>>> > diff --git a/boot/bootdata/txtsetup.sif b/boot/bootdata/txtsetup.sif
>>> > index 3ea62974b5..822c19c8c8 100644
>>> > --- a/boot/bootdata/txtsetup.sif
>>> > +++ b/boot/bootdata/txtsetup.sif
>>> > @@ -52,7 +52,6 @@ usbstor.sys=,,x,,4
>>> > kbdhid.sys=4
>>> > kbdclass.sys=,,x,,4
>>> > l_intl.nls=2
>>> > -ntfs.sys=4
>>> > pci.sys=4
>>> > scsiport.sys=,,x,,4
>>> > storport.sys=,,x,,4
>>> > @@ -69,7 +68,6 @@ ntdll.dll=2
>>> > wmilib.sys=4
>>> > ksecdd.sys=4
>>> > mountmgr.sys=,,x,,4
>>> > -btrfs.sys=,,x,,4
>>> > reiserfs.sys=,,x,,4
>>> > ffs.sys=,,x,,4
>>> > udfs.sys=,,x,,4
>>> > diff --git a/drivers/filesystems/btrfs/CMakeLists.txt
>>> b/drivers/filesystems/btrfs/CMakeLists.txt
>>> > index 65e61d255a..123c9f0522 100644
>>> > --- a/drivers/filesystems/btrfs/CMakeLists.txt
>>> > +++ b/drivers/filesystems/btrfs/CMakeLists.txt
>>> > @@ -41,4 +41,4 @@ add_definitions(-D__KERNEL__)
>>> > set_module_type(btrfs kernelmodedriver)
>>> > target_link_libraries(btrfs rtlver ntoskrnl_vista zlib_solo wdmguid
>>> ${PSEH_LIB})
>>> > add_importlibs(btrfs ntoskrnl hal)
>>> > -add_cd_file(TARGET btrfs DESTINATION reactos/system32/drivers NO_CAB
>>> FOR all)
>>> > +add_cd_file(TARGET btrfs DESTINATION reactos/system32/drivers FOR all)
>>> > diff --git a/drivers/filesystems/ntfs/CMakeLists.txt
>>> b/drivers/filesystems/ntfs/CMakeLists.txt
>>> > index 0b1af78947..5a193b449d 100644
>>> > --- a/drivers/filesystems/ntfs/CMakeLists.txt
>>> > +++ b/drivers/filesystems/ntfs/CMakeLists.txt
>>> > @@ -25,4 +25,4 @@ set_module_type(ntfs kernelmodedriver)
>>> > target_link_libraries(ntfs ${PSEH_LIB})
>>> > add_importlibs(ntfs ntoskrnl hal)
>>> > add_pch(ntfs ntfs.h SOURCE)
>>> > -add_cd_file(TARGET ntfs DESTINATION reactos/system32/drivers NO_CAB
>>> FOR all)
>>> > +add_cd_file(TARGET ntfs DESTINATION reactos/system32/drivers FOR all)
>>> >
>>> >
>>>
>>>
>>> ___
>>> Ros-dev mailing list
>>> Ros-dev@reactos.org
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] PineappleFund

[Javier Agustìn Fernàndez Arroyo]

well, i dont know if BTC can actually be used as of today but its a
good start

On Wed, Dec 13, 2017 at 9:40 PM, Alexander Rechitskiy 
wrote:

> Donating $1 million to the EFF, defending rights and privacy of internet
> users, fighting for net neutrality, and far far more
>
> https://www.reddit.com/r/Bitcoin/comments/7jj0oa/im_donating_5057_btc_to_
> charitable_causes/
>
> 13.12.2017, 22:58, "David Quintana (gigaherz)" :
>
> We are not a charity, though...
>
> On 13 December 2017 at 20:52, Alexander Shaposhnikov  > wrote:
>
> Hi all!
> Recenly a new Reddit post came up on #reactos IRC:
> https://redd.it/7jj0oa. Interesting stuff.
>
> A person is giving away ~5000 BTC for charitable causes. We can apply
> via the website but it must be done by someone from ReactOS e.V.
>
> --
> Cheers,
> Alexander Shaposhnikov
>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> ,
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> --
> Best regards,
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Merging our x86 HALs

[Javier Agustìn Fernàndez Arroyo]

"supporting very old hardware, which I see as a plain and simple waste of
resources."
I completely disagree.

Supporting very old hardware  means that it will consume very very fewer
resources in very new hardware, too.
But, speaking about the former, it would be wonderful to be able to run
Windows software in such hardware.

The question in this last case is, how HAL supports new CPU instructions?
but that`s an off-topic question

On Wed, Dec 13, 2017 at 8:24 AM, Riccardo Paolo Bestetti <
riccardo.kyo...@live.it> wrote:

> Hi David,
>
>
>
> I was talking about supporting very old hardware, which I see as a plain
> and simple waste of resources. There may be legacy computers running legacy
> software around, but you can be sure that no one is gonna redeploy these
> computer, especially with a different software configuration (i.e.
> installing ReactOS instead of Windows [2000|XP|2003] on it). Of course I
> leave the (very) technical discussion about how to implement HALs to you.
>
>
>
> BR.
>
> *Riccardo P. Bestetti*
>
>
>
> *From:* Ros-dev [mailto:ros-dev-boun...@reactos.org] *On Behalf Of *David
> Quintana (gigaherz)
> *Sent:* martedì 12 dicembre 2017 22:45
>
> *To:* ReactOS Development List <ros-dev@reactos.org>
> *Subject:* Re: [ros-dev] Merging our x86 HALs
>
>
>
> I think yes, on the fact that duplicate code is already causing bugs. Now
> wether we want to unify everything into one megaHAL, or compile multiple
> HALs fom the same codebase, or merge into two medium-sized HALs, that's
> what the discussion is meant to be about.
>
>
>
> On 12 December 2017 at 22:00, Riccardo Paolo Bestetti <
> riccardo.kyo...@live.it> wrote:
>
> My bi-annual IT guy peak:
>
>
>
> Is there a real need to?
>
> I think not.
>
>
>
> B.R.
>
> *Riccardo P. Bestetti*
>
>
>
> *From:* Ros-dev [mailto:ros-dev-boun...@reactos.org] *On Behalf Of *Javier
> Agustìn Fernàndez Arroyo
> *Sent:* martedì 12 dicembre 2017 18:13
> *To:* ReactOS Development List <ros-dev@reactos.org>
> *Subject:* Re: [ros-dev] Merging our x86 HALs
>
>
>
> Win8 does not support old hardware as ReactOS do!
>
>
>
> El 12 dic. 2017 17:52, "Alex Ionescu" <ion...@videotron.ca> escribió:
>
> I would move to the Win8+ HAL Model -- a single HAL for APIC, ACPI with
> runtime support for UEFI (if present) and MP (if present).
>
>
>
> If people still want to run on a PIC VM (why???) or old computer, then we
> can also maintain the HAL PIC x86 for UP.
>
>
>
> Hence there would only be 2 HALs.
>
>
> Best regards,
> Alex Ionescu
>
>
>
> On Mon, Dec 11, 2017 at 1:07 AM, Colin Finck <co...@reactos.org> wrote:
>
> Am 11.12.2017 um 01:18 schrieb Hermès BÉLUSCA-MAÏTO:> If you basically
> put all the HALs into one, then you obtain bloated stuff (which remains
> in memory for the whole life of the OS). Example: standard HAL is 1MB
> vs. ACPI HAL which is few kBHave you actually checked what makes up this
> difference?
> Hint: hal/halx86/legacy/bus/pci_vendors.ids
>
>
> > Note that if Windows nowadays has only one hal, it's because they now
> support basically only one "architecture"/platform, namely, ACPI
> multiprocessor (to put it simple). It has its pros, but also a lot of cons.
>
> That doesn't mean we need to do the same. We can have one HAL for all
> (Pentium and newer) x86 platforms. The overhead of additional checks at
> boot-up is negligible. That should be a solution for 99% of the people
> out there. The rest may still go and trim down our HAL to their needs.
>
> But let's not pretend we can maintain multiple x86 HALs for all x86
> computers out there. Do you really want to test X HALs with Y different
> systems? Ensure that a legacy HAL runs on a modern ACPI system? What
> would be the point?
>
>
> > Besides this, I've a question about your observation that in the APIC
> hal (not ACPI) there's different implementation of
> HalpCalibrateStallExecution and HalpInitializePICs /
> HalpInitializeLegacyPIC . Isn't it precisely because these stuff are
> completely different from the standard PICs used in platforms for which the
> standard HAL (and possibly the ACPI HAL) are used?
>
> Absolutely not! You need to reprogram the standard PICs also on an APIC
> system, and this is precisely what both functions do. Put them into a
> diff tool to see for yourself.
>
> The same goes for timers. Even with the introduction of ACPI Timers,
> Local APIC Timers, and Time-Stamp Counters, you still need a traditional
> one (like RTC or PIT) for calibration at system startup. Simply because
> the newer ones don't run at a known fixed freq

Re: [ros-dev] Merging our x86 HALs

[Javier Agustìn Fernàndez Arroyo]

i know you probably  can't answer, but
where is the ninja group? xD

On Tue, Dec 12, 2017 at 7:06 PM, Thomas Faber <thomas.fa...@reactos.org>
wrote:

> Now the only problem is that neither our APIC nor MP HAL actually
> work...
>
>
>
> On 2017-12-12 18:31, David Quintana (gigaherz) wrote:
>
>> I have to agree that reducing it to 2 HALs (one ACPI with multiprocessor
>> and such, that maybe is also used for single-cpu systems with ACPI), and a
>> legacy one for systems unable to handle ACPI+MP, sounds like a great idea.
>>
>> On 12 December 2017 at 18:13, Javier Agustìn Fernàndez Arroyo <
>> elh...@gmail.com> wrote:
>>
>> Win8 does not support old hardware as ReactOS do!
>>>
>>> El 12 dic. 2017 17:52, "Alex Ionescu" <ion...@videotron.ca> escribió:
>>>
>>> I would move to the Win8+ HAL Model -- a single HAL for APIC, ACPI with
>>>> runtime support for UEFI (if present) and MP (if present).
>>>>
>>>> If people still want to run on a PIC VM (why???) or old computer, then
>>>> we
>>>> can also maintain the HAL PIC x86 for UP.
>>>>
>>>> Hence there would only be 2 HALs.
>>>>
>>>> Best regards,
>>>> Alex Ionescu
>>>>
>>>> On Mon, Dec 11, 2017 at 1:07 AM, Colin Finck <co...@reactos.org> wrote:
>>>>
>>>> Am 11.12.2017 um 01:18 schrieb Hermès BÉLUSCA-MAÏTO:> If you basically
>>>>> put all the HALs into one, then you obtain bloated stuff (which remains
>>>>> in memory for the whole life of the OS). Example: standard HAL is 1MB
>>>>> vs. ACPI HAL which is few kBHave you actually checked what makes up
>>>>> this
>>>>> difference?
>>>>> Hint: hal/halx86/legacy/bus/pci_vendors.ids
>>>>>
>>>>>
>>>>> Note that if Windows nowadays has only one hal, it's because they now
>>>>>>
>>>>> support basically only one "architecture"/platform, namely, ACPI
>>>>> multiprocessor (to put it simple). It has its pros, but also a lot of
>>>>> cons.
>>>>>
>>>>> That doesn't mean we need to do the same. We can have one HAL for all
>>>>> (Pentium and newer) x86 platforms. The overhead of additional checks at
>>>>> boot-up is negligible. That should be a solution for 99% of the people
>>>>> out there. The rest may still go and trim down our HAL to their needs.
>>>>>
>>>>> But let's not pretend we can maintain multiple x86 HALs for all x86
>>>>> computers out there. Do you really want to test X HALs with Y different
>>>>> systems? Ensure that a legacy HAL runs on a modern ACPI system? What
>>>>> would be the point?
>>>>>
>>>>>
>>>>> Besides this, I've a question about your observation that in the APIC
>>>>>>
>>>>> hal (not ACPI) there's different implementation of
>>>>> HalpCalibrateStallExecution and HalpInitializePICs /
>>>>> HalpInitializeLegacyPIC . Isn't it precisely because these stuff are
>>>>> completely different from the standard PICs used in platforms for
>>>>> which the
>>>>> standard HAL (and possibly the ACPI HAL) are used?
>>>>>
>>>>> Absolutely not! You need to reprogram the standard PICs also on an APIC
>>>>> system, and this is precisely what both functions do. Put them into a
>>>>> diff tool to see for yourself.
>>>>>
>>>>> The same goes for timers. Even with the introduction of ACPI Timers,
>>>>> Local APIC Timers, and Time-Stamp Counters, you still need a
>>>>> traditional
>>>>> one (like RTC or PIT) for calibration at system startup. Simply because
>>>>> the newer ones don't run at a known fixed frequency.
>>>>> The Legacy HAL successfully employs an algorithm based on the RTC while
>>>>> the APIC HAL unsuccessfully tries to use the PIT.
>>>>>
>>>>>
>>>>> Actually we should, because the detection might not work (of course in
>>>>>>
>>>>> our simple case "ACPI UP/MP" vs. "Standard", it's simple, but think
>>>>> about
>>>>> other platforms where there can be subtle differences)
>>>>>
>>>>> Tell me about a single one we cannot detect and which is worth to
>>>>> support. I don't recall that we ever recommended our testers to choose
>>>>> a
>>>>> different HAL at setup.
>>>>>
>>>>>
>>>>> And normally it's not the setup that decides about the HAL, but the
>>>>>>
>>>>> bootloader.
>>>>>
>>>>> That defies your previous point about the setup initializing the
>>>>> registry depending on the HAL.
>>>>> If we can let the user select a Legacy HAL in the boot loader after
>>>>> installing with an ACPI HAL, it is also technically possible to have
>>>>> one
>>>>> HAL that encompasses both.
>>>>>
>>>>>
>>>>> - Colin
>>>>>
>>>>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Merging our x86 HALs

[Javier Agustìn Fernàndez Arroyo]

Win8 does not support old hardware as ReactOS do!

El 12 dic. 2017 17:52, "Alex Ionescu"  escribió:

> I would move to the Win8+ HAL Model -- a single HAL for APIC, ACPI with
> runtime support for UEFI (if present) and MP (if present).
>
> If people still want to run on a PIC VM (why???) or old computer, then we
> can also maintain the HAL PIC x86 for UP.
>
> Hence there would only be 2 HALs.
>
> Best regards,
> Alex Ionescu
>
> On Mon, Dec 11, 2017 at 1:07 AM, Colin Finck  wrote:
>
>> Am 11.12.2017 um 01:18 schrieb Hermès BÉLUSCA-MAÏTO:> If you basically
>> put all the HALs into one, then you obtain bloated stuff (which remains
>> in memory for the whole life of the OS). Example: standard HAL is 1MB
>> vs. ACPI HAL which is few kBHave you actually checked what makes up this
>> difference?
>> Hint: hal/halx86/legacy/bus/pci_vendors.ids
>>
>>
>> > Note that if Windows nowadays has only one hal, it's because they now
>> support basically only one "architecture"/platform, namely, ACPI
>> multiprocessor (to put it simple). It has its pros, but also a lot of cons.
>>
>> That doesn't mean we need to do the same. We can have one HAL for all
>> (Pentium and newer) x86 platforms. The overhead of additional checks at
>> boot-up is negligible. That should be a solution for 99% of the people
>> out there. The rest may still go and trim down our HAL to their needs.
>>
>> But let's not pretend we can maintain multiple x86 HALs for all x86
>> computers out there. Do you really want to test X HALs with Y different
>> systems? Ensure that a legacy HAL runs on a modern ACPI system? What
>> would be the point?
>>
>>
>> > Besides this, I've a question about your observation that in the APIC
>> hal (not ACPI) there's different implementation of
>> HalpCalibrateStallExecution and HalpInitializePICs /
>> HalpInitializeLegacyPIC . Isn't it precisely because these stuff are
>> completely different from the standard PICs used in platforms for which the
>> standard HAL (and possibly the ACPI HAL) are used?
>>
>> Absolutely not! You need to reprogram the standard PICs also on an APIC
>> system, and this is precisely what both functions do. Put them into a
>> diff tool to see for yourself.
>>
>> The same goes for timers. Even with the introduction of ACPI Timers,
>> Local APIC Timers, and Time-Stamp Counters, you still need a traditional
>> one (like RTC or PIT) for calibration at system startup. Simply because
>> the newer ones don't run at a known fixed frequency.
>> The Legacy HAL successfully employs an algorithm based on the RTC while
>> the APIC HAL unsuccessfully tries to use the PIT.
>>
>>
>> > Actually we should, because the detection might not work (of course in
>> our simple case "ACPI UP/MP" vs. "Standard", it's simple, but think about
>> other platforms where there can be subtle differences)
>>
>> Tell me about a single one we cannot detect and which is worth to
>> support. I don't recall that we ever recommended our testers to choose a
>> different HAL at setup.
>>
>>
>> > And normally it's not the setup that decides about the HAL, but the
>> bootloader.
>>
>> That defies your previous point about the setup initializing the
>> registry depending on the HAL.
>> If we can let the user select a Legacy HAL in the boot loader after
>> installing with an ACPI HAL, it is also technically possible to have one
>> HAL that encompasses both.
>>
>>
>> - Colin
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Merging our x86 HALs

[Javier Agustìn Fernàndez Arroyo]

But this breaks modularity, isnt It?

And HAL might become huge

El 10/12/2017 19:11, "Colin Finck"  escribió:

> Hi all,
>
> I have been looking into our HALs recently on the promise that it is a
> huge mess that needs fixing. Well, as a start I could imagine merging
> our 6 possible x86 HALs (Legacy, ACPI, APIC, ACPI+APIC, SMP, SMP+ACPI)
> into a single one, even if Windows ships individual ones. I see many
> advantages of that:
>
> * Less duplications and reduced mess: Right now, the APIC HAL hangs at
> HalpCalibrateStallExecution during boot, a function that has been fixed
> and universally implemented in all non-APIC HALs. The APIC HAL also
> duplicates HalpInitializePICs as HalpInitializeLegacyPIC.
> If you look at the SMP code, it didn't even receive the last build
> system changes and has conflicting implementations for APIC functions.
> A single x86 HAL would ensure that all possible configurations are
> maintained.
>
> * Future-proof: How is one going to implement newer features like x2APIC
> with a structure like that? Would it get another HAL, be integrated into
> the APIC HAL, or what?
> We wouldn't have such problems with a single x86 HAL.
>
> * Less setup work and testing: Currently, 1st stage setup detects the
> computer type and installs the appropriate HAL. As such, every
> additional HAL needs to be added to 1st stage setup code.
> The user is also able to select a custom HAL during setup, even if it
> wouldn't work on the machine. We should give neither the user nor the
> setup the ability to decide. The HAL itself knows best at boot-up what
> features to enable and what not.
>
> * Convenience: The same ReactOS installation could be used on several
> different x86 computers.
>
>
> So is this the way to go or do I miss something important?
>
>
> Best regards,
>
> Colin
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] ReactOS 0.4.7 to be released tomorrow, 6th December 2017 - Press Kit is online!

[Javier Agustìn Fernàndez Arroyo]

ReactOS rules! :P

On Tue, Dec 5, 2017 at 2:22 PM, David Quintana (gigaherz) <
gigah...@gmail.com> wrote:

> Awesome :D
>
> On 5 December 2017 at 14:09, Colin Finck  wrote:
>
>> Hi all!
>>
>> With all release preparations done, we can finally give a release date
>> for ReactOS 0.4.7: Tomorrow, Wednesday, 6th December 2017. During that
>> day (European time), the release will be published.
>>
>> A Press Kit for ReactOS 0.4.7 is already available:
>> https://sourceforge.net/projects/reactos/files/ReactOS/0.4.
>> 7/ReactOS-0.4.7-PressKit.zip
>> Feel free to send it to interested parties to let them know about the
>> upcoming release in advance.
>>
>>
>> Best regards,
>>
>> Colin Finck
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Git Migration: The documentation, rossubsys and wallpapers directories

[Javier Agustìn Fernàndez Arroyo]

what about some "art" repo?

It might have icons, wallpapers, some image and/or video galleries.
(just like Demo images and videos at Windows folders)

On Fri, Sep 8, 2017 at 7:03 PM, Mark Jansen  wrote:

> How about having a separate repository for wallpapers,
> and in 'master' or whatever only have the 'last release' wallpaper +
> one or 2 alternatives?
>
> The wallpaper repo can then have a structure where there is a folder
> per release,
> and an additional folder for potential candidates for next releases.
>
> On 8 September 2017 at 16:47, Colin Finck  wrote:
> > Am 08.09.2017 um 14:34 schrieb Hermès BÉLUSCA-MAÏTO:> It seems that both
> > these links :
> > https://stackoverflow.com/questions/3946538/git-clone-
> just-the-files-please
> > , and
> > https://stackoverflow.com/questions/120/using-git-
> to-get-just-the-latest-revision
> >>
> >> give a clue on how to just download the files without the history... >
> >
> >> [...]
> >>
> >>>
> >>> The builder(s) can have a "working" directory, in which they check-out
> >>> the
> >>> different "projects" they need for the build: reactos source can be
> DL'ed
> >>> into
> >>> "working/reactos.git" ; the wallpapers, rostests etc... can be DL'ed
> into
> >>> "working/rostests" and "working/wallpapers", then symlinks (OK on *nix
> &
> >>> windows) into the "working/reactos.git/modules" can be created that
> point
> >>> to "working/wallpapers" and "working/rostests" , and then we build as
> >>> usual
> >>> ?
> >
> >
> > Both of your ideas destroy the automatic relationship of a specific
> revision
> > of "reactos" with a specific revision of the modules.
> >
> > We don't want to start telling people to use that particular version of
> > "reactos" with that particular version of "rostests". It gets even worse
> if
> > you want to hack on both in a branch..
> > So matching versions must always stay together, and this is why I want to
> > keep them in a single repository, only enabled/disabled by a CMake
> variable.
> >
> > Of course, the logical next step would be overhauling our tree layout.
> > But first things first ;)
> >
> >
>  * I don't get the idea of that "rossubsys" directory created in 2014..
>  These subsystems are all stubs, never built with modern ReactOS, and
>  no work has happened since "reviving" them. I would just go and remove
>  them again. You can always find them in our repository history.
> 
> >>> As long as they can be found easily in the history, then ok.
> >
> >
> > As with every Version Control System, the difficulty of finding deleted
> > files in history boils down to the creativity of your used GUI :)
> >
> > Shortcut for you to find related commits:
> >   git log --name-only | grep -C 5 rossubsys
> >
> >
> > I have updated my conversion scripts and rules at
> > https://github.com/ColinFinck/reactos-git-conversion-scripts to split
> off
> > "documentation" into its own repository.
> > Also they now perform the "reactos" directory reorganization and add the
> > "0.4.7-dev" tag for git describe.
> >
> >
> > Cheers,
> >
> > Colin
> >
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] who is the ​​​​​​​administrator of ReactOS Facebook Group?

[Javier Agustìn Fernàndez Arroyo]

here in Spain we call this a "zas! en toda la boca"

On Wed, Aug 30, 2017 at 8:59 PM, Jared Smudde 
wrote:

> Well, it says you. So...
>
>
> --
> *From:* Ros-dev  on behalf of Alexander
> Rechitskiy 
> *Sent:* Wednesday, August 30, 2017 11:14 AM
> *To:* ReactOS Development List
> *Subject:* [ros-dev] who is the administrator of ReactOS Facebook Group?
>
> who is the administrator of that ReactOS FB Group?
>
>
> https://www.facebook.com/groups/135140536538192/
>
> --
> Best regards,
> Alexander Rechitskiy
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] ReactOS now listed in AppDB

[Javier Agustìn Fernàndez Arroyo]

I wonder how much time until admins remové It lol

El 12/08/2017 13:48, "Erkin Alp Güney"  escribió:

> I have recently added ReactOS as a distribution into Wine Application
> Compatibility database as ReactOS uses most of Wine components.
> ReactOS-Windows incompatibilities can now be tracked like Wine-Windows
> incompatibilies.
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Enabling themes in 3rd stage

[Javier Agustìn Fernàndez Arroyo]

I didnt say so, lol

El 31/07/2017 20:38, "Giannis Adamopoulos" 
escribió:

So you volunteer to create a theme?


Hermès BÉLUSCA-MAÏTO  wrote on Mon, July 31st, 2017,
6:24 PM:
> What about the « Whistler » - like theme ? ^^
>
>
>
> H.
>
>
>
> De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de Mark
Jansen
> Envoyé : lundi 31 juillet 2017 17:18
> À : ReactOS Development List
> Objet : Re: [ros-dev] Enabling themes in 3rd stage
>
>
>
> I like this theme!
>
>
>
> Op 31 jul. 2017 16:44 schreef "Ged Murphy" :
>
> A link to the theme I mentioned would probably help...
> http://aportz19.deviantart.com/art/Basic-Lite-and-Basic-
8-Visual-Style-for-Windows-XP-393826050
>
>
> -Original Message-
> From: Ged Murphy [mailto:gedmurphy.mailli...@gmail.com]
> Sent: 31 July 2017 15:43
> To: 'ReactOS Development List' 
> Subject: RE: [ros-dev] Enabling themes in 3rd stage
>
> Do you have some pics??
>
> I've always been a big fan of seeing the Basic Lite theme being on by
default, which would give ros a much more modern look and feel.
> We're missing the start menu implementation for this though.
>
>
>
> -Original Message-
> From: Ros-dev [mailto:ros-dev-boun...@reactos.org] On Behalf Of Giannis
Adamopoulos
> Sent: 31 July 2017 15:29
> To: ros-dev@reactos.org
> Subject: [ros-dev] Enabling themes in 3rd stage
>
> Hello,
> After recent changes in explorer, comctl32 and uxtheme the state of
themes in reactos was improved a lot. I would like to ask your opinions
about enabling themes in 3rd stage. It is also possible to have an option
in 2nd stage to select if we want 3rd stage to have themes enabled. Do you
think this should be enabled by default or not? All ideas are welcome. My
intention is to complete it ASAP so that it can make in the release.
>
> Thanks,
> Giannis Adamopoulos
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Enabling themes in 3rd stage

[Javier Agustìn Fernàndez Arroyo]

choose -- choice

El 31/07/2017 19:31, "Javier Agustìn Fernàndez Arroyo" <elh...@gmail.com>
escribió:

> hi all,
>
> honestly, i dont think theming is a crucial choose when installing. i
> would not add that screen, at 2nd stage at least.
>
> Maybe at 3rd, right after 1st run
>
> El 31/07/2017 18:28, "Hermès BÉLUSCA-MAÏTO" <hermes.belu...@sfr.fr>
> escribió:
>
> What about the « Whistler » - like theme ? ^^
>
>
>
> H.
>
>
>
> *De :* Ros-dev [mailto:ros-dev-boun...@reactos.org] *De la part de* Mark
> Jansen
> *Envoyé :* lundi 31 juillet 2017 17:18
> *À :* ReactOS Development List
> *Objet :* Re: [ros-dev] Enabling themes in 3rd stage
>
>
>
> I like this theme!
>
>
>
> Op 31 jul. 2017 16:44 schreef "Ged Murphy" <gedmurphy.mailli...@gmail.com
> >:
>
> A link to the theme I mentioned would probably help...
> http://aportz19.deviantart.com/art/Basic-Lite-and-Basic-8-
> Visual-Style-for-Windows-XP-393826050
>
>
> -Original Message-
> From: Ged Murphy [mailto:gedmurphy.mailli...@gmail.com]
> Sent: 31 July 2017 15:43
> To: 'ReactOS Development List' <ros-dev@reactos.org>
> Subject: RE: [ros-dev] Enabling themes in 3rd stage
>
> Do you have some pics??
>
> I've always been a big fan of seeing the Basic Lite theme being on by
> default, which would give ros a much more modern look and feel.
> We're missing the start menu implementation for this though.
>
>
>
> -Original Message-
> From: Ros-dev [mailto:ros-dev-boun...@reactos.org] On Behalf Of Giannis
> Adamopoulos
> Sent: 31 July 2017 15:29
> To: ros-dev@reactos.org
> Subject: [ros-dev] Enabling themes in 3rd stage
>
> Hello,
> After recent changes in explorer, comctl32 and uxtheme the state of themes
> in reactos was improved a lot. I would like to ask your opinions about
> enabling themes in 3rd stage. It is also possible to have an option in 2nd
> stage to select if we want 3rd stage to have themes enabled. Do you think
> this should be enabled by default or not? All ideas are welcome. My
> intention is to complete it ASAP so that it can make in the release.
>
> Thanks,
> Giannis Adamopoulos
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Enabling themes in 3rd stage

[Javier Agustìn Fernàndez Arroyo]

hi all,

honestly, i dont think theming is a crucial choose when installing. i would
not add that screen, at 2nd stage at least.

Maybe at 3rd, right after 1st run

El 31/07/2017 18:28, "Hermès BÉLUSCA-MAÏTO" 
escribió:

What about the « Whistler » - like theme ? ^^



H.



*De :* Ros-dev [mailto:ros-dev-boun...@reactos.org] *De la part de* Mark
Jansen
*Envoyé :* lundi 31 juillet 2017 17:18
*À :* ReactOS Development List
*Objet :* Re: [ros-dev] Enabling themes in 3rd stage



I like this theme!



Op 31 jul. 2017 16:44 schreef "Ged Murphy" :

A link to the theme I mentioned would probably help...
http://aportz19.deviantart.com/art/Basic-Lite-and-Basic-
8-Visual-Style-for-Windows-XP-393826050


-Original Message-
From: Ged Murphy [mailto:gedmurphy.mailli...@gmail.com]
Sent: 31 July 2017 15:43
To: 'ReactOS Development List' 
Subject: RE: [ros-dev] Enabling themes in 3rd stage

Do you have some pics??

I've always been a big fan of seeing the Basic Lite theme being on by
default, which would give ros a much more modern look and feel.
We're missing the start menu implementation for this though.



-Original Message-
From: Ros-dev [mailto:ros-dev-boun...@reactos.org] On Behalf Of Giannis
Adamopoulos
Sent: 31 July 2017 15:29
To: ros-dev@reactos.org
Subject: [ros-dev] Enabling themes in 3rd stage

Hello,
After recent changes in explorer, comctl32 and uxtheme the state of themes
in reactos was improved a lot. I would like to ask your opinions about
enabling themes in 3rd stage. It is also possible to have an option in 2nd
stage to select if we want 3rd stage to have themes enabled. Do you think
this should be enabled by default or not? All ideas are welcome. My
intention is to complete it ASAP so that it can make in the release.

Thanks,
Giannis Adamopoulos

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev



___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] About the bootcd and livecd, and the 1st-stage GUI setup

[Javier Agustìn Fernàndez Arroyo]

I'm with David too

El 05/07/2017 15:26, "Hermès BÉLUSCA-MAÏTO" 
escribió:

> Thank you guys for your brainstorming about the boot menu.
> This will require few adjustments to freeldr before being able to have the
> submenus, since we currently don't support them "dynamically" (aka.
> specified from within freeldr.ini), but only in hardcoded manner (like the
> F8 advanced options) up to now.
>
> Hermès;.
>
> -Message d'origine-
> De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de Ged Murphy
> Envoyé : mercredi 5 juillet 2017 15:20
> À : 'ReactOS Development List'
> Objet : Re: [ros-dev] About the bootcd and livecd, and the 1st-stage GUI
> setup
>
> Run or install?
> I think I prefer David's version.
>
> - Install
> - Try without installing
> - Cancel and boot from disk
> - Advanced options ...
>
>
> -Original Message-
> From: Ros-dev [mailto:ros-dev-boun...@reactos.org] On Behalf Of Giannis
> Adamopoulos
> Sent: 05 July 2017 14:03
> To: ReactOS Development List 
> Subject: Re: [ros-dev] About the bootcd and livecd, and the 1st-stage GUI
> setup
>
> I'd say that we should show:
> - Run or install ReactOS
> - Boot from hard disk
> - Advanced options
>
> Nothing more should be needed and the first option should be clear that
> can either lead to a live environment or a setup.
>
>
> David Quintana (gigaherz)  wrote on Tue, July 4th,
> 2017, 10:45 PM:
> > I feel like the boot menu is going to be far too busy for the end
> > user. I'd go with something closer to
> >
> > blah blah:
> >
> >- Install Now
> >- Try without installing
> >- Show advanced options...
> >
> > where:
> >
> >- Install now -- boots into the graphical installer (no desktop unless
> >you cancel or something)
> >- Try without installing -- boots into livecd desktop (backed by RAM,
> I
> >guess)
> >- Show advanced options... -- opens a second-level menu with
> >- Text-mode installer
> >   - Live boot without Ramdisk
> >   - etc.
> >
> >
> >
> > On 4 July 2017 at 21:45, Hermès BÉLUSCA-MAÏTO 
> wrote:
> >
> > > Hello everyone,
> > >
> > >
> > >
> > > One of the long-term plan for ReactOS was to have a graphical
> > > user-mode interface for the 1st-stage setup, similar to e.g. what
> > > may be found in newer versions of Windows (Vista+), as an
> > > alternative to our current 1st-stage setup in text-mode
> > >
> > > (note that I say “alternative”, not “replacement”, because both of
> > > them can live together without fundamental changes to either ReactOS
> > > or our ISO images, both of them can share core functionality, and
> > > finally because some people may prefer the text-mode either for
> > > unattended installations or for low-memory conditions).
> > >
> > >
> > >
> > > You can find some information about the 1st-stage GUI setup here:
> > > https://reactos.org/wiki/First_Stage_GUI_Setup . In our source code,
> > > it can be found in base/setup/reactos/ . Currently only most of the
> > > screens have been implemented, while the core functionality is not
> > > present. However this functionality can somehow be taken by reusing
> > > the source code of USETUP (see my branch
> > > https://svn.reactos.org/svn/reactos/branches/setup_
> > > improvements/base/setup/ ).
> > >
> > >
> > >
> > >
> > >
> > > Abstract (aka. TL;DR): I explain below the needed changes introduced
> > > experimentally in the “setup-improvements” branch, revision 75273,
> > > to generate an all-in-one ReactOS bootcd, that includes both the
> > > 1st-stage text-mode setup + 1st-stage GUI setup alternative +
> > > live-demo functionality. This is meant to replace our currently
> > > separated “bootcd” / “livecd” ISOs, where the latter currently do
> > > not offer the possibility to install ReactOS. Some currently known
> potential problems are evoked.
> > >
> > >
> > >
> > > Images: Proposed BootCD contents : http://i.imgur.com/EBA6JHd.png ;
> > > Proposed Boot Menu : http://i.imgur.com/14n5Ryi.png .
> > >
> > >
> > >
> > >
> > >
> > > Having a 1st-stage GUI setup also means that it’ll also use the
> > > already-existing functionality that we offer in our “Live-CD” ISOs.
> > > Currently, the “Live-CD” ISOs we provide only allow for
> > > demonstration purposes, while the ReactOS installation proper is
> > > found in our so-called “Boot-CD” ISOs (which currently only contain
> > > text-mode setup). Thus, the 1 st-stage GUI setup, as an alternative
> > > to the 1st-stage setup in text-mode, means that both ISOs can be
> > > merged all in one, and we won’t have to make a distinction between
> > > both: they will be able to offer both the 1 st-stage in text mode
> > > AND a graphical mode (à la “Live-CD”) where it is possible to choose
> > > whether to test ReactOS in demo mode, or to install it via the GUI
> setup.
> > >
> > > Such an all-in-one ISO capability was already present in the trunk
> > > under the name 

Re: [ros-dev] "Note: LibreOffice 5.4 will be the last codeline to support Windows XP or Vista"

[Javier Agustìn Fernàndez Arroyo]

have been*

On Thu, Jun 29, 2017 at 7:06 PM, Javier Agustìn Fernàndez Arroyo <
elh...@gmail.com> wrote:

> ...which leads me to an obscure question...
>
> "have these last attacks a way to force Windows users to update their
> PCs?" :-P
>
> On Thu, Jun 29, 2017 at 7:04 PM, Alexander Rechitskiy <art1st...@yandex.ru
> > wrote:
>
>> But ReactOS is Invulnerable for most of  Windows XP/Server 2003 malware.
>> And  actually, Windows XP support is not dropped.  Windows Embedded
>> POSReady 2009 will be supported till April 9, 2019​​​
>>
>> https://en.wikipedia.org/wiki/Windows_Embedded_Industry
>>
>>
>> 29.06.2017, 19:55, "Riccardo Paolo Bestetti" <riccardo.kyo...@live.it>:
>>
>> I’m just gonna snap in for my yearly IT guy NT6 rant: this mindset is
>> going to kill the project by making it useless whenever it reaches a usable
>> state.
>>
>> Windows XP/Server 2003 use is **already** marginal as of today, and it’s
>> only gonna get “worse” as more and more networks get infected by ransomware
>> and institutions all over the world wake up and update (and as time passes
>> of course). It’s not a matter of “fancy”, it is a matter of what people use
>> on their computers. With that argument you may as well advocate for DOS.
>>
>>
>>
>> Please don’t be offended, as always this is only intended as a reality
>> check.
>>
>>
>>
>> Best regards,
>>
>> Riccardo Paolo Bestetti
>>
>>
>>
>> *From:* Ros-dev [mailto:ros-dev-boun...@reactos.org] *On Behalf Of *Hermès
>> BÉLUSCA-MAÏTO
>> *Sent:* giovedì 29 giugno 2017 16:09
>> *To:* 'ReactOS Development List' <ros-dev@reactos.org>
>> *Subject:* Re: [ros-dev] "Note: LibreOffice 5.4 will be the last
>> codeline to support Windows XP or Vista"
>>
>>
>>
>> I’m wondering for which useless / fancy features they need Windows 7+
>> support only….
>>
>>
>>
>> H.
>>
>>
>>
>>
>>
>> *De :* Ros-dev [mailto:ros-dev-boun...@reactos.org
>> <ros-dev-boun...@reactos.org>] *De la part de* Javier Agustìn Fernàndez
>> Arroyo
>> *Envoyé :* jeudi 29 juin 2017 15:48
>> *À :* ReactOS Development List
>> *Objet :* [ros-dev] "Note: LibreOffice 5.4 will be the last codeline to
>> support Windows XP or Vista"
>>
>>
>>
>> https://wiki.documentfoundation.org/Releases/5.4.0/RC1
>>
>>
>>
>>
>>
>> FYI
>> ,
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>>
>>
>> --
>> Best regards,
>>
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] "Note: LibreOffice 5.4 will be the last codeline to support Windows XP or Vista"

[Javier Agustìn Fernàndez Arroyo]

...which leads me to an obscure question...

"have these last attacks a way to force Windows users to update their PCs?"
:-P

On Thu, Jun 29, 2017 at 7:04 PM, Alexander Rechitskiy <art1st...@yandex.ru>
wrote:

> But ReactOS is Invulnerable for most of  Windows XP/Server 2003 malware.
> And  actually, Windows XP support is not dropped.  Windows Embedded
> POSReady 2009 will be supported till April 9, 2019​​​
>
> https://en.wikipedia.org/wiki/Windows_Embedded_Industry
>
>
> 29.06.2017, 19:55, "Riccardo Paolo Bestetti" <riccardo.kyo...@live.it>:
>
> I’m just gonna snap in for my yearly IT guy NT6 rant: this mindset is
> going to kill the project by making it useless whenever it reaches a usable
> state.
>
> Windows XP/Server 2003 use is **already** marginal as of today, and it’s
> only gonna get “worse” as more and more networks get infected by ransomware
> and institutions all over the world wake up and update (and as time passes
> of course). It’s not a matter of “fancy”, it is a matter of what people use
> on their computers. With that argument you may as well advocate for DOS.
>
>
>
> Please don’t be offended, as always this is only intended as a reality
> check.
>
>
>
> Best regards,
>
> Riccardo Paolo Bestetti
>
>
>
> *From:* Ros-dev [mailto:ros-dev-boun...@reactos.org] *On Behalf Of *Hermès
> BÉLUSCA-MAÏTO
> *Sent:* giovedì 29 giugno 2017 16:09
> *To:* 'ReactOS Development List' <ros-dev@reactos.org>
> *Subject:* Re: [ros-dev] "Note: LibreOffice 5.4 will be the last codeline
> to support Windows XP or Vista"
>
>
>
> I’m wondering for which useless / fancy features they need Windows 7+
> support only….
>
>
>
> H.
>
>
>
>
>
> *De :* Ros-dev [mailto:ros-dev-boun...@reactos.org
> <ros-dev-boun...@reactos.org>] *De la part de* Javier Agustìn Fernàndez
> Arroyo
> *Envoyé :* jeudi 29 juin 2017 15:48
> *À :* ReactOS Development List
> *Objet :* [ros-dev] "Note: LibreOffice 5.4 will be the last codeline to
> support Windows XP or Vista"
>
>
>
> https://wiki.documentfoundation.org/Releases/5.4.0/RC1
>
>
>
>
>
> FYI
> ,
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> --
> Best regards,
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] "Note: LibreOffice 5.4 will be the last codeline to support Windows XP or Vista"

[Javier Agustìn Fernàndez Arroyo]

rasomware is definitely not a reason.

Windows XP may be patched against it. Its not a matter of design, but
implementation.

On Thu, Jun 29, 2017 at 6:54 PM, Riccardo Paolo Bestetti <
riccardo.kyo...@live.it> wrote:

> I’m just gonna snap in for my yearly IT guy NT6 rant: this mindset is
> going to kill the project by making it useless whenever it reaches a usable
> state.
>
> Windows XP/Server 2003 use is **already** marginal as of today, and it’s
> only gonna get “worse” as more and more networks get infected by ransomware
> and institutions all over the world wake up and update (and as time passes
> of course). It’s not a matter of “fancy”, it is a matter of what people use
> on their computers. With that argument you may as well advocate for DOS.
>
>
>
> Please don’t be offended, as always this is only intended as a reality
> check.
>
>
>
> Best regards,
>
> Riccardo Paolo Bestetti
>
>
>
> *From:* Ros-dev [mailto:ros-dev-boun...@reactos.org] *On Behalf Of *Hermès
> BÉLUSCA-MAÏTO
> *Sent:* giovedì 29 giugno 2017 16:09
> *To:* 'ReactOS Development List' <ros-dev@reactos.org>
> *Subject:* Re: [ros-dev] "Note: LibreOffice 5.4 will be the last codeline
> to support Windows XP or Vista"
>
>
>
> I’m wondering for which useless / fancy features they need Windows 7+
> support only….
>
>
>
> H.
>
>
>
>
>
> *De :* Ros-dev [mailto:ros-dev-boun...@reactos.org
> <ros-dev-boun...@reactos.org>] *De la part de* Javier Agustìn Fernàndez
> Arroyo
> *Envoyé :* jeudi 29 juin 2017 15:48
> *À :* ReactOS Development List
> *Objet :* [ros-dev] "Note: LibreOffice 5.4 will be the last codeline to
> support Windows XP or Vista"
>
>
>
> https://wiki.documentfoundation.org/Releases/5.4.0/RC1
>
>
>
>
>
> FYI
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] "Note: LibreOffice 5.4 will be the last codeline to support Windows XP or Vista"

[Javier Agustìn Fernàndez Arroyo]

Maybe se could send some mail to those proyects, something like "hey, XP is
dead but we are alive! ;)"

El 29/06/2017 16:56, "Thomas Faber" <thomas.fa...@reactos.org> escribió:

> There's an easy benefit for them: it reduces their test matrix.
> That's why you generally only support platforms that have value, rather
> than supporting everything unless and until you have a concrete reason
> to drop it.
>
>
> On 2017-06-29 16:08, Hermès BÉLUSCA-MAÏTO wrote:
>
>> I’m wondering for which useless / fancy features they need Windows 7+
>> support only….
>>
>>
>> H.
>>
>>
>>
>> De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de Javier
>> Agustìn Fernàndez Arroyo
>> Envoyé : jeudi 29 juin 2017 15:48
>> À : ReactOS Development List
>> Objet : [ros-dev] "Note: LibreOffice 5.4 will be the last codeline to
>> support Windows XP or Vista"
>>
>>
>> https://wiki.documentfoundation.org/Releases/5.4.0/RC1
>>
>>
>>
>> FYI
>>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] "Note: LibreOffice 5.4 will be the last codeline to support Windows XP or Vista"

[Javier Agustìn Fernàndez Arroyo]

https://wiki.documentfoundation.org/Releases/5.4.0/RC1


FYI
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] ReactOS Hackfest 2017 - Are you in?

[Javier Agustìn Fernàndez Arroyo]

sorry, i cant :(

El 21/06/2017 12:05, "Colin Finck"  escribió:

> Hi all!
>
> I'm currently planning the ReactOS Hackfest 2017 in the Cologne/Bonn
> area in Germany. Currently, the plan is to book a meeting room from
> Monday, August 14 to Friday, August 18. We can then use the weekend
> before to get to Cologne and explore the city a bit. After the Hackfest,
> everybody interested can join us at FrOSCon in Bonn the weekend after.
>
> As booking a room there involves significant costs, I'd like to know who
> of you can definitely make it for the Hackfest and who of you is
> definitely out.
>
> Please reply now to prevent me from bugging you on IRC all the time! ;)
>
>
> Cheers,
>
> Colin
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [hbelusca] 75133: [NTOS]: Revert the pool tag change from r75128, and explain in comment why we cannot actually use it.

[Javier Agustìn Fernàndez Arroyo]

imho the more documented the code is, the easier to read and understand

El 19/06/2017 19:48, "Thomas Faber"  escribió:

> On 2017-06-19 18:29, hbelu...@svn.reactos.org wrote:
>
>> +/*
>> + * Free it from the pool.
>> + *
>> + * We cannot use here ExFreePoolWithTag(..., OB_NAME_TAG); ,
>> because
>> + * the object name may have been massaged during operation by
>> different
>> + * object parse routines. If the latter ones have to resolve a
>> symbolic
>> + * link (e.g. as is done by CmpParseKey() and
>> CmpGetSymbolicLink()),
>> + * the original object name is freed and re-allocated from the
>> pool,
>> + * possibly with a different pool tag. At the end of the day,
>> the new
>> + * object name can be reallocated and completely different, but
>> we
>> + * should still be able to free it!
>> + */
>> +ExFreePool(Buffer);
>>
>
> I feel like
>
> ExFreePoolWithTag(Buffer, 0)
>
> conveys that same message without needing a huge comment?
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] mplayer -- branded name?

[Javier Agustìn Fernàndez Arroyo]

okay, forget it, i just saw our app is called "mplay32", and not "mplayer"

On Thu, Jun 1, 2017 at 10:26 AM, Javier Agustìn Fernàndez Arroyo <
elh...@gmail.com> wrote:

> Hey guys,
>
> An idea has just come to my mind,
> mplayer is an application that already exists for Linux:
>
> https://www.mplayerhq.hu/design7/news.html
>
> maybe we should change ReactOS´ player name so that we avoid possible
> future demands?
>
> what do u think?
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] mplayer -- branded name?

[Javier Agustìn Fernàndez Arroyo]

Hey guys,

An idea has just come to my mind,
mplayer is an application that already exists for Linux:

https://www.mplayerhq.hu/design7/news.html

maybe we should change ReactOS´ player name so that we avoid possible
future demands?

what do u think?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [ion] 74546: BL Library now works 100% in paging, protected mode. A picture is worth a thousand commits: http://i.imgur.com/Zx2nQ6x.jpg [BOOTLIB]: Add support for protocol op

[Javier Agustìn Fernàndez Arroyo]

Please tell me ReactOS won't have to buy a key from MS so that we are
authorized to boot into machines :p

El 15/05/2017 12:04, "Thomas Faber"  escribió:

> We have a bin2c tool that would make including the boot logo much
> nicer. You'll want to use something like the attached patch, and add
> the bmp file as app/rosload/logo.bmp. Then just include "logo.h"
> instead of the g_Logo array in rosload.c.
>
>
> On 2017-05-15 03:38, i...@svn.reactos.org wrote:
>
>> Author: ion
>> Date: Mon May 15 01:38:49 2017
>> New Revision: 74546
>>
>> URL: http://svn.reactos.org/svn/reactos?rev=74546=rev
>> Log:
>> BL Library now works 100% in paging, protected mode. A picture is worth a
>> thousand commits: http://i.imgur.com/Zx2nQ6x.jpg
>> [BOOTLIB]: Add support for protocol open/close/lookup while paging and
>> protected mode is enabled.
>> [BOOTLIB]: Implement support for dozens of UEFI functions while under
>> protected mode.
>> [BOOTLIB]: Fix bugs in existing UEFI functions which were switching to
>> _protected_ mode instead of _real mode_ before making the UEFI call.
>> [BOOTLIB]: Free dynamic descriptor in MmMdFreeDescriptor.
>> [BOOTLIB]: Implement BlHtDelete.
>> [BOOTLIB]: Implement re-initialize-all path in DsppInitialize.
>> [BOOTLIB]: Fix small bug in BlDisplayInvalidateOemBitmap
>> [BOOTLIB]: Fix bigger bug in BlDisplayGetOemBitmap :)
>>
>> Modified:
>> trunk/reactos/boot/environ/app/rosload/rosload.c
>> trunk/reactos/boot/environ/include/bl.h
>> trunk/reactos/boot/environ/lib/firmware/efi/firmware.c
>> trunk/reactos/boot/environ/lib/io/device.c
>> trunk/reactos/boot/environ/lib/io/display/display.c
>> trunk/reactos/boot/environ/lib/io/display/efi/gop.c
>> trunk/reactos/boot/environ/lib/misc/util.c
>> trunk/reactos/boot/environ/lib/mm/descriptor.c
>> trunk/reactos/boot/environ/lib/platform/time.c
>>
>> [This mail would be too long, it was shortened to contain the URLs only.]
>>
>> Modified: trunk/reactos/boot/environ/app/rosload/rosload.c
>> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/enviro
>> n/app/rosload/rosload.c?rev=74546=74545=74546=diff
>>
>> Modified: trunk/reactos/boot/environ/include/bl.h
>> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/enviro
>> n/include/bl.h?rev=74546=74545=74546=diff
>>
>> Modified: trunk/reactos/boot/environ/lib/firmware/efi/firmware.c
>> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/enviro
>> n/lib/firmware/efi/firmware.c?rev=74546=74545=74546=diff
>>
>> Modified: trunk/reactos/boot/environ/lib/io/device.c
>> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/enviro
>> n/lib/io/device.c?rev=74546=74545=74546=diff
>>
>> Modified: trunk/reactos/boot/environ/lib/io/display/display.c
>> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/enviro
>> n/lib/io/display/display.c?rev=74546=74545=74546=diff
>>
>> Modified: trunk/reactos/boot/environ/lib/io/display/efi/gop.c
>> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/enviro
>> n/lib/io/display/efi/gop.c?rev=74546=74545=74546=diff
>>
>> Modified: trunk/reactos/boot/environ/lib/misc/util.c
>> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/enviro
>> n/lib/misc/util.c?rev=74546=74545=74546=diff
>>
>> Modified: trunk/reactos/boot/environ/lib/mm/descriptor.c
>> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/enviro
>> n/lib/mm/descriptor.c?rev=74546=74545=74546=diff
>>
>> Modified: trunk/reactos/boot/environ/lib/platform/time.c
>> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/enviro
>> n/lib/platform/time.c?rev=74546=74545=74546=diff
>>
>>
>>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Vgal USB patches

[Javier Agustìn Fernàndez Arroyo]

True, i didnt

Sorry guys

El 16/04/2017 16:32, "Hermès BÉLUSCA-MAÏTO" <hermes.belu...@sfr.fr>
escribió:

> Hi Javier,
>
>
>
> Actually I don’t think you’ve found where these code reviews are taking
> place. They are here:
>
> https://code.reactos.org/cru/CR-109
>
> https://code.reactos.org/cru/CR-110
>
> https://code.reactos.org/cru/CR-111
>
> and you can find there who’s currently reviewing them.
>
>
>
> By what Alexander seems to say, the code changes seem to work quite well.
>
>
>
> Hermès
>
>
>
> *De :* Ros-dev [mailto:ros-dev-boun...@reactos.org] *De la part de*
> Javier Agustìn Fernàndez Arroyo
> *Envoyé :* dimanche 16 avril 2017 10:59
> *À :* ReactOS Development List
> *Objet :* Re: [ros-dev] Vgal USB patches
>
>
>
> please forgive me, as this may sound so rude...
>
> Is this code reliable? is anyone reviewing it?
>
>
>
> On Sat, Apr 15, 2017 at 2:09 PM, Alexander Rechitskiy <art1st...@yandex.ru>
> wrote:
>
> Hello everyone!
>
>
>
> Vgal sais that his code from СR-110 CR-111 is ready for trunk merging.
>
>
>
> Vgal's changes were tested a lot by the Russian community. Huge
> regressions are impossible. We have enough time before release (1 month and
> two days). I can't imagine a better time for the merge.
>
>
>
>
>
> We need the upcoming release to be great again!
>
>
>
>
>
>
>
> 06.04.2017, 08:14, "Peter Hater" <7elem...@mail.bg>:
>
> Code review is open for everyone.
>
> Go ahead at search for ((not so) obvious) bugs :)
>
> CR-110/CR-111 maybe more.
>
> BR,
>
> Peter
>
>
> On Apr 6, 2017, at 08:09, Javier Agustìn Fernàndez Arroyo <
> elh...@gmail.com> wrote:
>
>
> Wo is reviewing that Code?
>
>
>
> El 06/04/2017 06:46, "Peter Hater" <7elem...@mail.bg> escribió:
>
> No.
> This means that we won't have (much) BSODs and weird crashes when
> (dis)connecting usb devices.
> Booting from usb is (at least) blocked by CORE-10456.
>
> BR,
> Peter
>
> > On Apr 6, 2017, at 04:01, Thomas Mueller <mueller6...@twc.com> wrote:
> >
> > from Robert Naumann:
> >
> >> Codereview is already ongoing. If everything goes well, USB will become
> >> great again soon.
> >
> > Does this mean it will be possible to build ReactOS and install to a USB
> stick so as to be bootable?
> >
> > Tom
> >
> >
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> ,
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
>
>
> --
> Best regards,
>
>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Vgal USB patches

[Javier Agustìn Fernàndez Arroyo]

please forgive me, as this may sound so rude...

Is this code reliable? is anyone reviewing it?

On Sat, Apr 15, 2017 at 2:09 PM, Alexander Rechitskiy <art1st...@yandex.ru>
wrote:

> Hello everyone!
>
> Vgal sais that his code from СR-110 CR-111 is ready for trunk merging.
>
> Vgal's changes were tested a lot by the Russian community. Huge
> regressions are impossible. We have enough time before release (1 month and
> two days). I can't imagine a better time for the merge.
>
>
> We need the upcoming release to be great again!
>
>
>
> 06.04.2017, 08:14, "Peter Hater" <7elem...@mail.bg>:
>
> Code review is open for everyone.
> Go ahead at search for ((not so) obvious) bugs :)
> CR-110/CR-111 maybe more.
>
> BR,
> Peter
>
> On Apr 6, 2017, at 08:09, Javier Agustìn Fernàndez Arroyo <
> elh...@gmail.com> wrote:
>
>
> Wo is reviewing that Code?
>
> El 06/04/2017 06:46, "Peter Hater" <7elem...@mail.bg> escribió:
>
> No.
> This means that we won't have (much) BSODs and weird crashes when
> (dis)connecting usb devices.
> Booting from usb is (at least) blocked by CORE-10456.
>
> BR,
> Peter
>
> > On Apr 6, 2017, at 04:01, Thomas Mueller <mueller6...@twc.com> wrote:
> >
> > from Robert Naumann:
> >
> >> Codereview is already ongoing. If everything goes well, USB will become
> >> great again soon.
> >
> > Does this mean it will be possible to build ReactOS and install to a USB
> stick so as to be bootable?
> >
> > Tom
> >
> >
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> ,
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> --
> Best regards,
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Vgal USB patches

[Javier Agustìn Fernàndez Arroyo]

Wo is reviewing that Code?

El 06/04/2017 06:46, "Peter Hater" <7elem...@mail.bg> escribió:

> No.
> This means that we won't have (much) BSODs and weird crashes when
> (dis)connecting usb devices.
> Booting from usb is (at least) blocked by CORE-10456.
>
> BR,
> Peter
>
> > On Apr 6, 2017, at 04:01, Thomas Mueller  wrote:
> >
> > from Robert Naumann:
> >
> >> Codereview is already ongoing. If everything goes well, USB will become
> >> great again soon.
> >
> > Does this mean it will be possible to build ReactOS and install to a USB
> stick so as to be bootable?
> >
> > Tom
> >
> >
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Vgal USB patches

[Javier Agustìn Fernàndez Arroyo]

"P.S. Here is the link to legal VHD-image of Microsoft Windows Server 2003
R2 Enterprise Edition for test purposes"

lol
1st time i`ve heard about this

On Tue, Apr 4, 2017 at 1:39 AM, Hermès BÉLUSCA-MAÏTO 
wrote:

> Hi !
>
> A proper code review may be in order, where/how can we do that?
>
>
>
> Regards,
>
> Hermès BÉLUSCA - MAÏTO
>
>
>
> *De :* Ros-dev [mailto:ros-dev-boun...@reactos.org] *De la part de*
> Alexander Rechitskiy
> *Envoyé :* mardi 4 avril 2017 01:18
> *À :* ReactOS Development List
> *Objet :* [ros-dev] Vgal USB patches
>
>
>
> Hello all!
>
>
>
> Vgal showed significant progress in his USB patches. With his test images
> almost every sungle  usb keyboard and mouse works. We (russian community)
> have reached the top corner of our testing capabilities and we could not
> find any new bugs in his work anymore. So Vgal usb patches are now in very
> mature state.
>
>
>
> Now we probably need to make the next step and put all his work or parts
> of it into trunk. But before  this Vgal said that it is important to test
> his drivers against Windows 2003 server to be sure in compatibilty. And
> this where russian community can not provide enough help with . I know that
> many developers are familiar with this procedure. So probably it is your
> turn now.
>
>
>
> We need this patches in trunk in order to make our next release great
> again! And we have not so many but still enough time to finish this effort.
>
>
>
>
>
> P.S. Here is the link to legal VHD-image of Microsoft Windows Server 2003
> R2 Enterprise Edition for test purposes
>
> https://www.microsoft.com/en-us/download/details.aspx?id=19727
>
> --
> Best regards,
>
> Alexander Rechitskiy
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [khornicek] 74209: [RAPPS] - Add a custom build of the Mesa 3D Graphics Library. This build contains mesa, gallium and llvmpipe. It provides an enormous performance boost ove

[Javier Agustìn Fernàndez Arroyo]

what about adding this app too? its open source!

http://www2.cs.uidaho.edu/~jeffery/win32/wglgears.exe

http://www2.cs.uidaho.edu/~jeffery/win32/wglgears.c

from:

http://www2.cs.uidaho.edu/~jeffery/win32/

On Tue, Mar 21, 2017 at 7:10 PM, Pranay Pratyush 
wrote:

> Hi there,
> I have shared my GSOC proposal draft
> .
> It's really crude right now because I am yet to figure to go through all
> reactos code and figure out what exactly I need to do. Please comment on
> the proposal and help me improve it.
> Thank You
>
>
> --
> *Pranay Pratyush,*
> 3rd year undergraduate ,
> Computer Science and Engineering Department
> Indian Institute Of Technology, Kharagpur
> --
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [khornicek] 74209: [RAPPS] - Add a custom build of the Mesa 3D Graphics Library. This build contains mesa, gallium and llvmpipe. It provides an enormous performance boost ove

[Javier Agustìn Fernàndez Arroyo]

please please please write some user manual in wiki

plizzz

On Mon, Mar 20, 2017 at 9:44 PM, Jerome Gardou 
wrote:

> I have to say that I also like it very much :-) For having tried that, I
> can only stand in awe seeing someone mastering the whole stack needed to
> compile the damn thing on windows.
>
> Jérôme
>
>
>
> Le 20/03/2017 à 09:44, Kamil Hornicek a écrit :
>
>> Hi,
>> few other people asked me, but Jerome did it right. Mesa code base is
>> rather big and llvm is not small either. Integrating it in our building
>> process and keeping it in sync would require huge amount of effort. It
>> would also increase both the ISOs and the build time.
>>
>> It's much easier to download Mesa's sources for give or take every other
>> minor release and package it and I'm willing to do that.
>>
>> Kamil
>>
>> Dne 20.3.2017 9:06, Colin Finck napsal(a):
>>
>>> khorni...@svn.reactos.org wrote:
>>>
 [RAPPS]
 - Add a custom build of the Mesa 3D Graphics Library. This build
 contains mesa, gallium and llvmpipe. It provides an enormous
 performance boost over the software implementation present in
 opengl32.

>>>
>>> That sounds fantastic! I'm just wondering, if it is better than our
>>> current OpenGL software rendering in every regard, can't we just have it
>>> as the default in our tree?
>>>
>>>
>>> - Colin
>>>
>>> ___
>>> Ros-dev mailing list
>>> Ros-dev@reactos.org
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>
>>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

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

[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) <
gigah...@gmail.com> 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 <
> elh...@gmail.com> 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 <thomas.fa...@reactos.org>
>> 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 <co...@reactos.org> 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
>>>> Ros-dev@reactos.org
>>>> 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
>>> Ros-dev@reactos.org
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>
>>
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] JIRA/FishEye upgrade on March 8

[Javier Agustìn Fernàndez Arroyo]

hi there,

im not sure if this issue has raised because of this upgrade...

Go to web home and then click on "Live Activity" (at the botton of the page)
Shouldn´t it be public info?

>From upgrade, it asks you to login It didnt before upgrade

On Thu, Mar 9, 2017 at 8:11 PM, Colin Finck  wrote:

> Hi all!
>
> FishEye is back online as well now and currently indexing our
> repository. Due to the better performance of the new server, it does so
> nicely without taking down the entire JIRA and FishEye instances :)
>
> From my side, the entire upgrade is done now and all major bugs should
> have been fixed.
> If you still notice regressions, please report them! Note that some of
> them may need to be reported to Atlassian though as we basically use
> vanilla JIRA and FishEye installations.
>
> Cheers,
>
> Colin
>
>
> Am 08.03.2017 um 15:57 schrieb Colin Finck:
> > Hi all!
> >
> > I have successfully upgraded JIRA to the latest version 7.3.2 and
> > https://jira.reactos.org is back up!
> > Unfortunately, we already had the first regression report 15 minutes
> > later: https://jira.reactos.org/browse/ONLINE-682 :(
> >
> > Please check it out and tell me if anything else regressed.
> > I can try to fix any regressions tomorrow or we have to bring them to
> > Atlassian's attention.
> >
> > FishEye/Crucible continues to be the hard customer again and I probably
> > won't get it fully upgraded today. More will follow tomorrow.
> >
> > Cheers,
> >
> > Colin
> >
> >
> > Am 24.02.2017 um 19:35 schrieb Colin Finck:
> >> Hi all!
> >>
> >> Let me announce a definite date for our JIRA/FishEye upgrade:
> >>
> >>Wednesday, March 8, around 9:00 UTC
> >>
> >> Expect downtimes of several hours at https://code.reactos.org and
> >> https://jira.reactos.org around this time.
> >>
> >> I can say for sure that I will have enough time on this day and the
> >> following to deal with all possible incidents that could happen during
> >> the complex upgrade.
> >> This also allows me to get direct in-person feedback from all the devs
> >> attending CLT on the weekend after that :)
> >>
> >> The upgrade to JIRA 7.x is a major one, and Atlassian recommends
> >> everyone to have a look at the new features:
> >> https://confluence.atlassian.com/migration/jira-7/server_
> jira_product-changes
> >>
> >> Best regards,
> >>
> >> Colin
> >>
> >> ___
> >> Ros-dev mailing list
> >> Ros-dev@reactos.org
> >> http://www.reactos.org/mailman/listinfo/ros-dev
> >>
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Office (Excel, Word...) 2010 on ReactOS

[Javier Agustìn Fernàndez Arroyo]

that´s amazing!

congratulations! it´s wonderful to read such big news! :)

ReactOS (and you, devs, of course) is going to conquer desktop world! :)

On Wed, Feb 22, 2017 at 12:46 AM, Giannis Adamopoulos <
giannis.adamopou...@reactos.org> wrote:

> Jim completed the class rewrite years ago (with a great success) and afaik
> there is no other major rewrite/undertaking right now in win32k. Why do I
> have a feeling you plan some major undertaking?
>
> ReactOS Development List  wrote on Wed, February
> 22nd, 2017, 12:01 AM:
> > Hi all,
> >
> >
> >
> > Before touching parts of win32ss (user32/gdi32/win32k) I would like to
> know
> > what the status of different components are:
> >
> > -  James, have you finished with your win32 class rewrite? What’s
> > the status of it? Is there a bug report concerning this rewrite?
> >
> > -  Does anybody else currently work on cursors / GDI bitmap
> matters?
> >
> >
> >
> > Best,
> >
> > Hermès
> >
> >
> >
> >
> >
> > De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de victor
> > martinez
> > Envoyé : mardi 21 février 2017 23:35
> > À : ReactOS Development List
> > Objet : Re: [ros-dev] Office (Excel, Word...) 2010 on ReactOS
> >
> >
> >
> > Somehow it reminds me to the release/capture issues GIMP is showing with
> the
> > mouse:
> >  
> > https://jira.reactos.org/browse/CORE-11775
> >
> >   _
> >
> > De: Ros-dev  en nombre de Giannis
> Adamopoulos
> > 
> > Enviado: martes, 21 de febrero de 2017 11:50:04
> > Para: ReactOS Development List
> > Asunto: Re: [ros-dev] Office (Excel, Word...) 2010 on ReactOS
> >
> >
> >
> > Hi! This is excellent news! It's good to know that Samuel started working
> > again on ntlm. I guess the most productive way to help him complete it
> would
> > be to write several tests for it (and also convert Samuel's test to
> formal
> > tests). Not only will it help Samuel but will help you understand ntlm
> > yourself and then help Samuel. (It is not like I knew anything about
> > activation contexts before. It was the tests I wrote that helped me come
> up
> > with clever way to let our comctl32 really do what both versions of
> > comctl32).
> >
> > Keep up the good work!
> >
> > PS: regarding the capture problems I would suggest writing more tests!
> > (Win32k is so hard to come right that you are searching in the dark
> unless
> > you test it thoroughly). My instinct says that this is the same bug with
> the
> > spider solitaire where the last card isn't released when you win a game.
> > There is a bug report for that but I don't remember the number. I think
> that
> > if the mouse button is released we should also release capture (and this
> > needs testing, perhaps even interactive testing).
> >
> > Giannis
> >
> > ReactOS Development List < 
> ros-dev@reactos.org>
> > wrote on Tue, February 21st, 2017, 2:59 AM:
> > > Hello everyone,
> > >
> > > Today I was finally able to finish the installation of Office 2010 in
> > > ReactOS, using as a temporary measure the Wine’s NTLM layer that calls
> > into
> > > the ntlm_auth utility of Samba. This was done while Samuel is
> completing
> > his
> > > NTLM implementation.
> > > As this wine layer is here running on ReactOS, few modifications were
> > > needed, and I also needed to find a Windows build of Samba. I’ve found
> > one,
> > > by chance, at http://smithii.com/samba . Then, using ReactOS revision
> > 73868
> > > (or later), and using this version of Samba, the Office installation
> > > finishes (reminder: the problem was due to the fact the installer
> needed
> > > NTLM to communicate with the “Office Software Platform Service”,
> > > OSPPSVC.EXE). We are now able to use Excel, Word, … on ReactOS, as
> shown
> > in
> > > this picture:
> > > http://i.imgur.com/fLEwoVI.png
> > >
> > > There are now 2 main problems:
> > > - NTLM should be correctly implemented;
> > > - There are an awful lot of drawing problems with Office 2010
> applications
> > > (similar to those of Office 2007 apps): for example, dragging the graph
> > > downwards shows his frame going upwards; there are many black regions
> that
> > > show up, etc...: It seems we have problems in coordinate frames. And
> other
> > > problems too. Also, we have some mouse capture problems: if you try to
> > > redimension the windows the normal way (bring mouse cursor on top of
> the
> > > border, left-click-maintained, move mouse, release left button), and
> then
> > > move the mouse inside the window, it continues to be redimensioned...
> > > As a result, I took ~=15 minutes to make this simple trivial picture
> > above,
> > > almost all the time taken to fight against window dimensioning & the
> > drawing
> > > problems.
> > >
> > > But anyways, enjoy !
> > >
> > > This will be part of my next blog report.
> > >
> > > Cheers,
> > > Hermès
> > >
> > >
> > > 

Re: [ros-dev] Microsoft switched to Git

[Javier Agustìn Fernàndez Arroyo]

why change a working solution?

its a questin i have done myself many times :P

On Wed, Feb 15, 2017 at 3:18 PM, Brandin L Claar 
wrote:

> Just move everything to GitHub:
>
> https://github.com/blog/966-improved-subversion-client-support
>
> -brandin
>
> On Feb 15, 2017, at 06:32, ros-dev-requ...@reactos.org wrote:
>
> Send Ros-dev mailing list submissions to
>ros-dev@reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>http://www.reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
>ros-dev-requ...@reactos.org
>
> You can reach the person managing the list at
>ros-dev-ow...@reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
>
> Today's Topics:
>
>   1. Re: Microsoft switched to Git (Ged Murphy)
>   2. Re: Microsoft switched to Git (David Quintana (gigaherz))
>   3. Re: Microsoft switched to Git (Colin Finck)
>   4. Re: Microsoft switched to Git (David Quintana (gigaherz))
>   5. Re: Microsoft switched to Git (Colin Finck)
>
>
> --
>
> Message: 1
> Date: Wed, 15 Feb 2017 11:04:52 -
> From: "Ged Murphy" 
> To: "'ReactOS Development List'" 
> Subject: Re: [ros-dev] Microsoft switched to Git
> Message-ID: <004701d2877b$55983010$00c89030$@gmail.com>
> Content-Type: text/plain;charset="utf-8"
>
> I think the easiest path is to switch to a centralized style model using
> git.
> That is, we have a master copy (aka trunk) that gives the feel of our
> existing model. That would allow devs that prefer SVN to mostly continue
> working as before, and give the devs who want to use git in a more
> traditional way the ability to branch off and work in a git style manner,
> then sync their changes back into 'trunk'.
>
>
> -Original Message-
> From: Ros-dev [mailto:ros-dev-boun...@reactos.org
> ] On Behalf Of Colin Finck
> Sent: 15 February 2017 10:53
> To: ros-dev@reactos.org
> Subject: Re: [ros-dev] Microsoft switched to Git
>
> Am 15.02.2017 um 11:35 schrieb David Quintana (gigaherz):
>
> The number doesn't matter. The ReactOS project can't afford to lost
>
> any long-time members. Git would be a benefit for all of us, but it
>
> has to be a benefit for ALL of us.
>
>
> Let's not forget:
>
> - Part of the reasons developers had against Git may have been resolved by
> now.
> - Part of the problem may be that "Git is so different" to some devs, but
> I think this can be resolved by a detailed Wiki article showing how to do
> the same thing in SVN and Git. We already wrote such articles for
> TortoiseSVN after all!
> - And finally, we first need a plan for a Git move that doesn't suck. We
> tried SubGit and it failed for us. Then there is the "Merge workflow",
> which is supported very well by all tools, but creates a lot of parallel
> history. The "Rebase workflow" is more like what SVN does (keeping a linear
> history), but no idea how to enforce that with TortoiseGit.
>
> I think if a team could look after these things and help moving each and
> every developer towards Git, it may even be doable for us.
>
> Cheers,
>
> Colin
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
>
> --
>
> Message: 2
> Date: Wed, 15 Feb 2017 12:18:40 +0100
> From: "David Quintana (gigaherz)" 
> To: ReactOS Development List 
> Subject: Re: [ros-dev] Microsoft switched to Git
> Message-ID:
>
> Content-Type: text/plain; charset="utf-8"
>
> My belief is that the best path would be:
>
> Phase 0: This is how we are now. We have SVN master (trunk), and a
> read-only git mirror, and a semi-updated github mirror for when a
> contributor really wants to submit git PRs.
>
> Phase 1: Switch to using Git with PRs for submitting patches (Github's PR
> system is really really nice these days, but other solutions exist). Setup
> a SVN mirror "bot" that creates one svn commit for each push/merge detected
> in the master branch, and allows the buildbots to continue working as they
> do now.
>
> This would allow the existing svn-patch workflow to continue working, but
> commits on svn wouldn't be allowed anymore. Developers are expected to at
> least TRY to learn to use git (it's not that hard! I promise!).
>
> Phase 2: We switch the buildbots and testbots to pull from git, enable
> testbot access for git PRs (such as with a github bot that responds to
> "@rosbot runtest" or similar). The SVN mirror remains, for archival
> purposes, but git commits aren't merged so regularly. Release tags/branches
> can still be published through SVN, for ease of access.
>
> Phase 3: 

Re: [ros-dev] Bootlogos for FOSDEM (was: "RE: FOSDEM 2017 - It's happening!")

[Javier Agustìn Fernàndez Arroyo]

i choose *d*

On Sat, Jan 28, 2017 at 8:53 PM, Alexander Rechitskiy 
wrote:

> d is the best
>
> 28.01.2017, 19:04, "Hermès BÉLUSCA-MAÏTO" :
>
> Hello everyone,
>
> Upon an idea by Jared Smudde I modified a bit the ReactOS bootlogo to
> incorporate in addition the FOSDEM logo in it. See
> http://polariton.ad-l.ink/6WhjqNRrM/image.png or the attached file.
> I have done several versions and I would like to hear what you think from
> them (if possible, make a choice).
>
> Regards,
> Hermès
>
>
> -Message d'origine-
> De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de Colin
> Finck
> Envoyé : jeudi 26 janvier 2017 00:16
> À : 'ReactOS Development List'
> Objet : [ros-dev] FOSDEM 2017 - It's happening!
>
> Hi all!
>
> Hermès and me have just decided to go to FOSDEM this year. Which is a
> really good idea considering that we have a booth to staff there ;)
>
> Planning is currently happening at
> https://docs.google.com/document/d/1ofYUc7j0XwDH9SmNlGzNZlO8jOGho
> PUn7KTRcFmanIc
> Just request access if you're a ReactOS member and like to add or comment
> stuff there.
>
> Hermès will be preparing an ISO in the upcoming days. Please test current
> trunk to see if any last minute fixes need to go there. If you have ideas
> what cool apps we shall show at FOSDEM, please also share them here.
> We will go with burning and giving away CDs again (hopefully the last time
> before USBs do it).
>
> I hope that this definite plan will also motivate others to join us or
> visit our booth! :)
>
>
> Cheers,
>
> Colin
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> ,
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> --
> Best regards,
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Invitation to join ReactOS Deutschland e.V.

[Javier Agustìn Fernàndez Arroyo]

i guess this is only for developers, isnt it?  :)

On Sat, Nov 12, 2016 at 6:35 PM, Colin Finck  wrote:

> Hi all,
>
> This invitation is long overdue: Back in 2009 when our German foundation
> ReactOS Deutschland e.V. was established, it was merely the legal entity
> to handle the small amount of incoming donations.
>
> Today, things have drastically changed: Our fundraising campaign in 2014
> as well as the successful website relaunch and 0.4 release brought us
> many more funds. By establishing scholarships and contracting IT
> freelancers, ReactOS Deutschland e.V. is actively funding the actual
> ReactOS development. Apart from that, it is sponsoring and planning the
> presentation of ReactOS on popular Open-Source exhibitions.
>
> Furthermore, we have created an English translation of our Articles of
> Association/Charter and moved to English reports a while ago.
> This finally allows non-German members to join.
>
> Therefore, I'm inviting all active ReactOS developers to join ReactOS
> Deutschland e.V. as active members. Needless to say, active members
> don't pay any membership fees and have full voting rights at our General
> Assembly. We usually have such a General Assembly every year and this is
> basically your only duty: Attend the General Assemblies so that
> decisions are backed by a strong majority.
> The only exception I have to make is that the members candidating for
> the Board need to be German speakers to communicate with the
> authorities. This is necessary from time to time.
>
> You find the Articles of Association as well as all annual reports on
> our website https://ev.reactos.org
> To become an active member, simply fill out the application at
> https://ev.reactos.org/files/Membership_Application.pdf and send it to
> me via mail. You can cross out the "Direct Debit Authorization", this
> part is only relevant for supporting members.
> Unfortunately, we're bound to snail mail and can't do applications
> electronically, because I need a real signature and proof of your
> application for the authorities.
>
> Looking forward to your applications! :)
>
>
> Cheers,
>
> Colin
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Pale Moon drops ReactOS support

[Javier Agustìn Fernàndez Arroyo]

4th scenario - App is actually "buggy" and doesnt check for any export.
We´re fucked up :P

On Fri, May 20, 2016 at 12:56 PM, Love Nystrom 
wrote:

> Correct me if I'm wrong (Alex?), but isn't the biggest difference
> between kernel 5.2 and 6.x that 6.x is *paging the kernel* ?
> (A huge design mistake if you ask me. One I bet will bite MS on the a**.
> If the kernel gets too fat it needs liposuction, not paging.)
>
> IMHO, adding new APIs, while keeping the (non-paging) kernel seems ideal.
>
> Best Regards
> // Neo
>
>
> On 2016-05-19 05.43, ros-dev-requ...@reactos.org wrote:
>
> Subject:
> Re: [ros-dev] Pale Moon drops ReactOS support
>
> From:
> Alex Ionescu  
>
> Date:
> 2016-05-19 02.33
>
> To:
> ReactOS Development List  
>
> I don't believe I said 'let's add random exports to our DLLs'. In
> fact, in your old thread, I was totally FOR your idea, I even wrote
> that the only sane way of doing it is with the app compat work.
>
> On Wed, May 18, 2016 at 9:27 PM, Timo Kreuzer  
>  wrote:
>
> > We have been discussing this before and I wonder that Alex is not heavily> 
> > opposing the idea of randomly adding new exports to our user mode DLLs. It> 
> > is a well known fact that applications check for existance of exports to> 
> > decide how to behave, so ... not going to go over this again.>> To addess 
> > this issue I suggested to implement a compatibility layer. And> there was a 
> > detailed discussion about that on this mailing list.> 
> > https://www.reactos.org/pipermail/ros-dev/2015-March/017216.html>> Please 
> > take your time to read the whole thread again so we can avoid wasting> 
> > time, talking about the same things again.>> Timo
>
>
> --
> There is one thing stronger than all the armies in the world,
> and that's an idea whose time has come. [Victor Hugo]
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Pale Moon drops ReactOS support

[Javier Agustìn Fernàndez Arroyo]

just a side note... NT5.0 is Win2k we are targetting NT5.2

On Tue, May 17, 2016 at 9:09 PM, Alberto Vaudagna <
alberto.vauda...@gmail.com> wrote:

> Alex  also does the NT5.0 kernel not have patch guard support?
> It should be a good "secure" feature to add?
> So there is not that many change on karnel side between 5.0 and win10 one
> a part from the secure kernel stuff?
>
>
>
> 2016-05-17 20:58 GMT+02:00 Riccardo Paolo Bestetti <
> riccardo.kyo...@live.it>:
>
>> Il 17/05/2016 20:23, Magnus Johnsson ha scritto:
>>
>> I am an utter scrubnub, but has followed this mailing list for.. more
>> than a few years. Its not unheard of to get an angry response to a commit
>> saying that its an API that is newer than the targeted version.
>>
>> Being a scrubnub lurker I can't help but think that being somewhat
>> agressive on compatibilty modes would be nice, but.. I'll shut up now :').
>> Just wanted the "people are angry when non-targeted versions of API's are
>> implemented" thrown in there.
>>
>> +1 to this, forgot to mention it.
>>
>>
>> Il 17/05/2016 20:04, Alex Ionescu ha scritto:
>>
>> The project doesn't have to be hard-coded to NT5. For example, I am
>> building a UEFI loader/bootmgr based on Windows 10, because 2003
>> doesn't boot on UEFI systems.
>>
>> That being said, I don't see any good reason for us not to still
>> mainly focus on 2003 for the kernel. The kernel is NOT what's
>> preventing apps from working, or hardware from working. What's
>> preventing that from working is:
>>
>> 1) Lacking user-mode APIs, and in some cases Rtl APIs (sure, implement
>> Win 10 ones!)
>> 2) Lacking hardware support for things like UEFI (I'm working on it),
>> AHCI (we have a student working on it), USB 3 (someone can implement
>> this...but USB 2 barely works), etc..etc..etc..
>>
>> Find me a single device driver that *only* works on NT 6... Server
>> 2003 is still a support MS OS, so by definition there's still drivers
>> for it.
>> Best regards,
>> Alex Ionescu
>>
>> Hello Alex,
>>
>> You can definitely focus on 2003 for the kernel, however keep in mind
>> that you would be re-implementing 14 years that is an advanced state of the
>> process of migration towards new software.
>> Yes, user-mode APIs and lacking hardware support is what prevents apps
>> from working now. Lacking kernel support is what will prevent apps from
>> working in a few years.
>>
>> A clear example: most of new Windows application are being written
>> against the .NET libraries, and the last version of .NET has already
>> dropped Windows XP support. I doubt you can run .NET 4.5 on a 2003 type of
>> kernel even if you implement the last user-mode interface (and afaik you
>> can't even do that unless you implement some parts of NT6), so this is
>> already significant portion of apps that ReactOS will never be able to run
>> if you stick to NT5. Unless you want to reverse .NET 4.5 too and rewrite
>> the it to run on NT5... The same goes for all other examples of this kind,
>> both from Microsoft and from 3rd party vendors.
>>
>> I've also found an example of a device driver that only works on NT6, and
>> in fact I didn't even have to look for it: it was the first device I saw on
>> my desk. Elgato Game Capture HD, and that's pretty much the entire YouTube
>> and Twitch gaming business (a multi-million dollar industry, for those who
>> aren't familiar with it).
>> Also, some of the newer printers in my father's business, as well as the
>> GPS navigation system map update driver for some of his trucks, to give
>> some "job industry" examples.
>>
>> Windows Server 2003 is definitely supported by Microsoft (which doesn't
>> mean it is supported by others, and it mostly isn't), but it is almost
>> dead, and it would only do harm to deny that.
>> Implementing NT5 with the "NT6" user-mode API would lead to an Open
>> Source Windows Vista, without the "wow Aero looks so cool" factor. Please
>> don't waste all the magnificent work you've done so far like this. :)
>>
>> Best regards,
>> --- *Riccardo Paolo Bestetti*
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Pale Moon drops ReactOS support

[Javier Agustìn Fernàndez Arroyo]

 "companies and such support NT5?"

where "support NT5", i meant "drop support for NT5", sorry

On Tue, May 17, 2016 at 4:43 PM, Javier Agustìn Fernàndez Arroyo <
elh...@gmail.com> wrote:

> And why does few developers, companies and such support NT5? Because MS
> dropped support for those systems. But if ReactOS revives that support,
> maybe companies will support us.
>
> On Mon, May 16, 2016 at 10:22 PM, Riccardo Paolo Bestetti <
> riccardo.kyo...@live.it> wrote:
>
>> I'd like to drop my two cents, just because I really believe in this
>> project's filosofy. Since things have gotten pretty hot in the past,
>> especially when someone who is not a developer intervened in a discussion,
>> let me apprise you that my only intention it to bring in the point of view
>> of a potential user that really wants to see ReactOS happen and isn't
>> emotionally attached to the work that has been done.
>>
>> The reality is that very very few manufacturers and developers still
>> support NT5 and all of them are going to drop support in the next few
>> years. This is just a fact. NT5 is legacy software and there's nothing no
>> one can do about that.
>>
>> I've followed this project and this mailing list for the past five years
>> and in this time I've upgraded all of the computer systems of my father's
>> business to Windows 7 and then to Windows 10, because all the pieces of
>> software they run dropped support for NT5, one after another. They still
>> have a single machine in the whole building running Windows XP, for legacy
>> software, and honestly they don't use it very often. In my school, pretty
>> much the same. And even if someone, for whatever reason, intends to run NT5
>> for 10 more years, why should (s)he re-setup all the systems again to run
>> ReactOS instead of keeping Windows XP?
>>
>> The point is, you can either implement the architecture that runs all of
>> the computer in building, or the architecture that runs that one legacy
>> machine. And even that would happen if and only if you can achieve 100%
>> compatibility with all of NT5 and Windows XP bugs and quirks and give
>> people a really good reason to reinstall the OS on such machines, and sorry
>> that's just not gonna happen.
>>
>> I get why some of you may want to stick to NT5, but you have to be aware
>> that if you do that ReactOS will never be used in the real world. No reason
>> to stick to NT5 is good enough, since no one out there needs or wants NT5.
>> Hell, it would probably be easier for a business to switch from NT6 to
>> GNU/Linux than to go back to NT5.
>>
>> Again, these are just the two cents of a guy that works in the field.
>>
>> Best regards,
>> --- *Riccardo Paolo Bestetti*
>>
>> Il 16/05/2016 16:42, Ged Murphy ha scritto:
>>
>> But you’re missing the point. The problem is that modern software is
>> leaving XP behind and focusing on Win7 as a minimum recommended requirement.
>>
>> What use is ReactOS if none of the modern browsers or applications will
>> run on it? It limits the OS to being a compatibility solution for older
>> software, or a POS device. No one really wants to see that.
>>
>>
>>
>> I think the best solution to start with is to keep reporting as 5.2 in
>> the kernel, but allowing developers to start moving to the NT6 model. An
>> mish-mash of NT5 and NT6 can co-exist as long things are done sensibly.
>> e.g. adding IO cancelation to our NT5 kernel isn’t going to make us
>> incompatible for XP’s drivers, but it allows us to implement an NT6 feature
>> which hugely benefits the OS. Other obvious candidates are unimplemented
>> areas such as the fltmgr . Why implement the 2k3 fltmgr when we can
>> implement a later fltmgr model which still loads older filter drivers.
>>
>>
>>
>> Usermode should also still report as win2k3 (at least in the short term),
>> but start to add NT6 APIs directly into the codebase instead of using a
>> shim. We then maintain a whitelist of processes that don’t run on ros due
>> to a minimum requirement issue, and they get a modified result from
>> VerifyVersionInfo (and friends) to a later OS version.
>>
>>
>>
>> The above changes keep things pretty simple to start with, and allow us
>> to move forward almost immediately with very little infrastructure work.
>>
>>
>>
>> Ged.
>>
>>
>>
>>
>>
>> *From:* Ros-dev [mailto:ros-dev-boun...@reactos.org
>> <ros-dev-boun...@reactos.org>] *On Behalf Of *Javier Agustìn Fernàndez
>>

Re: [ros-dev] Pale Moon drops ReactOS support

[Javier Agustìn Fernàndez Arroyo]

"Continue doing as it does now, keep the NT5.2 target, stabilize the
existing components, and develop the remaining components, all within the
limitations of NT5, or"

let´s try to get this to a stable stage, then we will think about NT6+

On Sat, May 14, 2016 at 3:25 PM, Hans-Peter Diettrich <drdiettri...@aol.com>
wrote:

> Javier Agustìn Fernàndez Arroyo schrieb:
>
>> And, ROS is not complete yet. Isnt it more reliable to try to get it
>> stable for NT5, then shitch to NT6?
>>
>> If we change now, we are leaving things undone and we will leave them
>> again when switching to NT7, and so.
>>
>
> +1
>
> I'd like to see a modular system, that can be configured for whatever
> compatibility - as far as possible. I could imagine a modular OO approach,
> with virtual methods where needed, with lack of performance being
> compensated by progress in hardware.
>
> DoDi
>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Pale Moon drops ReactOS support

[Javier Agustìn Fernàndez Arroyo]

And, ROS is not complete yet. Isnt it more reliable to try to get it stable
for NT5, then shitch to NT6?

If we change now, we are leaving things undone and we will leave them
again when switching to NT7, and so.

On Sat, May 14, 2016 at 8:48 AM, Javier Agustìn Fernàndez Arroyo <
elh...@gmail.com> wrote:

> isnt this a project to "revive WinXP/2k3"?
>
> i think there is no need to upgrade to NT6...
>
> Yes, we will get outdated, but if we revive NT5, probably ROS can get that
> support back. Not for XP, but ReactOS. And XP/2k3 apps will work again,
> with us
>
> On Thu, May 12, 2016 at 7:22 PM, Ged Murphy <gedmurphy.mailli...@gmail.com
> > wrote:
>
>> It might be worth putting a doc together listing the kernel parts we’re
>> missing, the areas which need changes, and the areas which can be left
>> as-is.
>>
>>
>>
>>
>>
>> *From:* Ros-dev [mailto:ros-dev-boun...@reactos.org] *On Behalf Of *Mark
>> Jansen
>> *Sent:* 12 May 2016 18:14
>> *To:* ReactOS Development List <ros-dev@reactos.org>
>> *Subject:* Re: [ros-dev] Pale Moon drops ReactOS support
>>
>>
>>
>>
>>
>> For the features where this is possible without kernel support,
>>
>> there is a mechanism in the pipeline that makes this possible: 'apphelp'
>>
>> Currently I am still working on the base layer,
>>
>> but when that is progressed a bit more we could integrate it more tightly
>> in the Ldr,
>>
>> so that it uses the target platform to apply automatic fixes (shims).
>>
>>
>>
>> Having said that, it might be worth to upgrade parts of the kernel (only
>> where it makes sense) to NT6 already,
>>
>> without exposing that to applications.
>>
>> Especially in new parts, as it would mean that something is written for
>> NT5 now, and first thing we do next is upgrade it to NT6.
>>
>>
>>
>>
>>
>> On Thu, May 12, 2016 at 6:39 PM, Zachary Gorden <drakekaizer...@gmail.com>
>> wrote:
>>
>> Quite a few 'userland' features of NT6 requires kernel support to
>> function properly. If we go in, it would be, do NT6 kernel and slowly
>> bring the userland up to NT6. But we don't have a fully working NT5
>> kernel yet, so
>>
>>
>> On Thu, May 12, 2016 at 8:34 AM, David Quintana (gigaherz)
>> <gigah...@gmail.com> wrote:
>> > If we do NT6, we may want to have latest NT6 instead of trying to stick
>> to
>> > an older one and having the same deprecation issue in a couple years?
>> >
>> > Also, what about the "idea" of keeping the majority of the kernel and
>> large
>> > part of the usermode NT5, but having compatibility profiles that
>> > implement/emulate NT6 API functions using the existing NT5 feature set?
>> Is
>> > that unrealistic?
>> >
>> > On 12 May 2016 at 14:39, Aleksey Bragin <alek...@reactos.org> wrote:
>> >>
>> >> Which again brings in the topic of updating the version we are
>> targeting.
>> >> Windows 7 would be a minimum target these days, IMO.
>> >>
>> >> Regards,
>> >> Aleksey Bragin
>> >>
>> >> On 12.05.2016 14:04, Ged Murphy wrote:
>> >>>
>> >>> Yeah it's nonsense. No one drops support for ReactOS, they drop
>> support
>> >>> for
>> >>> older versions of Windows which likely includes reactos too.
>> >>> If they were adding in ReactOS specific code, they were doing it
>> wrong.
>> >>>
>> >>> The bigger issue here is that a lot of apps are starting to drop
>> support
>> >>> for
>> >>> XP and recommend a minimum of Win7. If we don't do something about our
>> >>> insistence on sticking with 2k3, we'll soon be in a position where no
>> >>> browsers will run on ros, as well as a whole other list of apps.
>> >>>
>> >>> Ged.
>> >>>
>> >>
>> >>
>> >> ___
>> >> Ros-dev mailing list
>> >> Ros-dev@reactos.org
>> >> http://www.reactos.org/mailman/listinfo/ros-dev
>> >
>> >
>> >
>> > ___
>> > Ros-dev mailing list
>> > Ros-dev@reactos.org
>> > http://www.reactos.org/mailman/listinfo/ros-dev
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>>
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Pale Moon drops ReactOS support

[Javier Agustìn Fernàndez Arroyo]

isnt this a project to "revive WinXP/2k3"?

i think there is no need to upgrade to NT6...

Yes, we will get outdated, but if we revive NT5, probably ROS can get that
support back. Not for XP, but ReactOS. And XP/2k3 apps will work again,
with us

On Thu, May 12, 2016 at 7:22 PM, Ged Murphy 
wrote:

> It might be worth putting a doc together listing the kernel parts we’re
> missing, the areas which need changes, and the areas which can be left
> as-is.
>
>
>
>
>
> *From:* Ros-dev [mailto:ros-dev-boun...@reactos.org] *On Behalf Of *Mark
> Jansen
> *Sent:* 12 May 2016 18:14
> *To:* ReactOS Development List 
> *Subject:* Re: [ros-dev] Pale Moon drops ReactOS support
>
>
>
>
>
> For the features where this is possible without kernel support,
>
> there is a mechanism in the pipeline that makes this possible: 'apphelp'
>
> Currently I am still working on the base layer,
>
> but when that is progressed a bit more we could integrate it more tightly
> in the Ldr,
>
> so that it uses the target platform to apply automatic fixes (shims).
>
>
>
> Having said that, it might be worth to upgrade parts of the kernel (only
> where it makes sense) to NT6 already,
>
> without exposing that to applications.
>
> Especially in new parts, as it would mean that something is written for
> NT5 now, and first thing we do next is upgrade it to NT6.
>
>
>
>
>
> On Thu, May 12, 2016 at 6:39 PM, Zachary Gorden 
> wrote:
>
> Quite a few 'userland' features of NT6 requires kernel support to
> function properly. If we go in, it would be, do NT6 kernel and slowly
> bring the userland up to NT6. But we don't have a fully working NT5
> kernel yet, so
>
>
> On Thu, May 12, 2016 at 8:34 AM, David Quintana (gigaherz)
>  wrote:
> > If we do NT6, we may want to have latest NT6 instead of trying to stick
> to
> > an older one and having the same deprecation issue in a couple years?
> >
> > Also, what about the "idea" of keeping the majority of the kernel and
> large
> > part of the usermode NT5, but having compatibility profiles that
> > implement/emulate NT6 API functions using the existing NT5 feature set?
> Is
> > that unrealistic?
> >
> > On 12 May 2016 at 14:39, Aleksey Bragin  wrote:
> >>
> >> Which again brings in the topic of updating the version we are
> targeting.
> >> Windows 7 would be a minimum target these days, IMO.
> >>
> >> Regards,
> >> Aleksey Bragin
> >>
> >> On 12.05.2016 14:04, Ged Murphy wrote:
> >>>
> >>> Yeah it's nonsense. No one drops support for ReactOS, they drop support
> >>> for
> >>> older versions of Windows which likely includes reactos too.
> >>> If they were adding in ReactOS specific code, they were doing it wrong.
> >>>
> >>> The bigger issue here is that a lot of apps are starting to drop
> support
> >>> for
> >>> XP and recommend a minimum of Win7. If we don't do something about our
> >>> insistence on sticking with 2k3, we'll soon be in a position where no
> >>> browsers will run on ros, as well as a whole other list of apps.
> >>>
> >>> Ged.
> >>>
> >>
> >>
> >> ___
> >> Ros-dev mailing list
> >> Ros-dev@reactos.org
> >> http://www.reactos.org/mailman/listinfo/ros-dev
> >
> >
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] ReactOS SVN Version Naming

[Javier Agustìn Fernàndez Arroyo]

what about changing "-" by "+"?

"0.4+SVNx"
that would mean, "this is the 0.4. version, plus svn revisions until x"


On Sun, Apr 10, 2016 at 11:25 PM, Mark Jansen 
wrote:

>
>
> This way of numbering seems very confusing to me, and I assume to other
> people as well..
> When ReactOS presents itself as 0.5-SVN, I would expect this to be a 0.5
> release, and not a 0.4 release that is working towards a 0.5.
>
>
> regards,
>
> Mark
>
>
> PS: I wasn't subscribed at the time this was sent, so sending a 'fake'
> reply :)
>
>
> *Ged Murphy* gedmurphy.maillists at gmail.com
>> 
>> *Mon Feb 29 16:07:49 UTC 2016*
>>
>> Because that’s what is being worked towards now, and there will be an
>> unknown number of point releases until it’s reached.
>>
>> It’s also a bit of nostalgia, it’s what we’ve always done :)
>>
>>
>>
>>>
>>> From: Ros-dev [mailto:ros-dev-bounces at reactos.org 
>>> ] On Behalf Of Hermès
>>> BÉLUSCA - MAÏTO
>>> Sent: 29 February 2016 16:00
>>> To: ReactOS Development List >> >
>>> Subject: [ros-dev] ReactOS SVN version naming
>>>
>>> Hi guys,
>>>
>>> I would like to understand what’s the rationale behind changing the ReactOS
>>> trunk version from “0.4-SVN” to “0.5-SVN” (see revision 70818) whereas we
>>> have just started to release ROS 0.4.0 only?
>>>
>>> Thanks in advance for your explanations!
>>>
>>> Cheers,
>>> Hermès.
>>
>>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (March 2016)

[Javier Agustìn Fernàndez Arroyo]

i dont have SVN password iirc, so i wouldnt be able to attend...

anyway, im not attending very much meetings in the last times sorry for
that

On Fri, Apr 1, 2016 at 5:39 AM, Colin Finck  wrote:

> Am 31.03.2016 um 02:18 schrieb Ged Murphy:
> > All our clients can log, in fact mine has logging turned on globally at
> all
> > times. It's pretty simple to upload one of those logs to reactos.org.
>
> rosev_ircsystem has the advantage that it logs live and offers the live
> log for download at a central location. No more interruptions like "I'm
> late, please hand me the logs". And no third party is later required for
> uploading.
> Apart from that, we've been using VoteBot several times.
> Personally, I also like to talk to people with real names on meetings
> (like we're also doing for serious stuff on the mailing lists).
>
> That said, I agree that the highly sensitive ReactOS Deutschland
> configuration may not be feasible for ReactOS Meetings.
> For the next meeting, I could offer everybody to log in with their SVN
> passwords instead of autogenerated ones. Would that help?
>
> It's your decision after all. Due to me being located in California
> right now, I won't be able to attend meetings on work days until June.
>
>
> Cheers,
>
> Colin
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] 502 Bad Gateway

[Javier Agustìn Fernàndez Arroyo]

Hello,

I am receiving this when trying to access website...

Is anyone having the same problem?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [akhaldi] 71057: [REISERFS] Import ReiserFS file system driver for Windows. It will be enabled later on. Brought to you by Peter Hater. CORE-11005

[Javier Agustìn Fernàndez Arroyo]

this is a candidate for "fix of the month"!

On Sat, Mar 26, 2016 at 11:42 PM, Alex Ionescu  wrote:

> Hide your wife.
> Best regards,
> Alex Ionescu
>
>
> On Sat, Mar 26, 2016 at 1:40 PM,   wrote:
> > Author: akhaldi
> > Date: Sat Mar 26 20:40:42 2016
> > New Revision: 71057
> >
> > URL: http://svn.reactos.org/svn/reactos?rev=71057=rev
> > Log:
> > [REISERFS] Import ReiserFS file system driver for Windows. It will be
> enabled later on. Brought to you by Peter Hater. CORE-11005
> >
> > Added:
> > trunk/reactos/drivers/filesystems/reiserfs/
> > trunk/reactos/drivers/filesystems/reiserfs/CMakeLists.txt   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/
> > trunk/reactos/drivers/filesystems/reiserfs/inc/gplntifs.h   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/bit_spinlock.h
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/bitops.h
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/config.h
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/errno.h   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/fs.h   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/jbd.h   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/journal-head.h
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/kernel.h
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/list.h   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/log2.h   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/module.h
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/nls.h   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/reiserfs_acl.h
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/reiserfs_fs.h
>  (with props)
> >
>  trunk/reactos/drivers/filesystems/reiserfs/inc/linux/reiserfs_fs_i.h
>  (with props)
> >
>  trunk/reactos/drivers/filesystems/reiserfs/inc/linux/reiserfs_fs_sb.h
>  (with props)
> >
>  trunk/reactos/drivers/filesystems/reiserfs/inc/linux/reiserfs_xattr.h
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/slab.h   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/spinlock.h
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/stddef.h
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/string.h
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/types.h   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/linux/version.h
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/reiserfs.h   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/inc/rfsd.h   (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/
> > trunk/reactos/drivers/filesystems/reiserfs/src/blockio.c   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/cleanup.c   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/close.c   (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/cmcb.c   (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/create.c   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/debug.c   (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/devctl.c   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/dirctl.c   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/dispatch.c   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/except.c   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/fastio.c   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/fileinfo.c   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/flush.c   (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/fsctl.c   (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/init.c   (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/lockctl.c   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/memory.c   (with
> props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/misc.c   (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/nls/
> > trunk/reactos/drivers/filesystems/reiserfs/src/nls.c   (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/nls/nls_base.c
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/nls/nls_big5.c
>  (with props)
> > trunk/reactos/drivers/filesystems/reiserfs/src/nls/nls_cp1251.c
>  (with props)
> >