Hello,
I am going to move reactos/apps/tests in to rosapps as the current
system of tests we have there does not fit in with the ideas of
regression testing. I know there might be some objections to this but
it is not hard to checkout rosapps or add your own custom test there if
you want. We really need to put some effort in to using (And merging
the Wine tests in to) the regression system Jason and Casper have
developed.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
Hi,
sometimes I see a debug messages like this:
(mm/npool.c:1641) Trying to allocate 254736304 bytes from nonpaged pool -
nothing suitable found, returning NULL (objects/text.c:1832) WARNING:
Failed to render glyph!
If this occurs the desktop background is flashing white. The big allocation
request comes from freetype\src\raster\ftrend1.c line #178. Has anyone an
idea what is wrong?
- Hartmut
Hello,
I know we already have a few tests like this in the ReactOS tree but I
have not had time to look at all of them or dig in to this at all.
I am forwarding part of a message from Jeremy White along with some
tests of timers and schedualing in case anyone wants to compare Windows
and ReactOS. We ran in to quite a few issues under CrossOver with
Office applications and were able to work around them. Even
applications such as Internet Explorer are affected. See recent hacky
patches on wine-devel for winmm timer resolution. Anyway here is a bit
of his notes and the collection of tests if anyone is interested.
Thanks
Steven
".....Spinning threads get all the cpu they can chew; being in a
foreground Window gives a pretty high bias, but otherwise things seem
to be evenly spread. Aric did a test program which showed how
SetThreadPriority biases things; it tends to be that only priorities -2
through 2,and 15, have any meaning. Further, if threads yield, then
only thetop priority threads get any time. If all threads 'work', then
there is a stair step effect where high priority threads get 'more',
but don't necessarily get it all."
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
Hello,
I guess the message is directed at James. I am going to merge our
implementation of advpack.dll with the current winehq implementation.
Any objections or suggestions?
Thanks
Steven
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
> Everything looks ok for me. I forgot to mention that Reactos is booted
> from real hardware + freeldr diskette.
> The native ne2000.sys driver from Reactos has also the same problem .
> this can be simulted as follows :
>
> - Build a ntoskrnl.exe with NDEBUG commented in ldr.c
> - Disable Amd Pcnet entry and enable Ne2000 entry in hivesys.inf file
> - Make registry
> - Boot Reactos and check the debug traces for loading of ne2000.sys driver
>
1) corrupt file system
2) bad LFN entry for low case ne200.sys name
3) Ob case sensitive and ne2000.sys in the reg, but NE2000.SYS on fs
____________________________________________________________
Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione.
Abbonati subito su http://www.libero.it
Hartmut Birr wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/ntoskrnl/
>Changes by: hbirr(a)mok.osexperts.com 04/10/17 08:39:32
>
>Modified files:
> reactos/hal/halx86/: irql.c
> reactos/ntoskrnl/ex/: sysinfo.c
> reactos/ntoskrnl/include/internal/: ke.h
> reactos/ntoskrnl/ke/i386/: irq.c kernel.c
> reactos/ntoskrnl/ke/: dpc.c timer.c
> reactos/ntoskrnl/ps/: idle.c thread.c
> reactos/ntoskrnl/: ntoskrnl.def
>
>Log message:
> - Used variables from the KPCR for the current irql, for dpc's, for time counters and for the idle thread.
>
>_______________________________________________
>Ros-cvs mailing list
>Ros-cvs(a)reactos.com
>http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
Hartmut,
_THANK_ You. I was looking forward to doing those changes (and others)
myself as soon as I'm done with the new header system.
Best regards,
Alex Ionescu
Hartmut Birr wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/ntoskrnl/include/internal/i386/
>Changes by: hbirr(a)mok.osexperts.com 04/10/17 03:53:08
>
>Modified files:
> reactos/ntoskrnl/include/internal/i386/: ps.h
>
>Log message:
> - Fixed the definition KPCR_SELF and KeGetCurrentKPCR.
>
>_______________________________________________
>Ros-cvs mailing list
>Ros-cvs(a)reactos.com
>http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
Is that really right? I can swear fs:18h was still used until NT 5.2.
Also, it would be of critical importance to:
1) Change the hardcoded offsets to FIELD_OFFSET(...,...)
2) Make the ASM use the defines instead of hardcoding 1Ch/18h
Best regards,
Alex Ionescu
Hi,
sometimes I get a crash in
ExWorkerThreadEntryPoint/ExInterlockedRemoveHeadList. I've checked all calls
to ExQueueWorkItem. It seems that something is wrong in the tcpip/ndis
driver. There is a timer dpc which calls ExQueueWorkItem with a static work
queue item. If the worker is not execute previous the next timer call, the
item is queued for twice. Possible it is the same bug as #425.
- Hartmut