Ros-dev January 2010

ros-dev@reactos.org

41 participants
64 discussions

by Max

if it is not sold, I suggest to build it into reactos http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=200427881447#ht_500wt_10… then users can install any kind of app. thoughts?

14 years, 11 months

Re: [ros-dev] [ros-diffs] [sir_richard] 45148: [NTOS]: Implement GUI thread promotion during the first GUI system call in C. This is tricky due to EBP, and actually requires some tiny inline ASM magic to make it work right. [NTOS]: Implement SYSENTER system calls

by Gabriel ilardi

Hi Sir Richard, Just for the record, trunk's broken in 1st stage: http://build.reactos.org:8010/builders/x86_%28Test%29/builds/1208/steps/tes… Regards, Gabriel. > Date: Tue, 19 Jan 2010 09:45:30 +0000 > To: ros-diffs(a)reactos.org > From: sir_richard(a)svn.reactos.org > Subject: [ros-diffs] [sir_richard] 45148: [NTOS]: Implement GUI thread promotion during the first GUI system call in C. This is tricky due to EBP, and actually requires some tiny inline ASM magic to make it work right. [NTOS]: Implement SYSENTER system calls in C as well. All system calls are now handled in C. This code will be further optimized/refined soon. > > Author: sir_richard > Date: Tue Jan 19 10:45:30 2010 > New Revision: 45148 > > URL: http://svn.reactos.org/svn/reactos?rev=45148&view=rev > Log: > [NTOS]: Implement GUI thread promotion during the first GUI system call in C. This is tricky due to EBP, and actually requires some tiny inline ASM magic to make it work right. > [NTOS]: Implement SYSENTER system calls in C as well. > > All system calls are now handled in C. This code will be further optimized/refined soon. > > Modified: > trunk/reactos/ntoskrnl/include/internal/ke.h > trunk/reactos/ntoskrnl/include/internal/trap_x.h > trunk/reactos/ntoskrnl/ke/i386/trap.s > trunk/reactos/ntoskrnl/ke/i386/traphdlr.c > > Modified: trunk/reactos/ntoskrnl/include/internal/ke.h > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/include/internal/… > ============================================================================== > --- trunk/reactos/ntoskrnl/include/internal/ke.h [iso-8859-1] (original) > +++ trunk/reactos/ntoskrnl/include/internal/ke.h [iso-8859-1] Tue Jan 19 10:45:30 2010 > @@ -138,6 +138,7 @@ > extern ULONG_PTR KiBugCheckData[5]; > extern ULONG KiFreezeFlag; > extern ULONG KiDPCTimeout; > +extern PGDI_BATCHFLUSH_ROUTINE KeGdiFlushUserBatch; > > /* MACROS *************************************************************************/ > > > Modified: trunk/reactos/ntoskrnl/include/internal/trap_x.h > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/include/internal/… > ============================================================================== > --- trunk/reactos/ntoskrnl/include/internal/trap_x.h [iso-8859-1] (original) > +++ trunk/reactos/ntoskrnl/include/internal/trap_x.h [iso-8859-1] Tue Jan 19 10:45:30 2010 > @@ -436,3 +436,42 @@ > > return Result; > } > + > +NTSTATUS > +FORCEINLINE > +KiConvertToGuiThread(VOID) > +{ > + NTSTATUS Result; > + PVOID StackFrame; > + > + /* > + * Converting to a GUI thread safely updates ESP in-place as well as the > + * current Thread->TrapFrame and EBP when KeSwitchKernelStack is called. > + * > + * However, PsConvertToGuiThread "helpfully" restores EBP to the original > + * caller's value, since it is considered a nonvolatile register. As such, > + * as soon as we're back after the conversion and we try to store the result > + * which will probably be in some stack variable (EBP-based), we'll crash as > + * we are touching the de-allocated non-expanded stack. > + * > + * Thus we need a way to update our EBP before EBP is touched, and the only > + * way to guarantee this is to do the call itself in assembly, use the EAX > + * register to store the result, fixup EBP, and then let the C code continue > + * on its merry way. > + * > + */ > + __asm__ __volatile__ > + ( > + "movl %%ebp, %1\n" > + "subl %%esp, %1\n" > + "call _PsConvertToGuiThread@0\n" > + "addl %%esp, %1\n" > + "movl %1, %%ebp\n" > + "movl %%eax, %0\n" > + : "=r"(Result), "=r"(StackFrame) > + : > + : "%esp", "%ecx", "%edx" > + ); > + > + return Result; > +} > > Modified: trunk/reactos/ntoskrnl/ke/i386/trap.s > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/trap.s?re… > ============================================================================== > --- trunk/reactos/ntoskrnl/ke/i386/trap.s [iso-8859-1] (original) > +++ trunk/reactos/ntoskrnl/ke/i386/trap.s [iso-8859-1] Tue Jan 19 10:45:30 2010 > @@ -129,260 +129,30 @@ > .endfunc > > .func KiFastCallEntry > -TRAP_FIXUPS FastCallDrSave, FastCallDrReturn, DoNotFixupV86, DoNotFixupAbios > _KiFastCallEntry: > > - /* Enter the fast system call prolog */ > - FASTCALL_PROLOG FastCallDrSave, FastCallDrReturn > - > -SharedCode: > - > - /* > - * Find out which table offset to use. Converts 0x1124 into 0x10. > - * The offset is related to the Table Index as such: Offset = TableIndex x 10 > - */ > - mov edi, eax > - shr edi, SERVICE_TABLE_SHIFT > - and edi, SERVICE_TABLE_MASK > - mov ecx, edi > - > - /* Now add the thread's base system table to the offset */ > - add edi, [esi+KTHREAD_SERVICE_TABLE] > - > - /* Get the true syscall ID and check it */ > - mov ebx, eax > - and eax, SERVICE_NUMBER_MASK > - cmp eax, [edi+SERVICE_DESCRIPTOR_LIMIT] > - > - /* Invalid ID, try to load Win32K Table */ > - jnb KiBBTUnexpectedRange > - > - /* Check if this was Win32K */ > - cmp ecx, SERVICE_TABLE_TEST > - jnz NotWin32K > - > - /* Get the TEB */ > - mov ecx, PCR[KPCR_TEB] > - > - /* Check if we should flush the User Batch */ > - xor ebx, ebx > -_ReadBatch: > - or ebx, [ecx+TEB_GDI_BATCH_COUNT] > - jz NotWin32K > - > - /* Flush it */ > - push edx > - push eax > - call [_KeGdiFlushUserBatch] > - pop eax > - pop edx > - > -NotWin32K: > - /* Increase total syscall count */ > - inc dword ptr PCR[KPCR_SYSTEM_CALLS] > - > -#if DBG > - /* Increase per-syscall count */ > - mov ecx, [edi+SERVICE_DESCRIPTOR_COUNT] > - jecxz NoCountTable > - inc dword ptr [ecx+eax*4] > -#endif > - > - /* Users's current stack frame pointer is source */ > -NoCountTable: > - mov esi, edx > - > - /* Allocate room for argument list from kernel stack */ > - mov ebx, [edi+SERVICE_DESCRIPTOR_NUMBER] > - xor ecx, ecx > - mov cl, [eax+ebx] > - > - /* Get pointer to function */ > - mov edi, [edi+SERVICE_DESCRIPTOR_BASE] > - mov ebx, [edi+eax*4] > - > - /* Allocate space on our stack */ > - sub esp, ecx > - > - /* Set the size of the arguments and the destination */ > - shr ecx, 2 > - mov edi, esp > - > - /* Make sure we're within the User Probe Address */ > - cmp esi, _MmUserProbeAddress > - jnb AccessViolation > - > -_CopyParams: > - /* Copy the parameters */ > - rep movsd > - > - /* Do the System Call */ > - call ebx > - > -AfterSysCall: > -#if DBG > - /* Make sure the user-mode call didn't return at elevated IRQL */ > - test byte ptr [ebp+KTRAP_FRAME_CS], MODE_MASK > - jz SkipCheck > - mov esi, eax /* We need to save the syscall's return val */ > - call _KeGetCurrentIrql@0 > - or al, al > - jnz InvalidIrql > - mov eax, esi /* Restore it */ > - > - /* Get our temporary current thread pointer for sanity check */ > - mov ecx, PCR[KPCR_CURRENT_THREAD] > - > - /* Make sure that we are not attached and that APCs are not disabled */ > - mov dl, [ecx+KTHREAD_APC_STATE_INDEX] > - or dl, dl > - jnz InvalidIndex > - mov edx, [ecx+KTHREAD_COMBINED_APC_DISABLE] > - or edx, edx > - jnz InvalidIndex > -#endif > - > -SkipCheck: > - > - /* Deallocate the kernel stack frame */ > - mov esp, ebp > - > -KeReturnFromSystemCall: > - > - /* Get the Current Thread */ > - mov ecx, PCR[KPCR_CURRENT_THREAD] > - > - /* Restore the old trap frame pointer */ > - mov edx, [ebp+KTRAP_FRAME_EDX] > - mov [ecx+KTHREAD_TRAP_FRAME], edx > + /* Sane FS segment */ > + mov ecx, KGDT_R0_PCR > + mov fs, cx > > - /* Exit the system call */ > - mov ecx, ebp > - mov edx, eax > - jmp @KiServiceExit@8 > -.endfunc > - > -KiBBTUnexpectedRange: > - > - /* If this isn't a Win32K call, fail */ > - cmp ecx, SERVICE_TABLE_TEST > - jne InvalidCall > - > - /* Set up Win32K Table */ > - push edx > - push ebx > - call _PsConvertToGuiThread@0 > - > - /* Check return code */ > - or eax, eax > - > - /* Restore registers */ > - pop eax > - pop edx > - > - /* Reset trap frame address */ > - mov ebp, esp > - mov [esi+KTHREAD_TRAP_FRAME], ebp > - > - /* Try the Call again, if we suceeded */ > - jz SharedCode > - > - /* > - * The Shadow Table should have a special byte table which tells us > - * whether we should return FALSE, -1 or STATUS_INVALID_SYSTEM_SERVICE. > - */ > - > - /* Get the table limit and base */ > - lea edx, _KeServiceDescriptorTableShadow + SERVICE_TABLE_TEST > - mov ecx, [edx+SERVICE_DESCRIPTOR_LIMIT] > - mov edx, [edx+SERVICE_DESCRIPTOR_BASE] > - > - /* Get the table address and add our index into the array */ > - lea edx, [edx+ecx*4] > - and eax, SERVICE_NUMBER_MASK > - add edx, eax > - > - /* Find out what we should return */ > - movsx eax, byte ptr [edx] > - or eax, eax > - > - /* Return either 0 or -1, we've set it in EAX */ > - jle KeReturnFromSystemCall > - > - /* Set STATUS_INVALID_SYSTEM_SERVICE */ > - mov eax, STATUS_INVALID_SYSTEM_SERVICE > - jmp KeReturnFromSystemCall > - > -InvalidCall: > - > - /* Invalid System Call */ > - mov eax, STATUS_INVALID_SYSTEM_SERVICE > - jmp KeReturnFromSystemCall > - > -AccessViolation: > - > - /* Check if this came from kernel-mode */ > - test byte ptr [ebp+KTRAP_FRAME_CS], MODE_MASK > - > - /* It's fine, go ahead with it */ > - jz _CopyParams > - > - /* Caller sent invalid parameters, fail here */ > - mov eax, STATUS_ACCESS_VIOLATION > - jmp AfterSysCall > - > -BadStack: > - > - /* Restore ESP0 stack */ > - mov ecx, PCR[KPCR_TSS] > - mov esp, ss:[ecx+KTSS_ESP0] > - > - /* Generate V86M Stack for Trap 6 */ > - push 0 > - push 0 > - push 0 > - push 0 > - > - /* Generate interrupt stack for Trap 6 */ > - push KGDT_R3_DATA + RPL_MASK > - push 0 > - push 0x20202 > - push KGDT_R3_CODE + RPL_MASK > - push 0 > - jmp _KiTrap06 > - > -#if DBG > -InvalidIrql: > - /* Save current IRQL */ > - push PCR[KPCR_IRQL] > - > - /* Set us at passive */ > - mov dword ptr PCR[KPCR_IRQL], 0 > - cli > - > - /* Bugcheck */ > - push 0 > - push 0 > - push eax > - push ebx > - push IRQL_GT_ZERO_AT_SYSTEM_SERVICE > - call _KeBugCheckEx@20 > - > -InvalidIndex: > - > - /* Get the index and APC state */ > - movzx eax, byte ptr [ecx+KTHREAD_APC_STATE_INDEX] > - mov edx, [ecx+KTHREAD_COMBINED_APC_DISABLE] > - > - /* Bugcheck */ > - push 0 > - push edx > - push eax > - push ebx > - push APC_INDEX_MISMATCH > - call _KeBugCheckEx@20 > - ret > -#endif > + /* Sane stack and frame */ > + mov esp, PCR[KPCR_TSS] > + mov esp, [esp+KTSS_ESP0] > + > + /* Make space for trap frame on the stack */ > + sub esp, KTRAP_FRAME_V86_ES > + > + /* Save EBP, EBX, ESI, EDI only! */ > + mov [esp+KTRAP_FRAME_EBX], ebx > + mov [esp+KTRAP_FRAME_ESI], esi > + mov [esp+KTRAP_FRAME_EDI], edi > + mov [esp+KTRAP_FRAME_EBP], ebp > + > + /* Call C handler -- note that EDX is the user stack, and EAX the syscall */ > + mov ecx, esp > + add edx, 8 > + jmp _KiFastCallEntryHandler > +.endfunc > > .func Kei386EoiHelper@0 > _Kei386EoiHelper@0: > > Modified: trunk/reactos/ntoskrnl/ke/i386/traphdlr.c > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/traphdlr.… > ============================================================================== > --- trunk/reactos/ntoskrnl/ke/i386/traphdlr.c [iso-8859-1] (original) > +++ trunk/reactos/ntoskrnl/ke/i386/traphdlr.c [iso-8859-1] Tue Jan 19 10:45:30 2010 > @@ -1465,6 +1465,7 @@ > } > > /* Check for syscall fault */ > +#if 0 > if ((TrapFrame->Eip == (ULONG_PTR)CopyParams) || > (TrapFrame->Eip == (ULONG_PTR)ReadBatch)) > { > @@ -1472,7 +1473,7 @@ > UNIMPLEMENTED; > while (TRUE); > } > - > +#endif > /* Check for VDM trap */ > ASSERT((KiVdmTrap(TrapFrame)) == FALSE); > > @@ -1725,9 +1726,14 @@ > goto ExitCall; > } > > - /* GUI calls are not yet supported */ > - UNIMPLEMENTED; > - while (TRUE); > + /* Convert us to a GUI thread -- must wrap in ASM to get new EBP */ > + Result = KiConvertToGuiThread(); > + if (__builtin_expect(!NT_SUCCESS(Result), 0)) > + { > + /* Figure out how we should fail to the user */ > + UNIMPLEMENTED; > + while (TRUE); > + } > > /* Try the call again */ > continue; > @@ -1741,8 +1747,7 @@ > if (__builtin_expect(Offset & SERVICE_TABLE_TEST, 0)) > { > /* Get the batch count and flush if necessary */ > - UNIMPLEMENTED; > - while (TRUE); > + if (NtCurrentTeb()->GdiBatchCount) KeGdiFlushUserBatch(); > } > > /* Increase system call count */ > @@ -1816,6 +1821,39 @@ > /* Enable interrupts and make the call */ > _enable(); > KiSystemCall(ServiceNumber, Arguments); > +} > + > +VOID > +__attribute__((regparm(3))) > +KiFastCallEntryHandler(IN ULONG ServiceNumber, > + IN PVOID Arguments, > + IN PKTRAP_FRAME TrapFrame) > +{ > + PKTHREAD Thread; > + > + /* Fixup segments */ > + Ke386SetDs(KGDT_R3_DATA | RPL_MASK); > + Ke386SetEs(KGDT_R3_DATA | RPL_MASK); > + > + /* Set up a fake INT Stack and enable interrupts */ > + TrapFrame->HardwareSegSs = KGDT_R3_DATA | RPL_MASK; > + TrapFrame->HardwareEsp = (ULONG_PTR)Arguments - 8; // Stack is 2 frames down > + TrapFrame->EFlags = __readeflags() | EFLAGS_INTERRUPT_MASK; > + TrapFrame->SegCs = KGDT_R3_CODE | RPL_MASK; > + TrapFrame->Eip = SharedUserData->SystemCallReturn; > + __writeeflags(0x2); > + > + /* Get the current thread */ > + Thread = KeGetCurrentThread(); > + > + /* Call the shared handler (inline) */ > + KiSystemCallHandler(TrapFrame, > + ServiceNumber, > + Arguments, > + Thread, > + UserMode, > + Thread->PreviousMode, > + KGDT_R3_TEB | RPL_MASK); > } > > VOID > > _________________________________________________________________ 25 Gygabite gratis online. Archivia e condividi i tuoi file! http://www.windowslive.it/skyDrive.aspx

