said: 
>But this fails: 
>    unzip -d C:\ BACKUP.ZIP 
If will work if you change this to: 
 unzip BACKUP.ZIP -d C:\ 
The help screen is not lieing when it shows the -d following all the other 
arguments.  The same is true for -x.  The ordering requirement makes some 
sense for -x, but does seem a bit arbitrary for -d.  So it goes. 
>The following works but I have to set C: to the root directory first: 
>    unzip -d C: BACKUP.ZIP 
It's not really working.  It does what you want by accident. :-) 
>Apparently UNZIP doesn't allow absolute paths either. 
Why would you assume such a silly thing?  How do you think everyone else 
manages to restore to an absolute path?  Also, the Unimaint snippets I 
posted clearly show restores to absolute paths. 
>Hmm, pretty much what I had except UniMaint uses the "-j junk (don't 
>record) directory names" option and doesn't save CONFIG.SYS. 
Right, but these are just details.  As I have said, there's nothing 
special about Unimaint's methods other than that theyt work without fail, 
for me. 
>UniMaint does a lot but it's not easy to use. 
If you say so.  I just read the manual when I don't understand something 
and ask questions if that doesn't work. 
>So I went to the Sup Files entry.  Yes it does CONFIG.SYS and 
>STARTUP.CMD.  No it doesn't come with SETUP.CMD (\MPTN\BIN\) by default 
>-- you apparently, and wisely, added it yourself. 
Along with a lot of others.  One technique I use which is not entirely 
obvious from the documentation is to supply unexpanded wildcards, rather 
than explict filenames when defining the supplemental files.  For example, 
to backup the WinOS2 .INI files is use: 
  Path:  f:\os2\mdos\winos2 
  Files: *.ini 
>Why UniMaint thinks there aren't any "supplemental" files defined is 
>beyond me.  Why UniMaint doesn't keep all the files in a single backup is 
>beyond me.  Why UniMaint didn't come with \OS2\MDOS\WINOS2\*.INI 
>specified in the supplemental backup so it would capture all the INI 
>files is beyond me. 
I never worry about these things unless I'm writing the code myself or if 
I know the author is doing active development.  Otherwise, I figure it's a 
better use of my time to just find ways to use the existing features that 
work the best for me. 
Regarding your inability to build the supplemental backup and restore CMD 
files, as you might suspect, it's not a problem I've ever had.  Take a 
look at the Desktop Defaults dialog.  Perhaps the error is a side effect 
of some other problem.  Try emptying the existing Supplemental File list 
and starting over.  You know, it's possible the list was empty and Larry 
initialized it to contain what you saw when you opened up the list.  Have 
you tried building the .CMD files after viewing the file list? 
Steven 
--  
--------------------------------------------------------------------- 
"Steven Levine"   MR2/ICE 2.35 #10183 Warp4/FP15/14.085_W4 
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST) 
--------------------------------------------------------------------- 
===================================================== 
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 [ 09 | 
April | 
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.