Ge van Geldorp wrote:
> AFAIK, it is about storing both a long and a short filename
> for the same
> file in the same directory.
>
> GvG
Do we really need the ability to store short file names?
Can we not just remove that feature entirely?
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
Does it really matter if people enable it or not if we still provide the functionality?
/Johannes Olofsson
> Till: ReactOS Development List <ros-dev(a)reactos.org>
> Rubrik: Re: [ros-dev] Patent on FAT
> Datum: Wed, 11 Jan 2006 14:57:50 -0500
> Hi,
>
> I think we should turn off the 8.3 short filename support by default
> and see what breaks. Providing a option right at the start of 2nd
> stage step "Patented features" using a checkbox to enable it should
> get us around the issue. Its not our problem if someone else enables
> it.
>
> --
> Steven Edwards - ReactOS and Wine developer
>
> "There is one thing stronger than all the armies in the world, and
> that is an idea whose time has come." - Victor Hugo
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> <a
> href=http://www.reactos.org/mailman/listinfo/ros-dev>http://www.reactos.org/
> mailman/listinfo/ros-dev</a>
nitro2k01 wrote:
> I haven't seen the patant documents, but doesn't this mean that any
> file system which stores both long and short file names on the same
> volume would be theoreticlly affected?
>
No. Long files names were incorporated into unix systems long before the
days FAT, or even DOS.
This patent (if correct) is linked to FAT only.
If is true, it would effect many things, but I can't see Microsoft enforcing
it, it would alienate themselves.
Just the fact that it is there is a problem for ReactOS though, even if they
don't do anything about it.
I haven't been able to find a copy of the patent yet. AFAIK, it was only
released today.
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
I've seen this bugcheck several times debugging various things. At
the moment, it reproducible following the steps in the bug. This has
been around for a while and it aid me greatly to have it fixed.
http://www.reactos.org/bugzilla/show_bug.cgi?id=1263
WD
--
<Alex_Ionescu> it's like saying let's rename Ke to Kernel because
people think it's Ketchup
Murphy, Ged (Bolton) wrote:
>
> I'm reading reports of a US patent on FAT.
>
Link:
http://news.com.com/Microsofts+file+system+patent+upheld/2100-1012_3-6025447
.html?part=rss&tag=6025447&subj=news
************************************************************************
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
gedmurphy(a)svn.reactos.org wrote:
> + case NM_RCLICK:
you should use WM_CONTEXTMENU instead so the menus are also accessible
by using the keyboard.
- Thomas
I'd quite like to see the blog page integrated into the site and made to
look pretty.
I also think it might entice devs to start using the thing. At the moment
there is only about 4 people listed, and of those only Alex every actually
uses it.
Would developers make an effort to start blogging if it was 'spruced up'
and integrated?
If not, I think it should be removed as it looks a bit pitiful as it is and
gives the impression not much is going on (which is obviously not the case)
It doesn't always have to be development related stuff in there. Anything
interesting draws a crowd.
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
I would have to agree with this.
ReactOS.Bugzilla(a)reactos.org wrote:
>http://www.reactos.org/bugzilla/show_bug.cgi?id=1264
>
>
>
>
>
>------- Additional Comments From gvg(a)reactos.org 2006-01-10 19:07 CET -------
>I'd prefer something along the lines of:
>
>FooBarFast:
> non-486 implementation
>
>FooBar486:
> 486 implementation
>
>FooBarInit:
> Store either FooBarFast or FooBar486 in FooBarPtr
>
>FooBarPtr:
> .long FooBarInit
>
> .global ExfFooBar
>ExfFooBar:
> jmp [FooBarPtr]
>
>No self modifying code, at the expense of an indirect jump
>
>
>
I was just taking a look at some ReactOS code this evening and it got
me thinking about what our general strategy for handling invalid
parameters is.
For example, in kernel32.dll there is a function DebugBreakProcess.
This function takes one parameter, a process handle.
This parameter is passed through the following list of functions
unchecked by any of them, until the final one will return a failure...
DebugBreakProcess
DbgUiIssueRemoteBreakIn
RtlCreateUserThread
RtlpCreateUserStack
ZwAllocateVirtualMemory
ObReferenceObjectByHandle
Now I know this isn't a security vulnerability, which is what I was
originally looking for, but it did make me think of the question of
where should bounds checking be added?
In this example, the process handle must be a value greater than zero.
Should this simple check be added to DebugBreakProcess, or all of the
above? Is there some sort of standard that everyone should work to?
e.g. should all functions check their own parameters. Sure it might
make it a little slower due to multiple checks but it would make
ReactOS very robust.
Any thoughts on this?
Martin
PS: Lack of activity recently had been due to uni. exams.
hbirr(a)svn.reactos.org wrote:
>
>- Defined KeIpiGenericCall. It is necessary for the smp build.
>
Hi,
It should be in the w32api DDK, not in the interal headers. Sorry for
removing it if this broke the build, I didn't notice on UP.
Best regards,
Alex Ionescu
It seems the old binutils versions don't have a problem with "cmpxchg8b" but
with "qword ptr". The patch below makes the code compile on older versions
again. Any objections to committing it?
I've created a bug 1264 for keeping track of the "no longer works on i486"
issue.
GvG
Index: ntoskrnl/ex/i386/fastinterlck_asm.S
===================================================================
--- ntoskrnl/ex/i386/fastinterlck_asm.S (revision 20747)
+++ ntoskrnl/ex/i386/fastinterlck_asm.S (working copy)
@@ -405,7 +405,7 @@
/* Get next pointer and do the exchange */
mov ebx, [eax]
- LOCK cmpxchg8b qword ptr [ebp]
+ LOCK cmpxchg8b [ebp]
jnz 1b
/* Restore registers and return */
@@ -449,7 +449,7 @@
lea ecx, [edx+0x10001]
/* Do the exchange */
- LOCK cmpxchg8b qword ptr [ebp]
+ LOCK cmpxchg8b [ebp]
jnz 1b
/* Restore registers and return */
@@ -489,7 +489,7 @@
mov cx, bx
/* Do the exchange */
- LOCK cmpxchg8b qword ptr [ebp]
+ LOCK cmpxchg8b [ebp]
jnz 1b
/* Restore registers and return */
@@ -623,7 +623,7 @@
mov edx, [edx+4]
/* Do the op */
- LOCK cmpxchg8b qword ptr [ebp]
+ LOCK cmpxchg8b [ebp]
/* Restore volatiles */
pop ebp
@@ -655,7 +655,7 @@
mov edx, [edx+4]
/* Do the op */
- LOCK cmpxchg8b qword ptr [ebp]
+ LOCK cmpxchg8b [ebp]
/* Restore volatiles */
pop ebp
ion(a)svn.reactos.org wrote:
> - Fix shamefully dangerously broken Work Thread/Queue/Item implementation:
> * Do not pollute the kernel with 10 real-time threads and 5 high-priority threads in order to manage work items. Work threads are very-low priority (< 7) and should never pre-empt userthreads like they do now. 1 priority 7, 5 priority 5 and 3 priority 4 threads are now properly created.
> * Implement a worker thread balance set manager. On SMP systems, it is able to determine when a new thread should be allocate to execute on a free CPU. On both UP and MP, it is also able to detect if a work queue has deadlocked, and will allocate new dynamic threads to unfreeze the queue.
> * Add check for threads returning with APC disabled, and re-enable APCs if this happend. This hack is used in NT for broken drivers.
> * Lots of code changes to support dynamic threads, which:
> - Can terminate.
> - Use a 10 minute timeout on the kernel queue.
> * Add skeleton code for swapping worker thread stacks as well as worker thread shutdown (not yet implemented).
> * Add WORKER_INVALID bugcheck definition.
> * These changes seem to make ROS a lot more responsive.
>
> - NDK:
> * Make more compatible with MS IFS
> * Fix EX_WORK_QUEUE definition.
> * Fix ETHREAD offsets.
> * Fix RtlIsNameLegalDOS8Dot3 definition.
> * Move splay tree defines to IFS.
>
>
> Updated files:
> trunk/reactos/include/ndk/exfuncs.h
> trunk/reactos/include/ndk/extypes.h
> trunk/reactos/include/ndk/ifssupp.h
> trunk/reactos/include/ndk/iofuncs.h
> trunk/reactos/include/ndk/obfuncs.h
> trunk/reactos/include/ndk/pstypes.h
> trunk/reactos/include/ndk/rtlfuncs.h
> trunk/reactos/include/ndk/rtltypes.h
> trunk/reactos/lib/rtl/dos8dot3.c
> trunk/reactos/ntoskrnl/ex/work.c
> trunk/reactos/ntoskrnl/ntoskrnl.mc
> trunk/reactos/w32api/include/ddk/ntifs.h
>
> _______________________________________________
> Ros-svn mailing list
> Ros-svn(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-svn
>
>
After applying this commit, I get a crash during compiling ros on ros
with 'make clean' on a clean tree on my smp machine:
Assertion (Thread->State == Waiting) == (Thread->WaitBlockList != NULL)
failed at ./ntoskrnl/ke/wait.c:722
I don't get a back trace. It may be a problem of the broken ASSERT
statement (DBG=1 and KDBG=0).
- Hartmut
Why is the ReactOS version of wininet out of sync with Wine?
There have been a ton of fixes going into Wine in recent months that
unfortunately ReactOS is missing out on.
--
Rob Shearman
On 08.01.2006 11:23:52 ion(a)svn.reactos.org wrote:
> - userinit, usetup, vmwinst, welcome, winefile, winlogon, winver.
> Updated files:
...
> trunk/reactos/subsys/system/winefile/winefile.c
May I ask what this changes should be for?
Adding "__cdecl" attributes doesn't make much sense for me.
And winefile compiles without problems on MSVC since ages.
Regards,
Martin
cwittich(a)svn.reactos.org wrote:
> - GetFileTitle(szFileName, Globals.szFileTitle, sizeof(Globals.szFileTitle));
>
> + GetFileTitle(szFileName, Globals.szFileTitle, wcslen(Globals.szFileTitle));
This change is wrong, sizeof(Globals.szFileTitle) is correct. The last
parameter is the size of the buffer the second parameter represents.
- Thomas
cwittich(a)svn.reactos.org wrote:
> + Data = (TCHAR*) HeapAlloc(GetProcessHeap(), 0, MAX_VALUE_NAME);
It should be MAX_VALUE_NAME * sizeof(TCHAR)
- Thomas
Royce Mitchell III wrote
> How are you source-level debugging ros?
Probably using Insight, that's what I use when building with mingw.
I don't know assembly well enough to even consider it.
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
I just got this error when trying to compile reactos:
> reub2000@reub2000 ~/reactos $ svn up && make clean && make
> At revision 20661.
> [CC] tools/rbuild/backend/msvc/vcprojmaker.cpp
> [CC] tools/rbuild/module.cpp
> [LD] output-i386/tools/rbuild/rbuild
> [NCI] ntoskrnl/include/internal/napi.h
> make: *** No rule to make target `drivers/net/npf/npf.xml', needed by
> `makefile.auto'. Stop.
>+ case CB_LIMITTEXT:
>+ if( lphc->wState & CBF_EDIT )
>+ return SendMessageW(lphc->hWndEdit, EM_LIMITTEXT, wParam, lParam);
>
>
<- "break;" statement is missing here and the indentation is fscked up.
- Filip
Hi Alex,
ion(a)svn.reactos.org wrote:
> - Get portcls to compile.
> trunk/reactos/drivers/multimedia/portcls/portcls.c
> trunk/reactos/drivers/multimedia/portcls/portcls.h
Was OSR wrong? Wow! 8^o
Thanks,
James
Hi all,
Most common, when exiting a app by clicking the "X" in the upper right corner,
(./subsys/win32k/objects/gdiobj.c:591) Attempted to free global gdi handle 0xe04
04b4, caller needs to get ownership first!!!
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invali
d usermode buffer
(lib/comctl32/toolbar.c:417) bitmap for ID 0, index 0 is not valid, number of bi
tmaps in imagelist: -2
(./ntoskrnl/ke/queue.c:420) Unwaiting Thread: 5
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invali
d usermode buffer
C0000005 is an Access error, due to MmCopyToCaller being called inside kernel space
when copying one object to another with in kernel space, sometimes but it is common.
In win32k/ntuser/message.c there is and it's my best guess,
Status = MmCopyFromCaller(KernelMem, (PVOID) UserModeMsg->lParam, Size);
at line ~1118, in function CopyMsgToKernelMem. If that function is used to copy data
inside kernel space it will through and exception.
This one is from OpenOffice, Some where in kernel32.dll.
(lib/rtl/exception.c:29) RtlRaiseException(Status 0054f404)
(lib/rtl/exception.c:36) ExceptionAddress 7c801217
(./ntoskrnl/ke/exception.c:94) KiRaiseException
(lib/rtl/exception.c:29) RtlRaiseException(Status 0054f41c)
(lib/rtl/exception.c:36) ExceptionAddress 7c801217
(./ntoskrnl/ke/exception.c:94) KiRaiseException
0 bytes requested - initiating pool verification
0 bytes requested - initiating pool verification
Sorry I haven't looked at this one yet, I just started!
8^>
James
Do those debug prints really need to be DPRINT1's ??
-----Original Message-----
From: jimtabor(a)svn.reactos.org [mailto:jimtabor@svn.reactos.org]
Sent: 06 January 2006 14:24
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [jimtabor] 20610: Revert, thx Thomas, wasnt sure.
Revert, thx Thomas, wasnt sure.
Modified: trunk/reactos/subsys/win32k/ntuser/menu.c
_____
Modified: trunk/reactos/subsys/win32k/ntuser/menu.c
--- trunk/reactos/subsys/win32k/ntuser/menu.c 2006-01-06 13:57:38 UTC (rev
20609)
+++ trunk/reactos/subsys/win32k/ntuser/menu.c 2006-01-06 14:23:26 UTC (rev
20610)
@@ -33,7 +33,7 @@
#define NDEBUG
#include <debug.h>
-extern PMENU_OBJECT FASTCALL
+PMENU_OBJECT FASTCALL
IntGetSystemMenu(PWINDOW_OBJECT Window, BOOL bRevert, BOOL RetMenu);
@@ -1659,7 +1659,7 @@
MENUBARINFO kmbi;
DECLARE_RETURN(BOOL);
- DPRINT("Enter NtUserGetMenuBarInfo\n");
+ DPRINT1("Enter NtUserGetMenuBarInfo\n");
UserEnterShared();
if (!(WindowObject = UserGetWindowObject(hwnd)))
@@ -1849,7 +1849,7 @@
RETURN(Res);
CLEANUP:
- DPRINT("Leave NtUserGetMenuBarInfo, ret=%i\n",_ret_);
+ DPRINT1("Leave NtUserGetMenuBarInfo, ret=%i\n",_ret_);
UserLeave();
END_CLEANUP;
}
@@ -1887,7 +1887,7 @@
PMENU_ITEM MenuItem;
DECLARE_RETURN(BOOL);
- DPRINT("Enter NtUserGetMenuItemRect\n");
+ DPRINT1("Enter NtUserGetMenuItemRect\n");
UserEnterShared();
if (!(Menu = UserGetMenuObject(hMenu)))
@@ -1923,7 +1923,7 @@
RETURN( TRUE);
CLEANUP:
- DPRINT("Leave NtUserGetMenuItemRect, ret=%i\n",_ret_);
+ DPRINT1("Leave NtUserGetMenuItemRect, ret=%i\n",_ret_);
UserLeave();
END_CLEANUP;
}
************************************************************************
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
ion(a)svn.reactos.org wrote:
> - New ERESOURCE implementation: fixes the return value of some functions (VOID vs NTSTATUS, USHORT vs ULONG), as well as optimized the code loops and general structure of the code. Additionnaly, functions do not simply call other functions with similar names; the exact implementation of each function has now been properly separated (see the DDK for more information on this) to have the most optimized scenarios.
> - Also, the spinlock is not actually acquired on non-SMP builds; instead, interrupts are blocked and unblocked for acquire/release, this optimizes locking.
> - Added many asserts and bugcheck scenarios.
> - Added thread priority boosting.
> - Added some debugging helpers and deadlock detection.
> - Added RESOURCE_NOT_OWNED bugcehck message.
> * Thanks again to Waxdragon (Andrew) for testing this build.
It seems, that your implementation is broken. On a non SMP machine
during 'make clean' on the ros source:
KeBugCheckEx at ./ntoskrnl/ex/resource.c:1847
A problem has been detected and ReactOS has been shut down to prevent
damage to your computer.
Technical information:
*** STOP: 0x000000E3 (0x81a5eb0c,0x81a55c70,0x00000000,0x00000002)
Frames:
<ntoskrnl.exe:2599 (./ntoskrnl/ke/bug.c:483 (KeBugCheckEx))>
<ntoskrnl.exe:27ac4 (./ntoskrnl/ex/resource.c:1843 (ExReleaseResourceLite))>
<vfatfs.sys:3ee2 (drivers/fs/vfat/dir.c:471 (DoQuery))>
<vfatfs.sys:416f (drivers/fs/vfat/dir.c:486 (VfatDirectoryControl))>
<vfatfs.sys:dc06 (drivers/fs/vfat/misc.c:119 (VfatDispatchRequest))>
<vfatfs.sys:dd8f (drivers/fs/vfat/misc.c:167 (VfatBuildRequest))>
<ntoskrnl.exe:4369b (./ntoskrnl/io/irp.c:1076 (IofCallDriver))>
<ntoskrnl.exe:53a3a (ntoskrnl/io/file.c:2607 (NtQueryDirectoryFile))>
<ntoskrnl.exe:a0daa (ntoskrnl\ke\i386\syscall.S:372 (KiSystemService))>
<kernel32.dll:9b22 (./lib/kernel32/file/find.c:143 (InternalFindNextFile))>
The same on a SMP machine (no back trace available):
KeBugCheckEx at ./ntoskrnl/ex/resource.c:1868
(./ntoskrnl/mm/mm.c:292 CPU0) Page fault at high IRQL was 2, address c2410
A problem has been detected and ReactOS has been shut down to prevent
damage to your computer.
Technical information:
*** STOP: 0x000000E3 (0x8131d0d8,0x81620d68,0x81376640,0x00000002)
- Hartmut
Hi,
So here is the first in what I hope to be quarterly reports. In future
reports I will provide more detail such as charts and graphs if I feel
so inclined. Depending on how much goes on in a period we may make it
every 6 months instead of every 3 months. Basically this report just
covers what has gone on during the 0.2.x development and where we plan
on going. Developers that I spoke with in private or that I have
worked with are listed here as to the project I know you have or are
working on. If your not listed please add yourself to
http://www.reactos.org/wiki/index.php/People_of_ReactOS
Also could someone convert this from Microsoft Word to OpenOffice and
or PDF and check the formatting of the doc? I lack good artistic skill
so feel free to make corrections before spamming it anywhere. I think
I spelled all the names right. Sorry if I left off any accent.
Also as a final note if I left of your project or did not give it the
coverage you feel it deserves do not take it personal. We are working
on a massive project and I have not even talked to all of the people
with commit access let alone know all of the things people are working
on. I have tried to keep the information here as general as possible
except where I feel that the public may have interest.
Thanks
--
Steven Edwards - ReactOS and Wine developer
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Please remember that some of us don't use Windows ;o)
make[1]: Entering directory `/home/alex/src/OpSys/reactos'
[CC] subsys/system/servman/servman.c
[WRC] obj-i386/subsys/system/servman/servman.coff
subsys/system/servman/servman.rc:15:17: En.rc: No such file or directory
make[1]: *** [obj-i386/subsys/system/servman/servman.coff] Error 1
make[1]: Leaving directory `/home/alex/src/OpSys/reactos'
--
http://www.munted.org.uk
Anyone that thinks an imaginary deity is going to protect them against
earthquakes and hurricanes needs psychiatric help.
Just got ReactOS to build and boot, but bluescreens during the GUI based
setup. It looks like there's something wrong with the code that
services the mouse.
(./ntoskrnl/ke/main.c:295)
---------------------------------------------------------------
(./ntoskrnl/ke/main.c:296) ReactOS 0.3-SVN (Build 20060105-r20584) Used
memory 131072Kb (./ntoskrnl/mm/mminit.c:386) Kernel Stack Limits.
InitTop = 0x800ba000, Init = 0x800b7000 (./ntoskrnl/mm/mm.c:283) No
current process (./ntoskrnl/ldr/loader.c:267) Could not open module
file: \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2168) Initialization of service serial failed
(Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module
file: \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2168) Initialization of service serial failed
(Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module
file: \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2168) Initialization of service serial failed
(Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module
file: \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2168) Initialization of service serial failed
(Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module
file: \SystemRoot\System32\drivers\pcnet.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2168) Initialization of service PCNet failed
(Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module
file: \SystemRoot\system32\drivers\vmx_svga.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2168) Initialization of service vmx_svga failed
(Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module
file: \SystemRoot\System32\drivers\pciide.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2168) Initialization of service pciide failed
(Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module
file: \SystemRoot\System32\drivers\pcnet.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2168) Initialization of service PCNet failed
(Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module
file: \SystemRoot\system32\drivers\vmx_svga.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2168) Initialization of service vmx_svga failed
(Status c0000001) (./ntoskrnl/ldr/loader.c:267) Could not open module
file: \SystemRoot\System32\drivers\pciide.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2168) Initialization of service pciide failed
(Status c0000001) (./ntoskrnl/io/pnpreport.c:86)
IoReportResourceForDetection partly implemented
(./ntoskrnl/io/pnpmgr.c:545) IoOpenDeviceRegistryKey(): Base key
doesn't exist, exiting... (./ntoskrnl/ldr/loader.c:267) Could not open
module file: \SystemRoot\System32\drivers\pciide.sys (Status
0xc0000034) (./ntoskrnl/io/pnpmgr.c:2168) Initialization of service
pciide failed (Status c0000034) (./ntoskrnl/ldr/loader.c:267) Could not
open module file: \SystemRoot\system32\drivers\sndblst.sys (Status
0xc0000034) (./ntoskrnl/ldr/loader.c:267) Could not open module file:
\SystemRoot\system32\drivers\mpu401.sys (Status 0xc0000034)
(./ntoskrnl/io/disk.c:630) RDiskCount 2
(./subsys/win32k/ntuser/winsta.c:108) IntWinStaObjectOpen
(./subsys/win32k/ntuser/winsta.c:118) Create winsta atomtable
(./subsys/win32k/ntuser/desktop.c:812) Trying to open desktop (\Windows
\WindowStations\WinSta0\Default) (./subsys/win32k/ntuser/desktop.c:646)
IntShellHookNotify: No desktop! (./subsys/win32k/ntuser/desktop.c:812)
Trying to open desktop (\Windows\WindowStations\WinSta0\Winlogon)
(./subsys/win32k/ntuser/desktop.c:646) IntShellHookNotify: No desktop!
(./subsys/win32k/ntuser/desktop.c:812) Trying to open desktop (\Windows
\WindowStations\WinSta0\Screen-Saver)
(./subsys/win32k/ntuser/desktop.c:646) IntShellHookNotify: No desktop!
WL-Status: ReactOS is starting up... WARNING: WSHGetSockaddrType at
drivers/net/wshtcpip/wshtcpip.c:103 is UNIMPLEMENTED!
(services/dhcp/util.c:72) ERROR: util.c read_client_conf not
implemented! 81178950: 00 00 00 00 c8 e4 64 00 01 00 00 00 00 00 00
00 ......d......... 81178960: 34 e5 64 00 34 20 76 00 ac 10 75 02 03
00 00 00 4.d.4 v...u..... 81178970: ac 18 65 00 c8 e4 64 00 00 00 00
00 b8 43 76 00 ..e...d......Cv. 81178980: 00 00 00
00 .... FIXME: CopyImage doesn't
support IMAGE_ICON correctly! (lib/ntdll/ldr/utils.c:1190)
LdrGetExportByName(): failed to find mxdMessage
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of
'msacm.drv' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to
create or open dll section of 'midimap.drv' (Status c0000135)
(SAMLIB:lib/samlib/samlib.c:399) User already exists!
(lib/setupapi/devinst.c:3167) Flags 0x800000 ignored
(lib/setupapi/devinst.c:3167) Flags 0x800000 ignored
(lib/setupapi/devinst.c:3167) Flags 0x800000 ignored
(lib/setupapi/devinst.c:3167) Flags 0x800000 ignored
(lib/setupapi/devinst.c:3167) Flags 0x800000 ignored
(lib/setupapi/devinst.c:3167) Flags 0x800000 ignored
(lib/setupapi/devinst.c:3167) Flags 0x800000 ignored
(lib/setupapi/devinst.c:3167) Flags 0x800000 ignored
(lib/setupapi/devinst.c:3167) Flags 0x800000 ignored
(lib/setupapi/devinst.c:3167) Flags 0x800000 ignored
(./lib/advapi32/service/scm.c:2036) dwBufSize: 0
(subsys/system/services/rpcserver.c:1759) ScmrStartServiceW() called
(./ntoskrnl/mm/mm.c:275) Page fault at high IRQL was 2, address 156
KeBugCheckWithTf at ntoskrnl/ke/i386/exp.c:1242 A problem has been
detected and ReactOS has been shut down to prevent damage to your
computer.
The problem seems to be caused by the following file: ntoskrnl.exe
Technical information:
*** STOP: 0x0000001E (0xc0000005,0x800028dd,0x00000000,0x00000156)
*** ntoskrnl.exe - Address 0x800028dd base at 0x80000000, DateStamp
0x0
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:800028dd <ntoskrnl.exe:28dd
(./ntoskrnl/ke/wait.c:0 ())> cr2 156 cr3 26000 Proc: 80804c20 Pid: 4
<System> Thrd: 80d6c7d8 Tid: 80 DS 23 ES 23 FS 30 GS 0
EAX: 9e458c14 EBX: 00000102 ECX: 00000102
EDX: 00000004 EBP: 9e458b80 ESI: 00000000 ESP: 9e458b04
EDI: 80d6c7d8 EFLAGS: 00010206 kESP 9e458b04 kernel stack base
9e456000 Frames:
<ntoskrnl.exe:34d5 (./ntoskrnl/ke/event.c:207 (KeSetEvent))>
<ntoskrnl.exe:29109 (./ntoskrnl/io/irp.c:0 (IopCompleteRequest))>
<ntoskrnl.exe:3164 (./ntoskrnl/ke/apc.c:0 (KiDeliverApc))>
<80405EAE>
<win32k.sys:3b3ed (./subsys/win32k/eng/mouse.c:588 (IntEngMovePointer))>
<win32k.sys:5d299 (./subsys/win32k/ntuser/input.c:0 ())>
<win32k.sys:5dc4b (./subsys/win32k/ntuser/input.c:148
(ProcessMouseInputData))> <win32k.sys:5de0f
(./subsys/win32k/ntuser/input.c:227 (MouseThreadMain))>
<ntoskrnl.exe:5aeab (./ntoskrnl/ps/thread.c:94 (PspSystemThreadStartup))
> <ntoskrnl.exe:62265 (ntoskrnl/ke/i386/ctxswitch.S:82 (KiThreadStartup))>
--
http://www.munted.org.uk
Anyone that thinks an imaginary deity is going to protect them against
earthquakes and hurricanes needs psychiatric help.
obj-i386/ntoskrnl/ke/i386/kernel.o: In function
`KeApplicationProcessorInitDispatcher': /home/alex/src/OpSys/reactos/ntoskrnl/ke/i386/kernel.c:147:
undefined reference to
`@KeAcquireDispatcherDatabaseLock@0' /home/alex/src/OpSys/reactos/ntoskrnl/ke/i386/kernel.c:149:
undefined reference to `@KeReleaseDispatcherDatabaseLock@4'
obj-i386/ntoskrnl/ke/i386/kernel.o: In function
`KeInit2': /home/alex/src/OpSys/reactos/ntoskrnl/ke/i386/kernel.c:442:
undefined reference to `@KeInitializeDispatcher@0' collect2: ld
returned 1 exit status
--
http://www.munted.org.uk
Anyone that thinks an imaginary deity is going to protect them against
earthquakes and hurricanes needs psychiatric help.
> From: ion(a)svn.reactos.org
>
> * Do not pollute the kernel with 10 real-time threads and 5
> high-priority threads in order to manage work items. Work
> threads are very-low priority (< 7) and should never pre-empt
> userthreads like they do now. 1 priority 7, 5 priority 5 and
> 3 priority 4 threads are now properly created.
I haven't looked at your code yet, but the comment worries me. Does it mean
that if a usermode app is stuck in a "while (1) ;" loop stuff queued by
IoAllocateWorkItem( ) never gets executed? If I misunderstood, nevermind,
disregard this message. If this is true we're in big trouble. We're using
work items in a lot of places to get from DPC level to PASSIVE level. For
example, the networking stack queues a work item when data was received from
the network card. I'd hate to see a stuck usermode app halt all network
communications...
GvG
Hi,
I have come to the conclusion that using -O2 is beneficial even for DBG
= 1 builds, and that it should be set on by default on all builds. The
typically given reason for not using optimizations on a "Debug" build is
because these apparently make assembly code harder to read. I have
realized otherwise, and as seen in the example that I will include
below, I'm sure this will be mutually agreed on. I note the following
advantages in using -O2 on a DBG = 1 build as well:
- -O2 makes the compiler do additional checks. For example, gcc will NOT
detect uninitialized variables unless -O2 is being used, even though
they are a very important programming bug. Apart from finding more bugs,
it also makes trunk compilable. Right now, I see at least two commits by
Thomas or others being made every week in order to fix some code which
used unitinialized variables (I myself have been guilty of this). This
means that some of us, like Thomas, have to constantly fix other
people's mistakes.
- -O2 means less last-minute blockers. Because we release in -O2 but
almost never build it like that, this creates a big problem for people
like Andrew or Brandon, which handle the release process and do testing.
Because the -O2 build gets less testing coverage, it is very possible
for a critical bug to be in ROS for a month before anyone notices it at
release time, in which case we will all have to scramble to find a fix
for it.
- -O2 will not undefine DBG or change anything else in the code. All the
advatanges, extra error checking and assertions of the DBG =1 build
would remain.
- -O2 builds are much faster, greatly helping testing speed.
- -O2 builds are much more likely to bring up race conditions and other
important timing bugs we need to watch out for.
- -O2 means easier debugging. This point is really important because
until I realized how true it was, I didn't want to bring this up. Here
is a pseudo(but real) disassembly of something I've seen in my dbg = 1
kernel binary while debugging:
0x40b845:
push ebp
mov ebp, esp
sub esp, 4
mov [ebp-4], fs:18h
mov eax, [ebp-4]
leave
retn
0x4bc8a5:
push ebp
mov ebp, esp
sub esp, 4
call 0x40b845
mov ecx, [eax+1c]
mov [ebp-4], eax
mov eax, [ebp-4]
leave
retn
0x42b845:
push ebp
mov ebp, esp
sub esp, 4
call 0x4bc8a5
mov ecx, [eax+124]
mov [ebp-4], eax
mov eax, [ebp-4]
leave
retn
KeFooBar:
push ebp
mov ebp, esp
sub esp, 4c
call 0x42b845
mov [ebp-0xc], eax
mov eax, [ebp-0xc]
<..>
leave
retn
This is how it looks with -O2
KeFooBar:
push ebp
mov ebp, esp
sub esp, 4c
mov eax, fs:124h
<..>
leave
retn
I hope we can all agree on which one of these is readable. The -O2 build
clearly shows you that eax is fs:124h, which you oughta know is
Pcrb->CurrentThread; even if you don't, you can easily check in a
header. The non-o2 build calls 3 other functions, out of which 2 are
merely calling other functions themselves (due to lack of symbols you
have no way of knowing what these functions are doing), until we finally
get to a function which does fs:18, which you then realize is the PCR,
you then walk back and realize pcr->0x1c is PCRB, and Prcb->0x124 is
current thread.
Yes, this example could easily be destroyed by saying " use a #define
with inline assembly" but I can bring many more; we can't start using
inline assembly everywhere... msvc does an amazing job at optimizing
these things, and even gcc isn't that bad, if only you let it. Code
built without -o2 makes horrible usage of the stack, which makes you
have to memory a lot more addresses then code which simple stores values
in registers. Because humans are smart, the loops generated by -O2 are
also much closer to what someone that understands assembly is used to
(for example, the loop will use ecx, and not a stack variable that you
need to memorize). I consider myself an expert on assembly coding, and I
simply have great trouble reading non-O2 kernels, so how exactly does it
help debugging?
In the end, I am convinced that the only disadvantage of using -O2 by
default is that it will slightly increase build times. I don't think
this increase is more then, at most 1 minute or two for a complete
build. If this issue is really critical to someone people, then perhaps
only core system files should use -O2 (kernel32, ntdll, ntoskrnl, csr,
win32k, drivers, etc).
I know some of the developers on IRC are strongly for this, but I want
to make sure I get a broader opinion.
Best regards,
Alex Ionescu
Ge van Geldorp wrote:
> Yup, using Insight (the cygwin GUI for gdb), which connects
> over a null
> modem to the GDB stub in ntoskrnl. I'm using a
> slightly-modified version,
> since the official one insists that when doing a stack
> backtrace the frame
> pointer should increase for each stack frame (which is
> correct generally but
> breaks when you're backtracing from the kernelmode stack back into the
> usermode stack). Also the official version has a problem with hardware
> watchpoints.
I use the Win32 port which comes as an add-on package with DevCpp.
However I've recently switched my pen drive compiler from DevCpp to
Code::Blocks
I'm finding the Code::Blocks built in debugger (which also uses mingw gdb)
to be excellent and have started using that in place of Insight, as it
doesn't seem have any of the problems Insight has.
In fact, I'm so impressed with Code::Blocks as a whole, I think it makes
DevCpp obsolete and needs a backend writing for rbuild. It's certainly the
best mingw enabled development tool for ROS I've come across. ;)
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
jimtabor(a)svn.reactos.org wrote:
> Clean up and fixed NtUserGetMenuItemRect. Needs more testing. I watch mplayerc swip all the menu items with out crashing.
>
>
> Updated files:
> trunk/reactos/subsys/win32k/ntuser/menu.c
>
*out
Hi,
it seems, some people have problems to install reactos from the boot cd.
The reason is, all newer pc with a P4-HT or an AMD64X2 cpu are
multiprocessor compliant. In this case, the auto choice is
multiprocessor for the computer type. If the choice isn't changed, the
multiprocessor hal and the uniprocessor kernel are installed. The next
boot will show an empty colored (light green or red) screen after
freeldr has started reactos. I think, we should disable the auto choice
for the computer type.
- Hartmut
Thomas Weidenmueller wrote:
> Murphy, Ged (Bolton) wrote:
> > which, IIRC (I don't have a compiler to hand) would throw
> up 'assignment in
> > expression' errors with our MSVC /w4 setting. We would
> therefore need
> > something like :
>
> Then don't use that warning level if it rejects good code that's not
> even confusing.
It's set via rbuilds MSDN backend. It needs functionality to set different
warning levels for different components. e.g. /w4 for core components only.
Having to do it manually is far too much effort for your average programmer
;)
Maybe I should stop moaning and correct it .... hmmm :p
> > Which has suddenly become rather long for a normally simple
> message loop
> > routine ..... LOL
>
> It's exactly the same, just ugly IMO.
I know, as I said, it was just for fun.
First day back at work after the Christmas break is hard going ;)
(and why are these mails being sent to both ros-diff and ros-dev when only
addressed to ros-dev, Gé ?)
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
Hi GreatLord!
greatlrd(a)svn.reactos.org wrote:
> forget remove a calc value in the for loop it can do outside the loop.
>
>
>
> Updated files:
> trunk/reactos/subsys/win32k/dib/dib16bpp.c
>
I'm getting this even after a make clean,
[CC] subsys/win32k/dib/dib16bpp.c
subsys/win32k/dib/dib16bpp.c: In function `CheckClipRegion':
subsys/win32k/dib/dib16bpp.c:631: error: structure has no member named `Height'
make[1]: *** [obj-i386/subsys/win32k/dib/dib16bpp.o] Error 1
Thanks,
James
I think our problem is because we are using GAS and NASM to assemble
the various assembly files. Oughtn't we standardise on NASM? Why not?
--
http://www.munted.org.uk
Anyone that thinks an imaginary deity is going to protect them against
earthquakes and hurricanes needs psychiatric help.
This should really be
while( GetMessage( &msg, NULL, 0, 0 ) > 0 )
as GetMessage returns <0 on failure.
It will then break on failure or WM_QUIT
Just being anal though as GetMessage should never really fail ;)
-----Original Message-----
From: mbosma(a)svn.reactos.org [mailto:mbosma@svn.reactos.org]
Sent: 03 January 2006 11:50
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [mbosma] 20543: fix typos.
+ while(GetMessage(&msg,NULL,0,0))
************************************************************************
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
Thomas Weidenmueller wrote
> Murphy, Ged (Bolton) wrote:
> > This should really be
> >
> > while( GetMessage( &msg, NULL, 0, 0 ) > 0 )
> >
> > as GetMessage returns <0 on failure.
> > It will then break on failure or WM_QUIT
> >
> > Just being anal though as GetMessage should never really fail ;)
>
> See
> http://msdn.microsoft.com/library/default.asp?url=/library/en-
> us/winui/WinUI/WindowsUserInterface/Windowing/MessagesandMessa
> geQueues/MessagesandMessageQueuesReference/MessagesandMessageQ
> ueuesFunctions/GetMessage.asp
>
> The loop shouldn't be broken if GetMessage returns -1.
>
> - Thomas
True, I suppose it depends on the reasoning behind the GetMessage error.
MSDN does have this to say:
"Warning
Because the return value can be nonzero, zero, or -1, avoid code like this:
while (GetMessage( lpMsg, hWnd, 0, 0)) ..."
For a bit of light hearted fun, here is the MSDN suggestion:
while( (bRet = GetMessage( &msg, NULL, 0, 0 )) != 0)
{
if (bRet == -1)
{
// handle the error and possibly exit
}
else
{
TranslateMessage(&msg);
DispatchMessage(&msg);
}
}
which, IIRC (I don't have a compiler to hand) would throw up 'assignment in
expression' errors with our MSVC /w4 setting. We would therefore need
something like :
bRet = GetMessage( &msg, NULL, 0, 0 );
while( bRet != 0 )
{
if (bRet == -1)
{
// handle the error and possibly exit
}
else
{
TranslateMessage(&msg);
DispatchMessage(&msg);
}
bRet = GetMessage( &msg, NULL, 0, 0 );
}
Which has suddenly become rather long for a normally simple message loop
routine ..... LOL
A nice case for a #pragma warning() ..... or reduce the warning level for
non core components (ping)
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
hbirr(a)svn.reactos.org wrote:
>Simplified the definition of the interrupt handlers for non smp machines.
>
>
>
>Updated files:
>trunk/reactos/ntoskrnl/ke/i386/irqhand.s
>
>
>
>
GMTA :)
Best regards,
Alex Ionescu
I thought that it was agreed that the minimum version of binutils would
be at least 2.15.90.0.2? The fix for this requires a newer version?
make[1]: Entering directory `/home/alex/src/OpSys/reactos'
[GAS] ntoskrnl/ex/i386/interlck_asm.S
ntoskrnl/ex/i386/interlck_asm.S: Assembler messages:
ntoskrnl/ex/i386/interlck_asm.S:440: Error: Unrecognized token `|0x4000'
ntoskrnl/ex/i386/interlck_asm.S:459: Error: Unrecognized token `|
0x4000)' ntoskrnl/ex/i386/interlck_asm.S:459: Error: Unexpected token `'
ntoskrnl/ex/i386/interlck_asm.S:508: Error: Unrecognized token `|
0x4000)'
ntoskrnl/ex/i386/interlck_asm.S:508: Error: Unexpected token `'
ntoskrnl/ex/i386/interlck_asm.S:527: Error: Unrecognized token `|
0x4000)'
ntoskrnl/ex/i386/interlck_asm.S:527: Error: Unexpected token `'
make[1]: *** [obj-i386/ntoskrnl/ex/i386/interlck_asm.o] Error 1
--
http://www.munted.org.uk
Anyone that thinks an imaginary deity is going to protect them against
earthquakes and hurricanes needs psychiatric help.
[GAS] ntoskrnl/ex/i386/fastinterlck_asm.S
ntoskrnl/ex/i386/fastinterlck_asm.S: Assembler messages:
ntoskrnl/ex/i386/fastinterlck_asm.S:408: Error: suffix or operands
invalid for `cmpxchg8b' ntoskrnl/ex/i386/fastinterlck_asm.S:452: Error:
suffix or operands invalid for `cmpxchg8b'
ntoskrnl/ex/i386/fastinterlck_asm.S:492: Error: suffix or operands
invalid for `cmpxchg8b' ntoskrnl/ex/i386/fastinterlck_asm.S:626: Error:
suffix or operands invalid for `cmpxchg8b'
ntoskrnl/ex/i386/fastinterlck_asm.S:658: Error: suffix or operands
invalid for `cmpxchg8b' make[1]: ***
[obj-i386/ntoskrnl/ex/i386/fastinterlck_asm.o] Error 1
--
http://www.munted.org.uk
Anyone that thinks an imaginary deity is going to protect them against
earthquakes and hurricanes needs psychiatric help.
Happy New Year to you all!
2005 was a great year for ReactOS. The core ReactOS code base is now
120MB large. The repository is currently 624MB large and contains
~20500 revisions. ~8000 of these revisions were created in 2005. This
mean 39% of the total number of revisions created during ReactOS'
entire 8 year history was created in 2005!
I'm positive that we will see similar growth (if not more) in 2006.
Keep up the good work!
Best regards,
Casper
Hi,
Can anyone test revision 20525 and select more than one drive and select Tile.
After multiple time selecting cascade and tile it becomes lost!
Thanks,
James
Debug info,
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invali
d usermode buffer
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invali
d usermode buffer
(./subsys/win32k/ntuser/timer.c:157) Unable to locate timer in message queue
(./subsys/win32k/ntuser/timer.c:92) Invalid window handle
MDITile
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invali
d usermode buffer
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invali
d usermode buffer
(./subsys/win32k/ntuser/timer.c:157) Unable to locate timer in message queue
(./subsys/win32k/ntuser/timer.c:92) Invalid window handle
MDICascade
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invali
d usermode buffer
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invali
d usermode buffer
(./subsys/win32k/ntuser/timer.c:157) Unable to locate timer in message queue
(./subsys/win32k/ntuser/timer.c:92) Invalid window handle
(./subsys/win32k/ntuser/timer.c:157) Unable to locate timer in message queue
(./subsys/win32k/ntuser/timer.c:92) Invalid window handle
(./subsys/win32k/ntuser/timer.c:157) Unable to locate timer in message queue
(./subsys/win32k/ntuser/timer.c:92) Invalid window handle
MDITile
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invali
d usermode buffer
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invali
d usermode buffer
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invali
d usermode buffer
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invali
d usermode buffer
When I try to link advapi32 with two widl-generated files (scm_client
and eventlog_client) I get conflict:
[LD] output-i386\lib\advapi32\advapi32.dll
obj-i386\include\idl\svcctl_c.o: In function `ScmrCloseServiceHandle':
D:/trunk/reactos/obj-i386/include/idl/svcctl_c.c:87: multiple definition
of `__MIDL_ProcFormatString'
obj-i386\include\idl\eventlogrpc_c.o:D:/trunk/reactos/obj-i386/include/idl/eventlogrpc_c.c:87:
first defined here
obj-i386\include\idl\svcctl_c.o: In function `ScmrLockServiceDatabase':
D:/trunk/reactos/obj-i386/include/idl/svcctl_c.c:245: multiple
definition of `__MIDL_TypeFormatString'
obj-i386\include\idl\eventlogrpc_c.o:D:/trunk/reactos/obj-i386/include/idl/eventlogrpc_c.c:182:
first defined here
collect2: ld returned 1 exit status
make: *** [output-i386\lib\advapi32\advapi32.dll] Error 1
How to solve this?
> From: ekohl(a)svn.reactos.org
>
> - Service list entries use a pointer to a group list entry
> instead of the goup name.
> - New group list entries are created in the
> unknown-group-list for services of unknown groups.
I'm seeing some crashes now because the lpGroup->lpService pointer is NULL.
Patch below seems to fix it, but I have no idea if it's the correct fix.
GvG
Index: subsys/system/services/rpcserver.c
===================================================================
--- subsys/system/services/rpcserver.c (revision 20508)
+++ subsys/system/services/rpcserver.c (working copy)
@@ -927,7 +927,7 @@
if (lpdwTagId != NULL)
{
- dwError = ScmAssignNewTag(lpService->lpGroup->lpGroupName,
+ dwError = ScmAssignNewTag(lpLoadOrderGroup,
&lpService->dwTag);
if (dwError != ERROR_SUCCESS)
goto done;
@@ -1161,7 +1161,7 @@
if (lpdwTagId != NULL)
{
- dwError = ScmAssignNewTag(lpService->lpGroup->lpGroupName,
+ dwError = ScmAssignNewTag(lpLoadOrderGroup,
&lpService->dwTag);
if (dwError != ERROR_SUCCESS)
goto done;
Sunday night I will remove the svn.reactos.com DNS entry, please use
svn.reactos.org in the future. If you currently have a working copy checked
out from svn://svn.reactos.com you can tell svn to use svn.reactos.org in
the future by:
> From: WaxDragon
>
> Say you have a checkout in ~/src/reactos that was originally checked
> out from svn://svn.reactos.com/trunk/reactos. from the root of the
> checkout (~src/reactos) issue:
>
> svn switch --relocate svn://svn.reactos.com/trunk/reactossvn://svn.reactos.org/trunk/reactos
If you're using Tortoise:
> From: Maarten Bosma
>
> Just right click in root dir, chosse "TortiseSVN > Relocate..." and then
> enter svn://svn.reactos.org/trunk/reactos into the dialog.
Or if you have no local changes you could just delete your working copy and
check out a new one from reactos.org.
If you insist on using svn.reactos.com, add a line "213.173.252.2
svn.reactos.com" to your hosts file (/etc/hosts for Linux/Unix,
%SystemRoot%\System32\drivers\etc\hosts on Windows).
Gé van Geldorp.
gedmurphy(a)svn.reactos.org wrote:
> + CONTROL "Automatically synchronize with an Internet time server", IDC_AUTODAYLIGHT,
> + "Button", BS_AUTOCHECKBOX | WS_GROUP | WS_TABSTOP,11,7,241,10
>
oops, ignore the IDC_AUTODAYLIGHT typo, I'll fix it when I get round to
putting the rest of the code in :)
Ged.
Does anyone mind if I import libjpeg for jpg support ? The License is
not a problem, but the patent might be. Sorry that ask so late (did
already a vendor import). I asked 2 times on IRC and thought that would
be enough, but GreatLord convinced me that I have to asked here too.
Maarten Bosma
PS: The size of the files that would go into reactos/lib is 694 KB.
A while ago, when it was mentioned that ROS 2.9 is soon to be released I
proposed to put out a VMWare image of it - never got a reply though, or
missed it. It has been mentioned multiple times that VMWare is used by some
ROS-devs, so this shouldn't be a problem in the first place.
Since the authors of VMWare have released a so-called VMWare-Player (see
http://www.vmware.com/products/player/ ), it is easy for anyone to get both
(given that they don't have VMWare, yet). VMWare is certainly faster than
QEMU or Bochs for several reasons and thus would be a better "experience"
for potential ROS testers and users.
And please don't tell me that is a kind of endorsement of VMWare, since the
link on the website already is. There is at least one (much cheaper)
alternative to VPC and VMWAre, called Parallels which is not mentioned on
the website at all ( http://www.parallels.com/en/products/workstation/ ).
I just wanted to remind all of you of this idea for (re)consideration.
Cheers,
Oliver
Hi,
I've fixed Alex' win32k changes. First, I try to commit the original
changes. I've used 'svn merge -r20366:20368
svn://svn.reactos.org/trunk/reactos' to get the changes and I'm using
'svn commit' to commit the changes again. I get an error message:
I:\Sandbox\ros_work\reactos>svn commit
Lösche include\win32k\bitmaps.h
<snip>
Sende w32api\include\wingdi.h
Übertrage Daten ................svn: Übertragen fehlgeschlagen (Details
folgen):
svn: Source url
'svn://svn.reactos.org/trunk/reactos/include/win32k/ntgdibad.h' is from
different repository
svn: Ihre Log-Meldung wurde in einer Temporärdatei abgelegt:
svn: 'I:/Sandbox/ros_work/reactos/svn-commit.2.tmp'
Usually, I get all error messages in german. What do I make wrong?
- Hartmut
ion(a)svn.reactos.org wrote:
> + /* Value changed... wait until it's locked */
> + while (*SpinLock == 1) YieldProcessor();
This might be optimized away since SpinLock was not defined as volatile
KSPIN_LOCK*
- Thomas
greatlrd(a)svn.reactos.org wrote:
> some case from win32k can call to RtlClearAllBits with NULL pointer. and check for null pointer after RtlClearAllBits. This take care of those case for moment.
This change is wrong, please revert it and fix win32k instead.
- Thomas
ion(a)svn.reactos.com wrote:
> - Also made the boot-up screen black, not blue, since that's the actual color it's been after NT4. If booting without NOGUIBOOT, this results in a much nicer transition to the boot screen (especially if using the NTLDR theme)
>
This changes the 'blue screen of death' to a 'black screen of death'. I
don't like it if you change every and any thing to the real windows
implementation. I see no reason for this cloning.
- Hartmut
Why was this done? Having these bugs listed as blockers to 399 allows
devs to find the old bugs easier in case of regressions. I don't see
any downsize to keeping them listed.
On 12/28/05, ReactOS.Bugzilla(a)reactos.org <ReactOS.Bugzilla(a)reactos.org> wrote:
> http://www.reactos.org/bugzilla/show_bug.cgi?id=399
>
>
> greatlord(a)reactos.com changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> BugsThisDependsOn|398, 400, 937 |
>
>
>
>
> ------- Additional Comments From greatlord(a)reactos.com 2005-12-28 17:54 CET -------
> Bug 398 are fixed, Bug 400 are fixed, Bug 937 are fixed
> I remove tuse from Bug depends on.
>
>
>
> --
> Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
> You are the QA contact for the bug, or are watching the QA contact.
> _______________________________________________
> Ros-bugs mailing list
> Ros-bugs(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-bugs
>
WD
--
<Russell> argh
<Russell> iterator shenanigans :/
ion(a)svn.reactos.com wrote:
> - Major Win32k Header Cleanup: Add ntgdi.h based on latest Platform SDK Public header. It contains the official definitions for NtGdi APIs.
> - Added ntgdityps.h for structures needed to use the header (which were sadly not publically shipped).
> - Removed internal win32k header data from public headers and put it to internal win32k headers.
> - Fixed ntuser.h STDCALL->WINAPI.
> - Added ntgdihdl.h for shared GDI Handle information between gdi32/win32k
> - Added ntusrtyp.h for some shared NtUser types.
> - Added ntgdibad.h which contains all non-compatible NtGdi prototypes, along with a detailed comment for each, and information on how to fix it. I had a 20 000+ line patch fixing all these issues, but it contained many bugs and I scrapped it in place for this approach, which while dirtier at first, simplifies the number of changes needed so that others can work on it as well.
> - Fixed some gdi32/win32k/user32 header issues.
>
>
This change breaks running ros on qemu and real hardware. I don't see a
mouse cursor after the gui is started. If I move the mouse, ros does
crash. If I don't move the mouse, ros starts up to the first device
install dialog. After this ros terminates itself and does switch off the
computer.
- Hartmut
(ntoskrnl\mm\mm.c:317) Address: 87dcf974
Unhandled exception
ExceptionCode: c0000005
Faulting Address: 87dcf974
Address: 77e9238b C:\ReactOS\system32\user32.dll
CS:EIP 1b:77e9238b
DS 23 ES 23 FS 3b GS 0
EAX: 87dcf974 EBX: 0144fdec ECX: 0144ffb4
EDX: f000ff53 EBP: 0144fb6c ESI: 00000000 ESP: 0144fb24
EDI: 00000000 EFLAGS: 00000246
Frames:
77e50000+2f461 C:\ReactOS\system32\user32.dll
77e50000+2fdf6 C:\ReactOS\system32\user32.dll
77e50000+31fb6 C:\ReactOS\system32\user32.dll
10000000+72cf C:\ReactOS\system32\win32csr.dll
77e50000+52657 C:\ReactOS\system32\user32.dll
77e50000+53a52 C:\ReactOS\system32\user32.dll
7c900000+a15b C:\ReactOS\system32\ntdll.dll
10000000+764e C:\ReactOS\system32\win32csr.dll
7c800000+2fe1d C:\ReactOS\system32\kernel32.dll
(./subsys/win32k/ntuser/window.c:581) thread cleanup: while destroy
wnds, wnd=0x870d11a4
(subsys\win32k\main\dllmain.c:281) thread clean: remove reference obj
0x870d11a4
(subsys\win32k\main\dllmain.c:281) thread clean: remove reference obj
0x870d11a4
KeBugCheckWithTf at ntoskrnl\ke\i386\exp.c:1242
A problem has been detected and ReactOS has been shut down to prevent
damage to your computer.
The problem seems to be caused by the following file: win32k.sys
Technical information:
*** STOP: 0x0000001E (0xc0000005,0x9da2ba1f,0x00000000,0xfffffff4)
*** win32k.sys - Address 0x9da2ba1f base at 0x9d99b000, DateStamp 0x0
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:9da2ba1f <win32k.sys:90a1f
(./subsys/win32k/ntuser/msgqueue.c:271 (co_MsqTranslateMouseMessage))>
cr2 fffffff4 cr3 f58c000 Proc: 80ac2050 Pid: 7c <csrss.exe> Thrd:
80c6d220 Tid: b4
DS 23 ES 23 FS 30 GS 0
EAX: fffffff4 EBX: 80c6d5f8 ECX: 00000000
EDX: 9da883d0 EBP: 9e194a8c ESI: 0164fe24 ESP: 9e1949f0
EDI: 9e194d64 EFLAGS: 00000297 kESP 9e1949f0 kernel stack base 9e192000
Frames:
<win32k.sys:9170b (./subsys/win32k/ntuser/msgqueue.c:621
(co_MsqPeekHardwareMessage))>
<win32k.sys:92bfa (./subsys/win32k/ntuser/msgqueue.c:1259
(co_MsqFindMessage))>
<win32k.sys:88626 (./subsys/win32k/ntuser/message.c:731
(co_IntPeekMessage))>
<win32k.sys:890a3 (./subsys/win32k/ntuser/message.c:941
(co_IntWaitMessage))>
<win32k.sys:893d2 (./subsys/win32k/ntuser/message.c:1051
(NtUserGetMessage))>
<ntoskrnl.exe:9a8ea (ntoskrnl\ke\i386\syscall.S:372 (KiSystemService))>
<user32.dll:52bd3 (lib/user32/windows/message.c:1166 (GetMessageW))>
>From the way ROS tends to hamng up when running CPU-intense processes,
I'm starting to suspect ROS is in fact not pre-emptively multitasking.
And this seems to have gotten worse from 0.2.8 to 0.2.9. Any thoughts?
/nitro2k01
--
The blog of nitro2k01: <http://soundandcomplete.blogspot.com/>
Saliga äro de som kan stava till 2k01!
hpoussin(a)svn.reactos.com wrote:
> Replace implementation of QueryServiceConfigW by a stub (like in pre-20255), as rpcrt4 throws sometimes an exception and breaks PnP manager
>
>
LOL!
That was no surprise! Sounds like Wine need to fix their broken code.
I had a patch but I'm still ban from sending email to wine-patch! So~
rm * the patch!
James
Hi,
I am pleased to announce that with Ge's patch to fix Exception
handling and Brandon and Thomas's work on the pagefile it is now
possible to install Office 2000 on the trunk. You will get quite a few
errrors at the end of the install due to missing dlls from MDAC/ADO
that Office2000 expects a Windows 2000 system to ship with, which we
of course do not have stubbed at this time. Thanks to Eric Kohls work
on services msiexec is mostly happy installing Office2000 if started
from the command line like the following
msiexec /i data1.msi
There is still issues with setup.exe properly working althogh I think
this is more due to version numbers we report.
We are still unable to run Office applications at this time due to
unhandled exceptions which look like they are due to COM errors as
well as some problems due to the amount of memory we are reporting.
Both Winword and Access display message boxes saying that there is not
enough memory to run the application. Also even if we do get those
issues fixed we are currently blocked by the registry instablity.
--
Steven Edwards - ReactOS and Wine developer
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
ReactOS on LinuxTag 2006
From 3. till 6. May 2006 over 15000 guests will visit the LinuxTag in
Wiesbaden (Germany).
They provide free stands on the expo for open source projects.
I think ReactOS could be there too. Wiesbaden is not far from where I
live and if some of
the developers are interrested we could talk about making a stand.
Best Regards,
dom
I have found some problems running Allegro programs in ReactOS. When I
have tested it they started up and the mouse moves the upper right hand
corner of the screen and ReactOS apparently hangs. I'm curious why is
this happening; although, I think it is possibly some bugs (or bug) that
is causing it, or it is caused by an unimplemented feature. It is most
like located in the DirectX and OpenGL components. This realtes to bug
1112.
Merry Christmas!! :D
On 12/24/05, ros-dev-request(a)reactos.org <ros-dev-request(a)reactos.org> wrote:
> Send Ros-dev mailing list submissions to
> ros-dev(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
> ros-dev-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-dev-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
>
> Today's Topics:
>
> 1. Merry Christmas! (Filip Navara)
> 2. Re: Merry Christmas! (Rick Langschultz)
> 3. Re: Merry Christmas! (James Tabor)
> 4. Re: Merry Christmas! (Jerry)
> 5. Re: Merry Christmas! (Sebastian Gasiorek)
> 6. Re: Merry Christmas! (TwoTailedFox)
> 7. Merry Christmas (Magnus Olsen)
> 8. Re: Merry Christmas! (David Hinz)
> 9. Re: Merry Christmas! (Jonathon Keogh)
> 10. Re: PC offered with ReactOS preinstalled? (wac)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 24 Dec 2005 22:36:45 +0100
> From: Filip Navara <xnavara(a)volny.cz>
> Subject: [ros-dev] Merry Christmas!
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <43ADBF6D.9020206(a)volny.cz>
> Content-Type: text/plain; charset=ISO-8859-2; format=flowed
>
> Hi all,
>
> I thought we can't break the tradion, so ... Merry Christmas and Happy
> New Year! :-)
>
> - Filip
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 24 Dec 2005 15:58:11 -0600
> From: Rick Langschultz <rlangschultz(a)cox.net>
> Subject: Re: [ros-dev] Merry Christmas!
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <4912B7CF-9876-438A-A7D5-8F0E37ACAEFE(a)cox.net>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> Merry Christmas Filip ;-) and Happy New Year
> On Dec 24, 2005, at 3:36 PM, Filip Navara wrote:
>
> > Hi all,
> >
> > I thought we can't break the tradion, so ... Merry Christmas and
> > Happy New Year! :-)
> >
> > - Filip
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 24 Dec 2005 22:07:21 +0000
> From: James Tabor <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net>
> Subject: Re: [ros-dev] Merry Christmas!
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID:
> <43ADC699.5020803(a)adsl-64-217-116-74.dsl.hstntx.swbell.net>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Filip Navara wrote:
> > Hi all,
> >
> > I thought we can't break the tradion, so ... Merry Christmas and Happy
> > New Year! :-)
> >
> > - Filip
> Yeah! Merry Christmas!
> 8^D
> James
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 24 Dec 2005 16:07:34 -0600
> From: Jerry <crashfourit(a)gmail.com>
> Subject: Re: [ros-dev] Merry Christmas!
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <43ADC6A6.1040503(a)gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Merry Christmas, Rick, Filip and all those who will read this.
> Rick Langschultz wrote:
>
> > Merry Christmas Filip ;-) and Happy New Year
> > On Dec 24, 2005, at 3:36 PM, Filip Navara wrote:
> >
> >> Hi all,
> >>
> >> I thought we can't break the tradion, so ... Merry Christmas and
> >> Happy New Year! :-)
> >>
> >> - Filip
> >> _______________________________________________
> >> Ros-dev mailing list
> >> Ros-dev(a)reactos.org
> >> http://www.reactos.org/mailman/listinfo/ros-dev
> >
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
>
>
> ------------------------------
>
> Message: 5
> Date: Sat, 24 Dec 2005 23:12:23 +0100
> From: Sebastian Gasiorek <zebasoftis(a)gmail.com>
> Subject: Re: [ros-dev] Merry Christmas!
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <77c53c6f0512241412m1644d008n(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Merry Christmas
> and
> Happy New Year to everybody :-)
>
>
> 2005/12/24, Rick Langschultz <rlangschultz(a)cox.net>:
> >
> > Merry Christmas Filip ;-) and Happy New Year
> > On Dec 24, 2005, at 3:36 PM, Filip Navara wrote:
> >
> > > Hi all,
> > >
> > > I thought we can't break the tradion, so ... Merry Christmas and
> > > Happy New Year! :-)
> > >
> > > - Filip
> > > _______________________________________________
> > > Ros-dev mailing list
> > > Ros-dev(a)reactos.org
> > > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
My Spanish is not that great, but I get the impression that they're offering
PCs with ReactOS preinstalled here:
http://articulo.mercadolibre.com.mx/MLM-10172918--_JM Can anyone confirm
that? Not that I mind, I'm just curious.
Gé van Geldorp.
Hi
I bit sick of correct it hold time for make a rc compile with ms vs
to right one.
Here is the rule to use it
Rule for SUBLANG_DEFAULT
Basic all langues only have one offcial langues must use SUBLANG_DEFAULT
example Czech, Danish, Hungarian, Polish and more.
Rule for SUBLANG_NEUTRAL
basic all langues only have more one offcial langues must use SUBLANG_NEUTRAL
example German, French, English, Swedish, and more
please think of this when you are writen or change .rc file.
Thanks
Could you do this for trunk too?
It is very annoying, if you can't see the buttons of the locale dialog,
plus it looks very unprofessional...
Maybe at least 800x600x8.
Greets,
David Hinz
turner(a)svn.reactos.com schrieb:
> set default res to 800x600x16
>
>
> Updated files:
> branches/ros-branch-0_2_9/reactos/bootdata/hivesys.inf
>
> _______________________________________________
> Ros-svn mailing list
> Ros-svn(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-svn
>
Brandon Turner wrote:
> I plan on releasing 0.2.9 final today and those devs that havent did
> their change logs yet please make an efforts. ;)
>
> http://www.reactos.org/wiki/index.php/ChangeLog-0.2.9
> www.brandonturner.org/029.txt
>
> that text file has all the commits in it.
>
> Brandon
>
Putting this on ros-dev too as not all devs are on ros-general.
-----Original Message-----
From: Royce Mitchell III [mailto:royce3@ev1.net]
Sent: 23 December 2005 03:18
To: ReactOS Development List
Subject: Re: [ros-dev] Change log
Ged Murphy wrote:
> Ge van Geldorp wrote:
>
>>> From: Magnus Olsen
>>>
>>> U need give lest 2-3 day when u request changelog not every are on
>>> same time line
>>>
>>
>>
>> The branch was created 2 weeks ago. Plenty of time for everyone to
>> get their
>> changelog entries in place.
>>
>> GvG
>>
>
>
> I also announced the creation of the changelog exactly 2 weeks ago,
> and various at times since then
>
> http://www.reactos.org/archives/public/ros-dev/2005-December/006728.html
>
Could we get a page setup describing how to pull down ( via cmd line and
tortoise ) a list of changes that occured between a previous release and
the current one? We didn't receive this information until about 2 days
ago. Yes I know I could probably find it on the net, but it would also
help to have this page list the revision #'s associated with each
release, just so that all info is in one place to make it easy for us to
record our respective contributions to the release.
Thanks.
In Tortoise, I just download the whole history for the branch and then
filter it with the date pull downs in the top left. It's as easy as that and
gives more information than the text version.
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
I may be just an idiot or blind, but I can't seem to find any
information on building freeldr, and it doesn't seem to have a makefile.
Everything that I can find points to it being loadable by GRUB and the
like, but I'm not sure why I can't find the *how* on building it.
Am I just blind, or missing something extremely obvious?
(Yes, I have been searching Google for a little while now... I'm not
turning anything up, yet.)
Thanks,
Mike
--
Michael B. Trausch fd0man(a)gmail.com
"Why geeks like computers: unzip, strip, touch, finger, grep, mount,
fsck, more, yes,fsck,fsck,fsck,umount, sleep." :-)
Phillip Susi wrote:
> Wait a second... why is it sending only one byte at a time?
> The caller
> is only send()ing one byte at a time?
This is true. Although Send() will return indicating the data has been sent,
nagling should hold the actual packet back until it is full, however this
should only happen if there is unconfirmed data i.e. no ACK.
To avoid any confusion, you can switch nagling off with the TCP_NODELAY flag
I'm interested in this bug, but I'm not around tonight to play about with it
:(
************************************************************************
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
Ge van Geldorp wrote
> If there are no objections, I want to commit the attached
> patch.
Looks good
+1
************************************************************************
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
Gang,
I have been unsuccessful in building a working MP bootcd for a
while now. I conferred with Hartmut about some of the details, but
still cannot get it working.
This is what I tried:
1. Set MP=1 in config.xml
2. Hacked the hal xml files to make halmp.dll hal.dll on the bootcd, per Harmut
Index: halx86/up/halup.xml
===================================================================
--- halx86/up/halup.xml (revision 20282)
+++ halx86/up/halup.xml (working copy)
@@ -1,6 +1,6 @@
<module name="halup" type="kernelmodedll">
<importlibrary definition="../../hal/hal.def" />
- <bootstrap base="reactos" nameoncd="hal.dll" />
+ <bootstrap base="reactos" />
<include base="hal_generic">../include</include>
<include base="ntoskrnl">include</include>
<define name="_DISABLE_TIDENTS" />
Index: halx86/mp/halmp.xml
===================================================================
--- halx86/mp/halmp.xml (revision 20282)
+++ halx86/mp/halmp.xml (working copy)
@@ -1,6 +1,6 @@
<module name="halmp" type="kernelmodedll">
<importlibrary definition="../../hal/hal.def" />
- <bootstrap base="reactos" />
+ <bootstrap base="reactos" nameoncd="hal.dll"/>
<include base="hal_generic">../include</include>
<include base="ntoskrnl">include</include>
<define name="_DISABLE_TIDENTS" />
3. make bootcd, as normal
The resulting bootcd fails to boot under "qemu -smp 2" with the following trace:
(./ntoskrnl/ke/main.c:295)
---------------------------------------------------------------
(./ntoskrnl/ke/main.c:296) ReactOS 0.3-SVN (Build 20051221-r20282)
(hal/halx86/mp/apic.c:420) Getting VERSION: 50011
(hal/halx86/mp/apic.c:423) Getting VERSION: 50011
(hal/halx86/mp/apic.c:454) Getting ID: 0
(hal/halx86/mp/apic.c:457) Getting ID: f000000
(hal/halx86/mp/apic.c:554) CPU0:
(hal/halx86/mp/apic.c:555) Physical APIC id: 0
(hal/halx86/mp/apic.c:556) Logical APIC id: 0
(hal/halx86/mp/apic.c:557) 00000000 00000000 f0000000
(hal/halx86/mp/apic.c:584) CPU0:
(hal/halx86/mp/apic.c:585) Physical APIC id: 0
(hal/halx86/mp/apic.c:586) Logical APIC id: 1
(hal/halx86/mp/apic.c:587) 00000000 01000000 f0000000
(hal/halx86/mp/apic.c:588) 0
(hal/halx86/mp/apic.c:619) enabled ExtINT on CPU#0
Used memory 131072Kb
(./ntoskrnl/mm/mminit.c:386) Kernel Stack Limits. InitTop =
0x8013c000, Init = 0x80139000
(./ntoskrnl/mm/mm.c:283) No current process
(hal/halx86/mp/processor_mp.c:112) Attempting to boot CPU 1
(hal/halx86/mp/apic.c:1014) Attempting to boot CPU 1
(hal/halx86/mp/apic.c:1044) 80572be0 25000 80001000 0
(hal/halx86/mp/apic.c:554) CPU1:
(hal/halx86/mp/apic.c:555) Physical APIC id: 1
(hal/halx86/mp/apic.c:556) Logical APIC id: 0
(hal/halx86/mp/apic.c:557) 01000000 00000000 f0000000
(hal/halx86/mp/apic.c:584) CPU1:
(hal/halx86/mp/apic.c:585) Physical APIC id: 1
(hal/halx86/mp/apic.c:586) Logical APIC id: 2
(hal/halx86/mp/apic.c:587) 01000000 02000000 f0000000
(hal/halx86/mp/apic.c:588) 1
(hal/halx86/mp/apic.c:624) masked ExtINT on CPU#1
CPU 1 is now running
(ntoskrnl/ke/i386/exp.c:539) Ignoring P6 Local APIC Spurious Interrupt Bug...
(./ntoskrnl/ke/ipi.c:88) CPU0, waiting longer than 5 seconds to start
the ipi routine
KeBugCheck at ./ntoskrnl/ke/ipi.c:89
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:2630> ./ntoskrnl/ke/bug.c:0 ()
<ntoskrnl.exe:2668> ./ntoskrnl/ke/bug.c:504 (KeBugCheck)
<ntoskrnl.exe:414f> ./ntoskrnl/ke/ipi.c:0 ()
<ntoskrnl.exe:4470> ./ntoskrnl/ke/ipi.c:0 ()
<ntoskrnl.exe:44df> ./ntoskrnl/ke/ipi.c:174 (KeIpiGenericCall)
<ntoskrnl.exe:abd71> ./ntoskrnl/mm/i386/page.c:1043 (MmDeleteVirtualMapping)
<ntoskrnl.exe:ac891> ./ntoskrnl/mm/i386/page.c:431 (MmDeletePageTable)
<ntoskrnl.exe:d52ce> ./ntoskrnl/mm/mminit.c:459 (MmInit3)
<ntoskrnl.exe:cf7c0> ./ntoskrnl/ex/init.c:622 (ExpInitializeExecutive)
<ntoskrnl.exe:66fc> ./ntoskrnl/ke/main.c:106 (KiSystemStartup)
<ntoskrnl.exe:cd851> ./ntoskrnl/ke/main.c:300 (_main)
<ntoskrnl.exe:104b> ./ntoskrnl/ke/i386/main_asm.S:46 (NtProcessStartup)
An MP bootcd I made several months ago (~18xxx) did the same thing on
a Abit BP6 with dual Celerons, so I'm fairly confident qemu is acting
properly. I still have the BP6 and am willing to test MP builds, but
I wasted about 10 CD-R's trying to get a working MP bootcd before
giving up.
Am I just doing something wrong? I would like to get this worked out
and documented somewhere.
WD
--
<Russell> argh
<Russell> iterator shenanigans :/
I've been tracking down a problem with ibrowser being extremely slow for me
(it took 64 sec to load http://www.reactos.org). It turns out to be a
problem associated with the loopback interface. The attached test program
(gcc -o loop.exe loop.c -lws2_32) is the minimum test program to demonstrate
the problem. It occurs when you send a small amount of data over the
loopback interface when there is no pending recv (so you send, then start a
recv for the data, then another send, then another recv, no recv waiting
while you send).
Sequence of events:
- Start first send
- TCP/IP stack queues the data at the receiving end
- First send returns
- Start first recv
- Queued data is retrieved, but it is determined that there's plenty of
space in the TCP window left, so there is no ACK sent back
- First recv returns
- Start second send
- tcp_output determines that the connection is not idle (there is some
un-ACKed data) and queues the data at the sending end
- Second send returns
- Start second recv
- Since there is no data waiting at the receiving end, recv just sits there
- An internal timer with a period of 2.5 sec expires
- The timer proc notices that there is an ACK pending
- ACK is sent back to the sending end
- Sending end determines connection is idle now and sends the queued data to
the receiving end
- Timer proc terminates and reschedules itself
- Data has now arrived at the receiving end and can be retrieved by the
waiting recv. Again no ACK is sent back
- Second recv returns
- Third send starts, queues its data at sending end and returns
- Third recv starts, has to wait 2.5 sec for the internal timer to timeout
and then returns
- etc.
Although I understand what's wrong, I have a bit of difficulty trying to
figure out how to fix it. Attached is a proposed fix, which basically
attacks the problem at the sending end by removing the check if the
connection is idle or not. With that fix the loop.c program works as I
expect and http://www.reactos.org loads in a much more reasonable 2-3 sec in
ibrowser. The problem that I have with the fix is that it's a change in code
we borrowed from the BSD stack. I can hardly imagine that a piece of
software so heavily used as the BSD stack would have such a fundamental
problem.
Any thoughts?
GvG
I've installed a script on the webserver which will run Doxygen (a source
cross-referencing tool, see http://www.doxygen.org) on our complete source
tree. The script runs once a day. The results can be viewed on
http://www.reactos.org/generated/doxygen (or choose "Doxygen" from the
"Development" menu on the website).
GvG
David Hinz wrote:
> Somewhere in reactos/lib/cabinet I found sourcecode calling functions
> like err, and the strings it gave to these functions looked like
> something output to the user e.g. errormessages like file * couldn't
> be found or something like this, so I wondered, if this should be
> translatable.
> As I don't know what kind of stings should be translatable, I
> just asked.
You need to understand the context in which the message is used. If it's
system debug message, it will normally be hardcoded in. If it's a generic
Win32 error message it should be picked up with FormatMessage. These will be
output in the users preferred language via the LANG_SYSTEM_DEFAULT or
LANG_USER_DEFAULT flags. Then you have simple MessageBox outputs which can
be picked out of a resource file, but are generally hardcoded in. There are
many other situations and usages, but I'll stop there.
As already said, becoming a programmer is the only real way of understanding
it all.
> Well, you say I should learn some things like structures of resource
> files, do you have any links for me?
There are thousands of C tutorials on the net. Here are a few:
Tutorials : http://www.cprogramming.com/tutorial.html
Forgers win32 : http://www.winprog.org/tutorial/
Everyone has their favourite books, but these are probably the most popular
for learning C and Windows programming:
K & R :
http://www.amazon.com/gp/product/0131103628/qid=1135081344/sr=2-1/ref=pd_bbs
_b_2_1/104-6581600-7986334?s=books&v=glance&n=283155
C Primer Plus :
http://www.amazon.com/gp/product/0672326965/qid=1135081234/sr=1-1/ref=sr_1_1
/104-6581600-7986334?s=books&v=glance&n=283155
Petzold :
http://www.amazon.com/gp/product/157231995X/qid=1135081418/sr=1-1/ref=sr_1_1
/104-6581600-7986334?s=books&v=glance&n=283155
Have fun,
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
We're coming close to the 0.2.9 release now, we need to get the changes into
the wiki sooner rather than later :)
http://www.reactos.org/wiki/index.php/ChangeLog-0.2.9
<http://www.reactos.org/wiki/index.php/ChangeLog-0.2.9>
************************************************************************
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
As GreatLord said, you will need programming knowledge to do this.
If you want to start making progress with this, you could start by getting a
sound understanding of C and basic Windows programming, including resource
file syntax. Then work from there.
You will generally find though that most stuff that should be in a resource
file, already is.
What have you found to make you think otherwise?
-----Original Message-----
From: David Hinz [mailto:post.center@gmail.com]
Sent: 20 December 2005 07:08
To: ReactOS Development List
Subject: Re: [ros-dev] Hardcoded strings
Sure, but the problem is, I don't really know which strings this are,
and how I can find them.
************************************************************************
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
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
The program below (when compiled with MSVC6, multithreaded DLL runtime) only
prints "in first handler" on ReactOS and then gets into an endless exception
loop:
int
main(int argc, char *argv[])
{
__try
{
RaiseException(0x55aa, 0, 0, NULL);
}
__except(EXCEPTION_EXECUTE_HANDLER)
{
printf("in first handler\n");
}
__try
{
RaiseException(0xaacc, 0, 0, NULL);
}
__except(EXCEPTION_EXECUTE_HANDLER)
{
printf("in second handler\n");
}
return 0;
}
I believe the reason is that our RtlUnwind removes the target exception
frame too, which it shouldn't do. The following patch seems to solve the
issue:
Index: lib/rtl/i386/exception.c
===================================================================
--- lib/rtl/i386/exception.c (revision 20225)
+++ lib/rtl/i386/exception.c (working copy)
@@ -333,7 +333,10 @@
RegistrationFrame2 = RegistrationFrame2->Next;
/* Remove this handler */
- RtlpSetExceptionList(OldFrame);
+ if (RegistrationFrame2 != RegistrationFrame)
+ {
+ RtlpSetExceptionList(OldFrame);
+ }
}
}
but I'm no expert on exception issues. Is this indeed the correct fix?
GvG
I quote from the ReactOS Weekly Newsletter - Volume 1, Issue 8
"0.2.9? Another One?
Yup, we have another release planned for you all. 0.2.9 is our last
release before the very-much-anticipated 0.3.0 release."
Could we stop saying that? 0.3.0 is not the release after 0.2.9, nor
0.2.8, nor 0.2.5! 0.3.0 will happen when we hit the stated goals, and
unless networking gets some serious attention, we will see 0.2.10.
So, please, can we stop saying "This is the last release before
0.3.0"? It makes us look bad, and confuses people when we release yet
another 0.2.x.
Don't get me wrong, we are closer to 0.3.0 than ever before, but there
are still many bugs.
WD
--
<Russell> argh
<Russell> iterator shenanigans :/
FYI. svn.reactos.org may be affected.
Casper
> -----Original Message-----
> From: WEBPARTNER Drift Information [mailto:drift@webpartner.dk]
> Sent: 15. december 2005 08:21
> To: driftinfo(a)webpartner.dk
> Subject: Strømarbejde i Serverpark Østerbro
>
> Affected customers : Serverpark Østerbro
>
> We are in the finishing phase of several improvement to our powersupply. Improvements witch gives
> us added capacity, to supply current and future power and cooling needs.
>
> Københavns Energi handle the last part of the work witch is done d. 19.12.2005 at 24:00 to d.
> 20.12.2005 at 04:00, while the work is done we are operating on disel generator. We dont expect any
> interuptions but in the period above there is an increased risc for outage.
>
> We are at your disposal if you need our assistance in relation to this work.
>
> Best regards
> WEBPARTNER A/S
>
> Visit us: http://www.webpartner.dk
> Mailing list removal: http://www.webpartner.dk/336
"insecure-by-inattention" - by that I mean software that must run as super-user
or otherwise (otherstupidly) it won't run at all. ReactOS is not only intended
as a plug-in replacement for MS Windows, if I read this-and-that correctly, it's
also intended to "get it done right". And so we can't have super-user as
default user, because that is Microsoft's thorn-in-the-flesh, and they can have
it. I don't want it.
What I've been thinking is there is quite a bit of useful information and
knowledge being actively developed and used in the Unix/BSD/Linux field for
handling that sort of problem. The BSD chroot jail is one such implementation -
there are even some aspects of the MS Windows directory structure that would
simplify the adaption of the chroot jail to the ReactOS.
[hardware]\Program Files\Abracadabra-Malware-Magnet\
"Abracadabra-Malware-Magnet" is a separate subdirectory within the Program Files
directory. Chroot jail, if I remember correctly, requires a separate directory
for each chrooted program so it sees itself as the one-and-only love of its
kernel's uptime. The MS Windows directory structure already has this separable
directory structure.
What needs to be done is to ensure that it thinks it's the only one around.
There would be some sizeable problems - ensuring that the dlls would be
sufficiently robust to avoid being hijacked, is just one, ensuring that it
couldn't make any changes to dlls outside its directory is a bigger one, but
that could be handled by making sure it installed all its (uniquely) needed dlls
in its chroot jail. Which a lot of Win32 programs do anyway.
What do people think?
Wesley Parish
"Sharpened hands are happy hands.
"Brim the tinfall with mirthful bands"
- A Deepness in the Sky, Vernor Vinge
"I me. Shape middled me. I would come out into hot!"
I from the spicy that day was overcasked mockingly - it's a symbol of the
other horizon. - emacs : meta x dissociated-press
Latest SVN is crashing with the following message:
Assertion 'Class->refs == 0' failed at ./subsys/win32k/ntuser/class.c
line 69
I created bug report here:
http://www.reactos.org/bugzilla/show_bug.cgi?id=1145
This bug only occurs on ANSI build of app, and is 100% reproduceable for
me. I suspect this bug may effect 0.2.9...
Hi,
I would like to attend the GPLv3 launch event to gain more knowlege
about it and how it will affect us. If you guys would like me to go on
the FSF dime then please drop my name here
http://gplv3.fsf.org/recommend
Thanks
--
Steven Edwards - ReactOS and Wine developer
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Although we're in feature freeze, do you think it's worth including the
getfirefox utility to the 0.2.9 branch?
It's a great little app and I had firefox running for a few hours last
night with no real issues.
I'm thinking it would be good to get lots of feedback to ensure it's
stable for the upcoming network release.
As this will be one of our selling points, we need to ensure it's stability.
Ged.
gvg(a)svn.reactos.com wrote:
> Fix by Royce3:
> Don't wait 10 sec after starting an app via a .lnk file (bug 1107)
>
>
>
> Updated files:
> trunk/reactos/lib/shell32/shelllink.c
>
So, was that the cause of that?
Wow!
James
> From: gvg(a)svn.reactos.com
>
> Don't pop-up device installer screen.
> Fixes bug 1026
I've committed this to the branch only, not sure if it should be committed
to trunk also. I'd like to hear how the PnP guys feel about this.
GvG
Thanks, I've been wonderig when this would be implemented ;)
On 12/14/05, navaraf(a)svn.reactos.com <navaraf(a)svn.reactos.com> wrote:
> Implement "!bug <number>" command.
>
>
> Added files:
> trunk/irc/TechBot/TechBot.Library/BugCommand.cs
>
> Updated files:
> trunk/irc/TechBot/TechBot/App.config
> trunk/irc/TechBot/TechBot/ServiceThread.cs
> trunk/irc/TechBot/TechBot.Console/App.config
> trunk/irc/TechBot/TechBot.Console/Main.cs
> trunk/irc/TechBot/TechBot.Library/IrcService.cs
> trunk/irc/TechBot/TechBot.Library/TechBot.Library.prjx
> trunk/irc/TechBot/TechBot.Library/TechBotService.cs
>
> _______________________________________________
> Ros-svn mailing list
> Ros-svn(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-svn
>
--
"I had a handle on life, but then it broke"
Hi all
ReactOS r20143 compilation on my Linux failed with messages:
[LD]
../../../../../../home/zv/reactos/output-i386/lib/freetype/freetype.dll
../../../../../../home/zv/reactos/obj-i386/lib/freetype/src/truetype/truetype.o:
In function `TT_RunIns':
/mnt/d/zv/ReactOS/src/reactos/lib/freetype/src/truetype/ttinterp.c:7467:
undefined reference to `_FT_MulDiv_No_Round'
collect2: ld returned 1 exit status
Environment:
gcc 3.4.2-20040916-1
binutils-2.15.94-20050118-1
Can anybody help me?
WBR,
DarkHobbit
Hi all,
Dont know where to file this one.
I have mozilla, winefile and Quake (in demo mode, windowed) running at the same time.
Other apps had been opened, WinObj and Abiword. I moved the mouse over mozilla with
the Reactos web page, to open RosDev mail.
Than!
(./ntoskrnl/ex/sysinfo.c:1098) PID: 0, KernelTime: 320755 PFFree: 50 PFUsed: 0
MC_CACHE 9121, MC_USER 9848, MC_PPOOL 2476, MC_NPPOOL 10011, MmStats.NrFreePages
222457
(KERNEL32:./lib/kernel32/mem/global.c:412) Memory Load: 12%
<Mozilla does this global memory check ever minute, ~60 seconds>
WARNING: NtGdiSetDIBitsToDevice at ./subsys/win32k/objects/dib.c:342 is UNIMPLEMENTED!
WARNING: NtGdiSetDIBitsToDevice at ./subsys/win32k/objects/dib.c:342 is UNIMPLEMENTED!
WARNING: NtGdiSetDIBitsToDevice at ./subsys/win32k/objects/dib.c:342 is UNIMPLEMENTED!
WARNING: NtGdiSetDIBitsToDevice at ./subsys/win32k/objects/dib.c:342 is UNIMPLEMENTED!
WARNING: NtGdiSetDIBitsToDevice at ./subsys/win32k/objects/dib.c:342 is UNIMPLEMENTED!
WARNING: NtGdiSetDIBitsToDevice at ./subsys/win32k/objects/dib.c:342 is UNIMPLEMENTED!
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0xcdcdcdcd could not be read: Page not present.
kdb:> bt
Eip:
<win32k.sys:913df (./subsys/win32k/ntuser/msgqueue.c:517 (co_MsqPeekHardwareMessage))>
Frames:
<win32k.sys:92ce1 (./subsys/win32k/ntuser/msgqueue.c:1259 (co_MsqFindMessage))>
<win32k.sys:8870d (./subsys/win32k/ntuser/message.c:731 (co_IntPeekMessage))>
<win32k.sys:88ef8 (./subsys/win32k/ntuser/message.c:871 (NtUserPeekMessage))>
<ntoskrnl.exe:9aa8c (ntoskrnl/ke/i386/syscall.S:372 (KiSystemService))>
<user32.dll:53225 (lib/user32/windows/message.c:1255 (PeekMessageW))>
<gkwidget.dll:94eb>
<gkwidget.dll:95c8>
<appshell.dll:8043>
<mozilla.exe:1969>
<mozilla.exe:2d2e>
<KERNEL32.dll:29583 (./lib/kernel32/process/create.c:68 (BaseProcessStartup))>
<00000000>
kdb:> cont
KeBugCheckWithTf at ntoskrnl/ke/i386/exp.c:1242
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
The problem seems to be caused by the following file: win32k.sys
Technical information:
*** STOP: 0x0000001E (0xc0000005,0x9e0fe3df,0x00000000,0xcdcdcdcd)
*** win32k.sys - Address 0x9e0fe3df base at 0x9e06d000, DateStamp 0x0
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:9e0fe3df
<win32k.sys:913df (./subsys/win32k/ntuser/msgqueue.c:517 (co_MsqPeekHardwareMessage))>
cr2 cdcdcdcd cr3 3a067000 Proc: 81c9ecc0 Pid: 1ec <mozilla.exe> Thrd: 81ca5b40 Tid: 1f0
DS 23 ES 23 FS 30 GS 0
EAX: cdcdcdcd EBX: 81cc5f88 ECX: 8d4ba45c
EDX: 8d8d6128 EBP: 9fbbebe8 ESI: 0053fc38 ESP: 9fbbea9c
EDI: 9fbbed64 EFLAGS: 00010297 kESP 9fbbea9c kernel stack base 9fbbc000
Frames:
<win32k.sys:92ce1 (./subsys/win32k/ntuser/msgqueue.c:1259 (co_MsqFindMessage))>
<win32k.sys:8870d (./subsys/win32k/ntuser/message.c:731 (co_IntPeekMessage))>
<win32k.sys:88ef8 (./subsys/win32k/ntuser/message.c:871 (NtUserPeekMessage))>
<ntoskrnl.exe:9aa8c (ntoskrnl/ke/i386/syscall.S:372 (KiSystemService))>
<user32.dll:53225 (lib/user32/windows/message.c:1255 (PeekMessageW))>
Entered debugger on embedded INT3 at 0x0008:0x800b0736.
Thanks for testing, i will commit my old code back with some other fixes
later on today.
Brandon
Alex Buell wrote:
> On Wed, 14 Dec 2005, Brandon Turner wrote:
>
>> I removed my changes already in 20163. However before updating can
>> you please try adding "ZeroMemory(RootDriveLetter,5*sizeof(WCHAR));"
>> to line 48 of subsys\smss\initpage.c and tell me if that fixes the
>> problem?
>
>
> Good news, that fix definitely works.
>
I removed my changes already in 20163. However before updating can you
please try adding "ZeroMemory(RootDriveLetter,5*sizeof(WCHAR));" to line
48 of subsys\smss\initpage.c and tell me if that fixes the problem?
Brandon
Alex Buell wrote:
> Won't boot - here's a debugging log if you're interested. Might be of
> use to someone!
>
> /home/alex/VMware/ReactOS > more reactos_debugging
> (./ntoskrnl/ke/main.c:295)
> ---------------------------------------------------------------
> (./ntoskrnl/ke/main.c:296) ReactOS 0.3-SVN (Build 20051214-r20162)
> Used memory 131072Kb
> (./ntoskrnl/mm/mminit.c:386) Kernel Stack Limits. InitTop =
> 0x80100000, Init = 0x800fd000
> (./ntoskrnl/mm/mm.c:283) No current process
> (./ntoskrnl/ldr/loader.c:267) Could not open module file:
> \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001)
> (./ntoskrnl/io/pnpmgr.c:2139) Initialization of service serial failed
> (Status c0000001)
> (./ntoskrnl/ldr/loader.c:267) Could not open module file:
> \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001)
> (./ntoskrnl/io/pnpmgr.c:2139) Initialization of service serial failed
> (Status c0000001)
> (./ntoskrnl/ldr/loader.c:267) Could not open module file:
> \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001)
> (./ntoskrnl/io/pnpmgr.c:2139) Initialization of service serial failed
> (Status c0000001)
> (./ntoskrnl/ldr/loader.c:267) Could not open module file:
> \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001)
> (./ntoskrnl/io/pnpmgr.c:2139) Initialization of service serial failed
> (Status c0000001)
> (./ntoskrnl/ldr/loader.c:267) Could not open module file:
> \SystemRoot\System32\drivers\pcnet.sys (Status 0xc0000001)
> (./ntoskrnl/io/pnpmgr.c:2139) Initialization of service PCNet failed
> (Status c0000001)
> (./ntoskrnl/ldr/loader.c:267) Could not open module file:
> \SystemRoot\system32\drivers\vmx_svga.sys (Status 0xc0000001)
> (./ntoskrnl/io/pnpmgr.c:2139) Initialization of service vmx_svga
> failed (Status c0000001)
> (./ntoskrnl/ldr/loader.c:267) Could not open module file:
> \SystemRoot\System32\drivers\pciide.sys (Status 0xc0000001)
> (./ntoskrnl/io/pnpmgr.c:2139) Initialization of service pciide failed
> (Status c0000001)
> (./ntoskrnl/ldr/loader.c:267) Could not open module file:
> \SystemRoot\System32\drivers\pcnet.sys (Status 0xc0000001)
> (./ntoskrnl/io/pnpmgr.c:2139) Initialization of service PCNet failed
> (Status c0000001)
> (./ntoskrnl/ldr/loader.c:267) Could not open module file:
> \SystemRoot\system32\drivers\vmx_svga.sys (Status 0xc0000001)
> (./ntoskrnl/io/pnpmgr.c:2139) Initialization of service vmx_svga
> failed (Status c0000001)
> (./ntoskrnl/ldr/loader.c:267) Could not open module file:
> \SystemRoot\System32\drivers\pciide.sys (Status 0xc0000001)
> (./ntoskrnl/io/pnpmgr.c:2139) Initialization of service pciide failed
> (Status c0000001)
> (./ntoskrnl/io/pnpreport.c:86) IoReportResourceForDetection partly
> implemented
> (./ntoskrnl/io/pnpmgr.c:545) IoOpenDeviceRegistryKey(): Base key
> doesn't exist, exiting...
> (./ntoskrnl/ldr/loader.c:267) Could not open module file:
> \SystemRoot\System32\drivers\pciide.sys (Status 0xc0000034)
> (./ntoskrnl/io/pnpmgr.c:2139) Initialization of service pciide failed
> (Status c0000034)
> (./ntoskrnl/ldr/loader.c:267) Could not open module file:
> \SystemRoot\system32\drivers\sndblst.sys (Status 0xc0000034)
> (./ntoskrnl/ldr/loader.c:267) Could not open module file:
> \SystemRoot\system32\drivers\mpu401.sys (Status 0xc0000034)
> (./ntoskrnl/io/disk.c:630) RDiskCount 2
> (./subsys/smss/init.c:106) SM: InitSessionManager: failed to create
> paging files (Status=c0000034)
>
>
Hi,
I noticed much of my test applications having problems finding classes.
7-zip,
(lib/rtl/res.c:152) root 77ec8000 dir 77ec8b08 name SYSMENU ret 77ec8b80
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName '7-Zip::Panel')!
(KERNEL32:./lib/kernel32/misc/lang.c:982) CompareString: STUB flags - 0x1001
(KERNEL32:./lib/kernel32/misc/lang.c:982) CompareString: STUB flags - 0x1001
(KERNEL32:./lib/kernel32/misc/lang.c:982) CompareString: STUB flags - 0x1001
On exit,
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invalid usermode buffer
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'SysDateTimePick32')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'SysIPAddress32')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'SysMonthCal32')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'NativeFontCtl')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'SysPager')!
WinAmp 5.11, see http://www.reactos.org/bugzilla/show_bug.cgi?id=1129
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'DSound_IPC')!
AbiWord, on exit,
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'ComboBoxEx32')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'SysDateTimePick32')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'SysIPAddress32')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'SysMonthCal32')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'NativeFontCtl')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'SysPager')!
My Delphi app, see http://www.reactos.org/bugzilla/show_bug.cgi?id=1113
(lib/rtl/res.c:152) root 005cb000 dir 005cb738 name MAINICON ret 005ccad8
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'TApplication')!
(lib/rtl/res.c:152) root 77ec8000 dir 77ec8b08 name SYSMENU ret 77ec8b80
on exit,
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel: invalid usermode buffer
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'ComboBoxEx32')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'SysDateTimePick32')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'SysIPAddress32')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'SysMonthCal32')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'NativeFontCtl')!
(./subsys/win32k/ntuser/class.c:127) Failed to lookup class atom (ClassName 'SysPager')!
Most of my test apps run fine, the rest? Anyone have ideas why Ros cannot find class?
Thanks,
James
Ge van Geldorp wrote:
> Last item is perhaps a bit controversial. I don't like the huge icons in
the
> start menu. It also makes the start menu not fit in 640x480. Can we please
> go back to smaller icons?
If my memory serves me correctly, (I don't have the code in front of me),
this change was intended to support 24x24 icons in the start menu as per
Windows. However as we don't have any 24x24 icons, it defaults to 32x32 (the
huge ones we see now)
I have this reverted in my tree. I was going to revert it in HEAD until we
have 24x24 icons to allow the change to work as it should. However I haven't
been able to get hold of Martin and didn't want to revert without his say
so.
I think reverting in the 0.2.9 branch would be ok though and I'll do it
later if no one objects.
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
When i try to make a bootcd i get:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
G:\ROS>mingw32-make bootcd
[CABMAN] all
ReactOS Cabinet Manager - Version 0.9
File does not exist: output-i386\lib\oleacc\oleacc.dll.
Directive file contains errors at line 140.
mingw32-make: *** [bootcd] Error 1
G:\ROS>
doing a mingw32-make works fine, just once i go to bootcd. I also tried
deleting makefile.auto which didnt change anything. Am i missing something?
Brandon
fireball(a)svn.reactos.com wrote:
> + if (Pdo)
> + IoInvalidateDeviceRelations(Pdo, BusRelations);
> + else
> + DPRINT1("Pdo == NULL, not sending IoInvalidateDeviceRelations()!");
This is going to be a problem if DPRINT1 isn't expanded. You should
create a {...} block for the else branch.
- Thomas
Hi,
It was Steven's idea that I should post this emai and I agreedl, so
please don't take it as my personal childish attempt to get attention,
unless you find that both I and Steven (our Project Coordinator) are
children.
Steven has recently expressed his opinion that: (modified quote so that
"your" -> "my")
"My arrogant attitude hurts this project more then any amount of code or
patches I commit will ever help it."
Therefore, since:
1) I really care about this project
2) I don't wish to spend time writing useless code (since no amount of
code will help the project more then I hurt it, then the code is
useless, like heating a room where the windows are open in winter).
I think it's important to know if this is a public opinion or not, so I
am opening a public ML vote. If it is, then I will gladly leave and stop
hurting this project, since those were not my intentions when I joined.
If this is the case, then I only regret for having stayed here so long
and done nothing but hurt the project for almost two years now, and I'm
sorry.
[ ] Alex's arrogant attitude hurts this project more then his code helps
it. Alex should therefore leave, so that the project can stop being hurt.
[ ] Alex's arrogant attitude is annoying at times but his presence in
this project significantly helps it grow and move towards reaching its
goals, and does not hurt the project.
Best regards,
Alex Ionescu
At the moment, there's one blocker bug registered, 1107: Opening a Command
Prompt (console) window causes the desktop to hang.
A lot of networking apps crash, all due to the same bug. Arty is working on
that one.
On each boot, I have to get rid of 5 device install screens. I'm not
complaining, I understand PnP is a work in progress, but if nobody objects
I'll change the code in the branch to never pop up the device install
screens.
Last item is perhaps a bit controversial. I don't like the huge icons in the
start menu. It also makes the start menu not fit in 640x480. Can we please
go back to smaller icons?
Other than these items (only 1 of them serious as far as I'm concerned) I
like the branch and I believe it will become a good release.
GvG
> From: Alex Buell
>
> I just got the following when trying to ftp to my host
> machine from ReactOS running in VMware. Are there any
> documentation out there that can help me make sense of what's
> happening below? Thanks.
>
> hal/halx86/generic/irql.c:272 CurrentIrql 2 NewIrql 1
> KeBugCheck at hal/halx86/generic/irql.c:273
Yes, this happens with a lot of networking programs at the moment. Art is
working on it.
GvG
2005/12/11, Alex Buell <alex.buell(a)munted.org.uk>:
>
> The patch that I issued for main.cpl DOES work - if you call control.exe
> directly and select either the keyboard and mouse applets you'll notice
> the patch works.
>
> Care to explain why you think the patch I sent in doesn't work?
>
sorry,
that's true.
I know that this is fluff, but I would like to contribute a good, honest
attempt at making a screensaver program for ReactOS. Basically, what I
am looking for is how is the API set up for ReactOS to write programs
for it? I am familiar with writing programs for Windows, and I know the
basic ins and outs of making a screensaver for
Windows (including it's registry settings), however there is some API
specific code that I need in order to give this a shot.
Do you guys have a reference of some kind as to what API functions,
constants, etc. that you have implemented in ReactOS that mirror those
of Windows?
Thanks in advance, and if there isn't enough in ReactOS yet for me to
try this out yet, then I'll try to help on something else that I would
be capable of.
And I must say, and I'm not trying to kiss ass here, but I really
appreciate what you guys are working at here. Keep it up.
Kenneth Armstrong
Hi,
First of all I would like to introduce myself. My name is Martin and I am
currently attempting to go through and audit the ReactOS source code for
security vulnerabilities. I've been keeping an eye on the project for
about a year now and I think as development is now rapidly increasing,
security must take more and more of a priority.
I started with the kernel32 library on Friday (9th) and have found a
number of possible security vulnerabilies. These have been filed with
bugzilla and i'm very impressed with the rate that these were fixed. So
well done on that count!
However, after submitting bugs #1102 and #1103 (now fixed by
BrandonTurner) it became apparent that incorrect usage of the
RtlAllocateHeap function (and its alias HeapAlloc) is quite common. It
may return NULL if memory cannot be allocated and in some parts of the
code this is not checked. This would lead to a segmentation fault on
reading / writing.
Through some judicious use of grep I went through the source code and
extracted calls to this function with their context. After going through
each one and investigating it I have now found another twenty occurances
of the same bug (This is just in the kernel32 library).
I am writing this to let all developers know that they must check their
return values. Errors can exist, resources may be starved and the call
may fail. Make sure your code can cope with this.
Finally, as I am fairly new to bugzilla, should I submit each of these
twenty bugs individually or should I submit them all as one bug?
Cheers,
Martin
Can't we include Mozilla Control in ReactOS? So that we build it with
our ROS Build Environment or whatever is used to compile ReactOS, put it
on bootcd and install it with ReactOS?
Greets,
David Hinz
gvg(a)svn.reactos.com schrieb:
> Files to create Mozilla Control installer with correct DLL
>
>
>
> Added files:
> trunk/tools/
> trunk/tools/MozillaControl/
> trunk/tools/MozillaControl/README.txt
> trunk/tools/MozillaControl/control-ros.nsi
> trunk/tools/MozillaControl/files.nsh
> trunk/tools/MozillaControl/local.nsh
> trunk/tools/MozillaControl/redist/
>
> _______________________________________________
> Ros-svn mailing list
> Ros-svn(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-svn
>
> From: gvg(a)svn.reactos.com
>
> Files to create Mozilla Control installer with correct DLL
I've created a "fixed" version of the Mozilla Control installer which
includes the correct MSVCP60.DLL and put it in our SourceForge download
area. shdocvw.dll will now download/install that fixed version.
GvG
We don't have the REVISIONS section anymore and a copyright notice is missing.
Casper
_____
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of arty(a)svn.reactos.com
Sent: 11. december 2005 09:26
To: ros-diffs(a)reactos.com
Subject: [ros-diffs] [arty] 20055: A little library for making it easier toget to PASSIVE_LEVEL. Just contains
_____
Added: trunk/reactos/drivers/lib/chew/workqueue.c
--- trunk/reactos/drivers/lib/chew/workqueue.c 2005-12-11 08:11:21 UTC (rev 20054)
+++ trunk/reactos/drivers/lib/chew/workqueue.c 2005-12-11 08:26:16 UTC (rev 20055)
@@ -0,0 +1,101 @@
+/*
+ * COPYRIGHT: See COPYING in the top level directory
+ * PROJECT: ReactOS TCP/IP protocol driver
+ * FILE: tcpip/main.c
+ * PURPOSE: Common Highlevel Executive Worker
+ * PROGRAMMERS: Art Yerkes
+ * REVISIONS:
+ * CSH 10/12-2005 Created
+ */
With r20024 I can get ibrowser to actually download the Mozilla webbrowser
control. It usually takes a few tries, often the download hangs halfway
through. I have the feeling that it helps if you move the mouse constantly
during download, but that could just be my imagination.
To install the control, you will need a copy of MSVCP60.DLL, which the
author forgot to include in the install image (Wine has the same problem).
So first copy MSVCP60.DLL from your Windows installation to
\ReactOS\System32, then start ibrowser, download the control and install it.
After that ibrowser (and the "Web" button in ROSExplorer) becomes
functional.
GvG
When I first throw in the idea, that we could try to get some big
companys supporting us, I was amazed by the huge response.
A lot of people seem to be very interested in this, but after some days,
I noticed that there are nearly no devs who replied to my mail, or the
numerous replies on it.
So what I'm asking for is how the devs and especially our PC Steven
Edwards think about asking some companys like IBM, Intel, AMD, nVIDIA,
ATI, Dell,... to support our project.
There are a lot of ways, they could support us, either by money, or by
developers, or by knowledge/documentations.
Every of the mentioned companys would be able to support us, but I think
the only person who has the right to ask any of them is our PC, or maybe
somebody he authorized to do so.
I'm waiting for your replies.
Greets,
David Hinz
BTW, the mail I mentioned above is
http://www.reactos.org/archives/public/ros-dev/2005-December/006645.html
Does this fix the reference to 'reactos.com' with the 'ver' command,
in the Command Interpreter?
On 12/9/05, gvg(a)svn.reactos.com <gvg(a)svn.reactos.com> wrote:
> reactos.org is the preferred name these days
>
>
>
> Updated files:
> trunk/reactos/subsys/system/explorer/shell/mainframe.cpp
>
> _______________________________________________
> Ros-svn mailing list
> Ros-svn(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-svn
>
--
"I had a handle on life, but then it broke"
When I try to compile ReactOS on Windows, I get the following error:
./subsys/win32k/objects/path.c: In function `PATH_PathToRegion':
./subsys/win32k/objects/path.c:1024: warning: 'hrgn' might be used
uninitialized
in this function
mingw32-make[1]: *** [obj-i386\subsys\win32k\objects.o] Error 1
Important: I'm compiling with optimisations for amd64 and dbg and kdbg=0.
Revision is 20025
If I'm not the only one with these problems, I hope you get that fixed
soon, I don't think this is because if my platform optimizations.
Greets,
David Hinz
Hi,
after compiling ros on ros, I see over 45000 memory blocks with the tags
TOKd, TOKp, TOKu and TOKp. It seems, something is wrong with the
referencing/dereferencing of tokens. I've add some debug code in
SeDeassignPrimaryToken (only called by PspDeleteProcess), which prints
the ref count of the token object. It is always greater than 1. The
process token is never deleted.
- Hartmut
The discussion is located here:
http://www.reactos.org/archives/public/ros-dev/2005-October/005671.html
I will create a vote with the options below.
Proposal A from Ged Murphy:
/*
* ReactOS <place holder>
* Copyright (C) 2005 ReactOS Foundation
*
* LICENCE: <place holder>
* PROJECT: <place holder>
* FILE: <place holder>
* PURPOSE: <place holder>
* PROGRAMMERS: <place holder>
* REVISIONS:
* <place holder>
*
*/
Proposal B from Alex Ionescu:
/*
* PROJECT: ReactOS Kernel
* LICENSE: GPL - See COPYING in the top level directory
* FILE: ntoskrnl/ex/mutant.c
* PURPOSE: section of the kernel
* PROGRAMMERS: Alex Ionescu (alex at reactos.org)
* David Welch (welch at cwcom.net)
*/
Proposal C from Casper Hornstrup/Gé van Geldorp:
/*
* PROJECT: ReactOS Kernel
* LICENSE: GPL - See COPYING in the top level directory
* COPYRIGHT: Copyright 2004-2005 John Doe
* Copyright 2005 Jane Doe
*/
XML is actively becoming part of technology and programming. Every
major development company has embraced some form of XML in one
product or another. I was wondering if ReactOS would be interested in
developing some form of application to handle XML-based applications.
These applications would be written in XML and bundled in a ZIP file
much like the ODF formats that OpenOffice 2.0 is using. XML
applications would be allowed to communicate with some processing
application protocols and functions. I think something like this
would be a great feature that would quickly allow novice programmers
to quickly develop applications for ReactOS and share them on the
website. Think of it, no compilation time. That would be great.
I will try to write a proof-of-concept application for Windows XP and
2000 for trial and testing.
My main question is: If something like this is wanted/needed/or if
ReactOS members finds interesting would ReactOS think about
supporting it in the first production release. Which is still far
off, I would imagine.
Ge van Geldorp wrote
> So in our case something like
>
> /*
> * COPYRIGHT: Copyright 2005 Alex Ionescu (alex(a)reactos.org)
> * Copyright 2005 Filip Navara (navaraf(a)reactos.org)
> */
I agree with this.
We don't have to do another vote though, do we.
Can we just agree to this one over the mailing list please?
************************************************************************
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
The changelog has been created. You can add your changes here :
http://www.reactos.org/wiki/index.php/ChangeLog-0.2.9
<http://www.reactos.org/wiki/index.php/ChangeLog-0.2.9>
************************************************************************
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
Please do it anyway since others may care in the future (for instance for security fixes) and replacing directories in Subversion is
troublesome and messes up history (log, blame et al.).
Casper
> -----Original Message-----
> From: ros-svn-bounces(a)reactos.org [mailto:ros-svn-bounces@reactos.org] On Behalf Of
> sedwards(a)svn.reactos.com
> Sent: 8. december 2005 23:21
> To: ros-svn(a)reactos.com
> Subject: [ros-svn] [sedwards] 19980: import libxml2-2.6.20. I did not botherwith a vendor import as
> I don't care much about trackingchanges and more recent versions don't even build on mingw
>
> import libxml2-2.6.20. I did not bother with a vendor import as I don't care much about tracking
> changes and more recent versions don't even build on mingw
Christoph von Wittich wrote
> Office 2003
>
> - - Christoph
>
>
> Thomas Weidenmueller schrieb:
> > sedwards(a)svn.reactos.com wrote:
> >
> >>import libxml2-2.6.20. I did not bother with a vendor
> import as I don't care much about tracking changes and more
> recent versions don't even build on mingw
> >
> >
> > What do we need it for? It takes several minutes to
> download just that
> > directory.
> >
> > - Thomas
Can we not trim it down?
I believe a lot of it consists of test cases which could be removed, or go
in rosapps.
************************************************************************
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
sedwards(a)svn.reactos.com wrote:
> import libxml2-2.6.20. I did not bother with a vendor import as I don't care much about tracking changes and more recent versions don't even build on mingw
What do we need it for? It takes several minutes to download just that
directory.
- Thomas
Dear ReactOS programmers,
We are working on login support in ReactOS like Windows NT 4.0 Login (as
educational project).
Would you contact me/us if you have been worked in the past on
WinLogon,Gina, LSA server, MSV1_0 or SAM?
We did the last 2.5 month a lot of research to this parts of the system.
We have found a lot of information but we need more. Maybe you can give
us more information if you have been worked on that parts in the past.
Contact me at icq: uin# 51588796 or msn: jhuzen(a)hotmail.com
Jasper Huzen
Hi All!
In Revision: 19942: K and DBG == 1,
(KERNEL32:./lib/kernel32/mem/global.c:412) Memory Load: 23%
(KERNEL32:./lib/kernel32/mem/global.c:412) Memory Load: 23%
(KERNEL32:./lib/kernel32/mem/global.c:412) Memory Load: 23%
(KERNEL32:./lib/kernel32/mem/global.c:412) Memory Load: 23%
(MSVCRT:lib/crt/io/open.c:100) not valid fd 0, g_fdend 5, fdinfo 7802f2e0, bucke
t 7802f2e0, fdflags 0
(MSVCRT:lib/crt/io/open.c:702) _setmode: inval fd (0)
(./ntoskrnl/mm/rpoolmgr.h:822) Trying to allocate 8192 bytes from paged pool - n
othing suitable found, returning NULL
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./ntoskrnl/mm/rpoolmgr.h:822) Trying to allocate 20160 bytes from paged pool -
nothing suitable found, returning NULL
Normally it should start at 5 - 7% an end at 16 - 18% even after I start over
again.
Should there be memory tab text in the debug print outs?
Thanks,
James
Hi,
I have a 100% reproducible problem at the end of the Office2000
install on the trunk + local patches. I am hitting a usermode
exception in ReadFile on line 233. The offending code is here
if (NT_SUCCESS(Status))
{
/* lpNumberOfBytesRead must not be NULL here, in fact Win doesn't
check that case either and crashes (only after the operation
completed) */
*lpNumberOfBytesRead = Iosb.Information;
}
Art suggested using ProbeForWrite to handle the problem. Can someone
point me to a example of how to handle this except or even better
would someone be willing to look at implementing the check for me? =)
Thanks
--
Steven Edwards - ReactOS and Wine developer
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
The SkyOS service plugin suite has been extended with a new service: Spell
checking service. This system and application wide usable SkyOS service
brings spell checking to each application. With a small and clean interface
every application can make use of this system wide integrated spell checking
available for various languages. Furthermore, spell checking can be enabled
for most SkyGI widgets like text input fields. The spell checking engine
itself is exchangeable and can be selected by the user. Currently a
proprietary engine and an aspell <http://aspell.sourceforge.net/> engine is
available.
As for all SkyOS services, the spell checking service which runs as a
standalone application can be enabled, disabled or configured via the System
Manager Services Plugin.
Can ReactOS have this?
--
David Johnson
http://www.davefilms.us
Producer
A few weeks (months?) ago i sent a message to the list stating I had
lost my commit password. Shortly after someone sent me that password my
windows installation (along with the drive it was on) went up in smoke
(literally) before i could write it down. I now have the system up and
running, and i was wondering if i could get it one more time. I won't
ask for it again I swear! :P
Richard
Warning: mysql_fetch_array(): supplied argument is not a valid MySQL
result resource in
/web/reactos.org/htdocs/roscms/inc/admin_dyncontent.php on line 304
Got this error when attempting to retrieve Dynamic Content listings
from the CMS.
--
"I had a handle on life, but then it broke"
Hi,
I am working to put together the first quarterly project status
updates. Could everyone that has commit access or works on the web and
translation teams could email me privately about what they are
currently working on as well as what they think they may hack on over
the next few months?
Thanks
--
Steven Edwards - ReactOS and Wine developer
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hi all,
Make clean etc.. ..
8^)
James
darkstar:/home/ros/rosbackup# make
[LD] output-i386/lib/ntdll/ntdll.dll
ntdll.temp.exp:fake:(.edata+0xdd8): undefined reference to `__allshr'
ntdll.temp.exp:fake:(.edata+0xde8): undefined reference to `__aullshr'
ntdll.temp.exp:fake:(.edata+0xdf0): undefined reference to `__fltused'
collect2: ld returned 1 exit status
make: *** [output-i386/lib/ntdll/ntdll.dll] Error 1
For some reason, when I was running 19899 yesterday, the dialog boxes
kept showing on every boot
On 12/5/05, weiden(a)svn.reactos.com <weiden(a)svn.reactos.com> wrote:
> disable the device if the user selects "Do not show this dialog anymore". However, this doesn't work at the moment because disabling devices isn't implemented. Once it works, umpnpmgr shouldn't display the device installation wizard for disabled devices anymore.
>
>
> Updated files:
> trunk/reactos/lib/newdev/newdev.c
> trunk/reactos/lib/newdev/newdev.h
>
> _______________________________________________
> Ros-svn mailing list
> Ros-svn(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-svn
>
--
"I had a handle on life, but then it broke"
I guess that would be good, a backer like IBM, but you need to look for
companies that would benefit from open source, or else, 9 times out of 10,
your gonna get a big, fat 'NO'.
ps: you all changed subject *pritty fast*!
Who says, they've got to opensource their drivers?
I think it could be a big help, if they would help us with implementing
the apis their drivers are úsing, so that their closed-source drivers
work fine.
Greets,
David Hinz
Alex Buell schrieb:
> On Mon, 5 Dec 2005, Jonathan Andrews wrote:
>
>>> What I'd really like to see are Hardware Manufacturers getting behind
>>> us. Realtek, nVIDIA, ATi, Intel, AMD, VIA, etc, could all be
>>> approached, and ask for collaboration on writing GPL Drivers
>>> (Although nVIDIA is notoriously skeptical about open-source)
>>
>> Im sorry, snot came out of my nose laughing when I read this...... If
>> you think ANY Manufacturer is going to back an open source windows
>> clone when they wont even touch a FreeBSD, let alone a Liux then you
>> are not living in the real world.
>>
>> If you want pure GPL then it is best NOT to contact these people and
>> ask, if by some miracle they sent you any data you would probably find
>> that you are in breech of NDA if you use it.
>>
>> Out of your list only VIA will give out data on request, and thats
>> only data for devices that don't do multimedia.
>
> One word: DRM. That's why the likes of NVidia won't give out information
> on how their devicess works.
>
Murphy, Ged (Bolton) wrote:
> > -----Original Message-----
> > From: WaxDragon [mailto:waxdragon@gmail.com]
> > Sent: 02 December 2005 01:02
> > To: ReactOS Development List
> > Subject: Re: [ros-dev] Freeze the trunk and release
> >
> >
> > In my 19792, I have a working dhcp client, and can access the cdrom
> > drive, under vmware.. I haven't had a chance to try Firefox.
> >
> > I'm for a freeze, but against a release at this time.
> >
>
> I think a freeze would lead directly onto a release as all
> the critical bugs
> should be fixed in the freeze period.
>
What's happening with this?
IIRC, either WD calls for a trunk freeze, or Brandon branches for a release.
Neither have happened yet ??
I think we should progress in some way or we'll never see 0.3.0
************************************************************************
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
When I just looked for something to translate, I updated the translation
of syssetup (trunk\reactos\lib\syssetup). While I read through the file,
I recognized, that I newer saw this before. When I checked the setup, I
found out, that until all steps of the setup are done, everything is in
english. Can't we extend the first part of the setup, so that you select
your language at the beginning of setup (the way nearly every
Linux-distributor is doing it...) so that people who don't understand
english very good are able to install ReactOS? Wouldn't this be nice for
0.3.0?
Greets,
David Hinz
David Hinz wrote:
> At the moment, it looks like the next release will be 0.2.9.
It definitely is going to be 0.2.9. We are no where near ready for 0.3.0
yet.
> I this is the case, I personally think we should branch now
> or maybe in a week.
Why in a week? We've discussed this a few times and the 1st December was
thrown about as a provisional date. I assumed that the release coordinator
was going to branch then, or the TC was going to call for a trunk freeze.
> But for 0.3.0 I think we should "clean up" the trunk i.e. WaxDragon
> should call for a feature freeze and we should fix all bugs and work
> very hard on the translations,
On the contrary, it's not a feature freeze we need for 0.3.0. There is
missing functionality to co-inside with the roadmap. The feature freeze will
come when trunk is ready to branch for 0.3.0, or beforehand is the TC deems
the trunk to be 'a mess' ;)
> as 0.3.0 is one of our major releases and
> will be reviewed by a lot of magazines (if we tell them about this
> release...), so it should be one of our best releases.
I agree, I've already got a few magazines and other features in the pipeline
;)
This is another reason I'm hungry to get 0.3.0 out of the door.
> Greets,
>
> David Hinz
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
gvg(a)svn.reactos.com wrote:
>- if (GetUpdateRect(hWnd,
>- &rcUpdate,
>- FALSE))
>
>
The previous code was perfectly valid. Why did you change it? If
GetUpdateRect returns FALSE then there's no need to call BeginPaint...
- Filip
Great news !!
I have a ream of paper itching to be printed on.
-----Original Message-----
From: Alex Ionescu [mailto:ionucu@videotron.ca]
Sent: 05 December 2005 04:38
To: ReactOS Development List
Subject: [ros-dev] ATT: Ged/Network Dudes
Hi Ged (and others interested),
As I promised to you, I'd like to announce that my user-mode networking
code is now complete and will undergo testing for the next 2-3 weeks
(just like ws2_32 did) in order to find bugs. I will also do as for
ws2_32 and commit it into the branch with the full svn logs of my local
svn server.
Best regards,
Alex Ionescu
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
************************************************************************
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
Hello to the group.... my first post....
I noticed some talk about the Reactos installer following the windows
form. As a long time NT admin who moved into product development on
Linux I would just like to point out how mediocre the windows installer
is.
With a bootable linux ISO you get a full network stack, functional USB
support, detected UDMA IDE drivers, Vesfa FB X11 etc etc etc... with the
windows installer you get a kernel, a few utils and a pretty inflexable
installer.
Would it not make more sense to write an installer thats based on a
bootable Linux image - if nothing else the use of networking offers a
host of possibilities (diskless installs, updates from the internet
during the install phase and so on).
Is the aim to clone windows, or to produce an operating system that is
API compatible with win32 ? They are very different aims with very
different requirements!
Jon
Hi Ged (and others interested),
As I promised to you, I'd like to announce that my user-mode networking
code is now complete and will undergo testing for the next 2-3 weeks
(just like ws2_32 did) in order to find bugs. I will also do as for
ws2_32 and commit it into the branch with the full svn logs of my local
svn server.
Best regards,
Alex Ionescu
Does anybody object to consolidating all but one of the partial NTSTATUS_*
copies to:
#ifndef WIN32_NO_STATUS
#include <ddk/ntstatus.h>
#endif
And keeping the copy in ddk/ntstatus.h ?
--
Here's a simple experiment. Stand on a train track between two locomotives
which are pushing on you with equal force in opposite directions. You will
exhibit no net motion. None the less, you may soon begin to notice that
something important is happening.
-- Robert Stirniman
I was just wondering, if we could implement symbolic links in ReactOS.
As I don't want to add this feature to every filesystem that doesn't
support symbolic links, I thought about another way.
I had two ideas:
1. Use a file for this, comparable to files like HOSTS etc
2. Use the registry
The more I thought about this, I liked my second idea more than my first
and noticed what a great thing the registry is.
We could simply add keys like HKEY_LOCAL_MACHINE\SYSTEM\symlinks\C:\My
Files and set the target directory as it's value.
It's very easy to search for such keys, so it shouldn't be that hard to
implement it into the IFS-driver.
More complicated would be the implementation into explorer and the
creation of a commandline utility.
A second feature could be to create such links for every user, so that
every user could use C:\My Files\... which would be linked to
C:\Documents and Settings\Username\My Files\... and he wouldn't even notice.
I think that would be a nice feature and I would really like to
implement this, but I'm afraid I can't do this alone, as I don't have
much experience and I'm just beginning to learn C++ and asm, so it would
be nice, if someone of you who likes this idea could help me with this.
Greets,
David Hinz
ion(a)svn.reactos.com wrote:
>- Fix KeAttackProcess, KeStackAttachProcess, KeUnstackDetachProcess and KeDetachProcess. The code was brain-dead and I must've been drunk when I first wrote it.
>- Update some NDK definitions and some fixes.
>- Update HAL Private Dispatch Table to 2.0
>- Make RtlIpv* API definitions more correct.
>
>
>
>
With this patch it is now possible to use process explorer:
http://www.relsoft.net/yay.png
There are some nice GUI bugs... the options menu is "expanded" and
becomes part of the main menu bar... Also double-clicking to open the
process properties makes the dialog hidden in the top-left corner..all I
can see is the resizing slider.
Best regards,
Alex Ionescu
Didn't notice you were only referring to explorer.
Ignore my mail below unless you want to build the whole thing
-----Original Message-----
From: Murphy, Ged (Bolton) [mailto:MurphyG@cmpbatteries.co.uk]
Sent: 03 December 2005 12:26
To: 'ReactOS Development List'
Subject: RE: [ros-dev] vc-2005 don't compile reactos-explorer (19750_
The msvc backend is not yet complete, this we don't fully support msvc at
this stage.
If you want to build, you will need to use mingw / gcc.
However you can build some sub projects within the ReacOS solution.
Run 'make msvc8' (you will need to have built rbuild) to populate the tree
with the relevant vcproj files and try a few things like arp.
Ged.
-----Original Message-----
From: hys545(a)dreamwiz.com [mailto:hys545@dreamwiz.com]
Sent: 03 December 2005 12:12
To: ros-dev(a)reactos.org
Subject: [ros-dev] vc-2005 don't compile reactos-explorer (19750_
Compiling...
precomp.cpp
c:\work\explorer\utility/shellclasses.h(556) : error C2504:
'IShellFolderPtr' : base class undefined
c:\work\explorer\utility/shellclasses.h(557) : error C2146: syntax error :
missing ';' before identifier 'super'
c:\work\explorer\utility/shellclasses.h(557) : error C4430: missing type
specifier - int assumed. Note: C++ does not support default-int
c:\work\explorer\utility/shellclasses.h(557) : error C4430: missing type
specifier - int assumed. Note: C++ does not support default-int
c:\work\explorer\utility/shellclasses.h(567) : error C2738: 'operator bool'
: is ambiguous or is not a member of 'ShellFolder'
c:\work\explorer\utility/shellclasses.h(555) : see declaration of
'ShellFolder'
c:\work\explorer\utility/shellclasses.h(578) : error C2504: 'IShellLinkWPtr'
: base class undefined
c:\work\explorer\utility/shellclasses.h(579) : error C2146: syntax error :
missing ';' before identifier 'super'
c:\work\explorer\utility/shellclasses.h(579) : error C4430: missing type
specifier - int assumed. Note: C++ does not support default-int
c:\work\explorer\utility/shellclasses.h(579) : error C4430: missing type
specifier - int assumed. Note: C++ does not support default-int
c:\work\explorer\utility/shellclasses.h(583) : error C2614: 'ShellLinkPtr' :
illegal member initialization: 'super' is not a base or member
c:\work\explorer\utility/shellclasses.h(674) : error C2819: type
'ShellFolder' does not have an overloaded member 'operator ->'
************************************************************************
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
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
************************************************************************
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
The msvc backend is not yet complete, this we don't fully support msvc at
this stage.
If you want to build, you will need to use mingw / gcc.
However you can build some sub projects within the ReacOS solution.
Run 'make msvc8' (you will need to have built rbuild) to populate the tree
with the relevant vcproj files and try a few things like arp.
Ged.
-----Original Message-----
From: hys545(a)dreamwiz.com [mailto:hys545@dreamwiz.com]
Sent: 03 December 2005 12:12
To: ros-dev(a)reactos.org
Subject: [ros-dev] vc-2005 don't compile reactos-explorer (19750_
Compiling...
precomp.cpp
c:\work\explorer\utility/shellclasses.h(556) : error C2504:
'IShellFolderPtr' : base class undefined
c:\work\explorer\utility/shellclasses.h(557) : error C2146: syntax error :
missing ';' before identifier 'super'
c:\work\explorer\utility/shellclasses.h(557) : error C4430: missing type
specifier - int assumed. Note: C++ does not support default-int
c:\work\explorer\utility/shellclasses.h(557) : error C4430: missing type
specifier - int assumed. Note: C++ does not support default-int
c:\work\explorer\utility/shellclasses.h(567) : error C2738: 'operator bool'
: is ambiguous or is not a member of 'ShellFolder'
c:\work\explorer\utility/shellclasses.h(555) : see declaration of
'ShellFolder'
c:\work\explorer\utility/shellclasses.h(578) : error C2504: 'IShellLinkWPtr'
: base class undefined
c:\work\explorer\utility/shellclasses.h(579) : error C2146: syntax error :
missing ';' before identifier 'super'
c:\work\explorer\utility/shellclasses.h(579) : error C4430: missing type
specifier - int assumed. Note: C++ does not support default-int
c:\work\explorer\utility/shellclasses.h(579) : error C4430: missing type
specifier - int assumed. Note: C++ does not support default-int
c:\work\explorer\utility/shellclasses.h(583) : error C2614: 'ShellLinkPtr' :
illegal member initialization: 'super' is not a base or member
c:\work\explorer\utility/shellclasses.h(674) : error C2819: type
'ShellFolder' does not have an overloaded member 'operator ->'
************************************************************************
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
Hi,
I have been able to get Office 2000 to mostly install with this msi.dll
http://steven-edwards.kicks-ass.org/~sedwards/msi.dll
It is a port of the msi from CrossOver 5.0 release with a few tweaks.
The issue I am having now is that Office applications fail to load due
to usermode exceptions on oso9.dll or whatever the core Office dll is.
If anyone is interested could they take a look at this?
You need install using
msiexec /i package.msi
where package.msi is the main Office2000 msi on the CD. There is still
some issue where the setup.exe program thinks it needs to upgrade our
msi.
Thanks
Steven
--
Steven Edwards - ReactOS and Wine developer
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
greatlrd(a)svn.reactos.com wrote:
> Corretat en översätting miss upptäckes av harteex program files till program
Can we please keep the commit messages in English? ;-)
- Thomas
Hi,
Using svn rev 19823 I cannot compile anything with msvc2k5. All source
files give the errors like the following
Compiling...
cl : Command line warning D9040 : ignoring option '/analyze'; Code
Analysis warnings are not available in this edition of the compiler
appwiz.c
c:\source\clean\reactos\lib\cpl\appwiz\appwiz.c(67) : warning C4244:
'=' : conversion from 'LRESULT' to 'int', possible loss of data
c:\source\clean\reactos\lib\cpl\appwiz\appwiz.c(152) : warning C4244:
'=' : conversion from 'LRESULT' to 'ULONG', possible loss of data
c:\source\clean\reactos\lib\cpl\appwiz\appwiz.c(110) : warning C4100:
'lParam' : unreferenced formal parameter
c:\source\clean\reactos\lib\cpl\appwiz\appwiz.c(187) : warning C4100:
'lParam' : unreferenced formal parameter
c:\source\clean\reactos\lib\cpl\appwiz\appwiz.c(187) : warning C4100:
'wParam' : unreferenced formal parameter
c:\source\clean\reactos\lib\cpl\appwiz\appwiz.c(187) : warning C4100:
'hwndDlg' : unreferenced formal parameter
c:\source\clean\reactos\lib\cpl\appwiz\appwiz.c(243) : warning C4100:
'hwndCPl' : unreferenced formal parameter
c:\source\clean\reactos\lib\cpl\appwiz\appwiz.c(275) : warning C4100:
'lpvReserved' : unreferenced formal parameter
c:\source\clean\reactos\lib\cpl\appwiz\appwiz.c(286) : error C2857:
'#include' statement specified with the /Ycstdafx.h command-line
option was not found in the source file
Build log was saved at
"file://c:\source\clean\reactos\lib\cpl\appwiz\Debug\BuildLog.htm"
appwiz - 1 error(s), 9 warning(s)
--
Steven Edwards - ReactOS and Wine developer
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
> -----Original Message-----
> From: Murphy, Ged (Bolton) [mailto:MurphyG@cmpbatteries.co.uk]
> Sent: 02 December 2005 08:16
> To: 'ReactOS Development List'
> Subject: RE: [ros-dev] msvc backend issue
>
>
>
> > -----Original Message-----
> > From: Steven Edwards [mailto:winehacker@gmail.com]
> > Sent: 02 December 2005 07:51
> > To: ReactOS Development List
> > Subject: [ros-dev] msvc backend issue
> >
> > '#include' statement specified with the /Ycstdafx.h command-line
> > option was not found in the source file
>
>
> I get this same error.
> Try reverting 19789. It was working fine up until this point
> as I did some
> testing with it.
>
Nevermind, I see Christoph fixed it as I was typing that ... heh.
************************************************************************
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
> -----Original Message-----
> From: WaxDragon [mailto:waxdragon@gmail.com]
> Sent: 02 December 2005 01:02
> To: ReactOS Development List
> Subject: Re: [ros-dev] Freeze the trunk and release
>
>
> In my 19792, I have a working dhcp client, and can access the cdrom
> drive, under vmware.. I haven't had a chance to try Firefox.
>
> I'm for a freeze, but against a release at this time.
>
I think a freeze would lead directly onto a release as all the critical bugs
should be fixed in the freeze period.
************************************************************************
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
> -----Original Message-----
> From: Steven Edwards [mailto:winehacker@gmail.com]
> Sent: 02 December 2005 07:51
> To: ReactOS Development List
> Subject: [ros-dev] msvc backend issue
>
> '#include' statement specified with the /Ycstdafx.h command-line
> option was not found in the source file
I get this same error.
Try reverting 19789. It was working fine up until this point as I did some
testing with it.
************************************************************************
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
Hi,
If our testing cordinator would agree to it I think it would be nice
to freeze the trunk for a week and then branch for another release.
Its been 2+ months and I am seeing the following bugs
dhcp client - broken
firefox - kernel crashes
cdrom - device not being found
I think its time we get her qusi-stable again.
--
Steven Edwards - ReactOS and Wine developer
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
gvg(a)svn.reactos.com wrote:
>Factor out probe and capture code from private ntoskrnl header and put it in
>a more public place so other kernelmode components can use it too
>
>
>
>Added files:
>trunk/reactos/include/reactos/probe.h
>
>Updated files:
>trunk/reactos/ntoskrnl/include/internal/ntoskrnl.h
>trunk/reactos/ntoskrnl/include/ntoskrnl.h
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.org
>http://www.reactos.org/mailman/listinfo/ros-svn
>
>
>
This is incorrect; other kernel-mode components should NOT use these
macros. They should do it the "long way" and go through ProbeForRead.
Best regards,
Alex Ionescu
> From: ion(a)svn.reactos.com
>
> +
> +@RtlPrefetchMemoryNonTemporal@8:
> + ret /* Overwritten by ntoskrnl/ke/i386/kernel.c if SSE is
supported (see Ki386SetProcessorFeatures() ) */
Is this routine so time-critical that we want to resort to self-modifying
code?
GvG
While working on proper logoff/shutdown processing, I'm running into an
interesting race condition inside kernel32. The shutdown command
(apps/utils/shutdown) calls ExitWindowsEx() and then terminates, which
causes kernel32's DllMain() function to be called with the
DLL_PROCESS_DETACH reason. This will clean up kernel32 resources, like
calling RtlDeleteCriticalSection(&ConsoleLock).
Now, before the process is completely shutdown, CSRSS will send it a
CTRL_LOGOFF_EVENT. To deliver this event, CSRSS calls CreateRemoteThread().
So CreateRemoteThread() is called while the main thread is executing
DLL_PROCESS_DETACH cleanup. During handling of CTRL_LOGOFF_EVENT, the new
thread will try to enter the ConsoleLock critical section, which was already
deleted by the main thread. Chaos results.
To solve this, first I was looking for a way to disable new thread creation
when a process enters ExitProcess(), but that won't solve the problem. We
can still have a thread A which calls ExitProcess(), have a context switch
to existing thread B of the same process which does something that needs the
ConsoleLock. Then I considered SuspendThread()ing all other threads of the
process when ExitProcess() is called, but that could potentially lead to
deadlocks if the suspended threads hold synchronization objects. So now I'm
inclined to believe that the solution is to just not do the resource cleanup
during DLL_PROCESS_DETACH handling. But that doesn't feel very clean either.
Anyone have a better idea?
GvG
We do not support some binutils for diffent reason
and I do not think this patch is good, for it active least one version of
binutils that always break reactos, it does not the linking right or was it
some other issue. And I do not want see this patch in reactos for that
reason. see older mails why we support 2.15.94 or higher.
----- Original Message -----
From: "Alex Buell" <alex.buell(a)munted.org.uk>
To: "ReactOS Development" <Ros-dev(a)reactos.org>
Sent: den 29 November 2005 17:52
Subject: [ros-dev] Patch for lib/rtl/i386/math_asm.S
> The following might be better for those of us using older binutils
>
> --- lib/rtl/i386/math_asm.S.orig 2005-11-29 15:47:23.000000000
> +0000
> +++ lib/rtl/i386/math_asm.S 2005-11-29 15:47:09.000000000 +0000
> @@ -731,7 +731,7 @@
> mov al,ah // Move condition flags to AL
> lahf // Load Flags into AH
> and al, 0b01000101 // Isolate C0, C2 and C3
> - and ah,not 0b01000101 // Turn off CF, PF and ZF
> + and ah, 0b10111010 // Turn off CF, PF and ZF
> or ah,al // Set new CF, PF and ZF
> sahf // Store AH into Flags
> jb __fpow1 // Re-direct if x < 0
> @@ -743,7 +743,7 @@
> mov al,ah // Move condition flags to AL
> lahf // Load Flags into AH
> and al, 0b01000101 // Isolate C0, C2 and C3
> - and ah,not 0b01000101 // Turn off CF, PF and ZF
> + and ah, 0b10111010 // Turn off CF, PF and ZF
> or ah,al // Set new CF, PF and ZF
> sahf // Store AH into Flags
> ja __fpow3 // Re-direct if y > 0
> @@ -759,7 +759,7 @@
> mov al,ah // Move condition flags to AL
> lahf // Load Flags into AH
> and al, 0b01000101 // Isolate C0, C2 and C3
> - and ah,not 0b01000101 // Turn off CF, PF and ZF
> + and ah, 0b10111010 // Turn off CF, PF and ZF
> or ah,al // Set new CF, PF and ZF
> sahf // Store AH into Flags
> je __fpow2 // Proceed if y = int(y)
>
> Cheers,
> Alex
> --
> http://www.munted.org.uk
>
> Anyone that thinks an imaginary deity is going to protect them against
> earthquakes and hurricanes needs psychiatric help.
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.362 / Virus Database: 267.13.9/185 - Release Date: 2005-11-28
>
>
We're at the 2 month period since our last release. Is it not time to branch
now and chase some more publicity
If Alex meets his 1st December deadline for User-Mode networking, I propose
a 0.2.9 branch then.
Any thoughts?
************************************************************************
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
The voting is closed and ReactOS now has a new project coordinator.
Steven Edwards has been appointed as Jason Filby's successor.
Congratulations, and good luck ;)
Speech ! ! !
************************************************************************
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
This change breaks copy in cmd, unless you are in the root of a drive.
>[ros-svn] [hbirr] 19535: - Allow trailing back slashes only for directories.
>hbirr at svn.reactos.com hbirr at svn.reactos.com
>Thu Nov 24 22:08:17 CET 2005
>
> * Previous message: [ros-svn] [gvg] 19534: Fix optimized builds
> * Next message: [ros-svn] [jimtabor] 19536: Fix missed files. Svn problem?
> * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>
>- Allow trailing back slashes only for directories.
>- Allow trailing back slashes, if a new directory will be created.
>
>
>
>Updated files:
>trunk/reactos/drivers/fs/vfat/create.c
>trunk/reactos/drivers/fs/vfat/vfat.h
WD
--
<mikedep333> but if it isnt working, why is it even included on the CD?
I was looking at reactos control panels and was wondering if there
was any MS HTA or something like it embedded. I was thinking that
XUL, Firefox, and Mozilla could be integrated into the Explorer and
other things to dynamically update the interface of Reactos.
Something like Apple's Safari RSS Reader, and Explorer's (XP)
Sidebars with common tasks and utilities.
On Wednesday 30 November 2005 18:19, Alex Buell wrote:
> Looks like I'll be filing a bug report with Gentoo to get them to bump
> their xmingw binutils to 2.15.94 - it's 2.15.90.0.2 at the moment.
> Thanks.
* dev-util/xmingw-binutils
Latest version available: 2.15.94.20050118.1
Latest version installed: 2.15.94.20050118.1
Just unmask it....
Hey Hey,
Just wanted to give a heads up to the community about the following
error on my iBook g4. There was USB enabled when i installed then I
removed it. I was wondering if there is being a rewrite of this or
something. Plus I can't submit a bugzilla report because of site
restrictions.
A problem has been detected and ReactOS has been shut down to prevent
damage to
your computer.
The problem seems to be caused by the following file: win32k.sys
KMODE_EXCEPTION_NOT_HANDLED
Technical information:
*** STOP: 0x0000001E (0xc0000005,0x9d929c33,0x00000000,0x00000004)
*** win32k.sys - Address 0x9d929c33 base at 0x9d872000, DateStamp 0x0
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:9d929c33 <win32k.sys:b7c33 (./subsys/win32k/
objects/dc.c:5
76 (IntPrepareDriver))>
cr2 4 cr3 e5ce000 Proc: 80dc9670 Pid: ec <umpnpmgr.exe> Thrd:
80e160a0 Tid: f8
DS 23 ES 23 FS 30 GS 0
EAX: 00000000 EBX: 9d92ad56 ECX: 00000000
EDX: 00000000 EBP: 9e29eb5c ESI: 00cef564 ESP: 9e29ea70
EDI: 9e29ed64 EFLAGS: 00000202 kESP 9e29ea70 kernel stack base
9e29c000
Frames:
<win32k.sys:b7e71 (./subsys/win32k/objects/dc.c:661
(IntPrepareDriverIfNeeded))>
<win32k.sys:b85ba (./subsys/win32k/objects/dc.c:838 (IntGdiCreateDC))>
<win32k.sys:b900b (./subsys/win32k/objects/dc.c:1051 (NtGdiCreateIC))>
<ntoskrnl.exe:9a4ea (ntoskrnl\ke\i386\syscall.S:372 (KiSystemService))>
<gdi32.dll:8761 (lib/gdi32/objects/dc.c:128 (CreateICW))>
I get the following error, when I try to compile revision 19777:
[CC] lib\devmgr\advprop.c
lib\devmgr\advprop.c: In function `DisplayDeviceAdvancedProperties':
lib\devmgr\advprop.c:247: error: `DIGCDP_FLAG_REMOTE_ADVANCED'
undeclared (first use in this function)
lib\devmgr\advprop.c:247: error: (Each undeclared identifier is reported
only once
lib\devmgr\advprop.c:247: error: for each function it appears in.)
mingw32-make: *** [obj-i386\lib\devmgr\advprop.o] Error 1
If I remember right, the last working revision was 19776, but I don't
know exactly.
Anyway, the files changed since my last successfull compilation are:
U lib\devmgr\devmgr.xml
U lib\devmgr\En.rc
U lib\devmgr\precomp.h
U lib\devmgr\advprop.c
U lib\devmgr\hwpage.c
U lib\devmgr\misc.c
U lib\devmgr\resource.h
Hope you get that fixed soon.
Greets,
David Hinz
LOL !!!
Check your mail headers and you'll see the unsubscribe address.
Or you can be lazy and click on the following link ;)
mailto:ros-dev-request@reactos.org?subject=unsubscribe
-----Original Message-----
From: frank.marx(a)t-online.de [mailto:frank.marx@t-online.de]
Sent: 30 November 2005 11:51
To: ReactOS Development List
Subject: Re: [ros-dev] [Fwd: [ros-svn] CC: Eric/IDL Guys - MIDL
Compatibility]
Importance: Low
Please DONT send me further emails !
Thank you !
Frank Marx
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
************************************************************************
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
Hello Alex
No, it wasnt commited yet. The best way to submit patches is through
bugzilla under the patch group. http://www.reactos.org/bugzilla/
Brandon
Alex Buell wrote:
> obj-i386/lib/rtl/rtl.a(math_asm.o)(.text+0x50e):lib/rtl/i386/math_asm.S:1439:
> undefined reference to `not'
> obj-i386/lib/rtl/rtl.a(math_asm.o)(.text+0x529):lib/rtl/i386/math_asm.S:1451:
> undefined reference to `not'
> obj-i386/lib/rtl/rtl.a(math_asm.o)(.text+0x54f):lib/rtl/i386/math_asm.S:1467:
> undefined reference to `not'
> collect2: ld returned 1 exit status
> make[1]: *** [output-i386/lib/ntdll/ntdll.dll] Error 1
>
> Why hasn't my patch gone in yet? If not, why not?
>
I have recently been reviewing the DosEmu thread on the list. Here is
my concern, why not try doing something like XEN for reactos. CMD.exe
could interact with all of the XENed hardware and software. One major
feature this would be great for is if someone needed to utilize a
EXT3 disk image or hard drive from ReactOS in the future all they
would have to do is pop open the cmd prompt and cd to a virtual hard
drisk something like C:\Volumes\HDA1\ would be equal to / on the
linux volume. A system service would also need to be implemented for
starting the other os on command, but that is only a suggestion...
Rick
cwittich(a)svn.reactos.com wrote:
>added more correct linker flags (patch by brezenbak)
>
>Modified: trunk/reactos/tools/rbuild/backend/msvc/vcprojmaker.cpp
>
>
> ------------------------------------------------------------------------
> *Modified: trunk/reactos/tools/rbuild/backend/msvc/vcprojmaker.cpp*
>
>--- trunk/reactos/tools/rbuild/backend/msvc/vcprojmaker.cpp 2005-11-30 00:25:48 UTC (rev 19764)
>+++ trunk/reactos/tools/rbuild/backend/msvc/vcprojmaker.cpp 2005-11-30 00:26:51 UTC (rev 19765)
>@@ -330,8 +330,17 @@
>
> }
> else if ( exe )
> {
>
>
>- fprintf ( OUT, "\t\t\t\tSubSystem=\"%d\"\r\n", console ? 1 : 2 );
>- fprintf ( OUT, "\t\t\t\tBaseAddress=\"%s\"\r\n", module.baseaddress.c_str ());
>
>
>+ if ( module.type == Kernel || module.type == NativeCUI)
>+ {
>+ fprintf ( OUT, "\t\t\t\tAdditionalOptions=\" /SUBSYSTEM:NATIVE /SECTION:INIT,D /ALIGN:4096 /FORCE:MULTIPLE\"\r\n" );
>+ fprintf ( OUT, "\t\t\t\tIgnoreAllDefaultLibraries=\"TRUE\"\r\n" );
>+ fprintf ( OUT, "\t\t\t\tEntryPointSymbol=\"%s\"\r\n", module.entrypoint.c_str ());
>+ fprintf ( OUT, "\t\t\t\tBaseAddress=\"%s\"\r\n", module.baseaddress.c_str ());
>+ }
>+ else if ( module.type == Win32CUI || module.type == Win32GUI )
>+ {
>+ fprintf ( OUT, "\t\t\t\tSubSystem=\"%d\"\r\n", console ? 1 : 2 );
>+ }
>
>
> }
> else if ( dll)
> {
>
>
This still isn't fully correct.
First, the check should be widened to inculde Drivers.
Secondly, /SECTION:INIT,D should only be used for Kernel or Drivers, not
Native apps. Thirdly, /ALIGN:4096 is irrelevant -- this is the default.
Kernel should get 0x80, and drivers should get 0x20.
Fourthly, Kernel entrypoint should be hard-coded to KiSystemStartup,
while Native apps shoudl be hardcoded to NtProcessStartup. This is
especially important so that nt.lib will get used properly.
Also, NativeCUI is a bit repetitive. Native can only be CUI.
Drivers should also be compiled with /DRIVER.
Native, Kernel and Drivers should have /NODEFAULTLIB.
/FORCE:MULTIPLE is ugly and I don't know why it was added.
Best regards,
Alex Ionescu