Hi, I prepared a distribution of ros 0.2.7 release. However, I have no good feeling.
Not very reproducable (at least I didn't get the rule, yet) it makes problems in qemu. -Sometimes the setup without format doesn't work (crash) -Then the creation of some hive didn't work -> freeldr can't boot -Install works, boot fails
At least I have an archive with qemu and working 0.2.7 Maybe that's all related. Possibly am I operating at some limit. Moving the mouse fills up the last bit of memory.
Actually, however, if this is the same on our customers pcs, I don't like the idea of delivering that...
Opinions
Robert Köpferl wrote:
Hi, I prepared a distribution of ros 0.2.7 release. However, I have no good feeling.
Not very reproducable (at least I didn't get the rule, yet) it makes problems in qemu. -Sometimes the setup without format doesn't work (crash)
This happens for a very long time...usually a crash in CcRos/vfat. We can't do much about it since nobody has looked at it/found a way to consistently reproduce it.
-Then the creation of some hive didn't work -> freeldr can't boot -Install works, boot fails
This can sometimes rarely happen too... I'm surprised you are reproducing it consistently though.
At least I have an archive with qemu and working 0.2.7 Maybe that's all related. Possibly am I operating at some limit. Moving the mouse fills up the last bit of memory.
How much memory did you dedicate to ROS?
Actually, however, if this is the same on our customers pcs, I don't like the idea of delivering that...
We are a pre-alpha OS, such things can happen. We'll never reach installion perfection. I've had trouble installing Windows XP on FOUR machines, in the same environment, but the machines were totally different. And the bug which stopped me from installing it is: 1) Known to microsoft 2) Happens since NT 5 Beta 3) Has about 20+ possible reasons and is almost impossible to debug.
All this to say that ReactOS will probably end up suffering from similar problems too. But I agree the issues you mentionned are important. Perhaps it will work better with the new Cc.
Best regards, Alex Ionescu
Opinions
Robert Köpferl wrote:
Hi, I prepared a distribution of ros 0.2.7 release. However, I have no good feeling.
These issues you have described are known, but intermittent. I have tested the 0.2.7 branch under vmware, qemu and real hardware, and the branch has performed consistantly under each platform. Considering the bugs we *did* catch for 0.2.7, I think it's a good release. The 0.2.7 branch has the TC 's blessing. Ship it.
WD
WaxDragon wrote:
These issues you have described are known, but intermittent. I have tested the 0.2.7 branch under vmware, qemu and real hardware, and the branch has performed consistantly under each platform. Considering the bugs we *did* catch for 0.2.7, I think it's a good release. The 0.2.7 branch has the TC 's blessing. Ship it.
Your word in echelon's ear. It'll be upped until tomorrow. The RC-releases will disappear as will 2.6
Hope this will be one of our better releases. (looking to 2.6)
WD
In an attempt to make this more of a full release then something we are blwoing off I have skimmed through the svn logs and pulled out all things i think should be in the change log. Here is a raw output of what changes i think should should be added: www.brandonturner.org/ROS/0.2.7.txt I dont know if i said this in my last email or not but I dont know what is important what isnt really so this could be way off. 3 big things that happened which arent stressed in the raw log, Filip changed everything(?) to USE_W32API, Filip and Alex mostly did all the ndk and other header fixes to make them windows compatible, Casper did rbuild. I dont know if the first two things will be added in generic or need to be added in all sections that they apply too(im guessing most?). Anyways, later today im going to go through the raw changes again and later tonight im going to add them to the wiki. Please tell me anything in there that should not be added to change log or anything i missed.
Thanks Brandon
Robert Köpferl wrote:
WaxDragon wrote:
These issues you have described are known, but intermittent. I have tested the 0.2.7 branch under vmware, qemu and real hardware, and the branch has performed consistantly under each platform. Considering the bugs we *did* catch for 0.2.7, I think it's a good release. The 0.2.7 branch has the TC 's blessing. Ship it.
Your word in echelon's ear. It'll be upped until tomorrow. The RC-releases will disappear as will 2.6
Hope this will be one of our better releases. (looking to 2.6)
WD
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Just now, I was on to extract the changelog off the wiki. While I came across your message, I thought, that this is exactly the right information I need. I can't say whehter you shal include this or that. At least it is usus to not provide every very detail, because the changelog on sf is rather for end-users to read (if). If you tell me to include your information in the wiki, I'll wait till tomorrow to include it. Seems like it is my part to delete potential unnecessary log entries. Or is anyone here who claims this decissions for her/himself ??
Brandon Turner wrote:
In an attempt to make this more of a full release then something we are blwoing off I have skimmed through the svn logs and pulled out all things i think should be in the change log. Here is a raw output of what changes i think should should be added: www.brandonturner.org/ROS/0.2.7.txt I dont know if i said this in my last email or not but I dont know what is important what isnt really so this could be way off. 3 big things that happened which arent stressed in the raw log, Filip changed everything(?) to USE_W32API, Filip and Alex mostly did all the ndk and other header fixes to make them windows compatible, Casper did rbuild. I dont know if the first two things will be added in generic or need to be added in all sections that they apply too(im guessing most?). Anyways, later today im going to go through the raw changes again and later tonight im going to add them to the wiki. Please tell me anything in there that should not be added to change log or anything i missed.
Thanks Brandon
Robert Köpferl wrote:
WaxDragon wrote:
These issues you have described are known, but intermittent. I have tested the 0.2.7 branch under vmware, qemu and real hardware, and the branch has performed consistantly under each platform. Considering the bugs we *did* catch for 0.2.7, I think it's a good release. The 0.2.7 branch has the TC 's blessing. Ship it.
Your word in echelon's ear. It'll be upped until tomorrow. The RC-releases will disappear as will 2.6
Hope this will be one of our better releases. (looking to 2.6)
WD
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Don't take anything off the wiki for about 2 more hours! It is unfinished and mess like you said. Filip looked over the changes and in general most are right so I'm adding them to wiki. I will be done in about 2 hours with new formatting and all changes. Please hold out if you can. I will also be making a less techincal version to explain things different in 0.2.7.
Thanks Brandon
Robert Köpferl wrote:
Just now, I was on to extract the changelog off the wiki. While I came across your message, I thought, that this is exactly the right information I need. I can't say whehter you shal include this or that. At least it is usus to not provide every very detail, because the changelog on sf is rather for end-users to read (if). If you tell me to include your information in the wiki, I'll wait till tomorrow to include it. Seems like it is my part to delete potential unnecessary log entries. Or is anyone here who claims this decissions for her/himself ??
Brandon Turner wrote:
In an attempt to make this more of a full release then something we are blwoing off I have skimmed through the svn logs and pulled out all things i think should be in the change log. Here is a raw output of what changes i think should should be added: www.brandonturner.org/ROS/0.2.7.txt I dont know if i said this in my last email or not but I dont know what is important what isnt really so this could be way off. 3 big things that happened which arent stressed in the raw log, Filip changed everything(?) to USE_W32API, Filip and Alex mostly did all the ndk and other header fixes to make them windows compatible, Casper did rbuild. I dont know if the first two things will be added in generic or need to be added in all sections that they apply too(im guessing most?). Anyways, later today im going to go through the raw changes again and later tonight im going to add them to the wiki. Please tell me anything in there that should not be added to change log or anything i missed.
Thanks Brandon
Robert Köpferl wrote:
WaxDragon wrote:
These issues you have described are known, but intermittent. I have tested the 0.2.7 branch under vmware, qemu and real hardware, and the branch has performed consistantly under each platform. Considering the bugs we *did* catch for 0.2.7, I think it's a good release. The 0.2.7 branch has the TC 's blessing. Ship it.
Your word in echelon's ear. It'll be upped until tomorrow. The RC-releases will disappear as will 2.6
Hope this will be one of our better releases. (looking to 2.6)
WD
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Brandon Turner wrote:
Don't take anything off the wiki for about 2 more hours! It is unfinished and mess like you said. Filip looked over the changes and in general most are right so I'm adding them to wiki. I will be done in about 2 hours with new formatting and all changes. Please hold out if you can. I will also be making a less techincal version to explain things different in 0.2.7. Thanks Brandon
Thanks, I'll wait for the less technical version to finish. Either put it in the wiki or send it directly to me or the list.
I'll add it in a vew hours.
Thank you for waiting. There is a non-technical changelog / overview at the top of that article. The change log is filled out pretty well and i think we have most important things in it.
http://www.reactos.com/wiki/index.php/ChangeLog-0.2.7
This the last step in the release? Tomorrow being the offical release date? Do we need GvG to update the homepage to reflect the new release?
Brandon
Robert Köpferl wrote:
Brandon Turner wrote:
Don't take anything off the wiki for about 2 more hours! It is unfinished and mess like you said. Filip looked over the changes and in general most are right so I'm adding them to wiki. I will be done in about 2 hours with new formatting and all changes. Please hold out if you can. I will also be making a less techincal version to explain things different in 0.2.7. Thanks Brandon
Thanks, I'll wait for the less technical version to finish. Either put it in the wiki or send it directly to me or the list.
I'll add it in a vew hours. _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Thank you a lot for doing this work. I extracted the text, put it in the Changelog textarea and signalled all listening recipents about our new release.
You seem to have some kind of numbering error in it. I didn't manage to get rid of it, thus i overtook it. I can change it within the next days.
Brandon Turner wrote:
Thank you for waiting. There is a non-technical changelog / overview at the top of that article. The change log is filled out pretty well and i think we have most important things in it.
http://www.reactos.com/wiki/index.php/ChangeLog-0.2.7
This the last step in the release? Tomorrow being the offical release date? Do we need GvG to update the homepage to reflect the new release?
Brandon
Robert Köpferl wrote:
Brandon Turner wrote:
Don't take anything off the wiki for about 2 more hours! It is unfinished and mess like you said. Filip looked over the changes and in general most are right so I'm adding them to wiki. I will be done in about 2 hours with new formatting and all changes. Please hold out if you can. I will also be making a less techincal version to explain things different in 0.2.7. Thanks Brandon
Thanks, I'll wait for the less technical version to finish. Either put it in the wiki or send it directly to me or the list.
I'll add it in a vew hours. _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Hi,
I just download the qemu image and noticed that it does not have Mozilla Control preinstalled, Network set up (I can't ping google.com or a ip in my network). Also a link to ibrowser on the destop would be nice. Since it is not announced officially there would be still time to fix it. I think that would be a greate improvement for the release.
Maarten Bosma
Robert Köpferl wrote:
Brandon Turner wrote:
Don't take anything off the wiki for about 2 more hours! It is unfinished and mess like you said. Filip looked over the changes and in general most are right so I'm adding them to wiki. I will be done in about 2 hours with new formatting and all changes. Please hold out if you can. I will also be making a less techincal version to explain things different in 0.2.7. Thanks Brandon
Thanks, I'll wait for the less technical version to finish. Either put it in the wiki or send it directly to me or the list.
I'll add it in a vew hours. _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
On 8/22/05, Maarten Bosma maarten.paul@bosma.de wrote:
Hi,
I just download the qemu image and noticed that it does not have Mozilla Control preinstalled, Network set up (I can't ping google.com or a ip in my network). Also a link to ibrowser on the destop would be nice. Since it is not announced officially there would be still time to fix it. I think that would be a greate improvement for the release.
Maarten Bosma
Both of those are networking releated, and 0.2.7 is NOT a networking release.
Hi,
filip2307 on IRC: ...there is a code to download the Mozilla Control if it's not present and the user is asked to allow it.
Okay, then it is not nessary to have it on the image. But I have not been asked when I started iBrowser maybe because network is not set up.
WaxDragon wrote:
Both of those are networking releated, and 0.2.7 is NOT a networking release.
But that does not mean that you can't activate network in qemu doesn't it ?
Maarten Bosma
WaxDragon wrote:
Both of those are networking releated, and 0.2.7 is NOT a networking release.
But that does not mean that you can't activate network in qemu doesn't it ?
Actually, during my testing, I checked that networking worked under both qemu 0.7.0 and vmware 5. I'm just saying that you shouldn't ask why 0.2.7 didn't have XXXX network feature..
On 8/22/05, Maarten Bosma maarten.paul@bosma.de wrote:
I did not. I just asked why networking is not activated in the qemu package.
I don't understand what you are saying. Networking (as much as it works) works under qemu-0.7.x right from the bootcd. What are you saying is broken?
Sorry i thought that it was some command line missing in the batch file and that is because network does not work. (ping)
WaxDragon worte:
On 8/22/05, Maarten Bosma maarten.paul@bosma.de wrote:
I did not. I just asked why networking is not activated in the qemu package.
I don't understand what you are saying. Networking (as much as it works) works under qemu-0.7.x right from the bootcd. What are you saying is broken?
On Mon, 22 Aug 2005 21:37:31 +0200 Maarten Bosma maarten.paul@bosma.de wrote:
Sorry i thought that it was some command line missing in the batch file and that is because network does not work. (ping)
WaxDragon worte:
On 8/22/05, Maarten Bosma maarten.paul@bosma.de wrote:
I did not. I just asked why networking is not activated in the qemu package.
I don't understand what you are saying. Networking (as much as it works) works under qemu-0.7.x right from the bootcd. What are you saying is broken?
Ping is not proxied by qemu -user-net. You'll have to test with some other tool.
-- Here's a simple experiment. Stand on a train track between two locomotives which are pushing on you with equal force in opposite directions. You will exhibit no net motion. None the less, you may soon begin to notice that something important is happening. -- Robert Stirniman
ros 027 is great!
On 8/23/05, art yerkes ayerkes@speakeasy.net wrote:
On Mon, 22 Aug 2005 21:37:31 +0200 Maarten Bosma maarten.paul@bosma.de wrote:
Sorry i thought that it was some command line missing in the batch file and that is because network does not work. (ping)
WaxDragon worte:
On 8/22/05, Maarten Bosma maarten.paul@bosma.de wrote:
I did not. I just asked why networking is not activated in the qemu package.
I don't understand what you are saying. Networking (as much as it works) works under qemu-0.7.x right from the bootcd. What are you saying is broken?
Ping is not proxied by qemu -user-net. You'll have to test with some other tool.
-- Here's a simple experiment. Stand on a train track between two locomotives which are pushing on you with equal force in opposite directions. You will exhibit no net motion. None the less, you may soon begin to notice that something important is happening. -- Robert Stirniman _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
On 22/08/05, Maarten Bosma maarten.paul@bosma.de wrote:
Hi,
I just download the qemu image and noticed that it does not have Mozilla Control preinstalled,
This is because there has too be the sources released for it too, which takes around 26MB EXTRA :)
Network set up (I can't ping google.com http://google.com or a ip in
my network). Also a link to ibrowser on the destop would be nice. Since it is not announced officially there would be still time to fix it. I think that would be a greate improvement for the release.
Maarten Bosma
Robert Köpferl wrote:
Brandon Turner wrote:
Don't take anything off the wiki for about 2 more hours! It is unfinished and mess like you said. Filip looked over the changes and in general most are right so I'm adding them to wiki. I will be done in about 2 hours with new formatting and all changes. Please hold out if you can. I will also be making a less techincal version to explain things different in 0.2.7. Thanks Brandon
Thanks, I'll wait for the less technical version to finish. Either put it in the wiki or send it directly to me or the list.
I'll add it in a vew hours. _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
-
Alex Ionescu -
Andrew Murphy -
art yerkes -
Brandon Turner -
David Johnson -
Maarten Bosma -
Robert Köpferl -
WaxDragon