I tried running unimaint.exe from a command line and it works.
442 UNIMAINT
I'll try viewing them _after_ I send this message (in case it shuts down
my system).
_____
Steven Levine wrote:
>
> >>>You say to run SysRestr, but there's no such program
>
> You didn't tell Unimaint to automatically
> rebuild sysrestr.cmd (do Restore CMD when
> Backup) and you didn't build it yourself.
> Desktop -> Create Restore CMD File.
Thanks. And I just looked and found "Creating a Restore CMD File" on p.
28 of the manual.
I have a sysrestr.cmd now. :)
> The really important question is do
> you have any files named SYSBCK*.ZIP
Yes, I have some:
[H:\Maintenance\UNIMAINT]dir *.z*
9-08-01 11:29a 1254207 55 SYSBCK01.zip
9-07-01 7:24a 1249852 55 SYSBCK02.ZIP
9-06-01 8:07p 1249679 200 SYSBCK03.ZIP
9-06-01 12:03a 1151181 55 SYSBCK04.ZIP
The number of SYSBCK*.ZIP generations isn't documented in the manual,
but the online Help says the default is 10. I changed it to 100. I
don't know where the value is kept -- I ran DIR /OD and no files had new
times. (And what's with the year 2016 on the TL* files?)
- 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 [ 08 |
September |
2001 ]
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.