Ros-dev

ros-dev@reactos.org

5790 discussions

Re: [ros-svn] [navaraf] 16445: Put the page tables and hyperspace at the right place in memory (ie. Windows compatible).
by Hartmut Birr 07 Jul '05

07 Jul '05

navaraf(a)svn.reactos.com wrote: >Put the page tables and hyperspace at the right place in memory (ie. Windows compatible). > > >Updated files: >trunk/reactos/boot/freeldr/freeldr/arch/i386/mb.S >trunk/reactos/boot/freeldr/freeldr/multiboot.c >trunk/reactos/ntoskrnl/mm/i386/page.c > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > > > Hi, on windows the hyperspace area is always 4MB. If you change the size you have also to change the mapping and initialisation functions. - Hartmut

1 0

A few bugs
by Rafal Kupiec 07 Jul '05

07 Jul '05

1) Task manager displays closed / killed software too. Maybe it cannot kill software? Runned software window disappears but in task manager it on runned application list. There's no info about this software in process tab. 2) In browse window I cannot enter in folders. System want to change its name when I double click on it. 3) In Task Manager there's 2x Windows posision in menu (sometimes).

6 8

ReactOS Website
by Rick Langschultz 07 Jul '05

07 Jul '05

I was wondering what software was being run on the ReactOS machine. I know that it is a version of linux and I guess php and mysql. Are there any others?

2 1

#16452 Bug
by Rafal Kupiec 07 Jul '05

07 Jul '05

Blue screen INACCESSIBLE_BOOT_DEVICE :) Nice work.

3 2

Branch for the 0.2.7-Release approaching
by Robert Köpferl 06 Jul '05

06 Jul '05

Hi, the date of the branch for the 0.2.7-release is fastly approaching. I dated it for Monday, 11.06. So there's still over one week ahead. I please you to stop implementing new features but and finish bigger reorganizations in the code. Keep the checked in code compileable. If you have issues concerning the date of the branch, post a message. More or less for my own (but also from comments on the ml) I decided to do a just normal release with normal names. So there will be no "network preview release" or such kind.

3 3

Website
by Murphy, Ged (Bolton) 06 Jul '05

06 Jul '05

Whats happening with this? It seems to have died a death again. Can we appoint some more people to the web team as there have been some great ideas put forward, but nobody seems to be acting on them. 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

1 0

Re: [ros-svn] [ekohl] 16437: Add architecture-specific headers and move I386-specific definitions into them.
by Alex Ionescu 05 Jul '05

05 Jul '05

ekohl(a)svn.reactos.com wrote: >Add architecture-specific headers and move I386-specific definitions into them. > > > Thanks a lot Eric. I did some research on another FIXME that is actually related to your PnP work, which you might want to take a look at. You will notice that DEVICE_NODE has 2 non-NT members. I saw that you had some previous patches concerning this structure that removed some of the ROS-Only fields, and I guess you might want to get rid of the two ones remaning. The first is BusTypeGuid. The correct way it should be handled is through a private array of GUIDs, which is indexed according DeviceNode.ChildBusTypeIndex. When querying, you just return the GUID in IopXxxxx[DeviceNode.ChildBusTypeIndex], and when creating a bus type guid, you just write the index there. I hope that's clear enough. The second is "Address". That field is actually already present in the DDK-documented DEVICE_CAPABILITIES structure. Therefore, when queried for it, simply send an IRP_MJ_QUERY_CAPABILITIES (or whatever the name is) to DeviceNode->PhysicalDeviceObject, and return the DeviceCapabilities.Address. That should be less then 20 lines of code to change, but I don't want to break any PnP features since they aren't my speciality.. Best regards, Alex Ionescu

1 0

PING
by Thomas Weidenmueller 05 Jul '05

05 Jul '05

PING

6 5

Re: [ros-svn] [gdalsnes] 16417: fix premature close og reg key
by TwoTailedFox 04 Jul '05

04 Jul '05

Shouldn't that be 'of reg key'? ;) On 7/4/05, gdalsnes(a)svn.reactos.com <gdalsnes(a)svn.reactos.com> wrote: > fix premature close og reg key > > > Updated files: > trunk/reactos/lib/setupapi/devinst.c > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-svn > -- "I had a handle on life, but then it broke"

1 0

Re: [ros-svn] [ekohl] 16393: - Move definitions from ntpnp.h into NDK and DDK
by Alex Ionescu 04 Jul '05

04 Jul '05

ekohl(a)svn.reactos.com wrote: >- Move definitions from ntpnp.h into NDK and DDK >- Remove ntpnp.h > > >Updated files: >trunk/reactos/include/ndk/zwfuncs.h >trunk/reactos/include/ndk/zwtypes.h >trunk/reactos/lib/wdmguid/wdmguid.c >trunk/reactos/ntoskrnl/include/ntoskrnl.h >trunk/reactos/ntoskrnl/io/plugplay.c >trunk/reactos/services/umpnpmgr/umpnpmgr.c >trunk/reactos/w32api/include/ddk/wdmguid.h > >Deleted files: >trunk/reactos/include/ddk/ntpnp.h > Hi, Heh, you beat me to it! I asked Filip if it was OK to do this and was going to do it myself, thanks for thinking foward. I just have two comments: - I think the GUIDs are undocumented, while wdmguid.h is a DDK header. Therefore, adding them there breaks MS DDK compatibility, since we'll get undefined errors if we build with it. Sorry to nitpick about compatibility again. - To keep size small and to stick with the current way the NDK has been made, I would prefer if there were no coments in it that describe or document structures. The comments should go on top of the actual APIs in the source files. Sorry for nitpicking again ;-). Best regards, Alex Ionescu

2 2

Jump to page:

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