Ros-dev February 2010

ros-dev@reactos.org

26 participants
32 discussions

Re: [ros-dev] [ros-diffs] [sir_richard] 45525: [MISC]: Build fixes to sync up with latest changes. [SETUPLDR]: Do not build on ARM. On a side note, I offer a bountry for "if ARCH != ARM" support in .rbuild files, instead of only allowing ==.

by Hervé Poussineau

Hi, sir_richard(a)svn.reactos.org a écrit : > Author: sir_richard > Date: Tue Feb 9 04:05:49 2010 > New Revision: 45525 > > URL: http://svn.reactos.org/svn/reactos?rev=45525&view=rev > Log: > [MISC]: Build fixes to sync up with latest changes. > [SETUPLDR]: Do not build on ARM. On a side note, I offer a bountry for "if ARCH != ARM" support in .rbuild files, instead of only allowing ==. > I think <ifnot property="ARCH" value="arm"> ... </ifnot> will fit your needs Hervé

14 years, 7 months

Trap handler rewrite

by Timo Kreuzer

No doubt the new code is a huge advantage over the old code. Still there are some issues in my opinion. Currently the trap handlers are generated inside C code by a macro called KiTrap(), located in trap_x.h. This macro creates a C function, that uses KiTrapStub inline function to create the actual entry stub. KiTrapStub is 90% pure gcc inline assembly. At the end it does a jmp to the real C handler. Most C handlers will start processing with an inline function KiEnterTrap, which is C code with inline assembly functions like KiSetSaneSegments, Ke386GetFs. KiTrap06Handler/Trap0DHandler are exceptions, they use KiIsV8086TrapSafe to determine in inline assembly if we have a v86 trap. In this case KiEnterV86Trap is used instead of KiEnterTrap. KiTrap02 is also an exception, it's a pure C handler Now what's wrong? 1.) The gcc inline assembly is very compiler specific and MSVC unfriendly. The old method using GAS specific asm files was at least linkable with MSVC code. The new code needs porting. 2.) The current C code makes assumptions about what the compiler will do, ignoring the ABI, which requires that you do not change ds/es in C code, not even temporarily and that the direction flag is clear on function entry. The compiler might at any place use ds/es for whatever it likes. It must be a valid flat segment. Only using stack variables might work on the current gcc, but might fail on other compilers. A good example would be MSVC's use of __security_cookie, which is referenced on function entry through ds. I remember that not having cleared the direction flag in a trap handler caused strange random bugs in the past, we should avoid making this mistake again. KiTrapStub even changes esp inside C code (in cases where the function is entered without valid esp) Suggested modifications: Implement the trap entry functions in a pure assembly file, using assembly macros which would combine KiTrapStub and the segment handling part of KiEnterTrap. Trap exit could possibly be done this way as well. On the amd64 branch the C handlers return a status value back to the assembly stub, but a jump or call could be done as well. It would be possible to use ML for these assembly files as well. This works fine in the amd64 branch. Also strictly stick to C ABI instead of using compiler extensions and making assumptions about how the compiler works. It would improve portability, make the code safe and also more readable. And we would not really add more assembly, just move the current inline assembly to a pure assembly file. Possible performance disadvantages: I don't see any. We might end up with a jmp or call instruction more, but we can possibly safe this somewhere else. And maybe finally someone deletes the disgusting Ke386SetDs()... ;-) Regards, Timo

14 years, 7 months

Fwd: Mail delivery failed: returning message to sender

by Andrew Faulds

Hmm... either his email address is invalid, the server is playing up or it filters out UK addresses... ---------- Forwarded message ---------- From: Mail Delivery System <Mailer-Daemon(a)jovenclub.cu> Date: Fri, Feb 5, 2010 at 6:58 PM Subject: Mail delivery failed: returning message to sender To: ajfweb(a)googlemail.com This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: cl2raul(a)cha.jovenclub.cu SMTP error from remote mail server after RCPT TO:< cl2raul(a)cha.jovenclub.cu>: host 192.168.54.3 [192.168.54.3]: 550 5.1.1 <cl2raul(a)cha.jovenclub.cu>: Recipient address rejected: User unknown in local recipient table ------ This is a copy of the message, including all the headers. ------ Return-path: <ajfweb(a)googlemail.com> Received: from [192.168.250.1] (helo=mx1.jovenclub.cu) by tinored.jovenclub.cu with esmtp (Exim 4.63) (envelope-from <ajfweb(a)googlemail.com>) id 1NdTNq-000HgO-6D for cl2raul(a)cha.jovenclub.cu; Fri, 05 Feb 2010 18:58:26 +0000 Received: from mailnull by mx1.jovenclub.cu with spam-scanned (Exim 4.63 (FreeBSD)) (envelope-from <ajfweb(a)googlemail.com>) id 1NdTNq-000IDE-7k for cl2raul(a)cha.jovenclub.cu; Fri, 05 Feb 2010 18:58:28 +0000 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mx1.jovenclub.cu X-Spam-Level: X-Spam-Status: No, score=-1.2 required=4.0 tests=ALL_TRUSTED,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR autolearn=ham version=3.1.6 Received: from mail-pz0-f182.google.com ([209.85.222.182]) by mx1.jovenclub.cu with esmtp (Exim 4.63 (FreeBSD)) (envelope-from <ajfweb(a)googlemail.com>) id 1NdTNn-000ICP-09 for cl2raul(a)cha.jovenclub.cu; Fri, 05 Feb 2010 18:58:26 +0000 Received: by pzk12 with SMTP id 12so4356424pzk.13 for <cl2raul(a)cha.jovenclub.cu>; Fri, 05 Feb 2010 10:58:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=Qjk7GMbRPg6inIkmDQ9DobZkrya+x133yYcrqGKOV/s=; b=E7Ib+hPZq0DnQoANH+Nm+wXSRntTlNmh6rFqQQzQl9/mUB4U/lfGq2/2DAeL/3CSi4 qDexVPr9cJgfYJQgbrWenSF0AStaHKKPXnx8cLdXbgmTKuS/NxH3vp1wTE1PJmWwEA71 1OWpVC6onFv/M3rFvazpXkBl5Qj7IJk1wr7Hw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=iY13PwPYzh1Na4Qq70qyWEjChhA0VmqlvPgD9zjgwXB+PtIWJzISeq/Fa928RmuhLb y1mOwDTK3ucwm6AZ03TdGRwUV87eHbPn8AW16r8gdvIbzn6cPg8g+p6dBk9B9jP5YrCv hQY2IrCYgkLpRmsV1iyzmhxm0EJ4NDBHnP3Gc= MIME-Version: 1.0 Received: by 10.141.90.15 with SMTP id s15mr2119324rvl.137.1265396333097; Fri, 05 Feb 2010 10:58:53 -0800 (PST) In-Reply-To: < 41245.192.168.54.4.1265395610.squirrel(a)webmail.cha.jovenclub.cu> References: <41245.192.168.54.4.1265395610.squirrel(a)webmail.cha.jovenclub.cu > From: Andrew Faulds <ajfweb(a)googlemail.com> Date: Fri, 5 Feb 2010 18:58:33 +0000 Message-ID: <bac4c08c1002051058i494abe2oe655dd2a5ab4c9f1(a)mail.gmail.com> Subject: Re: [ros-dev] FLISOL 2010 To: cl2raul(a)cha.jovenclub.cu, ReactOS Development List <ros-dev(a)reactos.org> Content-Type: multipart/alternative; boundary=000e0cd1124eef34f0047edf0ac2 --000e0cd1124eef34f0047edf0ac2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Please do bear in mind ReactOS is in ALPHA, i.e. not suitable for normal use. If you want such a CD, my advice would be to download the debug version of reactos from the website and source code then burn the two files (the ISO and the zip file) to a CD. ReactOS has one CD if I remember correctly, that does all languages (If I'm wrong please correct me) Also, AFAIK ReactOS has no manuals, it has SOME documentation in the wiki, but overall it lacks much documentation. 2010/2/5 Ra=FAl Avila Catal=E1 <raul08012(a)cha.jovenclub.cu> > Hi for all the ReactOS community, soon brings near to him the FLISOL2010 > and want to take the CD that appears in the ReactOS page, since the > discharge from tub makes to him impossible for the limited bandwidth that > has in the island... > > Please if some interested party in collaborating, it need a CD that it > contains the operative system ( in Spanish ), the source code of ReactOS > and some manuals ( in Spanish )... > > I, will make oneself responsible for make copy them and distribute it for > the happening, in order that the Cuban community that has not access to > the Internet can obtain " the alternative of Windows ". > > They can me write directly to my address of post: > raul08012(a)cha.jovenclub.cu > > > R++ > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > --000e0cd1124eef34f0047edf0ac2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Please do bear in mind ReactOS is in ALPHA, i.e. not suitable for normal us= e. If you want such a CD, my advice would be to download the debug versi= on of reactos from the website and source code then burn the two files (the= ISO and the zip file) to a CD. ReactOS has one CD if I remember correctly, that does all languages (If= I'm wrong please correct me) Also, AFAIK ReactOS has no manuals= , it has SOME documentation in the wiki, but overall it lacks much document= ation. <div class=3D"gmail_quote">2010/2/5 Ra=FAl Avila Catal=E1 <<a href=3D"mailto:raul08012@cha.jovenclub.cu">raul08012(a)cha.jovenc= lub.cu</a>> <blockquote class=3D"gmail_quote" style=3D"margin:= 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left= : 1ex;"> Hi for all the ReactOS community, soon brings near to him the FLISOL2010<br= > and want to take the CD that appears in the ReactOS page, since the discharge from tub makes to him impossible for the limited bandwidth that<b= r> has in the island... Please if some interested party in collaborating, it need a CD that it contains the operative system ( in Spanish ), the source code of ReactOS<br= > and some manuals ( in Spanish )... I, will make oneself responsible for make copy them and distribute it for<b= r> the happening, in order that the Cuban community that has not access to the Internet can obtain " the alternative of Windows ". They can me write directly to my address of post: <a href=3D"mailto:raul080= 12(a)cha.jovenclub.cu">raul08012(a)cha.jovenclub.cu</a> R++ _______________________________________________ Ros-dev mailing list <a href=3D"mailto:Ros-dev@reactos.org">Ros-dev(a)reactos.org</a> <a href=3D"http://www.reactos.org/mailman/listinfo/ros-dev" target=3D"_blan= k">http://www.reactos.org/mailman/listinfo/ros-dev</a> </blockquote></div> --000e0cd1124eef34f0047edf0ac2--

14 years, 7 months

Debugging at the next level...

by Timo Kreuzer

Source level debugging thanks to MSVC and pdb files. Only the line numbers seem to be a bit off.

14 years, 7 months

ros-amd64-bringup! Surprise! No Region Leaks!

by James Tabor

Since this is true and the ros-amd64-bringup tree is up to date with the region and WND code I committed without the assumed fixes to the region leaks in my working tree,,,,,,,,,,, Also to note I was looking for a ghost,,,,, wasting my TIME!,,,, Is it possible to build ros-amd64-bringup in 32 bit mode? So,,,,, I can continue my work and commit my updates to head knowing I'm not the FFFf ff uf problem! FYFI: I just finished a point to point compare and the only differences are kernel changes! Thanks, James

14 years, 7 months

Re: [ros-dev] [ros-diffs] [tkreuzer] 45433: [NTOS] On MSVC implement _lgdt, __sgdt, __lldt, __sldt, __ltr and __str as assembly functions, because there is no inline assembly. The MSVC/ML64 built kernel now boots and WinDbg connects.

by Steven Edwards

On Thu, Feb 4, 2010 at 10:05 PM, <tkreuzer(a)svn.reactos.org> wrote: > Author: tkreuzer > Date: Fri Feb 5 04:05:51 2010 > New Revision: 45433 > > URL: http://svn.reactos.org/svn/reactos?rev=45433&view=rev > Log: > [NTOS] > On MSVC implement _lgdt, __sgdt, __lldt, __sldt, __ltr and __str as assembly functions, because there is no inline assembly. > The MSVC/ML64 built kernel now boots and WinDbg connects. And there was much rejoicing ;) -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo

14 years, 7 months

Kernel Crash per Rev 45401

by James Tabor

Seems to be very common. *** Fatal System Error: 0x0000007f (0x00000008,0x00000000,0x00000000,0x00000000) Entered debugger on embedded INT3 at 0x0008:0x808c6708. kdb:> bt Eip: <ntoskrnl.exe:c6709 (lib/rtl/i386/debug_asm.S:42 (RtlpBreakWithStatusInstruction))> Frames: <ntoskrnl.exe:9e6d (ntoskrnl/ke/bug.c:1110 (KeBugCheckWithTf@24))> <ntoskrnl.exe:35d7 (ntoskrnl/ke/i386/exp.c:1170 (KeRaiseUserException@4))> <ntoskrnl.exe:60cb (ntoskrnl/ke/i386/traphdlr.c:741 (@KiTrap09Handler@4))> <00000000> kdb:>

14 years, 7 months

would You try to implement The Microsoft Active Accessibility standarts to The Reactos?

by Mgr. Janusz Chmiel