14 years, 11 months

Re: [ros-dev] Request for a project

by sudheer kumar

hello guys, I am sorry for not mentioning a specific area that I am interested. I am interested in filesystems. Thank you Aleksey , victor and others for providing the list of projects. From the list I am interested in the partition manger as arty shed some light it. Any suggestions and help are most welcome. Thanks & Regards, sudheer.

14 years, 11 months

CreateFileW doesn't support relative path???

by Xiaoming Gao

Hi,guys: it seems that CreateFileW doesn't support relative path to create a file,,,weird.... the code belows: InitializeObjectAttributes(&ObjectAttributes, &NtPathU, 0, NULL, NULL); if (lpSecurityAttributes) { if(lpSecurityAttributes->bInheritHandle) ObjectAttributes.Attributes |= OBJ_INHERIT; ObjectAttributes.SecurityDescriptor = lpSecurityAttributes->lpSecurityDescriptor; } if(!(dwFlagsAndAttributes & FILE_FLAG_POSIX_SEMANTICS)) ObjectAttributes.Attributes |= OBJ_CASE_INSENSITIVE; /* perform the call */ Status = NtCreateFile (&FileHandle, dwDesiredAccess, &ObjectAttributes, &IoStatusBlock, NULL, FileAttributes, dwShareMode, dwCreationDisposition, Flags, EaBuffer, EaLength);

