said: 
>In <200604012112.k31LCe4E009548@pimout5-ext.prodigy.net>, on 04/01/06 
>   at 01:12 PM, sshapiro@ucsd.edu (Sandy Shapiro) said: 
>>If it is not a memory problem, what is your thinking? 
>It could be anything.  Motherboard, power supply, cable, connector or an 
>add-in card.  As Ray noted, the only way to figure this kind of stuff out 
>is divide and conquer.  When the problem goes away, you know you have 
>done something that fixed it.  Unfortunately, you don't always know 
>exactly what fixed it.  Consider Tom's PMView install problem.  It's 
>gone, but we really don't know what we did to fix it. 
OK -- so you agree this points to some kind of hardware and not OS/2 
problem. Actually, that is reassuring. 
Hardware is something I know how to deal with! 
Thanks, 
Sandy 
===================================================== 
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 
"postmaster@scoug.com". 
===================================================== 
<< Previous Message << 
 >> Next Message >>
Return to [ 01 | 
April | 
2006 ]
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.