said: 
>>Based on the code I've read I would expect the OHCI controller to show up 
>>in the hardware manager.   
>OK, that's all I was referring to.  
Now I'm confused.  I'm saying it should show up.  Does it or does it not. 
>>Also, /V on the BASEDEV statement should 
>>generate screen output. 
>That didn't happen.  Though it didn't happen with the /v for the quatech 
>either, and that shows up in the hardware manager. 
This is probably the too many messages problem.  One needs to turn off all 
BASEDEV /Vs except for the BASEDEVs of interest. 
>I've had a /V on both for awhile now.  Neither is giving screen output.   
Try turning off the /Vs for all drivers but but the OHCI and UHCI 
BASEDEVs. 
Steven 
--  
---------------------------------------------------------------------- 
"Steven Levine"   MR2/ICE 2.47 #10183 Warp4/FP15/14.093c_W4 
www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST) 
---------------------------------------------------------------------- 
===================================================== 
To unsubscribe from this list, send an email message 
to "steward@scoug.com". In the body of the message, 
put the command "unsubscribe scoug-help". 
For problems, contact the list owner at 
"rollin@scoug.com". 
===================================================== 
<< Previous Message << 
 >> Next Message >>
Return to [ 15 | 
September | 
2004 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA  92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group.  ALL RIGHTS 
RESERVED. 
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International 
Business Machines Corporation.
All other trademarks remain the property of their respective owners.