Ros-dev March 2005

ros-dev@reactos.org

64 participants
200 discussions

by Magnus Olsen

Hi Why not create two diffrent changelog for each release. one that contain all svn commit msg next one is what is benefit for the user. I think this is good idea. ´Then the user can read what new for them. If some want really know what we have done. Then they can read all commit msg. I think this is good idea, and will benfit alot of people.

19 years, 9 months

Re: [ros-dev] I think I know how uxtheme works...

by rlangschultz＠cox.net

I would think that ReactOs is not anywhere near being ready for themeing partially because it needs to write much more of the system software. Themeing can always be an option later. I have mentioned an alternate filesystem, and other services, but since I have not submitted code, people on the mailing list think i can not program something of the sort. I think it is great that people are wanting to understand the process of themeing but keep in mind that loading a theme may cut down on the resources available to the opertating system or may interfere with someone elses environment. > > From: Jonathan Wilson <jonwil(a)tpgi.com.au> > Date: 2005/03/23 Wed PM 09:19:23 EST > To: wine-devel(a)winehq.org, ros-dev(a)reactos.com > Subject: [ros-dev] I think I know how uxtheme works... > > What I strongly suspect happens is this: > 1.The themes service is always loaded and running and holds the theme data > (and it contains details of which .msstyles file to use) > 2.At some point (either at startup if the changes are global or when an app > loads if the changes are app specific, I cant find where this bit happens > but I suspect the themes service does this) control passes to ordinal 34 in > uxtheme.dll (aka ThemeHooksInstall acording to uxtheme.pdb). This function > calls an undocumented function in user32 called RegisterUserApiHooks (which > appears to be taylor made for uxtheme to do what it needs to do). > The function hooks: > GetScrollInfo > SetScrollInfo > EnableScrollBar > SetWindowRgn > DefWindowProcW > DefWindowProcA > PreWndProc (probobly stuff that happens internally before the window > procedure gets called) > PostWndProc (probobly stuff that happens internally after the window > procedure gets called) > PreDefDlgProc (probobly connected to dialog boxes) > PostDefDlgProc (probobly connected to dialog boxes) > GetSystemMetrics > SystemParametersInfoA > SystemParametersInfoW > DrawFrameControl > DrawCaption > MDIRedrawFrame (probobly related to MDI frame windows) > This is what causes all apps (including non-theme-aware ones) to get themed > non-client areas (window borders etc) > 3.Apps that are theme aware have a manifest, load comctl32.dll 6.0 and > probobly have to call InitCommonControlsEx (although I think some of the > code in the dllmain for comctl32.dll 6.0 may also end up calling > InitCommonControlsEx). This causes new versions of the stock classes > (button, list box, edit, combo box etc etc etc) to be created and > registered. A cursory examination of some of these classes shows that they > dont seem to "pull code" from the stock implementation in user32.dll (i.e. > anything they dont themselves handle goes back to DefWindowProc). In > particular, it doesnt appear as though they have any knowledge of the > classes or window procedures contained in user32.dll. > then 4.Apps that need to do something extra call into functions exported by > uxtheme.dll to do whatever they need to do. > > user32.dll seems to have no knowledge whatsoever about themeing and > uxtheme. All that user32 has is RegisterUserApiHooks (and the matching > UnregisterUserApiHooks) that uxtheme uses to hook into user32.dll and do stuff. > > Exactly how the theme service and theme engine works "under the hood" > doesnt matter. > But for ReactOS and WINE purposes, I suggest we implement the following: > 1.A function similar to RegisterUserApiHooks/UnregisterUserApiHooks (either > reverse engineer the MS function or write our own). This will allow uxtheme > to hook into the global drawing for things like window borders without > user32 needing to care about uxtheme and what uxtheme does (just like how > MS hooks into user32 that way) > 2.Whatver code is necessary to get the hooks installed right so that all > apps get the "global" theming like on real windows > 3.Support to read the manifest and load a new comctl32.dll that would be > like the version 6 from microsoft (and would contain complete theme-aware > implementations of the stock controls just like MS comctl32.dll 6.0 does) > and 4.All the needed uxtheme exports to make stuff run > > This would be the same way Microsoft does things. > User32.dll would have no idea whatsoever about uxtheme and theming > All apps would get non-client-area themeing like on windows. > And only theme aware apps would get themed controls etc (the rest would get > "stock" windows controls) > > Oh and btw, if this "reverse engineering" is not "clean room" enough for > WINE and ReactOS, let me know and I will stop posting it :) > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev >

19 years, 9 months

Re: Colinux crash : Lock the kernel - Debug traces for Bug512]

by Hartmut Birr

Hi, with my last changes (r14296), coLinux does start and does mount the root partition. It exist an second problem. The coLinux window is only shown for a very short time. I'm not so familiar with the gdi, user and win32k code. I cannot fix the second problem. - Hartmut

19 years, 9 months

OpenOffice.Org 2.0 beta's installer causes kernel panic

by Wierd Wierd

Steven asked me to do a quick trial to see if any of the recent fixes in ROS had fixed this problem with the OOo 2.0 beta installer, then asked me to provide this debug dump. *************************** Used memory 131072Kb (mm/mminit.c:375) Kernel Stack Limits. InitTop = 0x800be000, Init = 0x800bb000 (mm/virtual.c:214) FIXME: MEMORY_AREA_SYSTEM case incomplete (or possibly wrong) for NtQueryVirtualMemory() (ke/bug.c:56) Found Bugcheck Resource Data! (ke/bug.c:67) Got Pointer to Bugcheck Resource Data! (ke/clock.c:80) KiInitializeSystemClock() (ke/clock.c:99) Finished KiInitializeSystemClock() (ex/timer.c:232) ExpInitializeTimerImplementation() (io/pnproot.c:676) DeviceID: Root\Ne2000 PDO 805451f8 (io/pnproot.c:689) InstanceID: 0000 PDO 805451f8 (io/pnproot.c:676) DeviceID: Root\PCI PDO 80545300 (io/pnproot.c:689) InstanceID: 0000 PDO 80545300 (io/pnproot.c:676) DeviceID: Root\LEGACY_UNKNOWN PDO 80545448 (io/pnproot.c:689) InstanceID: 0000 PDO 80545448 DriverBase for \SystemRoot\system32\drivers\pci.sys: 9cdaf000 Peripheral Component Interconnect Bus Driver DriverBase for acpi.sys: 9cdb7000 Advanced Configuration and Power Interface Bus Driver ACPI: System firmware supports: +------------------------------------------------------------ | Sx states: +S0 -S1 -S2 -S3 -S4 +S5 +------------------------------------------------------------ Sleep Button: found DriverBase for scsiport.sys: 9cde6000 DriverBase for atapi.sys: 9cdf1000 DriverBase for class2.sys: 9cdfb000 DriverBase for disk.sys: 9ce04000 DriverBase for vfatfs.sys: 9ce0c000 DriverBase for bootvid.sys: 9ce1f000 DriverBase for ndis.sys: 9ce3e000 DriverBase for \SystemRoot\system32\drivers\pcnet.sys: 9ce66000 DriverBase for \SystemRoot\system32\drivers\vmx_svga.sys: 9cea2000 DriverBase for \SystemRoot\system32\drivers\VIDEOPRT.SYS: 9cebe000 DriverBase for \SystemRoot\system32\drivers\floppy.sys: 9e0db000 DriverBase for \SystemRoot\system32\drivers\cdrom.sys: 9e0fb000 DriverBase for \SystemRoot\system32\drivers\fs_rec.sys: 9e10a000 DriverBase for \SystemRoot\system32\drivers\beep.sys: 9e118000 DriverBase for \SystemRoot\system32\drivers\null.sys: 9e126000 DriverBase for \SystemRoot\system32\drivers\psaux.sys: 9e13e000 DriverBase for \SystemRoot\system32\drivers\keyboard.sys: 9e157000 DriverBase for \SystemRoot\system32\drivers\mouclass.sys: 9e167000 DriverBase for \SystemRoot\system32\drivers\blue.sys: 9e175000 DriverBase for \SystemRoot\system32\drivers\msfs.sys: 9e18b000 DriverBase for \SystemRoot\system32\drivers\npfs.sys: 9e1a1000 (mm/virtual.c:235) FIXME: MEMORY_AREA_KERNEL_STACK case incomplete (or possibly wrong) for NtQueryVirtualMemory() DriverBase for \??\C:\ReactOS\system32\win32k.sys: 9e4fe000 DriverBase for \??\C:\ReactOS\system32\freetype.dll: 9e5e6000 DriverBase for \SystemRoot\System32\kbdus.dll: 9e66b000 (ntuser/desktop.c:574) IntShellHookNotify: No desktop! (ntuser/desktop.c:574) IntShellHookNotify: No desktop! (ntuser/desktop.c:574) IntShellHookNotify: No desktop! WL-Status: ReactOS is starting up... DriverBase for \SystemRoot\system32\drivers\tcpip.sys: 9eaa2000 DriverBase for \SystemRoot\system32\drivers\afd.sys: 9eadf000 (umpnpmgr.c:160) Device arrival event: HTREE\Root\0 (umpnpmgr.c:160) Device arrival event: Root\LEGACY_UNKNOWN\0000 (umpnpmgr.c:160) Device arrival event: Root\PCI\0000 (umpnpmgr.c:160) Device arrival event: Root\Ne2000\0000 (umpnpmgr.c:160) Device arrival event: Root\LEGACY_UNKNOWN\0000 (umpnpmgr.c:160) Device arrival event: Root\LEGACY_UNKNOWN\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_1274&DEV_1371&SUBSYS_13711274&REV_02\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_1022&DEV_2000&SUBSYS_20001022&REV_10\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_8086&DEV_7113&SUBSYS_197615AD&REV_08\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_8086&DEV_7112&SUBSYS_197615AD&REV_00\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_8086&DEV_7111&SUBSYS_197615AD&REV_01\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_8086&DEV_7110&SUBSYS_197615AD&REV_08\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_8086&DEV_7191&SUBSYS_00000000&REV_01\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_8086&DEV_7190&SUBSYS_197615AD&REV_01\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0A03\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0C02\31 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0200\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0001\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0100\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0B00\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0800\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0303\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0F13\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0A05\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0400\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0501\1 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0501\2 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0700\0000 LAN WORKER BUSY 9eac0380 8055f590 LAN WORKER BUSY 9eac0380 8055f590 LAN WORKER BUSY 9eac0380 8055f590 LAN WORKER BUSY 9eac0380 8055f590 LAN WORKER BUSY 9eac0380 8055ec28 LAN WORKER BUSY 9eac0380 8080be88 DriverBase for \SystemRoot\System32\vmx_fb.DLL: 9ec49000 (misc/driver.c:244) Unsupported DDI function 0x6 (misc/driver.c:244) Unsupported DDI function 0x47 (misc/driver.c:244) Unsupported DDI function 0x46 (misc/driver.c:244) Unsupported DDI function 0x45 FIXME: CopyImage doesn't support IMAGE_ICON correctly! (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find mxdMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find auxMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find mxdMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find midMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find modMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find widMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find wodMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find auxMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find mxdMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find midMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find widMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find wodMessage LAN WORKER BUSY 9eac0380 808a8798 LAN WORKER BUSY 9eac0380 808a8840 LAN WORKER BUSY 9eac0380 808a88e8 LAN WORKER BUSY 9eac0380 805bb5a0 LAN WORKER BUSY 9eac0380 806ef608 LAN WORKER BUSY 9eac0380 806ef648 (ntuser/class.c:114) Failed to lookup class atom! LAN WORKER BUSY 9eac0380 805c6138 LAN WORKER BUSY 9eac0380 805c7f80 LAN WORKER BUSY 9eac0380 805c8028 LAN WORKER BUSY 9eac0380 8069d090 LAN WORKER BUSY 9eac0380 8069d138 LAN WORKER BUSY 9eac0380 805c6138 Using shell hooks for notification of shell events. (ntuser/hook.c:504) Not implemented: HookId 3 Global TRUE SHELLHOOK 1 SHELLHOOK 4 SHELLHOOK 1 LAN WORKER BUSY 9eac0380 806fe7a8 SHELLHOOK 4 SHELLHOOK 4 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 806f7988 LAN WORKER BUSY 9eac0380 806f7a30 LAN WORKER BUSY 9eac0380 806f7ad8 LAN WORKER BUSY 9eac0380 806f7b80 LAN WORKER BUSY 9eac0380 806f7c28 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 806f7988 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 806f7ad0 SHELLHOOK 4 LAN WORKER BUSY 9eac0380 806f7988 LAN WORKER BUSY 9eac0380 806f7ad8 LAN WORKER BUSY 9eac0380 806fac18 LAN WORKER BUSY 9eac0380 806facc0 (ntuser/painting.c:619) PAINTING BUG: Thread marked as containing dirty windows, but no dirty windows found! LAN WORKER BUSY 9eac0380 806fac18 LAN WORKER BUSY 9eac0380 806fff60 LAN WORKER BUSY 9eac0380 806fac18 LAN WORKER BUSY 9eac0380 806fac18 LAN WORKER BUSY 9eac0380 806facc0 SHELLHOOK 1 SHELLHOOK 1 SHELLHOOK 4 LAN WORKER BUSY 9eac0380 8069aa98 LAN WORKER BUSY 9eac0380 8069ab40 LAN WORKER BUSY 9eac0380 8069aa98 LAN WORKER BUSY 9eac0380 8069aa98 LAN WORKER BUSY 9eac0380 8069aa98 LAN WORKER BUSY 9eac0380 806f8b10 LAN WORKER BUSY 9eac0380 8069aa98 LAN WORKER BUSY 9eac0380 808aad80 LAN WORKER BUSY 9eac0380 808aad80 LAN WORKER BUSY 9eac0380 808aad80 LAN WORKER BUSY 9eac0380 808aad80 LAN WORKER BUSY 9eac0380 808aad80 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5b60 LAN WORKER BUSY 9eac0380 808b5c08 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5b60 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5b60 LAN WORKER BUSY 9eac0380 808b5c08 LAN WORKER BUSY 9eac0380 808b5cb0 LAN WORKER BUSY 9eac0380 808b5d58 LAN WORKER BUSY 9eac0380 808b5e00 LAN WORKER BUSY 9eac0380 808b5ea8 LAN WORKER BUSY 9eac0380 808b5f50 LAN WORKER BUSY 9eac0380 808ac070 LAN WORKER BUSY 9eac0380 808ac118 LAN WORKER BUSY 9eac0380 808ac1c0 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5b60 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5b60 LAN WORKER BUSY 9eac0380 808b5c08 LAN WORKER BUSY 9eac0380 808b5cb0 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5b60 LAN WORKER BUSY 9eac0380 808b5c08 LAN WORKER BUSY 9eac0380 808b5cb0 LAN WORKER BUSY 9eac0380 808b5d58 (api/handle.c:71) CsrGetObject returning invalid handle (NTDLL:ldr/utils.c:2097) Relocating (777c0000 -> 750000) C:\ReactOS\system32\winmm.dll FIXME: CopyImage doesn't support IMAGE_ICON correctly! (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find mxdMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find auxMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find mxdMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find midMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find modMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find widMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find wodMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find auxMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find mxdMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find midMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find widMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find wodMessage (msi.c:390:MsiInstallProductW) L"openofficeorg1979.msi" (null) (action.c:1413:ACTION_PerformUIAction) UNHANDLED MSI ACTION L"SetupInitialization" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"FindRelatedProducts" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"ValidateProductID" LAN WORKER BUSY 9eac0380 80900b28 LAN WORKER BUSY 9eac0380 80900bd0 LAN WORKER BUSY 9eac0380 80907360 LAN WORKER BUSY 9eac0380 80907408 LAN WORKER BUSY 9eac0380 809074b0 LAN WORKER BUSY 9eac0380 80907558 LAN WORKER BUSY 9eac0380 80907600 LAN WORKER BUSY 9eac0380 80907280 LAN WORKER BUSY 9eac0380 80907440 LAN WORKER BUSY 9eac0380 80907558 LAN WORKER BUSY 9eac0380 80907600 LAN WORKER BUSY 9eac0380 80908908 LAN WORKER BUSY 9eac0380 80909628 LAN WORKER BUSY 9eac0380 8090ad58 LAN WORKER BUSY 9eac0380 8090b298 LAN WORKER BUSY 9eac0380 8090b420 LAN WORKER BUSY 9eac0380 8090b230 LAN WORKER BUSY 9eac0380 8090b500 LAN WORKER BUSY 9eac0380 8090b5a8 LAN WORKER BUSY 9eac0380 8090b6d0 LAN WORKER BUSY 9eac0380 8090b778 (action.c:1823:load_file) Unfound Component L"g_f_registry_spool_oo_td_internalgraphics_filters_xcu__share_registry_modules_o_"... (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"IsolateComponents" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"MigrateFeatureStates" (action.c:1413:ACTION_PerformUIAction) UNHANDLED MSI ACTION L"InstallWelcome" (action.c:1413:ACTION_PerformUIAction) UNHANDLED MSI ACTION L"SetupProgress" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveExistingProducts" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"AllocateRegistrySpace" (cm/ntfunc.c:251) NtCreateKey() doesn't create trees! (found '\' in remaining path: "\Installer\Components"!) LAN WORKER BUSY 9eac0380 80918ac0 LAN WORKER BUSY 9eac0380 80918e58 LAN WORKER BUSY 9eac0380 8090a070 LAN WORKER BUSY 9eac0380 8090a210 LAN WORKER BUSY 9eac0380 8090a5b0 LAN WORKER BUSY 9eac0380 8090b118 LAN WORKER BUSY 9eac0380 80918ac0 LAN WORKER BUSY 9eac0380 809122d0 LAN WORKER BUSY 9eac0380 80918e58 LAN WORKER BUSY 9eac0380 8090a210 LAN WORKER BUSY 9eac0380 8090a5b0 LAN WORKER BUSY 9eac0380 8090b118 LAN WORKER BUSY 9eac0380 80910138 LAN WORKER BUSY 9eac0380 809122d0 LAN WORKER BUSY 9eac0380 80916578 (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnpublishComponents" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"MsiUnpublishAssemblies" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnpublishFeatures" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"StopServices" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"DeleteServices" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterComPlus" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"SelfUnregModules" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterTypeLibraries" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveODBC" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterFonts" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveRegistryValues" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterClassInfo" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterExtensionInfo" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterProgIdInfo" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterMIMEInfo" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveIniValues" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveShortcuts" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveEnvironmentStrings" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveDuplicateFiles" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveFiles" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveFolders" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"MoveFiles" LAN WORKER BUSY 9eac0380 8094b8b8 LAN WORKER BUSY 9eac0380 8098c5e0 LAN WORKER BUSY 9eac0380 8098ccd0 LAN WORKER BUSY 9eac0380 8098cd78 LAN WORKER BUSY 9eac0380 8099c9e0 LAN WORKER BUSY 9eac0380 809a45b0 LAN WORKER BUSY 9eac0380 8099c9e0 LAN WORKER BUSY 9eac0380 8099c9e0 LAN WORKER BUSY 9eac0380 809aa588 LAN WORKER BUSY 9eac0380 809aa630 LAN WORKER BUSY 9eac0380 809aa6d8 LAN WORKER BUSY 9eac0380 809aa780 LAN WORKER BUSY 9eac0380 809aa828 LAN WORKER BUSY 9eac0380 809aa8d0 LAN WORKER BUSY 9eac0380 809aa978 LAN WORKER BUSY 9eac0380 809b7478 LAN WORKER BUSY 9eac0380 809b7520 LAN WORKER BUSY 9eac0380 809b75c8 LAN WORKER BUSY 9eac0380 809b7670 LAN WORKER BUSY 9eac0380 809beb88 (ntuser/painting.c:619) PAINTING BUG: Thread marked as containing dirty windows, but no dirty windows found! LAN WORKER BUSY 9eac0380 809ca050 LAN WORKER BUSY 9eac0380 809c8aa8 LAN WORKER BUSY 9eac0380 809c7900 LAN WORKER BUSY 9eac0380 809cd280 LAN WORKER BUSY 9eac0380 809cd328 LAN WORKER BUSY 9eac0380 809cd3d0 LAN WORKER BUSY 9eac0380 809ef990 LAN WORKER BUSY 9eac0380 809f0fd0 LAN WORKER BUSY 9eac0380 809f2850 LAN WORKER BUSY 9eac0380 809ef990 LAN WORKER BUSY 9eac0380 809f0fd0 LAN WORKER BUSY 9eac0380 809f2850 LAN WORKER BUSY 9eac0380 809f2ca8 LAN WORKER BUSY 9eac0380 809f2850 LAN WORKER BUSY 9eac0380 809f2ca8 LAN WORKER BUSY 9eac0380 809fcc50 LAN WORKER BUSY 9eac0380 809fccf8 LAN WORKER BUSY 9eac0380 809f2850 LAN WORKER BUSY 9eac0380 809f2ca8 LAN WORKER BUSY 9eac0380 809feb50 LAN WORKER BUSY 9eac0380 809febf8 LAN WORKER BUSY 9eac0380 809feca0 LAN WORKER BUSY 9eac0380 809fed48 LAN WORKER BUSY 9eac0380 809fedf0 LAN WORKER BUSY 9eac0380 809fee98 LAN WORKER BUSY 9eac0380 809fef40 LAN WORKER BUSY 9eac0380 809fefe8 LAN WORKER BUSY 9eac0380 809ff090 LAN WORKER BUSY 9eac0380 809ff138 LAN WORKER BUSY 9eac0380 809ff1e0 LAN WORKER BUSY 9eac0380 809ff288 LAN WORKER BUSY 9eac0380 809f2850 LAN WORKER BUSY 9eac0380 80a07570 LAN WORKER BUSY 9eac0380 80a07618 LAN WORKER BUSY 9eac0380 80a076c0 LAN WORKER BUSY 9eac0380 80a07768 LAN WORKER BUSY 9eac0380 80a07810 LAN WORKER BUSY 9eac0380 80a078b8 LAN WORKER BUSY 9eac0380 80a14f10 LAN WORKER BUSY 9eac0380 80a14fb8 LAN WORKER BUSY 9eac0380 80a15060 LAN WORKER BUSY 9eac0380 80a206b8 LAN WORKER BUSY 9eac0380 80a20a88 LAN WORKER BUSY 9eac0380 80a20b30 LAN WORKER BUSY 9eac0380 80a23e50 LAN WORKER BUSY 9eac0380 80a23ef8 LAN WORKER BUSY 9eac0380 80a23fa0 LAN WORKER BUSY 9eac0380 807a42a8 LAN WORKER BUSY 9eac0380 80769f10 LAN WORKER BUSY 9eac0380 80784578 LAN WORKER BUSY 9eac0380 808b9ec0 LAN WORKER BUSY 9eac0380 80541698 LAN WORKER BUSY 9eac0380 80a44ff0 LAN WORKER BUSY 9eac0380 80a45098 LAN WORKER BUSY 9eac0380 805b6538 LAN WORKER BUSY 9eac0380 805b6578 LAN WORKER BUSY 9eac0380 806ab958 LAN WORKER BUSY 9eac0380 806ab998 LAN WORKER BUSY 9eac0380 805cb660 LAN WORKER BUSY 9eac0380 805cb708 Freeing mapped page (0x5ff4000 count 1) KeBugCheck at mm/freelist.c:749 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The bug code is undefined. Please use an existing code instead. Technical information: *** STOP: 0x00000000 (0x00000000,0x00000000,0x00000000,0x00000000) Frames: <ntoskrnl.exe: a311> <ntoskrnl.exe: a337> <ntoskrnl.exe: 43a03> <ntoskrnl.exe: 4049e> <ntoskrnl.exe: 4f02e> <ntoskrnl.exe: 4c802> <ntoskrnl.exe: 127f7> <ntoskrnl.exe: 405ca> <ntoskrnl.exe: 40852> <ntoskrnl.exe: 1217b> <ntoskrnl.exe: 12442> <ntoskrnl.exe: 10151> <ntoskrnl.exe: 10818> <vfatfs.sys: 972c> <vfatfs.sys: ad6f> <ntoskrnl.exe: 32975> <ntoskrnl.exe: 32991> <ntoskrnl.exe: 3830b> <ntoskrnl.exe: 318b> <7FFE0304> ******************************** Enjoy. __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

19 years, 9 months

svn.reactos.com disturbances

by Casper Hornstrup

On 24-28 of March, between 05:00 and 08:00 CET, svn.reactos.com may be unavailable for a duration of up to 1 hour each day due to maintenance work at the hosting center. Sorry for the inconvenience, Casper

19 years, 9 months

Re: registry TODO

by Steven Edwards

Hi, --- Boaz Harrosh <boaz(a)hishome.net> wrote: > How is ReactOS's current (future) system? I think ReactOS's registry is binary compatible with NT4. It and the windows 2000 format was documented/reversed for samba and the linux ntchpwd bootdisk projects. If I remeber right Eirc Kohl offered to release some of his work to Wine for the binary format so you might want to ping him about the implementation details. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

19 years, 9 months

Re: [ros-dev] Re: [ros-svn] [ea] 14244: SM: init system reading the registry

by Steven Edwards

Hi Emanuele, --- ea <ea(a)iol.it> wrote: > I tested twice fresh builds before committing and the 3rd time right now > with local repository at revision 14248. For me it compiles, installs > and boots correctly (qemu 0.6.1). Can you tell me more about the lock? I > can't rollback right now because I am going out to work in a few > seconds. Feel free to restore subsys/csrss and subsys/smss to 14243 if > you feel this is a blocking bug for you. Sorry, its not your problem. I rm -fr'd my reactos tree and did a clean CVS checkout and things are cool now. I guess the current build system left some crap around that caused problems. Nice work btw on the smss stuff. How much trouble do you think it would be possible to make a native mode console application in smss like the Windows recovery console? I have been thinking about doing this for the boot CD for a while but would like to make it more powerful than the Windows recovery console. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

19 years, 9 months

Re: registry TODO

by Boaz Harrosh

James Hawkins wrote: >>Nobody's working on it, so it won't be supported until someone cares >>enough to do it. I encouraged a few people to start working on it but >>nobody did, so taking out the existing support is a way to provide >>more encouragement. If that's not enough then the feature simply won't >>be supported anymore. >> >> I started toying around the current and old code, Gathering knowledge and ideas. What I think of doing is: keep the boot registry as is (more less). Put in on wine/wine/config a key system that enables a "plugin" system of registry loaders/savers. Builtin plugins are current format and Windows binary format. Other formats could be easily implemented; candidates could be XML, MySQL etc... The system I thought of would also save the hives and sub trees, to the files/plugins it was loaded from. Each plugin could also implement a write behind so Data don't get lost in case of a crash or power lost. Good point with the on demand-loading/cache of keys. It should be done this way. So in summary: 1. Implement a Memory registry with plugin drivers and mount semantics. This driver goes here, that driver mounts there. 2. Implement 2 basic drivers: Wine builtin format, Windows binary format. 3. Enable dynamic load of external drivers. The Initial registry system is always loaded from system.reg builtin format which is also the "fstab" file of the registry. At minimum every thing is exactly like now one (two) files builtin format, and that's it. At the maximum it can be highly object oriented with per user, per application, per group management. Please tell me what you think. Any libraries I should look into? How is ReactOS's current (future) system? Free Life Boaz

19 years, 9 months

Re: [ros-svn] [ea] 14244: SM: init system reading the registry

by Steven Edwards

Hi, --- ea(a)svn.reactos.com wrote: > trunk/reactos/subsys/smss/initss.c "Debug Windows" fails to be registered causing it to not boot the Win32 subsystem and hard lock. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250

19 years, 9 months

RC1 of ros 0.2.6 is out

by Robert Köpferl

Hi, I just finished uploading the RC1 to sf.net The last build worked quite well, but improvements to the branch are welcome. If no major issues occour, we may perhaps advance to Release as next step, already. BTW: RosApps is from 2003, still. They are already in the installation, aren't they? So should they be hidden?

19 years, 9 months

← Newer
1
2
3
4
5
6
7
8
...
20
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev March 2005