Ros-dev

ros-dev@reactos.org

2 participants
5791 discussions

Re: [ros-dev] QEMU support broken!!!
by carlo.bramix 23 May '07

23 May '07

>From livecd-26861-rel it runs again under QEMU. Last tested image is livecd-26871-rel. Great job! Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ros-dev" ros-dev(a)reactos.org Cc : Date : Fri, 11 May 2007 17:21:55 +0200 Subject : Re: [ros-dev] QEMU support broken!!! > I just wanted to tell you that I downloaded and tested livecd-26700-rel.7z and it doesn't work yet. > > Sincerely, > > Carlo Bramini > > ---------- Initial Header ----------- > > >From : ros-dev-bounces(a)reactos.org > To : "ReactOS Development List" ros-dev(a)reactos.org > Cc : > Date : Fri, 11 May 2007 07:16:05 +0000 > Subject : Re: [ros-dev] QEMU support broken!!! > > > I also have a problem with booting LiveCD. > > Bugcheck in cmcontrl.c, line 151. > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > ------------------------------------------------------ > Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom > http://click.libero.it/infostrada > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom http://click.libero.it/infostrada

1 0

Re: [ros-dev] revision 26772, Mon May 14 03:18:42 2007 UTC
by jimtabor 23 May '07

23 May '07

Hi! > It should probably be > + Exp -= (1 - EXCESS); > in EFtoF() and > + Exp += (1 - EXCESS); > in FtoEF(). The other way round. > > No, this would break compatibility. The way to verify this. Write a driver, install it and send a packet to it, so to activate the test. Have the driver dump to WinDbg. > Suggestion to make it a little clearer: > #define BIAS 127 > Exp -+= (BIAS - 2); I know about the IEEE bias. I'm just using my old 68k code that I'm comfortable with. I'll change this later with the Dc handle stuff I'm still testing. Thanks, James

3 2

Re: [ros-dev] [ekohl] 26843: Update WIDL to rev 20070519.
by Aleksey Bragin 20 May '07

20 May '07

Hi, 2nd stage shows "Enable UsermodePnP failed", which doesn't appear with older WIDL. WBR, Aleksey Bragin. On May 20, 2007, at 3:02 AM, ekohl(a)svn.reactos.org wrote: > Author: ekohl > Date: Sun May 20 03:02:35 2007 > New Revision: 26843 > > URL: http://svn.reactos.org/svn/reactos?rev=26843&view=rev > Log: > Update WIDL to rev 20070519. >

1 0

Win32/Gdi32 Rewrite
by jimtabor 18 May '07

18 May '07

Hi all, On or about September 2006 I was asked by Aleksey (PC) and Alex if I could head up the win32 and gdi32 part of the rewrite. The discussion had taken place on irc. It was important that the rewrite would have one developer working alone (preferred method) or be the leading developer working with a small group of developers (no more than three). The rewrite was needed so that this section of ReactOS would be compatible with the new kernel and the very thing we are trying to do. Be compatible. This included interfaces, structures and the data that was contained in those structures. Just not only that, also dropping in the place of drivers and dlls, the real thing and still be compatible. Yes! Running with ReactOS. I do not recall any requirement for me to write a technical manual or any kind of web wiki. Even a How-To-Black-Box an OS interrupt calling hooky thingy with kmtest driver callback winpooch as an application interface. ReactOS developers should have a healthy tool box. This point on, the discussion is over. I have a job to do. I would like help and not debate everything I do. Some of you, need to, really think about, the future of this project. How can I help with this and how can I help make this work for compatibility with the very thing we are working toward. If you are thinking about something new and different other than something innovative, compatible and helpful? Maybe this project is not for you. Aros, FreeMint, Linux, Syllable, Visopsys, X, etc, these projects might be what you are looking for. If it breaks compatibility with interfaces and data stored in structures? I will reject it and post an email why it was rejected. Wine is not enough, okay? Thanks, James

1 0

revision 26772, Mon May 14 03:18:42 2007 UTC
by Timo Kreuzer 16 May '07

16 May '07

