said: 
>In <200310031915.0542455.6@scoug.com>, on 10/03/03  
>   at 07:15 PM, jack.huffman@worldnet.att.net said: 
>>Vaguely I remember your telling someone that you update the "original"  
>>config.sys with the current version.  Do I need to do this before using 
>>the SYSRESTR.CMD? 
>This option uses \os2\boot\config.x.  You only need to update it if you 
>have made hardware changes that will prevent this version of config.sys 
>from working. 
Thanks.  I replaced my cd-rom drive with the Plextor cd-rw drive.  So I am 
going to add to config.x the current config.sys lines that change 
required. 
>>Or can I just put G:\Unimaint\sysrestr.cmd on the 
>>command line? 
>Huh?  That a look at the Unimain manual.  It explains how to use 
>sysrestr.cmd. 
Thanks again.  I looked at the index and found nothing but did not go 
through the manual page by page.  Next time I will  do thatt, 
>>I ask this question because I found a config.sys file with a different 
>>size and created on a different date (except for two) in each of these 
>>five directories on my boot drive (c:). 
>These other versions are backups or garbage. 
>HTH, 
>Steven 
--  
----------------------------------------------------------- 
jack.huffman@worldnet.att.net 
----------------------------------------------------------- 
===================================================== 
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 [ 05 | 
October | 
2003 ]
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.