14 years, 11 months

Update on Wikipedia page

by Joshua Bailey

I read the PDF and other information earlier today. I've just updated the Wikipedia page (in English, at least) regarding Arwinss with the newer, more detailed information. Hopefully, once more people know about Arwinss and what it will do for ReactOS, more people will appreciate the potential of this project and join in. I felt you guys should know, since I brought up the issue earlier. Feel free to check on it and correct any errors I've made. :) -Joshua Bailey

14 years, 11 months

Can't compile

by Evans Jahja

Hi, I'm trying to compile React OS. (This time I use gcc version 4.3.4 20090804 (release) 1 (GCC) ) However, when compiling it returns: [CC] base/applications/screensavers/3dtext/3dtext.c In file included from include/psdk/windows.h:40, from base/applications/screensavers/3dtext/3dtext.c:21: include/crt/stdarg.h:34:2: error: #error Only Win32 target is supported! In file included from include/crt/stdarg.h:147, from include/psdk/windows.h:40, from base/applications/screensavers/3dtext/3dtext.c:21: include/crt/vadefs.h:10:2: error: #error Only Win32 target is supported! cc1: warnings being treated as errors In file included from include/psdk/winnt.h:48, from include/psdk/windef.h:339, from include/psdk/windows.h:41, from base/applications/screensavers/3dtext/3dtext.c:21: include/crt/ctype.h:121: error: conflicting types for built-in function `iswalpha' include/crt/ctype.h:123: error: conflicting types for built-in function `iswupper' include/crt/ctype.h:125: error: conflicting types for built-in function `iswlower' include/crt/ctype.h:127: error: conflicting types for built-in function `iswdigit' include/crt/ctype.h:129: error: conflicting types for built-in function `iswxdigit' include/crt/ctype.h:131: error: conflicting types for built-in function `iswspace' include/crt/ctype.h:133: error: conflicting types for built-in function `iswpunct' include/crt/ctype.h:135: error: conflicting types for built-in function `iswalnum' include/crt/ctype.h:137: error: conflicting types for built-in function `iswprint' include/crt/ctype.h:139: error: conflicting types for built-in function `iswgraph' include/crt/ctype.h:141: error: conflicting types for built-in function `iswcntrl' include/crt/ctype.h:146: error: conflicting types for built-in function `towupper' include/crt/ctype.h:148: error: conflicting types for built-in function `towlower' include/crt/ctype.h:159: error: conflicting types for built-in function `iswblank' make: *** [obj-i386/base/applications/screensavers/3dtext/3dtext_3dtext.o] Error 1 bash-3.2$ gcc -v Using built-in specs. Target: i686-pc-cygwin Configured with: /gnu/gcc/releases/packaging/4.3.4-3/gcc4-4.3.4-3/src/gcc-4.3.4/configure --srcdir=/gnu/gcc/releases/packaging/ ..3.4-3/gcc4-4.3.4-3/src/gcc-4.3.4 --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --libexecdir=/usr/lib -datadir=/usr/share --localstatedir=/var --sysconfdir=/etc --infodir=/usr/share/info --mandir=/usr/share/man --datadir=/usr/sha e --infodir=/usr/share/info --mandir=/usr/share/man -v --with-gmp=/usr --with-mpfr=/usr --enable-bootstrap --enable-version-spe ific-runtime-libs --with-slibdir=/usr/bin --libexecdir=/usr/lib --enable-static --enable-shared --enable-shared-libgcc --disabl -__cxa_atexit --with-gnu-ld --with-gnu-as --with-dwarf2 --disable-sjlj-exceptions --enable-languages=ada,c,c++,fortran,java,obj ,obj-c++ --disable-symvers --enable-libjava --program-suffix=-4 --enable-libgomp --enable-libssp --enable-libada --enable-threa s=posix --with-arch=i686 --with-tune=generic --enable-libgcj-sublibs CC=gcc-4 CXX=g++-4 CC_FOR_TARGET=gcc-4 CXX_FOR_TARGET=g++- GNATMAKE_FOR_TARGET=gnatmake GNATBIND_FOR_TARGET=gnatbind AS=/opt/gcc-tools/bin/as..exe AS_FOR_TARGET=/opt/gcc-tools/bin/as.exe LD=/opt/gcc-tools/bin/ld..exe LD_FOR_TARGET=/opt/gcc-tools/bin/ld.exe --with-ecj-jar=/usr/share/java/ecj.jar Thread model: posix gcc version 4.3.4 20090804 (release) 1 (GCC) bash-3.2$ make [WIDL] obj-i386/include/psdk/xmldom.h [WIDL] obj-i386/include/psdk/xmldso.h [WIDL] obj-i386/include/psdk/comcat.h [WIDL] obj-i386/include/psdk/wuapi.h [WIDL] obj-i386/include/psdk/wtypes.h [WIDL] obj-i386/include/psdk/exdisp.h [WIDL] obj-i386/include/psdk/mshtmhst.h [WIDL] obj-i386/include/psdk/mscoree..h [WIDL] obj-i386/include/psdk/mimeole.h [WIDL] obj-i386/include/psdk/wincodec.h [WIDL] obj-i386/include/psdk/urlmon.h [WIDL] obj-i386/include/psdk/urlhist.h [WIDL] obj-i386/include/psdk/unknwn.h [WIDL] obj-i386/include/psdk/tom.h [WIDL] obj-i386/include/psdk/textstor.h [WIDL] obj-i386/include/psdk/strmif.h [WIDL] obj-i386/include/psdk/shtypes.h [WIDL] obj-i386/include/psdk/shobjidl.h [WIDL] obj-i386/include/psdk/shldisp.h [WIDL] obj-i386/include/psdk/servprov.h [WIDL] obj-i386/include/psdk/sensevts.h [WIDL] obj-i386/include/psdk/richole.h [WIDL] obj-i386/include/psdk/pstore.h [WIDL] obj-i386/include/psdk/propidl.h [WIDL] obj-i386/include/psdk/perhist.h [WIDL] obj-i386/include/psdk/optary.h [WIDL] obj-i386/include/psdk/oleidl.h [WIDL] obj-i386/include/psdk/oledb.h [WIDL] obj-i386/include/psdk/oleacc.h [WIDL] obj-i386/include/psdk/ocmm.h [WIDL] obj-i386/include/psdk/ocidl.h [WIDL] obj-i386/include/psdk/objsafe.h [WIDL] obj-i386/include/psdk/objidl.h [WIDL] obj-i386/include/psdk/oaidl.h [WIDL] obj-i386/include/psdk/netfw.h [WIDL] obj-i386/include/psdk/msxml2.h [WIDL] obj-i386/include/psdk/msxml.h [WIDL] obj-i386/include/psdk/mstask.h [WIDL] obj-i386/include/psdk/mshtml.h [WIDL] obj-i386/include/psdk/msctf.h [WIDL] obj-i386/include/psdk/mlang.h [WIDL] obj-i386/include/psdk/mimeinfo.h [WIDL] obj-i386/include/psdk/indexsrv.h [WIDL] obj-i386/include/psdk/imnxport.h [WIDL] obj-i386/include/psdk/imnact.h [WIDL] obj-i386/include/psdk/icftypes.h [WIDL] obj-i386/include/psdk/iads.h [WIDL] obj-i386/include/psdk/htiframe.h [WIDL] obj-i386/include/psdk/hlink.h [WIDL] obj-i386/include/psdk/fusion.h [WIDL] obj-i386/include/psdk/downloadmgr.h [WIDL] obj-i386/include/psdk/docobj.h [WIDL] obj-i386/include/psdk/dispex.h [WIDL] obj-i386/include/psdk/dimm.h [WIDL] obj-i386/include/psdk/ctxtcall.h [WIDL] obj-i386/include/psdk/control.h [WIDL] obj-i386/include/psdk/bits..h [WIDL] obj-i386/include/psdk/bits1_5.h [WIDL] obj-i386/include/psdk/activscp.h [WIDL] obj-i386/include/psdk/activdbg.h [WIDL] obj-i386/include/psdk/activaut.h [GENDIB] obj-i386/subsystems/win32/win32k/dib/dib32gen.c [NCI] obj-i386/lib/ntdllsys/ntdll.S [RBUILD] makefile.auto Reading build files...done Detecting compiler...not detected Detecting binutils...not detected Detecting netwide assembler...not detected Detecting compiler -pipe support...not detected Detecting compiler pre-compiled header support...not detected Processing modules...done Creating directories...done Generating test support code...done Generating compilation unit support code...done Generating syssetup.inf....done Generating proxy makefiles...done Checking automatic dependencies....done [WIDL] obj-i386/include/psdk/exdisp.h [WIDL] obj-i386/include/psdk/msxml2.h [WIDL] obj-i386/include/psdk/commoncontrols.h [HOST-CC] lib/inflib/infcore.c lib/inflib/infcore.c: In function `line_start_state': lib/inflib/infcore.c:524: warning: array subscript has type `char' lib/inflib/infcore.c: In function `key_name_state': lib/inflib/infcore.c:597: warning: array subscript has type `char' lib/inflib/infcore..c: In function `value_name_state': lib/inflib/infcore.c:649: warning: array subscript has type `char' lib/inflib/infcore.c: In function `eol_backslash_state': lib/inflib/infcore.c:694: warning: array subscript has type `char' lib/inflib/infcore.c: In function `leading_spaces_state': lib/inflib/infcore.c:751: warning: array subscript has type `char' lib/inflib/infcore.c: In function `trailing_spaces_state': lib/inflib/infcore.c:772: warning: array subscript has type `char' [HOST-CC] lib/inflib/infget.c [HOST-CC] lib/inflib/infput.c [HOST-CC] lib/inflib/infhostgen.c [HOST-CC] lib/inflib/infhostget.c [HOST-CC] lib/inflib/infhostput.c [HOST-LD] output-i386/tools/rbuild/rbuild [GENDIB] obj-i386/subsystems/win32/win32k/dib/dib32gen.c [NCI] obj-i386/lib/ntdllsys/ntdll.S [RBUILD] makefile.auto Reading build files...done Detecting compiler...not detected Detecting binutils...not detected Detecting netwide assembler...not detected Detecting compiler -pipe support...not detected Detecting compiler pre-compiled header support...not detected Processing modules...done Creating directories...done Generating test support code...done Generating compilation unit support code...done Generating syssetup.inf...done Generating proxy makefiles...done Checking automatic dependencies...done [CC] base/applications/screensavers/3dtext/3dtext.c In file included from include/psdk/windows.h:40, from base/applications/screensavers/3dtext/3dtext.c:21: include/crt/stdarg.h:34:2: error: #error Only Win32 target is supported! In file included from include/crt/stdarg.h:147, from include/psdk/windows.h:40, from base/applications/screensavers/3dtext/3dtext.c:21: include/crt/vadefs.h:10:2: error: #error Only Win32 target is supported! cc1: warnings being treated as errors In file included from include/psdk/winnt.h:48, from include/psdk/windef.h:339, from include/psdk/windows.h:41, from base/applications/screensavers/3dtext/3dtext.c:21: include/crt/ctype.h:121: error: conflicting types for built-in function `iswalpha' include/crt/ctype.h:123: error: conflicting types for built-in function `iswupper' include/crt/ctype.h:125: error: conflicting types for built-in function `iswlower' include/crt/ctype.h:127: error: conflicting types for built-in function `iswdigit' include/crt/ctype.h:129: error: conflicting types for built-in function `iswxdigit' include/crt/ctype.h:131: error: conflicting types for built-in function `iswspace' include/crt/ctype.h:133: error: conflicting types for built-in function `iswpunct' include/crt/ctype.h:135: error: conflicting types for built-in function `iswalnum' include/crt/ctype.h:137: error: conflicting types for built-in function `iswprint' include/crt/ctype.h:139: error: conflicting types for built-in function `iswgraph' include/crt/ctype.h:141: error: conflicting types for built-in function `iswcntrl' include/crt/ctype.h:146: error: conflicting types for built-in function `towupper' include/crt/ctype.h:148: error: conflicting types for built-in function `towlower' include/crt/ctype.h:159: error: conflicting types for built-in function `iswblank' make: *** [obj-i386/base/applications/screensavers/3dtext/3dtext_3dtext.o] Error 1 Please help me. Regards, Evans New Email names for you! Get the Email name you've always wanted on the new @ymail and @rocketmail. Hurry before someone else does! http://mail.promotions.yahoo.com/newdomains/aa/

14 years, 11 months

Wikipedia article changes, censorship

by Joshua Bailey

If you guys don't know me by know, my name is Joshua Bailey, though you may recognize me better as RaptorEmperor on the forums. I infrequently do software testing for the ReactOS project, and I've also just started teaching myself how to do debugging work. If I knew C, better understood the Windows architecture, and felt more comfortable in my abilities as a programmer I would probably join in development outright. I'm a pretty frequent visitor to the forums, but I don't generally post anything to the ros-dev mailing list because I'd rather not distract the developers with my random questions about GDI support or whatever else crosses my mind and leave this mailing list open to more important matters. For as long as I have been involved with the ReactOS project I've also been a Wikipedia editor. I check on the ReactOS article on Wikipedia periodically to see if there are any points in the article to which I can add relevant information so readers are better informed (and hopefully more interested) in the ReactOS project. A few weeks ago I added a reference to Arwinss in the paragraph of the article detailing the relationship between ReactOS and other projects, more specifically Wine. Tonight I checked the article, and I noticed that the reference to Arwinss was removed by LoneRifle, with the attached comment "Current and future development: Remove information about arwinss on request of the Dev team". I initially linked my reference to Arwinss in the Wikipedia article to the Arwinss wiki page, and another user by the name of XRideBMX changed the reference to Newsletter #62, which was the first announcement on the main page about Arwinss. Both of these sources are publicly available from the ReactOS website. There's nothing dubious about their accuracy or point of view. Considering this, and the outright statement on the article's revision history, I'm left to conclude that the only reason that my edit was removed was censorship on the part of the ReactOS development team. The reason I find this disturbing is that Wikipedia standards dictate a non-point-of-view policy. By having underlings edit the article to best reflect the preferred viewpoints of the developers, the integrity of the article is compromised. If my edits were removed for a more legitimate reason, for example, because someone didn't feel they were relevant, I could argue the point with them personally. But as a source of free information, without intent of bias, seeing the developers complicit in censorship on Wikipedia makes me feel extremely uncomfortable about ReactOS. I'm sure Dick Cheney and the CIA don't appreciate their dirty laundry (waterboarding, etc.) being plastered in a public encyclopedia, but flags would be immediately raised if the waterboarding article was changed with the article history stating "Remove information about CIA waterboarding on the request of George Tenet". Seeing this kind of behavior coming from free and open-source project, and the flagrant nature of it, is extremely disturbing to me. I'm formally asking you, the development team, why my comments were deemed necessary for removal. Since I was the one who made the edit, and considering the concerns I have listed, I deserve some explanation. As far as I can tell, mentioning Arwinss in a public encyclopedia, using publicly available sources, does no harm to the project. What about the existence of Arwinss was deemed too secret for a Wikipedia page? How can Arwinss be considered public enough for the ReactOS front page, but not enough for a Wikipedia page? What legitimate reason is there for removing the reference to Arwinss in Wikipedia? Outside of a sloppy attempt at censorship? I have been very excited about the ReactOS project since I first discovered it around 2005, and with Arwinss on the radar I'm more excited to see what is going to come out of the project than I have been in a long time. However, if the development team is not comfortable enough to trust that people can make their own opinions about ReactOS without censoring irrelevant details on a Wikipedia page, maybe I should consider whether or not ReactOS really adheres to the principles of openness and freedom that I do. As much as I like ReactOS, the I hold the values of open-source first. I apologize if my formatting appears to be poor, because I don't send emails to mailing lists from this email account that often. I would greatly appreciate a response. If there is a misunderstanding here I would very much like to resolve it, to clear up my current reservations about the ReactOS project. If not, I reserve my right to revert the changes to the article. -Joshua Bailey

