- Ros-dev - ReactOS.org

VOTE: Switch to Wine Debug System
by Alex Ionescu 22 May '05

22 May '05

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

12 25

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 22 May '05

22 May '05

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

1 0

Re: [ros-svn] [hbirr] 15457: Don't interpret STATUS_PIPE_CONNECTED as error.
by Alex Ionescu 21 May '05

21 May '05

hbirr(a)svn.reactos.com wrote: >Don't interpret STATUS_PIPE_CONNECTED as error. > > > >Updated files: >trunk/reactos/lib/kernel32/file/npipe.c > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > > This is a hack, not a fix... Best regards, Alex Ionescu

2 2

object manager rewrite
by Hartmut Birr 21 May '05

21 May '05

Hi, since the object manger rewrite all objects are allocated with the tag 'None'. I would like it if we can go back and add a tag for each object type. This tag is used for the memory allocation of an object. - Hartmut

2 1

Re: ATT: [ros-dev] VOTE: Switch to Wine Debug System. [3 days remaining]
by Steven Edwards 21 May '05

21 May '05

Hi, --- Alex Ionescu <ionucu(a)videotron.ca> wrote: > Attention all ROS Developers who have not yet voted. There are 3 days > remaining for this vote. I have not been keeping tight track but it seems so far everyone is for it but Eric would like us to add a extention like DPRINT1 support such as FIXME1 or WARN1 for messages we always want to see or add on our own. It seems like we can just leave DPRINT1 and reduce its usage. Also we all agree we need to figure out a way to be able to toggle Wine debug messages at runtime. The only question remains about using it in kernel mode that Hartmut mentioned. Thanks Steven Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html

1 0

[Fwd: Re: [ros-svn] [hbirr] 15387: Fixed rsym for executables without any debug informations.]
by Alex Ionescu 20 May '05

20 May '05

2 2

RE: [ros-dev] Timing tests
by Murphy, Ged (Bolton) 20 May '05

20 May '05

Brandon Turner wrote: > Yes, i can with 0.2.6(or any build you want to give me) after i get out > of work today at 1pm EST. > Great thanks. Tests need to be done on SVN HEAD. If you don't have access to this, I can provide you with an iso. I'll be in IRC later on tonight. Ged. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

2 1

Timing tests
by Murphy, Ged (Bolton) 20 May '05

20 May '05

I've been working on some code which involves timing and while I have been getting good results in XP, I've not been getting the same results in ROS. I'm unsure as to whether this is due to missing functionality in ROS, or the fact that I'm using an emulator. If I put together a few tests researching different timing methods, could someone running ROS on real hardware run the tests for me, as I don't have access to machine I can run them one. Thanks, Ged. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

2 1

RE: [ros-svn] [arty] 15429: Turned on -Werror
by PETREOLLE Sylvain 20 May '05

20 May '05

Channel rule #2: Congrats to Art ! Cordialement, Usurp(aka Sylvain PETREOLLE) Service de Production & d'Exploitation Informatique GEFCO - #DMIT/DATO/PSI/PEI Mail : <mailto:exploit@gefco.fr> Tel : 01.49.05.29.29 -----Message d'origine----- De : arty(a)svn.reactos.com [mailto:arty@svn.reactos.com] Envoyé : vendredi 20 mai 2005 10:07 À : ros-svn(a)reactos.com Objet : [ros-svn] [arty] 15429: Turned on -Werror Turned on -Werror Propogate AdapterBinding rather than LogicalAdapter or MiniportBlock in places where we handle a request since we might need the protocol that did the request later on, get rid of LogicalAdapter completely as according to Filip, it's never needed. Also, remove the Packet context hack in send complete if possible as this is now unnecessary (we now send all needed information in the work item instead). MiniQueueWorkItem, MiniDequeueWorkItem and MiniDoRequest were all changed to take an AdapterBinding. Added MiniRequestComplete, which handles a request complete. Fixed hang in ipconfig and the tcpip control panel. Updated files: trunk/reactos/drivers/net/ndis/Makefile trunk/reactos/drivers/net/ndis/include/miniport.h trunk/reactos/drivers/net/ndis/include/ndissys.h trunk/reactos/drivers/net/ndis/ndis/miniport.c trunk/reactos/drivers/net/ndis/ndis/protocol.c _______________________________________________ Ros-svn mailing list Ros-svn(a)reactos.com http://reactos.com:8080/mailman/listinfo/ros-svn ---------------------------------------------------------------------------- Ce message ainsi que toutes pièces jointes (le "message") sont confidentiels et sont exclusivement destinés à l'usage de la personne à laquelle ils sont adressés. Tout point de vue ou toute opinion contenus dans ce message expriment la pensée personnelle de leur auteur et ne représentent pas nécessairement la position des sociétés du Groupe GEFCO. Si vous n'êtes pas la personne à laquelle ce message est destiné, veuillez noter que vous avez reçu cet e-mail par erreur et qu'il vous est strictement interdit d'utiliser, de diffuser, de transférer, d'imprimer ou de copier ce message. Si vous avez reçu ce message par erreur, merci de contacter la personne qui vous l'a adressé et de l'effacer immédiatement. Les sociétés du Groupe GEFCO déclinent toute responsabilité en cas d'altération, de modification, d'édition, de diffusion sans autorisation de ce message ou en cas d'affection de ce message par un virus. This message and any attachments (the "message") are confidential and intended solely for the use of the individual to whom they are addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the GEFCO Group of Companies. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this message is strictly prohibited. If you have received this message in error please contact the sender and delete the message immediately. The GEFCO Group of Companies shall not be liable for the message if altered, changed, falsified, edited, diffused without authorization or affected by any virus. ----------------------------------------------------------------------------

