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
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
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/
>> - 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?
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
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
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
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
