- Ros-dev - ReactOS.org

Big Bug in CreateWindowEx
by James Tabor 10 Aug '06

10 Aug '06

Hi, I guess Hervé has found something similar. We can not create a desktop window in createwindowex. I've looked at it again and at it's current state it would be imposable to do w/o some rewriting (already started). We need to fix this Atom issue I'm pushing! With a common atom we can fix this message problem. Setup the children so they can talk to each other. So far, we have four desktops w/o a root. Non of them can talk to each other. I can't see it! If this can be fixed, I bet things will magically start working. Well, look at this, it's from wine, I think they got it. #define DESKTOP_CLASS_ATOM MAKEINTATOMW(32769) /* create the desktop window */ hwnd = CreateWindowExW( 0, DESKTOP_CLASS_ATOM, NULL, WS_POPUP | WS_VISIBLE | WS_CLIPSIBLINGS | WS_CLIPCHILDREN, 0, 0, width, height, 0, 0, 0, NULL ); if (hwnd == GetDesktopWindow()) { SetWindowLongPtrW( hwnd, GWLP_WNDPROC, (LONG_PTR)desktop_wnd_proc ); SendMessageW( hwnd, WM_SETICON, ICON_BIG, (LPARAM)LoadIconW( 0, MAKEINTRESOURCEW(OIC_WINLOGO))); SetWindowTextW( hwnd, desktop_nameW ); SystemParametersInfoA( SPI_SETDESKPATTERN, -1, NULL, FALSE ); SetDeskWallPaper( (LPSTR)-1 ); <snip> LiteStep and DarkStep, look about the same thing except for the atom. We dont need much of this but the process looks sound. B^| James

1 0

Problem drawing the desktop in the updated color
by Timo Kreuzer 10 Aug '06

10 Aug '06

Hi, First, this is going to be a long post, sorry ;-) You might have noticed, that I have been working on the desk.cpl appearance tab, wich is working partly. Here's the first version: http://www.reactos.org/bugzilla/show_bug.cgi?id=1732 Some things still don't work. For example the desktop doesn't get repainted in the new color. > ------- /Comment #5 > <http://www.reactos.org/bugzilla/show_bug.cgi?id=1732#c5> >From > jimtabor 2006-08-05 04:46:36 CET / [reply > <http://www.reactos.org/bugzilla/show_bug.cgi?id=1732#add_comment>] > ------- > Hi, > You can use WM_SYSCOLORCHANGE in the desktop proc if it is used, should be!, > user32/misc/desktop.c; > > static > LRESULT > WINAPI > DesktopWndProc( HWND hwnd, UINT message, WPARAM wParam, LPARAM lParam ) > { > DPRINT1("Desktop Class Atom!\n"); > switch(message) > { > case WM_NCCREATE: > return TRUE; > > case WM_CREATE: > /* when I spy I see notify */ > SendNotifyMessageW( hwnd, WM_SYSCOLORCHANGE , 0, 0 ); > break; > > case WM_SYSCOLORCHANGE: > /* update everything, well in theory anyway */ > RedrawWindow( hwnd, NULL, 0, RDW_INVALIDATE | RDW_ERASE | > RDW_ALLCHILDREN ); > break; > > default: > return DefWindowProcW(hwnd,message,wParam,lParam); > } > return 0; /* all other messages are ignored */ > } > > Its crude, I'm not sure if it will compile, its off the top of my head ATM. > 8^D > Thanks, > James > Thanks for helping, James. I tried it, but it doesn't work. 1.) Sending WM_SYSCOLORCHANGE on WM_CREATE will probably do nothing, because the desktop has just been created with the initial SysColors, no need to update them. 2.) RedrawWindow calls NtUserRedrawWindow wich calls co_UserRedrawWindow wich calls co_IntPaintWindows wich sends a WM_PAINT message to the desktop window. WM_PAINT is then passed to DefWindowProc and passed on to User32DefWindowProc wich does only repaint the icon as it seems. So WM_PAINT must be evaluated in DesktopWndProc. I tried the following: > case WM_PAINT: > { > PAINTSTRUCT ps; > HDC hdc = BeginPaint(hwnd, &ps); > PaintDesktop(hdc); > EndPaint(hwnd, &ps); > } PaintDesktop calls NtUserPaintDesktop, wich then paints the desktop. I have also replaced DesktopBrush = (HBRUSH)UserGetClassLongPtr(WndDesktop->Class, GCL_HBRBACKGROUND, FALSE); with DesktopBrush = IntGetSysColorBrush(COLOR_BACKGROUND); But the desktop is still painted in the original color, whereas the icon text is in the color I have set in the registry. I played a little around with the code in NtUserPaintDesktop. I added the following code before the desktop background is painted: > if (IntGetSysColor(COLOR_BACKGROUND) == 0) // This is true after > SysColors are loaded from Registry > { > DesktopBrush = IntGetSysColorBrush(COLOR_ACTIVECAPTION); > } And suddenly the desktop is painted in COLOR_ACTIVECAPTION. This is strange, because I also added CreateSysColorObjects(); at the beginning of NtUserPaintDesktop. Anybody any idea?

4 8

Re: [ros-dev] [ros-diffs] [fireball] 23524: Force -fno-sibling-call-optimisation to every module's CFLAGs. This fixes *numerous* bugs (thanks to a bug in GCC itself), even in DBG=1 builds! Just an example, comctl32.dll doesn't crash anymore in LISTVIEW_Callback(). Thanks to Dmitriy Philippov (aka Shedon) for encountering the comctl32 bug and investigating it!
by Alex Ionescu 09 Aug '06

09 Aug '06

"Bugs? There's no bugs in GCC. GCC is perfect." "I've never encountered a bug in GCC that would have real-life effects, except a small one a long time ago" -- Best regards, Alex Ionescu Project Lead, TinyKRNL Kernel-Mode Software Design Engineer, ReactOS

1 0

Re: [ros-dev] [ros-bugs] [Bug 1743] The MOVEFILE_DELAY_UNTIL_REBOOT flag is incorrect processed in the MoveFileWithProgressW function
by Brandon Turner 08 Aug '06

08 Aug '06

ReactOS.Bugzilla(a)reactos.org wrote: > http://www.reactos.org/bugzilla/show_bug.cgi?id=1743 > > > shedon(a)mail.ru changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > AssignedTo|ros-bugs(a)reactos.org |shedon(a)mail.ru > Status|NEW |ASSIGNED > > > > > ------- Comment #1 from shedon(a)mail.ru 2006-08-08 23:55 CET ------- > Created an attachment (id=1015) > --> (http://www.reactos.org/bugzilla/attachment.cgi?id=1015&action=view) > The patch for this bug > > > I just skimmed the patch, but this: - DPRINT("MoveFileWithProgressW()\n"); + DPRINT1("MoveFileWithProgressW()\n"); probably isnt a good idea. -- Brandon Turner turnerb7(a)msu.edu http://www.amateurgramming.com 810-516-6236

1 0

Revision 23521 - Infinite loop in CreateProcessW
by Hervé Poussineau 08 Aug '06

08 Aug '06

Hi, I've an (mostly) infinite loop in CreateProcessW, probably due to a bug in ntdll/loader/utils.c or in kernel APCs. To reproduce: - Download revision >= 23433 - Enable the call to StartService in base/system/winlogon/winlogon.c:StartCustomService This call leads to base/system/services/database.c:ScmStartUserModeService, which calls CreateProcessW The debug log is: (KERNEL32:dll\win32\kernel32\process\create.c:679) CreateProcessW: lpApplicationName: <NULL> lpCommandLine: lsass.exe lp Environment: 00000000 lpCurrentDirectory: <NULL> dwCreationFlags: 8 (ntoskrnl\ps\process.c:692) FIX PS SDs!! (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 00B50000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 00C2B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 00407000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 00C57000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 00C80000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 010C0000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0119B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 00411000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 011C7000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 011F0000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 01630000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0170B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 00421000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 01737000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 01760000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 01BA0000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 01C7B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 01CA7000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 01CB0000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 01CD9000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 02120000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 021FB000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 01D04000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 02227000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 02250000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 02690000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0276B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 02797000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 027A0000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 027C9000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 02C10000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 02CEB000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 027F4000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 02D17000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 02D40000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 03180000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0325B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 03287000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 03290000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 032B9000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 03700000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 037DB000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 032E4000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 03807000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 03830000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 03C70000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 03D4B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 03D77000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 03D80000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 03DA9000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 041F0000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 042CB000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 03DD4000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 042F7000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 04320000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 04760000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0483B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 04867000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 04870000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 04899000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 04CE0000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 04DBB000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 048C4000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 04DE7000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 04E10000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 05250000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0532B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 05357000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 05360000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 05389000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 057D0000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 058AB000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 053B4000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 058D7000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 05900000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 05D40000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 05E1B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 05E47000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 05E50000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 05E79000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 062C0000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0639B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 05EA4000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 063C7000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 063F0000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 06830000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0690B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 06937000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 06940000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 06969000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 06DB0000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 06E8B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 06994000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 06EB7000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 06EE0000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 07320000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 073FB000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 07427000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 07430000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 07459000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 078A0000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0797B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 07484000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 079A7000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 079D0000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 07E10000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 07EEB000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 07F17000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 07F20000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 07F49000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 08390000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0846B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 07F74000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 08497000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 084C0000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 08900000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 089DB000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 08A07000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 08A10000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 08A39000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 08E80000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 08F5B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 08A64000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 08F87000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 08FB0000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 093F0000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 094CB000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 094F7000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 09500000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 09529000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 09970000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 09A4B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 09554000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 09A77000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 09AA0000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 09EE0000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 09FBB000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 09FE7000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 09FF0000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 0A019000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 0A460000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0A53B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 0A044000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 0A567000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 0A590000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 0A9D0000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0AAAB000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 0AAD7000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 0AAE0000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 0AB09000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 0AF50000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0B02B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 0AB34000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 0B057000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 0B080000) C:\ReactOS\system32\advapi32.dll (ntoskrnl\ps\thread.c:500) FIX PS SDs!! (dll\ntdll\ldr\utils.c:2076) Relocating (7c800000 -> 0B4C0000) C:\ReactOS\system32\KERNEL32.dll (dll\ntdll\ldr\utils.c:2076) Relocating (78000000 -> 0B59B000) C:\ReactOS\System32\msvcrt.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76540000 -> 0B5C7000) C:\ReactOS\System32\lsasrv.dll (dll\ntdll\ldr\utils.c:2076) Relocating (76000000 -> 0B5D0000) C:\ReactOS\System32\rpcrt4.dll (dll\ntdll\ldr\utils.c:2076) Relocating (77dc0000 -> 0B5F9000) C:\ReactOS\system32\advapi32.dll (dll\ntdll\ldr\startup.c:485) Failed to initialize image (ntoskrnl\ke\kthread.c:406) Mutant: 80FD17D8. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 80FD8540. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 80FDF2B8. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 80FE6048. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 80FECE90. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 80FF3C20. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 80FFA980. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 810016F8. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 81008488. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 8100F218. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 81016028. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 8101CDB8. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 81023B80. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 8102A980. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 810317C8. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 810385C8. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 8103F390. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 81046120. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 8104CE98. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 81053C68. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 8105AA28. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 81061820. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 81068610. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 8106F3E8. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 81076190. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 8107CF30. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 81083CF8. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 8108AA80. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 810918A0. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 81098700. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 80FC2B88. Type, Size 2 8 (ntoskrnl\ke\kthread.c:406) Mutant: 80FCA9E8. Type, Size 2 8 See that kernel32.dll and others are loaded multiple times, and each time at a different address. I've no clue how to debug this. Anyone can take a look at it? Thanks in advance, Hervé

1 0

Re: [ros-dev] [ros-diffs] [ekohl] 23521: - Implement ScmStartServiceA and revert the last modification of StartServiceA. - Fix EnumServicesStatusExW.
by Hervé Poussineau 08 Aug '06

08 Aug '06

Hi, > Subject: [ros-diffs] [ekohl] 23521: > - Implement ScmStartServiceA and revert the last modification of StartServiceA. > - Fix EnumServicesStatusExW. We now have an exact code duplication between StartServiceA/StartServiceW (except strlen/wcslen and strcpy/wcscpy) and ScmrStartServiceA/ScmrStartServiceW. I don't think it's a good thing because we will have some problems to keep the code in sync. I did r23519 to prevent this code duplication and because ScmrStartServiceA() was not called except in StartServiceA. By the way, I also implemented argument conversion between ANSI and Unicode in StartServiceA before calling StartServiceW, which meant that arguments were ignored only in ScmrStartServiceW. Now, you have 2 places to take care of them (ScmrStartServiceA/W)... That was just to say my feeling... Hervé

1 0

Registry
by Timo Kreuzer 07 Aug '06

07 Aug '06

> Commit by *fireball* :: r*23508* *reactos*/ntoskrnl/ (cm/regobj.c > ob/obhandle.c): > > Goodbye REGISTRY_ERROR bsod! > > * Change UserMode -> KernelMode in ObReferenceObject*() calls, > because that calls failed > * Remove Cm-specific hack from Ob "advapi32_winetest.exe registry" > shows 0 failures on the first run and 2 failures on further > runs. I suppose there might be a leakage in the CM. To be > investigated further (or wait till complete Cm rewrite in October). > Still regedit crashes when trying to open a key that contains one or more values.

2 1

Re: [ros-dev] [ros-diffs] [fireball] 23508: Goodbye REGISTRY_ERROR bsod! - Change UserMode -> KernelMode in ObReferenceObject*() calls, because that calls failed - Remove Cm-specific hack from Ob "advapi32_winetest.exe registry" shows 0 failures on the first run and 2 failures on further runs. I suppose there might be a leakage in the CM. To be investigated further (or wait till complete Cm rewrite in October).
by Alex Ionescu 06 Aug '06

06 Aug '06

Hi, Alex-from-Texas here. WOW, that was awesome. I forgive you for comitting that satanic LDT "patch" because of this. Best regards, Alex Ionescu fireball(a)svn.reactos.org wrote: >Author: fireball >Date: Mon Aug 7 01:15:55 2006 >New Revision: 23508 > >URL: http://svn.reactos.org/svn/reactos?rev=23508&view=rev >Log: >Goodbye REGISTRY_ERROR bsod! > >- Change UserMode -> KernelMode in ObReferenceObject*() calls, because that calls failed >- Remove Cm-specific hack from Ob > >"advapi32_winetest.exe registry" shows 0 failures on the first run and 2 failures on further runs. >I suppose there might be a leakage in the CM. To be investigated further (or wait till complete Cm rewrite in October). > >Modified: > trunk/reactos/ntoskrnl/cm/regobj.c > trunk/reactos/ntoskrnl/ob/obhandle.c > >Modified: trunk/reactos/ntoskrnl/cm/regobj.c >URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/cm/regobj.c?rev=2… >============================================================================== >--- trunk/reactos/ntoskrnl/cm/regobj.c (original) >+++ trunk/reactos/ntoskrnl/cm/regobj.c Mon Aug 7 01:15:55 2006 >@@ -148,7 +148,7 @@ > ObReferenceObjectByPointer(FoundObject, > STANDARD_RIGHTS_REQUIRED, > CmiKeyType, >- UserMode); >+ KernelMode); > if (End != NULL) > { > *End = L'\\'; >@@ -790,7 +790,7 @@ > ObReferenceObjectByPointer(ParentKey, > STANDARD_RIGHTS_REQUIRED, > CmiKeyType, >- UserMode); >+ KernelMode); > NewKey->ParentKey = ParentKey; > } > > >Modified: trunk/reactos/ntoskrnl/ob/obhandle.c >URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ob/obhandle.c?rev… >============================================================================== >--- trunk/reactos/ntoskrnl/ob/obhandle.c (original) >+++ trunk/reactos/ntoskrnl/ob/obhandle.c Mon Aug 7 01:15:55 2006 >@@ -239,17 +239,8 @@ > /* Dereference the object as well */ > ASSERT(ObjectHeader->Type); > ASSERT(ObjectHeader->PointerCount != 0xCCCCCCCC); >- if (!wcscmp(ObjectHeader->Type->Name.Buffer, L"Key")) >- { >- // >- // WE DONT CLOSE REGISTRY HANDLES BECAUSE CM IS BRAINDEAD >- // >- DPRINT("NOT CLOSING THE KEY\n"); >- } >- else >- { >- ObDereferenceObject(Body); >- } >+ >+ ObDereferenceObject(Body); > > /* Return to caller */ > OBTRACE(OB_HANDLE_DEBUG, > > > >

1 0

Broken Build
by James Tabor 06 Aug '06

06 Aug '06

From http://reactos.dyndns.org:8010/ [CC] drivers\network\ndis\ndis\control.c drivers\network\ndis\ndis\control.c: In function `NdisAcquireReadWriteLock': drivers\network\ndis\ndis\control.c:63: warning: assignment makes integer from pointer without a cast make: *** [obj-i386\drivers\network\ndis\ndis\control.o] Error 1 program finished with exit code 2 From Linux, [CC] drivers/network/ndis/ndis/control.c drivers/network/ndis/ndis/control.c: In function `NdisAcquireReadWriteLock': drivers/network/ndis/ndis/control.c:63: warning: assignment makes integer from pointer without a cast make[1]: *** [obj-i386/drivers/network/ndis/ndis/control.o] Error 1 make: *** [ndis] Error 2 8^) James

2 1

Re: [ros-dev] [ros-diffs] [fireball] 23491: [AUDIT] Configuration Manager Cm part of the kernel was developed from scratch for a long time ago, and based only on legally clean information sources. After going through the code, it doesn't have any signs of questionable origin. Authorship information will be added during formatting of the code.
by Alex Ionescu 05 Aug '06

05 Aug '06

fireball(a)svn.reactos.org wrote: > Author: fireball > Date: Sun Aug 6 01:39:29 2006 > New Revision: 23491 > > URL: http://svn.reactos.org/svn/reactos?rev=23491&view=rev > Log: > [AUDIT] > Configuration Manager > > After going through the code, it doesn't have any signs of questionable origin. If it did, where are all those REGISTRY_ERROR bugchecks I should be getting in Windows NT? :P -- Best regards, Alex Ionescu Project Lead, TinyKRNL Kernel-Mode Software Design Engineer, ReactOS

1 0

Re: [ros-dev] [ros-diffs] [fireball] 23489: Fix DbgPrint / DbgPrintEx definitions to use PCCHAR instead of PCCH (recent WDK uses PCCHAR). This change fixes compiling.
by Alex Ionescu 05 Aug '06

05 Aug '06

fireball(a)svn.reactos.org wrote: > Author: fireball > Date: Sun Aug 6 00:57:36 2006 > New Revision: 23489 > > URL: http://svn.reactos.org/svn/reactos?rev=23489&view=rev > Log: > Fix DbgPrint / DbgPrintEx definitions to use PCCHAR instead of PCCH (recent WDK uses PCCHAR). > This change fixes compiling. > Um, no, this is the latest definition: ULONG __cdecl DbgPrint ( __in PCCH Format, ... ); Why do you think I had changed it in the first place?! A PCCHAR is *NOT* a const char, it's just typedef char*. So my change correctly changed the definition to use const char (Because dbgprint fails if you're not sending a const char), and also allowed building with the fixed WDKs, and you just reverted that... when you asked on Google Talk if you could fix it, I assumed you know what you were doing :) -- Best regards, Alex Ionescu Project Lead, TinyKRNL Kernel-Mode Software Design Engineer, ReactOS

1 0

WinLogon
by Alex Ionescu 05 Aug '06

05 Aug '06

Hi, I'm really excited by all the recent WinLogon work! Congratulations to Hervé for working on this. Some questions: Will the GINA be 100% compatible with NT WinLogon? I hope so. Also, there is a fully FOSS GINA project out there, I'm sure it can be useful. MSDN also has a lot of information, and I can help with some Winlogon internals, by email only please, I'm not and won't be on IRC for a while. Are we also going to support GUI-on-demand? That was largely the big problem with Winlogon, and both Thomas and I (And others) think GUI On Demand is a big hack that currently screws up more stuff then it helps... If yes, then how's winlogon going to work? As a text-mode login problem as well? Hopefully that won't hack GINA compatibility. Since this was supposed to be an SoC program, I propose that we setup a personal fund (and advertise) on the website for Hervé to get paid. I'll also try talking to Google (since our SoC GINA guy failed) to see if they'd be willing to set up an exchange. Unless Hervé disagrees, of course. Good luck to all. -- Best regards, Alex Ionescu Project Lead, TinyKRNL Kernel-Mode Software Design Engineer, ReactOS

6 7

Registry binary hives -- "problem"
by Aleksey Bragin 04 Aug '06

04 Aug '06

Hello, it looks like it is a common problem that people don't like to read commit messages :-) So I post here - starting from the introduction of cmlib patch into our tree, the binary hives became compatible with Windows XP binary hives, BUT incompatible to ReactOS binary hives made with the previous versions of ReactOS (this includes the current 0.3 release). In order to overcome this problem, simply reinstall your reactos with formatting the harddrive partition during setup. Or manually delete the contents of \system32\config directory, issue a "make install_registry" command, and don't forget to upgrade your freeldr.sys too (in case you install all that manually without bootcd). WBR, Aleksey Bragin.

1 0

Re: [ros-dev] CreateFile, typecasts and PICE loader
by Murphy, Ged (Bolton) 04 Aug '06

04 Aug '06

Felipe Villarroel wrote: > Its ok to typecast the char* to LPCWSTR? as in > file = CreateFile((LPCWSTR) SrcFileNames[i],GENERIC_READ , 0, > NULL, OPEN_EXISTING, 0, 0); ? No. If you wanted to use an ASCI where a Unicode char was expected, you would have to first convert it to Unicode using a function like MiltiByteToWideChar. However, CreateFile actually expects LPCTSTR as it's first parameter. It is then converted to LPCSTR or LPCWSTR dependant on whether you have Unicode defined. (In your case, you must have) If this is the case, and you are using TCHAR within your code, then what is the reason for the char? Maybe it's a value returned from a network read? Could it be a TCHAR? My first approach would be to see why it's a char, and not a TCHAR (or WCHAR), and check whether you can change it in the source (perhaps it's just something the PICE devs missed) Secondly, if it must remain a char, but you still want to have Unicode defined (as we mentioned, not having Unicode defined will call the ASCI version, which will be fine for your char as it's first member is LPSTR), then you could call the ASCI version of CreateFile exclusively by calling CreateFileA. > and also i have another question. Currently in the source > (main.c) we assume in line 368 that sizeof(DWORD) == > sizeof(INT) and the compiler issues a warning. Its ok to > typecast this too? > find_stab_sections(p,IMAGE_FIRST_SECTION(pNTHeaders),pNTHeader > s->FileHeader.NumberOfSections,&pStab,(PINT) > &nStabLen,&pStr,&nStabStrLen); I'm assuming from '(PINT)&nStabLen' that you have a DWORD which you are typecasting to an INT. Whilst a DWORD and an INT are of the same size, a DWORD is an unsigned long, and an INT is signed, which means typecasting from DWORD to INT could result in data loss if nStabLen is a very high value i.e. more than an INT can hold. (check your limits.h for this value, it's 2147483647 for 4 byte ints) Is making nStabLen a DWORD not an option? > Also, i'm a native spanish speaker. I would be happy to help > in anyway i could. Pop into IRC. There is always plenty for people to do ;) Ged.

1 0

CreateFile, typecasts and PICE loader
by Felipe Villarroel 04 Aug '06

04 Aug '06

Hi ReactOS devs!, currently i'm trying to get PICE compiling and working again (and learning something about the ReactOS internals in the process). Currently i have a question related to what i'm doing. To fix some warnings in the compilation of the PICE loader i have to fix the first parameter to CreateFile, because CreateFile expects the first parameter to be a LPCWSTR and its a char* instead. Its ok to typecast the char* to LPCWSTR? as in file = CreateFile((LPCWSTR) SrcFileNames[i],GENERIC_READ , 0, NULL, OPEN_EXISTING, 0, 0); ? and also i have another question. Currently in the source (main.c) we assume in line 368 that sizeof(DWORD) == sizeof(INT) and the compiler issues a warning. Its ok to typecast this too? find_stab_sections(p,IMAGE_FIRST_SECTION(pNTHeaders),pNTHeaders->FileHeader.NumberOfSections,&pStab,(PINT) &nStabLen,&pStr,&nStabStrLen); Well, thats all i have to say. Hmm, i forgot, thanks for all your hard work done in ReactOS!. I'm watching the project and the mailing list from 2000 onwards but i only speak if i need to say anything :). I always try to get people interested in this project, explaining to people what is and what its not. Also, i'm a native spanish speaker. I would be happy to help in anyway i could. thanks again for your great work, Best regards, Logan_V8 -- _______________________________________________ Check out the latest SMS services @ http://www.linuxmail.org This allows you to send and receive SMS through your mailbox. Powered by Outblaze

1 0

Re: [ros-dev] ReactOS presentations
by Murphy, Ged (Bolton) 03 Aug '06

03 Aug '06

Aleksey Bragin wrote: > We have a rather nice presentation done by Steven Edwards, I suggest we use it as a base. I've looked at Stevens in the past, but didn't think there was much in there we can use anymore. Also, whilst the theme was pretty, I think it could be made a little more professional. > Though we need something fresh and reworked too, because the Steven's one is already outdated in some parts > (ReactOS progressed quite a while since presentation were used last time). I agree, plus Stevens was aimed at a Wine audience, which also needs to be changed to a general audience. How about I put together a new base presentation and submit it to SVN once approved? An anyone interested in contributing to the presentation can then work through SVN. Ged.

3 2

ReactOS presentations
by Murphy, Ged (Bolton) 03 Aug '06

03 Aug '06

I have a few large presentations to give on ReactOS in September, and as a group we don't have any previous presentations stored. Although not a weekly event, a few of us do give presentations from time to time, which means we are probably going through the same process of compiling a presentation from scratch. So I was wondering if anyone was interested in putting our heads together and compiling a default presentation which we can use. This first default presentation should cover topics such as what ROS is and what it's goals are, and then move onto a description of the system, finalising with a short demonstration. As ROS grows, requests for us to give these sort of things will obviously grow too, including more detailed discussions on ROS internals. Therefore, as more specialised presentations are given, we could store these too, eventually offering a nice collection of presentations which we can pull out when a need arises. So, any volunteers? Ged.

4 3

Re: [ros-dev] Probelms with ZwOpenKey or RtlFormatCurrentUserKeyP ath?
by Murphy, Ged (Bolton) 02 Aug '06

02 Aug '06

Timo Kreuzer wrote: > This is the code: > > RtlFormatCurrentUserKeyPath(&CurrentUserKeyPath); > > InitializeObjectAttributes(&ObjectAttributes,&CurrentUserKeyPath,OBJ_CASE_IN SENSITIVE,NULL,NULL); > Status = ZwOpenKey(&CurrentUserKeyHandle, KEY_READ, &ObjectAttributes); > > And I always get Status == STATUS_OBJECT_NAME_NOT_FOUND What makes you sure ZwOpenKey is failing, and not one of the functions above it? You should use error checking where nessesary. Ged.

6 10

Re: [ros-dev] ReactOS presentations
by Murphy, Ged (Bolton) 02 Aug '06

02 Aug '06

WaxDragon wrote: > Maybe the first order of business would be picking a file format! Whenever I give presentations, whether it be at work, uni or a company I've never had anything other than MS PowerPoint available. I would say this is a must for a base format, and people can convert from this is need be. Ged.

3 2

Probelms with ZwOpenKey or RtlFormatCurrentUserKeyPath?
by Timo Kreuzer 02 Aug '06

02 Aug '06

Hi, I tried to read the Values of the SysColors from registry in win32k. But I get an error opening the CurrentUserKey. This is the code: RtlFormatCurrentUserKeyPath(&CurrentUserKeyPath); InitializeObjectAttributes(&ObjectAttributes,&CurrentUserKeyPath,OBJ_CASE_INSENSITIVE,NULL,NULL); Status = ZwOpenKey(&CurrentUserKeyHandle, KEY_READ, &ObjectAttributes); And I always get Status == STATUS_OBJECT_NAME_NOT_FOUND This is in trunk. Is there something wrong with my code or is there something wrong with Registry functions? Greetings, Timo

3 2

ReactOS Self Build System Crash
by James Tabor 02 Aug '06

02 Aug '06

http://reactos.dyndns.org:8010/ [PCH] obj-i386\base\applications\ibrowser\precomp.h.gch [CC] base\applications\ibrowser\utility\utility.cpp [CC] base\applications\ibrowser\utility\window.cpp [CC] base\applications\ibrowser\utility\xmlstorage.cpp base\applications\ibrowser\utility\xmlstorage.cpp:52: error: explicit qualification in declaration of `XMLStorage::XS_EMPTY' base\applications\ibrowser\utility\xmlstorage.cpp:53: error: explicit qualification in declaration of `XMLStorage::XS_TRUE' base\applications\ibrowser\utility\xmlstorage.cpp:54: error: explicit qualification in declaration of `XMLStorage::XS_FALSE' base\applications\ibrowser\utility\xmlstorage.cpp:55: error: explicit qualification in declaration of `XMLStorage::XS_INTFMT' base\applications\ibrowser\utility\xmlstorage.cpp:56: error: explicit qualification in declaration of `XMLStorage::XS_FLOATFMT' make: *** [obj-i386\base\applications\ibrowser\utility\xmlstorage.o] Error 1 Thanks, James

1 0

OpenOffice.org 2.0.3
by James Tabor 01 Aug '06

01 Aug '06

Hi, I just tested OOo 2.0.3, I get up to most of files are unzipping, then a pop up! "This package requires a newer version of the Windows Installed. Do you want to update the version of windows Installed on you system?" [Yes] [No] NO! 8^o I thought we had this fixed! BTW, I can install it under wine. James

2 1

[ros-diffs] [ekohl] 23376: Synchronize with current WINE widl 20060729.
by James Tabor 31 Jul '06

31 Jul '06

Hi, build is broken. sorry to find out like this, [CC] tools/widl/write_msft.c In file included from tools/widl/widltypes.h:25, from tools/widl/write_msft.c:48: include/reactos/wine/guiddef.h:48: warning: redefinition of `LPGUID' include/psdk/winnt.h:1545: warning: `LPGUID' previously declared here tools/widl/write_msft.c: In function `ctl2_find_name': tools/widl/write_msft.c:261: warning: implicit declaration of function `_strnicmp' [CC] tools/widl/parser.tab.c In file included from tools/widl/widltypes.h:25, from tools/widl/widl.h:24, from parser.y:36: include/reactos/wine/guiddef.h:48: warning: redefinition of `LPGUID' include/psdk/winnt.h:1545: warning: `LPGUID' previously declared here [CC] tools/widl/port/mkstemps.c [LD] output-i386/tools/widl/widl obj-i386/tools/widl/write_msft.o(.text+0x25c): In function `ctl2_find_name': : undefined reference to `_strnicmp' collect2: ld returned 1 exit status make: *** [output-i386/tools/widl/widl] Error 1 Thanks, James

3 3

Re: [ros-dev] 0.3.0 RC1 is out! (Need a wordcount)
by Murphy, Ged (Bolton) 31 Jul '06

31 Jul '06

Katarzyna Chauca wrote: > Couse MSCoder publishes in Spain, France and Germany but you > can write in english. Sorry, I thought it was an e-mag, I hadn't realise it was hard copy only. > As far as I know you have developers from all over the world > so I hope you will be interested in promote ReactOS in those > countries. As a collective group, we are certainly interested in promoting ROS in every country. > I saw one magazine from France with ReactOS so why you don't > want to cooperate with us? I assume that was written by a 3rd party author, not a ROS dev. I didn't say I don't want to cooperate, but I personally don't want to write a 10 page article for a magazine which I can't read. > I think that such proyects as ReactOS are for developers from > all countries. I agree, which is why I personally wouldn't want to write an article limited to those languages. However, this doesn't mean someone else won't, you've already had an offer from weird_w, who is a native English speaker. Have you ever considered an English release? It would open your magazine up to a much greater audience. As for the current status, you would probably have more success targeting ROS devs who's native language is one of the magazines published languages. If you popped into IRC, I could point out some of the culprits for you ;) > Will you please cooperate with us? Of course, my cooperation was never an issue, hence my replies to your past emails :) Ged.

4 4

Re: [ros-dev] 0.3.0 RC1 is out! (Need a wordcount)
by Murphy, Ged (Bolton) 31 Jul '06

31 Jul '06

Katarzyna Chauca wrote: > > Hi again > I have no confirmation if someone will write an article about > ReactOS for > MSCoder magazine. > Please let me know Is there a reason your website is only available in German, French and Spanish? I wouldn't want write an article for a magazine which followed the same pattern. Ged

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev