Ros-dev

ros-dev@reactos.org

5789 discussions

by Olaf Siejka

Dear colleagues I am very pleased to inform you that a new builder has been just made operational. Named Patch_x86_GCCWin Debug, you can see it waterfall right now. Based on x86 RBuild trunk, its capable of downloading a patch from bugzilla, applying it to trunk, building reactos testcd and running winetests on it via VBox sysreg. To use it, just pass revision, as well as Parameter 1, name id, value: attachement id. For example, http://www.reactos.org/bugzilla/attachment.cgi?id=5989 name: id, value: 5989 Just the same way you use source for vbox retesting. Right now test ISOs are stored, named with x86_Patch, revision and patch id. Logs itself will be also stored (when i bugfix them) If any issues arise, please mail me or catch me on irc.

13 years, 11 months

Fwd: [hm] Open Source Hardware Convention 2011 en Madrid

by Javier Agustìn Fernàndez Arroyo

Hi all, let me forward this email that i have received i dunno if this is useful for you, as its a *hardware *meeting, but anyway.... have a look and let me know! P.S.: email is in english language at the bottom ---------- Forwarded message ---------- From: Syvic <syvic(a)sindormir.net> Date: 2011/3/18 Subject: [hm] Open Source Hardware Convention 2011 en Madrid To: Hackmeeting <hackmeeting(a)listas.sindominio.net> Buenas, (Perdón si os llega por duplicado) Hoy, tras unos cuantos meses de curro, lanzamos al mundo las OSHWCon 2011: (Catalán e inglés más abajo) La OSHWCon <http://oshwcon.org/es> es un encuentro anual de 3 días que organiza el colectivo Synusia <http://synusia.es/> en un esfuerzo de difundir el uso delHardware Libre<http://es.wikipedia.org/wiki/Hardware_libre> y de promocionar la electrónica y la filosofía del «Hazlo tú mismo<http://es.wikipedia.org/wiki/Diy>». Tendrá lugar en el Centro de Formación Padre Piquer<http://www.padrepiquer.com/> de Madrid los *días 23, 24 y 25 de Septiembre de 2011*. Durante la OSHWCon se ofrecerán *charlas*, *talleres*, *mesas redondas*, exposición de *proyectos personales* y sobre todo, un *lugar de encuentro para profesionales y aficionados al mundo de la electrónica*. La *asistencia * es *libre y gratuita* y está pensada para que nadie se quede fuera. Se programarán desde actividades de iniciación, hasta charlas y talleres de alto nivel técnico. Estamos trabajando para que durante la OSHWCon todo el mundo disfrute aprendiendo, intercambiando conocimientos, concursando e incluso jugando con la electrónica o la robótica, siempre desde la filosofía del *Open Source Hardware*. Contamos con *cuatro espacios* para celebrar varias *actividades simultáneas*, de forma que siempre habrá algo que hacer. Si tienes algo que aportar, quieres compartir tu última creación electrónica, eres experto en cierta materia electrónica y deseas explicarlo al mundo, háznoslo saber en el apartado «Propón tu charla<http://jhl.synusia.es/propuesta_charla>». Mira antes el «Call4Papers <http://jhl.synusia.es/call4papers>» para obtener más información acerca de las actividades en las que estamos interesados. Si quieres saber más acerca de qué nos motiva a realizar este encuentro, consulta la página «Manifiesto <http://jhl.synusia.es/manifiesto>». Estáis todos invitados a participar, ya sea como visitantes o como ponentes durante la Con. *¡Te esperamos el fin de semana del 23 al 25 de Septiembre!* Recuerda inscribirte <http://jhl.synusia.es/inscripcion> en la web si tienes pensado asistir. Además, una vez finalizada la OSHWCon, pondremos a disposición de todo el mundo las grabaciones de todas las actividades. Sobre Synusia Synusia <http://synusia.es/> es el grupo de trabajo de electrónica establecido en el C.F. Padre Piquer <http://www.padrepiquer.com/> que organiza esta Con. Synusia nació de la necesidad de crear un punto de encuentro donde compartir libremente y profundizar en el conocimiento de diferentes tecnologías electrónicas y el OSHW. Si estás interesado en participar en la OSHWCon o en saber más acerca de Synusia, no dudes en mandarnos un correo (Encontrarás más información en nuestra página web<http://synusia.es/>). Cualquier sugerencia será bienvenida. CATALÀ La Convenció de Hardware Lliure, Electrònica i Robòtica<http://oshwcon.org/ca> és una trobada anual de 3 dies que organitza el col.lectiu Synusia en un esforç per difondre l'ús del Maquinari Lliure i de promocionar l'electrònica i la filosofia de “Fes-ho tu mateix<http://ca.wikipedia.org/wiki/Do_It_Yourself>” Tindrà lloc en el Centre de Formació Padre Piquer<http://www.padrepiquer.com/> de Madrid els dies *23, 24 i 25 de setembre del 2011*. Durant el OSHWCon s'oferiran *xerrades*, *tallers*, *taules rodones*, exposició de *projectes personals* i, sobretot, un lloc de trobada pels professionals i aficionats al món de l'electrònica. *L'assistència és lliure i gratuïta* i està pensada perquè ningú es quedi fora. Es programaran des d'activitats d'iniciació fins a xerrades i tallers d' un alt nivell tècnic. Estem treballat per a que durant la convenció tothom disfruti aprenent, concursant i, fins i tot, jugant amb l'electrònica o la robòtica, sempre des de la filosofia de l' Open Source Hardware. Comptem amb *quatre espais* per celebrar diverses*activitats simultànies*, de manera que sempre hi haurà alguna cosa a fer. Si tens alguna cosa per aportar, vols compartir la teva darrera creació electrònica, ets expert en certa matèria electrònica i vols explicar-ho a tothom, fes-nos-ho saber en l'apartat “Proposa la teva xerrada<http://oshwcon.org/ca/proposa>”. Mira abans el “Call4Papers <http://oshwcon.org/ca/call4papers>” per obtenir més informació sobre les activitats que realitzem. Si vols saber més sobre què ens motiva a realitzar aquesta trobada, consulta la pàgina “Manifest<http://oshwcon.org/ca/manifest> ”. Esteu tots convidats a participar, ja sigui com a visitants o com a membres actius de el OSHWCon. *T'esperem el cap de setmana del 23 al 25 de setembre! * Recorda inscriure't a la web si tens pensat assistir-hi. A més, una vegada finalitzat la convenció, posarem a la disposició de tothom els enregistraments de les activitats. Sobre Synusia Synusia <http://synusia.es/> és el grup de treball d'electrònica establert en el C.F. Padre Piquer <http://www.padrepiquer.com/> que organitza aquesta convenció. Synusia va nèixer de la necessitat de crear un punt de trobada on es pogués compartir lliurement y profunditzar en el coneixement de diverses tecnologies electròniques i el OSHW. Si estàs interessat en participar en el OSHWCon o en saber més sobre Synusia, no dubtis en enviar-nos un correu (Trobaràs més informació a la nostra pàgina web <http://synusia.es/>). Qualsevol suggerència serà benvinguda. ENGLISH Open Source Hardware, Electronics and Robotics Convention<http://oshwcon.org/en> is a 3-days event organized by the Synusia group in an effort to spread the Open Source Software <http://en.wikipedia.org/wiki/Open-source_hardware> and to promote Electronics and the philosophy of "do it yourself<http://en.wikipedia.org/wiki/DIY>". The event will take place in Madrid, in C. F. Padre Piquer<http://www.padrepiquer.com/>, from *23 to 25 September 2011*. During the OSHWCon, visitors will be able to watch and participate in *talks, workshops, round table discussions*,*personal projects exhibitions* and, above all, we'll offer a meeting place for professionals and amateurs of the world of electronics. *Attendance is free and open to everyone*. Activities are intended to be for everybody: from beginners to hi-level talks and workshops. Our objective is for everybody to enjoy learning, sharing knowledge, taking part or even playing with electronics and robotics throughout the OSHWCon... All of it from the Open Source Hardware philosophy. There are *four different rooms/halls* to hold several *simultaneous activities*, so there will always be something interesting to do. If you have something to contribute with, you want to share your latest electronic creation or you are an expert on some electronic matters and you want to explain it to the world, let us know in "Suggest your talk<http://oshwcon.org/en/suggestyourtalk>". Check out first "Call4Papers <http://oshwcon.org/en/call4papers>" for more information about the activities we are into. In case you wonder what make us organize this event, take a look at our "Manifesto<http://oshwcon.org/en/manifesto> ". You are all welcome to participate, either as a visitor or as an active member of the OSHWCon. *We'll be waiting for you on September 23 to 25!* Please, remember to register first on our site if you are intended to come. We'll also offer the recordings of every activity once the OSHWCon come to close. About Synusia Synusia <http://synusia.es/> is the working group established in C. F. Padre Piquer <http://www.padrepiquer.com/> that organizes this Convention. Synusia<http://synusia.es/> was born from the need of setting up a meeting point where sharing and deepen into the knowledge of different electronic technologies. If you are willing to participate in the OSHWCon or you want to know more about Synusia, feel free to send us an email (you'll find out more in our web site<http://synusia.es/>). Any suggestions will be welcome! _______________________________________________ HackMeeting mailing list HackMeeting(a)listas.sindominio.net https://listas.sindominio.net/mailman/listinfo/hackmeeting

