SCOUG-HELP Mailing List Archives
Return to [ 29 | 
July | 
2004 ]
<< Previous Message << 
 >> 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.  
=====================================================  
 
Harry Motin wrote:  
>   
> Peter Skye wrote:  
>   
> >I wrote a little .cmd which tells me if  
> >the OS2*.INI files have been updated.  
>   
> But the point is here, that you CANNOT use that *.cmd file. If you use  
> it and one or both *.INI files have not been updated, then your repairs  
> to that file(s) will not take affect. You have to simply WAIT WITHOUT  
> DOING ANYTHING UNTIL THE OS WRITES THE REPAIRS TO THE OS*.INI FILES  
 
Why can't I use it?  How can running my simple little .cmd cause these  
changes to end up in a parallel dimension known only to Stephen Hawking,  
Stephen King or Steven Levine?  
 
> >I don't know why UniMaint's updates aren't applied  
> >to the OS2*.INI files in all situations.  
>   
> Because, with Warp 4 you've got to wait for the  
> write update, before you do anything!  
 
Why?  Why why why why?  
 
- Peter  
 
 
 
=====================================================  
 
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 [ 29 | 
July | 
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.
 
 |