SCOUG-HELP Mailing List Archives

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

Date:	Sat, 20 Jul 2002 10:44:44 PST7
From:	Harry Chris Motin <hmotin@attglobal.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: boot hang... still

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

HCM said:
> > 6. Finally, do not do anything for a couple of minutes. Give the system
> >time to update the OS2.INI. What's going on here is that, when OS/2 is up
> >and running, it does not use the OS2.INI file to record the changes that
> >you make to your system. Instead, it uses the OS2.!!! file, which in the

Steven said:
> TTBOMK, this not doing what you think it is. When you reset the Desktop,
> you effectively throw away the changes that the WPS has been caching in
> OS2.!!!. What the reset is supposed to accomplish is to prevent these
> cached changes from reversing the changes made by Unimaint or checkini.

OK! I hear your explanation, above, about the function of restarting the
desktop (to prevent changes that the WPS has been caching from reaching
the OS2.INI file). However, that's not my experience. My routine is to
run UniMaint, then Checkini and finally Cleanini. I reset the desktop
after each one. Maybe I'm wrong, but I've discovered that after I
perform the cleaning, I have to do nothing for a couple of minute, or
reboot. If I immediately start doing things, some or all of the fixes
made by one or all of UniMaint, Checkini and/or Cleanini will not stick.
Go figure!

HCM
_______________________________________________________________________________

Steven Levine 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.
> =====================================================
>
> In <3D3899E1.D67E0C2A@attglobal.net>, on 07/19/02
> at 02:58 PM, Harry Chris Motin said:
>
> >Steven and I have talked several times in the past about the correct
> >procedure to regularly clean the OS2.INI. I believe he told me (Steven,
> >correct me if I'm wrong here) the following (and this is in fact what I
> >do!):
>
> Couple of things. IIRC, Wayne does not have Unimaint. At least, he had
> not mentioned using it.
>
> There's not absolute right or wrong here. I prefer not to let Unimaint or
> checkini reset the Desktop. Others claim I'm and idiot and that unless
> the Desktop is reset to fixes won't stick. I let them glory in there
> opinion.
>
> That said, if using my normal procedures does not fix a problem, then it's
> time to try something else. :-)
>
> > 6. Finally, do not do anything for a couple of minutes. Give the system
> >time to update the OS2.INI. What's going on here is that, when OS/2 is up
> >and running, it does not use the OS2.INI file to record the changes that
> >you make to your system. Instead, it uses the OS2.!!! file, which in the
>
> TTBOMK, this not doing what you think it is. When you reset the Desktop,
> you effectively throw away the changes that the WPS has been caching in
> OS2.!!!. What the reset is supposed to accomplish is to prevent these
> cached changes from reversing the changes made by Unimaint or checkini.
>
> >or at least not in a long while. It is quite dirty with a lot of junk.
> >The correct procedure here is to use UniMaint, first and only (Steven,
> >again correct me, if I am wrong). Clean it gradually, a little at a time.
>
> That's a good suggestion if the changes appear to not be sticking. The
> longer you take to run checkini, the more chance that the WPS will decide
> to flush its internal buffers and overwrite a change.
>
> Steven
>
> --
> ---------------------------------------------------------------------
> "Steven Levine" MR2/ICE 2.31a #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".
>
> =====================================================

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

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 [ 20 | July | 2002 ]

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.