RE: Ros-dev Digest, Vol 13, Issue 13

[Lucio Diaz]

>   Message: 1
>  Date: Tue, 6 Sep 2005 08:42:13 -0400
>  From: WaxDragon <waxdragon(a)gmail.com>
>  Subject: Re: [ros-dev] Bootcd installation failure
>  To: ReactOS Development List <ros-dev(a)reactos.com>
>  Message-ID:
>  <9b0d5f32050906054215dd322b(a)mail.gmail.com>
>  Content-Type: text/plain; charset=ISO-8859-1
>  
>  Well, I have no idea what Lucio means by that "known
>  problem", since
>  he isn't very specific.  17600 is not even close to
>  where we forked
>  0.2.7.  I remember there were some problems around
>  then.  Try 17604, I
>  personally tested that rev and it seemed to work ok.
>  
>  In the future, if you are going to call something a
>  "known problem"
>  please link to the bug in Bugzilla.  If the "known
>  problem" isn't in
>  bugzilla, it isn't "known" as far as I care.
>  
>  Thanks
>  WD
>   
I reported it in both the general and dev mailing
lists, it happens in real hardware in two complitely
diferent computers, one Intel and one AMD, with
completely diferent OSes as base instalation and both
with previus sucesfull reactos instalations. In both
the instalation CD hangs before installing anything
(maybe reading the partitions?) to the Hard drive.

Not many people test reactos in Real Hardware, but i
was told the problem was already known. I have not
tested the SVN since long so i can not say if it is
solved. Still it is a KNOW reproducible problem of
0.2.7.

With best regards,
Lucio Diaz.


		
______________________________________________ 
Renovamos el Correo Yahoo! 
Nuevos servicios, más seguridad 
http://correo.yahoo.es

[WaxDragon]

I think you missed the point. I'm talking about
http://www.reactos.com/wiki/index.php/Known_Problems

When calling things "known problems" I want bugs for them.  I'm going
to assume you are talking about this known problem:

http://www.reactos.com/bugzilla/show_bug.cgi?id=688

Which was even noted on the 0.2.7 changelog page:

http://www.reactos.com/wiki/index.php/ChangeLog-0.2.7#Known_Bugs

PLEASE, if you write ANYWHERE that ReactOS has a "known bug" please
provide a link to the bug in bugzilla.

If there is no bug in BugZilla, then there is a great possibility the
Testing team doesn't know about it.  By filing bugs, we can reduce the
amount of duplicate effort required to fix said bug.

When filing bugs, please review
http://www.reactos.com/wiki/index.php/File_Bugs first.

With that out of the way, I know that noone has looked at that bug
since 0.2.7 was released.  If you can gather any useful info about the
hardware (the i8042 controller specifically) that you are
experienceing the problem with, update the bug, this may help with
getting it resolved.


WD

PS. I'm very tempted to make the "Know Problems" page go away, or
heavily modify it.

>   I reported it in both the general and dev mailing
>  lists, it happens in real hardware in two complitely
>  diferent computers, one Intel and one AMD, with
>  completely diferent OSes as base instalation and both
>  with previus sucesfull reactos instalations. In both
>  the instalation CD hangs before installing anything
>  (maybe reading the partitions?) to the Hard drive.
>  
>  Not many people test reactos in Real Hardware, but i
>  was told the problem was already known. I have not
>  tested the SVN since long so i can not say if it is
>  solved. Still it is a KNOW reproducible problem of
>  0.2.7.
>  
>  With best regards,
>  Lucio Diaz.

[Gge]

WaxDragon wrote:
>   I think you missed the point. I'm talking about
>  http://www.reactos.com/wiki/index.php/Known_Problems
>  
>  When calling things "known problems" I want bugs for them.  I'm going
>  to assume you are talking about this known problem:
>  
>  http://www.reactos.com/bugzilla/show_bug.cgi?id=688
>  
>  Which was even noted on the 0.2.7 changelog page:
>  
>  http://www.reactos.com/wiki/index.php/ChangeLog-0.2.7#Known_Bugs
>  
>  PLEASE, if you write ANYWHERE that ReactOS has a "known bug" please
>  provide a link to the bug in bugzilla.
>  
>  If there is no bug in BugZilla, then there is a great possibility the
>  Testing team doesn't know about it.  By filing bugs, we can reduce the
>  amount of duplicate effort required to fix said bug.
>  
>  When filing bugs, please review
>  http://www.reactos.com/wiki/index.php/File_Bugs first.
>  
>  With that out of the way, I know that noone has looked at that bug
>  since 0.2.7 was released.  If you can gather any useful info about the
>  hardware (the i8042 controller specifically) that you are
>  experienceing the problem with, update the bug, this may help with
>  getting it resolved.
>  
>  
>  WD
>  
>  PS. I'm very tempted to make the "Know Problems" page go away, or
>  heavily modify it.
>  
>   
I agree this you , we should not duplicate the informations in different 
places unless in this "known bugs" page  they are grouped per 
application or function

Gge