Steven Levine wrote:
> 
> Define fail.  Do you get the /V output.  Does the system trap or is the
> problem just drive detection.

No trap.  At some point it cannot proceed.
> 
> If you are interested in persuing this read the section of Danis506.doc
> labeled "BUGS."  It describes who to need to do to supply useful data.

All I have been able to determine is /DEBUG:31.  From my previous 
attempts to deal with this, it is my understanding that if boot does not 
complete, that produces nothing.

Hence my general question.  I am not so much interested in beating one 
particular system into submission, but rather having a general approach 
to collecting boot data.  I have two systems that by changing the 
version of one file will either boot or not, but fail in different ways. 
  There just might be a third.....

Ray


------------------------ Yahoo! Groups Sponsor --------------------~--> 
Get to your groups with one click. Know instantly when new email arrives
http://us.click.yahoo.com/.7bhrC/MGxNAA/yQLSAA/9rHolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

 To visit your group on the web, go to:
    http://groups.yahoo.com/group/os2hardware/

 To unsubscribe from this group, send an email to:
    os2hardware-unsubscribe{at}yahoogroups.com

 Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



---