Hey all,
at the moment I try to create an overview on the current German
translation of ReactOS and for this I need to know one important little
thing:
Which hardcoded strings should be moved to rc-files?
And is there a howto on this topic?
I would be very happy about some fast responses, I want to get the
German translation ready before the 0.3.0 release...
Greets,
David Hinz
And yes, I know I should post this to the ros-translate list, but it
seems to be inactive...
Hi,
I was testing with drivers.exe from the W2K DDK. It worked once before about
a month ago. Now it crashes the system w/o any display at all. WinObj.exe works
fine.
Revision: 19187
Node Kind: directory
Schedule: normal
Last Changed Author: hbirr
Last Changed Rev: 19187
Last Changed Date: 2005-11-12 23:45:32 +0000 (Sat, 12 Nov 2005)
Properties Last Updated: 2005-10-01 16:19:41 +0000 (Sat, 01 Oct 2005)
(subsys/win32k/objects/gdiobj.c:585) Attempted to free global gdi handle 0x13080
1fb, caller needs to get ownership first!!!
lib/rtl/unicode.c:916: Pagable code called at IRQL > APC_LEVEL (2)
KeBugCheck at ntoskrnl/rtl/libsupp.c:139
(ntoskrnl/mm/mm.c:275) Page fault at high IRQL was 2, address c5b62
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
Technical information:
*** STOP: 0x00000000 (0x00000000,0x00000000,0x00000000,0x00000000)
Frames:
<ntoskrnl.exe:2585 (ntoskrnl/ke/bug.c:479 (KeBugCheckEx))>
<ntoskrnl.exe:25bd (ntoskrnl/ke/bug.c:500 (KeBugCheck))>
<ntoskrnl.exe:8d20d (ntoskrnl/rtl/libsupp.c:139 (CHECK_PAGED_CODE_RTL))>
<ntoskrnl.exe:b9bda (lib/rtl/unicode.c:918 (RtlUnicodeStringToAnsiString))>
<ntoskrnl.exe:554cd (ntoskrnl/ldr/loader.c:435 (LdrpQueryModuleInformation))>
<ntoskrnl.exe:27f6a (ntoskrnl/ex/sysinfo.c:803 (QSISystemModuleInformation))>
<ntoskrnl.exe:28e5d (ntoskrnl/ex/sysinfo.c:1558 (NtQuerySystemInformation))>
<ntoskrnl.exe:9c57c ({standard input}:373 (KiSystemService))>
<drivers.EXE:146f>
Entered debugger on embedded INT3 at 0x0008:0x800b2376.
kdb:> bt
Eip:
<ntoskrnl.exe:b2377 ({standard input}:28 (DbgBreakPointWithStatus))>
Frames:
<ntoskrnl.exe:2585 (ntoskrnl/ke/bug.c:479 (KeBugCheckEx))>
<ntoskrnl.exe:25bd (ntoskrnl/ke/bug.c:500 (KeBugCheck))>
<ntoskrnl.exe:8d20d (ntoskrnl/rtl/libsupp.c:139 (CHECK_PAGED_CODE_RTL))>
<ntoskrnl.exe:b9bda (lib/rtl/unicode.c:918 (RtlUnicodeStringToAnsiString))>
<ntoskrnl.exe:554cd (ntoskrnl/ldr/loader.c:435 (LdrpQueryModuleInformation))>
<ntoskrnl.exe:27f6a (ntoskrnl/ex/sysinfo.c:803 (QSISystemModuleInformation))>
<ntoskrnl.exe:28e5d (ntoskrnl/ex/sysinfo.c:1558 (NtQuerySystemInformation))>
<ntoskrnl.exe:9c57c ({standard input}:373 (KiSystemService))>
<drivers.EXE:146f>
<drivers.EXE:170f>
<kernel32.dll:31635 (lib/kernel32/process/create.c:68 (BaseProcessStartup))>
<00000000>
kdb:>
Ge van Geldorp wrote:
> Reminder to devs: with the release of 0.2.9-RC2 we're now in
> code freeze for
> the branch. During code freeze, the only allowed commits are
> bugfixes to
> release-blocking bugs. These fixes are generally discussed on
> the mailing
> list prior to committing a fix.
>
> GvG
I'm not sure if I'm missing something here, but these rules seem to
contradict themselves.
According to the rules :
We don't move from Feature Freeze to Code Freeze until, and I quote "the
testing coordinator indicates that all blocker bugs in the release branch
have been fixed"
I interpret this as, we move to Code Freeze, when and only when all blockers
have been fixed.
We then dictate that "During code freeze, the only allowed commits are
bugfixes to release-blocking bugs"
If all blockers must be fixed before we move to Code Freeze, and we can only
commit bug fixes to free up blockers during Feature Freeze, what is the
actual point in having a Code Freeze as we will never have any blockers to
fix.
I hope that reads ok.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
> From: Brandon Turner
>
> I just released 0.2.9 to sf.net. A lot of bug fixes since
> RC1 so get out there and check it out. File any bugs in in
> bugzilla or give us any feedback on the ml.
Reminder to devs: with the release of 0.2.9-RC2 we're now in code freeze for
the branch. During code freeze, the only allowed commits are bugfixes to
release-blocking bugs. These fixes are generally discussed on the mailing
list prior to committing a fix.
GvG
Hey all,
I was about to publish all the files for 0.2.9 RC2 when i releazied that
my network is not working in qemu. It worked a few days ago(friday?).
But it isnt working for me now. Is anyone else having this problem?
www.brandonturner.org/rc2.PNG
Brandon