- Ros-dev - ReactOS.org

Re: [ros-diffs] [cwittich] 19765: added more correct linker flags (patch by brezenbak)
by Alex Ionescu 30 Nov '05

30 Nov '05

cwittich(a)svn.reactos.com wrote: >added more correct linker flags (patch by brezenbak) > >Modified: trunk/reactos/tools/rbuild/backend/msvc/vcprojmaker.cpp > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/tools/rbuild/backend/msvc/vcprojmaker.cpp* > >--- trunk/reactos/tools/rbuild/backend/msvc/vcprojmaker.cpp 2005-11-30 00:25:48 UTC (rev 19764) >+++ trunk/reactos/tools/rbuild/backend/msvc/vcprojmaker.cpp 2005-11-30 00:26:51 UTC (rev 19765) >@@ -330,8 +330,17 @@ > > } > else if ( exe ) > { > > >- fprintf ( OUT, "\t\t\t\tSubSystem=\"%d\"\r\n", console ? 1 : 2 ); >- fprintf ( OUT, "\t\t\t\tBaseAddress=\"%s\"\r\n", module.baseaddress.c_str ()); > > >+ if ( module.type == Kernel || module.type == NativeCUI) >+ { >+ fprintf ( OUT, "\t\t\t\tAdditionalOptions=\" /SUBSYSTEM:NATIVE /SECTION:INIT,D /ALIGN:4096 /FORCE:MULTIPLE\"\r\n" ); >+ fprintf ( OUT, "\t\t\t\tIgnoreAllDefaultLibraries=\"TRUE\"\r\n" ); >+ fprintf ( OUT, "\t\t\t\tEntryPointSymbol=\"%s\"\r\n", module.entrypoint.c_str ()); >+ fprintf ( OUT, "\t\t\t\tBaseAddress=\"%s\"\r\n", module.baseaddress.c_str ()); >+ } >+ else if ( module.type == Win32CUI || module.type == Win32GUI ) >+ { >+ fprintf ( OUT, "\t\t\t\tSubSystem=\"%d\"\r\n", console ? 1 : 2 ); >+ } > > > } > else if ( dll) > { > > This still isn't fully correct. First, the check should be widened to inculde Drivers. Secondly, /SECTION:INIT,D should only be used for Kernel or Drivers, not Native apps. Thirdly, /ALIGN:4096 is irrelevant -- this is the default. Kernel should get 0x80, and drivers should get 0x20. Fourthly, Kernel entrypoint should be hard-coded to KiSystemStartup, while Native apps shoudl be hardcoded to NtProcessStartup. This is especially important so that nt.lib will get used properly. Also, NativeCUI is a bit repetitive. Native can only be CUI. Drivers should also be compiled with /DRIVER. Native, Kernel and Drivers should have /NODEFAULTLIB. /FORCE:MULTIPLE is ugly and I don't know why it was added. Best regards, Alex Ionescu

1 0

RE: [ros-svn] [weiden] 19755: remove obsolete shutdown tool from rosapps
by Ge van Geldorp 29 Nov '05

29 Nov '05

> From: weiden(a)svn.reactos.com > > remove obsolete shutdown tool from rosapps Didn't even know that it was there... Thanks for cleaning up. GvG

2 1

accessing dereferenced file objects
by Hartmut Birr 29 Nov '05

29 Nov '05

Hi, looking through our file functions, we do always access a file object after it was dereferenced by the completion routine and if the FO_SYNCHRONOUS_IO flag is set. If FO_SYNCHRONOUS_IO is set, the completion routine should not dereference the file object or we have to add an additional reference. If FO_SYNCHRONOUS_IO is set, we have also to dereference the file object after calling the driver. - Hartmut

1 0

Re: [ros-svn] [frik85] 19758: RosCMS Update:
by TwoTailedFox 29 Nov '05

29 Nov '05

Thanks a barrel load, Frik. That's fixed a few bugs that have been a pain in the arse On 11/29/05, frik85(a)svn.reactos.com <frik85(a)svn.reactos.com> wrote: > RosCMS Update: > > admin_dyncontent_edit.php: "update bug" fixed > generate_page.php: page generation by translations works now the correct way > > > Updated files: > trunk/web/reactos.org/htdocs/roscms/inc/admin_dyncontent_edit.php > trunk/web/reactos.org/htdocs/roscms/inc/generate_page.php > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-svn > -- "I had a handle on life, but then it broke"

1 0

Re: [ros-diffs] [ion] 19742: - Implement RtlPrefectMemoryNonTemporal. Patch by Patrick Baggett <baggett.patrick@gmail.com> and myself.
by Thomas Weidenmueller 29 Nov '05

29 Nov '05

ion(a)svn.reactos.com wrote: > - Implement RtlPrefectMemoryNonTemporal. Patch by Patrick Baggett <baggett.patrick(a)gmail.com> and myself. > ------------------------------------------------------------------------ > *Modified: trunk/reactos/lib/rtl/mem.c* > > --- trunk/reactos/lib/rtl/mem.c 2005-11-29 01:54:33 UTC (rev 19741) > +++ trunk/reactos/lib/rtl/mem.c 2005-11-29 02:40:18 UTC (rev 19742) > @@ -140,7 +140,7 @@ > > } > > /* > > -* @unimplemented > > +* @implemented > > */ > VOID > FASTCALL > @@ -149,7 +149,9 @@ > > IN SIZE_T Length > ) > { > > - UNIMPLEMENTED; > > + /* By nature of prefetch, this is non-portable. */ > + (void)Source; > + (void)Length; > > } > > > Why have a function stub then? This just encourages someone to use it without #ifdef'ing it when porting to another platform. - Thomas

2 2

Revision: 19742
by James Tabor 29 Nov '05

29 Nov '05

(./ntoskrnl/ke/main.c:295) ----------------------------------------------------- ---------- (./ntoskrnl/ke/main.c:296) ReactOS 0.3-SVN (Build 20051129-r19742) Used memory 1015744Kb (./ntoskrnl/mm/mminit.c:386) Kernel Stack Limits. InitTop = 0x80122000, Init = 0 x8011f000 (./ntoskrnl/mm/mm.c:283) No current process (./ntoskrnl/io/driver.c:1294) Driver 'buslogic.sys' load failed, status (c000000 1) (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\system32\d rivers\sndblst.sys (Status 0xc0000034) (./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\system32\d rivers\mpu401.sys (Status 0xc0000034) (./ntoskrnl/io/disk.c:630) RDiskCount 1 Entered debugger on last-chance exception number 14 (Page Fault) Memory at 0x800affb4 could not be written: Page protection violation. kdb:>bt Eip: <ntoskrnl.exe:d7e9c (ntoskrnl/ke/i386/kernel.c:525 (Ki386SetProcessorFeatures))> Frames: <ntoskrnl.exe:ccdd3 (./ntoskrnl/ex/init.c:0 ())> <ntoskrnl.exe:cd87e (./ntoskrnl/ex/init.c:672 (ExpInitializeExecutive))> <ntoskrnl.exe:63d5 (./ntoskrnl/ke/main.c:106 (KiSystemStartup))> <ntoskrnl.exe:cb851 (./ntoskrnl/ke/main.c:300 (_main))> <ntoskrnl.exe:104b (ntoskrnl/ke/i386/main_asm.S:46 (NtProcessStartup))> (lib/rtl/i386/exception.c:90) Invalid exception frame Entered debugger on last-chance exception number 14 (Page Fault) Memory at 0x000764e0 could not be read: Page not present. KeBugCheckWithTf at ntoskrnl/ke/i386/exp.c:1242 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 Technical information: *** STOP: 0x0000001E (0xc0000005,0x800c939c,0x00000000,0x000764e0) *** ntoskrnl.exe - Address 0x800c939c base at 0x80000000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:800c939c <ntoskrnl.exe:c939c (lib/string/i386/memcpy_asm.s :43 (memcpy))> cr2 764e0 cr3 22000 Proc: 81004ba0 Pid: 4 <System> Thrd: 81005630 Tid: 0 DS 23 ES 23 FS 30 GS 0 EAX: 8011b1d4 EBX: 800aee40 ECX: 00000004 EDX: 8011b130 EBP: 8011b124 ESI: 000764e0 ESP: 8011b0a8 EDI: 8011b1d4 EFLAGS: 00210002 kESP 8011b0a8 kernel stack base 80118260 Frames: <ntoskrnl.exe:a2f00 (ntoskrnl/kdbg/kdb.c:1557 (KdbpSafeReadMemory))> <ntoskrnl.exe:a3e49 (ntoskrnl/kdbg/kdb_cli.c:570 (KdbpCmdBackTrace))> <ntoskrnl.exe:a72c8 (ntoskrnl/kdbg/kdb_cli.c:2178 (KdbpDoCommand))> <ntoskrnl.exe:a7402 (ntoskrnl/kdbg/kdb_cli.c:2237 (KdbpCliMainLoop))> <ntoskrnl.exe:a2453 (ntoskrnl/kdbg/kdb.c:1119 (KdbpCallMainLoop))> <ntoskrnl.exe:a0b1d (ntoskrnl/kdbg/i386/kdb_help.S:134 (KdbpStackSwitchAndCall)) > <ntoskrnl.exe:a24e1 (ntoskrnl/kdbg/kdb.c:1150 (KdbpInternalEnter))> <ntoskrnl.exe:a2c96 (ntoskrnl/kdbg/kdb.c:1457 (KdbEnterDebuggerException))> <ntoskrnl.exe:53adb (./ntoskrnl/kd/kdmain.c:127 (KdpEnterDebuggerException))> <ntoskrnl.exe:9782d (ntoskrnl/ke/i386/exp.c:1226 (KiDispatchException))> <ntoskrnl.exe:9639f (ntoskrnl/ke/i386/exp.c:194 (KiKernelTrapHandler))> <ntoskrnl.exe:af0a4 (ntoskrnl/mm/i386/pfault.c:128 (KiPageFaultHandler))> <ntoskrnl.exe:9aab1 (ntoskrnl/ke/i386/trap.s:151 (KiTrapProlog2))> <ntoskrnl.exe:d7e9c (ntoskrnl/ke/i386/kernel.c:525 (Ki386SetProcessorFeatures))> <ntoskrnl.exe:ccdd3 (./ntoskrnl/ex/init.c:0 ())> <ntoskrnl.exe:cd87e (./ntoskrnl/ex/init.c:672 (ExpInitializeExecutive))> <ntoskrnl.exe:63d5 (./ntoskrnl/ke/main.c:106 (KiSystemStartup))> <ntoskrnl.exe:cb851 (./ntoskrnl/ke/main.c:300 (_main))> <ntoskrnl.exe:104b (ntoskrnl/ke/i386/main_asm.S:46 (NtProcessStartup))> Entered debugger on embedded INT3 at 0x0008:0x800b0076. (lib/rtl/i386/exception.c:90) Invalid exception frame

2 2

Freeldr crash - real hw - INVALID OPCODE
by David Kredba 28 Nov '05

28 Nov '05

Hello. I am trying to boot ReactOS by freeldr on floppy from SCSI harddrive (80h) on an aic78xx. Freeldr loads and display Welcome message. I run Reactos HardDrive (C:) and got : An error occured in FreeLoader FreeLoader v2.1 Report this ... Exception 06: INVALID OPCODE EAX:00000001 ESP:0000FEFC CR0:00000011 DR0:00000000 EBX:2046C700 EBP:C7000000 CR1:00000000 DR1:00000000 ECX:00000000 ESI:FFFFFFFF CR2:00000000 DR2:00000000 EDX:00000001 EDI:002846C7 CR3:00000000 DR3:00000000 DR6:FFFF0FF0 DR7:00000400 CS:0008 EIP:FFFF2C46 DS:0010 ERROR CODE:00000000 ES:0010 EFLAGS:00010016 FS:0010 GDTR Base:0000842C Limit:0027 GS:0010 IDTR Base:000086E0 Limit:0100 SS:0010 LDTR:0000 TR:0000 Frames: Nothing more displayed. Computer is Dual PIII machine, Reactos is todays svn version builded on linux with mingw, 512 MB RAM. There is w2k server on second partition of the SCSI harddrive and boots and runs without errors. First partition is 4 GB FAT32, disk capacity is 18GB. Thank you. David

1 0

'make clean' errors
by WaxDragon 28 Nov '05

28 Nov '05

Anyone else seeing this under linux? Detecting netwide assembler...detected (nasm) Detecting compiler -pipe support...detected Detecting compiler pre-compiled header support...detected Processing modules...done Creating directories...done Unpacking WINE resources...done Generating test support code...done Generating compilation unit support code...done Generating syssetup.inf...done Generating proxy makefiles...done Checking automatic dependencies...done [CC] tools/cdmake/cdmake.c [CC] tools/cdmake/llmosrt.c [LD] output-i386/tools/cdmake/cdmake [LD] output-i386/tools/mkhive/mkhive gcc: obj-i386/lib/inflib_host/infcore.o: No such file or directory gcc: obj-i386/lib/inflib_host/infget.o: No such file or directory gcc: obj-i386/lib/inflib_host/infput.o: No such file or directory gcc: obj-i386/lib/inflib_host/infhostgen.o: No such file or directory gcc: obj-i386/lib/inflib_host/infhostget.o: No such file or directory gcc: obj-i386/lib/inflib_host/infhostglue.o: No such file or directory gcc: obj-i386/lib/inflib_host/infhostput.o: No such file or directory make: *** [output-i386/tools/mkhive/mkhive] Error 1 WD -- <mikedep333> but if it isnt working, why is it even included on the CD?

4 3

GPL Microsoft Code in the CRT
by Steven Edwards 28 Nov '05

28 Nov '05

Hi, There is some code in the C Runtime that was part of the Win32 port of perl. As such it carries the copyright Microsoft. I suggest we remove and rewrite these functions, as this will hinder us from being able to say "ReactOS is 100% free of Microsoft Code" Even if it is GPL it does not sit well with me. Anyone up to help on this? -- Steven Edwards - ReactOS and Wine developer "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo

8 13

RE: [ros-diffs] [sedwards] 19675: XML.cpp -> xml.cpp, XML.h -> xml.h.
by Casper Hornstrup 28 Nov '05

28 Nov '05

If the rule is always lowercase filenames why not vote on it and make it official and save ourselves some trouble in the future? Casper

2 3

Possible Compiler/Library problem?
by TwoTailedFox 28 Nov '05

28 Nov '05

http://neowin.ath.cx/twotailedfox/Error.png Can anyone help me shed some light on this rather perculiar error? GCC 3.4.4/G++ 3.4.2, MSYS 1.0, GNU Make 3.80, NASM 0.98, Binutils 2.16.91, MinGW 4.1.0 -- "I had a handle on life, but then it broke"

1 0

Re: [ros-diffs] [sedwards] 19673: more crt, crtdll and msvcrt cleanup
by Thomas Weidenmueller 27 Nov '05

27 Nov '05

sedwards(a)svn.reactos.com wrote: > more crt, crtdll and msvcrt cleanup > +#include "precomp.h" That doesn't work, it should be <precomp.h>.... - Thomas

2 1

Re: [ros-svn] [ion] 19693: - Remove KTSS_NOIOMP from NDK.
by Alex Ionescu 27 Nov '05

27 Nov '05

ion(a)svn.reactos.com wrote: >- Remove KTSS_NOIOMP from NDK. >- Fix KTSS definition. >- Fix KTRAP_FRAME definition. >- Fix RTL_PROCESS_BACKTRACE_INFORMATION and RTL_PROCESS_BACKTRACES definitions. >- Fix/rename RUNDOWN_DESCRIPTOR definition. >- Rename PPF_ definitions to RTL_USER_PROCESS_PARAMETERS_ >- Setup a global _REACTOS_ define when code is compiled. >- #ifdef out the multiboot flags from the NDK so they'll only be available for ReactOS. Dirty 'hack' until we stop using them. >- Update NDK Fixme list, since all major bugs are fixed now. > > > > Hi, Sorry, this breaks compiling. I think there is a bug in compilation units. I did make ntoskrnl_clean about 3 times, and even a complete "make depends -j2" and it compiled the whole tree fine. Then I started doing other changes, and I started getting build failures. Best regards, Alex Ionescu

2 2

Do it right first time ??
by Biera Gaino 27 Nov '05

27 Nov '05

It seems to me that is always best to do it right first time. Then it is easier to get quality, Well anyway it is my opinion. Like the Japanese car manufacturers discovered first, that is always best to track down and solve problems in early stage, than later...... Bierá L. gaino

3 2

Re: [ros-diffs] [ion] 19666: - Add DDK alignment macros and move/rename the ones in the NDK for user-mode only (since kernel-mode should use the DDK ones).
by Hartmut Birr 27 Nov '05

27 Nov '05

ion(a)svn.reactos.com wrote: > - Add DDK alignment macros and move/rename the ones in the NDK for user-mode only (since kernel-mode should use the DDK ones). > - Fix helper.h's alignment macros to protect properly and also use a faster implementation. > - Update NDK readme. > Modified: trunk/reactos/include/ndk/lpctypes.h > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/include/ndk/lpctypes.h* > --- trunk/reactos/include/ndk/lpctypes.h 2005-11-26 23:26:04 UTC (rev 19665) > +++ trunk/reactos/include/ndk/lpctypes.h 2005-11-27 02:55:13 UTC (rev 19666) > @@ -234,9 +234,9 @@ > // Maximum total Kernel-Mode LPC Message Structure Size > // > #define LPCP_MAX_MESSAGE_SIZE \ > > - ROUND_UP(PORT_MAXIMUM_MESSAGE_LENGTH + \ > > + ALIGN_UP(PORT_MAXIMUM_MESSAGE_LENGTH + \ > > sizeof(LPCP_MESSAGE) + \ > > - sizeof(LPCP_CONNECTION_MESSAGE), 16) > > + sizeof(LPCP_CONNECTION_MESSAGE), sizeof(ULONGLONG) * 2) > > > // > // Maximum actual LPC Message Length > > ------------------------------------------------------------------------ This or the definition of ALIGN_UP is wrong. ALIGN_UP needs a type as second parameter. Now the value of LPCP_MAX_MESSAGE_SIZE, LPC_MAX_MESSAGE_LENGTH and LPC_MAX_DATA_LENGTH are changed. ReactOS won't boot because csrss uses hard coded values in CsrpCreateListenPort. - Hartmut

3 3

Re: [ros-dev] [Vote] Top-level source header
by Brandon Turner 27 Nov '05

27 Nov '05

Only developers can vote. Brandon Alex Buell wrote: > On Sun, 27 Nov 2005, Casper Hornstrup wrote: > >> http://www.reactos.org/forum/viewtopic.php?p=10398#10398 > > > Since I cannot vote (even though I've signed up), I'll stand up and > say I'd vote for option B if I could. >

1 0

Re: [ros-diffs] [turner] 19669: Don't hardcode user to .DEFAULT when reading registry
by Thomas Weidenmueller 27 Nov '05

27 Nov '05

turner(a)svn.reactos.com wrote: > Don't hardcode user to .DEFAULT when reading registry > > Modified: trunk/reactos/subsys/win32k/ntuser/misc.c > + NtClose(CurrentUserKey); This needs to be ZwClose - Thomas

1 0

Debian win32 port, file system, installer, ELF
by Drew Scott Daniels 27 Nov '05

27 Nov '05

Hi, For background in the Debian win32 port see the mailing list archives [1]. Basically, the only reason the port is allowed by Debian is that it could run on ReactOS or wine which are both DFSG [2] compliant. Microsoft Windows, OS/2... aren't DFSG compliant. I've read [3] that the Debian win32 ports "failed because most unix software made unforgivable presumptions about file system semantics; mainly that you could delete files that were in-use, and rename open files on top of other open files, etc." Is this something that could be resolved? I'd imagine the Installable File System (IFS) driver would need to be modified to remember open files, or perhaps something could intercept calls to an IFS driver? I think this is what some virus scanners do, and what clamav is missing. Porting Debian to ReactOS would give ReactOS a huge number of packages. The BSD ports collection method or gentoo's build systems may be useful too. All three would probably mean porting some base software though. Any comments about porting the base of another OS to ros? Packages like perl, bash, gcc, glibc seem to have native MS Windows ports. http://packages.debian.org/stable/base/ lists all the various packages in Debian's base (note some are specific to various ports, and there are some semi-duplicated packages). Another advantage of a Debian win32 port using ReactOS would be a really nice flexible, modular installer (debian-installer or d-i for short). I've had problems with the ros installer in the past, specifically I couldn't install on one system without a mouse. It also asked many questions, couldn't resize partitions... d-i is nice in that it can be used with about three prompts, has partition resizing, can download additional modules... I'd suggest checking it out (I feel like I'm starting to just advertise it). Fwiw, longhorn seems to boot from a CD to do it's graphical install that is supposed to have file system resizing. Can/does ReactOS support ELF? Alex Ionescu said that there's now an ELF loader [4]. If so, would there be anything special that would need to be done to run Linux binaries on ReactOS (beyond syscalls and porting dependencies)? Is there any advantages to the PE format? If ReactOS could support running Linux binaries it would be an easier sell to port Debian to ReactOS as it could reuse things that are already compiled for Debian. I believe the FreeBSD port (kFreeBSD that is) [5] re-uses some packages compiled for Linux. OTOH, PE would be a nicer way to go so that some support for MS Windows could be allowed... Or could MS Windows be made to support ELF? I'm afraid I also don't know much about the coff format. [1] http://lists.debian.org/debian-win32/ [2] http://www.debian.org/social_contract#guidelines (very similar or the same as the OpenSource definition) [3] http://lists.debian.org/debian-win32/2005/10/msg00003.html Message-id: <43663BFE.9010004(a)liddicott.com> [4] http://www.reactos.org/bugzilla/show_bug.cgi?id=293 [5] http://www.debian.org/ports/kfreebsd-gnu/ Drew Daniels Resume: http://www.boxheap.net/ddaniels/resume.html

3 2

Re: [ros-diffs] [chorns] 19566: Speed up compilation of ntoskrnl
by Alex Ionescu 27 Nov '05

27 Nov '05

Hi, Do these changes break the MSVC backend? Best regards, Alex Ionescu

6 10

DOSemu for ReactOS
by crashfourit 27 Nov '05

27 Nov '05

Could we port DOSemu (http://www.dosemu.org/) to ReactOS for Dos and Win16 support? -- My DeviantArt.com page: http://crashfourit.deviantart.com/ My FanFiction.net bio page: http://www.fanfiction.net/u/726606/ My Blog: http://crashfourit.blogspot.com/ America's Debate: http://www.americasdebate.com/

4 5

Registry is messed up
by Brandon Turner 27 Nov '05

27 Nov '05

I think the registry is messed up. desk.cpl isnt writing the wallpaper style values, SystemParametersInfoW isnt wrtiting the path, and IntSystemParametersInfo isnt able to read the wallpaper settings from it. Also, my livecd wont boot with an error about not finding the codepage. This all leads me to believe that something is up with the registery. The last update i have is w3seek's where he reverted filip's registry changes. I dont know when this started happening, last day or so. It all worked fine when i commited 19476. Royce: The reason you werent getting the bugcheck with my stretch patch was because desk.cpl wasnt writing the wallpaper style values to the registry and tat is why the wallpaper didnt stick. I'm kinda busy right now. But hopfully within an hour I will be free and be able to do some more debuging. Brandon

1 1

Re: [ros-diffs] [gvg] 19572: Implement adding new sections/lines/fields and writing the resulting file
by Hartmut Birr 26 Nov '05

26 Nov '05

gvg(a)svn.reactos.com wrote: > Implement adding new sections/lines/fields and writing the resulting file > Added: trunk/reactos/lib/inflib/infhostglue.c > > *Added: trunk/reactos/lib/inflib/infhostglue.c* > --- trunk/reactos/lib/inflib/infhostglue.c 2005-11-25 21:29:16 UTC (rev 19571) > +++ trunk/reactos/lib/inflib/infhostglue.c 2005-11-25 21:37:23 UTC (rev 19572) > @@ -0,0 +1,24 @@ > +/* > + * PROJECT: .inf file parser > + * LICENSE: GPL - See COPYING in the top level directory > + * COPYRIGHT: Copyright 2005 Ge van Geldorp <gvg(a)reactos.org> > + */ > + > +/* INCLUDES *****************************************************************/ > + > +#include "inflib.h" > + > +#define NDEBUG > +#include <debug.h> > + > +void > +DbgPrint(const char *Fmt, ...) > +{ > + va_list Args; > + > + va_start(Args, Fmt); > + vfprintf(stderr, Fmt, Args); > + va_end(Args); > +} > + > +/* EOF */ > It is a little bit dirty to implement a well known function in a different way. - Hartmut

2 3

Re: [ros-dev] Log off reboots!
by TwoTailedFox 26 Nov '05

26 Nov '05

In Short, A Lot. ReactOS needs a proper shutdown and restart sequence (Like Linux does, when it sends TERM to all processes). Log Off is a tad harder. In order for Log Off to work properly, all the core processes need to be kept running (csrss, winlogon, etc), and the system needs to "Fall back" to a login screen. To do this, a User Logon System must be implemented, complete with per-user registry files, settings storage, and all the associated functions therein. AFAIK. On 11/26/05, Alex Buell <alex.buell(a)munted.org.uk> wrote: > On Fri, 25 Nov 2005, TwoTailedFox wrote: > > > No, the Shutdown/Restart and Log Off portions are in need of a > > re-write, AFAIK. Since Local User Accounts are not implemented yet, we > > cannot "Log Off" per se on ReactOS just yet. > > Ok, what needs doing to implement this properly? I'd like to help if I > can. > > -- > http://www.munted.org.uk > > Anyone that thinks an imaginary deity is going to protect them against > earthquakes and hurricanes needs psychiatric help. > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > -- "I had a handle on life, but then it broke"

3 3

RE: [navaraf] 19636/19637/19638: Don't make cells smaller than they are.
by Ge van Geldorp 26 Nov '05

26 Nov '05

> From: navaraf(a)svn.reactos.com > > Don't make cells smaller than they are. Wow. Isn't it time we factor out the common code in cm, mkhive and freeldr and put it in a static library? GvG

2 1

Re: [ros-diffs] [navaraf] 19636: Don't make cells smaller than they are.
by Hartmut Birr 26 Nov '05

26 Nov '05

navaraf(a)svn.reactos.com wrote: > Don't make cells smaller than they are. > Modified: trunk/reactos/ntoskrnl/cm/regfile.c > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/ntoskrnl/cm/regfile.c* > --- trunk/reactos/ntoskrnl/cm/regfile.c 2005-11-26 13:26:48 UTC (rev 19635) > +++ trunk/reactos/ntoskrnl/cm/regfile.c 2005-11-26 15:21:44 UTC (rev 19636) > @@ -3431,7 +3431,7 @@ > > RtlZeroMemory(*Cell, > CellSize); > > - ((PCELL_HEADER) (*Cell))->CellSize = -CellSize; > > + ((PCELL_HEADER) (*Cell))->CellSize *= -1; > > } > > return STATUS_SUCCESS; > This change is wrong. Possible we have split the cell. In this case, we have to set the new cell size. - Hartmut

1 0

RE: [ros-svn] [chorns] 19566: Speed up compilation of ntoskrnl
by Ge van Geldorp 26 Nov '05

26 Nov '05

> From: chorns(a)svn.reactos.com > > Speed up compilation of ntoskrnl Hmm, an unexpected consequence is that we can no longer enable DPRINTs per file by removing the "#define NDEBUG" statement. At the moment, the first source files included by io.c and cc.c (resp io/adapter.c and cc/cacheman.c) don't define NDEBUG before including debug.h. As a result, all DPRINTs in every file included by io.c/cc.c are enabled. GvG

3 3

Re: [ros-diffs] [gvg] 19618: Sync to Wine-0_9_2:
by Ged Murphy 26 Nov '05

26 Nov '05

2 1

Re: [ros-diffs] [sgasiorek] 19624: fixed reference to PML_TransError
by Thomas Weidenmueller 26 Nov '05

26 Nov '05

sgasiorek(a)svn.reactos.com wrote: > + wprintf(PML_TransError(error, (WCHAR*)errbuf, sizeof(errbuf)/sizeof(WCHAR))); This typecast is kind of useless... - Thomas

1 0

Re: [ros-svn] [sgasiorek] 19570: - changed name of package library to package.dll
by James Tabor 26 Nov '05

26 Nov '05

Hi! sgasiorek(a)svn.reactos.com wrote: > - changed name of package library to package.dll > - fixed PML_TransError function (possibly fixes bug 730) > > > > Added files: > trunk/rosapps/packmgr/lib/package.xml > > Updated files: > trunk/rosapps/packmgr/cmd-line/rosget.xml > trunk/rosapps/packmgr/directory.xml > trunk/rosapps/packmgr/gui/main.c > trunk/rosapps/packmgr/gui/packmgr.xml > trunk/rosapps/packmgr/lib/es.rc > trunk/rosapps/packmgr/lib/main.cpp > trunk/rosapps/packmgr/lib/package.cpp > trunk/rosapps/packmgr/lib/package.h > trunk/rosapps/packmgr/lib/package.hpp > > Deleted files: > trunk/rosapps/packmgr/lib/packlib.xml > [CC] modules/rosapps/packmgr/cmd-line/main.c modules/rosapps/packmgr/cmd-line/main.c: In function `SetStatus': modules/rosapps/packmgr/cmd-line/main.c:123: error: too few arguments to function `PML_TransError' modules/rosapps/packmgr/cmd-line/main.c: In function `Install': modules/rosapps/packmgr/cmd-line/main.c:139: error: too few arguments to function `PML_TransError' modules/rosapps/packmgr/cmd-line/main.c:162: error: too few arguments to function `PML_TransError' modules/rosapps/packmgr/cmd-line/main.c: In function `Show': modules/rosapps/packmgr/cmd-line/main.c:186: error: too few arguments to function `PML_TransError' make[1]: *** [obj-i386/modules/rosapps/packmgr/cmd-line/main.o] Error 1 Thanks, James

2 1

FreeDos32 and ReactOS
by crashfourit 26 Nov '05

26 Nov '05

We could work with Freedos32 (http://freedos-32.sourceforge.net/) with for the dos implimentation. -- My DeviantArt.com page: http://crashfourit.deviantart.com/ My FanFiction.net bio page: http://www.fanfiction.net/u/726606/ My Blog: http://crashfourit.blogspot.com/ America's Debate: http://www.americasdebate.com/

2 2

Re: [ros-dev] Log off reboots!
by TwoTailedFox 25 Nov '05

25 Nov '05

No, the Shutdown/Restart and Log Off portions are in need of a re-write, AFAIK. Since Local User Accounts are not implemented yet, we cannot "Log Off" per se on ReactOS just yet. On 11/25/05, Alex Buell <alex.buell(a)munted.org.uk> wrote: > Has someone confused the Log off menu item with the Shutdown menu item? > When logging off, it reboots. Is this intended? > > -- > http://www.munted.org.uk > > Anyone that thinks an imaginary deity is going to protect them against > earthquakes and hurricanes needs psychiatric help. > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > -- "I had a handle on life, but then it broke"

1 0

TAB+K -> ESC+K
by Royce Mitchell III 25 Nov '05

25 Nov '05

anybody have a problem with me changing Tab+K to Esc+K. I was working in command prompt and accidentally hit the combo when using tab completion. Thanks

2 2

RE: [greatlrd] 19565: implement addbuffer to waveTheard. itcan play wave one time if it is same file in windows
by Ge van Geldorp 25 Nov '05

25 Nov '05

> From: greatlrd(a)svn.reactos.com > > implement addbuffer to waveTheard. it can play wave one time > if it is same file in windows I guess you forgot to commit a header file: [CC] lib/mmdrv/wave.c lib/mmdrv/wave.c: In function `waveThread': lib/mmdrv/wave.c:94: error: syntax error before '*' token lib/mmdrv/wave.c:99: error: `pHdrSearching' undeclared (first use in this function) lib/mmdrv/wave.c:99: error: (Each undeclared identifier is reported only once lib/mmdrv/wave.c:99: error: for each function it appears in.) lib/mmdrv/wave.c:116: warning: implicit declaration of function `waveStart' GvG

2 1

Re: [ros-diffs] [sedwards] 19564: Fix pch usage in most of the rest of crt.lib. Stop the abuse of including io.h, stdio.h and a few others directly. Add a generic license header to those source files that were missing it. There is still a few other headers left to fix and a few files missing pch and license headers
by Alex Ionescu 25 Nov '05

25 Nov '05

Hi Steven, You should include -all- headers in the main PCH,and have the files include only the PCH. This will be much faster. Best regards, Alex Ionescu

1 0

RE: [ros-diffs] [sedwards] 19564: Fix pch usage in most of the rest ofcrt.lib...
by Casper Hornstrup 25 Nov '05

25 Nov '05

How useful ;-) Casper _____ From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of sedwards(a)svn.reactos.com Sent: 25. november 2005 19:07 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [sedwards] 19564: Fix pch usage in most of the rest ofcrt.lib. Stop the abuse of including io.h,stdio.h and a few others directly. Add a generic license header tothose source files that were missing it. There is still a fewother headers left t Modified: trunk/reactos/lib/crt/io/chmod.c --- trunk/reactos/lib/crt/io/chmod.c 2005-11-25 17:13:40 UTC (rev 19563) +++ trunk/reactos/lib/crt/io/chmod.c 2005-11-25 18:05:42 UTC (rev 19564) @@ -1,9 +1,16 @@ +/* + * COPYRIGHT: See COPYING in the top level directory + * PROJECT: ReactOS system libraries + * FILE: lib/crt/?????? + * PURPOSE: Unknown + * PROGRAMER: Unknown + * UPDATE HISTORY: + * 25/11/05: Created + */

1 0

RE: [ros-diffs] [turner] 19541: Read the registry to set the wallpapermode in in WinSta.
by Casper Hornstrup 25 Nov '05

25 Nov '05

CreatedStyleNum? _____ From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of turner(a)svn.reactos.com Sent: 25. november 2005 05:15 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [turner] 19541: Read the registry to set the wallpapermode in in WinSta. Read the registry to set the wallpaper mode in in WinSta. Modified: trunk/reactos/subsys/win32k/ntuser/misc.c _____ Modified: trunk/reactos/subsys/win32k/ntuser/misc.c --- trunk/reactos/subsys/win32k/ntuser/misc.c 2005-11-25 03:50:49 UTC (rev 19540) +++ trunk/reactos/subsys/win32k/ntuser/misc.c 2005-11-25 04:14:59 UTC (rev 19541) @@ -6,7 +6,7 @@ * FILE: subsys/win32k/ntuser/misc.c * PROGRAMER: Ge van Geldorp (ge(a)gse.nl) * REVISION HISTORY: - * 2003/05/22 Created + * 2003/05/22 CreatedStyleNum */ #include <w32k.h> @@ -928,7 +928,18 @@

2 1

RE: [ros-dev] RE: [ros-diffs] [turner] 19541: Read the registry t o set the wallpapermode in in WinSta.
by Murphy, Ged (Bolton) 25 Nov '05

25 Nov '05

lol, I was just thinking the same thing. -----Original Message----- From: Casper Hornstrup [mailto:ch@csh-consult.dk] Sent: 25 November 2005 10:01 To: ros-dev(a)reactos.org Subject: [ros-dev] RE: [ros-diffs] [turner] 19541: Read the registry to set the wallpapermode in in WinSta. CreatedStyleNum? _____ From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of turner(a)svn.reactos.com Sent: 25. november 2005 05:15 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [turner] 19541: Read the registry to set the wallpapermode in in WinSta. Read the registry to set the wallpaper mode in in WinSta. Modified: trunk/reactos/subsys/win32k/ntuser/misc.c _____ Modified: trunk/reactos/subsys/win32k/ntuser/misc.c --- trunk/reactos/subsys/win32k/ntuser/misc.c 2005-11-25 03:50:49 UTC (rev 19540) +++ trunk/reactos/subsys/win32k/ntuser/misc.c 2005-11-25 04:14:59 UTC (rev 19541) @@ -6,7 +6,7 @@ * FILE: subsys/win32k/ntuser/misc.c * PROGRAMER: Ge van Geldorp (ge(a)gse.nl) * REVISION HISTORY: - * 2003/05/22 Created + * 2003/05/22 CreatedStyleNum */ #include <w32k.h> @@ -928,7 +928,18 @@ ************************************************************************ 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-diffs] [jimtabor] 19536: Fix missed files. Svn problem?
by Casper Hornstrup 25 Nov '05

25 Nov '05

Now the "FILE:" header line is wrong. A prime example that these lines get outdated. Casper _____ From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of jimtabor(a)svn.reactos.com Sent: 24. november 2005 23:09 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [jimtabor] 19536: Fix missed files. Svn problem? Fix missed files. Svn problem? Added: trunk/reactos/drivers/multimedia/portcls/ Added: trunk/reactos/drivers/multimedia/portcls/portcls.c Added: trunk/reactos/drivers/multimedia/portcls/portcls.def Added: trunk/reactos/drivers/multimedia/portcls/portcls.h Added: trunk/reactos/drivers/multimedia/portcls/portcls.rc Added: trunk/reactos/drivers/multimedia/portcls/portcls.xml _____ Added: trunk/reactos/drivers/multimedia/portcls/portcls.c --- trunk/reactos/drivers/multimedia/portcls/portcls.c 2005-11-24 21:08:13 UTC (rev 19535) +++ trunk/reactos/drivers/multimedia/portcls/portcls.c 2005-11-24 22:08:38 UTC (rev 19536) @@ -0,0 +1,505 @@ +/* + * ReactOS PortCls Driver + * Copyright (C) 2005 ReactOS Team + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License as published by + * the Free Software Foundation; either version 2 of the License, or + * (at your option) any later version. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not, write to the Free Software Foundation, + * Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA + * + * COPYRIGHT: See COPYING in the top level directory + * PROJECT: ReactOS Sound System + * PURPOSE: Audio Port Class Functions + * FILE: drivers/dd/sound/portcls/portcls.c + * PROGRAMMERS: + * + * REVISION HISTORY: + * 21 November 2005 Created James Tabor + */

3 2

Re: [ros-svn] [sedwards] 19515: more msvc compile fixes by Brezenbak and I
by Hartmut Birr 24 Nov '05

24 Nov '05

sedwards(a)svn.reactos.com wrote: > more msvc compile fixes by Brezenbak and I > > > Hi, this change breaks compiling for me. I get the following error. - Hartmut: gcc -c lib\crt\float\chgsign.c -o .\up\obj-i386\lib\crt\float\chgsign.o -I.\up\obj-i386\lib\crt -Ilib\crt -Ilib\crt\include -D_DISABLE_TIDENTS -D__MINGW_IMPORT=extern -D__USE_W32API -D_WIN32_IE=0x600 -D_WIN32_WINNT=0x501 -D__REACTOS__ -DUSE_MSVCRT_PREFIX -D_MSVCRT_LIB_ -D_MSVCRT_ -D_MT -Iinclude -Iinclude\reactos -Iinclude\libs -Iinclude\drivers -Iinclude\subsys -Iinclude\ndk -Iw32api\include -Iw32api\include\crt -Iw32api\include\ddk -D_M_IX86 -D_X86_ -D__i386__ -DDBG -Wall -momit-leaf-frame-pointer -mpreferred-stack-boundary=2 -ftracer -Os -fno-strict-aliasing -fno-optimize-sibling-calls -Wpointer-arith -g -pipe -Werror gcc -c lib\crt\float\clearfp.c -o .\up\obj-i386\lib\crt\float\clearfp.o -I.\up\obj-i386\lib\crt -Ilib\crt -Ilib\crt\include -D_DISABLE_TIDENTS -D__MINGW_IMPORT=extern -D__USE_W32API -D_WIN32_IE=0x600 -D_WIN32_WINNT=0x501 -D__REACTOS__ -DUSE_MSVCRT_PREFIX -D_MSVCRT_LIB_ -D_MSVCRT_ -D_MT -Iinclude -Iinclude\reactos -Iinclude\libs -Iinclude\drivers -Iinclude\subsys -Iinclude\ndk -Iw32api\include -Iw32api\include\crt -Iw32api\include\ddk -D_M_IX86 -D_X86_ -D__i386__ -DDBG -Wall -momit-leaf-frame-pointer -mpreferred-stack-boundary=2 -ftracer -Os -fno-strict-aliasing -fno-optimize-sibling-calls -Wpointer-arith -g -pipe -Werror In file included from lib\crt\float\chgsign.c:1: lib/crt/include/float.h:94:1: "DBL_MAX_10_EXP" redefined In file included from lib/crt/include/float.h:19, from lib\crt\float\chgsign.c:1: e:/mingw/bin/../lib/gcc/mingw32/3.4.2/include/float.h:97:1: this is the location of the previous definition _make: *** [.\up\obj-i386\lib\crt\float\chgsign.o] Error 1 _make: *** Waiting for unfinished jobs.... In file included from lib\crt\float\clearfp.c:1: lib/crt/include/float.h:94:1: "DBL_MAX_10_EXP" redefined In file included from lib/crt/include/float.h:19, from lib\crt\float\clearfp.c:1: e:/mingw/bin/../lib/gcc/mingw32/3.4.2/include/float.h:97:1: this is the location of the previous definition _make: *** [.\up\obj-i386\lib\crt\float\clearfp.o] Error 1

1 0

Re: [ros-svn] [gvg] 19517: Use inflib
by Thomas Weidenmueller 24 Nov '05

24 Nov '05

gvg(a)svn.reactos.com wrote: > Use inflib I can no longer link usetup compiled with gcc4: obj-i386\lib\inflib\inflib.a(infcore.o): In function `leading_spaces_state': C:/MingW/include/ctype.h:151: undefined reference to `_imp____mb_cur_max' C:/MingW/include/ctype.h:151: undefined reference to `_isctype' C:/MingW/include/ctype.h:151: undefined reference to `_imp____mb_cur_max' C:/MingW/include/ctype.h:151: undefined reference to `_imp___pctype' C:/MingW/include/ctype.h:151: undefined reference to `_isctype' obj-i386\lib\inflib\inflib.a(infcore.o): In function `trailing_spaces_state': C:/MingW/include/ctype.h:151: undefined reference to `_imp____mb_cur_max' C:/MingW/include/ctype.h:151: undefined reference to `_isctype' C:/MingW/include/ctype.h:151: undefined reference to `_imp____mb_cur_max' C:/MingW/include/ctype.h:151: undefined reference to `_imp___pctype' C:/MingW/include/ctype.h:151: undefined reference to `_isctype' obj-i386\lib\inflib\inflib.a(infcore.o): In function `line_start_state': C:/MingW/include/ctype.h:151: undefined reference to `_imp____mb_cur_max' C:/MingW/include/ctype.h:151: undefined reference to `_isctype' C:/MingW/include/ctype.h:151: undefined reference to `_imp___pctype' obj-i386\lib\inflib\inflib.a(infcore.o): In function `key_name_state': C:/MingW/include/ctype.h:151: undefined reference to `_imp____mb_cur_max' C:/MingW/include/ctype.h:151: undefined reference to `_isctype' C:/MingW/include/ctype.h:151: undefined reference to `_imp___pctype' obj-i386\lib\inflib\inflib.a(infcore.o): In function `value_name_state': C:/MingW/include/ctype.h:151: undefined reference to `_imp____mb_cur_max' C:/MingW/include/ctype.h:151: undefined reference to `_isctype' C:/MingW/include/ctype.h:151: undefined reference to `_imp___pctype' obj-i386\lib\inflib\inflib.a(infcore.o): In function `eol_backslash_state': C:/MingW/include/ctype.h:151: undefined reference to `_imp____mb_cur_max' C:/MingW/include/ctype.h:151: undefined reference to `_isctype' C:/MingW/include/ctype.h:151: undefined reference to `_imp___pctype' mingw32-make: *** [output-i386\subsys\system\usetup\usetup.exe] Error 1 - Thomas

2 2

Re: [ros-general] Re: Freeldr UI modifications
by João Jerónimo Barata de Oliveira 24 Nov '05

24 Nov '05

Alex Ionescu wrote: > Here are some changes I made to Freeldr last night. Also to ntoskrnl and the HAL. Booting takes 4 seconds now and seems much faster, it probably is a bit too. > > http://www.relsoft.net/rosldr1.png > http://www.relsoft.net/rosldr2.png In my opinion, it was best before with more graphical design... Now it's just like NTLDR, nothing special... I even think you would better entirely change FreeLDR configuration... I don't like poly-bootloaders (for distinguishing from multiboot, which is a standard) that run from disk partitions... In my opinion, the ideal boot loader: MBR boot code (446 bytes)... loads some contents of the 1st cylinder of the disk (after the MBR sector, it's usually empty) Contents of that space: configuration of the boot loader (no config reading from partitions while running this first stage boot loader); executable that shows the menu accordingly to the config it should read; some routines (possibly modules) for loading specific OSs, becuase they aren't all started the same way; and parhaps an image in some format... MBR boot code would load (and jump to) the menu binary, which reads the config and builds the menu accordingly... after knowing the user decision, it would read the right routine for that OS... That routine would, then, do what it has to do (i.e. load the kernel, switch to protected mode if that's the case, etc) or just chainload to another partition's boot code (on filesystems that allow it)... Well, indeed there's a boot loader that works very much like this... GRUB uses that sector to store some parts of the program... but I don't know if it stores there the config and I think that would be essencial (because, in my opinion, a boot loader needs to be independent from operating systems so, for example, there could be configuration floppy disks for changing its configuration)... As Grub is very similar (or parhaps identic) to my description of the ideal boot loader, I would like you to chose Grub as ReactOS boot loader (either by modifying it's configuration or by installing it from scratch, depending on the pré-install configuration)... That is, of course, also making ReactOS multiboot-compilant if it isn't already (It doesn't look like that)... I don't claim to be a pioneer on those ideas... But I think you are following the same path as Microsoft (i.e. I am the main OS, chainload to my partition and then I can load other OSs if you want) and it's not good... I think a boot loader must be on its own place, and MBR (and those bytes between MBR and the partitions) is the right place for a boot loader... Finally, I'm merelly giving my opinion... if you think that there are other priorities, I understand that... of course you have many other things to implement/stabilise/improve... I'm not very skilled in programming, otherwise I would help... João Jerónimo _______________________________________________________ Yahoo! Acesso Grátis: Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com/

2 1

Faster compilation
by Casper Hornstrup 23 Nov '05

23 Nov '05

Hi. I've been working on getting ReactOS to build faster. By compiling fewer, but larger source files (compilation units), we can build ReactOS much faster. I estimate that we can build ReactOS 200-300% faster if we do this. See the attached patch for kernel32 for an example. On my slow box (Windows), I get the following numbers: kernel32 (1 compilation unit per file): build time: 32 seconds space consumed by object files: 52MB kernel32 (fewer compilation units): build time: 11 seconds space consumed by object files: 14MB Another advantage is the less disk space requirements. I estimate ~700-800MB will be needed for object files after this change. Compare that to the 2GB that is needed today. Gé did some testing on Linux: kernel32 (1 compilation unit per file): build time: 11.3 seconds kernel32 (fewer compilation units): build time: 4.4 seconds Some issues: * You can't mix source code files with different file name extensions in the same compilation unit (currently only *.c is supported) * There must not be duplicate definitions in the same compilation unit even though it is spread over several source code files (duplicating code is bad practice anyway). * Like when you compile a big source file, memory usage during compilation is higher than when compiling several smaller source code files, one at a time. This puts a practical limit on how large the compilation unit can be. * Every source code file in the compilation unit is recompiled after a change to one or more source code files within the compilation unit. The time needed for linking may however be significantly less (due to the fewer, much smaller object files) so it may be faster in the end. * Pre-compiled headers are not easy to support, while at the same time maintaining compatibility with MSVC and one source code file per compilation unit mode. Currently PCHs are disabled for a module if the module has compilation units with more than one source code file in it. While compiling kernel32 as one big compilation unit, GCC required 60MB of virtual memory. What is an acceptable memory usage? It determines how large we can make the compilation units and affects how fast we can build ReactOS. Now we have 300+ modules that need to be split into compilation units. Are there any volunteers that wish to help with these tasks? Thoughts? Casper

2 2

PC poll
by Ged Murphy 23 Nov '05

23 Nov '05

Just a quick note to say I set up the Project Coordinator poll this morning. It appears the auto mail functionality isn't working. It can be found here : http://www.reactos.org/forum/viewtopic.php?t=1193

2 1

Java and Mono
by Rick Langschultz 23 Nov '05

23 Nov '05

I have been developing a port of Java and Mono for ReactOS. Is anyone doing this already???

5 9

RE: [ros-diffs] [sedwards] 19482: porting fixes
by Casper Hornstrup 23 Nov '05

23 Nov '05

Why not just remove it, if it isn't needed? _____ From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of sedwards(a)svn.reactos.com Sent: 23. november 2005 07:34 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [sedwards] 19482: porting fixes porting fixes Modified: trunk/reactos/apps/utils/net/tracert/tracert.c _____ Modified: trunk/reactos/apps/utils/net/tracert/tracert.c --- trunk/reactos/apps/utils/net/tracert/tracert.c 2005-11-23 06:02:15 UTC (rev 19481) +++ trunk/reactos/apps/utils/net/tracert/tracert.c 2005-11-23 06:33:19 UTC (rev 19482) @@ -28,7 +28,7 @@ */ -#include <windows.h> +//#include <windows.h> #include <winsock2.h> #include <tchar.h> #include <stdio.h> @@ -726,7 +726,7 @@ */ int main(int argc, char* argv[]) { - if (!ParseCmdline(argc, _argv)) return -1; + if (!ParseCmdline(argc, argv)) return -1; Driver();

2 1

Security Suite
by David Hinz 23 Nov '05

23 Nov '05

As recently the discussion about a firewall and a virus-scanner came up again, I thought of a new thing, that is a bit different than the already known things. My idea is not to use a firewall and a virus-scanner, I want to create a new service, that may be configured by a gui, a console app or by other apps, that might use some of its features. This service should do the following things: - Having a look at the network traffic, which includes the following: - Controlling, which application may use the network connections - Controlling, how many traffic they cause, which could warn the user about suspicious actions - Watching the running processes for unusual events - Checking every file that is read or written for viruses - Scanning the http-traffic for ads and viruses But the most important thing for me is that if this service is shutdown without the user agreeing to that, which may be checked by ntoskrnl, the user should be informed about it and nearly all network traffic should be blocked. Then the network-card should be deactivated, all userprocesses should be paused and all drives should be checked for viruses. I think this is hard, but it will make it much harder for worms to spread, as they don't have the chance to deactivate our securitysuite and so they will be detected within two days and if they try to shutdown the securitysuite they have no chance to spread. That would be more secure than any other existing OS. This are just a few thoughts, feel free to change it the way you like it. Greets, David Hinz

9 15

RE: [ros-diffs] [cwittich] 19320: got a lot of crypt32 stuff working
by Casper Hornstrup 22 Nov '05

22 Nov '05

We cant send this back to Wine so were going to get lots of conflicts when synchronizing with Wine and thus wasting a lot of Gé's time. What is needed is to make the ReactOS environment more like Wine or submit patches to Wine to make the Wine environment more like Windows' environment. So removing WINE_EXCEPTION_FILTER is not the way to do it since then it won't work on Wine. ReactOS grew 40% in 2004 just because of reusing code from Wine, so sharing code is definitely beneficial to both ReactOS and Wine.

5 16

Call for discussion: release process
by Ge van Geldorp 22 Nov '05

22 Nov '05

Our current release process is documented at http://www.reactos.org/wiki/index.php/Release_Management_Overview. With the outcome of the TC function description vote, we need to change it to incorporate the TC role in the release process. I'd like to propose the following changes: - change "Once the project coordinator signals that a release is to be made, dates are set for all three stages and the release process begins." to "Once the testing coordinator (in consultation with the release engineer) signals that a release is to be made, tentative dates are set for all three stages and the release process begins.". Rationale: TC involvement, dates are not fixed but dependent on blocker bugs. - change "At the time of feature freeze, the first release candidate is produced by the release engineer." to "At the time of feature freeze, a release preview is produced by the release engineer.". Rationale: "release candidate" is probably not the best term to describe the state of the .iso. "Beta" is confusing since we're in alpha. "Preview" seems a nice generic term. - change "Code freeze is the next stage of the release process." to "Code freeze, the next stage of the release process, is entered when the testing coordinator indicates that all blocker bugs in the release branch have been fixed.". Rationale: TC involvement. - change "At the time of code freeze, the second and final release candidate is produced by the release engineer." to "At the time of code freeze, a release candidate is produced by the release engineer.". Rationale: I think we can safely call this one a release candidate. Gé van Geldorp.

1 2

RE: [hpoussin] 19463: Fix sublanguage IDs in .rc files:
by Ge van Geldorp 22 Nov '05

22 Nov '05

> From: hpoussin(a)svn.reactos.com > > Fix sublanguage IDs in .rc files: > - LANG_ENGLISH -> SUBLANG_ENGLISH_US > - LANG_JAPANESE -> SUBLANG_DEFAULT > - others -> SUBLANG_NEUTRAL For reference, this is the search order currently used by ReactOS (copied from Wine, I'm not claiming Windows uses this same exact search order too, haven't tested): 1. specified language 2. specified language with neutral sublanguage 3. neutral language with neutral sublanguage if no explicitly specified language 4. current thread locale language 5. user locale language 6. user locale language with neutral sublanguage 7. system locale language 8. system locale language with neutral sublanguage 9. LANG_ENGLISH/SUBLANG_DEFAULT If searching for all of these fails, the first resource item found in the resource file matching the resource type and resource id is used. You can find this in lib/ntdll/ldr/res.c function LdrFindResource_U(). GvG

1 0

RE: [ros-dev] Change of Project Coordinator
by Murphy, Ged (Bolton) 21 Nov '05

21 Nov '05

Considering there were no objections to the job description now in the wiki, it would be good to get the ball rolling again on this and start up the 1 week discussion period. Can any candidates wishing to put their name forward for this role please do so. Current list includes: - Steven Edwards. http://www.reactos.org/wiki/index.php/ReactOS_Project_Coordinator -----Original Message----- From: Casper Hornstrup [mailto:ch@csh-consult.dk] Sent: 10 November 2005 10:41 To: 'ReactOS Development List' Subject: RE: [ros-dev] RE: Change of Project Coordinator Better draft and vote on the project coordinator description first. It's good to know the job description when you apply for a job ;-) Casper > -----Original Message----- > From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Murphy, Ged > (Bolton) > Sent: 10. november 2005 10:14 > To: 'ReactOS Development List' > Subject: [ros-dev] RE: Change of Project Coordinator > > Jason Filby wrote: > > > I've decided that now is the best time to step down as Project > > Coordinator. The process to vote for a new PC will be - as previously > > decided for this type of decision - that only registered committers > > can vote. > > > This topic seems to have died a death, so I'm bringing it back up now as the > new voting system is in place. > I was speaking to Steven last night who advised he is now available to run > as PC. > Can any other candidates put their name forward again for the 1 week > discussion period. > > 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] [weiden] 19406: fixed the ProbeForWriteLargeInteger and ProbeForWriteUlargeInteger macros
by Thomas Weidenmueller 21 Nov '05

21 Nov '05

weiden(a)svn.reactos.com wrote: > fixed the ProbeForWriteLargeInteger and ProbeForWriteUlargeInteger macros I'm sorry, I meant to write ProbeForReadLargeInteger and ProbeForReadUlargeInteger. - Thomas

1 0

RE:[cwittich] 19402: WINE 0.9.1 vendor drop
by Ge van Geldorp 21 Nov '05

21 Nov '05

> From: cwittich(a)svn.reactos.com > > WINE 0.9.1 vendor drop > > Added files: > vendor/wine/dlls/avifil32/Wine-0_9_1/ Can you "svn copy svn://svn.reactos.org/vendor/wine/dlls/avifil32/current svn://svn.reactos.org/vendor/wine/dlls/avifil32/Wine-0_9_1" instead of re-adding the files to .../Wine-0_9_1? By using "svn copy" you establish a common ancestry between .../current and .../Wine-0_9_1. (Of course, you need to svn delete .../Wine-0_9_1 now before you can do the svn copy). Thanks, GvG.

3 3

RE: [ros-svn] [cwittich] 19403: import avifil32 from WINE 0.9.1
by Ge van Geldorp 21 Nov '05

21 Nov '05

> From: cwittich(a)svn.reactos.com > > import avifil32 from WINE 0.9.1 Another case where you should use "svn copy". The vendor import process is described here: http://www.reactos.org/wiki/index.php/Using_code_from_other_projects GvG

1 0

DLL registration during setup: new rbuild task?
by Ge van Geldorp 21 Nov '05

21 Nov '05

In Wine, you get a popup if your program tries to load a WebBrowser control. That popup asks you if you want to download the Mozilla control. This is implemented in shdocvw.dll. Since we use the same code in ReactOS, I expected to get the same popup, but it doesn't show, instead ibrowser (as an example of an app that tries to load a WebBrowser control) just says "Sorry - no web browser control could be loaded". The reason that it doesn't work the same as in Wine is that the DllRegisterServer() procedure of shdocvw.dll is never called during setup. If you manually register shdocvw.dll ("regsvr32 shdocvw.dll") you do get the popup. There are 2 ways to fix this: we could hack it and add the registry entries (class registration) to hivecls.inf, or we can properly implement DLL registration during (second stage) setup. Although I don't mind cutting a corner every now and then, in this case my preference is to implement DLL registration during setup. That means we'll need an .inf file to describe which DLLs need to be registered. Windows has a syssetup.inf file for this, with a [OleControlDlls] section listing the DLLs to register/install. We can of course manually maintain a syssetup.inf file in bootdata, but this means one more file to keep up to date when you add a module. So I was thinking, maybe we could add an 'autoregister="R"' (indicating setup should call DllRegisterServer(), "I" to indicate it should call DllInstall() and "B" to indicate it should call both) attribute to <module> in the .xml file. Then rbuild should be able to automatically generate a syssetup.inf file. We could go one step further and also generate the bootdata/packages/reactos.dff file in a similar way. So, does this sound like the correct approach? If so, would anyone be interested in implementing the rbuild side of things? I can take care of the stuff that needs to be done during setup, but I've never worked on rbuild before. Gé van Geldorp.

4 8

RE: [ros-dev] 0.3 release plan - Again
by Murphy, Ged (Bolton) 20 Nov '05

20 Nov '05

USB is not a prerequisite for 0.3.0 so you might have to hold your breath for a little while longer. -----Original Message----- From: David Johnson [mailto:davidjohnson.johnson@gmail.com] Sent: 17 November 2005 14:55 To: ReactOS Development List Subject: Re: [ros-dev] 0.3 release plan - Again I am waiting with bated breth for 0.3. I have a test system that is waiting for USB. As soon as USB is working I will put ROS on my real hardware for testing. I hope this will be a help to the group. ************************************************************************ 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

6 6

Re: [ros-diffs] [ion] 19352: - Reimplement Fast Mutex implementation in HAL/NT to be compatible with the real implementation. (Fast Mutex needs to raise IRQL).
by Hartmut Birr 20 Nov '05

20 Nov '05

ion(a)svn.reactos.com wrote: > - Reimplement Fast Mutex implementation in HAL/NT to be compatible with the real implementation. (Fast Mutex needs to raise IRQL). > - Implement ExEnterCriticalRegionAndAcquireFastMutexUnsafe and ExReleaseFastMutexUnsafeAndLeaveCriticalRegion. > - Make win32k use those two new functions so that it can continue running at PASSIVE_LEVEL. > - Remove CcBrokenMutex and use the new APIs instead. > - Implement and export ntoskrnl version of Fast Mutex > - Update headers for new fast-mutex definition and API exports. > - Fix RemoveEntryList in NDK. > - Add exfuncs.h to NDK. > - Fix path in mmtypes.h in NDK to be compatible to how it shoudl be included. > *Modified: trunk/reactos/hal/halx86/generic/fmutex.c* > --- trunk/reactos/hal/halx86/generic/fmutex.c 2005-11-19 21:07:25 UTC (rev 19351) > +++ trunk/reactos/hal/halx86/generic/fmutex.c 2005-11-19 22:13:35 UTC (rev 19352) > +VOID > +FASTCALL > +ExAcquireFastMutex(PFAST_MUTEX FastMutex) > > { > > - KeEnterCriticalRegion(); > - ExAcquireFastMutexUnsafe(FastMutex); > > + KIRQL OldIrql; > + > + /* Raise IRQL to APC */ > + OldIrql = KfRaiseIrql(APC_LEVEL); > + > + /* Decrease the count */ > + if (InterlockedDecrement(&FastMutex->Count)) > + { > + /* Someone is still holding it, use slow path */ > + FastMutex->Contention++; > + KeWaitForSingleObject(&FastMutex->Gate, > + WrExecutive, > + WaitAny, > + FALSE, > + NULL); > + } > + > + /* Set the owner and IRQL */ > + FastMutex->Owner = KeGetCurrentThread(); > + FastMutex->OldIrql = OldIrql; > > } > Hi, this piece of code is wrong. If we terminating a thread, which waits on something, we do unblock the thread. The thread must check, if it got the lock, if not it must wait again. - Hartmut

2 4

ReactOS not installable
by Hartmut Birr 20 Nov '05

20 Nov '05

Hi, I'm not able to install ReactOS from the current trunk. It seems, that the new FastMutex implementation is broken. - Hartmut lib\rtl\error.c:910) RTL: RtlNtStatusToDosErrorNoTeb(0xc0): no valid W32 error mapping (lib\rtl\error.c:910) RTL: RtlNtStatusToDosErrorNoTeb(0xc0): no valid W32 error mapping (subsys\win32k\ntuserAssertion 'InterlockedIncrement((PLONG)(&_locked)) == 1' failed at subsys\win32k\ntuser\msgqueue.c line 1318 KeBugAssertion 'InterlockedIncrement((PLONG)(&_locked)) == 1' failed at subsys\win32k\ntuser\msgqueue.c line 1318 KeBugC(drivers\fs\np\fsctrl.c:25) NpfsListeningCancelRoutine() called \window.c:581) thread cleanup: while destroy wCheckWithTf at ntoskrnl\ke\i386\exp.c:1236 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 Technical information: *** STOP: 0x0000001E (0x80000003,0x8006a721,0x812324e8,0x8173ba28) *** ntoskrnl.exe - Address 0x8006a721 base at 0x80000000, DateStamp 0x0 Breakpoint Exception: 3(0) Processor: 0 CS:EIP 8:8006a721 <ntoskrnl.exe:6a721 ({standard input}:23 ())> cr2 81737dfc cr3 1f12d000 Proc: 80f9a050 Pid: 78 <csrss.exe> Thrd: 812324e8 Tid: b0 DS 23 ES 23 FS 30 GS 0 EAX: 00000000 EBX: 9dc08cde ECX: 9e2f8a18 EDX: 00000000 EBP: 9e2f8c60 ESI: 9dc116b0 ESP: 9e2f8be4 EDI: 8d709120 EFLAGS: 00000286 kESP 9e2f8be4 kernel stack base 9e2f6000 Frames: <win32k.sys:5ea58 (subsys/win32k/ntuser/msgqueue.c:1318 (co_MsqWaitForNewMessages))> <win32k.sys:58aa6 (subsys/win32k/ntuser/message.c:948 (co_IntWaitMessage))> <win32k.sys:58d3a (subsys/win32k/ntuser/message.c:1051 (NtUserGetMessage))> <ntoskrnl.exe:647ca ({standard input}:373 (KiSystemService))> <user32.dll:310d9 (lib/user32/windows/message.c:1169 (GetMessageW))>

1 0

Re: [ros-svn] [weiden] 19334: - define STATUS_* codes correctly in winnt.h and ntstatus.h
by James Tabor 20 Nov '05

20 Nov '05

Hi, We need to check RosApps too. Thanks, James [CC] modules/rosapps/sysutils/ctm/ctm.c In file included from include/ndk/umtypes.h:18, from include/ndk/ntndk.h:19, from modules/rosapps/sysutils/ctm/ctm.c:45: w32api/include/ntstatus.h:30:1: "DBG_EXCEPTION_HANDLED" redefined In file included from w32api/include/windef.h:253, from w32api/include/windows.h:49, from modules/rosapps/sysutils/ctm/ctm.c:35: w32api/include/winnt.h:251:1: this is the location of the previous definition In file included from include/ndk/umtypes.h:18, from include/ndk/ntndk.h:19, from modules/rosapps/sysutils/ctm/ctm.c:45: w32api/include/ntstatus.h:31:1: "DBG_CONTINUE" redefined In file included from w32api/include/windef.h:253, from w32api/include/windows.h:49, from modules/rosapps/sysutils/ctm/ctm.c:35: w32api/include/winnt.h:252:1: this is the location of the previous definition In file included from include/ndk/umtypes.h:18, from include/ndk/ntndk.h:19, from modules/rosapps/sysutils/ctm/ctm.c:45: w32api/include/ntstatus.h:34:1: "DBG_TERMINATE_THREAD" redefined In file included from w32api/include/windef.h:253, from w32api/include/windows.h:49, from modules/rosapps/sysutils/ctm/ctm.c:35: w32api/include/winnt.h:253:1: this is the location of the previous definition In file included from include/ndk/umtypes.h:18, from include/ndk/ntndk.h:19, from modules/rosapps/sysutils/ctm/ctm.c:45: w32api/include/ntstatus.h:35:1: "DBG_TERMINATE_PROCESS" redefined In file included from w32api/include/windef.h:253, from w32api/include/windows.h:49, from modules/rosapps/sysutils/ctm/ctm.c:35: w32api/include/winnt.h:254:1: this is the location of the previous definition In file included from include/ndk/umtypes.h:18, from include/ndk/ntndk.h:19, from modules/rosapps/sysutils/ctm/ctm.c:45: w32api/include/ntstatus.h:36:1: "DBG_CONTROL_C" redefined <Snip. ..> w32api/include/ntstatus.h:772:1: "STATUS_FLOAT_MULTIPLE_FAULTS" redefined In file included from w32api/include/windef.h:253, from w32api/include/windows.h:49, from modules/rosapps/sysutils/ctm/ctm.c:35: w32api/include/winnt.h:245:1: this is the location of the previous definition In file included from include/ndk/umtypes.h:18, from include/ndk/ntndk.h:19, from modules/rosapps/sysutils/ctm/ctm.c:45: w32api/include/ntstatus.h:773:1: "STATUS_FLOAT_MULTIPLE_TRAPS" redefined In file included from w32api/include/windef.h:253, from w32api/include/windows.h:49, from modules/rosapps/sysutils/ctm/ctm.c:35: w32api/include/winnt.h:246:1: this is the location of the previous definition In file included from include/ndk/umtypes.h:18, from include/ndk/ntndk.h:19, from modules/rosapps/sysutils/ctm/ctm.c:45: w32api/include/ntstatus.h:786:1: "STATUS_REG_NAT_CONSUMPTION" redefined In file included from w32api/include/windef.h:253, from w32api/include/windows.h:49, from modules/rosapps/sysutils/ctm/ctm.c:35: w32api/include/winnt.h:247:1: this is the location of the previous definition In file included from include/ndk/umtypes.h:18, from include/ndk/ntndk.h:19, from modules/rosapps/sysutils/ctm/ctm.c:45: w32api/include/ntstatus.h:1114:1: "STATUS_SXS_EARLY_DEACTIVATION" redefined In file included from w32api/include/windef.h:253, from w32api/include/windows.h:49, from modules/rosapps/sysutils/ctm/ctm.c:35: w32api/include/winnt.h:248:1: this is the location of the previous definition In file included from include/ndk/umtypes.h:18, from include/ndk/ntndk.h:19, from modules/rosapps/sysutils/ctm/ctm.c:45: w32api/include/ntstatus.h:1115:1: "STATUS_SXS_INVALID_DEACTIVATION" redefined In file included from w32api/include/windef.h:253, from w32api/include/windows.h:49, from modules/rosapps/sysutils/ctm/ctm.c:35: w32api/include/winnt.h:249:1: this is the location of the previous definition make: *** [obj-i386/modules/rosapps/sysutils/ctm/ctm.o] Error 1

2 1

Announce mailing list, newsletter, TC & automated testing
by Drew Scott Daniels 19 Nov '05

19 Nov '05

Hi, It'd be nice if the announcement mailing list was still used. I'd suggest announcing the weekly newsletter in order to keep the list alive between releases. Can the "splash" newsletter be marked as dead? I enjoyed splash's RSS feed. Even more I'd enjoy if the ReactOS (ros) newsletter could become part of kernel cousin or have alike services. The job of the TC came up recently, and thus automated testing. Does the wine test suite run on ReactOS (it runs on Windows and wine)? Would it's results be useful to the TC? Could it be extended? Maybe it needs to be supplemented by something else. Codeweavers have software for automated testing that may be worth looking at too. Drew Daniels Resume: http://www.boxheap.net/ddaniels/resume.html

2 3

RE: [ros-diffs] [ion] 19327: Due to CcRos's abusive usage and dep endency on our broken Fast Mutex implementation, Fast Mutex can't be fixe d until the Cc Rewrite is complete. Since that seems to take longer and w e've identified drivers which need the corre
by Murphy, Ged (Bolton) 19 Nov '05

19 Nov '05

lmao @ these function names ..... -----Original Message----- From: ion(a)svn.reactos.com [mailto:ion@svn.reactos.com] Sent: 18 November 2005 18:52 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [ion] 19327: Due to CcRos's abusive usage and dependency on our broken Fast Mutex implementation, Fast Mutex can't be fixed until the Cc Rewrite is complete. Since that seems to take longer and we've identified drivers which need the correct F +VOID +FASTCALL +CcAcquireBrokenMutex(PFAST_MUTEX FastMutex); + +VOID +FASTCALL +CcReleaseBrokenMutex(PFAST_MUTEX FastMutex); + +BOOLEAN +FASTCALL +CcTryToAcquireBrokenMutex(PFAST_MUTEX FastMutex); + ************************************************************************ 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-diffs] [hbirr] 19329: - Changed all registry functions to WCHAR.
by Alex Ionescu 18 Nov '05

18 Nov '05

hbirr(a)svn.reactos.com wrote: >- Changed all registry functions to WCHAR. >- Implemented packed/unpacked names for keys and values. >- Fixed the hash values for very short data. >- Fixed the debug build. >- Don't search for a serial mouse, if the port is used for debug prints. > Hi Hartmut, Microsoft have managed to write their Cm code in a very portable way so that the Hv* (Hive) and Cm* (NT Config Manager) APIs are very seperated. The result of this is that they've been able to share the registry code between the kernel and the boot loader. Is there any way we can do the same? Certaintly having two pieces of code that are very similar but have subtle differences creates only more avenues for bugs. (Casper, you agree?) Best regards, Alex Ionescu

2 1

[Fwd: [ros-general] BIOS]
by David Hinz 18 Nov '05

18 Nov '05

jh schrieb: > From dev mailing list archive > >> From bblaauw at home.nl Thu Nov 17 16:09:23 2005 >> From: bblaauw at home.nl (Bernd Blaauw) >> Date: Thu Nov 17 16:12:08 2005 >> Subject: [ros-dev] 0.3 release plan - Again >> >> Would "USB working" also mean "boot from USB" ? Not even MS allows this. >> Sadly no PC BIOS supports "boot from FireWire", like Apples do. Guess >> we'd need LinuxBIOS for that, as current motherboard manufacturers don't >> want to pay AMI/Phoenix/Award for including the "boot from firewire" >> >module. >> >> Bernd >> > > Would these be of any interest. > > http://freebios.sourceforge.net/ > > http://www.openbios.info/ > > I am not subscribed to the dev mailing list, so does anyone want to > pass this on. > > Regards, > jh > _______________________________________________ > ros-general mailing list > ros-general(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-general >

1 0

Re: [ros-svn] [sedwards] 19259: created crt public headers directory. Moved excpt.h there
by Thomas Weidenmueller 18 Nov '05

18 Nov '05

sedwards(a)svn.reactos.com wrote: > created crt public headers directory. Moved excpt.h there > > > Added files: > trunk/reactos/w32api/include/crt/ > trunk/reactos/w32api/include/crt/excpt.h > > Updated files: > trunk/reactos/ReactOS.xml > > Deleted files: > trunk/reactos/w32api/include/excpt.h This change or r19260 causes compiling with GCC4 to fail: [CC] apps\utils\ps\ps.c In file included from include/ndk/ntndk.h:52, from apps\utils\ps\ps.c:28: include/ndk/rtltypes.h:544: error: conflicting types for 'PEXCEPTION_HANDLER' w32api/include/crt/excpt.h:56: error: previous declaration of 'PEXCEPTION_HANDLER' was here mingw32-make: *** [obj-i386\apps\utils\ps\ps.o] Error 1 - Thomas

2 1

RE: [ros-dev] Re: [ros-diffs] [gedmurphy] 19312: Improve stopping control of the service
by Murphy, Ged (Bolton) 18 Nov '05

18 Nov '05

> -----Original Message----- > From: Thomas Weidenmueller [mailto:w3seek@reactos.com] > Sent: 18 November 2005 12:03 > To: ReactOS Development List > Subject: Re: [ros-dev] Re: [ros-diffs] [gedmurphy] 19312: > Improve stopping control of the service > > > Murphy, Ged (Bolton) wrote: > > This function is new to me. > Now that you're writing multithreaded code it's about time to learn > about these functions ;) > > > I'm just doing a bit of research on it now to better > understand it, but > > could you just give me a bit of background of the > difference between this, > > and using something like a mutex or CS, and why it's better in this > > scenario? > Of course you can use mutexes or critical sections, but for > this purpose > interlocked operations are much more lightweight because with > mutexes or > critical sections you'd have to protect the read operation as > well. The > Interlocked* functions basically guarantee that a certain > operation on a > variable shared by multiple threads is performed in an atomic > matter. I > probably should mention that reads are always atomic, so reading a > variable with the size smaller or equal as the size of a > general purpose > register does not need to be protected, writes however have > to be protected. > > You should read the following articles: > http://msdn.microsoft.com/library/default.asp?url=/library/en- > us/dllproc/base/interlocked_variable_access.asp > http://blogs.msdn.com/oldnewthing/archive/2004/09/15/229915.aspx Thanks for the info, much appreciated. I've been reading up on Interlocked Variable Access this morning and have now implemented it into the code. 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-dev] Re: [ros-diffs] [gedmurphy] 19312: Improve stopping control of the service
by Murphy, Ged (Bolton) 18 Nov '05

18 Nov '05

> -----Original Message----- > From: Thomas Weidenmueller [mailto:w3seek@reactos.com] > Sent: 17 November 2005 23:38 > To: ReactOS Development List > Subject: Re: [ros-dev] Re: [ros-diffs] [gedmurphy] 19312: > Improve stopping control of the service > > > Ged Murphy wrote: > > Could you explain what you mean? > As you want to change the value of the variables which are used in a > multithreaded environment you need to used the Interlocked* > functions to > ensure an atomic change in all environments (UP, MP, ...), and also to > make sure it's portable. > > > Those variables are only modified within the base thread, all other > > threads just check the value and act upon it. > > Why would that not be thread safe? > You're assuming the code will only run on a x86 system. In > fact, as long > as the variables are aligned properly it is an atomic operation. But > don't forget the other architectures and possibly upcoming > technologies > based on x86 that could void this assumption. > > I have to admit that the code wouldn't break, even in circumstances > where the operation wouldn't be atomic, but technically the code still > isn't thread-safe this way. > > - Thomas This function is new to me. I'm just doing a bit of research on it now to better understand it, but could you just give me a bit of background of the difference between this, and using something like a mutex or CS, and why it's better in this scenario? 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-dev] Microsoft Office files in the trunk
by Murphy, Ged (Bolton) 18 Nov '05

