Stewart Honsberger,

14-Nov-99 11:39:53, Stewart Honsberger wrote to Andy Roberts
 SH> 12 Nov 99 07:24, Andy Roberts wrote to Stewart Honsberger:
          Subject: Get Going

 SH>>> Just re-install the OS, and re-create icons for the neccesary
 SH>>> applications.

 AR>> You would not have to manually re-create the Icons nor even edit
 AR>> your config.sys etc, (and maybe not even reinstall at all) if you
 AR>> used:

 SH> The problem with a utility to save my WPS is the fact that the WPS
 SH> is typically the reason I'm forced to re-install.

Exactly, that's why I suggested RoboSave and ShiftRun.  Furthermore it backs
up more than just the WPS.  My last run saved 168 files or actually 302 files
including the 134 EAs, which it also restores and attaches perfectly.

 SH> Restore the old WPS, get the problems back.

If you have a problem with WPS, then there is no point is saving that as a
backup, so it won't get restored.  I only use RoboSave's Restore to put back a
known good previous setup.

Just before I run RoboSave again I copy my last previous 'save' to another
dir:
\Tools\RoboSave\   <=- Active for use with ShiftRun
\Tools\rs-4Jul99\  <=- Previously was in RoboSave dir
\Tools\rs-6Oct99\  <=- Previously was in RoboSave dir
\Tools\rs-9Oct99\  <=- Previously was in RoboSave dir

So if for any reason my active RoboSave 'saved' files are a problem, then I
can simply copy a previously 'saved' version into the RoboSave dir again.
Then reboot and use ShiftRun again.

Furthermore by looking in the ROBOSAVE.LOG file I can see the file names of
each individual file and it's new name, so I can manually copy/rename any
particular file back to the way it was before.

I doubt that I will ever have to reinstall or recreate an Icon again, no
matter how bad things get.  And even if I do reinstall to solve some problem
that RoboSave/ShiftRun can not cure (which I've never found yet), then I can
still use ShiftRun to recreate my previous setup with the new installation.

This paragraph is getting a little off of the topic but it does show the power
of RoboSave/ShiftRun along with with some other tricks.  I had Warp4 installed
on a primary C partition with about 50 custom Icons for my CMD files on my
DeskTop.  I made a Extended partition D and installed Warp4 from scratch just
to have a quick backup if an emergency did occur.  Of course that new
installation did not have any of my Icons etc.  So I made a copy of my entire
\Tools\RoboSave\ directory that worked with C drive and manually edited the
ROBOREST.CMD file to restore to the D drive instead.  What that accomplished
was to attach all the EAs as well as replace all the INI and RS and Config
files.  Then I manually edited all the INI and RS and Config files to change
every instance of "C" drive/path to "D" drive/path.  Some of that editing
requires a HEX editor, so I don't recommend that for a novice.  That editing
sounds worse than it really is, since in most cases a sequential "Find and
Replace" searching for " C " or " C:" and replacing with " D " or " D:"
respectively, will catch almost every reference to the installation
drive/path.  In the end I had an exact duplicate of Warp4 working on C drive
only this was working on D drive and had no reference to any file on C drive,
yet worked with all my apps on all other partitions.  Eventually I deleted my
original Warp4 from C drive, since the duplicate on D drive had all my Icons
and everything working.  Needless to say I didn't have to mess with any
obscure Config parameters nor reinstall any apps nor recreate any Icons to do
all that, thanks to RoboSave/ShiftRun.

     Thanks and Good Luck,        Andy Roberts
                                  andy@shentel.net
--- Terminate 5.00/Pro*at