Hi,
Guys(and Girls) did you heard about a program called "stress prime"?
It was developed to calculate prime numbers. And it is very sensitive
to small errors.
Since it has some kinda detecting errors, many overclockers are using
it to confirm overclocked H/W stability.
Yes, I tried to run this program, just for fun, and surprise! The
system is not overclocked, nor has problem when running stressprime on
WindowsXP.
The rounding error amount was huge. I saw the source code of the
stress prime and I'm sorry it was assembly language, so I couldn't
check what could make such prolem under ReactOS. It was all about the
math, and I'm not good at both(asm,math)
But, one thing sure, is something is not working properly(maybe
kernel?) and it is affecting ReactOS stability.
What is your opinion? any comments?
--
Regards,
Ashuaria Lee
Hi,
Alex Ionescu wrote:
> You should always use memset and void HEAP_ZERO_MEMORY.
Could you please tell why HEAP_ZERO_MEMORY should not be used?
It is used in many places, so if something wrong with RtlAllocateHeap, maybe
better to fix it?
Thanks,
Dmitry
hi,guys:
I don't know if it is proper to ask such a question here. I'm sorry if
I break some rules.
why IOCTL_DISK_GET_DRIVE_GEOMETRY_EX fail in windows 2000 and succeed in
windows xp and greater version?
or how can I get a disk(whatever,ATA,SCSI,USB )'s real size(including
additional sectors) in a easy way in windows 2000, just like there is such a
function,
__int 64GetDiskRealSize(HANDLE hDisk);
Could anybody help me?
Waiting for reply.
Thank you!
On Tue, Dec 9, 2008 at 12:58 AM, <jimtabor(a)svn.reactos.org> wrote:
> Author: jimtabor
> Date: Mon Dec 8 23:58:23 2008
> New Revision: 37952
>
> URL: http://svn.reactos.org/svn/reactos?rev=37952&view=rev
> Log:
> - Add CP_UNIXCP for CP_ACP, this will help cross tests.
>
> Added:
> trunk/reactos/include/reactos/wine/winnls.h (with props)
> +#ifndef __WINE_WINNLS_H
> +#define __WINE_WINNLS_H
> +
> +#define CP_UNIXCP CP_ACP
Rather than keep the include_next brokeness, perhaps we should add the
define to wine/port.h and include that in any offending source file.
--
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
Hi folks,
yesterday a user shows me a program what is working properly under windows,
but not working under reactos. It was an open source program and it was easy
to figure out the problem. It was an invalid win-api-call (wrong parameter
value). Due to this situation I would like to ask one question. How
compatible reactos should be? Even fault compatible?
Matthias
--
Matthias Kupfer Telefon +49 (0) 371 236 46 52
Wilhelm-Firl-Straße 21 Mobil +49 (0) 160 859 43 54
09122 Chemnitz
Steven Edwards wrote:
> We discussed something like this years ago. It would be nice if every sort
> of legacy API that has any sort of hacks for brokeness as part of its
> implementation, could be isolated and a simple recompile with something
> like a #define NO_LEGACY_WIN32 so you could recompile without the hacks.
> Not really that useful for the real world as you need the backward
> compatibility but it is a nice idea for embedded or non-normal windows
> targets like ARM.
I think this is like compiler warnings. Some checks are disabled by default
as they would cause more harm than good. But there is an option to enable
them. It will help to catch bugs in software.
>> It was already broken in r37496.
> Gdi is right Win32k is wrong.
I mean that GCC (by default) silently discards code like
if (i < 0) { ... }
where i is unsigned. So there was a bug in GDI...
Now that Stefan has cleaned up some stuff in the ddk headers, maybe we
should think of some additional design fixes here.
We currently have ntddk.h include "per version" headers: winxp.h,
win2k.h, winnt4.h. These contain very few stuff.
My suggestion is to merge them into winddk.h. We could also merge
winddk.h and ntddk.h
It might make sense to split wdm.h and ntddk.h into architecture
specific files
Layout suggestion:
- ntddk.h: includes wdm.h and contains arch-independent definitions
currently in winddk.h/win2k.h/winnt4.h
- wdm.h: includes arch-dependent headers, contains arch-independend wdm
definitions
- ddk_x86.h / ddk_x64.h, ddk_arm.h, ddk_ppc.h / ddk_mips.h:
arch-dependent definitions for both wdm.h and ntddk.h definitions
(#ifdef _NTDDK_ ...)
Comments appreciated.
Timo
What's the reason to copy & paste comments from ms headers?
Please remember: Interfaces are not copyrighted, header files (including
the comments) are!
> +//
> +// Types to use to contain PFNs and their counts.
> +//
> +typedef ULONG PFN_COUNT;
> typedef ULONG PFN_NUMBER, *PPFN_NUMBER;
> +typedef LONG SPFN_NUMBER, *PSPFN_NUMBER;
>
Hi! I'm sorry I broke the trunk.
About "extra" comma within braces, it is not a mistake. It is allowed.
There is a fragment of C grammar:
initializer
: assignment_expression
| '{' initializer_list '}'
| '{' initializer_list ',' '}'
;
Hello,
booting bootcd leads to a stackfault of VMWare, build server
experiences similar problems.
Trunk is locked with write access available to Dmitry Gorbachev to
fix the issue, and to anyone by request who has the fix.
WBR,
Aleksey Bragin.
On Dec 3, 2008, at 8:34 PM, dgorbachev(a)svn.reactos.org wrote:
> Author: dgorbachev
> Date: Wed Dec 3 11:34:49 2008
> New Revision: 37830
> -static FREELDR_SETTINGS Settings = { 0, {0}, 0 };
> +static FREELDR_SETTINGS Settings = { 0, { 0, }, 0, 0, FALSE };
I suspect there is a typo in the above line ("extra" comma within
braces, should've been something like 0, {0, 0}, 0, FALSE instead
probably).
WBR,
Aleksey.
Hi Eric,
Just wanted to tell you that your patch is correct and the Release
Buildslave is failing as you can see from its log. For some reason, it
stopped cleaning properly today and also has weird file deletion issues
sometimes.
But as long as the patch builds on the Debug slave, it's correct in 99% of
all cases.
Wanted to finish this mail before you reverted in r37802, but I was too
slow. :-(
So, it's safe for you to reapply r37801 and it's here to stay!
Best regards,
Colin
On Nov 30, 2008, at 10:19 PM, gschneider(a)svn.reactos.org wrote:
> Author: gschneider
> Date: Sun Nov 30 13:19:45 2008
> New Revision: 37774
> - if (!(tmp = (char*)und_alloc(sym, len))) return NULL;
> + if (!(tmp = und_alloc(sym, len))) return NULL;
You might want to keep these when syncing, it reduces compiler warnings.
Hello, everyone.
Since I'm new to this mailing list, I may ask stupid questions, so
don't be mad at me. ;-)
I was trying to get the status of east asian language support, but
couldn't find it in the wiki.
Could someone tell me some brief status about east asian support?
--
Regards,
Ashuaria Lee