18 Nov '05

Mike Swanson wrote: > In the branch of press-media, there are two documents currently. An MS > Word and MS PowerPoint document. > > I'm calling for SVN committers for _no more_ MS Office documents. They > are a proprietary format, of which not all the features are currently > known. I recommend instead the use of OASIS OpenDocument. Not only > does it save much space, but it also does not contain any secrets in > which need to be reverse engineered to discover. > [...] > > Please, for the good of the project, use the free OpenDocument format. > If not for the reason of being open or free, but simply for the fact > that it ensures that everybody will be able to view such documents (no > need to buy any pricey office suites here!). I disagree with this. I don't know how to use oo.o or variants, and I don't intend on learning something I have no interest in. I'm currently putting together a presentation for the speeches I have coming up on ReactOS. If a rule was put in place where we could only commit OpenDocument files, I would simply not put it into the repository and would instead share it with anyone who wanted it via email. This isn't because I'm being awkward, it's because I have no time or interest to learn a new office suite .... and I certainly don't want to install oo.o on my machine. I suppose it's this attitude which keeps MS Office up as a monopoly, which now make me realise why they don't want to support OpenDocument. ************************************************************************ 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

6 7

Re: [ros-diffs] [gedmurphy] 19312: Improve stopping control of the service
by Thomas Weidenmueller 17 Nov '05

17 Nov '05

gedmurphy(a)svn.reactos.com wrote: > Improve stopping control of the service > > @@ -137,14 +137,14 @@ > > { > case SERVICE_CONTROL_SHUTDOWN: /* fall through */ > case SERVICE_CONTROL_STOP: > > - bShutDownFlag = TRUE; > > + bShutDown = TRUE; > > UpdateStatus(SERVICE_STOP_PENDING, -1); > break; > case SERVICE_CONTROL_PAUSE: > > - bPauseFlag = TRUE; > > + bPause = TRUE; > > break; > case SERVICE_CONTROL_CONTINUE: > > - bPauseFlag = FALSE; > > + bPause = FALSE; You might want to use InterlockedExchange to make it thread-safe. - Thomas

2 2

RE: [ros-svn] [gvg] 19303: Wine-0_9_1 vendor import
by Ge van Geldorp 17 Nov '05

17 Nov '05

> From: gvg(a)svn.reactos.com > > Wine-0_9_1 vendor import "svn update" will probably fail, you'll need to delete lib\dplay + lib\dplayx and do a second "svn update". Sorry about this, there seems to be no way around it. GvG

4 5

Freeldr Question
by Alex Ionescu 17 Nov '05

17 Nov '05

Hi, Freeldr currently contains an ugly (imo) wrapper around the GUI where every drawing operation is supposed to have multiple "modes" (some fancy 3d gizmo whizmo GUI and the normal text-mode interface). I would really like to simply this interface and make the drawing operations much simpler and just draw, instead of going through all the hoops they do now. But before I do, does anyone have any objections? Is anyone working on fancy 3D GUI for Freeldr, or can I go ahead with my changes? Note nothing would change to the user, everything will look and act the exact same way as it does now. Best regards, Alex Ionescu

4 14

CodePage Reg Key Error at Boot
by James Tabor 17 Nov '05

17 Nov '05

Hi, I'm getting "Couldn't open CodePage registry key. With OK". I copied freeldr.sys and the rest and reinstall everything, including config files from hives. Installs and go. 1st install system, 2nd reboot ok run fine, and 3rd reboot and get the above error at freeldr. Revision: 18820 Node Kind: directory Schedule: normal Last Changed Author: cwittich Last Changed Rev: 18820 Thanks, James

3 9

Re: [ros-diffs] [cwittich] 19291: implemented CreateServiceA
by Thomas Weidenmueller 17 Nov '05

17 Nov '05

cwittich(a)svn.reactos.com wrote: > implemented CreateServiceA This implementation theoretically is wrong, at least in windows this is also done using RPC (see the .idl file, there should be methods for ansi and unicode). - Thomas

2 1

0.3 release plan - Again
by Steven Edwards 17 Nov '05

17 Nov '05

Hi All, My how history repeats itself. I would like to call for a feature freeze on Jan 1st with the approval of the Testing Coordinator. Although we have not had that many releases of the 0.2.x line I feel enough has changed to and that we need to bump to 0.3. Lets review some history 0.1.x - winhello 0.2.x - explorer and a few wine dlls 0.3.x - OpenGL games, Firefox, Mirc, OpenOffice, third party drivers, start of PnP, USB, Xbox support, Initial DirectX Support, etc For the record we really did not plan on all of this other stuff for 0.3 and a year ago most of us would have been happy with just Firefox and Mirc working under VMware and Qemu. In fact we were planning on that work for the 0.3 line to be included in 0.4 release. Which is great! I am happy to see that we have gone much further beyond our once limited goals. What I propose now is that everyone that has a open project try to either get it to a Alpha state by Jan 1st or admit that it just wont be ready for 0.3 and accept that. Current major works in progress: DirectX - GreatLord USB - Fireball PnP - hpoussin Ws2 - Ionescu msvcDDK - sedwards Can we get all of these in for 0.3? Ws2 is a showstopper for 0.3, USB at least for the Xbox in my mind is a showstopper as well. PnP would be really, really nice to have but if its not ready I think we should ship anyway and plan on doing a short run to 0.4 before we fully support PnP. DirectX I have no idea how close it is to working and my current pet project for MSVC/DDK and rbuild is not a feature. I would like to be able to build ReactOS with our DDK under msvc in the hopes of getting more developers to join the project and improve the quality of our code but I am happy to admit this is not a priority. So what does everyone think? Can we shot for a feeze for Jan 1st? How does Feb 1st sound for a release? Thanks Steven __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

8 8

[hpoussin] 19288: Second attempt to have a workingkeyboard and mouse at third reboot
by Ge van Geldorp 17 Nov '05

17 Nov '05

> From: hpoussin(a)svn.reactos.com > > Second attempt to have a working keyboard and mouse at third > reboot May fix bug 1018 It does. Thanks! GvG

1 0

RE: [ros-dev] 0.3 release plan - Again
by Murphy, Ged (Bolton) 17 Nov '05

17 Nov '05

> -----Original Message----- > From: Steven Edwards [mailto:steven_ed4153@yahoo.com] > Sent: 17 November 2005 04:35 > To: ros-dev(a)reactos.org > Subject: [ros-dev] 0.3 release plan - Again > > > So what does everyone think? Can we shot for a feeze for Jan > 1st? How does Feb 1st sound for a release? Considering the state of HEAD at the moment, I think we should be going for a feature freeze much sooner than this. 1st of Jan is quite a long way off and it would be difficult to make any headway, especially on networking which is our showstopper, until this is sorted. IMO, we should be calling for a feature freeze as soon as the TC is elected. If that feature freeze gets HEAD back in stable and usable condition quickly, and with a bit of collaboration on networking, we could even aim at going for a Christmas release for 0.3.0 ?? If we are only stating networking must run for qemu and vmware, then I don't think we are that far off. It's been running in these two environments, intermittently, for quite some time now. Stable networking on real hardware could be kept for the 0.3.1 release. -- my glass is half full ;) 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-dev] RE: [ros-diffs] [cwittich] 19266: fix memory leak i n case of erro r
by Murphy, Ged (Bolton) 16 Nov '05

16 Nov '05

sorry ignore, I didn't read the full function. -----Original Message----- From: Murphy, Ged (Bolton) [mailto:MurphyG@cmpbatteries.co.uk] Sent: 16 November 2005 15:57 To: 'ros-dev(a)reactos.org' Subject: [ros-dev] RE: [ros-diffs] [cwittich] 19266: fix memory leak in case of erro r There is another here : HardwareIdW = HeapAlloc(GetProcessHeap(), 0, len * sizeof(WCHAR)); if (!HardwareIdW) { SetLastError(ERROR_GEN_FAILURE); return FALSE; } -----Original Message----- From: cwittich(a)svn.reactos.com [mailto:cwittich@svn.reactos.com] Sent: 16 November 2005 15:54 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [cwittich] 19266: fix memory leak in case of error fix memory leak in case of error Modified: trunk/reactos/lib/newdev/newdev.c _____ Modified: trunk/reactos/lib/newdev/newdev.c --- trunk/reactos/lib/newdev/newdev.c 2005-11-16 15:14:31 UTC (rev 19265) +++ trunk/reactos/lib/newdev/newdev.c 2005-11-16 15:53:16 UTC (rev 19266) @@ -66,6 +66,7 @@ FullInfPathW = HeapAlloc(GetProcessHeap(), 0, len * sizeof(WCHAR)); if (!FullInfPathW) { + HeapFree(GetProcessHeap(), 0, HardwareIdW); SetLastError(ERROR_GEN_FAILURE); return FALSE; } ************************************************************************ 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 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 ************************************************************************ 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-diffs] [cwittich] 19266: fix memory leak in case of erro r
by Murphy, Ged (Bolton) 16 Nov '05

16 Nov '05