It should probably be + Exp -= (1 - EXCESS); in EFtoF() and + Exp += (1 - EXCESS); in FtoEF(). The other way round. Suggestion to make it a little clearer: #define BIAS 127 Exp -+= (BIAS - 2); jimtabor wrote: > --- trunk/reactos/dll/win32/gdi32/objects/painting.c 2006/12/28 22:36:53 25235 > +++ trunk/reactos/dll/win32/gdi32/objects/painting.c 2007/05/14 03:18:42 26772 > @@ -1,15 +1,66 @@ > [...] > +/* the following deal with IEEE single-precision numbers */ > +#define EXCESS 126L > +#define SIGNBIT 0x80000000L > +#define SIGN(fp) ((fp) & SIGNBIT) > +#define EXP(fp) (((fp) >> 23L) & 0xFF) > +#define MANT(fp) ((fp) & 0x7FFFFFL) > +#define PACK(s,e,m) ((s) | ((e) << 23L) | (m)) > [...] > +LONG > +FASTCALL > +EFtoF( EFLOAT_S * efp) > +{ > + long Mant, Exp, Sign = 0; > + > + if (!efp->lMant) return 0; > + > + Mant = efp->lMant; > + Exp = efp->lExp; > + Sign = SIGN(Mant); > + > +//// M$ storage emulation > + Mant = ((Mant & 0x3fffffff) >> 7); > + Exp += (1 - EXCESS); > +//// > + Mant = MANT(Mant); > + return PACK(Sign, Exp, Mant); > +} > + > +VOID > +FASTCALL > +FtoEF( EFLOAT_S * efp, FLOATL f) > +{ > + long Mant, Exp; > + gxf_long worker; > + > +#ifdef _X86_ > + worker.l = f; // It's a float stored in a long. > +#else > + worker.f = f; > +#endif > + > + Exp = EXP(worker.l); > + Mant = MANT(worker.l); > + > +//// M$ storage emulation > + Mant = ((Mant << 7) | 0x40000000 | SIGN(worker.l)); > + Exp -= (1 - EXCESS); > +//// > + efp->lMant = Mant; > + efp->lExp = Exp; > +} >

1 0

Re: [ros-dev] Bug into log10 function.
by carlo.bramix 16 May '07

16 May '07

Unfortunately, I just tested it into the latest working SVN build under QEMU (livecd-26665-rel) and this bug it is still into the CRT library. I also read the source code with SVN-WEB and it's still the same of 0.3.1. BTW, from livecd-26771-rel, a bad thing happens with QEMU: immediately after starting the boot, a blu screen appear with errors and everything is dead. Sincerely, Carlo Bramini ---------- This bug have already been fixed by me. log time ago. some time after 0.3.1 was relase or under 0.3.1 release process. plese use svn source code, and try make own build of reactos as well. the trunk is changes so fast, the code in 0.3.1 is already outdated in many areas. Citerar "carlo\\.bramix" <carlo.bramix at libero.it>: > While I was doing the final tests with ReactOS Calc before releasing the new > version, I discovered that it didn't work because a bug into log10 function. > This happens because the two operands are swapped into: > > \ReactOS-0.3.1\lib\crt\math\i386\log10_asm.s > > I attached the patch. > > Sincerely, > > Carlo Bramini. > > > > > ------------------------------------------------------ > Leggi GRATIS le tue mail con il telefonino i-mode di Wind > http://i-mode.wind.it/ > > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

Re: [ros-dev] Differences in Windows and Linux builds
by hto＠mail.cnt.ru 13 May '07

13 May '07

>> - At the boot screen, the version compiled under Windows shows >> "Service Pack 1" correctly, but the version compiled under Linux >> shows "Service Pac 1" > > I see this "Service Pac 1" in ReactOS compiled under Windows with GCC 4.1.2 (from RosBE). In ExpInitializeExecutive(): ... ANSI_STRING CsdString; ... RtlInitAnsiString(&CsdString, MsgEntry->Text); CsdString.Length -= sizeof(UNICODE_NULL); ... Why Unicode?

2 1

reactos.c compilation error
by Mikhail Y. Zvyozdochkin 13 May '07

13 May '07

Hi All Latest revisions of ReactOS produces compilation error at my system. Build Environment: RosBE 0.3.5b2 File: boot\freeldr\freeldr\reactos\reactos.c Error message (after 'make clean' and 'make'): cc1.exe: warnings being treated as errors boot\freeldr\freeldr\reactos\reactos.c: In function 'LoadAndBootReactOS': boot\freeldr\freeldr\reactos\reactos.c:524: warning: dereferencing type-punned pointer will break strict-aliasing rules mingw32-make: *** [obj-i386\boot\freeldr\freeldr\reactos\reactos.o] Error 1 WBR, DarkHobbit

1 0

tkreuzer r26742
by James Tabor 13 May '07

13 May '07

Sorry net split on irc. Physicus r26742 is right,,, I will change it this week once I have the rest of my changes ready. We should support 0x00010000 - 1 = 0xffff handles and it will give us 65K. Thanks James

1 0

Differences in Windows and Linux builds
by Colin Finck 12 May '07

12 May '07

Hello, After the latest Kernel changes, I noticed some differences in ReactOS builds compiled under Windows (RosBE 0.3.4) and under Linux (BuildBot and my 32-bit Ubuntu system): - At the boot screen, the version compiled under Windows shows "Service Pack 1" correctly, but the version compiled under Linux shows "Service Pac 1" - The version compiled under Linux hangs at "Flushing cache" for me, when I test it under VMware. Some other users also wrote that they could not run the latest ReactOS builds under QEMU. Although, I could not reproduce this problem with r26719, it might be related to these build differences. As I don't know, where this problem might originate from, maybe someone else could look at it. Regards, Colin

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev