Ros-dev September 2005

ros-dev@reactos.org

67 participants
129 discussions

Re: [ros-diffs] [npwoods] 18056: Lightweight sync with WINE regedit; imported obvious changes such as const correctness, TCHAR string usage etc
by Thomas Weidenmueller 26 Sep '05

26 Sep '05

npwoods(a)svn.reactos.com wrote: > + if (hRootKey == HKEY_DYN_DATA) return _T("HKEY_DYN_DATA"); This key doesn't exist on NT... ;) - Thomas

3 3

Re: [ros-svn] [ea] 18050: Required for binary compatibility with MS KERNEL32.DLL.
by KJKHyperion 25 Sep '05

25 Sep '05

ea(a)svn.reactos.com wrote: >Required for binary compatibility with MS KERNEL32.DLL. > >NOTE >Filip and I still don't understand why KERNEL32 calls twice CsrConnectToServer. >A possible explanation is because the Win32 server is a dual server: gui+console. > > yes. It connects to subsystems 1 and 2. In general, all CSR calls made by kernel32.dll are easily identifiable as calls to either subsystem from their code (the subsystem code is in the upper 16 bits). The GUI subsystem's functions, if you were wondering, are: SrvExitWindowsEx SrvEndTask SrvLogon SrvRegisterServicesProcess SrvActivateDebugger SrvGetThreadConsoleDesktop SrvDeviceEvent SrvRegisterLogonProcess SrvCreateSystemThreads SrvRecordShutdownReason

3 2

Re: [ros-svn] [ea] 18050: Required for binary compatibility with MS KERNEL32.DLL.
by Alex Ionescu 25 Sep '05

25 Sep '05

ea(a)svn.reactos.com wrote: >Required for binary compatibility with MS KERNEL32.DLL. > > > I don't understand this change; it is incorrect. MS kernel32.dll sends the name of the port. Best regards, Alex Ionescu

2 2

Re: [ros-svn] [ea] 18050: Required for binary compatibility with MS KERNEL32.DLL.
by Alex Ionescu 25 Sep '05

25 Sep '05

1 0

Re: [ros-diffs] [navaraf] 18043: Add TestAlert check to NtContinue.
by Hartmut Birr 25 Sep '05

25 Sep '05

navaraf(a)svn.reactos.com wrote: >Add TestAlert check to NtContinue. > >Modified: trunk/reactos/ntoskrnl/ps/i386/continue.c > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/ntoskrnl/ps/i386/continue.c* > >--- trunk/reactos/ntoskrnl/ps/i386/continue.c 2005-09-25 09:22:22 UTC (rev 18042) >+++ trunk/reactos/ntoskrnl/ps/i386/continue.c 2005-09-25 09:23:05 UTC (rev 18043) >@@ -80,6 +80,11 @@ > > KeLowerIrql(oldIrql); > } > > > >+ if (TestAlert) >+ { >+ KeTestAlertThread(TrapFrame->PreviousMode); >+ } >+ > > > /* Restore the user context */ > Thread->TrapFrame = PrevTrapFrame; > __asm__("mov %%ebx, %%esp;\n" "jmp _KiServiceExit": : "b" (TrapFrame)); > > You know, that ps\i386\continue.c is not longer used. The code was moved to ke\i386\syscall.S. - Hartmut

2 1

RE: [ros-dev] Priorities
by Murphy, Ged (Bolton) 24 Sep '05

24 Sep '05

I plan to implement these in the near future ..... unless someone else does it first. I currently have reworked code for tracert, arp, netstat, ipconfig, pathping and route I will start to commit over the next few weeks. I then plan to implement other services and apps in relation to networking, including test apps. Ged. -----Original Message----- From: WaxDragon [mailto:waxdragon@gmail.com] Sent: 24 September 2005 06:25 To: ReactOS Development List Subject: Re: [ros-dev] Priorities I'm would be very interested in a set of network "simple services" like echo, chargen, daytime, etc.. Having those on the install would help ReactOS get some wider network testing. WD On 9/23/05, Rick Langschultz <rlangschultz(a)cox.net> wrote: > I was wondering if there was a priority list for the next release. > Whether it be 0.2.8 or 0.3.0 I would either like to work on > implementing services and/or tcp/ip based networking. Primarily > though, getting services up and running would be great for me who > develops services. > Rick Langschultz > rlangschultz(a)cox.net (Home) > rlangschultz(a)ellemaespa.com (Work) > rlangschultz(a)email.uophx.edu (School) > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev > -- <arty> don't question it ... it's clearly an optimization _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev ************************************************************************ 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

Priorities
by Rick Langschultz 24 Sep '05

24 Sep '05

I was wondering if there was a priority list for the next release. Whether it be 0.2.8 or 0.3.0 I would either like to work on implementing services and/or tcp/ip based networking. Primarily though, getting services up and running would be great for me who develops services. Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

2 1

Re: [ros-diffs] [gvg] 17985: Return atom length when requested. Fixes bug 793.
by Hartmut Birr 23 Sep '05

23 Sep '05

gvg(a)svn.reactos.com wrote: >Return atom length when requested. Fixes bug 793. > >Modified: trunk/reactos/lib/rtl/atom.c >Modified: trunk/reactos/subsys/win32k/ntuser/class.c > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/lib/rtl/atom.c* > >--- trunk/reactos/lib/rtl/atom.c 2005-09-22 20:17:55 UTC (rev 17984) >+++ trunk/reactos/lib/rtl/atom.c 2005-09-22 20:24:50 UTC (rev 17985) >@@ -610,6 +610,10 @@ > > *NameLength = Length; > } > } > > >+ else if (NameLength != NULL) >+ { >+ *NameLength = (Entry->NameLength + 1) * sizeof(WCHAR); >+ } > > > > return Status; > } >@@ -651,6 +655,10 @@ > > > *NameLength = Length; > } > } > > >+ else if (NameLength != NULL) >+ { >+ *NameLength = (Entry->NameLength + 1) * sizeof(WCHAR); >+ } > > > } > else > { > > > ------------------------------------------------------------------------ Entry is uninitialized at this two points. - Hartmut

2 3

Moving onto 0.3 with networking
by Murphy, Ged (Bolton) 23 Sep '05

23 Sep '05

As one of our main features for 0.3, we can't progress out of the 0.2.* releases until it is either complete, or the goalposts are moved. With nobody working on networking at the moment, 0.2.8 seems likely and I'm starting to wonder how far into the 0.2.* releases we are going to go. Also, at what stage will the network model be enough to satisfy a 0.3 release? Does this just mean stable, basic TCP/IP with basic ws2_32 support? How many drivers need to be supported? What about service providers for ws2_32.dll (Mswsock.dll is stubbed apart from TransmitFile, and Wshtcpip.dll is non existent) What about NDIS? Change in circumstances has just released most of my evenings now, however although I'm starting to work on networking apps, and hopefully soon User Mode code, my coding skills and windows knowledge are not yet up to a level where I can tackle the more in-depth stuff, especially kernel mode (eek) Does any one plan to, or is anyone going to volunteer to take up networking? I would be more than happy to throw all my spare time into helping them in any way possible. If we glean some information from this email, I can start to document it in the wiki (we don't have much networking documentation in there at the moment) Regards, 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

Re: [ros-dev] Starcraft Setup BSODs due to KMODE_EXCEPTION_NOT_HANDLED
by eek2121＠comcast.net 23 Sep '05

23 Sep '05

Try using a crack and seeing if it works then. I know there was work done on DirectDraw, so you might have some luck. > Glad I could help you, and help get my favorite game working on ReactOS. > > BTW, the colors on the liltle setup title program (or whatever you call > it) where weird. Just skin deep, and starcraft finished installation as > usual. However, it fails the CD test as it usually does. > > Ge van Geldorp wrote: > > >>From: Reuben Perelman > >> > >> > >> > >>>Ge van Geldorp wrote: > >>>Does the patch below fix this? > >>> > >>> > >> > >>Yes it does. > >> > >> > > > >Ok, thanks for testing. The patch is an ugly hack and I don't want to commit > >it. But at least I know what's going on now and can think about a better > >patch. > > > >Ge van Geldorp. > > > >_______________________________________________ > >Ros-dev mailing list > >Ros-dev(a)reactos.com > >http://reactos.com:8080/mailman/listinfo/ros-dev > > > > > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev

7 12

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev September 2005