Ros-dev October 2010

ros-dev@reactos.org

31 participants
23 discussions

Re: [ros-dev] [ros-diffs] [jgardou] 49281: [PSDK] - Add MIDL_user_allocate and MIDL_user_free definitions - #ifdef a GCC hack

by Timo Kreuzer

Am 26.10.2010 18:01, schrieb jgardou(a)svn.reactos.org: > +#ifdef __GCC__ > /* Note: this should return a CLIENT_CALL_RETURN, but calling convention for > * returning structures/unions is different between Windows and gcc on i386. */ > LONG_PTR RPC_VAR_ENTRY > @@ -659,6 +663,13 @@ > NdrAsyncClientCall( PMIDL_STUB_DESC pStubDescriptor, PFORMAT_STRING pFormat, ... ); > LONG_PTR RPC_VAR_ENTRY > NdrDcomAsyncClientCall( PMIDL_STUB_DESC pStubDescriptor, PFORMAT_STRING pFormat, ... ); > +#else > +CLIENT_CALL_RETURN RPC_VAR_ENTRY NdrClientCall2( > + PMIDL_STUB_DESC pStubDescriptor, > + PFORMAT_STRING pFormat, > + ... > +); > +#endif > Is this hack even neccessary? I couldn't see any difference between gcc and msvc with the correct prototype. Both return the result in eax.

14 years, 10 months

Yarotows trunk integration

by Gregor Schneider

Hi, good to see the branch work back in trunk, I suspected this work would be left to rot and finally be forgotten (like in most other experimental branches). Altogether this looks like a huge step forward, got to test those mode switches it once I have enough time. One thing I noticed from the diffs is the eng/mem.c file, which exceeded my EVIL / HACK threshold. Is this supposed to stay - especially in the context of ARM3's to be proven awesomeness? --- snippet --- EngSecureMem(PVOID Address, ULONG Length) { return (HANDLE)-1; // HACK!!! } EngUnsecureMem(HANDLE Mem) { if (Mem == (HANDLE)-1) return; // HACK!!! } --- snippet --- Good work anyway, thanks to the people involved! Regards, Gregor

14 years, 10 months

Re: [ros-dev] Please tell me

by WaxDragon

You could always run two installs in different directories. On Oct 25, 2010 10:51 AM, "Bernd Blaauw" <bblaauw(a)home.nl> wrote: Op 25-10-2010 16:09, Fan Zhang schreef: > > Thanks. But I don't know if i run ReactOS, how could I replace the kernel file, such as ntoskrl... So basicly running a ReactOS installation with RosBE installed as application, sources downloaded and modified, and then you want a way to update files from this ReactOS installation itself? As long as ReactOS installs only on FAT filesystem, I guess you could use a DOS bootdisk/installation to overwrite any files. It's not entirely convenient. Is there basicly a set of lists of ReactOS files for the following: * which ReactOS files can be overwritten by a new file while you're still running in ReactOS? .inf files? small games like solitaire? * which ReactOS files can be overwritten, but require a reboot to be properly noticed? some drivers perhaps? * which ReactOS files require you to be outside of ReactOS in order to replace them? ntoskrnl comes to mind, explorer I guess All in all, mr Fan Zhang might be asking for some kind of update mechanism. If you had an old machine which you run ReactOS on, together with same casual data (audio files perhaps), do you need to reformat the disk to update ReactOS? or only remove the installation directory? or pick a different installation directory? or same directory? After all, you don't want to lose any user data. _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://ww...

14 years, 11 months

Please tell me

by Fan Zhang

Hi guys, I want to know how do you debug ReactOS. For example, when I change the code, I used to execute 'Make bootcd'. After that, I will install the ReactOS system by ReactOS.iso. So I'm confused if I have to install the whoe system after compiling. Do you have some easy way? Thanks. Fan

14 years, 11 months

(no subject)

by Mikhail Zuev

-- С уважением Михаил

14 years, 11 months

Introduction

by Oleg Baikalow

Hi, I thought I would drop a line here finally :) My name is Oleg, I am from Russia (some 180km from Moscow :)). I worked with Aleksey many years ago on some kernelmode networking-related tasks for Windows NT 4.0 and later Windows 2000. Your recent 0.3.12 release news was all over the place here on Russian news sites, my congratulations! ReactOS is a great project, though I never had enough time to actually start hacking, but recent achievements seems to motivate me more. What is situation with networking in ReactOS? I think this could be my main direction of work. I would glad if someone writes a current state of networking in ROS, so I would know where to start. // Oleg Baikalow.

14 years, 11 months

yarotows

by Timo Kreuzer

Hi everyone, I'd like to announce that I'm soon going to merge yarotows back into trunk, if no other regressions are found. The current issues (red icons and blue text on disabled buttons will be fixed, Kamil has already a fix.) Last chance to test and object ;-) Regards, Timo

14 years, 11 months

0.3.12 milestones status

by victor martinez

I am currently checking our 0.3.12 milestones. And the milestones status is: **********(Bug 5517)Some icons look wrong (blue background)********** There is a Hack for the release. **********(Bug5560): Adobe Acrobat Reader 7.1 throws exception at start**** This is a Wine regression. It is not in our hands.We have to wait for a Fix. **********(Bug 5472) comctl32: Keyboard shortcuts don't work after winesync*** Not as bad as it sounds. It does not work just in 2nd Installation Stage. Anyway, there is a Hack for this issue too. **********(Bug 5314) REGRESSION: Acrobat Reader: pen leak******* It is supposed to be fixed, but it is Bug5560 dependant so it is impossible to confirm the Fixed status. **********(Bug 5598) PATCH: Opera 9.64, FireFox 3.0+ crash when using Russian/Lithuanin/Ukrainian locale**** Reverting the *.nls changes solves the issue. There is a Hack attached. **********(Bug 5482)REGRESSION: ExplorerXP: black background on treeview area***** This is a Wine regression. It is not in our hands. We have to wait for a Fix. **********(Bug 4106) REGRESSION: Wrong text spacing in popup menus / icons after show a font in control applet / Remote Desktop******* It is a minor regression since it has been there for a while. Also Yarotows seems to fix some of the issues. **********(Bug 5591) REGRESSION: devmgr: wrong icons in the TreeView ***** Updating comctl32 will fix the issues. Or we can revert the comctl32 changes. ************** * Summing up * ************** There are 8 regressions. 4 has different options to be solved (Hack or Wine update/revert) 2 are current Wine regressions (we have to wait for a fix or revert Ole32/Comctl32 changes) 1 could be fixed (the Acrobar Reader leakage) but we need to fix Acrobat first(reverting?) 1 is a minor regression without a solution ( "Bug 4106") So we can solve 7/8 regressions. Is it time to think about a 0.3.12 release? It is time to take decisions (reverting/updating/waiting Fixes) since there are solutions. I don't think having the Trunk frozen is good for the project. So, opinions?

14 years, 11 months

ReactOS development cycle

by Olaf Siejka

I think its a good time to discuss current development cycle. It become clear to me, that there is no way we can currently adhere to 3 months development cycle. Its pointless to stick to something we managed to succeed only once or twice. Agreeing with the fact we do need releases, for various reasons, i would like to propose a new, longer cycle. The most apparent choices to me are 4 and 6 month ones. At least half of the cycle would be spent on all out development, with the following half turning its concentration to stabilizing trunk, searching for regressions and bugs, fixing them. The cycles would be separated by branching the release version. The actual release would be taking place on the first month of the NEXT DEVELOPMENT cycle. The actual emergency hacking, writing changelog etc. One month is more than enough, to release two RC (at the branching and next one - after two weeks). End of the month must result in final release. RC should be rather released internally for testing purposes on a default iso. The actual proposals are: 4 months: month 1: Development on version x. At the same time, the Release x-1 is to be final-tested, emergency-hacked, changelogged and shipped. The deadline is end of month 1. month 2: Development on version x. All development that can affect trunk stability, but also will not be shipped with the release X should end or be limited to branch only by the end of this month; month 3: Switching from development more to stabilizing trunk, searching for regressions, fixing bugs. Finalizing sub-projects that are to be included in release x; month 4; No new functionality/code, bug-fixing and hunting regressions. This month should end with branching for release x; 6 months: month 1: Development on version x. At the same time, the Release x-1 is to be final-tested, emergency-hacked, changelogged and shipped. The deadline is end of month 1. month 2: Development on version x; month 3: Development on version x. All development that can affect trunk stability, but also will not be shipped with the release X should end or be limited to branch only by the end of this month; month 4: Switching from development more to stabilizing trunk, searching for regressions, fixing bugs. Ongoing development work only for features that are to be shipped with release x; month 5: Switching from development more to stabilizing trunk, searching for regressions, fixing bugs. Finalizing sub-projects that are to be included in release x; month 6: No new functionality/code, bug-fixing and hunting regressions. This month should end with branching for release x;

14 years, 11 months

Goodbye Window Object

by James Tabor

Hi! Since I'm starting to move around now and fell better. Let's just say, I guess it's time to move from the window object and move to the wnd one. I have two local branches here on the portable system, one for Right to Left support (wine sync) I've started and the standard test one. I would like to have all the available Win32 developers help out. You too Ged! Try to get this done before to much goes into CMAKE and have to rework it all. >From window.h: /* Scrollbar info */ PSBINFOEX pSBInfo; // convert to PSBINFO /* Entry in the list of thread windows. */ LIST_ENTRY ThreadListEntry; } WINDOW_OBJECT; /* PWINDOW_OBJECT already declared at top of file */ /* Window flags. */ #define WINDOWOBJECT_NEED_SIZE WNDS_SENDSIZEMOVEMSGS #define WINDOWOBJECT_NEED_ERASEBKGND WNDS_ERASEBACKGROUND #define WINDOWOBJECT_NEED_NCPAINT WNDS_SENDNCPAINT #define WINDOWOBJECT_RESTOREMAX (0x00000020) // Set/Clr WS_MAXIMIZE & #define WINDOWSTATUS_DESTROYING WNDS2_INDESTROY <----- "WNDS2" state2 flag #define WINDOWSTATUS_DESTROYED WNDS_DESTROYED <----- "WNDS" state flag Move this to ntuser.h including the SBINFOEX too, not sure I did that one yet, and start hacking it then test the hell out of it. The flags just convert them to the correct ones, _RESTOREMAX may need more research (another word for HAX). Just writing this and it looks simple, but this is one file that effects the whole w32k tree. Thanks, James

14 years, 11 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev October 2010