1 0

RE: [ros-svn] [Phreak] 15423: Removed invalid . from path in thisusetup ini file as a temporary fix. Next step is to removethe darn ini file entirely
by Casper Hornstrup 20 May '05

20 May '05

Which ini file? > -----Original Message----- > From: ros-svn-bounces(a)reactos.com [mailto:ros-svn-bounces@reactos.com] On Behalf Of > Phreak(a)svn.reactos.com > Sent: 20. maj 2005 04:22 > To: ros-svn(a)reactos.com > Subject: [ros-svn] [Phreak] 15423: Removed invalid . from path in thisusetup ini file as a > temporary fix. Next step is to removethe darn ini file entirely > > Removed invalid . from path in this usetup ini file as a temporary fix. Next step is to remove the > darn ini file entirely > > > Updated files: > trunk/reactos/bootdata/packages/reactos.dff > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-svn

1 0

install problem
by Hartmut Birr 19 May '05

19 May '05

Hi, I'm not able to install reactos from the current svn with the bootcd. Usetup and the second stage setup works. After the next reboot, I get only a message box with 'Userint failed to start the shell!'. If I revert the changes from 15403 (using memory mapped files), I can install reactos. - Hartmut

2 1

[Fwd: Re: [ros-dev] install problem]
by Alex Ionescu 19 May '05

19 May '05

1 0

[Fwd: Re: [ros-dev] Re: [ros-svn] [hbirr] 15381: - Reference the file object in IopSecurityFile.]
by Alex Ionescu 19 May '05

19 May '05

1 0

Re: [ros-svn] [hbirr] 15381: - Reference the file object in IopSecurityFile.
by Alex Ionescu 19 May '05

19 May '05

hbirr(a)svn.reactos.com wrote: >- Reference the file object in IopSecurityFile. >- Don't set FO_DIRECT_DEVICE_OPEN in IoCreateStreamFileObject. >- Disabled the setting of IRP_NOCACHE, because vfat cannot handle cached and non cached requests for the same file. >- Set the correct device object in NtWriteFile. > > > > > > Hi, This change breaks usetup. As I said, IoCreateStreamFileObject must be left with the current hack intact. Best regards, Alex Ionescu

3 2

Re: [ros-svn] [ion] 15395: Object Manager Patch. This patch continues the work done in the previous patch and makes the following changes in order to support OB 2.0 (it basically temporarily fixes a highly incorrect implementation so that caller code will be ready to work with the OB 2.0 without change):
by Hartmut Birr 19 May '05

19 May '05

Hi, I'm not able to boot reactos after your last four commits. - Hartmut (io/pnpreport.c:84) IoReportResourceForDetection partly implemented (io/pnpreport.c:84) IoReportResourceForDetection partly implemented (io/pnpreport.c:84) IoReportResourceForDetection partly implemented (io/pnpreport.c:84) IoReportResourceForDetection partly implemented (cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in remaining path:"\DeviceClasses\{86E0D1E0-8089-11D0-9CE4-08003E301F73}\##?#ACPI#PNP0501#1#{86E0D1E0-8089-11D0-9CE4-08003E301F73}"!) KeBugCheckWithTf at ke/catch.c:222 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: ntoskrnl.exe KMODE_EXCEPTION_NOT_HANDLED Technical information: *** STOP: 0x0000001E (0xc0000005,0x80039e70,0x00000000,0x00000004) *** ntoskrnl.exe - Address 0x80039e70 base at 0x80000000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:80039e70 <ntoskrnl.exe:39e70 (io/device.c:86 (IopInitializeDevice))> cr2 4 cr3 34000 Proc: 80806364 Pid: 4 <System> Thrd: 80807680 Tid: 0 DS 10 ES 10 FS 30 GS 10 EAX: 00000000 EBX: 000764dc ECX: 80952008 EDX: 809b9e24 EBP: 800eeba0 ESI: 15b62000 ESP: 800eeb14 EDI: 00000000 EFLAGS: 00210296 kESP 800eeb14 kernel stack base 800ed000 Frames: <ntoskrnl.exe:4b8cf (io/pnpmgr.c:1523 (IopActionInitChildServices))> <ntoskrnl.exe:4b986 (io/pnpmgr.c:1569 (IopActionInitAllServices))> <ntoskrnl.exe:4aa6b (io/pnpmgr.c:695 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:4aaa1 (io/pnpmgr.c:709 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:4aaa1 (io/pnpmgr.c:709 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:4aae7 (io/pnpmgr.c:735 (IopTraverseDeviceTree))> <ntoskrnl.exe:4b9ec (io/pnpmgr.c:1628 (IopInitializePnpServices))> <800AB56A> <800A909C> <ntoskrnl.exe:10544 (ke/main.c:103 (KiSystemStartup))> <800A77AA> <ntoskrnl.exe:104b (D:\DOKUME~1\hb\LOKALE~1\Temp/ccO4aaaa.s:51 (_section_alignment__))>

3 6

Recent horrid slowdown
by Phillip Susi 19 May '05

19 May '05

About a week or two ago usetup took about 20 seconds on my system under qemu to copy over the installation files. I thought even that seemed a bit slow, so I started rewriting the code to use memory mapped files to see if I could speed it up. Now that I finished with it, I noticed that the current code in the repository now takes just over 90 seconds to install the files, which my changes reduce back down to 20 seconds. Does anyone have any idea about what revision this huge slowdown was introduced in? I'll try and figure out the problem tonight but it would help if someone could point me towards the vicinity of it now so I don't have to spend time looking when I get home. I'd like to get the normal code back to it's former 20 second install area so I can get a good comparison with my new code. I'd be thrilled if it then could get the install times down to 10 seconds.

3 5

Directory name problem.
by WaxDragon 19 May '05

19 May '05

Just recently, (cd "Program Files") has stopped working. It works without the quotes, but when you tab complete the directory name, it quotes it for you automatically. Anyone touch this recently? WD -- "<arty> the tree was touched a lot recently"

1 0

Networking is back!
by WaxDragon 19 May '05

19 May '05

Thanks to Alex and Arty! 15407 & 15408 fix the problems I was seeing with ftp. Please check your networking apps again! WD -- "<arty> the tree was touched a lot recently"

1 0

r15402 breakage
by Phillip Susi 19 May '05

19 May '05

The changes in this revision broke building, I get this: ntoskrnl: [CC] io/pnpmgr.c io/pnpmgr.c: In function `IoGetDeviceProperty': io/pnpmgr.c:63: warning: 'Data' might be used uninitialized in this function mingw32-make[1]: *** [io/pnpmgr.o] Error 1 mingw32-make: *** [ntoskrnl] Error 2

1 0

Dhcp Client
by James Tabor 19 May '05

19 May '05

NOTE: DHCPACK from 10.65.145.76 NOTE: Input: 255.255.255.0 NOTE: got 255.255.255.0 NOTE: got <NULL> NOTE: Input: 10.65.145.1 NOTE: got 10.65.145.1 NOTE: got <NULL> NOTE: Input: 151.164.1.8 151.164.1.7 NOTE: got 151.164.1.8 NOTE: got 151.164.1.7 NOTE: got <NULL> NOTE: Input: 10.65.145.255 NOTE: got 10.65.145.255 NOTE: got <NULL> NOTE: Input: 10.65.145.76 NOTE: got 10.65.145.76 NOTE: got <NULL> (dispatch.c:338)(add_timeout) Adding timeout 428be4f7 0040394b 781fbc NOTE: bound to 10.65.145.106 -- renewal in 21600 seconds. What is there not to like? 8^D James

2 1

[Fwd: Re: [ros-dev] Recent horrid slowdown]
by Alex Ionescu 18 May '05

18 May '05

1 0

RE: [ros-dev] Compiling ReactOS on Linux
by Murphy, Ged (Bolton) 18 May '05

18 May '05

Vit Herman wrote: > So my question is: what is needed to get cross-compilation > enviroment capable of building ReactOS on linux? Here is an install script for 3.4.1, from Casper's site. http://reactos.csh-consult.dk/download.php?id=13 Ged. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

3 2

Regression Testing
by WaxDragon 18 May '05

18 May '05

I'm working on a list of things to test ReactOS with, and I already have a good list of networking apps to try. I am interested in what others use for personal "regression tests", particularly non-network apps. I would like to make a comprehensive list of manual regression tests to use in combination with programmatic ones. Any info on our programmatic regression testing would be useful also. Some things I scribbled down: Changing the wallpaper Ros on ros compilation rosperf I'm not including "Installing from the bootcd/running the livecd" since alot of people do that anyway. Thanks! WD -- "<arty> the tree was touched a lot recently"

1 0

15386 bootcd fails to install freeldr...
by WaxDragon 18 May '05

18 May '05

I run though the first stage installer (formatting the disk) and after it asks where I want to install freeldr (I choose MBR) ReactOS then bugchecks: (cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in remaining path: "\Hardware Profiles\Current\System\CurrentControlSet\Services\vmx_svga\Device0"!) (cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in remaining path: "\Hardware Profiles\Current\System\CurrentControlSet\Services\vmx_svga"!) (cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in remaining path: "\Hardware Profiles\Current\System\CurrentControlSet\Services"!) (cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in remaining path: "\Hardware Profiles\Current\System\CurrentControlSet"!) (cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in remaining path: "\Hardware Profiles\Current\System"!) (cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in remaining path: "\Hardware Profiles\Current"!) (cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in remaining path: "\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00\0000"!) (bootsup.c:1760) System path: '\Device\Harddisk0\Partition1' (bootsup.c:1966) No or unknown boot loader found (bootsup.c:1974) Copy: \Device\CdRom0\loader\freeldr.sys ==> \Device\Harddisk0\Partition1\freeldr.sys (bootsup.c:1989) Copy: \Device\CdRom0\loader\freeldr.sys ==> \Device\Harddisk0\Partition1\freeldr.ini (inicache.c:1037) BufferSize: 694 (bootsup.c:2003) Save bootsector: \Device\Harddisk0\Partition1 ==> \Device\Harddisk0\Partition1\bootsect.old Entered debugger on last-chance exception number 14 (Page Fault) Memory at 0x138 could not be read: Page not present. kdb:> bt Eip: <vfatfs.sys:b592 (rw.c:572 (VfatRead))> Frames: <vfatfs.sys:d1f4 (misc.c:110 (VfatDispatchRequest))> <vfatfs.sys:d3ee (misc.c:168 (VfatBuildRequest))> <ntoskrnl.exe:4c898> <ntoskrnl.exe:4c810> <ntoskrnl.exe:487bf> <ntoskrnl.exe:36d2> <smss.exe:19c3> <smss.exe:426f> <smss.exe:16f18> <smss.exe:17623> <deadbeef> kdb:> Thanks to Alex for showing me how to enable serial output for the bootcd! WD -- "<arty> the tree was touched a lot recently"

1 0

Compiling ReactOS on Linux
by Vit Herman 18 May '05

18 May '05

Hi Few days ago, I did my check of the state of ReactOS. I was surprised by the progress made and decided to do some hacking with it. So I did a SVN checkout of the source tree and wanted to build it, BUT! I realized that cross-compiling ReactOS on linux is not as easy as I thought. So my question is: what is needed to get cross-compilation enviroment capable of building ReactOS on linux? I don't have any Windows box here and I must admit I don't like the idea of having one either. If there's anybody hacking ReactOS on Linux, I would apreciate his help. I would personaly love to see some information about cross-compiling on the website - it's really concise on this topic :( Thanks for your help Vit Herman

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev