SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Wed, 26 Dec 2001 19:11:50 PST7
From:	Harry Chris Motin <hmotin@attglobal.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: A Little Knowledge is a Dangerous Thing

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.
=====================================================

Jordan,

I presume that you straightened out your desktop problem and now have
your system back up with everything more or less as you had it before?
Hope so!

Sorry about the preaching BUT ...,
The most important thing you can do (besides making regular full backups
of your hard drive) is to backup get a reliable system for backing up
and restoring both INI files and the desktop. And you must test it to
see whether or not it works and you know how to do it. For example, I
use BackAgain/2000 Workstation. It has a complete restore crash recovery
system. I had to write down and save on paper how to use the crash
recovery system (the method for entering drive and path data in one the
sub-windows was not obvious for me).

OK enough preaching.

A little while ago I send you 4 script files for automating the use of
CHECKINI and CLEANINI via PMREXX. Have you been able to use these files
for your system yet? If not, do you think that you will?

Harry

_______________________________________________________________________________________________

Harry Chris Motin wrote:
>
> Jordan,
>
> I confess that I've never used the UniMaint desktop backups to restore
> my system. I think, however, that you can do a complete restore that
> way. According to the UniMaint reader's manual, the desktop backup makes
> a backup of the desktop and both INI files. Do you have a copy of the
> manual? If so, on pages 168 to 169 it tells how to restore the desktop
> and/or INI files. If not, you I think you will have to muddle through
> it, using UniMaint online help.
>
> HCM
>
> _______________________________________________________________________________________________
>
> "J. R. Fox" wrote:
> >
> > =====================================================
> > 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.
> > =====================================================
> >
> > Fie upon you meddlesome tinkerers, you devotees of CHECKINI &
> > CLEANINI, forever chasing down trivial inefficiencies and
> > illusory "problems"!! (You know who you are.) I never even got
> > that far, and still you have led me down the primrose path to
> > desktop destruction. Let me explain.
> >
> > I've had UNIMAINT for as long as I've been running OS/2. It is
> > the only one of these system repair thingies that I've used, and
> > even that sparingly. And I've (almost) never had a significant
> > problem. From conversations with other SCOUG members at
> > meetings, I know there are others whose experience has been quite
> > similar. Whatever the other repair util.s might be able to find
> > "wrong" under the hood, most of the time, it can't have been
> > terribly important.
> >
> > I never noticed the "Do Agressive File Handles Repair" option
> > until now, after it was mentioned on the List. Perhaps this
> > option was introduced with the last UniMaint csd, which I only
> > recently applied. Well, I tried this, and it has seriously
> > compromised my desktop. (Guess they weren't kidding about it
> > being aggressive . . . . ) Most of the objects and folder
> > contents have seemingly lost their icons and won't open, beyond
> > an initial Properties screen. I've manually test-fixed a few of
> > these, by re-entering the Program Tab info. In some cases, the
> > icon is not actually "lost." In most of the ones inspected thus
> > far, the File Associations are not gone either. But some other
> > custom info may have been lost. Restoring each and every
> > affected object by hand looks like a most dreary prospect.
> >
> > I'm theorizing that I inadvertently wiped out a ton of program
> > .INIs, and probably knocked a lot of important stuff out of the
> > Warp system .INIs. I think that UniMaint may have some shortcut
> > way of fixing this, in effect turning back the clock -- possibly
> > via Restore Desktop INIs in the Desktop menu -- but I don't want
> > to try it or even reboot before getting some guidance, for fear
> > of winding up someplace worse. I've never had to do this
> > before. Luckily, I made a Desktop backup (plus a Portable
> > Backup), just before embarking on this ill-advised venture.
> >
> > If I can successfully get back to where I was, it will be *very
> > easy* to resist any further temptations to "fix" things.
> >
> > Jordan
> >
> > =====================================================
> >
> > 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".
> >
> > =====================================================

=====================================================

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".

=====================================================

Return to [ 26 | December | 2001 ]

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.