SCOUG-HELP Mailing List Archives
Return to [ 17 | 
June | 
2004 ]
 >> Next Message >>
 
 
 
Content Type:   text/plain 
=====================================================  
If you are responding to someone asking for help who  
may not be a member of this list, be sure to use the  
REPLY TO ALL feature of your email program.  
=====================================================  
 
On Wed, 16 Jun 2004 22:40:04 PDT7, Gary Granat wrote:  
 
>installed RSJ on the Dragon box.  When I rebooted, OS2CDROM.DMD refused to   
load  
>(an expected result, according to the discussions).    
 
 
I protest! That is NOT an expected, nor desired result. Something is wrong with your   
RSJ setup.  
 
 
>Prior to installing RSJ, the drive identified itself to the system as "S" and  
>acted like a normal CD-ROM reader.  After RSJ was installed, "S" no longer  
>appeared in the drive list, but RSJ offered to attach "Z" to the system.  When  
>I did that, the CD-ROM in the drive became visible.  Since I was more  
>interested in reading CDs than in burning them, I commented out the RSJ stuff  
>and the Dragon returned to its previous state.  
 
 
From what I can gather on your discussion, I believe you have a conflict of drivers. In   
your CONFIG.SYS how many *.FLT drivers do you have loading?  
HCM  
 
 
=====================================================  
 
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".  
 
=====================================================  
 
  
 >> Next Message >>
Return to [ 17 | 
June | 
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.
 
 |