There is another here : HardwareIdW = HeapAlloc(GetProcessHeap(), 0, len * sizeof(WCHAR)); if (!HardwareIdW) { SetLastError(ERROR_GEN_FAILURE); return FALSE; } -----Original Message----- From: cwittich(a)svn.reactos.com [mailto:cwittich@svn.reactos.com] Sent: 16 November 2005 15:54 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [cwittich] 19266: fix memory leak in case of error fix memory leak in case of error Modified: trunk/reactos/lib/newdev/newdev.c _____ Modified: trunk/reactos/lib/newdev/newdev.c --- trunk/reactos/lib/newdev/newdev.c 2005-11-16 15:14:31 UTC (rev 19265) +++ trunk/reactos/lib/newdev/newdev.c 2005-11-16 15:53:16 UTC (rev 19266) @@ -66,6 +66,7 @@ FullInfPathW = HeapAlloc(GetProcessHeap(), 0, len * sizeof(WCHAR)); if (!FullInfPathW) { + HeapFree(GetProcessHeap(), 0, HardwareIdW); SetLastError(ERROR_GEN_FAILURE); return FALSE; } ************************************************************************ 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] [cwittich] 19264: added UpdateDriverForPlugAndPlayDevicesA (untested)
by Thomas Weidenmueller 16 Nov '05

16 Nov '05

cwittich(a)svn.reactos.com wrote: > added UpdateDriverForPlugAndPlayDevicesA (untested) It leaks memory in some error cases. Also, ERROR_GEN_FAILURE doesn't look like the correct error code, although i might be wrong. Maybe it'd be ok if the buffers are on the stack, that would save memory allocations. - Thomas

1 0

RE: [ros-dev] Setup for Net Card
by James Tabor 16 Nov '05

16 Nov '05

Hi Herve! It's coming along nicely. I wanted to paste it but you have left the channel. Thanks, James (subsys/csrss/win32csr/conio.c:1079) Console_Api Ctrl-C FIXME: CopyImage doesn't support IMAGE_ICON correctly! (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find mxdMessage (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'msacm.drv' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'midimap.dr v' (Status c0000135) (lib/setupapi/parser.c:1119) D:\6102v25VIA\FETNDIS.inf Net 2 00000000 (lib/setupapi/parser.c:1166) L"D:\\6102v25VIA\\FETNDIS.inf" -> 00533c90 (lib/setupapi/parser.c:1531) (00533c90,L"Version",L"ClassGUID"): returning 4 (lib/setupapi/parser.c:1531) (00533c90,L"Version",L"Class"): returning 3 (lib/setupapi/parser.c:1104) Returning 1 (lib/setupapi/parser.c:1433) (00533c90,L"Manuf",(null)): returning 2/0 (lib/setupapi/parser.c:1706) context 00533c90/00533c90/2/0 index 2 returning "PC I\\VEN_1106&DEV_3065&SUBSYS_01021106" (lib/setupapi/parser.c:1706) context 00533c90/00533c90/2/1 index 2 returning "PC I\\VEN_1106&DEV_3043&SUBSYS_01001106" (lib/setupapi/devinst.c:1663) (null) L"PCI" 00000000 0x00000006 00000000 (null) 00000000 (lib/setupapi/devinst.c:623) 00000000 00000000 <NULL> 00000000 (lib/setupapi/devinst.c:1693) : flag DIGCF_PRESENT ignored (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3065&SUBSYS_734C1462&REV_ 74\1&644af68e&12' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3059&SUBSYS_73401462&REV_ 50\1&644af68e&B1' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_0571&SUBSYS_73401462&REV_ 06\1&644af68e&31' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3177&SUBSYS_31771106&REV_ 00\1&644af68e&11' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3104&SUBSYS_73401462&REV_ 82\1&644af68e&70' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_ 80\1&644af68e&50' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_ 80\1&644af68e&30' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_ 80\1&644af68e&10' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_10EC&DEV_8029&SUBSYS_802910EC&REV_ 00\1&644af68e&05' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_B198&SUBSYS_00000000&REV_ 00\1&644af68e&01' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3205&SUBSYS_32051106&REV_ 00\1&644af68e&00' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_7205&SUBSYS_73481462&REV_ 01\2&ddb52e18&00' to device info set 00533c10 (lib/setupapi/devinst.c:670) 00533c10, 0x00000000, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000001, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000002, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000003, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000004, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000005, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000006, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000007, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000008, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000009, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x0000000a, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x0000000b, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x0000000c, 0052fc90 (lib/setupapi/devinst.c:1902) 00533c10 (lib/setupapi/devinst.c:1915) Returning 1 (lib/setupapi/devinst.c:1663) (null) L"PCI" 00000000 0x00000006 00000000 (null) 00000000 (lib/setupapi/devinst.c:623) 00000000 00000000 <NULL> 00000000 (lib/setupapi/devinst.c:1693) : flag DIGCF_PRESENT ignored (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3065&SUBSYS_734C1462&REV_ 74\1&644af68e&12' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3059&SUBSYS_73401462&REV_ 50\1&644af68e&B1' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_0571&SUBSYS_73401462&REV_ 06\1&644af68e&31' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3177&SUBSYS_31771106&REV_ 00\1&644af68e&11' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3104&SUBSYS_73401462&REV_ 82\1&644af68e&70' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_ 80\1&644af68e&50' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_ 80\1&644af68e&30' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_ 80\1&644af68e&10' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_10EC&DEV_8029&SUBSYS_802910EC&REV_ 00\1&644af68e&05' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_B198&SUBSYS_00000000&REV_ 00\1&644af68e&01' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_3205&SUBSYS_32051106&REV_ 00\1&644af68e&00' to device info set 00533c10 (lib/setupapi/devinst.c:1221) Adding 'PCI\VEN_1106&DEV_7205&SUBSYS_73481462&REV_ 01\2&ddb52e18&00' to device info set 00533c10 (lib/setupapi/devinst.c:670) 00533c10, 0x00000000, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000001, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000002, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000003, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000004, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000005, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000006, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000007, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000008, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x00000009, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x0000000a, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x0000000b, 0052fc90 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 00000000 0 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 00531d80 0 0052fc38 (lib/setupapi/devinst.c:2332) Returning 0 (lib/setupapi/devinst.c:2079) 00533c10 0052fc90 1 0052fc88 0053a170 146 0052fc80 (lib/setupapi/devinst.c:2154) 00533c10 0052fc90 1 0052fc40 0053a210 292 0052fc38 (lib/setupapi/devinst.c:2332) Returning 1 (lib/setupapi/devinst.c:670) 00533c10, 0x0000000c, 0052fc90 (lib/setupapi/devinst.c:1902) 00533c10 (lib/setupapi/devinst.c:1915) Returning 1 (lib/setupapi/stubs.c:70) stub: source "D:\\6102v25VIA\\FETNDIS.inf" location "D :\\6102v25VIA\\" ... (lib/rpcrt4/ndr_marshall.c:499) sized string format=68 (lib/rpcrt4/ndr_marshall.c:446) sized string format=68 (lib/rpcrt4/ndr_marshall.c:563) sized string format=68 (lib/rtl/exception.c:29) RtlRaiseException(Status 0052fb98) (lib/rtl/exception.c:36) ExceptionAddress 7c801fd1 (ntoskrnl/ke/exception.c:94) KiRaiseException Unhandled exception ExceptionCode: 80000100 Address: 7c801fd1 C:\ReactOS\system32\KERNEL32.dll lib/kernel32/except/except.c:268 (RaiseException) CS:EIP 1b:7c801fd1 DS 23 ES 23 FS 3b GS 0 EAX: 0052f8a8 EBX: 0000000c ECX: 0052f638 EDX: 00000023 EBP: 0052fbf0 ESI: 0040900c ESP: 0052fb88 EDI: 0052fc62 EFLAGS: 00000212 Frames: 76660000+21555 C:\ReactOS\system32\SETUPAPI.dll lib/setupapi/setupapi.stubs.c:16 (__wine_spec_unimplemented_stub) 76660000+21f68 C:\ReactOS\system32\SETUPAPI.dll lib/setupapi/setupapi.stubs.c:112 (__wine_stub_setupapi_dll_154) 400000+1330 D:\6102v25VIA\winsetup\w2kxp\w2ksetup.EXE 7c800000+31095 C:\ReactOS\system32\KERNEL32.dll lib/kernel32/process/create.c:68 (BaseProcessStartup) (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!

2 3

RE: [ros-diffs] [cwittich] 19254: add a check for SPDRP_CONFIGFLAGSwhich is not working yet
by Casper Hornstrup 15 Nov '05

15 Nov '05

~1700 lines to add a check? In the future, please do reformatting in its own patch without semantic changes. This patch would require an hour or more to review if anyone dared to do it and even if someone did, that person would have be superhuman to be able to keep track of that many lines of information. The risk of introducing a bug is higher with some types of operations than others. Formatting is a relatively safe operation while semantic changes to complex code is a highly risky operation. This means that reviewing a formatting patch is not as important as reviewing a patch with semantic changes to complex code (and thus it doesn't hurt so much if a formatting change is large). When mixing safe and unsafe operations, the overall risk of a introducing a bug in a given patch is the same as if the changes were spread over several patches. However, the risk of the individual patch is equal to risk of the most risky operation in the patch. So if a 1 line highly risky change is hidden in a 1700 line otherwise safe patch, then the overall risk for the whole patch is highly risky. It may not seem important to have only a few bugs in releases now. We can always use the excuse that ReactOS is alpha software. However, if we ever want to have an 1.x release which is more than a toy-OS, then we have to learn to build better software. And I would prefer that we learn it before 1 day before the deadline for 1.0.0 since that might give us some years to get really good at it. I've written several school papers the night before the deadline, and they were never any good ;-( Another side effect of starting early is that some might even be able to use ReactOS before 1.0.0. Casper

2 4

GDI32.DLL exports
by tobitosso 15 Nov '05

15 Nov '05

I used Depends.exe and examined gdi32.dll. I found out that at least there functions are missing in the gdi32.dll api status at svn.reactos.com: AnimatePalette Arc ArcTo BitBlt cGetTTFFromFOT CombineRgn CombineTransform CreateBitmap CreateBitmapIndirect CreateCompatibleBitmap CreateCompatibleDC CreateDiscardableBitmap CreateEllipticRgn CreateEllipticRgnIndirect CreateHalftonePalette CreateHatchBrush CreatePalette CreatePatternBrush CreatePen CreatePenIndirect CreatePolygonRgn CreatePolyPolygonRgn CreateRectRgn CreateRectRgnIndirect CreateRoundRectRgn CreateSolidBrush DdEntry0 DdEntry1 DdEntry10 --------------------------------- Gesendet von Yahoo! Mail - Jetzt mit 1GB kostenlosem Speicher

2 3

RE: [ros-dev] TC vote
by Murphy, Ged (Bolton) 15 Nov '05

15 Nov '05

> > It's been 7 days since the TC position was put up for > discussion, thus > > I have created the poll for voting to commence. > > _http://www.reactos.org/forum/viewtopic.php?t=1140_ > > > > Anyone wanna take a bet on the outcome ;) > > > I think the only bet that could be placed would be on whether > it's going > to be unanimous :P That's what I was referring too, and I know what my money would be on ;) ************************************************************************ 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

TC vote
by Murphy, Ged (Bolton) 15 Nov '05

15 Nov '05

It's been 7 days since the TC position was put up for discussion, thus I have created the poll for voting to commence. http://www.reactos.org/forum/viewtopic.php?t=1140 <http://www.reactos.org/forum/viewtopic.php?t=1140> Anyone wanna take a bet on the outcome ;) ************************************************************************ 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

Setup for Net Card
by James Tabor 15 Nov '05

15 Nov '05

Hi, Running 6102v25Via setup for w2k. Thanks, James Revision: 19212 Node Kind: directory Schedule: normal Last Changed Author: cwittich Last Changed Rev: 19212 Last Changed Date: 2005-11-13 20:58:29 +0000 (Sun, 13 Nov 2005) Properties Last Updated: 2005-10-01 16:19:41 +0000 (Sat, 01 Oct 2005) (lib/setupapi/parser.c:915) class L"Net" not supported yet (lib/setupapi/devinst.c:1690) : flag DIGCF_PRESENT ignored Unhandled exception ExceptionCode: c0000005 Faulting Address: 0 Address: 7c92575c C:\ReactOS\system32\ntdll.dll CS:EIP 1b:7c92575c DS 23 ES 23 FS 3b GS 0 EAX: 0052f95c EBX: 0000000c ECX: 76664890 EDX: 00000000 EBP: 0052f960 ESI: 0040900c ESP: 0052f954 EDI: 0052fcde EFLAGS: 00010202 Frames: 76660000+65fb C:\ReactOS\system32\SETUPAPI.dll 76660000+74dc C:\ReactOS\system32\SETUPAPI.dll 76660000+5f0b C:\ReactOS\system32\SETUPAPI.dll 76660000+5d1b C:\ReactOS\system32\SETUPAPI.dll 400000+1c9c D:\6102v25VIA\winsetup\w2kxp\w2ksetup.EXE (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!

2 2

[patch] Spelling/Grammatical/Presentation fixes to power.c
by TwoTailedFox 14 Nov '05

14 Nov '05

Hi, all Just went through this file, and fixed parts of the Shutdown messages, so they actually look right. (Like replacing "i'm" with "I'm", and "signal" to "signals", for example). No changes to the important code. I do have one question, though. How does it tell the difference between whether or not to include one line, or two, in the quote at shutdown? A few extend to two (One even, to four) - TwoTailedFox -- "I had a handle on life, but then it broke"

4 6

Re: [ros-bugs] [Bug 986] devmgr - DeviceCreateHardwarePage, DeviceCreateHardwarePageEx
by Brandon Turner 14 Nov '05

14 Nov '05

Also, just 2 things i noticed: 1) int -> INT and void -> VOID 2) the name of the function should be the first word on the line per our unspoken formatting. Brandon ReactOS.Bugzilla(a)reactos.org wrote: >http://www.reactos.org/bugzilla/show_bug.cgi?id=986 > > > > > >------- Additional Comments From w3seek(a)reactos.com 2005-11-14 16:21 CET ------- >If you happen to use TortoiseSVN, there's an option 'Create Patch' in the menu, >otherwise see help for svn diff. Anyway, here are the things I'd like you to fix >before I'm going to commit it to svn: > >- add missing definitions to cfgmgr32.h if missing (instead of defining it in >the .c file) >- please don't mix tchar and unicode-only stuff like here (just use unicode >stuff in there): wsprintf( resData, TEXT("%s %s"), resData, textData); >- the code lacks a lot important failure case checks, making it unpredictable >when a single function call fails > >This may sound like a lot, I'm just trying to preserve a certain level of >quality ;) We already have more than enough code that needs a serious overhaul >or even rewrite. > > >

1 0

RE: [ros-dev] ReactOS goes commercial ;-)
by Murphy, Ged (Bolton) 14 Nov '05

14 Nov '05

Reuben Perelman wrote: > With the activity of reactos, you'd be crazy to use anything older than an hour. I'm not sure about that. I'm using 0.2.8 for testing at the moment, HEAD is too broken .... Heh ;) ************************************************************************ 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

I think we have an Outlook-compatible email client already
by Wesley Parish 14 Nov '05

14 Nov '05

Understanding and Replacing Microsoft Exchange by Tom Adelstein http://www.linuxjournal.com/article/6368 I've downloaded it in connection with something entirely different (shades of Monty Python! ;) and discoverred this article. So, we've got some network functionality already, we've got a NetBEUI in the form of Sambs-NG, we've got most of the specialized stuff already out there. We've just got to get it all fitting together. (famous last words ;) Wesley Parish -- Clinersterton beademung, with all of love - RIP James Blish ----- Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people.

1 0

devmgr x 2
by Sebastian Gąsiorek 14 Nov '05

14 Nov '05

Hi, could somebody change name of devmgr in \subsys\system\devmgr because it conflict with \lib\devmgr library. thanks, Sebastian Gasiorek

3 4

Voting rule
by Murphy, Ged (Bolton) 14 Nov '05

14 Nov '05

What happens in a situation where a project position is up for a vote, and only one candidate puts there name forward? Do we just state a unanimous decision, or to try and keep some kind of option do we do something like: [] Yes, I want <person> to be <position> [] No, I don't want <person> to be <position> There is nothing in the wiki for this situation. ************************************************************************ 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-dev] devmgr x 2
by Murphy, Ged (Bolton) 14 Nov '05

14 Nov '05

Sebastian Gasiorek wrote: > Is there any possibility to get svn write access? I would like to work > with devmgr and control panel applets. Writing bug reports for every > patch doesn't make me happy. :-) Using bugzilla is the preferred method, but if you don't like using bugzilla to submit patches, come into IRC, speak to the devs and get your code committed directly through them. (if they aren't too busy) It isn't difficult to get commit access, but you must prove your worth by submitting code for a while first. You can then ask to be recommended for commit access. ************************************************************************ 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

ReactOS goes commercial ;-)
by Casper Hornstrup 14 Nov '05

14 Nov '05

http://www.frozentech.com/ilhd.php

2 3

RE: [ros-dev] Microsoft Office files in the trunk
by Murphy, Ged (Bolton) 14 Nov '05

14 Nov '05

You can't realistically expect things like slide show presentations and flyers to be done in ASCII format. -----Original Message----- From: Reuben Perelman [mailto:reub2000@earthlink.net] Sent: 14 November 2005 09:21 To: ReactOS Development List Subject: Re: [ros-dev] Microsoft Office files in the trunk "svn diff" can't handle binary files as good as text files. Casper Hornstrup wrote: Subversion handles binary files just as good as text files. -----Original Message----- From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Reuben Perelman Sent: 14. november 2005 04:32 To: ReactOS Development List Subject: Re: [ros-dev] Microsoft Office files in the trunk Why use a binary format? Shouldn't you be using ascii formats in a subversion repository. Mike Swanson wrote: In the branch of press-media, there are two documents currently. An MS Word and MS PowerPoint document. I'm calling for SVN committers for _no more_ MS Office documents. They are a proprietary format, of which not all the features are currently known. I recommend instead the use of OASIS OpenDocument. Not only does it save much space, but it also does not contain any secrets in which need to be reverse engineered to discover. Real life example: I opened the MS Word flyer into AbiWord, and saw strange boxes. I wondered what they could be, so I loaded very-large OpenOffice.org. They are images! Not only that, but the formatting was drastically different in OOo compared to AbiWord. However, in OOo, it did look a lot more jumbled than the image-less AbiWord interpretation. Without a copy of Microsoft Office, I am unable to determine how the documents really should look. I am able to open the PowerPoint file in OpenOffice.org too, but as it's the only presentation software I have, I can't tell to see if there's any other interpretation differences between free presentation programs (assuming they support PPT . . . ) OpenDocument isn't just some crazy format that a couple of programs support, either. Two complete office suits which support it are OpenOffice.org and KOffice. Two examples of individual applications supporting it are AbiWord and Gnumeric. By far, these are not the only programs which support it, the number is in the dozens. It's an XML-based format (easy to implement), compressed with Info-ZIP's DEFLATE. Really, Microsoft is the only developer that refuses to use this open file format. They claim that "it doesn't support all the features of Office", but even that shouldn't stop them (weather it's true or not), after all, they use _far_ more limiting formats like plain text or CSV. Please, for the good of the project, use the free OpenDocument format. If not for the reason of being open or free, but simply for the fact that it ensures that everybody will be able to view such documents (no need to buy any pricey office suites here!). -- Mike _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/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

Microsoft Office files in the trunk
by Mike Swanson 14 Nov '05

14 Nov '05

In the branch of press-media, there are two documents currently. An MS Word and MS PowerPoint document. I'm calling for SVN committers for _no more_ MS Office documents. They are a proprietary format, of which not all the features are currently known. I recommend instead the use of OASIS OpenDocument. Not only does it save much space, but it also does not contain any secrets in which need to be reverse engineered to discover. Real life example: I opened the MS Word flyer into AbiWord, and saw strange boxes. I wondered what they could be, so I loaded very-large OpenOffice.org. They are images! Not only that, but the formatting was drastically different in OOo compared to AbiWord. However, in OOo, it did look a lot more jumbled than the image-less AbiWord interpretation. Without a copy of Microsoft Office, I am unable to determine how the documents really should look. I am able to open the PowerPoint file in OpenOffice.org too, but as it's the only presentation software I have, I can't tell to see if there's any other interpretation differences between free presentation programs (assuming they support PPT . . . ) OpenDocument isn't just some crazy format that a couple of programs support, either. Two complete office suits which support it are OpenOffice.org and KOffice. Two examples of individual applications supporting it are AbiWord and Gnumeric. By far, these are not the only programs which support it, the number is in the dozens. It's an XML-based format (easy to implement), compressed with Info-ZIP's DEFLATE. Really, Microsoft is the only developer that refuses to use this open file format. They claim that "it doesn't support all the features of Office", but even that shouldn't stop them (weather it's true or not), after all, they use _far_ more limiting formats like plain text or CSV. Please, for the good of the project, use the free OpenDocument format. If not for the reason of being open or free, but simply for the fact that it ensures that everybody will be able to view such documents (no need to buy any pricey office suites here!). -- Mike

8 11

Direct3D - NtGdi...
by Jurgen Van Gael 14 Nov '05

14 Nov '05

Hi Guys, I'm a little lost and in need for some suggestions. I am implementing the device creation for Direct3D but cannot seem to figure out what microsoft wants for NtGdiD3dContextCreate. My plan is to get d3d9.dll to work with Microsoft's gdi32 and win32k and then later make it work by maybe filling in some gaps in the ROS implementation of gdi32 and win32k. Anyways, does anybody know where the hSurfColor handle comes from. The documentation says it is a handle to a DD_SURFACE_LOCAL structure however. My experiments have shown that win32k expects some specific handle, but I don't know where it could get it from. (Apimon shows that NtGdiCreateSurfaceObject hasn't been called so it can't be a handle returned by that call.) Any suggestions on this are welcome as I have been stuck on this for the last week now ... Jurgen (hoping to get D3D device creation to work before christmas ...)

1 0

RE: [ros-diffs] [hbirr] 19209: Shutdown the process manager beforeshutdown the registry.
by Casper Hornstrup 13 Nov '05

13 Nov '05

What is it waiting for? Maybe an event is more appropriate? Casper _____ From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of hbirr(a)svn.reactos.com Sent: 13. november 2005 18:32 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [hbirr] 19209: Shutdown the process manager beforeshutdown the registry. Shutdown the process manager before shutdown the registry. Running processes may have opened a registry handle. Modified: trunk/reactos/ntoskrnl/ex/power.c _____ Modified: trunk/reactos/ntoskrnl/ex/power.c --- trunk/reactos/ntoskrnl/ex/power.c 2005-11-13 17:28:24 UTC (rev 19208) +++ trunk/reactos/ntoskrnl/ex/power.c 2005-11-13 17:32:01 UTC (rev 19209) @@ -148,15 +148,16 @@ sizeof(PCH))]); } + PiShutdownProcessManager(); + Waittime.QuadPart = (LONGLONG)-10000000; /* 1sec */ + KeDelayExecutionThread(KernelMode, FALSE, &Waittime); + CmShutdownRegistry(); IoShutdownRegisteredFileSystems(); IoShutdownRegisteredDevices(); - PiShutdownProcessManager(); MiShutdownMemoryManager(); - Waittime.QuadPart = (LONGLONG)-10000000; /* 1sec */ - KeDelayExecutionThread(KernelMode, FALSE, &Waittime); if (Action == ShutdownNoReboot) {

3 2

RE: [ros-svn] [ion] 19196: - Add new configuration option "SARCH" todefine the sub-architecture. Examples include i386-xbox, ppc-be/le (little/bigendian), or any other sub-types of the specified ARCH.
by Ge van Geldorp 13 Nov '05

13 Nov '05

> From: ion(a)svn.reactos.com > > - Add new configuration option "SARCH" to define the > sub-architecture. Examples include i386-xbox, ppc-be/le > (little/bigendian), or any other sub-types of the specified ARCH. This means we will have to build, test and distribute different .isos for different sub-architectures, only to save a few bytes in the freeldr/setupldr binaries. I implemented calling of sub-architecture specific code via a table of function pointers precisely to be able to keep one binary (per architecture). Please revert. Gé van Geldorp.

3 3

WinAmp 5.1111 (Very Long)
by James Tabor 13 Nov '05

13 Nov '05

Hi all, Installing winamp, (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'C:\Program Files\Winamp\Plugins\cddbcontrolwinamp.dll' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'comcat.dll ' (Status c0000135) (lib/ole32/compobj.c:1630) couldn't load InprocServer32 dll L"comcat.dll" (lib/ole32/compobj.c:1840) no classfactory created for CLSID {0002e005-0000-0000 -c000-000000000046}, hres is 0x80070005 (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'comcat.dll ' (Status c0000135) <Note: Window poped up about haven a problem with a file.> (lib/ole32/compobj.c:1630) couldn't load InprocServer32 dll L"comcat.dll" (lib/ole32/compobj.c:1840) no classfactory created for CLSID {0002e005-0000-0000 -c000-000000000046}, hres is 0x80070005 FIXME: CopyImage doesn't support IMAGE_ICON correctly! (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find mxdMessage (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'msacm.drv' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'midimap.dr v' (Status c0000135) (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! FIXME: CopyImage doesn't support IMAGE_ICON correctly! (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find mxdMessage (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'msacm.drv' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'midimap.dr v' (Status c0000135) (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 441000) C:\ReactOS\System32 \wshtcpip.dll WARNING: WSHGetSockaddrType at drivers/net/wshtcpip/wshtcpip.c:103 is UNIMPLEME NTED! <Note: It did not like this.> Entered debugger on last-chance exception number 14 (Page Fault) Memory at 0x00000004 could not be read: Page not present. kdb:> cont KeBugCheckWithTf at ntoskrnl/ke/i386/exp.c:1236 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 Technical information: *** STOP: 0x0000001E (0xc0000005,0x80033121,0x00000000,0x00000004) *** ntoskrnl.exe - Address 0x80033121 base at 0x80000000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:80033121 <ntoskrnl.exe:33121 (ntoskrnl/io/device.c:860 (Io GetRelatedDeviceObject))> cr2 4 cr3 333bf000 Proc: 81f120f8 Pid: 180 <eMusic-7plus.ex> Thrd: 81f1a028 Tid: 17c DS 23 ES 23 FS 30 GS 0 EAX: 00000000 EBX: 8003f043 ECX: 81f62cb8 EDX: 8dc04000 EBP: a5911b74 ESI: 0055ee90 ESP: a5911af8 EDI: a5911d64 EFLAGS: 00010296 kESP a5911af8 kernel stack base a590f000 Frames: <afd.sys:ccfe (drivers/net/afd/afd/tdi.c:1107 (TdiDisconnect))> <afd.sys:5b8f (drivers/net/afd/afd/main.c:284 (AfdDisconnect))> <afd.sys:6064 (drivers/net/afd/afd/main.c:384 (AfdDispatch))> <ntoskrnl.exe:46824 (ntoskrnl/io/irp.c:1076 (IofCallDriver))> <ntoskrnl.exe:3d4dc (ntoskrnl/io/file.c:619 (IopDeviceFsIoControl))> <ntoskrnl.exe:3f09b (ntoskrnl/io/file.c:1738 (NtDeviceIoControlFile))> <ntoskrnl.exe:9c57c ({standard input}:373 (KiSystemService))> <msafd.dll:38e0 (lib/msafd/misc/dllmain.c:1278 (WSPShutdown))> Entered debugger on embedded INT3 at 0x0008:0x800b2376. kdb:> bt Eip: <ntoskrnl.exe:b2377 ({standard input}:28 (DbgBreakPointWithStatus))> Frames: <ntoskrnl.exe:99a62 (ntoskrnl/ke/i386/exp.c:1231 (KiDispatchException))> <ntoskrnl.exe:9820f (ntoskrnl/ke/i386/exp.c:189 (KiKernelTrapHandler))> <ntoskrnl.exe:b1344 (ntoskrnl/mm/i386/pfault.c:128 (KiPageFaultHandler))> <ntoskrnl.exe:9cc61 ({standard input}:152 (KiTrapProlog2))> <ntoskrnl.exe:33121 (ntoskrnl/io/device.c:860 (IoGetRelatedDeviceObject))> <afd.sys:ccfe (drivers/net/afd/afd/tdi.c:1107 (TdiDisconnect))> <afd.sys:5b8f (drivers/net/afd/afd/main.c:284 (AfdDisconnect))> <afd.sys:6064 (drivers/net/afd/afd/main.c:384 (AfdDispatch))> <ntoskrnl.exe:46824 (ntoskrnl/io/irp.c:1076 (IofCallDriver))> <ntoskrnl.exe:3d4dc (ntoskrnl/io/file.c:619 (IopDeviceFsIoControl))> <ntoskrnl.exe:3f09b (ntoskrnl/io/file.c:1738 (NtDeviceIoControlFile))> <ntoskrnl.exe:9c57c ({standard input}:373 (KiSystemService))> <msafd.dll:38e0 (lib/msafd/misc/dllmain.c:1278 (WSPShutdown))> <ws2_32.dll:804a (lib/ws2_32/misc/stubs.c:217 (shutdown))> <NSISdl.dll:1274> <NSISdl.dll:2e20> <eMusic-7plus.exe:138f> <72676f72> (ntoskrnl/mm/mm.c:275) Page fault at high IRQL was 31, address 505c3a47 (lib/rtl/i386/exception.c:90) Invalid exception frame Entered debugger on last-chance exception number 14 (Page Fault) Memory at 0x505c3a47 could not be read: Page not present. KeBugCheckWithTf at ntoskrnl/ke/i386/exp.c:1236 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 Technical information: *** STOP: 0x0000001E (0xc0000005,0x800cb6cc,0x00000000,0x505c3a47) *** ntoskrnl.exe - Address 0x800cb6cc base at 0x80000000, DateStamp 0x0 Reboot and run winamp, <snip ....> (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) WARNING: ModifyMenuW at lib/user32/windows/menu.c:4424 is UNIMPLEMENTED! (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (ntoskrnl/cm/regfile.c:3507) CellOffset exceeds valid range (134656 > 131072) (lib/ntdll/ldr/utils.c:2072) Relocating (76200000 -> 760000) C:\ReactOS\system32 \comdlg32.dll (lib/ntdll/ldr/utils.c:2072) Relocating (77400000 -> 7df000) C:\ReactOS\system32 \iphlpapi.dll (lib/ntdll/ldr/utils.c:2072) Relocating (77800000 -> 7f3000) C:\ReactOS\system32 \winspool.drv FIXME: CopyImage doesn't support IMAGE_ICON correctly! (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find mxdMessage (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'msacm.drv' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'midimap.dr v' (Status c0000135) (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsAlloc (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsGetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsSetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsFree (lib/ole32/compobj.c:1615) class {00000000-fe14-0065-ae4b-a577f8204800} not regi stered (ntoskrnl/ob/object.c:347) failed (lib/ole32/rpc.c:614) class {00000000-fe14-0065-ae4b-a577f8204800} not registere d (lib/ole32/compobj.c:1840) no classfactory created for CLSID {00000000-fe14-0065 -ae4b-a577f8204800}, hres is 0x80040150 (lib/ole32/compobj.c:1615) class {00000001-fe14-0065-ae4b-a577e8354800} not regi stered (ntoskrnl/ob/object.c:347) failed (lib/ole32/rpc.c:614) class {00000001-fe14-0065-ae4b-a577e8354800} not registere d (lib/ole32/compobj.c:1840) no classfactory created for CLSID {00000001-fe14-0065 -ae4b-a577e8354800}, hres is 0x80040150 (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (subsys/win32k/ntuser/window.c:2412) Failed to lookup class atom! (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsAlloc (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsGetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsSetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsFree (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsAlloc (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsGetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsSetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsFree (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'C:\Program Files\Winamp\wmahelp.dll' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'wmvcore.dl l' (Status c0000135) (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsAlloc (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsGetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsSetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsFree (ntoskrnl/cm/ntfunc.c:1666) ObReferenceObjectByHandle() failed with status c0000 008 00000000 (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1030000) C:\Program Files\W inamp\Plugins\read_file.dll (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find winampGetExten dedFileInfo (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 104b000) C:\Program Files\W inamp\Plugins\in_mod.dll (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsAlloc (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsGetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsSetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsFree (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find winampGetExten dedFileInfo (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 11a0000) C:\Program Files\W inamp\Plugins\in_vorbis.dll (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsAlloc (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsGetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsSetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsFree (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1310000) C:\Program Files\W inamp\Plugins\in_mp4.dll (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsAlloc (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsGetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsSetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsFree (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1440000) C:\Program Files\W inamp\Plugins\in_cdda.dll (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsAlloc (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsGetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsSetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsFree (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 15a0000) C:\Program Files\W inamp\pxsdkpls.dll (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 15bd000) C:\ReactOS\System3 2\PX.dll (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'PXDDM.DLL' (Status c0000135) (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1850000) C:\ReactOS\System3 2\PXDRV.DLL (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'TFSWAPI.DL L' (Status c0000135) (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 19b0000) C:\ReactOS\System3 2\PXMAS.DLL (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1af0000) C:\ReactOS\System3 2\PXWAVE.DLL (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'PXDDM.DLL' (Status c0000135) (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1850000) C:\ReactOS\System3 2\PXDRV.DLL (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'TFSWAPI.DL L' (Status c0000135) (lib/ole32/compobj.c:1615) Unhandled exception ExceptionCode: c0000005 Faulting Address: 0 Address: 77a84071 C:\ReactOS\system32\ole32.dll CS:EIP 1b:77a84071 DS 23 ES 23 FS 3b GS 0 EAX: 00000000 EBX: 77a50000 ECX: 01c8fa3c EDX: 7ffb9000 EBP: 01c8fc24 ESI: 7c823e72 ESP: 01c8fc1c EDI: 00000000 EFLAGS: 00010216 Frames: 77a50000+346be C:\ReactOS\system32\ole32.dll 77a50000+65c4 C:\ReactOS\system32\ole32.dll 77a50000+63cf C:\ReactOS\system32\ole32.dll 77a50000+6a13 C:\ReactOS\system32\ole32.dll 15bd000+1ce1b C:\ReactOS\System32\PX.dll (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'PXDDM.DLL' (Status c0000135) (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1850000) C:\ReactOS\System3 2\PXDRV.DLL (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'TFSWAPI.DL L' (Status c0000135) (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =D: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =E: (ntoskrnl/io/file.c:125) Failed to mount logical volume (Status c000014f) (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =F: (ntoskrnl/io/file.c:125) Failed to mount logical volume (Status c000014f) (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =G: (ntoskrnl/io/file.c:125) Failed to mount logical volume (Status c000014f) (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =H: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =I: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =J: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =K: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =L: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =M: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =N: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =O: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =P: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =Q: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =R: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =S: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =T: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =U: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =V: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =W: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =X: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =Y: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =Z: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =D: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =E: (ntoskrnl/io/file.c:125) Failed to mount logical volume (Status c000014f) (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =F: (ntoskrnl/io/file.c:125) Failed to mount logical volume (Status c000014f) (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =G: (ntoskrnl/io/file.c:125) Failed to mount logical volume (Status c000014f) (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =H: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =I: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =J: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =K: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =L: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =M: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =N: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =O: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =P: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =Q: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =R: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =S: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =T: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =U: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =V: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =W: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =X: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =Y: (lib/rtl/env.c:570) Return STATUS_VARIABLE_NOT_FOUND: =Z: (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 533000) C:\Program Files\Wi namp\Plugins\in_wave.dll (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find winampGetExten dedFileInfo (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsAlloc (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsGetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsSetValue (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsFree (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1d90000) C:\Program Files\W inamp\Plugins\in_dshow.dll (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find FlsAlloc It loaded okay~, I had to kill winamp with Ctm. Thanks, James

1 1

Re: [ros-diffs] [gvg] 19180: Add some more shutdown messages
by Royce Mitchell III 13 Nov '05

13 Nov '05

gvg(a)svn.reactos.com wrote: >+ "Buy this place for advertisment purposes.\n", > > advertis*e*ment?

1 0

Re: [ros-diffs] [gvg] 19180: Add some more shutdown messages
by Royce Mitchell III 13 Nov '05

13 Nov '05

gvg(a)svn.reactos.com wrote: >+ "Don't abandon your computer, he wouldnt to it to you.\n", > > he wouldn't *do* it to you ? >+ "Remember to turn of your computer. (That was a public service message!)\n", > > Remember to turn *off* your computer?

1 0

Re: [ros-svn] [hpoussin] 19059: When a driver is a legacy driver, call its AddDevice function with a NULL Pdo
by Hartmut Birr 12 Nov '05

12 Nov '05

hpoussin(a)svn.reactos.com wrote: > When a driver is a legacy driver, call its AddDevice function with a NULL Pdo > > > Updated files: > trunk/reactos/drivers/bus/acpi/ospm/acpisys.c > trunk/reactos/drivers/input/i8042prt/i8042prt.c > trunk/reactos/drivers/input/kbdclass/kbdclass.c > trunk/reactos/drivers/input/mouclass/mouclass.c > trunk/reactos/ntoskrnl/io/device.c > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-svn > > This change breaks installing reactos within qemu for me. Reactos crashes at the second boot: The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0xc0000005,0x8003366e,0x00000000,0x00000010) *** ntoskrnl.exe - Address 0x8003366e base at 0x80000000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:8003366e <ntoskrnl.exe:3366e (ntoskrnl/io/device.c:726 (IoGetAttachedDevice))> cr2 10 cr3 22000 Proc: 80804ba0 Pid: 4 <System> Thrd: 80805630 Tid: 0 DS 23 ES 23 FS 30 GS 0 EAX: 00000000 EBX: 80827e78 ECX: 00000000 EDX: 000000e9 EBP: 80108ac0 ESI: 80827748 ESP: 80108a48 EDI: 00076514 EFLAGS: 00200292 kESP 80108a48 kernel stack base 80106000 Frames: <ntoskrnl.exe:32fc5 (ntoskrnl/io/device.c:344 (IoAttachDeviceToDeviceStackSafe))> <ntoskrnl.exe:32f71 (ntoskrnl/io/device.c:319 (IoAttachDeviceToDeviceStack))> <acpi.sys:174a1 (drivers/bus/acpi/ospm/acpisys.c:146 (ACPIAddDevice))> <ntoskrnl.exe:32c0b (ntoskrnl/io/device.c:88 (IopInitializeDevice))> <ntoskrnl.exe:c63d2 (ntoskrnl/io/driver.c:1269 (IopInitializeBuiltinDriver))> <ntoskrnl.exe:3b19e (ntoskrnl/io/driver.c:1332 (IopInitializeBootDrivers))> <ntoskrnl.exe:c6d3d (ntoskrnl/io/iomgr.c:391 (IoInit2))> <ntoskrnl.exe:c3857 (ntoskrnl/ex/init.c:646 (ExpInitializeExecutive))> <ntoskrnl.exe:6866 (ntoskrnl/ke/main.c:100 (KiSystemStartup))> <ntoskrnl.exe:c1857 (ntoskrnl/ke/main.c:294 (_main))> <0> - Hartmut

2 2

RE: [ros-dev] RE: Change of Project Coordinator
by Murphy, Ged (Bolton) 12 Nov '05

12 Nov '05

Sorry, here's a link for anyone feeling particularly lazy :) http://www.reactos.org/wiki/index.php/ReactOS_Project_Coordinator -----Original Message----- From: Murphy, Ged (Bolton) [mailto:MurphyG@cmpbatteries.co.uk] Sent: 12 November 2005 09:59 To: 'ReactOS Development List' Subject: RE: [ros-dev] RE: Change of Project Coordinator I've put the draft into the wiki for review and discussion. Wasn't sure whether to follow the layout of the TC, but that would've meant altering the text, so I left it. -----Original Message----- From: Steven Edwards [mailto:steven_ed4153@yahoo.com] Sent: 11 November 2005 04:48 To: ReactOS Development List Subject: RE: [ros-dev] RE: Change of Project Coordinator Hi, --- "Murphy, Ged (Bolton)" <MurphyG(a)cmpbatteries.co.uk> wrote: > Can someone draft something up, this isn't really my forte. How does the following sound? Thanks Steven ReactOS Project Coordinator Job Description: Mediate Small disputes to remove the need to vote on every issue - The Coordinator is simply a figure head and does not have the power to dictate policy so if mediation cannot be reached on a conflicting issue then it is taken to a vote. No issue has to be brought to the Coordinator. All developers are free to start a vote without consulting the Coordinator. His role is an advisory one. Provide a contact point for media and 3party project relations - The Project Coordinator be advised of major news announcements and be free to provide interviews, and or conduct meetings on behalf of the project with any 3rd party such as other Free Software Projects, Businesses and Universities. The PC has the responsibility to keep track of these events and advise the community of new developments. All developers have the freedom to grant interviews, establish relationships with other projects and organizations. Provide quarterly status updates regarding all major activities of the project - The PC will provide reports as to the project status due on Jan 1st, April 1st July 1st Oct 1st Conduct regular meetings with the other Coordinators and developers in the ReactOS Project - The PC will make a good faith effort to meet monthly via IRC, email exchange or VoIP with the various team coordinators to discuss any issues they feel may need to be addressed. The PC will also be obliged to be upon request conduct meetings with any other Coordinator or developer to address any issue. For developers that are limited in Internet Access the PC will make a good faith effort to keep in touch with those developers on a limited basis and seek out and address their development needs and goals. __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/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 _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/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

RE: [ros-dev] RE: Change of Project Coordinator
by Murphy, Ged (Bolton) 12 Nov '05

12 Nov '05

I've put the draft into the wiki for review and discussion. Wasn't sure whether to follow the layout of the TC, but that would've meant altering the text, so I left it. -----Original Message----- From: Steven Edwards [mailto:steven_ed4153@yahoo.com] Sent: 11 November 2005 04:48 To: ReactOS Development List Subject: RE: [ros-dev] RE: Change of Project Coordinator Hi, --- "Murphy, Ged (Bolton)" <MurphyG(a)cmpbatteries.co.uk> wrote: > Can someone draft something up, this isn't really my forte. How does the following sound? Thanks Steven ReactOS Project Coordinator Job Description: Mediate Small disputes to remove the need to vote on every issue - The Coordinator is simply a figure head and does not have the power to dictate policy so if mediation cannot be reached on a conflicting issue then it is taken to a vote. No issue has to be brought to the Coordinator. All developers are free to start a vote without consulting the Coordinator. His role is an advisory one. Provide a contact point for media and 3party project relations - The Project Coordinator be advised of major news announcements and be free to provide interviews, and or conduct meetings on behalf of the project with any 3rd party such as other Free Software Projects, Businesses and Universities. The PC has the responsibility to keep track of these events and advise the community of new developments. All developers have the freedom to grant interviews, establish relationships with other projects and organizations. Provide quarterly status updates regarding all major activities of the project - The PC will provide reports as to the project status due on Jan 1st, April 1st July 1st Oct 1st Conduct regular meetings with the other Coordinators and developers in the ReactOS Project - The PC will make a good faith effort to meet monthly via IRC, email exchange or VoIP with the various team coordinators to discuss any issues they feel may need to be addressed. The PC will also be obliged to be upon request conduct meetings with any other Coordinator or developer to address any issue. For developers that are limited in Internet Access the PC will make a good faith effort to keep in touch with those developers on a limited basis and seek out and address their development needs and goals. __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/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

Re: [ros-svn] [sedwards] 19158: fix a few more makefiles
by James Tabor 12 Nov '05

12 Nov '05

Hi! sedwards(a)svn.reactos.com wrote: > fix a few more makefiles > > > Updated files: > trunk/rosapps/tests/accelerator/accelerator.xml [CC] modules/rosapps/tests/accelerator/accelerator.c modules/rosapps/tests/accelerator/accelerator.c:16: error: `VK_A' undeclared here (not in a function) modules/rosapps/tests/accelerator/accelerator.c:16: error: initializer element is not constant modules/rosapps/tests/accelerator/accelerator.c:16: error: (near initializationfor `Accelerators[0].key') modules/rosapps/tests/accelerator/accelerator.c:16: error: initializer element is not constant modules/rosapps/tests/accelerator/accelerator.c:16: error: (near initializationfor `Accelerators[0]') modules/rosapps/tests/accelerator/accelerator.c:17: error: initializer element is not constant modules/rosapps/tests/accelerator/accelerator.c:17: error: (near initializationfor `Accelerators[1].key') modules/rosapps/tests/accelerator/accelerator.c:17: error: initializer element is not constant modules/rosapps/tests/accelerator/accelerator.c:17: error: (near initializationfor `Accelerators[1]') modules/rosapps/tests/accelerator/accelerator.c:18: error: initializer element is not constant modules/rosapps/tests/accelerator/accelerator.c:18: error: (near initializationfor `Accelerators[2].key') modules/rosapps/tests/accelerator/accelerator.c:18: error: initializer element is not constant modules/rosapps/tests/accelerator/accelerator.c:18: error: (near initializationfor `Accelerators[2]') modules/rosapps/tests/accelerator/accelerator.c:19: error: initializer element is not constant modules/rosapps/tests/accelerator/accelerator.c:19: error: (near initializationfor `Accelerators[3].key') modules/rosapps/tests/accelerator/accelerator.c:19: error: initializer element is not constant modules/rosapps/tests/accelerator/accelerator.c:19: error: (near initializationfor `Accelerators[3]') make[1]: *** [obj-i386/modules/rosapps/tests/accelerator/accelerator.o] Error 1 make: *** [accelerator] Error 2 Thanks, James

2 1

RE: [ros-svn] [greatlrd] 19138: Make notepad lang rc MSVC compatible
by Ge van Geldorp 11 Nov '05

11 Nov '05

> From: greatlrd(a)svn.reactos.com > > Make notepad lang rc MSVC compatible Can you take care of bug 967 (Greek translation for notepad) too then? I have no idea what to change to make it MSVC compatible. GvG

2 1

RE: [ros-dev] RE: Change of Project Coordinator
by Murphy, Ged (Bolton) 11 Nov '05

11 Nov '05

Good point ;) I thought this was already done, as we'd started the discussion for this position earlier. Can someone draft something up, this isn't really my forte. -----Original Message----- From: Casper Hornstrup [mailto:ch@csh-consult.dk] Sent: 10 November 2005 10:41 To: 'ReactOS Development List' Subject: RE: [ros-dev] RE: Change of Project Coordinator Better draft and vote on the project coordinator description first. It's good to know the job description when you apply for a job ;-) Casper > -----Original Message----- > From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Murphy, Ged > (Bolton) > Sent: 10. november 2005 10:14 > To: 'ReactOS Development List' > Subject: [ros-dev] RE: Change of Project Coordinator > > Jason Filby wrote: > > > I've decided that now is the best time to step down as Project > > Coordinator. The process to vote for a new PC will be - as previously > > decided for this type of decision - that only registered committers > > can vote. > > > This topic seems to have died a death, so I'm bringing it back up now as the > new voting system is in place. > I was speaking to Steven last night who advised he is now available to run > as PC. > Can any other candidates put their name forward again for the 1 week > discussion period. > > Ged. _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/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

4 3

RE: [ros-dev] RE: Change of Project Coordinator
by Murphy, Ged (Bolton) 11 Nov '05

11 Nov '05

Yeah, I didn't mean just edit it at will. I meant it should go in the wiki now, so it's easily accessible to modify if need be .... i.e. if a problem is highlighted in discussion. -----Original Message----- From: Royce Mitchell III [mailto:royce3@ev1.net] Sent: 11 November 2005 15:26 To: ReactOS Development List Subject: Re: [ros-dev] RE: Change of Project Coordinator I agree it's a good starting point, but changes should be discussed here first, not just modified. Murphy, Ged (Bolton) wrote: >I agree. I think it should go in the wiki now so anyone can make changes >before the voting, if need be. > >-----Original Message----- >From: Aleksey Bragin [mailto:aleksey@studiocerebral.com] >Sent: 11 November 2005 14:54 >To: ReactOS Development List >Subject: Re: [ros-dev] RE: Change of Project Coordinator > > >Sounds just great, especially I like the point about mediating small >disputes - that's exactly what I wanted to see for the long time. >Quarterly reports are quite cool also. > > >WBR, >Aleksey. > >On Nov 11, 2005, at 7:47 AM, Steven Edwards wrote: > > > >>Hi, >> >>--- "Murphy, Ged (Bolton)" <MurphyG(a)cmpbatteries.co.uk> wrote: >> >> >> >> >>>Can someone draft something up, this isn't really my forte. >>> >>> >>> >>How does the following sound? >> >>Thanks >>Steven >> >> >>ReactOS Project Coordinator Job Description: >> >>Mediate Small disputes to remove the need to vote on every issue - >> The Coordinator is simply a figure head and does not have the >>power to >>dictate policy so if mediation cannot be reached on a conflicting >>issue then it >>is taken to a vote. No issue has to be brought to the Coordinator. >>All developers >>are free to start a vote without consulting the Coordinator. His >>role is an >>advisory one. >> >>Provide a contact point for media and 3party project relations - >> >> The Project Coordinator be advised of major news announcements >>and be >>free to provide interviews, and or conduct meetings on behalf of >>the project >>with any 3rd party such as other Free Software Projects, Businesses >>and Universities. >>The PC has the responsibility to keep track of these events and >>advise the community >>of new developments. >> All developers have the freedom to grant interviews, establish >>relationships >>with other projects and organizations. >> >>Provide quarterly status updates regarding all major activities of >>the project - >> >> The PC will provide reports as to the project status due on >>Jan 1st, April 1st July 1st Oct 1st >> >>Conduct regular meetings with the other Coordinators and developers >>in the ReactOS Project - >> >> The PC will make a good faith effort to meet monthly via IRC, >>email >>exchange or VoIP with the various team coordinators to discuss any >>issues they >>feel may need to be addressed. The PC will also be obliged to be >>upon request >>conduct meetings with any other Coordinator or developer to address >>any issue. >> For developers that are limited in Internet Access the PC will >>make a >>good faith effort to keep in touch with those developers on a >>limited basis and >>seek out and address their development needs and goals. >> >> >_______________________________________________ >Ros-dev mailing list >Ros-dev(a)reactos.org >http://www.reactos.org/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 > > >_______________________________________________ >Ros-dev mailing list >Ros-dev(a)reactos.org >http://www.reactos.org/mailman/listinfo/ros-dev > >. > > > _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/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

RE: [ros-dev] RE: Change of Project Coordinator
by Murphy, Ged (Bolton) 11 Nov '05

11 Nov '05

I agree. I think it should go in the wiki now so anyone can make changes before the voting, if need be. -----Original Message----- From: Aleksey Bragin [mailto:aleksey@studiocerebral.com] Sent: 11 November 2005 14:54 To: ReactOS Development List Subject: Re: [ros-dev] RE: Change of Project Coordinator Sounds just great, especially I like the point about mediating small disputes - that's exactly what I wanted to see for the long time. Quarterly reports are quite cool also. WBR, Aleksey. On Nov 11, 2005, at 7:47 AM, Steven Edwards wrote: > Hi, > > --- "Murphy, Ged (Bolton)" <MurphyG(a)cmpbatteries.co.uk> wrote: > > >> Can someone draft something up, this isn't really my forte. >> > > How does the following sound? > > Thanks > Steven > > > ReactOS Project Coordinator Job Description: > > Mediate Small disputes to remove the need to vote on every issue - > The Coordinator is simply a figure head and does not have the > power to > dictate policy so if mediation cannot be reached on a conflicting > issue then it > is taken to a vote. No issue has to be brought to the Coordinator. > All developers > are free to start a vote without consulting the Coordinator. His > role is an > advisory one. > > Provide a contact point for media and 3party project relations - > > The Project Coordinator be advised of major news announcements > and be > free to provide interviews, and or conduct meetings on behalf of > the project > with any 3rd party such as other Free Software Projects, Businesses > and Universities. > The PC has the responsibility to keep track of these events and > advise the community > of new developments. > All developers have the freedom to grant interviews, establish > relationships > with other projects and organizations. > > Provide quarterly status updates regarding all major activities of > the project - > > The PC will provide reports as to the project status due on > Jan 1st, April 1st July 1st Oct 1st > > Conduct regular meetings with the other Coordinators and developers > in the ReactOS Project - > > The PC will make a good faith effort to meet monthly via IRC, > email > exchange or VoIP with the various team coordinators to discuss any > issues they > feel may need to be addressed. The PC will also be obliged to be > upon request > conduct meetings with any other Coordinator or developer to address > any issue. > For developers that are limited in Internet Access the PC will > make a > good faith effort to keep in touch with those developers on a > limited basis and > seek out and address their development needs and goals. _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/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

2 1

Bye for time
by Robert 11 Nov '05

11 Nov '05

Let me say bye bye for an unknown period. right now, im going on my voyage. I't not all evening's days, I'll be back

2 1

RE: [ros-dev] TC election
by Murphy, Ged (Bolton) 11 Nov '05

11 Nov '05

> In my mind we should try to nail down all the regressions > that have anything to do > with networking. Figure out whats left to fix and stick a > fork in 0.3 and focus on > 0.4 which will feature > > - True plug and play > - Real stablity > > Amen! Amen to that !!! ************************************************************************ 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

TC election
by Ge van Geldorp 11 Nov '05

11 Nov '05

With the TC function description settled, it's time to elect a Testing Coordinator. I'd like to nominate Andrew Munger aka WaxDragon for this position. Voting will start 7 days from now and the vote will run for 7 days. Gé van Geldorp.

3 2

Impressive...
by Richard Campbell 10 Nov '05

10 Nov '05

3 3

RE: [ros-dev] API documentation
by Murphy, Ged (Bolton) 10 Nov '05

10 Nov '05

Steven Edwards wrote: > I would like to propose we adopt the updated API documentation system Winehq has. > Please take a look at the updated system and tell me what you think. I like it. Can it be integrated into our CMS? ************************************************************************ 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: Change of Project Coordinator
by Murphy, Ged (Bolton) 10 Nov '05

10 Nov '05

Jason Filby wrote: > I've decided that now is the best time to step down as Project > Coordinator. The process to vote for a new PC will be - as previously > decided for this type of decision - that only registered committers > can vote. This topic seems to have died a death, so I'm bringing it back up now as the new voting system is in place. I was speaking to Steven last night who advised he is now available to run as PC. Can any other candidates put their name forward again for the 1 week discussion period. 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

API documentation
by Steven Edwards 10 Nov '05

10 Nov '05

Hi, I would like to propose we adopt the updated API documentation system Winehq has. Please take a look at the updated system and tell me what you think. http://source.winehq.org/WineAPI/ http://source.winehq.org/WineAPI/comctl32.html Thanks Steven __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com

2 1

Listdlls is Broken.
by James Tabor 10 Nov '05

10 Nov '05

Hi, After running listdlls, (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of '\SystemRoo t\system32\smss.exe' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of '\SystemRoo t\system32\smss.exe' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of '\??\C:\Rea ctOS\system32\csrss.exe' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of '\??\C:\Rea ctOS\system32\csrss.exe' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of '\SystemRoo t\system32\winlogon.exe' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of '\SystemRoo t\system32\winlogon.exe' (Status c0000135) Unhandled exception ExceptionCode: c0000005 Faulting Address: 978333 Address: 7c9253d8 C:\ReactOS\system32\ntdll.dll CS:EIP 1b:7c9253d8 DS 23 ES 23 FS 3b GS 0 EAX: 00978333 EBX: 00866b00 ECX: 00000004 EDX: 00007473 EBP: 0052d904 ESI: 77a49064 ESP: 0052d8fc EDI: 00978333 EFLAGS: 00010202 Frames: 77a40000+17db C:\ReactOS\system32\VERSION.dll 77a40000+181d C:\ReactOS\system32\VERSION.dll 400000+115d D:\rosbackup\tools\listdlls.EXE I tried "listdlls > dumpdata", and it did not work. Only touch the file w/o any data, just 0 bytes in file size. It quits at winlogon.exe at pid 156. svn info Path: . URL: svn://svn.reactos.com/trunk/reactos Repository UUID: Revision: 19072 Node Kind: directory Schedule: normal Last Changed Author: ion Last Changed Rev: 19072 Last Changed Date: 2005-11-08 22:54:39 +0000 (Tue, 08 Nov 2005) Properties Last Updated: 2005-10-01 16:19:41 +0000 (Sat, 01 Oct 2005) Thanks, James

2 2

ReactOS compilation errors (fixed)
by Damjan Jovanovic 09 Nov '05

09 Nov '05

Do you guys actually try to compile the release versions of ReactOS? Version 0.2.8-REL doesn't compile: 1. Need to "copy lib/msafd/msafd.h lib/msafd/include", otherwise you get: [CC] lib/msafd/misc/dllmain.c lib/msafd/misc/dllmain.c:13:19: msafd.h: No such file or directory 2. Need to comment out "-Werror", otherwise thousands of these warnings become errors: In file included from include/ndk/kefuncs.h:13, from include/ndk/ntndk.h:31, from hal/hal/hal.c:15: include/ndk/ketypes.h:295: warning: redefinition of `PKINTERRUPT' w32api/include/ddk/winddk.h:205: warning: `PKINTERRUPT' previously declared hereIn file included from include/ndk/cmtypes.h:15, from include/ndk/extypes.h:19, from include/ndk/pstypes.h:17, from include/ndk/psfuncs.h:13, from include/ndk/ntndk.h:34, from hal/hal/hal.c:15: include/ndk/iotypes.h:562: warning: redefinition of `PIO_TIMER' w32api/include/ddk/winddk.h:201: warning: `PIO_TIMER' previously declared here 3. Doesn't link under Linux, binutils 2.14.90, it needs to be severely hacked to link, and then crashes when booted. __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

4 4

RE: [ros-dev] ReactOS compilation errors (fixed)
by Murphy, Ged (Bolton) 09 Nov '05

09 Nov '05

> -----Original Message----- > From: Damjan Jovanovic [mailto:dj015@yahoo.com] > Sent: 09 November 2005 13:39 > To: ReactOS Development List > Subject: RE: [ros-dev] ReactOS compilation errors (fixed) > > --- Ge van Geldorp <gvg(a)reactos.org> wrote: > > > > From: Damjan Jovanovic > > > > > > Do you guys actually try to compile the release > > versions of > > > ReactOS? Version 0.2.8-REL doesn't compile > > > > No, we just do some magic chants and poof, the .iso > > appears. > > Then how come I am getting the errors I described and > you're not? I built it with the standard build > environment. More than likely your build environment is wrong. > > > > 3. Doesn't link under Linux, binutils 2.14.90, it > > needs to be > > > severely hacked to link, and then crashes when > > booted. > > > > 2.14.90 is seriously old and contains some bugs > > which prevent ReactOS from > > building correctly. > > Why isn't that documented anywhere? http://www.reactos.org/wiki/index.php/HOWTO/setup_a_build_environment_for_Li nux States you should use the mingw x-compile script, which uses binutils 2.15.91 (although this does need updating) http://www.reactos.org/wiki/index.php/HOWTO/setup_a_build_environment_for_Wi ndows States the files you need for the full build environment, including binutils 2.15.94 (although I personally prefer 2.16.91) > > > I'm using MinGW binutils 2.15.94 > > and MinGW gcc 3.4.2 on > > Linux, works without a hitch. > > > > Gé van Geldorp. > > Once you have your build environment set up correctly, you'll find ReactOS builds well. It's not very often the build is broken, and when it is, it's quickly fixed. 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] [ion] 19090: User-Mode Networking Rewrite for 0.2.9
by Murphy, Ged (Bolton) 09 Nov '05

09 Nov '05

Eerrmm, scratch that. I've just noticed that the ws2_32 code is already in the branch ........ and I'm currently doing a little dance at my desk !!! <homer voice> Woo Hoo!! </homer voice> -----Original Message----- From: Murphy, Ged (Bolton) Sent: 09 November 2005 11:47 To: 'ros-dev(a)reactos.org' Subject: RE: [ros-svn] [ion] 19090: User-Mode Networking Rewrite for 0.2.9 Cool, will the winsock code be in this branch anytime soon? -----Original Message----- From: ion(a)svn.reactos.com [mailto:ion@svn.reactos.com] Sent: 09 November 2005 05:07 To: ros-svn(a)reactos.com Subject: [ros-svn] [ion] 19090: User-Mode Networking Rewrite for 0.2.9 User-Mode Networking Rewrite for 0.2.9 Added files: branches/alex-network-branch/ _______________________________________________ Ros-svn mailing list Ros-svn(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-svn ************************************************************************ 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] [ion] 19090: User-Mode Networking Rewrite for 0.2.9
by Murphy, Ged (Bolton) 09 Nov '05

09 Nov '05

Cool, will the winsock code be in this branch anytime soon? -----Original Message----- From: ion(a)svn.reactos.com [mailto:ion@svn.reactos.com] Sent: 09 November 2005 05:07 To: ros-svn(a)reactos.com Subject: [ros-svn] [ion] 19090: User-Mode Networking Rewrite for 0.2.9 User-Mode Networking Rewrite for 0.2.9 Added files: branches/alex-network-branch/ _______________________________________________ Ros-svn mailing list Ros-svn(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-svn ************************************************************************ 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

Vote on constitution closed
by Casper Hornstrup 09 Nov '05

09 Nov '05

The vote on the constitution is now closed. The results are: Yes, make the constitution official 15 No, don't make the constitution official 0 Further discussion 1 This means the constitution is now accepted, effective immediately. Casper

1 0

RE: [ros-dev] VMWare 5.0 Networking issues...
by Murphy, Ged (Bolton) 09 Nov '05

09 Nov '05

You might not be doing anything wrong with regard to ipconfig. There are a couple of issues with our ipconfig in ROS at the moment. I haven't been able to look at it recently as I haven't been able to boot ROS. Now as this is fixed, I'll find some time to have a look at it. -----Original Message----- From: Richard Campbell [mailto:eek2121@comcast.net] Sent: 09 November 2005 05:31 To: ReactOS Development List Subject: [ros-dev] VMWare 5.0 Networking issues... Currently when i try to use networking with VMWare 5.0 i notice the adapter (which doesn't seem to have a name in IPConfig) has a loopback address (127.0.0.1) but no other address. Trying to renew results in a function not supported message. If i try to set a static IP then ipconfig fails with a GetAdapterInfo() error. I cannot figure out what i am doing wrong, i tried both the WinNT and win2k drivers. Any idea as to how to get networking running with VMWare 5? _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/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

VMWare 5.0 Networking issues...
by Richard Campbell 09 Nov '05

09 Nov '05

Currently when i try to use networking with VMWare 5.0 i notice the adapter (which doesn't seem to have a name in IPConfig) has a loopback address (127.0.0.1) but no other address. Trying to renew results in a function not supported message. If i try to set a static IP then ipconfig fails with a GetAdapterInfo() error. I cannot figure out what i am doing wrong, i tried both the WinNT and win2k drivers. Any idea as to how to get networking running with VMWare 5?

1 0

RE: [ros-svn] [ion] 19053: - Update KTHREAD and KUSER_SHARED_DATA tolatest versions. This should make 2K3 drivers (eg: npfs.sys)work with their inlinedKeEnterCriticalRegion/KeLeaveCriticalRegion and ASSERTS.
by Ge van Geldorp 09 Nov '05

09 Nov '05

> From: ion(a)svn.reactos.com > > - Update KTHREAD and KUSER_SHARED_DATA to latest versions. > This should make 2K3 drivers (eg: npfs.sys) work with their > inlined KeEnterCriticalRegion/KeLeaveCriticalRegion and ASSERTS. > - Update KAPC and DISPATCHER_HEADER to latest DDK definitions. This change seems to break networking in VMware. Gé van Geldorp.

3 3

TC function description: opening discussion prior to vote
by Ge van Geldorp 08 Nov '05

08 Nov '05

There was some confusion and disagreement about the Testing Coordinator function description recently. The best way to solve it seems to be a vote. With the new voting procedure established and 0.2.8 (almost) out the door, this seems a good time to start the voting process. Our (draft) constitution calls for a 5 day discussion period, followed by a 5 day voting period. This email starts the 5 day discussion period. Preferred location for the discussion is the ros-dev mailing list, since all developers have easy access to that. At the end of the discussion, I'll post a call for votes to the mailing list and create the vote on the forum. We have two proposals for the TC function description, A and B. A is the original function description. Proposal B is almost the same, the only difference is that the TC does not have the authority to block a release. This is the motion I would like to vote on: "Do you want to: A) set the function description for the TC role as described in http://www.reactos.org/wiki/index.php/ReactOS_Testing_Coordinator or B) set the function description for the TC role as described in http://www.reactos.org/wiki/index.php/ReactOS_Testing_Coordinator_Alternate" Gé van Geldorp.

5 10

WinPE Tools by TheTruth
by Robert Köpferl 08 Nov '05

08 Nov '05

Hi, I'm not experienced with networking on NT but combination says me that this tool could be an enrichment for ReactOS 0.3 It's a network configurator for win PE http://www.geocities.com/pierremounir/ Technical opinions?

7 16

RE: [ros-dev] DeviceCreateHardwarePage and control panel applets
by Murphy, Ged (Bolton) 08 Nov '05

08 Nov '05

You can work on whatever takes your interest. Grab the latest code from SVN, make your changes and submit a patch to bugzilla. -----Original Message----- From: Sebastian Gasiorek [mailto:zebasoftis@gmail.com] Sent: 08 November 2005 08:50 To: ReactOS Development List Subject: [ros-dev] DeviceCreateHardwarePage and control panel applets Hi! I would like to work on DeviceCreateHardwarePage from devmgr.dll and then implement Hardware pages in Mouse and Keyboard Control panel applet. Can I do that or maybe there is somebody who is working on than already? thanks, Sebastian ************************************************************************ 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-diffs] [greatlrd] 19038: change En.rc to defualt take care ofcode page error at lest for swedish
by Hervé Poussineau 08 Nov '05

08 Nov '05

>De : ros-diffs-bounces(a)reactos.org >[mailto:ros-diffs-bounces@reactos.org] De la part de >greatlrd(a)svn.reactos.com Envoyé : lundi 7 novembre 2005 18:35 À : >ros-diffs(a)reactos.com Objet : [ros-diffs] [greatlrd] 19038: change >En.rc to defualt take care ofcode page error at lest for swedish > >change En.rc to defualt take care of code page error at lest for >swedish >Modified: trunk/reactos/boot/freeldr/fdebug/En.rc >Modified: trunk/reactos/boot/freeldr/fdebug/En.rc >--- trunk/reactos/boot/freeldr/fdebug/En.rc 2005-11-07 10:53:52 UTC (rev 19037) >+++ trunk/reactos/boot/freeldr/fdebug/En.rc 2005-11-07 17:35:10 UTC (rev 19038) >@@ -3,7 +3,7 @@ > > > #if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENU) #ifdef _WIN32 > >-LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US >+LANGUAGE LANG_ENGLISH, SUBLANG_DEFAULT > > #pragma code_page(1252) > #endif //_WIN32 I don't agree with this change. See http://www.reactos.org/archives/public/ros-dev/2005-October/005217.html What was the problem with SUBLANG_ENGLISH_US? Regards, Hervé

2 1

DeviceCreateHardwarePage and control panel applets
by Sebastian Gąsiorek 08 Nov '05

08 Nov '05

Hi! I would like to work on DeviceCreateHardwarePage from devmgr.dll and then implement Hardware pages in Mouse and Keyboard Control panel applet. Can I do that or maybe there is somebody who is working on than already? thanks, Sebastian

1 0

RE: [ros-bugs] [Bug 957] Build 19052 - Installation fails with 'A llocConsole() failed (Status=0x90000001)'
by Murphy, Ged (Bolton) 08 Nov '05

08 Nov '05

> -----Original Message----- > From: ReactOS.Bugzilla(a)reactos.org > [mailto:ReactOS.Bugzilla@reactos.org] > Sent: 08 November 2005 05:10 > To: ros-bugs(a)reactos.com > Subject: [ros-bugs] [Bug 957] Build 19052 - Installation > fails with 'AllocConsole() failed (Status=0x90000001)' > > > http://www.reactos.org/bugzilla/show_bug.cgi?id=957 > > > paniq(a)paniq.org changed: > > What |Removed |Added > -------------------------------------------------------------- > -------------- > Severity|normal |critical > > > > > ------- Additional Comments From paniq(a)paniq.org 2005-11-08 > 06:10 CET ------- > this one is actually critical. i'm a bit reluctant to call it > critical because > it has a workaround, but not everybody possesses a failsafe > ps/2 keyboard > (unless you happen to own an intel usb onboard chip... do you > have any idea how > often these chips crash?) > This isn't critical, nor is it a bug, nor is it a a chip crashing. There is no support for USB yet. This is already documented in bugzilla ************************************************************************ 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] [OTAnn] Feedback
by TwoTailedFox 07 Nov '05

07 Nov '05

I've seen this on the VLC-SVN and Ros-SVN Mailing Lists. What exactly *is* this spam? On 11/7/05, shenanigans <maillist(a)roomity.com> wrote: > I was interested in getting feedback from current mail group users. > > We have mirrored your mail list in a new application that provides a more > aggregated and safe environment which utilizes the power of broadband. > > Roomity.com v 1.5 is a web 2.01 community webapp. Our newest version adds > broadcast video and social networking such as favorite authors and an html > editor. > > It?s free to join and any feedback would be appreciated. > > S. > > > > ---------------------------------------------------------------------------------------------------------------------------------------------- > Broadband interface (RIA) + mail box saftey = > React_OS_SVN_Commits_List.roomity.com > *Your* clubs, no sign up to read, ad supported; try broadband internet. > ~~1131397873209~~ > ---------------------------------------------------------------------------------------------------------------------------------------------- > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-svn > > -- "I had a handle on life, but then it broke"

4 3

Can I use 'distcc' to compile ReactOS?
by Andrew "Silver Blade" Greenwood 07 Nov '05

07 Nov '05

I just discovered distcc. For those who don't know, distcc is a distributed compiler utility that interfaces with gcc on Linux (and compatible platforms.) It comes as a daemon and a client - the daemon is run on each machine you wish to include in the "compiler farm" (so to speak), and the client is told which servers to use (via an environment variable.) When you run distcc it just acts like gcc/g++, and distributes the file to be compiled to each of the hosts. It doesn't need the headers or libraries on the hosts - the output of the preprocessor is passed to each host. Anyway... As I have a second machine which usually runs Windows solely for when I wish to make music, it's ideal for running a small Linux installation, aimed at running distcc/gcc etc. and not much else. All is well, except I cannot configure ReactOS to make use of distcc :( The standard usage for distcc (according to the authors site) is: make -j8 distcc The only way I even got close to compiling ReactOS using distcc was to hack the main Makefile and replace "gcc" with "distcc", and "g++" with "distcc g++" (to specify the compiler to use on each host.) This works perfectly... for the initial make tasks (building the build system?) but after this distcc is completely ignored. Is there a way to allow distcc to work? Ideally the Makefile should take note of the CC variable, I guess? As I have a laptop and 2 desktop machines at my disposal (plus - as I'm staying at a friends house at present - his experimental 3 GHz server box), I'd like to make use of distcc so I don't have to make so much coffee ;) Any ideas?

2 2

reactos: uncompilable
by Damjan Jovanovic 07 Nov '05

07 Nov '05

I don't know how you guys develop or release ReactOS, but I have never gotten a single release to compile cleanly. First I tried 0.2.6, and I had to edit GCC inline assembly to get it to compile, and use various hacks to get it to work. Last night I tried 0.2.7, which I had to force to compile with multiple declarations (by editing C++ files in tools/rbuild to disable the -Werror flag), force to link by 'make VERBOSE=full' and then manually copying the command line and adding 'obj-i386/hal/hal/libhal.a', and then after a few more hours, ntoskrnl.exe would not link (several thousand missing symbols). I'm gonna get 0.2.8 now and try again, with the Windows version of mingw (been using Linux so far). Just in case, would someone explain to me how you guys get it to compile? And how do you expect anyone to develop an OS that is practically uncompilable? Damjan __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com

5 4

Piles upon piles of regressions
by Alex Ionescu 07 Nov '05

07 Nov '05

Hi, I realize maybe some of you are aware of these, but it seems that we just keep adding more and more regressions and there hasn't really been an effort to fix them... We don't have a TC anymore and now the tree is becoming as bad as before, which just proves the point of how badly this project needed a TC. I've just booted ROS for the first time in a month and I'm surprised at the number of new things that have cropped up. The start menu became huge, the registry is not cleanly dereferenced at shutdown (causing it to get damaged and that makes freeldr display the "Codepage error"), dhcp still crashes on first-boot since networking isn't installed, the 16x16 icons look like crap since alphablending was implemented, all sorts of drivers "fail to load' on startup, RPC displays messages about "Buffer overflows", umpnpmgr tries to copy invalid drivers, shutdown still doesn't work on my QEMU,... and this is only what I've noticed after 2 minutes. Anyways, I don't want to nitpick, just to bring these issues up to attention in case noobdy is aware of them. Best regards, Alex Ionescu

2 1

install problem
by Hartmut Birr 06 Nov '05

06 Nov '05

Hi, since some time, I'm not able to install ReactOS on real hardware. Freeldr fails at the first boot after the second stage setup. The error message is 'Couldn't open CodePage registry key'. I've add some debug messages to freeldr. Freeldr isn't able to open the key '\Registry\Machine\SYSTEM\CurrentControlSet'. If I rename umpnpmgr.exe between usetup and the second stage setup, ReactOS boots without any problems. If I rename umpnpmgr.exe back, ReactOS fails on the second boot with umpnpmgr.exe. - Hartmut

5 4

Where to commit?
by Brandon Turner 05 Nov '05

05 Nov '05

I have interesting in working on the following programs: C:\WINDOWS\system32\tree.exe C:\WINDOWS\system32\gettype.exe(win2k3) C:\WINDOWS\system32\findstr.exe C:\WINDOWS\system32\w32tm.exe and if I'm feeling extra fiesty maybe C:\WINDOWS\system32\osk.exe Now my question is where i should put these, rospapps or maybe reactos\subsys\system\ ? Brandon

5 6

[ros-dev] RE:[blight] 19008: Implement (Int)EngAlphaBlend and 8, 16, 24 and 32 bpp DIB AlphaBlend functions. AlphaBlend()should work now.
by Ge van Geldorp 05 Nov '05

05 Nov '05

> From: blight(a)svn.reactos.com > > Implement (Int)EngAlphaBlend and 8, 16, 24 and 32 bpp DIB > AlphaBlend functions. AlphaBlend() should work now. Great work. Not sure if you realized it, but this helps Firefox a lot. Screenshot with these changes applied: http://www.reactos.nl/pics/ff2.png (the "before" screenshot is at http://www.reactos.nl/pics/ff1.png see the difference in the toolbars) Thanks again, Gé.

1 0

NPFS problems
by Ge van Geldorp 04 Nov '05

04 Nov '05

After changes r18883/r18912 umpnpmgr.exe (and eventlog.exe) don't start anymore. The problem is that they try to connect to the service control manager using a named pipe (advapi32/service/sctrl.c function ScConnectControlPipe). Before opening the pipe, a call is made to WaitNamedPipe() to see if the pipe exists. This call currently fails, resulting in failure of ScConnectControlPipe(), resulting in failure of umpnpmgr.exe, resulting in network drivers not being installed, resulting in no network connectivity. WaitNamedPipe() NtOpenFile()s the pipe and then issues a FSCTL_PIPE_WAIT ioctl. The problem is that this end of the pipe is now connected to the server end (which is already listening) during the call to NtOpenFile() (in function NpfsCreate(), setting the PipeStatus to FILE_PIPE_CONNECTED_STATE. NpfsWaitPipe first checks the PipeStatus and bails out if it's not 0 (passive waiting state). So, in our case NpfsWaitPipe fails, 'cause the pipe is already connected. The patch below just makes NpfsWaitPipe return success in case it's already connected, which solves the umpnpmgr problem. However, I don't think it's the correct solution, after the FSCTL_PIPE_WAIT ioctl returns WaitNamedPipe() will close its end, so the server end sees an unexpected close. I have no clue how to proceed, and to be honest I'm not interested in solving it myself. I'd rather see the author of the original patch take his responsibility and fix the regression he introduced. GvG.

7 10

Re: [ros-svn] [blight] 18997: Import Mesa-6.4 release. (Thanks GvG :-)
by Jirka Doubek 04 Nov '05

04 Nov '05

Sorry, I was too fast with my question... Jirka

1 0

Re: [ros-svn] [blight] 18984: Import Mesa-6.2 sources.
by Jirka Doubek 04 Nov '05

04 Nov '05

Hi! Blight: I have a little question: why are you importing Mesa3d 6.2 sources, when there is a new stable version 6.4 out there? Maybe I something misunderstood (I know almost nothing about OpenGL sources and implementation in ReactOS), so there is a reason - in that case can you explain it, please? Thank you very much. Best regards, Jirka

1 0

RE: NPFS problems
by Ge van Geldorp 03 Nov '05

03 Nov '05

> From: Ge van Geldorp > > The patch below just makes NpfsWaitPipe > return success in case it's already connected, which solves > the umpnpmgr problem. Forgot the patch: Index: fsctrl.c =================================================================== --- fsctrl.c (revision 18977) +++ fsctrl.c (working copy) @@ -278,8 +278,13 @@ WaitPipe = (PFILE_PIPE_WAIT_FOR_BUFFER)Irp->AssociatedIrp.SystemBuffer; Pipe = Fcb->Pipe; - if (Fcb->PipeState != 0) + if (FILE_PIPE_CONNECTED_STATE == Fcb->PipeState) { + DPRINT("Pipe is already connected\n"); + return STATUS_SUCCESS; + } + else if (Fcb->PipeState != 0) + { DPRINT("Pipe is not in passive (waiting) state!\n"); return STATUS_UNSUCCESSFUL; }

1 0

patch for test/review
by Hartmut Birr 03 Nov '05

03 Nov '05

Hi, I've changed rbuild a little bit, that it can run on msys (on windows). The major changes are: - The separator (slash or back slash), exepostfix and exeprefix are initialized from environment variables. - The separators in the path for the system command are always converted for the host system. - Our own build utilities must convert paths itself (bin2res). It exist some problems with absolute paths on msys, because msys uses '/c/foo/bar' and windows 'c:\foo\bar' or 'c:/foo/bar'. I've tested the patch on msys and on windows. I cannot test the patch on linux. Currently, msys is the only way to use all cpus or cores for the build process on windows. - Hartmut

5 14

auto vs manual vc6 project files naming conflict
by Royce Mitchell III 03 Nov '05

03 Nov '05

our "make -vs6 msvc" command generates dsp files automatically for all project in the tree. At the moment, this is overwriting the following files: subsys/system/explorer/notifyhook/notifyhook.dsp subsys/system/ibrowser/ibrowser/ibrowser.dsp lib/opengl32/opengl32.dsp lib/cpl/ncpa/ncpa.dsp lib/cpl/control/control.dsp lib/cpl/appwiz/appwiz.dsp Would anybody have a problem with it if I renamed all these dsp files out of the way, or would it be better if the auto-generated dsp files were named something like notifyhook_auto.dsp? Thanks

6 8

RE: [ros-bugs] [Bug 948] New: ReactOS Hangs After Changing ISO Images
by Casper Hornstrup 02 Nov '05

02 Nov '05

Why don't 0.2.8 display filenames and line numbers in stack traces? Casper > -----Original Message----- > From: ros-bugs-bounces(a)reactos.org [mailto:ros-bugs-bounces@reactos.org] On Behalf Of > ReactOS.Bugzilla(a)reactos.org > Sent: 2. november 2005 10:49 > To: ros-bugs(a)reactos.com > Subject: [ros-bugs] [Bug 948] New: ReactOS Hangs After Changing ISO Images > > http://www.reactos.org/bugzilla/show_bug.cgi?id=948 > > Summary: ReactOS Hangs After Changing ISO Images > Product: ReactOS > Version: 0.2.8 > Platform: VMWare 5 > OS/Version: Microsoft Windows NT 4.0 > Status: NEW > Severity: major > Priority: P3 > Component: Kernel > AssignedTo: ros-bugs(a)reactos.com > ReportedBy: the80sphreak(a)yahoo.co.uk > QAContact: ros-bugs(a)reactos.com > > > Hi there, > > I am using ReactOS inside vmware 5.0 on a Pentium 4 (2GHZ) laptop with 768MB > Ram, 20GB Hard disk and windows XP Home + SP2. During my testing of ReactOS > 0.2.8, I unmounted one CD image, and mounted another. This caused ReactOS to > hang and VMWare to report the processor being halted by the guest OS. I tried > a reboot, but this did not help, and now any time I try and access CDs > (physical or ISO,) ReactOS hangs with a BSOD. > > I have posted 2 screenshots on my website at: > > http://www.geocities.com/the80sphreak/reactos.jpg > http://www.geocities.com/the80sphreak/reactos2.jpg > > If you require any more information, please send me an email at: > > the80sphreak(a)yahoo.co.uk > > Thanks, > > R. McLay > > -- > Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > You are the QA contact for the bug, or are watching the QA contact. > _______________________________________________ > Ros-bugs mailing list > Ros-bugs(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-bugs

2 2

RE: [ros-dev] Re: [ros-bugs] [Bug 949] New: command prompt needs a buffer and scroll bar
by Murphy, Ged (Bolton) 02 Nov '05

02 Nov '05

> -----Original Message----- > From: Brandon Turner [mailto:turnerb7@msu.edu] > Sent: 02 November 2005 15:37 > To: ros-dev(a)reactos.org > Subject: [ros-dev] Re: [ros-bugs] [Bug 949] New: command > prompt needs a buffer and scroll bar > > > Hello, > > I am quite confused about all this and im sure someone can > explain it to > me. When using ROS cmd on windows, it has a scroll bar but > when using > it on ROS it doesnt. What is causing this to happen, someone > said it in > IRC a few days ago and i glanced over the code real quick to see if i > could find out but i couldnt. Ill look more later but if > anyone knows > could you please explain this to me. > > Brandon > Hi Brandon. I hadn't realised this, I've never tried our cmd in Windows. Does it also have a configurable buffer? 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-bugs] [Bug 949] New: command prompt needs a buffer and scroll bar
by Brandon Turner 02 Nov '05

