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.
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?
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
>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é
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
> -----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
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"
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?
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
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