Testing 0.4 Trunk nightlies

Here you can discuss ReactOS related topics.

Moderator: Moderator Team

Post Reply
nathan
Posts: 1
Joined: Sat Oct 22, 2005 1:06 pm

Testing 0.4 Trunk nightlies

Post by nathan » Thu Aug 10, 2006 12:48 am

I've one big issue with the latest trunk nighlies.

I got blue screens on boot in ndis. I discovered ndis is the network driver so I tried running qemu with -net none. That worked perfectly for me.
Than I looked in the svn browers
http://svn.reactos.org/svn/reactos/trun ... ndis/ndis/
Some logic:

Fact 1: The most recent change is from a few days ago.
Fact 2: Earlier changes are from some months ago.
Fact 3: Erros appear in the last days
Conclusion: Revert that last revision and networking should work again in qemu with latest trunk.
Maybe it is not that simple, but can a developer look into this problem?

Thanks.
BTW: Great work on the login/logoff suport, it seems to be nice already!!!!
Other developers: I've noticed other nice things on the latest trunk. Seems that ReactOS 0.4 is becoming a huge milepile.

Coviti
Posts: 300
Joined: Wed Mar 01, 2006 4:26 am

Post by Coviti » Thu Aug 10, 2006 2:39 am

nathan wrote:Conclusion: Revert that last revision and networking should work again in qemu with latest trunk.
I think it would be a better idea to repair the problem, rather than reverting the fix to another problem, which caused your difficulties.

Also, the IRC channel might be a better place to suggest things such as this. The developers tend to avoid the forums for certain reasons, but you can usually catch them in the project's IRC channel.

EmuandCo
Developer
Posts: 4333
Joined: Sun Nov 28, 2004 7:52 pm
Location: Germany, Bavaria, Steinfeld
Contact:

Post by EmuandCo » Thu Aug 10, 2006 10:14 am

Thats why its the trunk. In trunk you can have the problem of half comitet work and incomplete stuff. Thats why there are release Versions from time to time. Btw reverting a patch is not the best solution as Coviti said already. Fixing the Patch is more intelligent than falling back to old code.

Ps. Guess why Devs dont come in here very often ;-)

nute
Posts: 251
Joined: Tue Aug 29, 2006 1:30 am

ReactOS 0.3.1

Post by nute » Wed Jan 10, 2007 1:39 am

Okay, there is a delay getting the next alpha release out.

Should there be if the modules are laid out correctly?

How is Reactos being programmed anyways? And while we are
on the subject, why would the developers avoid the forums?

A thought, can reactos be programmed to bring it to a stable
state before it is feature complete? Why do people have to get
the blue screen of death at all sometimes? I realize in alpha
stage that there are a lot of bugs and that you want to find
out about them.

If ReactOS isn't laid out well, how is it going to be better than Windows?
Will more than financial participation and pointng out bugs ever be
possible for American coders?

Z98
Release Engineer
Posts: 3379
Joined: Tue May 02, 2006 8:16 pm
Contact:

Post by Z98 » Wed Jan 10, 2007 2:34 am

1. What modules?

2. ROS is being coded by developers in their free time using the C language. C is one of the more difficult languages to master especially when it comes to pointers and memory management. Winter is also a slow period for them, as Greatlord has already stated.

3. Some developers avoid the forum simply because at times users have been very impolite. Here's an example: http://www.reactos.org/forum/viewtopic. ... 6&start=15

4. The "stable" releases are the point releases, such as 0.3.1, which is being delayed because they're trying to make it more stable even though it's missing parts. If a feature is expected but isn't implemented, that by itself can cause instability. So until all or at least most features are implemented, ROS cannot be viewed as stable. As you yourself said, this is alpha. Blue screens should be expected. Anyone using ROS would be using it to find these bugs.

5. If you don't think ROS is well laid out, then outline where you think it's bad. An operating system is a very complicated piece of work. Some things must be done the way they are to be NT compatible. However, I really don't see what you're getting at with that statement.

6. This is an open source project. What people do with their free time is up to them. Some of the people pointing out bugs aren't even programmers. Others aren't advanced enough to participate fully in the OS development beyond submitting patches and the like. Just be glad they either do donate money or submit bug reports and patches. ROS can use all the help it can get.

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests