Hello guys,
My name is Federico Montanari and I am a student. I am from Italy and I
hope to join to ReactOS Team as web developer.
My skills:
- English and Italian Languages
- HTML and CSS (I'm learning Drupal)
- Base of C (Not WIN32 API)
Timezone: UTC +1
ReactOS Account name: decodp
ReactOS IRC name: decodp
What Can I do here?
I can write some articles about ReactOS Status or something, fix online
bugs and I can be moderator of forum and wiki to delete spam.
This is my proposal. Have you got any idea?
I ready to work on team (especially ReactOS Team)
You are a great team! Thank you for your work on ReactOS (I wrote one
program in C and.. it was difficult :p)
With my greetings,
Federico Montanari
Hello ReactOS community!
My name is Vardan.
First of all I want to say thank you to all the members of this community
who helped me to figure out status of works and make a proposal for GSoC.
Also I want to express my gratitude to those who makes decision to accept
my proposal. It is very responsible for me to be accepted for this project.
You can be sure that I'll do my best to be able to meet your expectations.
For all other members of ReactOS community, I want to introduce myself. I
am 1st year master student from Armenia. I have about 2 years of Linux
Driver development experience. My GSoC project title is "Improve ReactOS
USB stack" and I will be very grateful for any help from anyone of you. I
can easily communicate on Russian and English.
During this month after submission and before acceptance I have done some
investigation of ReactOS and it's built environment. Related to RosBE I
want to express separate thanks to them who created such environment where
newbies like me are able to easily build and test ReactOS and it's drivers
(even with MSVS!). ReactOS wiki page is also very helpful!
I have started Investigation of NT driver concepts with "Microsoft Windows
Internals" book and some online articles. Any recommendations related
sources of information are strongly appreciated by me.
I hope that this GSoC project will be a good starting point for me, to join
to "very small and exclusive ranks of people who know how to do NT systems
development" :)
Best regards,
Vardan.
Thomas, the standard says:
"If one of the strings has an encoding prefix and the other doesn't,
the one that doesn't will be considered to have the same encoding
prefix as the other."
In other words, this now sends a wide-string to ASSERTMSG. Which is wrong.
Best regards,
Alex Ionescu
On Sun, Apr 24, 2016 at 5:14 AM, Thomas Faber <thomas.faber(a)reactos.org> wrote:
> On 2016-04-20 14:16, akhaldi(a)svn.reactos.org wrote:
>> [CLASSPNP] Fix MSVC build. Brought to you by Timo.
>
>> --- trunk/reactos/drivers/storage/classpnp/class.c [iso-8859-1] (original)
>> +++ trunk/reactos/drivers/storage/classpnp/class.c [iso-8859-1] Wed Apr 20 12:16:16 2016
>> @@ -877,7 +877,7 @@
>> status = devInfo->ClassStopDevice(DeviceObject, IRP_MN_STOP_DEVICE);
>>
>> ASSERTMSG("ClassDispatchPnp !! STOP_DEVICE should "
>> - "never be failed\n", NT_SUCCESS(status));
>> + L"never be failed\n", NT_SUCCESS(status));
>>
>> if(isFdo) {
>> status = ClassForwardIrpSynchronous(commonExtension, Irp);
>>
>
> This makes no sense to me at all. You're now concatenating a narrow and
> a wide string (which should be an error, but compilers suck), and
> passing it to a macro that calls RtlAssert -- which expects a narrow
> string.
> Am I missing something here?
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
Given there seems to be no place where s is checked for length, it would
be more appropriated to perform such as check:
if ((!joliet && strlen(s) > MAX_EXTENSION_LENGTH) || strlen(s) >
MAX_NAME_LENGTH)
Le 24/04/2016 20:59, spetreolle(a)svn.reactos.org a écrit :
> Author: spetreolle
> Date: Sun Apr 24 18:59:33 2016
> New Revision: 71201
>
> URL: http://svn.reactos.org/svn/reactos?rev=71201&view=rev
> Log:
> [CDMAKE]
> Don't check for extension length on Joliet images.
> Encountered with AHK binaries.
>
> ONLINE-567
>
> Modified:
> trunk/reactos/sdk/tools/cdmake/cdmake.c
>
> Modified: trunk/reactos/sdk/tools/cdmake/cdmake.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/sdk/tools/cdmake/cdmake.c?…
> ==============================================================================
> --- trunk/reactos/sdk/tools/cdmake/cdmake.c [iso-8859-1] (original)
> +++ trunk/reactos/sdk/tools/cdmake/cdmake.c [iso-8859-1] Sun Apr 24 18:59:33 2016
> @@ -692,7 +692,8 @@
> error_exit("'%s' is not ISO-9660, aborting...", filename);
> s++;
> }
> - if (strlen(s) > MAX_EXTENSION_LENGTH)
> + // Check for extension length
> + if (!joliet && strlen(s) > MAX_EXTENSION_LENGTH)
> {
> error_exit("'%s' has too long extension, aborting...", filename);
> }
>
>
--
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
On 2016-04-20 14:16, akhaldi(a)svn.reactos.org wrote:
> [CLASSPNP] Fix MSVC build. Brought to you by Timo.
> --- trunk/reactos/drivers/storage/classpnp/class.c [iso-8859-1] (original)
> +++ trunk/reactos/drivers/storage/classpnp/class.c [iso-8859-1] Wed Apr 20 12:16:16 2016
> @@ -877,7 +877,7 @@
> status = devInfo->ClassStopDevice(DeviceObject, IRP_MN_STOP_DEVICE);
>
> ASSERTMSG("ClassDispatchPnp !! STOP_DEVICE should "
> - "never be failed\n", NT_SUCCESS(status));
> + L"never be failed\n", NT_SUCCESS(status));
>
> if(isFdo) {
> status = ClassForwardIrpSynchronous(commonExtension, Irp);
>
This makes no sense to me at all. You're now concatenating a narrow and
a wide string (which should be an error, but compilers suck), and
passing it to a macro that calls RtlAssert -- which expects a narrow
string.
Am I missing something here?
Are you equally confused when Windows 10 Anniversary Update preview
builds also present themselves as such, even though it'snot coming out
until later?
Best regards,
Alex Ionescu
On Wed, Apr 13, 2016 at 9:31 AM, Javier Agustìn Fernàndez Arroyo
<elhoir(a)gmail.com> wrote:
> 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 <learn0more+ros(a)gmail.com>
> 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 <ros-dev at reactos.org>
>>>> 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(a)reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
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
> <ros-dev%40reactos.org?Subject=Re%3A%20%5Bros-dev%5D%20ReactOS%20SVN%20version%20naming&In-Reply-To=%3C005201d1730b%2456b98b90%24042ca2b0%24%40gmail.com%3E>
> *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 <http://www.reactos.org/mailman/listinfo/ros-dev>] On Behalf Of Hermès
>> BÉLUSCA - MAÏTO
>> Sent: 29 February 2016 16:00
>> To: ReactOS Development List <ros-dev at reactos.org <http://www.reactos.org/mailman/listinfo/ros-dev>>
>> 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.
>
>