Ros-dev

ros-dev@reactos.org

5788 discussions

by James Tabor

Rev 24339 with gcc 3.4.2, bin utils 2.15.94 [COPY] reactos/system32/win32k.sys [CC] tools/mkhive/binhive.c include/psdk/intrin.h: In function `_InterlockedCompareExchange8': include/psdk/intrin.h:193: error: output operand constraint lacks `=' include/psdk/intrin.h: In function `_InterlockedCompareExchange16': include/psdk/intrin.h:200: error: output operand constraint lacks `=' include/psdk/intrin.h: In function `_InterlockedCompareExchange': include/psdk/intrin.h:207: error: output operand constraint lacks `=' include/psdk/intrin.h: In function `_InterlockedCompareExchange64': include/psdk/intrin.h:236: error: output operand constraint lacks `=' include/psdk/intrin.h: In function `_InterlockedCompareExchangePointer': include/psdk/intrin.h:250: error: output operand constraint lacks `=' include/psdk/intrin.h: In function `_InterlockedExchange': include/psdk/intrin.h:257: error: output operand constraint lacks `=' include/psdk/intrin.h: In function `_InterlockedExchangePointer': include/psdk/intrin.h:264: error: output operand constraint lacks `=' include/psdk/intrin.h: In function `_InterlockedExchangeAdd': include/psdk/intrin.h:271: error: undefined named operand 'retval' include/psdk/intrin.h:271: error: undefined named operand 'Addend' include/psdk/intrin.h:271: error: output operand constraint lacks `=' include/psdk/intrin.h: In function `__writecr0': include/psdk/intrin.h:1009: error: undefined named operand 'value' include/psdk/intrin.h: In function `__writecr3': include/psdk/intrin.h:1014: error: undefined named operand 'value' include/psdk/intrin.h: In function `__writecr4': include/psdk/intrin.h:1019: error: undefined named operand 'value' make: *** [obj-i386/tools/mkhive/binhive.o] Error 1

17 years, 12 months

Actual NTLDR boot screenshot

by Alex Ionescu

Sometimes pictures speak better then commit messages, so here's the current boot status: http://www.tinykrnl.org/ros_by_ntldr.png It fails because our Memory Manager early-boot initialization depends on some freeldr information. If I can/have time, I'll try to make it not depend on them, and/or use NTLDR structures instead. Anyways, serial debug printing works and the GDT, IDT, TSS, KPCR are all setup, so this can now be used as a good tool for blackboxing ntldr. -- Best regards, Alex Ionescu Project Lead, TinyKRNL Kernel-Mode Software Design Engineer, ReactOS

17 years, 12 months

Working trunk?

by Alex Ionescu

Hi, I took a break from the project hoping any regressions I might've caused could be found/fixed... isntead, I now find myself with an OS that won't recognize my mouse/keyboard. I've tried rebooting it to re-start 2nd stage (which used to work before), but all this does is gradually damage the registry more and more, either leading to aSSERTs or freeldr codepage error. This is with a 100% clean trunk on QEMU 0.8.2. -- Best regards, Alex Ionescu Project Lead, TinyKRNL Kernel-Mode Software Design Engineer, ReactOS

17 years, 12 months

Time date control panel applet bug and DrawStatusText issues

by Felipe Villarroel

Hello list!, i have two questions that i hope that someone of you could answer. The first one: - Should RegOpenKeyExW() do a SetLastError() or it just return an error code? I ask this because in the timedate control panel applet, GetSyncSetting() reads a key from the registry using that function and if it fails it calls the function GetError() that calls FormatMessage() using GetLastError() as an argument. For some reason in my computer this call fails and i receive an window that says "ERROR_INVALID_WINDOW_HANDLE" that obviously is not the right error code. This bug could be reproduced by double clicking in the Hour located in the right corner of the start menu bar. Next you click the Internet Time tab and you should receive the error. To fix this i can think of two possibilities: - Modify RegOpenKeyExW() to do a SetLastError() if this fails to set a right code for GetLastError(), or - Modify the GetError() function in the timedate control panel applet I don't know which is the right way to fix this. Finally in my opinion, if an error occurs in this situation i think that no message should appear because i think that is not too bad if this key isn't present. And the second question follows... - I have written a program that displays a Status bar using the DrawStatusText() function. In Windows it is working pretty well but in ReactOS it doesnt. DrawStatusText() in ReactOS doesnt draw a background when calling this function thus my status window draws over itself each time i receive a WM_PAINT message. So its clear that in windows DrawStatusText() draws a background before painting the text, but in ReactOS it doesnt. Currently i have hacked the DrawStatusText() function to draw a background like this: void WINAPI DrawStatusTextW (HDC hdc, LPRECT lprc, LPCWSTR text, UINT style) { RECT r = *lprc; UINT border = BDR_SUNKENOUTER; HBRUSH hBkBrush, hOldBrush; if (style & SBT_POPOUT) border = BDR_RAISEDOUTER; else if (style & SBT_NOBORDERS) border = 0; DrawEdge (hdc, lprc, border, BF_RECT|BF_ADJUST); /* now draw text */ if (text) { int oldbkmode = SetBkMode (hdc, TRANSPARENT); UINT align = DT_LEFT; if (*text == L'\t') { text++; align = DT_CENTER; if (*text == L'\t') { text++; align = DT_RIGHT; } } r.left += 3; if (style & SBT_RTLREADING) FIXME("Unsupported RTL style!\n"); // yep this fixed the problem, but i don't know what the // right color it is hBkBrush = GetSysColorBrush(GetSysColor(COLOR_BTNFACE)); hOldBrush = SelectObject(hdc, hBkBrush); FillRect(hdc, lprc, hBkBrush); DrawTextW (hdc, text, -1, lprc, align|DT_VCENTER|DT_SINGLELINE|DT_NOPREFIX); SelectObject(hdc, hOldBrush); SetBkMode(hdc, oldbkmode); } } Attached i send the code that shows this "bug" and a precompiled binary. Also i have tested this program under WINE with the same results (0.9.x i think). Thats all, Best regards, Felipe Villarroel -- _______________________________________________ Get your free email from http://www.linuxmail.org Powered by Outblaze

17 years, 12 months

Re: [ros-dev] [ros-diffs] [hpoussin] 24286: Support mount manager in disk.sys

by Alex Ionescu

hpoussin(a)svn.reactos.org wrote: > Author: hpoussin > Date: Thu Sep 28 20:33:12 2006 > New Revision: 24286 > > URL: http://svn.reactos.org/svn/reactos?rev=24286&view=rev > Log: > Support mount manager in disk.sys > > Modified: If you're going to add this kind of support, I'd appreciate it if you took a look at TinyKRNL/WDK to see how this should be done. FTDISK is responsible for all the code you've added, not disk.sys, and if we're going to implement NT5+ Storage stack features on top of an NT4 driver, this will mean either one of these two things: 1) A crappy "ROS" stack that's incompatible with anything NT offers (and the storage stack is heavily documented in NT, so we're at a big loss if we do this). 2) Someone will have to eventually re-write even more code to make it compatible. I suggest you work on implementing an XP/2K3 style classpnp driver first. The WDK and TinyKRNL have sample source code (non-reversed), and there's 50 pages of documentation on it. Once that works, a new disk.sys can be written (same information as above is available). Then ftdisk should follow. It handles all Fault-Tolerance stuff, but about 6000 lines of it are responsible for the glue layer between the storage stack. TinyKRNL has just finished implementing it, so the information and documentation located there should be helpful (using TinyKRNL documentation and code for learning purposes is fully in-line with our IP policy and the whole point of the project). Then partmgr, mountmgr can be written. These are also implemented in TinyKRNL completely. (Except GPT support). Finally, some parts of the kernel's IoMgr needs to be changed in the method in which it sets up disk letters, and kernel32 needs some new code (which Filip has on his disk). -- Best regards, Alex Ionescu Project Lead, TinyKRNL Kernel-Mode Software Design Engineer, ReactOS

17 years, 12 months

MSCoder Magazine

by Katarzyna Chauca

Dear Friends Here I am again. I would like to prepare the CD with ReactOS live. But I need a description - how to instal, why use it, how use it, what works on it etc for our readers. Please let me know if someone can help us and write it. Best Regards Kate www.mscoder.org/es --- Katarzyna Chauca Market Manager Editorial Software 0048228871457

18 years

test

by Magnus Olsen

Hi I have not resive any mail for 48hours from reactos mailing list, so I am trying see if they are working or not

18 years

RE : Usb Fault

by James Tabor

Hi, Sylvain Petreolle wrote: > Hi James, > why dont you try the new driver ? > (drivers/usb/nt4compat/usbdriver) I guess I can try it. I moved the drivers out of the directory and the system just sit there doing nothing. Thanks, James

18 years

Usb Fault

by James Tabor

Hi! Happy to boot again! Thank you Arty and Hervé! So, USB fault with real hardware. r24264 in second stage boot. It lockup on first stage and I did not get the setup gui. (dll/win32/newdev/newdev.c:736) Installing PCI-ISA bridge (PCI\VEN_1106&DEV_3177 &SUBSYS_31771106&REV_00\1&f103bba4&11) (dll/win32/newdev/newdev.c:525) Installing driver (Generic system devices): Standard PCI to ISA bridge (dll/win32/setupapi/queue.c:1456) copy error 2 L"C:\\ReactOS\\inf\\isapnp.sys" - > L"C:\\ReactOS\\System32\\drivers\\isapnp.sys" (ntoskrnl/ps/thread.c:496) FIX PS SDs!! (dll/win32/newdev/newdev.c:736) Installing USB controller (PCI\VEN_1106&DEV_3104 &SUBSYS_73401462&REV_82\1&f103bba4&70) (dll/win32/newdev/newdev.c:525) Installing driver (Generic USB devices): EHCI USB controller (dll/win32/setupapi/queue.c:1456) copy error 2 L"C:\\ReactOS\\inf\\usbport.sys" -> L"C:\\ReactOS\\System32\\drivers\\usbport.sys" (dll/win32/setupapi/queue.c:1456) copy error 2 L"C:\\ReactOS\\inf\\usbehci.sys" -> L"C:\\ReactOS\\System32\\drivers\\usbehci.sys" (ntoskrnl/ps/thread.c:496) FIX PS SDs!! (ntoskrnl/ps/thread.c:496) FIX PS SDs!! (ntoskrnl/ps/thread.c:496) FIX PS SDs!! (dll/win32/rpcrt4/ndr_marshall.c:928) unhandled data type=09 (ntoskrnl/ps/thread.c:496) FIX PS SDs!! (ntoskrnl/ps/thread.c:496) FIX PS SDs!! (ntoskrnl/ldr/loader.c:262) Could not open module file: \SystemRoot\System32\drivers\usbehci.sys (Status 0xc0000034) (ntoskrnl/io/pnpmgr/pnpmgr.c:2371) Initialization of service usbehci failed (Status c0000034) (ntoskrnl/ps/thread.c:496) FIX PS SDs!! (dll/win32/newdev/newdev.c:736) Installing USB controller (PCI\VEN_1106&DEV_3038 &SUBSYS_30381106&REV_80\1&f103bba4&50) (dll/win32/newdev/newdev.c:525) Installing driver (Generic USB devices): UHCI USB controller (dll/win32/setupapi/queue.c:1456) copy error 2 L"C:\\ReactOS\\inf\\usbport.sys" -> L"C:\\ReactOS\\System32\\drivers\\usbport.sys" (dll/win32/setupapi/queue.c:1456) copy error 2 L"C:\\ReactOS\\inf\\usbuhci.sys" -> L"C:\\ReactOS\\System32\\drivers\\usbuhci.sys" (ntoskrnl/ps/thread.c:496) FIX PS SDs!! (ntoskrnl/ps/thread.c:496) FIX PS SDs!! (ntoskrnl/ps/thread.c:496) FIX PS SDs!! (dll/win32/rpcrt4/ndr_marshall.c:928) unhandled data type=09 (ntoskrnl/ps/thread.c:496) FIX PS SDs!! (ntoskrnl/ps/thread.c:496) FIX PS SDs!! (drivers/usb/usbport/usbcore.c:15) Miniport 0x81C5AB48 registered (drivers/usb/miniport/common/fdo.c:337) IRP_MJ_PNP / unknown minor function 0x8 (drivers/usb/miniport/sys/linuxwrapper.c:479) IoGetDmaAdapter done 0x81C7A128, mapRegisterCount=2 (drivers/usb/usbport/hcd-pci.c:74) usbcore: usb_hcd_pci_probe() called (drivers/usb/miniport/sys/linuxwrapper.c:201) driver_register 0: A05850B8 A05803F3 (ntoskrnl/ps/thread.c:496) FIX PS SDs!! (drivers/usb/miniport/sys/linuxwrapper.c:137) usbcore: Created system thread 172 (drivers/usb/miniport/sys/linuxwrapper.c:201) driver_register 1: A0585114 A05802F0 (drivers/usb/usbport/hcd-pci.c:74) usbcore: usb_hcd_pci_probe() called (drivers/usb/usbport/../miniport/linux/pci_hal.c:13) pci_enable_device() called. .. (drivers/usb/usbport/hub.c:1230) hub_thread startingEntered debugger on last-chance exception (Exception Code: 0xc0000005) (Page Fault) Memory at 0xCDCDCDF1 could not be read: Page not present. kdb:> bt Eip: <usbuhci.sys:65b4 (drivers/usb/miniport/common/pdo.c:132 (UsbMpPdoPnp))> Frames: <usbuhci.sys:5ac2 (drivers/usb/miniport/common/main.c:402 (DispatchPnp))> <ntoskrnl.exe:3630a (ntoskrnl/io/iomgr/irp.c:1084 (IofCallDriver))> <ntoskrnl.exe:3b906 (ntoskrnl/io/pnpmgr/pnpmgr.c:944 (IopInitiatePnpIrp))> <ntoskrnl.exe:3c3c0 (ntoskrnl/io/pnpmgr/pnpmgr.c:1753 (IopActionInterrogateDeviceStack))> <ntoskrnl.exe:3c0e2 (ntoskrnl/io/pnpmgr/pnpmgr.c:972 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:3c0f7 (ntoskrnl/io/pnpmgr/pnpmgr.c:986 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:3c119 (ntoskrnl/io/pnpmgr/pnpmgr.c:1011 (IopTraverseDeviceTree))> <ntoskrnl.exe:3d822 (ntoskrnl/io/pnpmgr/pnpmgr.c:2542 (IopInvalidateDeviceRelations))> <ntoskrnl.exe:35a75 (ntoskrnl/io/iomgr/iowork.c:30 (IopWorkItemCallback))> <ntoskrnl.exe:22f38 (ntoskrnl/ex/work.c:162 (ExpWorkerThreadEntryPoint))> <ntoskrnl.exe:69bbc (ntoskrnl/ps/thread.c:134 (PspSystemThreadStartup))> <ntoskrnl.exe:73ad2 (ntoskrnl/ke/i386/ctxswitch.S:258 (KiThreadStartup@156))> kdb:>

18 years

Mailserver and website migration over

by Aleksey Bragin

Hello, The ReactOS server is finally fully migrated now, including mailing lists, webserver with all its contents, SVN server, etc. Thanks for your patience during the server movement, we had to change really a lot of stuff, to make future transfers easier, to prevent "slashdotting" and many many other things. I am very pleased to announce that now everything is in place and is expected to work as it always did. There is a note however, for translators and admins, the static webpages are cached now and are automatically updated every 2 hours. So a change in the static web page can take as much as 2 hours before it goes "live". With the best regards, Aleksey Bragin. P.S. That spammer in ros-dev is unsubscribed from the list.

18 years

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