ekohl(a)svn.reactos.com wrote:
>Fix indentation, remove trailing whitespace and sort prototypes.
>
>
>
>
Hi Eric,
Thanks a lot, this takes off one of the things which I was planning to
do once everything is finalized!
Best regards,
Alex Ionescu
Currently, the "Initial Owner" of bug reports is set based on the component
selected in the bug report. Most of the components still have Vizzini as the
initial owner. Since he left the project, that doesn't make much sense
anymore.
I'd like to change all initial owners to "ros-bugs(a)reactos.com", a new
mailing list. Subscribers to that list would then get notifications of new
bug submissions. This type of setup seems to work for a lot of open source
projects.
If there are no objections I'll create the list and switch Bugzilla on
Thursday.
Gé van Geldorp.
jakov(a)vmlinux.org wrote:
>
>
> Why not release every other month... it's not nonsensical.
> It's agile.
>
> If no big changes: 0.2.6.1
>
> If big bugfixes: 0.2.7
>
> If important features: 0.3
>
I think this is a very good idea.
Who am I? Well I guess I'm what you could call a typical reactos 'user' in that I occaisionally download the latest releases to see how things are progressing.
Personally, I know that there is progress being made but only because I follow this list, but I'm sure there are plenty of others who don't and just check the site for a new release every now and then (or subscribe to the freshmeat release notices etc).
Now, I agree with other comments that if a new release (either 0.3 or 0.2.7) comes out and there are no immediately visible improvements to the user then it could cause trust issues. And on the other hand if there aren't any releases for a while then it looks from the outside like the project is stagnating.
Which is why I think the above idea is a good one - if I've downloaded 0.2.6 in the past and a 0.2.6.1 comes out 2 months later, then I know not to expect too many noticable changes, but it indicates to me that there is at least progress behind the scenes. And when the 0.2.7 comes out I should expect some new features around but nothing breathtakingly new. And when 0.3 came out I'd be hitting the download ASAP to see what major new developments are now afoot. So I think with the regular interval releases, but making sure they are marked to indicate what sort of release they are, means everyone knows where they stand.
Cheers
Derek
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
When I hover over the start menu item "Administration" ROS crashes and
goes to the "You can switch of the computer now" screen. The debugger
isn't started.
How to get more information here?
I'm using current SVN in qemu 0.7.0.
Greetings,
Jan Schiefer!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCu+pUzC00UKXFdVcRAlh/AJ9Ps7yJIvjjV1/oDkN2HkI/Q38zcQCcC3nQ
J80ijeO5Yinqs2TaUlt2Zmc=
=qFD6
-----END PGP SIGNATURE-----
On 6/24/05, art yerkes <ayerkes(a)perpetual.com> wrote:
> If the structure appears in the DDK headers, you should consider it to
> be in use by drivers, even if it's accompanied by a note saying that
> the structure is internal and will change. Driver writers tend to
> ignore such warnings.
You have a point, but I checked their DDK and it's not described there
(it's an alias for PVOID in their DDK). Its members appear only in our
DDK.
I've been snooping a little through their ndis.sys and it seems that
their structure has some extra members, like pointers to lists of used
packets and stuff like that. I guess it's safe then to add a few
variables to help in the implementation.
I also saw another interesting thing: the MS ndis.sys doesn't have all
the functions listed in the DDK. A few of them are declared as exports
but not implemented.
Best regards,
Andrei Homescu
Hello!
I've been studying the sources for ndis.sys for a while and I started
writing some functions, until now simple ones (wrappers for kernel
calls). I would like to implement NdisAllocatePacketPoolEx and
NdisPacketPoolUsage, but I don't think I can without modifying
NDIS_PACKET_POOL in w32api/include/ddk/ndis.h. Is that data structure
internal to ndis.sys or is publicly documented (and thus I can't touch
it)? I would like to add a couple of new members to count the overflow
packets and the used packets.
I've also been reading "Undocumented Windows NT" and I have a few
questions regarding some legal issues. Are the function declarations
for documented functions copied&pasted from the DDK? The undocumented
function declarations are obtained by disassembly of Windows sources?
Doesn't snooping around kernel code violate any copyright law?
Best regards,
Andrei Homescu
Jan Schiefer wrote:
> When I hover over the start menu item "Administration" ROS
> crashes and goes to the "You can switch of the computer now"
> screen. The debugger isn't started.
>
> How to get more information here?
>
> I'm using current SVN in qemu 0.7.0.
>
You really need to be using ROS in DBG mode to gather more information.
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
Craig Talbert wrote:
> On 6/22/05, Murphy, Ged (Bolton) <MurphyG(a)cmpbatteries.co.uk> wrote:
>
> > We need regular releases to keep public interest. New releases
> > generate interest outside of the community, which can only
> be a good
> > thing, even if they don't contain radical new features.
>
> I would be very careful about mixing concern for generating
> more interest in to a release policy that might give a false
> impression of the progress being made on the project.
>
> It does give me a warm fuzzy feeling to see the version
> number go up on reactos.com -- on (almost) any f/oss project
> for that matter. But I if I discovered the progress being
> made was misrperesented, I might lose trust in the people
> working on the project. Trust is important, and if we can
> gain the trust of end users, that's something we'll have that
> microsoft never really earned. :)
This is a good point. However we're only talking about a minor release.
Minor releases generally only consist of bug fixes and small improvements /
functionality.
0.2.6 was a particularly bad release, and at the moment, (not counting the
header rewrites currently taking place) HEAD is much more stable and usable.
0.3 is meant to be the big bang release where users are blown away, not
minor releases. To take Alex's earlier comparison, the Linux kernel often
jumps minor releases (2.6.*) with no obvious improvements. You generally
have to read the changelog to see what has changed (and if it's worth you
upgrading)
Again, my point is; if we're not going to do anymore 0.2.* releases, then we
could be in for a long wait before networking is at a stage which meets the
0.3 criteria.
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
I was wondering if you all would be interested in doing something like a
portal system. I know that a content management system is important, and
that will be a feature also, but I think a portal system for users,
developers, and administrators can become quite a useful feature. I think
another factor in getting ReactOS into mainstream computer useage would be a
single-sign-on service much like microsoft's passport service or apple's
.mac service, which may or may not be sso based I am not really sure. There
should also me an MSDN like library for programmers that are currently
unaware of programming protocol. There should also me a software
compatibility library.
Just a few suggestions
1 - Utilize a portal system
2 - Supply users and developers with a application/driver
compatibility library
3 - Supply users, and developers with an online application for
programming help/collaboration.
4 - Utilize a content management system over the portal system
to allow the portal be updateable.
Those are a few of my suggestions.
On another note I think ReactOS should not wait to do a "networking" release
and should provide 0.2.7 or 0.2.6.1 etc. The networking support is an
important feature but stability is a major factor in releasing software. If
networking is unstable the version should be 0.2.6.1 for each major bugzilla
fix. Even if that means 0.2.6.99999.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
cdrom.sys ( current SVN ) freezes the system when starting the installer
and when booting the live cd. No bluescreen is displayed.
Is there a way to aquire debug information in such a case ( from
installer or when booting the live cd ).
Greetings,
Jan Schiefer!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCt9rrzC00UKXFdVcRApo3AJwMJmYjf+Fiu23eeAQR7M707Q1KeACgk5TV
yvUHCavl4WtzMEs4Mhrufeo=
=SfSY
-----END PGP SIGNATURE-----
KMODE_EXCEPTION_NOT_HANDLED
STOP: 0x0000001E (0xc0000005, 0x9d805fe5, 0x00000000, 0x9e9e0000)
win32k.sys - Address 0x9d805fe5 base at 0x9d7fb000, DateStamp 0x0
Page fault Exception: 14(2)
I had this Blue Screen of Dead when i tried to resize Task Manager window.
Hi,
Following the most recent changes the build fails at present with the
following
ntoskrnl\io\disk.c:1614: error: conflicting types for 'IoReadPartitionTable'
w32api/include/ddk/win2k.h:67: error: previous declaration of
'IoReadPartitionTable' was here
ntoskrnl\io\disk.c:1614: error: conflicting types for 'IoReadPartitionTable'
w32api/include/ddk/win2k.h:67: error: previous declaration of
'IoReadPartitionTable' was here
ntoskrnl\io\disk.c:1641: error: conflicting types for
'IoWritePartitionTable'
w32api/include/ddk/win2k.h:86: error: previous declaration of
'IoWritePartitionTable' was here
ntoskrnl\io\disk.c:1641: error: conflicting types for
'IoWritePartitionTable'
w32api/include/ddk/win2k.h:86: error: previous declaration of
'IoWritePartitionTable' was here
regards
Mike Lerwill
Robert k. wrote:
>
>
> Hi,
> let's put it this way: I have no problem in doing an
> intermediate release. NEither idealistic nor by work. For my
> unterstanding, releases are time driven, not feature driven.
> So you're currently not feeling good for having a release
> build? I asked for a release one month ago, but I have to
> admit, not inbetween, anymore. So if not more people are
> worrying, I think we should have a try ???
>
>
> WaxDragon said:
> > I've been asking for a intermediate release for a month now, and
> > frankly now is not a good time. HEAD is going to need a
> while (again)
> > after all of these header changes. After we got rbuild stabilized
> > would have been a good time, but several of the developers
> are stuck
> > in this "No more 0.2.x releases" mentality.
> >
> > We are not going to get to 0.3.0 anytime soon unless someone other
> > than arty works on networking (or we change the requirements for
> > 0.3.0).
> >
> > WD
We need regular releases to keep public interest. New releases generate
interest outside of the community, which can only be a good thing, even if
they don't contain radical new features.
I agree with WD about networking. Arty is busy with the new job, and nobody
else is working on networking. Considering networking is meant to be the key
feature for the 0.3 release, then either people need to start working on
networking or the 0.3 goalposts need to be changed.
I would be more than happy to help with networking in any way I can, however
I'm not yet up to a standard to get my hands dirty with the core
infrastructure. With a mentor, and a little guidance, maybe myself and a few
others might be of more use in this area. (this is where I'm aiming)
Regards,
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Casper Hornstrup wrote:
> > -----Original Message-----
> > From: ros-dev-bounces(a)reactos.com
> [mailto:ros-dev-bounces@reactos.com]
> > On Behalf Of Murphy, Ged
> > (Bolton)
> > Sent: 23. juni 2005 13:08
> > To: 'ReactOS Development List'
> > Subject: RE: [ros-dev] New Release - how're you feeling?
> >
> >
> > AFAIK, the new design consists of a front page only so far.
> > We need a whole new Content Management System to control the entire
site.
>
> We have MediaWiki.
>
> Casper
Yeah, but MediaWiki isn't really a core website. More an information
gathering environment.
I'm thinking along the lines of full, browsable website, with core sections
like:
About, Features, Screenshots, news, Licence, Download links, Documentation,
Forums, View cvs, Wiki, FAQ/Howto, Bugzilla, Mailing lists, Status,
Resources.
Something along the lines of www.gentoo.org, or www.winehq.com
Yes, we could write our own design from scratch, or we could use pre-built
CMS like some of the below, which I listed last year sometime in the mailing
list:
<snip>
WebGUI - http://www.plainblack.com/webgui
Appears to be very popular and was recommended by quite a few people.
Performance is very good as are the features it offers
Quick overview available here
http://www.cmsmatrix.org/matrix?wid=2&func=viewDetail&listingId=1001
Mambo - http://mamboserver.com/
Recommended by many people to me, and has glowing reports from all the
sites
I visited. Certainly my favourite.
Quick overview available here
http://www.cmsmatrix.org/matrix?wid=2&func=viewDetail&listingId=1074
Confluence - http://www.atlassian.com/software/confluence/
This was recommended to me by a friend. I am going only off his
recommendation.
I've looked at other websites that use it and it appears to be good,
although I don't have any performance statistics.
OpenCMS - http://www.opencms.org/opencms/en/
This was also recommended, but I wasn't overly impressed by it.
OpenSourceCMS - http://www.opensourcecms.com/
Overviews and statistics of many CMS' can be found here -
http://www.cmsmatrix.org/
</snip>
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
navaraf(a)svn.reactos.com wrote:
>
> Don't include windows.h in drivers.
>
>
> Updated files:
> trunk/reactos/drivers/dd/blue/blue.c
> trunk/reactos/drivers/dd/mpu401/mpu401.h
> trunk/reactos/drivers/dd/mpu401/portio.c
> trunk/reactos/drivers/dd/mpu401/settings.c
> trunk/reactos/drivers/lib/bzip2/bzlib.h
Filip makes 3rd in CIA today, so far ... 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
Ge van Geldorp wrote:
> > From: Murphy, Ged (Bolton)
> >
> > I agree with WD about networking. Arty is busy with the new
> > job, and nobody else is working on networking. Considering
> > networking is meant to be the key feature for the 0.3
> > release, then either people need to start working on
> > networking or the 0.3 goalposts need to be changed.
>
> I don't see why the 0.3 goalposts would need to be changed.
> As long as we're not comfortable saying "basic TCP/IP
> networking is implemented now" we just call the release 0.2.x
> instead of 0.3.
>
> Gé van Geldorp.
>
My understanding of the goal for 0.3 is; basic networking with support for
common NIC's and Modems plus a GUI to configure it. If nobody is working on
networking, then (possibly exaggerated) it could be a year before it is
implemented.
What I was getting at is, if this is the case, does more focus need to be
put into networking, or would it be better to change the milestone for 0.3
(maybe stating networking as partly implemented, as it is now)
If everyone is happy to continue incrementing 0.2.x then I don't really see
a problem, but to quote WaxDragon "several of the developers are stuck in
this "No more 0.2.x releases" mentality.", which could mean we're stuck at
0.2.6 for another 6-12 months.
Ged.
(p.s. apologies for the bloat attached to the bottom of my mails)
************************************************************************
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
Freeworld wrote:
> Hi!
>
> I'm just waiting for the new design (mf?) to start changing
> the homepage. Nothing else is holding us back. I've also
> quite a lot of time, so I could start working on it.
>
> Greetings
> Michael
> (Website Coordinator)
AFAIK, the new design consists of a front page only so far. We need a whole
new Content Management System to control the entire site.
I know this was talked about a while back, as I remember doing quite a bit
of research and suggesting some very good, open source management systems we
could easily adopt. (I can find my original email with the list if need be)
What's the score on this now?
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
Since I am not deep in developement and thus have no feeling about the
curent state, I ask you:
How about the next Release build to put on sf.net?
Is the new build system running well, already?
Do we have the features for a 0.3?
Will we want to do another intermediate?
Why not release every other month... it's not nonsensical.
It's agile.
If no big changes: 0.2.6.1
If big bugfixes: 0.2.7
If important features: 0.3
And so on.
Hi all,
this is just a little note for those nice guys that are working hard in
cleaning the headers.
LPC proper and related names are divided in three groups:
- PORT_xxx or xxx_PORT (API/struct/macro for LPC port object handling;
end user API);
- LPC_xxx (API/struct/macro used in other executive subsystems or drivers);
- LPCP_xxx (executive mode only private LPC facility memory object names).
(I do not guarantee it is 100% correct; some subsets may overlap).
--
:Emanuele Aliberti
Hello,
I am just subscribed, I do not know if I will contribute or not, need to browse the code and the website for longer to see. Now the question:
Where is if any documentation to the ReactOS booting process in maximum details?
The area of my interest is to try to create Win32 console environement build from ReactOS. That is no windows, no graphics. Only the command line, much like linux or freebsd after the boot.
My experience with ReactOS has never been any good. I guess few years ago when I first heared of ReactOS, I tried to set it up, and got no luck. I keep trying every six month, and few days ago I downloaded the .iso and - oops, no luck again, it now complains about "cabinet not found", dude, this is an installation CD! So I guess I have to go down to source and keep the stuff under control. And the first thing I want to know is the boot process in details.
If anyone here is afraid of anonyms my name is Yakov Sudeikin I live in Siberia. I like the idea of ReactOS and I just unsubscribed from other developer's mailing lists ([dev-freepascal] and [dev-shareware] got me bored finally) and it looks I cannot simply live without being a part of [dev-something].
Yash
Hi.
Due to work on the power at the Danish Internet eXchange (DIX) from 2300 - 2400 GMT+1 (in ~45 minutes) there may be short
disturbances in the traffic to svn.reactos.com during that period.
Sorry for the inconvenience,
Casper
> Hi Martin,
> Thanks for this info. It looks like this might work. How do I contact
> Eric Kohl?
>
> Thanks,
> James
This is his email address: Eric Kohl <eric.kohl(a)t-online.de>
Perhaps you should also send a note to the ReactOS Development List.
Regards,
Martin
> On Tue, 2005-06-21 at 17:57 +0200, Martin Fuchs wrote:
> > Hi James,
> >
> > > Last night Martin Fuchs suggested that we look into using ReactOS's
> > > registry format in order to be compatible with Windows registry
> > > databases. I have the latest release of ReactOS running on QEMU on my
> > > box, so I checked it out. Basically, they're using the same regedit
> > > program from Wine, missing find command and all (Which I too feel is a
> > > pain in the neck).
> >
> > A bunch of dlls and applications are synced between Wine and ROS from
> > time to time, also including regedit. What about implemting the
> > missing find functionality at your own to bring both projects a little
> > foreward? ;-)
> >
> >
> > > I looked at the config stuff, and I found what looked
> > > like some binary database files for each of the main registry sections.
> > > Unfortunately, there's no documentation at all on any of this on their
> > > website.
> >
> > I can forward you a mail from Steven Edwards to bring a bit light into
> > this issue:
> >
> > S> I think ReactOS's registry is binary compatible with NT4. It and
> > the windows 2000 format was
> > S> documented/reversed for samba and the linux ntchpwd bootdisk
> > projects. If I remeber right Eric
> > S> Kohl offered to release some of his work to Wine for the binary
> > format so you might want to ping
> > S> him about the implementation details.
> >
> > So Eric Kohl would be the right man to ask about the internals of NT's
> > registry format.
> >
> > > If we decide to go this route, we may be in for a hell of a lot
> > > of work. But, I do agree with all of your points. I think the current
> > > system could use some improvement, especially in the area of searching.
> > > Let me know what you think of all this.
> >
> >
> > Regards,
> >
> > Martin
hyperion(a)svn.reactos.com wrote:
>fixes for Visual C++:
>
>
You should _really_ merge most of these (the non-hack ones) into trunk
ASAP. If not, what has a large risk of happening is that:
1) Too many changes happen in your branch which are purely related to
MSVC compilation and not to UMODE, bugs happen and we don't know why anymore
2) If you take large breaks from the branch, changes rot away and
eventually never get included.
So please, I urge you to commit most of these fixes into trunk and check
that they remain GCC compatible... for your own good too. These kinds of
branches can be a pain.
Best regards,
Alex Ionescu
ion(a)svn.reactos.com wrote:
> Syssetup has fallen to the dark side
ion(a)svn.reactos.com wrote:
> jingle bells batman smells, robin laid an egg (build rosrtl with NDK)
Thanks, very informative, definitely improves the credibility of the
project...
Thomas