Ros-dev May 2005

ros-dev@reactos.org

68 participants
173 discussions

VOTE RESULTS: Switch to Wine Debug System

by Alex Ionescu

The results have been delayed for a day due to some last minute questions by Emanuelle. The final results are now in: YES, switch to a "Wine-Inspired/Compatible" Debug System, but using NT Debugging facilities as channels: 7 UNDECIDED/HAS RESERVATIONS: 2 There were no "NO" answers, but both Eric and Hartmut expressed certain disagreements. I've replied to them but have yet to receive a reply to my arguments. In any case, by a majority, the new system has been elected. We now need developers to implement it :) Best regards, Alex Ionescu

19 years, 3 months

Usb Tools that work with ROS

by James Tabor

HI, I'm trying to get USB development cooking. Enjoy, James

19 years, 3 months

Re: Thanks

by Jason Filby

Thanks al-Quaknaa! On 5/24/05, Alli Quaknaa <alquaknaa(a)gmail.com> wrote: > Hello Jason, > I want to thank for all your work on ReactOS and on that project - > it's great! Thanks also to everyone in the team. > al-Quaknaa >

19 years, 3 months

Vfatfs Bug

by James Tabor

Hi, Is this bug Hartmut was referring to? Entered debugger on last-chance exception number 14 (Page Fault) Memory at 0x4 could not be read: Page not present. kdb:> bt Eip: <vfatfs.sys:7fc2 (fcb.c:224 (vfatReleaseFCB))> Frames: <vfatfs.sys:1937 (close.c:59 (VfatCloseFile))> <vfatfs.sys:19d8 (close.c:100 (VfatClose))> <vfatfs.sys:d1c8 (misc.c:106 (VfatDispatchRequest))> <vfatfs.sys:d3ee (misc.c:168 (VfatBuildRequest))> <ntoskrnl.exe:4c8f8 (io/irp.c:1009 (IofCallDriver))> <ntoskrnl.exe:4c870 (io/irp.c:954 (IoCallDriver))> <ntoskrnl.exe:45829 (io/file.c:213 (IopDeleteFile))> <ntoskrnl.exe:7aa8c (ob/object.c:807 (ObpDeleteObject))> <ntoskrnl.exe:7abd5 (ob/object.c:879 (ObpDeleteObjectDpcLevel))> <ntoskrnl.exe:7ada2 (ob/object.c:988 (ObfDereferenceObject))> <ntoskrnl.exe:1afc1 (cc/view.c:964 (CcRosDeleteFileCache))> <ntoskrnl.exe:1b5e6 (cc/view.c:1232 (CmLazyCloseThreadMain))> <ntoskrnl.exe:86185 (ps/thread.c:88 (PspSystemThreadStartup))> <ntoskrnl.exe:3885 (/tmp/ccsgLh0O.s:83 (KiThreadStartup))> kdb:> cont KeBugCheckWithTf at ke/catch.c:217 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: vfatfs.sys KMODE_EXCEPTION_NOT_HANDLED Technical information: *** STOP: 0x0000001E (0xc0000005,0x9d538fc2,0x00000000,0x00000004) *** vfatfs.sys - Address 0x9d538fc2 base at 0x9d531000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:9d538fc2 <vfatfs.sys:7fc2 (fcb.c:224 (vfatReleaseFCB))> cr2 4 cr3 26000 Proc: 80c47364 Pid: 4 <System> Thrd: 80c57874 Tid: 54 DS 10 ES 10 FS 30 GS 23 EAX: 00000000 EBX: 00000000 ECX: 818b00dc EDX: 00031380 EBP: 9d4a0b9c ESI: 0001fef4 ESP: 9d4a0b10 EDI: 00000000 EFLAGS: 00010206 kESP 9d4a0b10 kernel stack base 9d49e000 Frames: <vfatfs.sys:1937 (close.c:59 (VfatCloseFile))> <vfatfs.sys:19d8 (close.c:100 (VfatClose))> <vfatfs.sys:d1c8 (misc.c:106 (VfatDispatchRequest))> <vfatfs.sys:d3ee (misc.c:168 (VfatBuildRequest))> <ntoskrnl.exe:4c8f8 (io/irp.c:1009 (IofCallDriver))> <ntoskrnl.exe:4c870 (io/irp.c:954 (IoCallDriver))> <ntoskrnl.exe:45829 (io/file.c:213 (IopDeleteFile))> <ntoskrnl.exe:7aa8c (ob/object.c:807 (ObpDeleteObject))> <ntoskrnl.exe:7abd5 (ob/object.c:879 (ObpDeleteObjectDpcLevel))> <ntoskrnl.exe:7ada2 (ob/object.c:988 (ObfDereferenceObject))> <ntoskrnl.exe:1afc1 (cc/view.c:964 (CcRosDeleteFileCache))> <ntoskrnl.exe:1b5e6 (cc/view.c:1232 (CmLazyCloseThreadMain))> <ntoskrnl.exe:86185 (ps/thread.c:88 (PspSystemThreadStartup))> <ntoskrnl.exe:3885 (/tmp/ccsgLh0O.s:83 (KiThreadStartup))> Entered debugger on embedded INT3 at 0x0008:0x800058ee. kdb:>

19 years, 3 months

Compatibility Problems

by James Tabor

Hi, Our compatibility with w2k and XP sux! Here is a old psx.exe command and compare it with the new windows 2k compatible one we have. http://adsl-64-217-116-74.dsl.hstntx.swbell.net/ftp/pub/ReactOS/psx.exe Just in case! Looking at Nebbetts book Win NT/2k Native API Ref, our SYSTEM_PROCESS_INFORMATION for w2k is not close at all! Where is LLLONG or LONGLONG PrivatePageCount? What is funny, psx.exe uses NT4 structures! So how can we use w2k structs with w2k and see if they really work? Thanks, James

19 years, 3 months

Re: [ros-svn] [hpoussin] 15474: Add ReactOS version at the start of the debug log

by Alex Ionescu

hpoussin(a)svn.reactos.com wrote: >Add ReactOS version at the start of the debug log > > >Updated files: >trunk/reactos/ntoskrnl/ke/main.c > > > Please revert: 1) KiSystemStartup is called for each CPU. 2) If you want to print something to the debug log, then add it into the debug log's wrapper code or something. The version info is already displayed on screen anyways..I don't get the point of this commit. Best regards, Alex Ionescu

19 years, 3 months

Re: [ros-svn] [hpoussin] 15473: Remove some debug messages at boot

by Alex Ionescu

hpoussin(a)svn.reactos.com wrote: >Remove some debug messages at boot > > >Updated files: >trunk/reactos/ntoskrnl/mm/mminit.c > >_______________________________________________ > > Please revert, these are important. Best regards, Alex Ionescu

19 years, 3 months

Compatibility Problems

by James Tabor

Hi, Our compatibility with w2k and XP sux! Here is a old psx.exe command and compare it with the new windows 2k compatible one we have. Looking at Nebbetts book Win NT/2k Native API Ref, our SYSTEM_PROCESS_INFORMATION for w2k is not close at all! Where is LLLONG or LONGLONG PrivatePageCount? What is funny, psx.exe uses NT4 structures! So how can we use w2k structs with w2k and see if they really work? Thanks, James

19 years, 3 months

VOTE: Switch to Wine Debug System

by Alex Ionescu

VOTING TOPIC: Switch to Wine Debug System, a run-time configurable Debug System in which various debug modes can be used (TRACE, WARN, FIXME, ERROR, etc). It would use DbgPrintEx along with Debug Filters (just like on XP) which can be configured at run-time in the registry to set how many of the messages to show. I believe the current WINE system has the library doing all this checking, but it's possible they do actually use the NT method. DbgPrintEx and filter states are currently unimplemented in our ntdll/ntoskrnl, so they must be implemented. Additionally, these Debug Messages would only be inserted into the code for a DBG build, just like it is currently done now. Finally, using this system will allow us to better share code with WINE. PROS: - Configurable debugging - More versatility then just "Print Always" and "Print if I remove NDEBUG" - Better code sharing with WINE - Will lead to the implementation of some DbgPrint functions which NT Drivers are bound to use. CONS: - Requires developer time to switch to this system. - Requires implementing some Kernel Functions. VOTING TIME: 2 weeks. Results announced Monday 23rd at 5PM EST. VOTING CHOICES: - Yes! Get rid of DPRINT/DPRINT1 and implement a run-time configurable Debug System with multiple verbose levels, based on WINE syntax and Windows NT implementation. - No! Stick with the current static, compile-time DPRINT/DPRINT1 system. VOTING OPEN TO: Due to the nature of this source-level change, voting is opened only to developers. Best regards, Alex Ionescu

19 years, 3 months

Re: [ros-svn] [jimtabor] 15466: This is a CompareStringW hack to get (7z313.exe /Q) to install. If anyone else has a better way, go for it!

by James Tabor

jimtabor(a)svn.reactos.com wrote: > This is a CompareStringW hack to get (7z313.exe /Q) to install. If anyone else has a better way, go for it! > > > Updated files: > trunk/reactos/lib/kernel32/misc/lang.c > I managed to get it to install by c:\7z313 /Q, it worked. I'm guessing with the compare string hack, it can be wrong, but? Anyone else with something better, I'm open! Thanks, James

19 years, 3 months

← Newer
1
2
3
4
5
6
7
8
9
...
18
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 May 2005