14 years, 11 months

Wikipedia article changes, censorship

by Joshua Bailey

>yes, I asked LoneRifle to remove the reference because I was preparing much better information (which has just been released yesterday) and >didn't want people to read old incomplete info. So from now on you could use this information in our wikipedia article. If that was the case, that makes sense. Removing the information from the article outright, as opposed to simply waiting and updating the article with more detailed information when it was available might have been a better way of doing things so no red flags pop up, in my mind or the mind of others. Alternately, you, LoneRifle, or whoever is the one most in charge of maintaining the Wikipedia page should have at least noted that the information was going to be replaced with updated information so no other Wikipedia editors were left to assume that the information was simply going to disappear. Probably the only reason I didn't revert the changes immediately was because I wanted to ask the devs about it first to see if there was a misunderstanding. My desire to see ReactOS succeed was tempering my natural instinct to assume the worst about the situation. Betov already made accusations of ReactOS fans tampering with Wikipedia a while back, and while I don't believe that his claims are true, a random person reading Betov's accusations and then seeing that kind of a statement in the article's revision history might be more apt to be apprehensive about the project. Because of the bad rap ReactOS has gotten in the past, we have to be more careful to avoid feeding into any misinformation that has been spread about ReactOS. Hopefully you can see why I was concerned. It's cool now, we'll just have to do things a bit differently in the future. Thanks for getting back to me so quickly. Since that's cleared up, now I can sit around and get excited about Arwinss again. When should us testers expect to see a working Arwinss in the trunk builds to test? -Joshua Bailey

14 years, 11 months

Re: [ros-dev] Request for a project

by sudheer kumar

hello, Thank you very much for all the help guys. I am interested in the Fast FAT project. Also arty and colibri gave me an idea to work on partmgr.sys. I am more interested towards Fast FAT as I have prior experience on file systems and I can show something concrete to my professor. The other thing is for partmgr.sys I need to start from the scratch and there isnt much info about it. Is it fine for others ??(since some one might be working on it).The idea of adding list of all the medium sized task to the wiki is good as its going to help people like me. Thanks & Regards, sudhir.

14 years, 11 months

Re: [ros-dev] [ros-diffs] [spetreolle] 45091: Disable spooler service. This allows bootcdregtest to start here under qemu-kvm.

by Ged Murphy

This sounds like a hack. Why would disabling a service fix an operating system? Also, don't we need this service for certain Wine tests? -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of spetreolle(a)svn.reactos.org Sent: 15 January 2010 22:17 To: ros-diffs(a)reactos.org Subject: [ros-diffs] [spetreolle] 45091: Disable spooler service. This allows bootcdregtest to start here under qemu-kvm. Author: spetreolle Date: Fri Jan 15 23:17:16 2010 New Revision: 45091 URL: http://svn.reactos.org/svn/reactos?rev=45091&view=rev Log: Disable spooler service. This allows bootcdregtest to start here under qemu-kvm. Modified: trunk/reactos/boot/bootdata/hivesys_i386.inf Modified: trunk/reactos/boot/bootdata/hivesys_i386.inf URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/bootdata/hivesys_i386… ============================================================================== --- trunk/reactos/boot/bootdata/hivesys_i386.inf [iso-8859-1] (original) +++ trunk/reactos/boot/bootdata/hivesys_i386.inf [iso-8859-1] Fri Jan 15 23:17:16 2010 @@ -1198,7 +1198,7 @@ HKLM,"SYSTEM\CurrentControlSet\Services\Spooler","Group",0x00000000,"SpoolerGroup" HKLM,"SYSTEM\CurrentControlSet\Services\Spooler","ImagePath",0x00020000,"%SystemRoot%\system32\spoolsv.exe" HKLM,"SYSTEM\CurrentControlSet\Services\Spooler","ObjectName",0x00000000,"LocalSystem" -HKLM,"SYSTEM\CurrentControlSet\Services\Spooler","Start",0x00010001,0x00000002 +HKLM,"SYSTEM\CurrentControlSet\Services\Spooler","Start",0x00010001,0x00000004 HKLM,"SYSTEM\CurrentControlSet\Services\Spooler","Type",0x00010001,0x00000110 ; WLAN service

14 years, 11 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev January 2010