02 Nov '05

Hello, I am quite confused about all this and im sure someone can explain it to me. When using ROS cmd on windows, it has a scroll bar but when using it on ROS it doesnt. What is causing this to happen, someone said it in IRC a few days ago and i glanced over the code real quick to see if i could find out but i couldnt. Ill look more later but if anyone knows could you please explain this to me. Brandon ReactOS.Bugzilla(a)reactos.org wrote: >http://www.reactos.org/bugzilla/show_bug.cgi?id=949 > > Summary: command prompt needs a buffer and scroll bar > Product: ReactOS > Version: TRUNK > Platform: x86 Hardware > OS/Version: ReactOS > Status: NEW > Severity: enhancement > Priority: P3 > Component: Win32 > AssignedTo: ros-bugs(a)reactos.com > ReportedBy: gedmurphy(a)gmail.com > QAContact: ros-bugs(a)reactos.com > > >Feature request. > >It can be fustrating not being able to scroll back up to previous output. >I think the addition of a buffer and scroll bar would greatly enhance the >ReactOS command prompt. > > >

3 3

Fwd: SOURCEFORGE.NET UPDATE - 2005-10-31 EDITION
by Wesley Parish 02 Nov '05

02 Nov '05

KeePass Password Safe sounds interesting. Anyone been in touch with the key developer/s? Wesley Parish ---------- Forwarded Message ---------- Subject: SOURCEFORGE.NET UPDATE - 2005-10-31 EDITION Date: Wed, 02 Nov 2005 05:57 From: "SourceForge.net Team" <noreply(a)sourceforge.net> To: wes.parish(a)paradise.net.nz (You have acquired this SF.net update because you requested to be on the list. Honest! An explanation is at the bottom of this email, and also info on how to be extracted from the list.) <snip> 17. KeePass Password Safe https://sourceforge.net/projects/keepass KeePass Password Safe is a free, open-source, light-weight and easy-to-use password manager for Windows. You can store your passwords in a highly-encrypted database, which is locked with one master key or key-disk. <snip> ------------------------------------------------------- -- Clinersterton beademung, with all of love - RIP James Blish ----- Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people.

1 0

0.3.0 roadmap
by Murphy, Ged (Bolton) 01 Nov '05

01 Nov '05

We've been saying this for the past 12 months now, but as work in networking has stepped up a gear, it looks as though 0.3.0 is imminent, and could be ready within the next few months. In light of this, I've been though the 0.3.0 roadmap and updated it to what appears to be peoples current perception of requirements. http://www.reactos.org/wiki/index.php/0.3.x/0.3.0 <http://www.reactos.org/wiki/index.php/0.3.x/0.3.0> It would be really great if we could pull out all the stops and get this release out for Christmas. ************************************************************************ 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

[VOTE] Constitution
by Casper Hornstrup 01 Nov '05

01 Nov '05