13 years, 11 months

Choice of google summer of code project

by Andrew Green

I have been investigating a lot of aspects about theming, and my make that my proposal. Though I have been thinking that will not be of much valuable in the short term or in learning ongoing skills that will be needed in reactos. Of course on of the stated goals of gsoc or to give programmers the skills to contribute in the long term. So I was wondering what were your ideas on what would be considered valuable short term and what would give the skills to to help reactos in the long term. I know it is still 18 hours until google summer of code organizations are announced, but I'm sure reactos will be accepted. Any thoughts or suggestions would be much appreciated.

13 years, 11 months

After the release

by Olaf Siejka

Hiya I would like to point out to actions in my opinion necessary to be done after the release: 1. Syncing: Starting a new development/release cycle is the best moment for winesync to be performed. Syncing early will give us much time to find and wipe all Wine-originated bugs, which are simply unavoidable. The Winesync itself should be spreaded to as many revisions as its possible/feasible, as it will help out testers to regress-test any issues more precisely. Before Winesync can be performed, CMake branch should be synchronized with current trunk and the revision synchronized - locked up as reference frame for any Trunk-CMake comparison tests. We would not want CMake effort to be delayed due to any issues with WINE code in trunk. 2. Patches Now guys, i know i`m repeating myself, but please be warned that i will not drop this issue. The way our project is handling patches from outside is absolutely counterproductive. This is the only way new devs can be recruited and get commit access, but delays in reviewing and even reacting to patches is disgraceful. We are driving away potential newcomers, something no one should wonder about, if it often takes months for someone to write down a simple question about the patch content... We are risking a potential project dawnfall if we continue doing this way. I know you are busy with real life, project and other stuff, but seriously, this approach will only make things even more difficult. I did all things i could think of to help you out. Patches are now clearly tagged, listed in accessible way ( http://www.reactos.org/wiki/Bug_Filters ), i even tried to filter them, moving old and questionable stuff into separate directory (WIP aka Work in progress). Right now i took the more direct step of assigning patches to devs personally. It might be questionable, please react in such cases and comment, i will gladly relocate, but please do react. Due to Daniel recent issues and lack of free time, i volunteered for commit translation patches, at least those that can be done easily. Next thing planned here, is a builder dedicated to patch testing, but this is just a rough plan for futher discussion. I would be grateful for ANY feedback from you, perhaps some things could be done better/differently. Thanks in advance for your comments

13 years, 11 months

Last 0.3.13 tests

by Colin Finck

Hi all, The branch with all planned changes for 0.3.13 has been finished now and I've uploaded a first build: http://svn.reactos.org/prereleases/ReactOS-0.3.13-prerelease-r51045-bootcd.… It's now time to test this build out and update http://reactos.org/wiki/Tests_for_0.3.13 accordingly. mIRC has already been discovered as a prominent failing application, which just crashes upon connecting (see http://www.reactos.org/bugzilla/show_bug.cgi?id=6005). I consider this a release blocker bug, so some networking guy should look at it. - Colin

13 years, 11 months

[ros-diffs] [gadamopoulos] 51031: [win32] - Rafal Harabien:

by James Tabor

Hi all! Since everyone works so fast to ride my ass for breaking things, I hope one of you have a fix for this one and also hope this did not make it into branch! The commit breaks things, I wanted Michael to review the patch before hand. I'm sure any of the IRC archives can find my comments. Going on Holiday, James

13 years, 11 months

Re: [ros-dev] [ros-diffs] [fireball] 51013: [NOTEPAD] - Edijs: Zero initialize the caption string. See issue #5992 for more details.

by Aleksey Bragin

I made a mistake, this patch was written by Rafal Harabien. WBR, Aleksey Bragin. On Mar 11, 2011, at 1:07 AM, fireball(a)svn.reactos.org wrote: > Author: fireball > Date: Thu Mar 10 22:07:56 2011 > New Revision: 51013 > > URL: http://svn.reactos.org/svn/reactos?rev=51013&view=rev > Log: > [NOTEPAD] > - Edijs: Zero initialize the caption string. > See issue #5992 for more details. > > Modified: > trunk/reactos/base/applications/notepad/dialog.c

13 years, 12 months

Re: [ros-dev] [ros-diffs] [gedmurphy] 51011: FatCreateCcb has no params. Fixes building on msvc

by Gabriel ilardi

omg, glad to see you committing :-) > Date: Thu, 10 Mar 2011 15:37:51 +0000 > To: ros-diffs(a)reactos.org > From: gedmurphy(a)svn.reactos.org > Subject: [ros-diffs] [gedmurphy] 51011: FatCreateCcb has no params. Fixes building on msvc > > Author: gedmurphy > Date: Thu Mar 10 15:37:51 2011 > New Revision: 51011 > > URL: http://svn.reactos.org/svn/reactos?rev=51011&view=rev > Log: > FatCreateCcb has no params. > Fixes building on msvc > > Modified: > trunk/reactos/drivers/filesystems/fastfat_new/dir.c > > Modified: trunk/reactos/drivers/filesystems/fastfat_new/dir.c > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/filesystems/fastfa… > ============================================================================== > --- trunk/reactos/drivers/filesystems/fastfat_new/dir.c [iso-8859-1] (original) > +++ trunk/reactos/drivers/filesystems/fastfat_new/dir.c [iso-8859-1] Thu Mar 10 15:37:51 2011 > @@ -248,7 +248,7 @@ > } > > /* Set the file object */ > - Ccb = FatCreateCcb(IrpContext); > + Ccb = FatCreateCcb(); > FatSetFileObject(FileObject, > UserDirectoryOpen, > Dcb, > >

13 years, 12 months

Re: [ros-dev] [ros-diffs] [fireball] 50981: [NTOS/FSRTL] - Implement parameters checking i

by Pierre Schweitzer

Hi, this commits just shows you didn't understand how that function works. If you had, you wouldn't have said: "- Implement parameters checking in FsRtlIsNameInExpressionPrivate." It's already done. "- Add two shortcuts for common wildcard invocations to make the function faster." If you look at the algorithm, it will take at maximum as much loop iterations as name length. "- Second (main part of the function) is still under review." Thanks for discussing the issue with the original author of the algorithm, especially since you don't understand it. Furthermore, if you're not happy with said algorithm, you were asked to review it more than a year ago, and for at least 6 months. Thing that you NEVER did. So, now you discovered what my mail address is, contact me before committing anything wrong/useless to current code. And as you said less than a week ago, focus on fixing things that don't work, instead of rewriting working code. And as someone else also said once: 1:1 isn't the solution everywhere. Or if you think so, start dropping arwinss. Of course, don't take that personal, I like everyone ;-). Regards, P. Schweitzer

13 years, 12 months

Re: [ros-dev] [ros-diffs] [jimtabor] 50933: [Win32k|User32] - Clarify the meaning and the

by Johannes Anderwald

> Author: jimtabor > Date: Mon Feb 28 06:31:44 2011 > New Revision: 50933 > > URL: http://svn.reactos.org/svn/reactos?rev=50933&view=rev > Log: > [Win32k|User32] > - Clarify the meaning and the use of 0, 1 and 2 for user window regions, wine never did. Noticing patches not corresponding in correctness and understanding, leaving potential crashes in the DCE code, which depend on these types. > - Patch based on Rafal Harabien patch, fixes wine msg SetWindowRgn test, see also bug 5959. This change breaks Winamp 5.601: (ntoskrnl/ps/thread.c:119) PS: Unhandled Kernel Mode Exception Pointers = 0xF86A8568 (ntoskrnl/ps/thread.c:126) Code c0000005 Addr F87D4C3E Info0 00000000 Info1 00000020 Info2 00000000 Info3 00000020 *** Fatal System Error: 0x0000007e (0xC0000005,0xF87D4C3E,0xF86A8A50,0xF86A8690) [7hEntered debugger on embedded INT3 at 0x0008:0x808fd45c.bt Eip: <ntoskrnl.exe:fd45d (lib/rtl/i386/debug_asm.S:39 (RtlpBreakWithStatusInstruction))> Frames: <ntoskrnl.exe:a902 (ntoskrnl/ke/bug.c:1110 (KeBugCheckWithTf@24))> <ntoskrnl.exe:aa4d (ntoskrnl/ke/bug.c:1438 (KeBugCheckEx@20))> <ntoskrnl.exe:ead94 (ntoskrnl/ps/thread.c:129 (PspUnhandledExceptionInSystemThread))> <ntoskrnl.exe:eadaf (ntoskrnl/ps/thread.c:159 (_SEHExcept.39966))> <ntoskrnl.exe:fa9fa (lib/pseh/i386/framebased-gcchack.c:132 (_SEH2FrameHandler))> <ntoskrnl.exe:fcecb (lib/rtl/i386/except_asm.s:183 (RtlpExecuteHandler2))> <ntoskrnl.exe:fce9f (lib/rtl/i386/except_asm.s:150 (RtlpExecuteHandlerForUnwind))> <ntoskrnl.exe:3222 (ntoskrnl/ke/i386/exp.c:938 (KiDispatchException@20))> <ntoskrnl.exe:36bd (ntoskrnl/ke/i386/exp.c:1137 (KiDispatchExceptionFromTrapFrame@28))> <ntoskrnl.exe:6941 (ntoskrnl/include/internal/arch/../i386/ke.h:597 (@KiTrap0EHandler@4))> <ntoskrnl.exe:f7408 (ntoskrnl/ke/i386/trap.s:99 (VfIsVerificationEnabled@8))> <win32k.sys:bac39 (subsystems/win32/win32k/objects/region.c:2104 (@RGNOBJAPI_Lock@8))> <win32k.sys:bb0b3 (subsystems/win32/win32k/objects/region.c:3753 (NtGdiPtInRegion@12))> <win32k.sys:71bbb (subsystems/win32/win32k/ntuser/msgqueue.c:248 (@co_MsqInsertMouseMessage@4))> <win32k.sys:5ded4 (subsystems/win32/win32k/ntuser/cursoricon.c:205 (UserSetCursorPos))> <win32k.sys:66630 (subsystems/win32/win32k/ntuser/input.c:1134 (@IntMouseInput@4))> <win32k.sys:66cca (subsystems/win32/win32k/ntuser/input.c:194 (@ProcessMouseInputData@8))> <win32k.sys:66fbf (subsystems/win32/win32k/ntuser/input.c:308 (MouseThreadMain@4))> <ntoskrnl.exe:eac86 (ntoskrnl/ps/thread.c:156 (PspSystemThreadStartup@8))> <ntoskrnl.exe:5936 (ntoskrnl/ke/i386/thrdini.c:78 (KiThreadStartup@0))> <ntoskrnl.exe:eac22 (ntoskrnl/ps/thread.c:625 (PsCreateSystemThread@28))> WBR, Johannes

13 years, 12 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev