Ros-dev January 2018

ros-dev@reactos.org

16 participants
14 discussions

[ros-diffs] [reactos] 01/02: [PSDK] Fix definition of INVALID_PROCESSTRACE_HANDLE as suggested by Thomas. #267

by James Tabor

Just curious, why does that just look so wrong to me....... https://git.reactos.org/?p=reactos.git;a=commitdiff;h=e3459ec36ecd783d67c27… commit e3459ec36ecd783d67c27dac4e81ad9facc08605 Author: Mark Jansen <mark.jansen at reactos.org <http://www.reactos.org/mailman/listinfo/ros-diffs>> AuthorDate: Sat Jan 6 21:09:51 2018 +0100 [PSDK] Fix definition of INVALID_PROCESSTRACE_HANDLE as suggested by Thomas. #267 --- sdk/include/psdk/evntrace.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sdk/include/psdk/evntrace.h b/sdk/include/psdk/evntrace.h index dbbc660963..7056f119fa 100644 --- a/sdk/include/psdk/evntrace.h +++ b/sdk/include/psdk/evntrace.h @@ -711,7 +711,7 @@ typedef struct _ENABLE_TRACE_PARAMETERS { PEVENT_FILTER_DESCRIPTOR EnableFilterDesc; } ENABLE_TRACE_PARAMETERS, *PENABLE_TRACE_PARAMETERS; -#define INVALID_PROCESSTRACE_HANDLE ((TRACEHANDLE)INVALID_HANDLE_VALUE) +#define INVALID_PROCESSTRACE_HANDLE ((TRACEHANDLE)(ULONG_PTR)INVALID_HANDLE_VALUE) #if defined(UNICODE) || defined(_UNICODE) >From W7U SDK rc: sdkinc.v7rc/Evntrace.h:93:typedef ULONG64 TRACEHANDLE, *PTRACEHANDLE; sdkinc.v7rc/Evntrace.h:1500:#define INVALID_PROCESSTRACE_HANDLE ((TRACEHANDLE)INVALID_HANDLE_VALUE) Did this break three of the build bots?

6 years, 8 months

*PREVIEW* : ReactOS 1st-stage GUI installer testing on Windows

by Hermès BÉLUSCA-MAÏTO

Hello everyone, Lately I was continuing working on my setup_improvements branch: https://github.com/HBelusca/reactos/commits/setup_improvements (whose main purpose, I recall, is to share a maximum of installation code between our working 1st-stage text-mode usetup and our 1st-stage GUI-mode reactos.exe setup that needs to be implemented). The last results of this is that I am now able to install ReactOS files to a user-provided directory using the GUI-mode setup! As Im developing under Windows I tested the file-copying part of the installer (which is, at the time of writing, the latest part of installation code I has been able to share between the two installers) on Windows. You can see the demo here: https://i.imgur.com/xF97hv1.gifv The animated gif also demonstrates the capability of the installer to halt file copying if the user pops the installation-cancel confirmation dialog out; file-copying is resumed when the user does not want to cancel the installation, but it is stopped when the user really cancels the installation. And of course, the file-copying status is displayed with an animated progress-bar. I have worked out a bit the wizard transitions, but some work remains to be done, especially for the partitioning step (currently Im hardcoding in the GUI installer the disk & partition where I want the copy to take place). One can note in the animation that the preparation of the list of files to be copied seems to take a while: indeed, the shared installation code works exclusively with NT paths. However, when this shared code is used in the win32 GUI-mode installer, this code calls inside setupapi.dll functions to manage the installation file queue (in usetup on the contrary, it uses instead a file queue implementation that works directly with NT paths). As a consequence, I need to convert the NT paths back to Win32 ones before feeding them into the setupapi functions, and this is not trivial. I want to improve this conversion by caching some of the computed results. Enjoy! Best regards, Hermès P.S.: Please dont put that on Twitter since this is under heavy work-in-progress and this demo hasnt been done under ReactOS at all.

6 years, 8 months

Creative sound cards drivers

by 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

6 years, 8 months

Postponing December Status Meeting

by Colin Finck

Hi all! If we follow our usual schedule, the December Status Meeting would be today. With such a late announcement and many people still on holidays, I suggest postponing it to next Thursday, January 4, 2018. Time will be 19:00 UTC as always. I already asked on #reactos-dev and got some approvals, so consider this the official meeting invitation :) This also gives you one week from now for agenda proposals. Additionally, we have got some new contributors in the recent months. If you think you should join the meeting or know somebody who should join, please let me know in advance. See you all next year! Colin

6 years, 8 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev January 2018