Dear core developers of Reactos, I Am very nicely surpriced by The fact, that so complex project like developing new operating system from scratch based on Windows XP kernel and API functions calls exists. I tried to install The Reactos and i can tell You, that even visually impaired user can install Reactos to The empty computer harddrive without need to even make unattended installation. I was able to successfully install Reactos operating system to my computer. I Am now solving issue, how to install The driver for my sound cart when many functions of Reactos are for now only accessible with mouse. So please, if Reactos device manager is reporting, That The sound device is working correctly, but only multimedia adapter list item is presenting my Soundmax integrated digital audio sound cart, it do not means, that Reactos can automatically use this eevice without need to add The driver? I tried to install The driver by using The setup program provided with The driver, i unfortunately have got a error message, that setup has occurred an error and must be closed. Please check, if another instance of setup is not active. By using add new hardware wizard, could i install The driver by specifiing The exact location for this driver? It is The WDM based driver for Soundmax digital integrated audio, which is build in The motherboard of The IBM Thinkpat 2668. I would like to know, if Microsoft Active accessibility standards could be implemented on The future during developing Reactos. I found out, that oleacc.dll is being presented and is The part of The Reactos installation. But i do not know, if You could implement MSAA standarts, because knowing The API functions and The object methods and properties will not be probably enough to ensure, that MSAA standarts would work. I would like to test some screen reader, which is based on using API calls and by using MSAA calls, but i do not know, if it is implemented. My problems is now to add sound cart driver to test this. I Am advanced user with some advanced system administration knowledge, i know Windows operating systems starting with Windows for Workgroups 3.11 to Windows XP Professional. I can use Linux distributions to copy some needed files to The partition, where Reactos has been installed. I can even find necessary debug logs and send them as AN E-mails by using Linux distribution. Linux distro could help me in The situations, when Reactos can not give me some feetback. Installing sound driver manually by using registry editor is not easy task and i can not perform it without screen reader support. I Am surpriced by The stability of Reactos. Eventhough some API calls are not awailable for now, The kernel is very stable and i have never got some crash dialog Window informing me, that application has crashed, sorry for any problems. If You would try to think about implementation of MSAA, many visually impaired users would be very very glad because of it. And later, what about triing to implement some hod keys for controlling The user interface and for controlling The Explorer? Thank you very much, i Am ready for debugging and testing The Reactos. PS: I have never able to install and run Windows XP so quickly, without using Nlite program, which is able to modifi setup.sif file and some other files on Windows XP installation CD, i would never been able to perform The installation of commercial Windows XP myself. Only with Reactos, i could perform this without stress and without need to use some other external utility. I AM also very very glad, that Reactos is even able to work as a live CD. And here are some links for downloading freeware or opensource screen readers, which are fully compatible with Windows Xp and are not based on Display chaining manager DCM, which is too complex to implement even on future for You. Those screen readers are based on using API calls and on using MSAA standarts. Unfortunately, NVDA will not work, because some important libraryes are not The part of The installation of Reactos. It is probably wrong idea triing to mix original libraries from Microsoft with Yours operating system, because i think, that it could cause some confuses and often crashes. Because i can really constructively cooperate with You, i will send You The list of libraryes, on which NVDA screen reader is depend on. And here is The direct link for downloading latest stable version of NVDA, which do not have to be installed, You can only unzip it and place it on some directory on Yours Reactos installation. http://www.nvda-project.org/download/releases/nvda_2009.1_portable.exe I Am recommending You to join to The NVDA development mailing list. YOu will need to have YOur sound drivers properly configured. NVDA screen reader is by The default triing to load included Espeak speech synthesizer, which is The part of NVDA package. This speech synthesizer is written by using Microsoft Visual C++ express 2005, and The original source code of this speech synthesizer variant for WIndows has been modified so this synthesizer is not working like The SAPI5 compatible speech synthesizer, but like a Activex library, which can be called from NVDA. Espeak will very probably depend on wdmaud.drv and NVDA is also using winmm.dll library. The list of dlls, which NVDA is using will be sended on The separate E-mail. PS: Please, try to allow visually impaired computer users to use freeware and fully functional operating system, which is based on standarts of WIndows XP and 2003. If MSAA standarts are too complex to develope from scrath for You to prevent random crashes while using Yours future new dlls, which would come out from this standarts, i will understand it. You are working on very, very complex project while using legally obtained technical information from various sources. PS: I know, that it is not possible to use products, which are developed by Microsoft on other operating system, that on original operating system from Microsoft, so triing to donwload WIndows Internet Explorer 8.0 and triing to use it with Reactos will probably not be legal. But if it is so, never mind. There is Mozilla Firefox WEB browser, which is working with NVDA screen reader very nicely, and also Opera WEB browser is able to provide some accessibility support for visually impaired computer users. And Openoffice ORG is also working very nicely. But for now, i would atleast like to try, if NVDA can speak atleast somethink or if many API calls are not presented. Thank You for cooperation with me. With kindness regards. Janusz Chmiel

14 years, 7 months

SVN server

by Aleksey Bragin

Hi, we're upgrading the SVN server currently, which should finish shortly. It's in readonly state until the upgrade finishes. WBR, Aleksey Bragin.

14 years, 7 months

[ros-diffs] [evb] 45403: -

by James Tabor

My best guess or 45402 but~ the test bot is dead, I hope this is leading somewhere good and fast!

14 years, 7 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev February 2010