- Ros-dev - ReactOS.org

by Lucio Diaz

Jason Filby wrote: Message: 5 Date: Sun, 16 Oct 2005 09:04:49 -0600 From: Jason Filby <jason.filby(a)gmail.com> Subject: Re: [ros-dev] Break To: ReactOS Development List <ros-dev(a)reactos.org> Message-ID: <e7a1591e0510160804q74f7424fy1e8a6b53ff39d4b0(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 That doesn't seem to tie in with people leaving if they're not told that they are right. Regards Jason On 10/15/05, Royce Mitchell III <royce3(a)ev1.net> wrote: > Would you be so kind as to at least commit your work-in-progress code to > a branch, please? > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------ Message: 6 Date: Sun, 16 Oct 2005 09:06:56 -0600 From: Jason Filby <jason.filby(a)gmail.com> Subject: Re: [ros-dev] Break To: ReactOS Development List <ros-dev(a)reactos.org> Message-ID: <e7a1591e0510160806jf1ddb50le7e3154168a23a(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 On 10/15/05, James Tabor <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net> wrote: > TC was voted for and I consider it closed business. Wax has the job deal > with it! Mostly on IRC! That's not the way we've agreed to do things. > I'm not against you. Just because some of us miss the Memo does not make them right! Well excuse me. > Before anyone complains, they should open their minds and read what Alex > has to say. Right, and Alex is a great listener. Jason ----------------------------------- I am not a developer, but i am an adult man, with some experience with team working and have been reading this mailing list since the begining, and what can i say? First: I have seen Alex Ionescu apologicing, often, so yes, drop IRONY, Alex is a great listener, and NO! it is not easy to find people who would apologice nowadays. Second: I saw the loss of focus in this proyect for a long time, with the largely delayed 0.3.0, and it have being people like Alex, Filip, Ge, Waxdragon, Tabor... who took the torch and carried the proyect for a full year. Third: I have seen Alex Ionescu as the one in the center of all discusions, and he could be fast to answer, but he proved to be as fast to apologice, and that i have not seen from some other developers. Four: It IS NORMAL, to have discussions where you are working in such a big proyect, not everyone can have the same vision of a whole OS, but what have NO sense, is to harass people for doing their work well, just cause there is not a F* paper about their "election". Fith: I thought this was an open source project, so people commit if they want, if they dont they dont, period. Harassing people wont grow the developer base. I have been following this proyect before 0.2 was released, i even submited some documentation and i wonder if i have been wasting my time. Sorry if i look a bit angry, but i AM a bit angry as i see several good developers force to leave for this kind of avoidable situations even if i can not (but wish) help with code. Good luck, Lucio Diaz-Flores Varela. ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

19 years, 11 months

3
2
0 0

Change of Project Coordinator

by Jason Filby

Hi all 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. Regards Jason PS - I've cc'd the developers on leave as to not exclude anyone

19 years, 11 months

4
5
0 0

OK, Time for a few words..

by TwoTailedFox

I've seen quite a few users propose ideas, such as a new GUI, or new functionality, only to be told it doesn't fit in with the Core Goal of ReactOS. ReactOS is all about creating a Win32-compatible Operating System. Now, later on, when the Kernel is sufficiently developed, we can do what Linux does, and create "Distributions". I had a look at the KDE/Ros Thread, and noted that a version of that, and GNOME may well be available for Windows next year. If the UI Team chooses to Grow, you can offer, for example mind you, a Core ReactOS System, with Windows Classic, and one or more "Distributions", with a different GUI, such as KDE or GNOME. Same goes for ReactOS in different 'roles'. Offering versions aimed at Workstations, Servers, or even for Educational/Testing use, would be feasible down the line. Just my 0.02c -- "I had a handle on life, but then it broke"

19 years, 11 months

1
0
0 0

New ReactOS Newsletter. Now Live on ReactOS.org

by TwoTailedFox

Hello All. Just sending out an announcement that Issue 1 of the new ReactOS Weekly Newsletter is now available for viewing on http://www.reactos.org Thanks to GvG for showing me the internals of RosCMS, Bac9 on #reactos for helping with validation checks, and dnordenberg, again on #reactos, for offering to help with the Newsletter in the form of an XML-Based back-end, to come soon. -- "I had a handle on life, but then it broke"

19 years, 11 months

1
0
0 0

Alex.

by Lucio Diaz

Alex Ionescu wrote: Hi, Since it seems Emanuele has not made a post about this yet, maybe I should... I have been informed that due to time and focus reasons, Emanuele has decided to leave the project for an indeterminate time (forever?). I wish him the best of luck, and I thank him for his contributions to ReactOS. I have also talked to Filip lately, and I have understood from him that he will also be gone for the next month or two. Finally, in light of recent events, I feel that it's also best if I follow the example and take a break as well. I was undecided before, but the recent fight over the TC has convinced me that maybe this isn't the best place or time for me to apply my knowledge. I'm bit sick of being always the one in the middle of a fight. First I was blamed for always breaking the tree or causing incompatibilities, and now I'm blamed for project decisions as well. I really have too many things to worry about in life then to spend my life fighting all the time. I don't care that there are 40 people on IRC that agree with me, but when Jason and Ge, which are the two most influencial members of this project seem to be set against me, then I don't want to cause any more trouble. Best regards, Alex Ionescu ------------------------------------------ After being reading this mailing list for over a year i can really understand Alex, Period. Lucio Diaz-Flores Varela. ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

19 years, 11 months

1
0
0 0

Break

by Alex Ionescu

Hi, Since it seems Emanuele has not made a post about this yet, maybe I should... I have been informed that due to time and focus reasons, Emanuele has decided to leave the project for an indeterminate time (forever?). I wish him the best of luck, and I thank him for his contributions to ReactOS. I have also talked to Filip lately, and I have understood from him that he will also be gone for the next month or two. Finally, in light of recent events, I feel that it's also best if I follow the example and take a break as well. I was undecided before, but the recent fight over the TC has convinced me that maybe this isn't the best place or time for me to apply my knowledge. I'm bit sick of being always the one in the middle of a fight. First I was blamed for always breaking the tree or causing incompatibilities, and now I'm blamed for project decisions as well. I really have too many things to worry about in life then to spend my life fighting all the time. I don't care that there are 40 people on IRC that agree with me, but when Jason and Ge, which are the two most influencial members of this project seem to be set against me, then I don't want to cause any more trouble. Best regards, Alex Ionescu

19 years, 11 months

8
14
0 0

Ros boot failure - r 18469

by Gge

Hi, Ros installs successfuly from BootCD ( r 18469) but then at start Ros bugchecks . Any idea ? (ntoskrnl\ldr\loader.c:876) Loading Module \SystemRoot\system32\drivers\npfs.sys... (ntoskrnl\ldr\loader.c:879) Module \SystemRoot\system32\drivers\npfs.sys loaded at 0x9d120000. (ntoskrnl\ke\i386\exp.c:1306) Unhandled UserMode exception, terminating thread KeBugCheckEx at ntoskrnl\ex\init.c:716 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. Technical information: *** STOP: 0x00000071 (0x00000001,0x00000000,0x00000000,0x00000000) Frames: <ntoskrnl.exe:2615 (ntoskrnl/ke/bug.c:479 (KeBugCheckEx))> <ntoskrnl.exe:bea8a (ntoskrnl/ex/init.c:716 (ExpInitializeExecutive))> <ntoskrnl.exe:6806 (ntoskrnl/ke/main.c:100 (KiSystemStartup))> <ntoskrnl.exe:bc854 (ntoskrnl/ke/main.c:294 (_main))> <ntoskrnl.exe:104b ({standard input}:47 (_text_start__))> 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 (0x80000003,0x800a2d47,0x00000000,0x1f000000) *** ntoskrnl.exe - Address 0x800a2d47 base at 0x80000000, DateStamp 0x0 Regards Gge

19 years, 11 months

1
0
0 0

Installing ReactOS 0.2.8 on vmware 5.5 beta

by Saravanan Jayakumar

Hi, Can anyone please let me know how to run React 0.2.8 RC1 on VMware 5.5 Beta.When i run it on vmware its asking to install certain vmwarre tools, i guess its the graphics driver.Then vmware complains that the driver is not found for this OS and i dont see anything on the screen. regards Jay

19 years, 11 months

5
7
0 0

Gudie Lines for SVN Write access

by Magnus Olsen

Hi I should love to see some new gudieles how to get svn access. Today it seam anyone that provide with a patch that is coder can getting svn access. But I think we need start think how we should handle it, Here is some ideas how it can be 1. A maling list with patch or in Bugzila I love see a maling list with the patch 2. When people have submit the patch to us we start examing it see if it any godd (we are doning that already) 3. To get SVN write access u need lest provide patch in regual basic under 6 month lest, Then after 6 month the provider can write to mailing list see if can getting SVN write access before he grant SVN write access, the full name and mailing address must be provided, and we should have a vote if that provder can getting SVN write access. no accpect from all this rules. Yestday some was granted svn access his name was not on the mailing list why he got one, he did not write either on the mailing list asking for svn access that why I want see new guide lines how svn write access handles. so every one know how he is and why he was granted to be granted after few patcher are not accpect in my eys. For we are starting getting alot with people with svn write access. And new guide lines must be create. BestReagds Magnus Olsen

19 years, 11 months

7
8
0 0

MM and CM architecture

by Saravanan Jayakumar

Hi, I am new to React-OS but following the project for quite sometime. I would like to know how the memory managemnet and cache manger works in React OS.Isit similar to NT?.If anyone can let me know the arcitecture of these two components in ReactOS, it would be helpful for me to follow the code.Youcould also give me a few pointers as of where to start of in the code for MM and CM so that i could dissect the flow. regards Jay

19 years, 11 months

2
1
0 0

Re: [ros-diffs] [gvg] 18468: Make sure we don't hang forever when activating a window belonging to

by Gunnar Dalsnes

gvg(a)svn.reactos.com wrote: > > - co_IntSendMessage(Window->hSelf, WM_WINDOWPOSCHANGING, 0, (LPARAM) WinPos); > > + co_IntPostOrSendMessage(Window->hSelf, WM_WINDOWPOSCHANGING, 0, (LPARAM) WinPos); > I think the whole co_IntPostOrSendMessage function is wrong and crazy. Who made it? Sending and posting messages are completely different things. I think something like co_IntSendMessageTimeout should be used instead, but i dont think its implemented yet. G.

19 years, 11 months

3
3
0 0

Via 8233 Sound Install

by James Tabor

Hi! From running Setup in the via8233 directory. http://www.qdigrp.com/qdisite/eng/support/d_downloadcd.htm http://www.qdigrp.com/qdisite/driver/utility/sound/Via8233.zip (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (lib/ntdll/ldr/utils.c:2072) Relocating (76160000 -> 6e0000) C:\ReactOS\system32 \comctl32.dll (lib/ntdll/ldr/utils.c:2072) Relocating (777d0000 -> 782000) C:\ReactOS\system32 \winmm.dll (lib/ntdll/ldr/utils.c:2072) Relocating (76260000 -> 7db000) C:\ReactOS\system32 \oleaut32.dll (lib/ntdll/ldr/utils.c:2072) Relocating (77a90000 -> 4b1000) C:\ReactOS\system32 \VERSION.dll (lib/comctl32/theming.c:138) Could not re-register class L"#32770": 57 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 -> 1240000) C:\DOCUME~1\ADMINI ~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP0.DIR\193e5.DLL (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'C:\DOCUME~ 1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP0.DIR\_ISUSER.DLL' (Status c00001 35) (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1263000) C:\DOCUME~1\ADMINI ~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_WUTL951.DLL (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! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! WARNING: ModifyMenuA at lib/user32/windows/menu.c:4327 is UNIMPLEMENTED! WARNING: ModifyMenuA at lib/user32/windows/menu.c:4327 is UNIMPLEMENTED! (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! (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 4c1000) C:\DOCUME~1\ADMINI~ 1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP0.DIR\v32audio.dll (lib/setupapi/devinst.c:1818) : flag DIGCF_PRESENT ignored Unhandled exception ExceptionCode: c0000005 Faulting Address: 0 Address: 7c9250bc C:\ReactOS\system32\ntdll.dll CS:EIP 1b:7c9250bc DS 23 ES 23 FS 3b GS 0 EAX: 005df4a0 EBX: 7ffdf000 ECX: 7668543c EDX: 00000000 EBP: 005df4a4 ESI: 00000000 ESP: 005df498 EDI: 00696120 EFLAGS: 00010202 Frames: 76660000+5ccc C:\ReactOS\System32\SETUPAPI.DLL 76660000+6ba9 C:\ReactOS\System32\SETUPAPI.DLL 76660000+55fc C:\ReactOS\System32\SETUPAPI.DLL 76660000+540c C:\ReactOS\System32\SETUPAPI.DLL 4c1000+1452 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP 0.DIR\v32audio.dll 400000+fff8 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+10b29 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+16912 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+16bff C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+10e60 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+113ad C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+76b77 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 7c800000+31255 C:\ReactOS\system32\KERNEL32.dll (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! The linux sound system does work. Thanks, James

19 years, 11 months

3
4
0 0

ReactOS build fallen over

by Wesley Parish

I started compiling ReactOS 0.2.7 on my Linux box uname -a Linux localhost 2.6.3-7mdk #1 Wed Mar 17 15:56:42 CET 2004 i686 Celeron (Coppermine) unknown GNU/Linux This was the result. I'm using i586-mingw32mscv-*. Now my question is, in which file do I find the elusive (PREFIX)? Because I can't find it in Makefile. [wparish@localhost reactos027]$ make [MKDIR] obj-i386/tools [MKDIR] obj-i386/tools/rbuild [MKDIR] obj-i386/tools/rbuild/backend [MKDIR] obj-i386/tools/rbuild/backend/mingw [CC] tools/rbuild/backend/mingw/mingw.cpp [CC] tools/rbuild/backend/mingw/modulehandler.cpp [CC] tools/rbuild/backend/mingw/proxymakefile.cpp [MKDIR] obj-i386/tools/rbuild/backend/devcpp [CC] tools/rbuild/backend/devcpp/devcpp.cpp [CC] tools/rbuild/backend/backend.cpp [CC] tools/rbuild/automaticdependency.cpp [CC] tools/rbuild/bootstrap.cpp [CC] tools/rbuild/cdfile.cpp [CC] tools/rbuild/compilerflag.cpp [CC] tools/rbuild/configuration.cpp [CC] tools/rbuild/define.cpp [CC] tools/rbuild/exception.cpp [CC] tools/rbuild/filesupportcode.cpp [CC] tools/rbuild/include.cpp [CC] tools/rbuild/installfile.cpp [CC] tools/rbuild/linkerflag.cpp [CC] tools/rbuild/module.cpp [CC] tools/rbuild/project.cpp [CC] tools/rbuild/ssprintf.cpp [CC] tools/rbuild/stubbedcomponent.cpp [CC] tools/rbuild/testsupportcode.cpp [CC] tools/rbuild/wineresource.cpp [CC] tools/rbuild/XML.cpp [CC] tools/rbuild/rbuild.cpp [MKDIR] output-i386/tools [MKDIR] output-i386/tools/rbuild [LD] output-i386/tools/rbuild/rbuild [MKDIR] obj-i386/tools/bin2res [CC] tools/bin2res/bin2res.c [CC] tools/bin2res/mkstemps.c [MKDIR] output-i386/tools/bin2res [LD] output-i386/tools/bin2res/bin2res [MKDIR] obj-i386/tools/buildno [CC] tools/buildno/buildno.cpp [CC] tools/buildno/exception.cpp [CC] tools/buildno/ssprintf.cpp [CC] tools/buildno/XML.cpp [MKDIR] output-i386/tools/buildno [LD] output-i386/tools/buildno/buildno [BUILDNO] include/reactos/buildno.h [MKDIR] obj-i386/tools/wmc [CC] tools/wmc/getopt.c [CC] tools/wmc/lang.c [CC] tools/wmc/mcl.c [CC] tools/wmc/utils.c [CC] tools/wmc/wmc.c [CC] tools/wmc/write.c [CC] tools/wmc/y_tab.c [CC] tools/wmc/misc.c [MKDIR] output-i386/tools/wmc [LD] output-i386/tools/wmc/wmc [WMC] include/reactos/bugcodes.h [WMC] include/reactos/errcodes.h [MKDIR] obj-i386/tools/nci [CC] tools/nci/ncitool.c [MKDIR] output-i386/tools/nci [LD] output-i386/tools/nci/nci [NCI] ntoskrnl/include/internal/napi.h [MKDIR] obj-i386/tools/gendib [CC] tools/gendib/gendib.c [MKDIR] output-i386/tools/gendib [LD] output-i386/tools/gendib/gendib [GENDIB] subsys/win32k/dib/dib16gen.c [RBUILD] makefile.auto Reading build files...done Detecting compiler...not detected Detecting netwide assembler...detected (nasm) Detecting compiler -pipe support...not detected Detecting compiler pre-compiled header support...not detected Processing modules...done Creating directories...done Unpacking WINE resources...done Generating test support code...done Generating proxy makefiles...done Checking automatic dependencies...done [DLLTOOL] obj-i386/lib/kernel32/libkernel32.a make: mingw32-dlltool: Command not found make: *** [obj-i386/lib/kernel32/libkernel32.a] Error 127 [wparish@localhost reactos027]$ -- 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.

19 years, 11 months

2
2
0 0

Re: [ros-diffs] [hbirr] 18481: Don't use alloca in a macro, which may be used in a loop. This does fix bug #805.

by Gunnar Dalsnes

This is not the right fix... I will revert these changes when i come up with a proper fix. I also dont understand how this can fix bug 805 (eternal loop in thread windows cleanup routine). Even with your changes the eternal loop is still there, it just doesnt run out of stack? G. hbirr(a)svn.reactos.com wrote: > Don't use alloca in a macro, which may be used in a loop. This does fix bug #805. >

19 years, 11 months

2
1
0 0

file copy during install

by Hartmut Birr

Hi, during install, I see the following two lines: (lib\setupapi\queue.c:1441) copy error 2 L"C:\\ReactOS\\inf\\ne2000.sys" -> L"C:\\ReactOS\\System32\\drivers\\ne2000.sys" (lib\setupapi\queue.c:1441) copy error 2 L"C:\\ReactOS\\inf\\pci.sys" -> L"C:\\ReactOS\\System32\\drivers\\pci.sys" Why does ROS try to copy drivers from the inf directory? - Hartmut

19 years, 11 months

2
1
0 0

0.2.8 Branch

by Brandon Turner

After switching too DBG = 0 i get the following error: [WRC] obj-i386\apps\utils\net\tcpsvcs\quotes.coff [WRC] obj-i386\apps\utils\net\tcpsvcs\tcpsvcs.coff [LD] output-i386\apps\utils\net\tcpsvcs\tcpsvcs.exe [RSYM] output-i386\apps\utils\net\tcpsvcs\tcpsvcs.exe [CC] apps\utils\net\telnet\src\ansiprsr.cpp [CC] apps\utils\net\telnet\src\keytrans.cpp C:/RosBE/bin/../lib/gcc/mingw32/3.4.4/../../../../include/c++/3.4.4/bits/stl_uni nitialized.h: In member function `void std::vector<_Tp, _Alloc>::reserve(size_t) [with _Tp = KeyMap, _Alloc = std::allocator<KeyMap>]': C:/RosBE/bin/../lib/gcc/mingw32/3.4.4/../../../../include/c++/3.4.4/bits/stl_uni nitialized.h:82: warning: '__cur' might be used uninitialized in this function mingw32-make: *** [obj-i386\apps\utils\net\telnet\src\keytrans.o] Error 1 Do i need to update anything? Brandon

19 years, 11 months

3
3
0 0

Winsock 2.2 Status

by Alex Ionescu

Hi, As many of you know, I've been working on Winsock for the last 3 weeks, then lost all my work. I have finished writing everything that I had lost and did some serious tests with MIRC. I want to update Ged, Waxdragon, Ge, Magnus and the others which were interested in a status report. MIRC uses some serious features, including asyncronous hostname lookups, which is an extremly complex part of ws2_32.dll. After fixing about 20 bugs (let me add a small note here: Microsoft has done some SERIOUSLY amazing work with MSVC 2005. The latest RC1 is now even faster, since the internal build system was updated and now supports multi-threaded compiles: ws2_32 takes me 2.5 seconds (officially timed) to compile AND link AND rc with full optimizations + pdb generated... not only did fast rebuild times help out during testing, but the integrated debugger just keeps getting better too. Finding those 20 bugs was extremly easy), I was able to connect to MIRC by using /server irc.freenode.net and join the channels, identify and talk normally. DCC transfer worked as well. Almost all of the ws2_32 APIs were being called, and both TCP and UDP (from dnsapi) communication seemed to work fine. In other words, mirc was fully usable with my ws2_32.dll My next test app is firefox. As of now, it loads fine but hangs at 100% cpu usage. I'm guessing it must be another small bug causing an inifite loop somewhere. Since it's 4AM now, I'll go sleep and check it out tomorrow. Best regards, Alex Ionescu

19 years, 11 months

2
1
0 0

Re: [ros-svn] [hbirr] 18481: Don't use alloca in a macro, which may be used in a loop. This does fix bug #805.

by Royce Mitchell III

hbirr(a)svn.reactos.com wrote: >Don't use alloca in a macro, which may be used in a loop. This does fix bug #805. > > > >Updated files: >trunk/reactos/subsys/win32k/include/object.h >trunk/reactos/subsys/win32k/ntuser/accelerator.c >trunk/reactos/subsys/win32k/ntuser/caret.c >trunk/reactos/subsys/win32k/ntuser/class.c >trunk/reactos/subsys/win32k/ntuser/focus.c >trunk/reactos/subsys/win32k/ntuser/message.c >trunk/reactos/subsys/win32k/ntuser/misc.c >trunk/reactos/subsys/win32k/ntuser/msgqueue.c >trunk/reactos/subsys/win32k/ntuser/painting.c >trunk/reactos/subsys/win32k/ntuser/scrollbar.c >trunk/reactos/subsys/win32k/ntuser/vis.c >trunk/reactos/subsys/win32k/ntuser/window.c >trunk/reactos/subsys/win32k/ntuser/winpos.c >trunk/reactos/subsys/win32k/objects/color.c > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.org >http://www.reactos.org/mailman/listinfo/ros-svn > >. > > > I think this fix should be applied to 0.2.8

19 years, 11 months

1
0
0 0

Re: [ros-svn] [greatlrd] 18471: Japanese translation by tsk email tsk_n@mail.goo.ne.jp

by Thomas Weidenmueller

greatlrd(a)svn.reactos.com wrote: > Added files: > trunk/reactos/lib/msi/msi_Ja.rc > trunk/reactos/lib/oleaut32/oleaut32_Ja.rc > trunk/reactos/lib/shdocvw/Ja.rc > > Updated files: > trunk/reactos/lib/comctl32/comctl_Ja.rc > trunk/reactos/lib/comdlg32/cdlg_Ja.rc > trunk/reactos/lib/mpr/mpr_Ja.rc > trunk/reactos/lib/msacm/msacm_Ja.rc > trunk/reactos/lib/msi/msi.rc > trunk/reactos/lib/oleaut32/oleaut32.rc > trunk/reactos/lib/oledlg/oledlg_Ja.rc > trunk/reactos/lib/setupapi/Ja.rc > trunk/reactos/lib/shdocvw/shdocvw.rc > trunk/reactos/lib/shell32/shell32_Ja.rc > trunk/reactos/lib/shlwapi/shlwapi_Ja.rc > trunk/reactos/lib/wininet/wininet_Ja.rc > trunk/reactos/lib/winmm/winmm_Ja.rc I hope you're also going to submit all these changes to winehq... - Thomas

19 years, 11 months

1
0
0 0

Reactos 0.2.8 RC-1 is out

by Robert Köpferl

You can find a new version on SF.NET Initial network support and some more complex apps as firefox respectively seamonkey seem to work. Against to what I wrote, there's no additional app included in this RC. I try to include some in the qemu variant for the next RC. And for the intermediate time I question you to download the RC1 and try it out, PLUS report bugs into our nice bugzilla!

19 years, 11 months

6
5
0 0

Re: [ros-svn] [greatlrd] 18464: Fixing directx headers from wine, by adding alot of missing struct and some struct was wrong. Complete the header dmemmgr.h it was missing and move stuff into that header.

by Alex Ionescu

greatlrd(a)svn.reactos.com wrote: >Fixing directx headers from wine, by adding alot of missing struct and some struct was wrong. Complete the header dmemmgr.h it was missing and move stuff into that header. > > >Added files: >trunk/reactos/w32api/include/ddk/dmemmgr.h > >Updated files: >trunk/reactos/w32api/include/ddk/ddrawi.h >trunk/reactos/w32api/include/ddk/ddrawint.h >trunk/reactos/w32api/include/ddk/dvp.h > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.org >http://www.reactos.org/mailman/listinfo/ros-svn > > > This breaks the build. Best regards, Alex Ionescu

19 years, 11 months

2
1
0 0

RE: [ros-dev] Winsock 2.2 Status

by Murphy, Ged (Bolton)

Fantastic news Alex! Can't wait to get hold of it and read through it, and put it through some tests. It's all about the networking with me ;) -----Original Message----- From: Alex Ionescu [mailto:ionucu@videotron.ca] Sent: 15 October 2005 09:06 To: ReactOS Development List Subject: [ros-dev] Winsock 2.2 Status Hi, As many of you know, I've been working on Winsock for the last 3 weeks, then lost all my work. I have finished writing everything that I had lost and did some serious tests with MIRC. I want to update Ged, Waxdragon, Ge, Magnus and the others which were interested in a status report. MIRC uses some serious features, including asyncronous hostname lookups, which is an extremly complex part of ws2_32.dll. After fixing about 20 bugs (let me add a small note here: Microsoft has done some SERIOUSLY amazing work with MSVC 2005. The latest RC1 is now even faster, since the internal build system was updated and now supports multi-threaded compiles: ws2_32 takes me 2.5 seconds (officially timed) to compile AND link AND rc with full optimizations + pdb generated... not only did fast rebuild times help out during testing, but the integrated debugger just keeps getting better too. Finding those 20 bugs was extremly easy), I was able to connect to MIRC by using /server irc.freenode.net and join the channels, identify and talk normally. DCC transfer worked as well. Almost all of the ws2_32 APIs were being called, and both TCP and UDP (from dnsapi) communication seemed to work fine. In other words, mirc was fully usable with my ws2_32.dll My next test app is firefox. As of now, it loads fine but hangs at 100% cpu usage. I'm guessing it must be another small bug causing an inifite loop somewhere. Since it's 4AM now, I'll go sleep and check it out tomorrow. Best regards, Alex Ionescu _______________________________________________ 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

19 years, 11 months

1
0
0 0

Re: [ros-svn] [hpoussin] 18453: Remove entries that are created by netcfgx.dll

by James Tabor

hpoussin(a)svn.reactos.com wrote: > Remove entries that are created by netcfgx.dll > > > Updated files: > trunk/reactos/bootdata/hivesys.inf > Hi! Will we need to add entries in hivesys for ROS Ne2K pci (2) driver? Currently the driver loads but ROS dhclient does not work. All my other dhclient systems, Win98-2 and XP work. Thanks, James Notes: I have two net cards installed. 1) VIA VT6102 Rhine II Fast Ethernet Controller rev. 116, Irq 11, IO 0xe800 [0xe8ff], mem 0xde001000 [0xde001fff], W2k driver not tested yet. 2) RealTek RTL-8029, IO 0xd000, Irq 11 Ne2K-pci, using ROS ne2000.sys. My hivesys.inf setup. This works very well. ; NIC drivers are like any other drivers - but no card-specific info here. ; Comment the networking stuff out if you don't have the card and don't want to see errors ; NE2000 NIC driver HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","ErrorControl",0x00010001,0x00000001 HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","Group",0x00000000,"NDIS" HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","ImagePath",0x00020000,"system32\drivers\ne2000.sys" HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","Start",0x00010001,0x00000003 HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","Type",0x00010001,0x00000001 HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","Route",0x00000000,"Ne20001" ; Configuration Entries for the NE2000 Adapter HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","Characteristics",0x00010001,0x00000000 HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","DriverDesc",0x00000000,"Ne2000" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","ProviderName",0x00000000,"Provider Name(from Inffile)" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","NetCfgInstanceId",0x00000000,"{RANDOMCFGGUIDFOR_NE20001}" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001\Linkage","Export",0x00000000,"\Device\Ne20001" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001\Linkage","RootDevice",0x00000000,"Ne20001" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001\Linkage","UpperBind",0x00000000,"Tcpip" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","Port",0x00000000,"D000" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","Irq",0x00000000,"B" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","NetworkAddress",0x00000000,"001122334455" HKLM,"SYSTEM\CurrentControlSet\Services\Ne20001\Parameters\Tcpip","DefaultGateway",0x00010000,"10.65.145.1" HKLM,"SYSTEM\CurrentControlSet\Services\Ne20001\Parameters\Tcpip","IPAddress",0x00010000,"10.65.145.79" HKLM,"SYSTEM\CurrentControlSet\Services\Ne20001\Parameters\Tcpip","SubnetMask",0x00010000,"255.255.255.0" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","BusType",0x00000000,"5" ;This is from the Registry from Windows 2000 HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","SlotNumber",0x00000000,"11" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","BusNumber",0x00000000,"0" ;And this i get from the BIOS bootscreen.

19 years, 11 months

2
1
0 0

FreeWin95

by Emanuele Aliberti

I just want to warn you are going to build FreeWin95 with WDM support. -- :Emanuele Aliberti

19 years, 11 months

20
53
0 0

RE: [ros-dev] A call for 0.2.8 (Pic of Mozilla)

by Murphy, Ged (Bolton)

On Fri, 14 Oct 2005 11:50, Richard Campbell wrote: > Murphy, Ged (Bolton) wrote: > >Richard Campbell wrote: > >>But how WELL does mozilla work with it? Well enough we could include it > >>with 0.2.8? > > > >No, it's still full of bugs. > >Mozilla won't be included anyway, it's a 3rd party app. > > > >Ged. > > Normally i'd take this hardline stance on 3rd party apps, but if we say, > ship firefox with ReactOS 0.3, we'd raise a lot of eyebrows. Suddenly > this puny operating system that crashes all the time and isn't > compatible with much of anything is running several complex, everyday apps. Actually, come to this of it, you make a fair point. I'm dead against having application code in the trunk, as I'm sure everyone else is. However shipping a few 'enhancements' with the prebuilt release builds can only help with much needed publicity. (assuming they meet licensing demands). They can always be dropped as we get closer to the 1.0 build (where I think user choice should take precedence via the package manager) WaxDragon mentioned including some of our apps like Solitaire with 0.2.8. Although everyone seemed to like the idea, we don't have a definitive answer yet. Are we going ahead with this one? 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

19 years, 11 months

7
6
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev