- Ros-dev - ReactOS.org

by Murphy, Ged (Bolton)

Alex Ionescu wrote: > thereby jeopardizing this entire project, the developers, > and my own position and life? Life? As in life itself? I would prefer it if you didn't jeopardize life, if possible, as I've become quite attached to it over the years. 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

20 years, 3 months

1
0
0 0

Re: [ros-svn] [ion] 15712: Fix some debug messages (do I need to patch this to wine?)

by Sylvain Petreolle

> Updated files: > trunk/reactos/lib/setupapi/devinst.c > trunk/reactos/lib/setupapi/makefile One thing you need to do too : stop patching this makefile and remove it from svn :) Kind regards, Usurp (aka Sylvain Petreolle) humans are like computers, yesterday the BIOS was all - today its just a word

20 years, 3 months

1
0
0 0

Vmware 5.0 Linux Licenses

by Alex Ionescu

Developers, Please contact me if you wish to receive a legal copy of VMWare 5.0 for Linux. There are 7 spots remaining, first come first serve. Best regards, Alex Ionescu

20 years, 3 months

6
8
0 0

RE: [ros-dev] More RBuild issues...

by Steven Edwards

--- Casper Hornstrup <ch(a)csh-consult.dk> wrote: > > Coudn't they written to hd ? On reboot reporterror would ask if he may > > send it. > > Exactly. You can't trust the system to write to the disk on a BSOD. If the crash is bad enough to BSOD then it is bad enough to hose a fat16/32/ext2 fs. A crash that cannot be recovered from that results in a BSOD should ONLY BSOD. If you can figure out a way to fix /DEBUGPORT=FILE to flush its buffers and safely write to disk on BSOD I have a bounty for you. This is way doing a memory dump or minidump of a crash is inheritly risky which is why it should be off by default. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new Resources site http://smallbusiness.yahoo.com/resources/

20 years, 3 months

3
2
0 0

[Fwd: [ros-dev] Reactos directory created in Recatos local tree when building Ros = Unexpected]

by Gge

In these reactos\reactos\inf+media}system32 sub directories there is no file created during the ros build by make . Is it really needed ? Regards Gerard

20 years, 3 months

1
0
0 0

Fighting the Tide of Change. Usb Update!

by James Tabor

Hi all, After a big set back, 8^6, I've manage to get cromwell to compile with the new build system. I have started the Fdo, Pdo and Ioctl stuff. It's cool! I'll commit the stuff I have now and we can start working on it again. Thanks, James

20 years, 3 months

1
0
0 0

Crash with current svn

by Hartmut Birr

Hi, I'm not able to boot the current svn tree in qemu. It crashs in the very early boot phase: (hal\halx86\generic\acpi.c:443) Unable to locate RSDP (ntoskrnl\ke\main.c:292) --------------------------------------------------------------- (ntoskrnl\ke\main.c:293) ReactOS 0.3-SVN (Build 20050530-r15689) Used memory 131072Kb (ntoskrnl\mm\mminit.c:378) Kernel Stack Limits. InitTop = 0x800f4000, Init = 0x800f1000 (ntoskrnl\mm\mminit.c:106) NonPagedPool 80800000 - 86bfffff, PagedPool 87000000 - 8d3fffff ******* Dumping non paging pool stats ****** Tag ffffffff Blocks 1 Total Size 3200 Average Size 3200 TotalBlocks 1 TotalSize 3200 AverageSize 3200 Freeblocks 1 TotalFreeSize 816 AverageFreeSize 816 ***************** Dump Complete *************** (ntoskrnl\mm\mm.c:327) No current process red zone verification requested for block 0x8D3D38A8 ntoskrnl\mm\/rpoolmgr.h(708): double-free detected for paged pool address 0x8d3d38a8 Tag (0), Size -1515870811, UserSize 0 First few Stack Frames: <ntoskrnl.exe:48> <68> <ntoskrnl.exe:62cb4> Contents of Block: A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The bug code is undefined. Please use an existing code instead. Technical information: *** STOP: 0x00000000 (0x00000000,0x00000000,0x00000000,0x00000000) Frames: <ntoskrnl.exe:23f7> <ntoskrnl.exe:242f> <ntoskrnl.exe:61f14> <ntoskrnl.exe:61fd5> <ntoskrnl.exe:628fb> <ntoskrnl.exe:63240> <ntoskrnl.exe:61100> <ntoskrnl.exe:611b6> <ntoskrnl.exe:4646a> PnpRootQueryBusRelations <ntoskrnl.exe:4651e> <ntoskrnl.exe:4658f> <ntoskrnl.exe:46655> <ntoskrnl.exe:40f67> <ntoskrnl.exe:40edf> <ntoskrnl.exe:43448> <ntoskrnl.exe:44b41> <800B5953> <800B325D> <ntoskrnl.exe:6216> <800B16C6> <ntoskrnl.exe:104b> It does not crash on real hardware. An other question, how do I get back the nostrip-files for addr2line? - Hartmut

20 years, 3 months

3
2
0 0

Reactos directory created in Recatos local tree when building Ros = Unexpected

by Gge

I built Ros with svn 15689 after a checkout ( mingw32-make ) and I noticed that a Reactos Directory is created in the Reactos source directory . This is not needed. D:\Gerard\Reactos\Svn\reactos\reactos>dir Volume in drive D has no label. Volume Serial Number is C4F7-46D4 Directory of D:\Gerard\Reactos\Svn\reactos\reactos 30/05/2005 23:16 <DIR> . 30/05/2005 23:16 <DIR> .. 30/05/2005 23:16 <DIR> inf 30/05/2005 23:16 <DIR> media 30/05/2005 23:16 <DIR> system32 0 File(s) 0 bytes 5 Dir(s) 3 877 736 448 bytes free D:\Gerard\Reactos\Svn\reactos\reactos> Regards Gerard

20 years, 3 months

1
0
0 0

UI Coordinator Vote

by Jason Filby

Hi all We need to vote on the UI Coordinator Vote. This will take 2 weeks according to our voting rules and only committers may participate. If you're not listed as a committer but participate in the project in an important way (testing/web work) then talk to an existing committer to get a recommendation. For voting rules see: http://www.reactos.com/wiki/index.php/Voting Regards Jason

20 years, 3 months

3
3
0 0

ReactOS IRC Group Contact Information

by Alex Ionescu

Hi, Since not all the developers are on IRC and/or are aware of this, I wanted to make the following announcement so that future requests/flames can go to the right person (ie: me). I have registered ReactOS as an official group with Freenode, and we now have full, legitimate control over #reactos and all #reactos-**** channels (as well as ros-dev but there is (and has always been) a remote risk some new project called "ROS" might come and dispute that)) and enjoy all the benefits of an actual group registration. Since I am the group contact, that means that any requests that cannot be done by yourselves as operators (ie: major changes, like requesting a cloak) should be sent to me, and I'll take care of them ASAP. I'm also currently fixing the IRC Access Lists so they work properly (people would get operator status but not auto-voice, and other such silly things). I have already fixed up #ros-dev so that Level 10ers get +v, Level 20ers +o and Level 40ers have almost unlimited access. Similarly to before, all the devs have been set to have this access level (40). In the old system some people were 45, some were 46, some 47, etc, which kind of made everything seem awkard (ie: "why is developer foo 44 but developer bar 47? is bar more 'powerful'?). This resulted because instead of having a single person assign the access, everyone tried their best, but people can only give one access level lower then what they already are. So in the future, just send me a pm/email and I'll add the proper access for a new dev. But that won't be a problem since I'm 24/7 on IRC and I doubt I would not notice a new developer :). Tomorrow I'll be fixing up #reactos, which suffers from even bigger access level problems. Apart from making you aware of the fact that I'm here to help for any IRC-related business, I also wanted to say that I can now assign you user cloaks! This means that instead of being kjk_hyperion(a)some.random.italian.dsl.isp.it you can now be kjk_hyperion(a)developers.reactos. I will also be handing out @users.reactos or @testers.reactos for people who are not developers but have been helping us quite a lot (one notable example is WaxDragon, or tinus, etc). We can of course even have @webteam.reactos or @translators.reactos...etc. The main advantages of a cloak is that 1) people know you're with us, and what your position is 2) Your actual ISP/Hostname/IP is hidden from the public, so you don't need to worry about script kiddies 3) It's cool (imo) So here's what I'll be needing from you if you want to be cloaked: (CONTRIBUTORS ONLY FOR NOW, PLEASE!) 1) Your IRC Nickname and IRC Alternate Nickname (you *must* set one up...and your nickname *must* have been registered to a valid e-mail address) 2) Your choice of cloak... recommendations: (developer.reactos, translator.reactos, media (or designer? or ui?).reactos, board.reactos) PM me on IRC or send me an e-mail with the above information and you should have your cloak in less then a day. Best regards, Alex Ionescu

20 years, 3 months

1
0
0 0

Re: [ros-dev] XML-Build and rosapps

by Steven Edwards

Hi, --- Maarten Bosma <maarten.paul(a)bosma.de> wrote: > Maarten Bosma wrote: > > I just want to point out that thunk/posix, trunk/os2, trunk/vms and > > rosapps are still using the old build system. > > I forgot the bad thing, they can't use it if it's not there. Fixing rosapps is on my TODO list for the next week. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new Resources site http://smallbusiness.yahoo.com/resources/

20 years, 3 months

1
0
0 0

Re: [ros-svn] [gvg] 15685: Revert some incorrect changes that were made during rbuild merge

by Hartmut Birr

gvg(a)svn.reactos.com wrote: >Revert some incorrect changes that were made during rbuild merge > > > >Updated files: >trunk/reactos/tools/wrc/parser.y >trunk/reactos/tools/wrc/y.tab.c >trunk/reactos/tools/wrc/y.tab.h > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > Hi, after this commit, I get the following build error: [WRC] obj-i386\lib\cpl\appwiz\appwiz.coff lib\\cpl\\appwiz\\/Cz.rc:11:41: Error: parse error _make: *** [obj-i386\lib\cpl\appwiz\appwiz.coff] Error 1 - Hartmut

20 years, 3 months

2
1
0 0

All months again: New Release

by Robert Köpferl

Hi, we're stright aproaching a new release. Or at first: A branch. What about the version number? As far as I followed the discussions, 0.3 is still away :-( . And how about our new build system. Is it successfully running? I for my part would feel more comfortable if the next intermediate-release would still use the old build system.

20 years, 3 months

7
10
0 0

svn.reactos.com maintenance

by Casper Hornstrup

Hi. Within the next 3 hours, I'll be taking the svn.reactos.com box down for maintenance. I expect it to take less than 30 minutes. Casper

20 years, 3 months

1
0
0 0

Re: [ros-dev] RE: [greatlrd] 15646: Remove two file that are not need anylonger

by Sylvain Petreolle

`Remove two file that are not need any longer fix some compilings warings' <== --- Ge van Geldorp <gvg(a)reactos.com> a écrit: > > From: greatlrd(a)svn.reactos.com > > > > Updated files: > > trunk/reactos/lib/cabinet/cabextract.c > > trunk/reactos/lib/cabinet/cabinet_main.c > > What's the purpose of the changes you made to these two files? > > Gé van Geldorp. > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev > Kind regards, Usurp (aka Sylvain Petreolle) humans are like computers, yesterday the BIOS was all - today its just a word

20 years, 3 months

2
1
0 0

RE: [greatlrd] 15646: Remove two file that are not need anylonger

by Ge van Geldorp

> From: greatlrd(a)svn.reactos.com > > Updated files: > trunk/reactos/lib/cabinet/cabextract.c > trunk/reactos/lib/cabinet/cabinet_main.c What's the purpose of the changes you made to these two files? Gé van Geldorp.

20 years, 3 months

1
0
0 0

RBuild woes...

by Alex Ionescu

Hi, Here is my beef with rbuild. I can't fix most of these as I don't have the skills/knowledge of rbuild. 1) Project link flags are applied at the end of the command line...this makes -Wl optimization flags not work. 2) DBG = 0 and GCC 4 creates a load of new warnings that weren't there before. For example, I can't build ntoskrnl anymore. This is because it's detecting "uninitialized variables" which are actually being initalized by the macros themselves (see mm/pe.c and elf.inc.h). This did not happen before rbuild. 3) Strip isn't being executed for dbg = 0 anymore... I can add it but I have no idea how to make it dbg = 0 only. Not sure: 4) Is the OPTIMIZED envirovar still taken into account? I didn't seem to see so. Best regards, Alex Ionescu

20 years, 3 months

3
10
0 0

New build system ready for trunk

by Casper Hornstrup

Hi. I believe the new build system is ready to replace the current build system in trunk. Unless there are objections, I plan on merging the branch to trunk in the weekend of 27 - 29 of may. I'd like to take the opportunity to thank everyone that helped make this possible - especially Royce Mitchell III, Ge van Geldorp, and Steven Edwards. It would be nice if you could checkout the branch and check that the features you can't live without are still there so we can have them ready before the merge. If you have major new feature requests that are not essential, I'd like to put them on hold until after the merge. To checkout the branch do a: svn co svn://svn.reactos.com/branches/xmlbuildsystem/reactos For a list of environment variables that controls the build see: http://svn.reactos.com/viewcvs/*checkout*/branches/xmlbuildsystem/reactos/M… For more technical information see: http://svn.reactos.com/viewcvs/*checkout*/branches/xmlbuildsystem/reactos/t… This is not a 100% solution to our dependency problems though. There can still be corner-cases where it is needed to manually clean some files, but it will be needed a lot less than today. Also in order to have acceptable performance, we cannot check dependencies on every included file on each make invocation. Therefore, this is currently only checked each time the automatically generated makefile (makefile.auto) is regenerated. Makefile.auto is regenerated each time a build system file (*.xml) is modified. If you need to check the dependencies on files not specified in the build system files "automatic dependencies", then delete makefile.auto and run make again. Casper

20 years, 3 months

6
9
0 0

Re: [ros-svn] [navaraf] 15570: Use W32API.

by Alex Ionescu

navaraf(a)svn.reactos.com wrote: >Use W32API. > > >Updated files: >trunk/reactos/drivers/net/npf/Makefile >trunk/reactos/drivers/net/npf/dump.c >trunk/reactos/drivers/net/npf/jitter.c >trunk/reactos/drivers/net/npf/openclos.c >trunk/reactos/drivers/net/npf/packet.c >trunk/reactos/drivers/net/npf/packet.h >trunk/reactos/drivers/net/npf/read.c >trunk/reactos/drivers/net/npf/win_bpf.h >trunk/reactos/drivers/net/npf/write.c > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > > This breaks the dbg=0 build because of the ASSERT macro in winddk.h. Best regards, Alex Ionescu

20 years, 3 months

1
1
0 0

Re: [ros-svn] [navaraf] 15574: Bye, bye "include/net/" directory...

by Alex Ionescu

navaraf(a)svn.reactos.com wrote: >Bye, bye "include/net/" directory... > > >Deleted files: >trunk/reactos/include/net/ > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > > This breaks the build because lib/packet can't find the net include files anymore. Best regards, Alex Ionescu

20 years, 3 months

1
0
0 0

Re: [ros-svn] [greatlrd] 15482: VBE driver never write which reslutions it should use as defualt

by Gge

greatlrd(a)svn.reactos.com wrote: > VBE driver never write which reslutions it should use as defualt > therefor the change resultions did not working on bootcd > do not remove this settings. from the reg. > Thanks > > > > Updated files: > trunk/reactos/bootdata/hivesys.inf > This is already possible in the "hiveinst.file" It should be only in one place Regards Gge

20 years, 3 months

2
1
0 0

Re: [ros-dev] All months again: New Release

by Steven Edwards

--- Robert K�pferl <rob(a)koepferl.de> wrote: > we're stright aproaching a new release. > Or at first: A branch. > What about the version number? As far as I followed the discussions, 0.3 > is still away :-( . > > And how about our new build system. Is it successfully running? > I for my part would feel more comfortable if the next > intermediate-release would still use the old build system. I would rather wait till Casper merges rbuild and we get it stable then tag a release. There is no point in stablising the tree to just break it again in another week or two. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new Resources site http://smallbusiness.yahoo.com/resources/

20 years, 3 months

2
1
0 0

Re: [ros-dev] Build Error

by Filip Navara

20 years, 3 months

1
0
0 0

compile warning at kd/kdinit.c with gcc 3.3.1 on win32

by Theodor Willax

Hi, have problems to compile revison 15501. See below: D:\home\willaxt\Entwicklung\ROS\src\reactos>make crt: [DEPENDS] wine/.cppexcept.d crt: [DEPENDS] wine/.cpp.d crt: [CC] wine/cpp.c crt: [CC] wine/cppexcept.c crt: [AR] ../../dk/w32/lib/libcrt.a freeldr: Tools are up to date. freeldr: Tools are up to date. ===================================================== Assembling fat ===================================================== Assembling fat32 freeldr: Compiling mm/mm freeldr: Compiling freeldr freeldr: LINKING freeldr.sys freeldr: LINKING setupldr.sys freeldr: Make ALL done. ntoskrnl: [DEPENDS] ob/.object.d ntoskrnl: [CC] kd/kdinit.c kd/kdinit.c:24: warning: initialization from incompatible pointer type kd/kdinit.c:25: warning: initialization from incompatible pointer type kd/kdinit.c:26: warning: initialization from incompatible pointer type make[1]: *** [kd/kdinit.o] Error 1 make: *** [ntoskrnl] Error 2 D:\home\willaxt\Entwicklung\ROS\src\reactos>gcc -v Reading specs from D:/home/willaxt/Entwicklung/ROS/tool/MinGW/bin/../lib/gcc-lib /mingw32/3.3.1/specs Configured with: ../gcc/configure --with-gcc --with-gnu-ld --with-gnu-as --host= mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable -languages=c,c++,f77,objc,ada,java --disable-win32-registry --disable-shared --e nable-sjlj-exceptions --enable-libgcj --disable-java-awt --without-x --enable-ja va-gc=boehm --disable-libgcj-debug --enable-interpreter --enable-hash-synchroniz ation Thread model: win32 gcc version 3.3.1 (mingw special 20030804-1) Did a complete new check out before. Could this be a compiler problem. Am I using the right gcc version. Thanks for help, Theo ------------------------------------------- Dipl.-Inf. (FH) Theodor Willax, Moosburg http://www.willax-online.de ------------------------------------------- _________________________________________________________________ So einfach geht das. MSN Toolbar mit Pop-up-Blocker. http://toolbar.msn.de/ Jetzt kostenlos downloaden und gut ist!

20 years, 3 months

1
1
0 0

Static IP behavior with dhcp service

by Gge

Hi, Dynamic IP is not working actually for some unknown reason in my Ros real hardware as dhcp DISCSCOVERmessage sent to dhcp server (my router) by dhcp client has no reply ( noDHCPOFFER received in Ros) This configuration is working fine in window but it is broken in my box ( don't know why it is broken but this happened already once ) . As a alternative solution I setup Hivesys.inf for static IP and I got the same dialog problem between dhpcp client and dhcp server . => the dhpc client service should not sent a DHCPDISCOVER message to the dhcp server if the IP address is static in Hivesys.inf ( so different of "0.0.0.0") => The Ip address setup in Hivesys.ing must be taken into account in that case. I have created the Bug 639 for this issue The test has been done with svn 15447 Regards Gge

20 years, 3 months

2
3
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