Should we make the constitution the official document that describes the basic rights of the project members and the decision making processes of the project? I've started the vote at http://www.reactos.org/forum/viewtopic.php?t=1043. = Introduction = This document explains the decision making entities, their abilities and the decision making processes of the ReactOS Project. = Terminology = ReactOS: Free/Open Source Operating System that is compatible with Microsoft WindowsR applications and drivers. ReactOS Project: A community of individuals and organisations dedicated to making a Free/Open Source Operating System compatible with Microsoft WindowsR based applications and drivers. Project: See ReactOS Project. ReactOS Foundation: US non-profit (501c3) organisation with goal to aid the ReactOS Project in achieving its goal of creating a Free/Open Source Operating System that is compatible with Microsoft WindowsR based applications and drivers. Foundation: See ReactOS Foundation. Constitution: Document explaining decision making entities, their abilities and decision making processes of an organisation. May: The action may be performed. Must: The action must be performed in order to abide this Constitution. Should: The action should be performed, but it is not required. Repository: Central database containing the source code, documentation, and other files used by the Project. Registered Project Member: An individual participating in the Project who has received authentication information for the Repository. Unregistered Project Member: An individual participating in the Project who has not received authentication information for the Repository. Project Member: Registered or Unregistered Project Member. Coordinator Description: Document defining an area of responsibility and special abilities. Project Coordinator: Registered Project Member who has special abilities. Only one Project Coordinator exist in the Project. Area Coordinator: Registered Project Member who has special abilities within a given area. Several Area Coordinators exists in the Project. Repository Coordinator: Registered Project Member who can promote Unregistered Project Members to Registered Project Members. Coordinator Election: Process which results in a Registered Project Member being promoted to Repository Coordinator, Area Coordinator or Project Coordinator. General Resolution: Document containing a proposal and rationale for a change within the Project. Project Rules: Formal rules established by way of General Resolution that Must be adhered to by all Project Members. Standard Resolution Procedure: Procedure used to make a decision. = General rules = * No Project Member can be forced to perform a task. However, in case a Project Member has made a contribution, and the general consensus among the Project Members is that the contribution is harmful to the Project, then the Project Member Should undo the contribution. * A Project Member can leave the Project at any given time. Before leaving the Project, the Project Member Should issue a statement containing their intentions to leave the Project on a public Project mailing list. A former Project Member May rejoin the Project at any time again. * The Project Coordinator Must not be assigned another Coordinator position. * All Project Rules, Coordinator Descriptions, and Coordinator Elections Must be documented in a central location accessible by all Project Members. = Decision making entities of the Project = The decision making entities of the Project are listed below: * The Registered Project Members, by way of General Resolution or Coordinator Election. * The individual Registered Project Member. * The Project Coordinator. * The individual Area Coordinator. * The Repository Coordinator. * The Project Secretary. * The individual Unregistered Project Member. == The Registered Project Members, by way of General Resolution or Coordinator Election == The Registered Project Members are Project Members who have received authentication information for the Repository from the Repository Coordinator. Registered Project Members have the right to vote and can exercise their right to vote in order to: * Override any decision made by the Project Secretary or any Coordinator. * Appoint or dismiss the Project Secretary or any Coordinator. * Amend this Constitution provided there is a 3:1 majority. * Introduce new Project Rules. * Remove existing Project Rules. * Override any decision made by any individual Project Member. * Undo any contribution and reverse any reversible action made by any individual Project Member. The Registered Project Members follow the Standard Resolution Procedure when making decisions. == The individual Registered Project Member == The individual Registered Project Member can: * Propose General Resolutions. * Nominate themselves as candidates in Coordinator Elections. * Vote on General Resolutions and in Coordinator Elections. * Do everything an Unregistered Project Member can do. == The Project Coordinator == The Project Coordinator Should attempt to make decisions according to the consensus of the Project Members. The Project Coordinator is elected by way of Coordinator Election to a one (1) year term of office. The Project Coordinator can: * Define an area of responsibility and abilities that does not conflict with this Constitution and delegate them to a Registered Project Member (whom is thereby promoted to Area Coordinator) by way of Coordinator Election. The defined area of responsibility and abilities is collectively called a Coordinator Description. * Make a decision when urgent action is required. * Make any decision for whom nobody else has responsibility. * In cooperation with the ReactOS Foundation, manage the properties of the ReactOS Project in the best interest of ReactOS. * Do everything an individual Registered Project Member can do. == The individual Area Coordinator == The Area Coordinator is appointed by way of Coordinator Election and has the responsibilities and abilities for a particular area as defined in the Coordinator Description for that particular area. The Area Coordinator holds the position until the Area Coordinator resigns or until Coordinator Election for that area occur. The Area Coordinator can: * Do whatever is described in the Coordinator Description for that particular area. * Do everything an individual Registered Project Member can do. == The Repository Coordinator == The Repository Coordinator Should issue authentication information for the Repository to whomever the Repository Coordinator judges to provide contributions which are valuable to the Project in the future, and is believed by the Repository Coordinator to be able to use the granted access responsibly. Once the Unregistered Project Member has received authentication information, the Unregistered Project Member is promoted to Registered Project Member. The Repository Coordinator must keep records of everyone who has access to the Repository. The records must include full name, email address and assigned Repository username of each Registered Project Member. Full name and assigned Repository username of each Registered Project Member Must be made available to all Project Members. The Repository Coordinator can: * Allow or deny commit access to Project Members. * Do everything an individual Registered Project Member can do. The Repository Coordinator Should make decisions which are fair and reasonable, and preferably consistent with the consensus of the Project Members. == The Project Secretary == The Project Secretary is a Registered Project Member who is appointed by the Project Coordinator. The Project Secretary collects votes amongst the Registered Project Members on General Resolutions or Coordinator Elections, and determines the identities of Registered Project Members who exercises their right to vote. The Project Secretary Must document General Resolutions and Coordinator Elections, the voting process, and the outcome that resulted from the voting process. The Project Secretary can: * Adjudicate any disputes about the interpretation of this Constitution. * Delegate parts or all of their authority to another Registered Project Member, or withdraw such a delegation at any time. * Do everything an individual Registered Project Member can do. The Project Secretary Should make decisions which are fair and reasonable, and preferably consistent with the consensus of the Project Members. == The individual Unregistered Project Member == The individual Unregistered Project Member can: * Make any decision with regard to their own contributions to the Project as long as these contributions do not conflict with the current Project Rules established by way of General Resolution. = Standard Resolution Procedure = The Standard Resolution Procedure is used to make decisions in the Project and at the same time ensure that all Registered Project Members have equal opportunity to influence these decisions. == The procedure == The resolution procedure is described below: * The procedure begins when a draft General Resolution is announced on a public Project mailing list. * Following the announcement of a draft General Resolution, its contents may be discussed on the same public Project mailing list on which the draft General Resolution was announced. * The proposer of the draft General Resolution May change the contents of the draft General Resolution until the voting begins. * A formal amendment May be accepted by the proposer of the draft General Resolution, in which case the draft General Resolution is immediately changed to match the amendment. * If a formal amendment is not accepted by the proposer of the draft General Resolution, the amendment remains as an amendment and will be voted on. * The length of the discussion period May be specified in the draft General Resolution. If not specified, then 7 days is assumed. The discussion period begins at the time when the draft General Resolution or amendment was announced on a public Project mailing list. * If the proposer of the draft General Resolution makes semantic changes to it, then the discussion period is restarted, and thus begins at the time of announcement of the changed draft General Resolution. Minor non-semantic changes (e.g. typographical errors or inconsistencies) will not cause the discussion period to be restarted. This also applies to amendments and their proposers. == Calling for a vote == The proposer of a draft General Resolution May call for a vote on the General Resolution and relevant amendments, provided that the discussion period has elapsed for the General Resolution and all related amendments. The proposer can call for a vote by posting to the public Project mailing list on which the draft General Resolution was first sent to. == Voting procedure == The voting procedure is described below: * The General Resolution and its related amendments is voted on in a single ballot that includes an option for the original General Resolution, each relevant amendment, and the default option (where applicable). * The votes from Registered Project Members are registered in a public Project information system. * Unless specified otherwise, the default option is Further Discussion. * The length of the voting period May be specified in the draft General Resolution. If not specified, then 7 days is assumed. The voting period begins at the time the vote was called for on a public Project mailing list by the proposer of the draft General Resolution. * The Project Secretary Should decide on matters of procedure in cases of doubt. == Withdrawing General Resolutions or unaccepted amendments == The proposer of a General Resolution or unaccepted amendment May withdraw it before the voting begins. Other Registered Project Members May reinstate it again, in which case the first Registered Project Member to do so becomes the new proposer. == Expiry of General Resolutions == In case a proposed General Resolution has not been discussed, amended, voted on or otherwise dealt with for a period of 4 weeks or more, the Project Secretary May issue a statement on the public Project mailing list on which the draft General Resolution was first sent to, that the issue is being withdrawn. If none of the proposers object within one (1) week, the issue is withdrawn. == Vote counting == The votes from each Registered Project Member who exercise his or her right to vote are registered in a public Project information system. Whichever General Resolution or amendment gets the most valid votes is passed, unless a 3:1 majority is required. The Project Secretary Must document the result of the voting in a public Project information system if it meant that a new Project Rule was introduced or the Constitution was amended. = General Resolutions = A General Resolution Must contain the following information: * A subject that describes the General Resolution. * The Repository username of the Registered Project Member that proposed it. * The number of days of discussion which May be "None" if the proposer judges such a period to not be needed. If not specified, then 7 days is assumed. * The number of days of voting which Must be at least 2 days and at most 21 days. If not specified, then 7 days is assumed. * A detailed explanation of the General Resolution. * Rationale for the General Resolution. * If more than half of the valid votes must be in favor of the change proposed in the General Resolution in order for the change to be in effect, then it must be clearly stated in the General Resolution how many votes that are required to be in favor for it to be passed. = Coordinator Elections = A Coordinator Election is held when a Coordinator position needs to be filled or whenever the Registered Project Members demand it by way of General Resolution. == The procedure == The Coordinator Election procedure is described below: * The procedure begins when the Project Secretary announcing the Coordinator Election on a public Project mailing list, asking for candidates for the Coordinator position that needs to be filled. The Project Secretary Must include, in the announcement, the Coordinator Description which describes the area of responsibility and abilities of the Registered Project Member who receives the Coordinator position. * In the following one (1) week from the announcement of the Coordinator Election, each Registered Project Member May announce on the same public Project mailing list on which the Coordinator Election was announced, that they will run as a candidate for the Coordinator position. * Once the candidates are found, the Project Secretary announces the candidates for the Coordinator position and calls for a vote on the same public Project mailing list on which the Coordinator Election was announced. * In the following one (1) week from the announcement of the vote, the candidates May do their campaigning on the same public Project mailing list on which the vote was announced, and each Registered Project Member May vote for any of the available candidates by registering their votes in a public Project information system. == Vote counting == The votes from each Registered Project Member who exercise his or her right to vote are registered in a public Project information system. Whichever candidate gets the most valid votes, wins the election. The Project Secretary Must document the result of the voting in a public Project information system.

1 0

install bug
by Hartmut Birr 01 Nov '05

01 Nov '05

Hi, the 'AllocConsole() failed (Status = 0xc0000001)' bug is back. Kbdclass.sys failed to load from the bootcd, because it cannot find its registry entries. - Hartmut

1 0

About the DirectDraw test
by Magnus Olsen 01 Nov '05

01 Nov '05

Thanks every one that have tested Here is the result 1. Cretesurface does not working for nvidia GeForce FX Go5200 32M/64M and GeForce 6200 TurboCache(TM) 2. Small problem for Intel(R) 82852/82855 GM/GME surface lost Here is list on graphic card that is working Ati Radon 9200SE Ati Radeon 9600 Ati Radeon 9600 Mobility Ati Rage 128 NVidia GeForce FX Go5200 32M/64M NVidia GeForce 6800 Ultra I need to figout why it does not working for alex but it is working for Tim Jobling when it comes to nvidia GeForce FX Go5200 32M/64M. I got a idea why it does not working for Alex is using DVI and we do not provide the VideoPort struct as we should. That maybe is the main problem for alex. Thanks everone it seam few got some problem I can continue to write in ddraw.dll now. and I will try take care of CreateSurface problem. Next test will be 1-2 week. and it has the bltblt implement u will see a green surface then if everthing goes well. if get bad with time again it will take longer time to take care of this. and the next test will be delay.

1 0

About DirectDraw in reactos
by Magnus Olsen 01 Nov '05

01 Nov '05

Hi I am instread to know reactos ddraw.dll party working in windows 1. unpack the files and the files must be in same folder. 2. Double click on the exefile choice the windows mode not the fullscreen mode it will fail other wise. 3. if it working party u will see a gray windows without any dialog error have popup. I am instread in to know which os u runing it and the graphic card. and if u choice windows mode, and the error msg have been popup up or not. if u have not choice windows mode I am not instread. in the reslut. I know fullscreen does bugout and I have not track it down yet. BestReagds Magnus Olsen

8 8

Google Alerts
by Maarten Bosma 01 Nov '05

01 Nov '05

Hi, I have subscribed Google Alerts with the keyword ReactOS. Here is what I got for the 0.2.8 release. Golem.de - Germany - http://www.golem.de/0510/41322.html Der Standard - Wien,Austria - http://derstandard.at/?id=2226945 addict3d.org - USA - http://addict3d.org/index.php?page=downloadfile&ID=2322 The frist two once are german and last one is a download site. But I think anyway that it would be a good idea to sucripe the ros-dev or general mailing list at Google alerts. Maarten Bosma

2 1

New WS2.2 Binary
by Alex Ionescu 01 Nov '05

01 Nov '05

Hi All, Thanks for everyone that tested the previous Winsock 2.2 binary and for your reports. Since last week, I've done a lot of bug fixing and implemented new features, and this should reduce the number of crashes you might have seen. As always, please follow the same testing procedure as described in the last email (create a .local file for the .exe and copy the dll in the same directory). I am highly interested in the following apps: Opera, Mozilla, Outlook, P2P Applications, Bittorrent. Changelog: - Made stubs return error instead of success, so calling apps don't crash - Implemented blocking hook/callbacks, which were required for cancelling Async requests and WS1.1 functionality. - Rewrote QuerySetA<->QuerySetW conversion functions as not to overwrite, corrupt the heap and properly convert all the time. - Implemented getprotobyname/getprotobyaddr - Fixed 4 infinite loops which were hit in some cases. - Fixed cleanup on WSACleanup - Fixed SOL_PROTOINFO_A support in getsockopt - Added support for restarting lookup if WSASocketW fails with special error code - Fixed WSALookupService* functions to handle failuers with the right error codes - Added registry notifications for live catalog changes monitoring - Added code to write to the registry if entries are missing - Added RAS Auto-dial helper implementation, still incomplete. Best regards, Alex Ionescu

2 4

Move.c from cmd
by Mikhail Y. Zvyozdochkin 31 Oct '05

31 Oct '05

Hi all! Two small notes on MOVE command implementation: 1) option /Y isn't described in En.rc (and, ergo, in ALL translations); 2) NOT ALL hardcoded strings was moved from source. Yes, this ConOutPuts will never compiled (under #if 0), but maybe it's better to remove this dead code? WBR, DarkHobbit

3 3

Re: [ros-diffs] [weiden] 18883: fix some flags calculations and access rights in CreateNamedPipe and CreatePipe
by Hartmut Birr 31 Oct '05

31 Oct '05

weiden(a)svn.reactos.com wrote: > fix some flags calculations and access rights in CreateNamedPipe and CreatePipe > Modified: trunk/reactos/lib/kernel32/file/pipe.c > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/lib/kernel32/file/pipe.c* > --- trunk/reactos/lib/kernel32/file/pipe.c 2005-10-30 13:55:28 UTC (rev 18882) > +++ trunk/reactos/lib/kernel32/file/pipe.c 2005-10-30 14:51:12 UTC (rev 18883) > @@ -86,10 +89,10 @@ > > } > > Status = NtOpenFile(&WritePipeHandle, > > - FILE_GENERIC_WRITE, > > + FILE_GENERIC_WRITE | SYNCHRONIZE, > > &ObjectAttributes, > &StatusBlock, > > - 0, > > + FILE_SHARE_READ | FILE_SHARE_WRITE, > > FILE_SYNCHRONOUS_IO_NONALERT | FILE_NON_DIRECTORY_FILE); > if (!NT_SUCCESS(Status)) > { > This change does break the using of pipes which are created by CreatePipe. Usually it isn't necessary to open the end of the pipe in share mode. Each opening request generates a new instance of a pipe. FILE_SHARE_READ doesn't make sense, because this pipe-end is opened for write access. If FILE_SHARE_READ|FILE_SHARE_WRITE is used, npfs.sys interprets it as a special value and doesn't connect the pipe. This breaks compiling ros on ros. - Hartmut

2 1

RE: [ros-svn] [fireball] 18910: I don't think tracert really depe nds on winmm lib.
by Murphy, Ged (Bolton) 31 Oct '05

31 Oct '05

No it doesn't. Hadn't noticed it there, thanks. -----Original Message----- From: fireball(a)svn.reactos.com [mailto:fireball@svn.reactos.com] Sent: 31 October 2005 12:00 To: ros-svn(a)reactos.com Subject: [ros-svn] [fireball] 18910: I don't think tracert really depends on winmm lib. I don't think tracert really depends on winmm lib. Updated files: trunk/reactos/apps/utils/net/tracert/tracert.xml _______________________________________________ Ros-svn mailing list Ros-svn(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-svn ************************************************************************ 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

Hello there!
by Jonathon Keogh 31 Oct '05

31 Oct '05

Hello! My name is Jonathon, and I would like to offer some help to ReactOS Development. I can program in C/C++, [little] ASM, PHP, [little] PERL, etc. I can grasp programming languages quite quickly, as I'm 15 and program quite a bit. I'm British too. I've been watching SVN updates quite a lot recently, and I find it quite interesting how the OS is coded. I'm very interested in OSDev, too. What can I do to help? Jonny

2 1

Role of UI coordinator and committing graphical improvements
by Murphy, Ged (Bolton) 30 Oct '05

30 Oct '05

How does this work? I can't find anything in the wiki about this and it seems a bit of a grey area. There has been quite a bit of discussion about the UI recently, and I've had a few people asking me how they can get involved, as they are finding it difficult to get their ideas accepted. Two good designs that spring to mind are that of crappish and Dominic. Due to the recent interest in the GUI, I would be relatively interested in getting some of their ideas into ReactOS. I know Alex has some thoughts on improvements for 0.3 also For instance, I think the button icon and menu graphic Dominic did are much fresher and easier on the eye (see attached ... the graphic text needs tweaking). However I don't know whether I can just commit, whether there is a vote, whether MindFlyer can overrule us, etc. <<start.jpg>> Can we set some rules down so no toes are stepped on. 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

14 23

Re: [ros-dev] Vote on voting method
by Jens Collin 30 Oct '05

30 Oct '05

Robert Köpferl wrote: > As robertk I can see the forum but : > You cannot post new topics in this forum > You cannot reply to topics in this forum > You cannot edit your posts in this forum > You cannot delete your posts in this forum > You cannot vote in polls in this forum > I get the same text when I login and I cannot vote either. I'm perhaps not as active as it is required to be allowed to vote? / Jens

2 2

merging code to 0.2.8
by Ged 29 Oct '05

29 Oct '05

I've just realised the work on populating the start menu with eye candy isn't in the 0.2.8 branch. This involved links to games and core apps and was done specifically for this release to give the users something new to play with. Should we wait for the next release for this, or merge it in now? Ged.

3 2

RE: [ros-dev] Role of UI coordinator andcommitting graphicalimpro vements
by Murphy, Ged (Bolton) 29 Oct '05

29 Oct '05

Ahh right. Yes, we've sorted that :) > -----Original Message----- > From: Magnus Olsen [mailto:magnus@itkonsult-olsen.com] > Sent: 28 October 2005 23:36 > To: ReactOS Development List > Subject: Re: [ros-dev] Role of UI coordinator andcommitting > graphicalimprovements > > > I did look at the pic start.jpg it say ros is beta > but ros is alpha > > ----- Original Message ----- > From: "Ged" <gedmurphy(a)gmail.com> > To: "ReactOS Development List" <ros-dev(a)reactos.org> > Sent: den 29 October 2005 00:02 > Subject: Re: [ros-dev] Role of UI coordinator andcommitting > graphicalimprovements > > > > Magnus Olsen wrote: > > > ReactOS is not in beta we are in alpha > > > > I never said it was. I don't understand your email. > > > > 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

0.2.8 Release
by Brandon Turner 28 Oct '05

28 Oct '05

Hi, I have just finished building all the packages for 0.2.8 and they are ready for release. Please don't commit anything furthur to this branch. I would like to release it to sf right now. However we lack a changelog. I guess I dont know how important this really is, if it isnt important then we can just release? I think it is important and would like to see it filled out. Shall i wait till tomorrow or maybe sunday before I release it? all commits to between 027 and 028 can be found at www.msu.edu/~turnerb7/028.full.txt Brandon

1 0

RE: [ros-diffs] [arty] 18825: Added build xml.
by Casper Hornstrup 28 Oct '05

28 Oct '05

Is that really required to be a bootstrap driver? _____ From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of arty(a)svn.reactos.com Sent: 28. oktober 2005 09:04 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [arty] 18825: Added build xml. Added build xml. Added: trunk/reactos/drivers/dd/green/green.xml _____ Added: trunk/reactos/drivers/dd/green/green.xml --- trunk/reactos/drivers/dd/green/green.xml 2005-10-28 07:03:31 UTC (rev 18824) +++ trunk/reactos/drivers/dd/green/green.xml 2005-10-28 07:04:05 UTC (rev 18825) @@ -0,0 +1,14 @@ +<module name="green" type="kernelmodedriver" installbase="system32/drivers" installname="green.sys"> + <bootstrap base="reactos" /> + <define name="__USE_W32API" /> + <library>ntoskrnl</library> + <library>hal</library> + <file>createclose.c</file> + <file>dispatch.c</file> + <file>green.c</file> + <file>keyboard.c</file> + <file>misc.c</file> + <file>pnp.c</file> + <file>screen.c</file> + <file>green.rc</file> +</module>

1 0

mingw32-make erros in rbuild
by tobitosso 28 Oct '05

28 Oct '05

I want to build. revision 18766 of ReactOS I typed in mingw32-make bootcd in my MSYS window but GCC (both, 3.4.2 and 3.4.4) return these errors in mingw.cpp: [CC] toolsrbuildbackendmingwmingw.cpp tools\rbuild\backend\mingw\mingw.cpp:18:23: ../../pch.h: No such file or directory . . . When I replace "#include "../../pch.h" with "#include "pch.h", the erros does not occur any more. This error occurs also in other files and its just the same so I only write what I replaced with what in which file(the base dir I am using for this is tools\rbuild: backend/mingw/mingw.h: #include "../backend.h" -> #include "backend/backend.h" backend\mingw/modulehandler.h #include "../backend.h" -> #include "backend/backend.h" backend/mingw/mingwmodulehandler.cpp: #include "../../pch.h" -> #include "pch.h" #include "../../rbuild.h" -> #include "rbuild.h" backend/mingw/proxymakefile.cpp: #include "../../pch.h" -> #include "pch.h" backend\devcpp/devcpp.h: #include "../backend.h" -> #include "backend/backend.h" backend\msvc/genguid.cpp: #include "../../pch.h" -> #include "../../../pch.h" backend\msvc/msvc.h: #include "../backend.h" -> #include "../../backend.h" backend\msvc/msvc.cpp: #include "../mingw/mingw.h" -> #include "../../mingw/mingw.h" backend\backend.cpp: #include "../pch.h" -> #include "pch.h" #include "../rbuild.h" -> #include "rbuild.h" backend\backend.h: #include "../rbuild.h" -> #ifndef __MSVC_H__ #include "rbuild.h" #else #include "../rbuild.h" #endif Now building rbuild works. ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

4 7

RE: [ros-dev] Re: [ros-svn] [gedmurphy] 18814: - start of a rewri te for ipconfig
by Murphy, Ged (Bolton) 28 Oct '05

28 Oct '05

> -----Original Message----- > From: Tim Jobling [mailto:tjob800@yahoo.co.uk] > Sent: 28 October 2005 09:44 > To: ReactOS Development List > Subject: Re: [ros-dev] Re: [ros-svn] [gedmurphy] 18814: - > start of a rewrite for ipconfig > > > Having said that, I am pleased to see that someone is working > in this area > of the networking apps, please do keep up the good work. Adding a full suite of network apps is one of the areas I'm interested in (along with the network model in general right down to NDIS) and my aim was to have all the network apps pretty much complete for the 0.3 release. Due to missing functionality in our iphlpapi it's not going to be possible, but most the general functionality of arp, tracert, netstat, ipconfig and route is now in place and their output simulates that of the MS tool suite. I really need to start working on iphlpapi soon, but services and the GUI have recently caught my attention ... heh. > No need to add it back. When I looked at it last night I glanced at your > _tmain function, containing the command line is parsing, I noticed it looked > almost identical to my main. So I questioned if it really was a rewrite. > Having read through the rest of the file, I see that most of it is new. Glad your not offended. As a learning process for me, I've been rewriting much of the existing code. This has also had the added benefit of being able to simulate the MS tools easier, as I had a general framework in my head to code to instead of trying to decipher and modify existing code. I didn't realise you still read the mailing lists. Does this mean you might return at some point? It would be nice to have another developer from the UK back on board, as at the moment, I'm the only one fighting our cause .... lol :) 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-dev] Re: [ros-svn] [gedmurphy] 18814: - start of a rewri te for ipconfig
by Murphy, Ged (Bolton) 28 Oct '05

28 Oct '05

> -----Original Message----- > From: Murphy, Ged (Bolton) [mailto:MurphyG@cmpbatteries.co.uk] > Sent: 28 October 2005 08:05 > To: 'ReactOS Development List' > Subject: RE: [ros-dev] Re: [ros-svn] [gedmurphy] 18814: - > start of a rewri te for ipconfig > > > > > -----Original Message----- > > From: Tim Jobling [mailto:tjob800@yahoo.co.uk] > > Sent: 28 October 2005 00:50 > > To: ros-dev(a)reactos.org > > Subject: [ros-dev] Re: [ros-svn] [gedmurphy] 18814: - start > > of a rewrite for ipconfig > > > > > > Ged, > > > > Whilst I applaud your efforts in tidying and advancing > > ipconfig.c, I must > > say that I think it is bad form to remove the previously > > named authors from > > the header and replace with only your own name. > > > > Kind regards, > > Tim Jobling. > > Who was on it before me? > I stripped it down and started again. > > Ged. I just diffed against the previous revision and noted Rob Dickinson and your name. Pretty much all of the code from that revision has been replaced, with the acception of the manner in which the command line is parsed. http://svn.reactos.com/viewcvs/trunk/reactos/apps/utils/net/ipconfig/ipconfi g.c?rev=18814&r1=18297&r2=18814 I would assume this is classed as a rewrite and previous revision details aren't therefore noted in the source, but are accessible via the SVN logs. If this is incorrect, or you feel offended, I will put the revision history back in the file. 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-dev] Re: [ros-svn] [gedmurphy] 18814: - start of a rewri te for ipconfig
by Murphy, Ged (Bolton) 28 Oct '05

28 Oct '05

> -----Original Message----- > From: Tim Jobling [mailto:tjob800@yahoo.co.uk] > Sent: 28 October 2005 00:50 > To: ros-dev(a)reactos.org > Subject: [ros-dev] Re: [ros-svn] [gedmurphy] 18814: - start > of a rewrite for ipconfig > > > Ged, > > Whilst I applaud your efforts in tidying and advancing > ipconfig.c, I must > say that I think it is bad form to remove the previously > named authors from > the header and replace with only your own name. > > Kind regards, > Tim Jobling. Who was on it before me? I stripped it down and started again. 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] [gedmurphy] 18814: - start of a rewrite for ipconfig
by Tim Jobling 28 Oct '05

28 Oct '05

Ged, Whilst I applaud your efforts in tidying and advancing ipconfig.c, I must say that I think it is bad form to remove the previously named authors from the header and replace with only your own name. Kind regards, Tim Jobling. ----- Original Message ----- From: <gedmurphy(a)svn.reactos.com> To: <ros-svn(a)reactos.com> Sent: Friday, October 28, 2005 12:13 AM Subject: [ros-svn] [gedmurphy] 18814: - start of a rewrite for ipconfig >- start of a rewrite for ipconfig > - simulate the MS netstat utilitys output > - again, it's incomplete, but commiting for SVN log purposes. > > > Updated files: > trunk/reactos/apps/utils/net/ipconfig/ipconfig.c > trunk/reactos/apps/utils/net/ipconfig/ipconfig.rc > trunk/reactos/apps/utils/net/ipconfig/ipconfig.xml > > Deleted files: > trunk/reactos/apps/utils/net/ipconfig/trace.c > trunk/reactos/apps/utils/net/ipconfig/trace.h > ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com

2 2

Re: [ros-svn] [gedmurphy] 18814: - start of a rewrite for ipconfig
by Ged 27 Oct '05

27 Oct '05

gedmurphy(a)svn.reactos.com wrote: > - start of a rewrite for ipconfig > - simulate the MS netstat utilitys output > Sorry, that should say 'simulate the MS ipconfig utility output' I wasn't thinking ;) > - again, it's incomplete, but commiting for SVN log purposes. >

1 0

RE: [ros-dev] Role of UI coordinator and committing graphical imp rovements
by Murphy, Ged (Bolton) 27 Oct '05

27 Oct '05

Alex Ionescu wrote: > Wow, Dominic's design is just amazing. Is that a real local copy or a > mockup? I'm all for it, the icons and all are great! The icons are from Vista, so that's a no go. But some other bits we can use. There is a discussion here with a nice screenshot : http://www.reactos.org/forum/viewtopic.php?t=985 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

Change Log for 0.2.8
by Brandon Turner 27 Oct '05

27 Oct '05

I am going to do the releases tonight at 9pm-ish EST. So if you have anything that should be fixed in 0.2.8 please get it in soon. Please get your changes added to http://www.reactos.org/wiki/index.php/ChangeLog-0.2.8 before 1pm Friday. That is when i will upload sf, and hopfully(GvG/MgW/Frik?) can change reactos.org and add a new accounment. For devs that dont get their changes in I do have a _rough_ log of what changes devs have made that I think are important and before I release I will add them myself but no grauntee that it will cover everything you have done. Thanks! Brandon

1 0

FW: Issue 3. [Re: [ros-general] ROS-User-Issues]
by Murphy, Ged (Bolton) 27 Oct '05

27 Oct '05

Sorry, just realised I sent this to your address, instead of the list. -----Original Message----- From: Murphy, Ged (Bolton) Sent: 27 October 2005 13:56 To: 'jwalsh(a)bigpond.net.au' Subject: RE: Issue 3. [Re: [ros-general] ROS-User-Issues] > -----Original Message----- > From: jwalsh(a)bigpond.net.au [mailto:jwalsh@bigpond.net.au] > Sent: 27 October 2005 13:26 > To: ReactOS General List > Cc: Murphy, Ged (Bolton) > Subject: RE: Issue 3. [Re: [ros-general] ROS-User-Issues] > > > Please do me a favour: just take a look at his 98/95 micro > (hybrid) and then tell me again what you think. He has even > reduced it to flash card. I'm not talking about how many features you can remove from 9x, or how small and fast you can make it. I'm talking about it's architectural design. The kernel, memory management, GDI. It's inherently insecure and unstable. To take one or two examples: Most of the GDI is nonreentrant. It applies system wide mutex's blocking other threads. Process memory is visible and writable from all other process, meaning any process can potentially corrupt data used by another process. Parts of the kernel mode are writable from user mode. There is no security system worth mentioning. There are many many other design issues and I don't know, and am not about to start listing them all. The NT design solved these issues. > No future for 9x? Microsoft is making threats, but it is > still supporting 9x. They are still supporting it (to an extent) because it's a problem they created, and it has their name written all over it. There are still too many 9x users floating about to cast it aside. > They are not so brash that they would insult their client base. It wasn't meant as an insult. You've taken this too seriously. > What makes you so cocksure of yourself? I'm not. > His software cost me $45 and I got good service and it works > first time, it is so lean that I can make a ghost backup in > under 3 minutes. Great. But it's still 3 minutes of backing up a bad system which could have been time better spent :p (I'm being sarcastic) > I have been running a test for three weeks on a separate > machine, without any protection, except that provided by a > router, I have even rejected the Windows Updates. Admittedly > I don't surf, but in principle and under restricted > conditions it works. Running with no protection is crazy, even if you have locked down your router. Not monitoring your system using the correct precautions is irresponsible. > And what is more Shane does not blame his users. > Nor does he resort to cheap shots. I'm sorry you have taken this to heart, is was not meant like that. > ReactOS, after three expensive downloads, still does not work. > But I am still not giving up on it, nor you for that matter. Expensive? It's completely free, where is the cost? ************************************************************************ 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-diffs] [gvg] 18782: Change Tcpip and Afd drivers from auto-start to system-start, since we don't
by xnavara＠volny.cz 27 Oct '05

27 Oct '05

This is change is wrong. We start auto-start drivers, but we stop on first failure (see subsys/system/services). You're just workarounding the real problem. - Filip ----- PŮVODNÍ ZPRÁVA ----- Od: gvg(a)svn.reactos.com Komu: ros-diffs(a)reactos.com Předmět: [ros-diffs] [gvg] 18782: Change Tcpip and Afd drivers Datum: 27.10.2005 - 1:28:07 > Change Tcpip and Afd drivers from auto-start to system-start, > since we > don't > auto-start device drivers yet > Modified: trunk/reactos/bootdata/hivesys.inf > _____ > > Modified: trunk/reactos/bootdata/hivesys.inf > --- trunk/reactos/bootdata/hivesys.inf 2005-10-26 23:19:37 UTC > --- (rev > 18781) > +++ trunk/reactos/bootdata/hivesys.inf 2005-10-26 23:26:44 UTC > (rev > 18782) > @@ -365,7 +365,7 @@ > > > HKLM,"SYSTEM\CurrentControlSet\Services\Afd","ErrorControl",0x00010001,0 > x00000001 > HKLM,"SYSTEM\CurrentControlSet\Services\Afd","Group",0x00000000,"TDI" > > HKLM,"SYSTEM\CurrentControlSet\Services\Afd","ImagePath",0x00020000,"sys > tem32\drivers\afd.sys" > -HKLM,"SYSTEM\CurrentControlSet\Services\Afd","Start",0x00010001,0x00000 > 002 > +HKLM,"SYSTEM\CurrentControlSet\Services\Afd","Start",0x00010001,0x00000 > 001 > > HKLM,"SYSTEM\CurrentControlSet\Services\Afd","Type",0x00010001,0x0000000 > 1 > > ; Atapi miniport driver > @@ -615,7 +615,7 @@ > > HKLM,"SYSTEM\CurrentControlSet\Services\Tcpip","ErrorControl",0x00010001 > ,0x00000001 > > HKLM,"SYSTEM\CurrentControlSet\Services\Tcpip","Group",0x00000000,"PNP_T > DI" > > HKLM,"SYSTEM\CurrentControlSet\Services\Tcpip","ImagePath",0x00020000,"s > ystem32\drivers\tcpip.sys" > -HKLM,"SYSTEM\CurrentControlSet\Services\Tcpip","Start",0x00010001,0x000 > 00002 > +HKLM,"SYSTEM\CurrentControlSet\Services\Tcpip","Start",0x00010001,0x000 > 00001 > > HKLM,"SYSTEM\CurrentControlSet\Services\Tcpip","Type",0x00010001,0x00000 > 001 > ; NOTE: These settings should be added by the network setup > ; These bindings are of the windows 2000 type, and will > probably need > to be > -- Volejte za 0,- Kč po celé ČR se službou VOLNÝ TelefoNet. Více informací na http://telefonet.volny.cz

1 0

RE: [ros-dev] Role of UI coordinator and committing graphical imp rovements
by Murphy, Ged (Bolton) 27 Oct '05

27 Oct '05

> > Wow, Dominic's design is just amazing. Is that a real local copy or a > > mockup? I'm all for it, the icons and all are great! > > The icons are from Vista, so that's a no go. But some other bits we can use. > There is a discussion here with a nice screenshot : > http://www.reactos.org/forum/viewtopic.php?t=985 It looks better still with an address bar in explorer : http://reactosde.re.funpic.de/media/mediadown/2005_302962_reactgui.jpg ************************************************************************ 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-dev] RE: [ros-svn] [turner] 18776: Calculate the screens ize correctly . Allow a file name input.
by Murphy, Ged (Bolton) 27 Oct '05

27 Oct '05

> -----Original Message----- > From: Casper Hornstrup [mailto:ch@csh-consult.dk] > Sent: 26 October 2005 18:36 > To: 'ReactOS Development List' > Subject: RE: [ros-dev] RE: [ros-svn] [turner] 18776: > Calculate the screensize correctly . Allow a file name input. > > > -----Original Message----- > > From: ros-dev-bounces(a)reactos.org > [mailto:ros-dev-bounces@reactos.org] On Behalf Of Eric Kohl > > Sent: 26. oktober 2005 19:06 > > To: ReactOS Development List > > Subject: Re: [ros-dev] RE: [ros-svn] [turner] 18776: > Calculate the screensize correctly . Allow a > > file name input. > > > > Murphy, Ged (Bolton) wrote: > > > > > Does anyone have any objections to this? > > > > > > If not, I will start to move the following into rosapps tonight: > > > binpatch > > > driver > > > dumprecbin > > > infinst > > > nts2w32err > > > objdir > > > partinfo > > > patchnv4 > > > pice > > > pnpdump > > > sc > > > sdkparse > > > stats > > > theme > > > tickcount > > > > Most of these utils were/are used to develop ReactOS. They > should stay > > where they are because they are used by developers. > > > > > > Eric > > [CSH] Please speak up whoever use them and don't want to > checkout rosapps > in order to use them. > > Casper No one seems to be speaking up. Perhaps these tools were in for historical purposes, but are now redundant. They aren't currently included in the build, so it wouldn't generate anymore work having them in rosapps and dropping the needed ones into /reactos/modules as opposed to editing /apps/directory.xml 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-dev] RE: [ros-svn] [turner] 18776: Calculate the screen size correctly . Allow a file name input.
by Murphy, Ged (Bolton) 27 Oct '05

27 Oct '05

> -----Original Message----- > From: WaxDragon [mailto:waxdragon@gmail.com] > Sent: 26 October 2005 17:55 > To: ReactOS Development List > Subject: Re: [ros-dev] RE: [ros-svn] [turner] 18776: > Calculate the screen size correctly . Allow a file name input. > My XP install has sc (what ours does, who knows), otherwise moving > them is fine by me. Be sure to update > reactos/bootdata/packages/reactos.dff please. Our current sc.exe does pretty much nothing. I've started a full rewrite of it which I'll drop into /subsys/system when ready ************************************************************************ 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] [gvg] 18782: Change Tcpip and Afd drivers from auto-start to system-start, since we don't
by Gge 27 Oct '05

27 Oct '05

gvg(a)svn.reactos.com wrote: > Change Tcpip and Afd drivers from auto-start to system-start, since we don't > auto-start device drivers yet > > > > Updated files: > trunk/reactos/bootdata/hivesys.inf > Networking works again for me (Mirc) Regards Gge

1 0

The 'did you forget your password?' link...
by Richard Campbell 27 Oct '05

27 Oct '05

The 'Did you forget your password?' link on the ROS website does not work.

1 0

Function stubs
by crashfourit 26 Oct '05

26 Oct '05

Does React OS have function Stubs for unimplemented Windows NT 4.0 API? Does React OS log an attempted call to an unimplemented API, tell the user where to find it in the source tree? I believe this would help speed up the development process of ROS.

2 1

Vote - 'Chocolate in ReactOS official cheesecake?'
by administrator＠reactos.org 26 Oct '05

26 Oct '05

Hello ros-dev audience A new vote was started by Royce3 on the forum. The topic is 'Chocolate in ReactOS official cheesecake?'. The vote will last one week. You can get directly to the vote with this link: http://www.reactos.org/forum/viewtopic.php?p=9106 This is an auto generated message. -- Thanks, The ReactOS Team

1 0

RE: [ros-dev] RE: [ros-svn] [turner] 18776: Calculate the screen size correctly . Allow a file name input.
by Murphy, Ged (Bolton) 26 Oct '05

26 Oct '05

> -----Original Message----- > From: Brandon Turner [mailto:turnerb7@msu.edu] > Sent: 26 October 2005 14:34 > To: ReactOS Development List > Subject: Re: [ros-dev] RE: [ros-svn] [turner] 18776: > Calculate the screen size correctly . Allow a file name input. > > > Yes, i would also like to move any app that is in windows to > reactos\apps or reactos\susbsys\system\ and leave all the unix / test > apps in rosapps. > > Brandon > > Murphy, Ged (Bolton) wrote: > > >I've had a fix for this for a while, but because it's been > in rosapps, I'd > >forgotten about it. > > > >I agree with Alex's earlier comment. This is essentially a > core app and > >should at least be moved into /reactos/apps, if not > /reactos/subsys/system. > > > >Maybe we should also consider moving some apps which are in > /reactos/apps > >over to /rosapps too, as there are some odd ones in there > which are not core > >apps, even a unix tool or two :-o Does anyone have any objections to this? If not, I will start to move the following into rosapps tonight: binpatch cat driver dumprecbin infinst nts2w32err objdir partinfo patchnv4 pice pnpdump sc sdkparse stats theme tickcount Should we bring in a selection of apps which are considered core to windows: comp find mode more sort What do we think about Solitaire and WineMine? Should they be left in rosapps for release builds only? They are certainly core to my Windows experience though :) ************************************************************************ 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

6 7

Development Coordinator Description
by Casper Hornstrup 26 Oct '05

26 Oct '05

Here is what I've been able to come up with so far. Comments? Casper More efficient development The development coordinator should work on identifying inefficiencies within the project and should work on providing solutions for the identified inefficiencies. The analysis should be done from a project-wide perspective. What may seem to be more efficient for a few project members, may cause even more inefficiency amongst several other project members and thus result in overall lower productivity within the project. The development coordinator should consider this when drafting proposals for more efficient development practices. The development coordinator should work on improving both the processes and the tools which are used in the development. Spread the knowledge Being a volunteer effort, the project members come and go, perhaps more often than in your average commercial development project. This makes it even more important to the success of the project, that knowledge is preserved within the project in the event that a project member is leaving the project. The development coordinator should work on improving the processes for spreading knowledge within the project. Education The experience of the project members is important to an open source development project like ReactOS, just like it is to commercial development projects. The development coordinator should work on improving the processes for educating the project members.

1 0

Kernel Crash when runnign task manager more than twice
by Saravanan Jayakumar 26 Oct '05

26 Oct '05

Hi All, I am getting the attached kernel crash on Vmware 5.5 beta when i launch task manager the third time.The attached doc shows the blue screen details of the crash. ragards Jay

2 2

RE: RE: [ros-dev] mingw32-make erros in rbuild
by Murphy, Ged (Bolton) 26 Oct '05

26 Oct '05

> -----Original Message----- > From: tobitosso [mailto:patriciak784-ros@yahoo.de] > Sent: 26 October 2005 15:24 > To: ReactOS Development List > Subject: RE: RE: [ros-dev] mingw32-make erros in rbuild > > > > --- Ge van Geldorp <gvg(a)reactos.org> wrote: > > That's the problem probably. When you use MSYS, > > "make" will use its shell > > program to execute subcommands. The shell doesn't > > understand backslashes. > > Remove MSYS and CygWin from your path and try again. > > > > Gé van Geldorp. > The backlslash problem can be easily solved by editing > the Makefile. Line 230: SEP = \$(ROS_EMPTY); > replace it with SEP = /$(ROS_EMPTY). MinGW, MSYS and > perhaps even Windows itself understand using / instead > of \. That's not a solution, it's a nasty hack! > Then the build process works until using > Makfile.auto is used. I think replacing / with \ in > Makefile.auto in MinGW on Windows is coded in the > rbuild sources. > This is senseless as I wrote above. You couldn't be further from the truth. It actually makes a great deal of sense. > Please remove these lines because then, I will be able > to build the other parts of ReactOS, too. If you don't > want to change the files in SVN-Repository first, > please send the changed sources to me per e-mail. The rbuild code is fine, it's your environment which is wrong. Listen to what Ge is telling you! ************************************************************************ 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] [turner] 18776: Calculate the screen size correctly . Allow a file name input.
by Murphy, Ged (Bolton) 26 Oct '05

26 Oct '05

I've had a fix for this for a while, but because it's been in rosapps, I'd forgotten about it. I agree with Alex's earlier comment. This is essentially a core app and should at least be moved into /reactos/apps, if not /reactos/subsys/system. Maybe we should also consider moving some apps which are in /reactos/apps over to /rosapps too, as there are some odd ones in there which are not core apps, even a unix tool or two :-o -----Original Message----- From: turner(a)svn.reactos.com [mailto:turner@svn.reactos.com] Sent: 26 October 2005 13:47 To: ros-svn(a)reactos.com Subject: [ros-svn] [turner] 18776: Calculate the screen size correctly. Allow a file name input. Calculate the screen size correctly. Allow a file name input. Updated files: trunk/rosapps/cmdutils/more/more.c _______________________________________________ Ros-svn mailing list Ros-svn(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-svn ************************************************************************ 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

Vote on voting method
by Freworld 26 Oct '05

26 Oct '05

Hi! I think we've discussed enough to start the vote on the new voting method. The two options to vote are: 1. Future votings will be held on the forum. As always only the commiters can vote but everyone can read the voting forum. The forum will send a mail to ros-dev everytime a thread (a vote) is created in the voting forum, so the people that don't track the forums will get informed too. Every other rule that concerns voting will stay the same. 2. Keep the old voting system. As always only commiters are allowed to vote. The vote will last 5 days. Greetings Michael

16 22

ROS 0.2.8 RC-2 available
by Robert Köpferl 25 Oct '05

25 Oct '05

A new version of ReactOS has arrived on SourceForge.Net Release Candidate 2 of version 0.2.8 has been finished last night and upped. As usual you're welcome to download and test. At this space some personal note: This is the first publish the new Releasemanager Brandon Turner did. For an unknown time, he'll do all future releases, since I go on some longer jorney. I'll not disappear from ROS but at least for some time. But I'm coming back within a year or so.

2 1

RC-2
by Murphy, Ged (Bolton) 25 Oct '05

25 Oct '05

When is this planned? I thought it was Monday ************************************************************************ 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 4

rbuild question
by Hartmut Birr 24 Oct '05

24 Oct '05

Hi, for a sample program, I have to specify a linker script file. I'm using the following xml-file: <module name="lowalign" type="win32cui" installbase="bin" installname="lowalign.exe"> <include base="lowalign">.</include> <define name="__USE_W32API" /> <file>lowalign.c</file> <linkerflag>-Wl,-T,modules/myapps/lowalign/ldscript</linkerflag> <linkerflag>-Wl,--file-alignment=0x80</linkerflag> <linkerflag>-Wl,--section-alignment=0x80</linkerflag> </module> I would like it if I can remove the absolute path from the linker script file. Any ideas? - Hartmut

5 13

Idea for the textual setup of ReactOS
by Jonathon Keogh 24 Oct '05

24 Oct '05

This is just an idea - there's no need to go crazy and bombard me with reasons why not. Just a thought, wouldn't it be better to ask for all the data (in the textual part of the setup for ReactOS) to be asked and then do all the proccessing? At the moment, it goes like so: * .... * Ask questions about drives * Apply drive stuff * Ask question about location of ReactOS * Apply ReactOS location (and copy files) * Ask question about booting * Apply booting stuff * Reboot PC Wouldn't it be better to do: * .... * Ask questions about drives * Ask question about location of ReactOS * Ask question about booting * Apply drive stuff * Apply ReactOS location (and copy files) * Apply booting stuff * Reboot PC This is just an idea, remember. Jonny

11 22

Constitution
by Casper Hornstrup 24 Oct '05

24 Oct '05

I have looked at the successful Debian project for inspiration on how to make decisions in a large distributed project like ReactOS. I have drafted a constitution for the ReactOS project which is similar to the Debian project constitution. You may find it here: http://www.reactos.org/wiki/index.php/Constitution. The constitution explains the decision making entities, their abilities and the decision making processes of the ReactOS project. Feel free to comment, suggest changes, etc. Casper

7 15

RE: [ros-svn] [ekohl] 18723: - Implement ScmrChangeServiceConfigW stub.
by Ge van Geldorp 24 Oct '05

24 Oct '05

> From: ekohl(a)svn.reactos.com > > - Implement ScmrChangeServiceConfigW stub. > - CreateServiceW calls ScmrCreateServiceW. This breaks the build: lib\advapi32\service\scm.c: In function `ChangeServiceConfigW': lib\advapi32\service\scm.c:149: warning: implicit declaration of function `ScmrChangeServiceConfigW' I've disabled the code in r18735. Gé van Geldorp.

1 0

Re: [ros-svn] [ekohl] 18723: - Implement ScmrChangeServiceConfigW stub.
by James Tabor 24 Oct '05

24 Oct '05

Hi! ekohl(a)svn.reactos.com wrote: > - Implement ScmrChangeServiceConfigW stub. > - CreateServiceW calls ScmrCreateServiceW. > > > Added files: > trunk/reactos/subsys/system/services/config.c > > Updated files: > trunk/reactos/lib/advapi32/service/scm.c > trunk/reactos/subsys/system/services/rpcserver.c > trunk/reactos/subsys/system/services/services.h > trunk/reactos/subsys/system/services/services.xml > make[1]: Entering directory `/home/ros/rosbackup' [CC] lib/advapi32/service/scm.c lib/advapi32/service/scm.c: In function `ChangeServiceConfigW': lib/advapi32/service/scm.c:149: warning: implicit declaration of function `ScmrChangeServiceConfigW' make[1]: *** [obj-i386/lib/advapi32/service/scm.o] Error 1 make[1]: Leaving directory `/home/ros/rosbackup' make: *** [depends] Error 2 This after a make clean && svn up && make depends. Thanks, James

1 0

DOS/GRUB based FreeLDR floppy image available.
by Bernd Blaauw 23 Oct '05

23 Oct '05

Using LOADLIN with FreeLDR didn't work to load ReactOS from DOS, so I remembered the GRUB4DOS program. Please download but don't distribute in any way the following file (this is just a demo, I don't feel like listing sites for sourcefiles) http://odin.fdos.org/odin2005/freeldr.img bootsequence: 1) bootfloppy 2) FreeDOS bootsector (see kernel ; GPL ) 3) FreeDOS kernel (kernel 2035A, www.freedos.org ; GPL ) 4) FreeDOS command.com (FreeCOM, see www.fdos.org/kernel ; GPL ) 5) Batchfile (autoexec.bat, see below ; just a script, public domain thus) 6) GRUB (compresses nicely with UPX ; GPL) 7) FreeLDR (compresses nice with zip, but not bootable then. Can't be compressed by UPX unfortunately) Same configuration can be done on harddisk, I think (fat32 also???), which means you can now boot FreeLDR from harddisk even without a FreeLDR realmode install program or associated bootsector. configuration might be even more lightweight if I omitted FreeCOM (command.com) and used "SHELL=A:\GRUB.EXE --config-file="kernel (fd0)/freeldr.sys" instead. Some small misc. bugs on ReactOS: FreeLDR: Title part has issues when it's too long, overwrites Brian Palmer's name, and at right side it's cut-off CMD: why does "EXIT /?" (give helpscreen for EXIT command) close the cmd-window? @echo off cdd a:\ echo. echo Welcome to FreeDOS (http://www.freedos.org) echo Booting FreeLDR 2.0.0 through GRUB4DOS. Press CTRL-C to abort or pause grub --config-file="kernel (fd0)/freeldr.sys

1 0

The ROS Wiki Mentions you need volunteers...
by TwoTailedFox 23 Oct '05

23 Oct '05

I was looking at the Wiki's "New Homepage Content", and it mentioned you needed volunteers, to scan the mailing lists, etc, for a useful end-of-week Newsletter. Well, I'd like to volunteer. I use Gmail to subscribe to The ROS and VLC lists, and it presents Emails as Conversations, minimising search time for specific parts of an email. That, and I religiously digest what I can, both on ROS, ROS-Dev, and the ROS-Dev SVN Commits. I'd like to do something to help contribute to ReactOS, and a Weekly Newsletter sounds quite appealing. I've done the odd article for a few IRL ones, so this is hopefully taking the next logical step. I've got a good grasp of English (Or so I'd like to think, but I swear the typo demon is about to leap out of my keyboard, and remove an "e" when I least expect it...), and good English is an excellent way to tell a user, "Wow, these guys aren't just another amateur batch of programmers!" So.. yeah, consider me Vounteered. -Stuart Robbins -- "I had a handle on life, but then it broke"

5 8

0.2.8 RC2 planned realse on Monday.
by Brandon Turner 23 Oct '05

23 Oct '05

As you might know this is the last release Robert will be able to do for a while(long term). So I will be trying to fill his spot while he is gone. Monday works out for us to be the best time where we can work together and he can show me everything that goes into packaging the release. Because of this we are going to do RC2 on this day. I need the experience and to learn from him other wise I will go into doing it blind. I know there is a lot of talk about deciding when to release and such. And no vote was taken on this, but we are stuck between a rock and a hard spot. Please understand why this decision was made. Feel free to express your views on this, and if there is over whelming opposition we can probably work something out. Brandon

4 3

Boot Up Error with Dhcp.exe
by James Tabor 23 Oct '05

23 Oct '05

Hi all! WARNING: WSHGetSockaddrType at drivers/net/wshtcpip/wshtcpip.c:103 is UNIMPLEME NTED! Unhandled exception ExceptionCode: c0000005 Faulting Address: 0 Address: 7c92659d C:\ReactOS\system32\ntdll.dll CS:EIP 1b:7c92659d DS 23 ES 23 FS 3b GS 0 EAX: 00000000 EBX: 00000022 ECX: ffffffff EDX: 7ffe0304 EBP: 0066fe18 ESI: 00841c98 ESP: 0066fdc8 EDI: 00000000 EFLAGS: 00010246 Frames: 400000+1bbf C:\ReactOS\system32\dhcp.exe 400000+2282 C:\ReactOS\system32\dhcp.exe 400000+2a95 C:\ReactOS\system32\dhcp.exe 400000+11e7 C:\ReactOS\system32\dhcp.exe 400000+1258 C:\ReactOS\system32\dhcp.exe 7c800000+31285 C:\ReactOS\system32\KERNEL32.dll Thanks, James

2 3

Re: [ros-svn] [royce] 18675: add raddr2line back to build
by James Tabor 22 Oct '05

22 Oct '05

royce(a)svn.reactos.com wrote: > add raddr2line back to build > > > Added files: > trunk/reactos/tools/raddr2line.mak > > Updated files: > trunk/reactos/tools/tools.mak > YEAH!!!! Thanks! James

1 0

compile problem
by Hartmut Birr 22 Oct '05

22 Oct '05

Hi, since some days (weeks?), I get a nice error message during compilation, if I add the '-ftracer' switch: gcc -c hal\halx86\mp\mpconfig.c -o .\up\obj-i386\hal\halx86\mp\mpconfig.o -Ihal\halx86\include -Intoskrnl\include -D_DISABLE_TIDENTS -DCONFIG_SMP -D_NTHAL_ -D__USE_W32API -Iinclude -Iinclude\reactos -Iinclude\libs -Iinclude\drivers -Iinclude\subsys -Iw32api\include -Iw32api\include\ddk -D_M_IX86 -DDBG -Wall -ftracer -Wpointer-arith -g -pipe -Werror -D_SEH_NO_NATIVE_NLG hal\halx86\mp\mpconfig.c: In function `HaliScanForMPConfigTable': hal\halx86\mp\mpconfig.c:552: internal compiler error: in cfg_layout_merge_blocks, at cfgrtl.c:2631 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.mingw.org/bugs.shtml> for instructions. _make: *** [.\up\obj-i386\hal\halx86\mp\mpconfig.o] Error 1 I can fix the problem a) if I remove one of the case statements after line #514 in mpconfig.c or b) if I remove the return statement at line #542 in mpconfig.c. I'm using gcc 3.4.2 for windows. Does someone see the same bug? - Hartmut

1 0

Ws2_32.dll test binary
by Alex Ionescu 22 Oct '05

22 Oct '05

Hi, A lot of people have requested to see try out the new ws2_32.dll binary. It's not complete yet, and I know the following applications don't work: - Possibly all cygwin apps that use fork() and sockets - tracert, and other XP applications which use getnameinfo(). IE6, Filezilla, Thunderbird, Firefox, MIRC, MSN, Outlook Express all work for me, but I'd be interested in other big applications that have trouble. Instructions: 1) Unzip zip file contents to the directory of the program you wish to test 2) Create a blank file in that directory, named program.exe.local, where program is the name of your app. Example: iexplore.exe.local Please make sure that you are using Microsoft Windows XP or higher for your tests. I'd be happy to receive any news of application crashes or incompatibilities. I'm most interested in games. Best regards, Alex Ionescu PS. This is a debug build. It prints out a lot of debug messages if you have a debugger attached and is also built without any optimizations. As such, network throughput might be slower. This is normal.

3 2

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