SCOUG-HELP Mailing List Archives
Return to [ 14 |
December |
2001 ]
>> Next Message >>
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.
=====================================================
Sandy,
When you run checkini without any options, you get an output to the
logfile, checkini.log. Have you studied that output for any clues to the
problem? What does the logfile say?
HCMotin
_______________________________________________________________________________________________
Sandy Shapiro 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.
> =====================================================
>
> HI Harry,
>
> OK, UniMaint 5.10.23 says: "Nothing to repair or Display"
> Checkini /C says error : cannot resolve the handle to a path.
>
> It then goes back to a command prompt. That's where I am stuck. Can't get
> beyond that error message.
>
> Sandy
>
> >Sandy,
>
> >I wish I could help you on that one. Sorry, I'm stumped. Also, I thought
> >about your problem with checkini bombing out. Can't help there. Steven
> >knows alot about the workings of checkini.
>
> >The only thing I can offer is to make sure that you use UniMaint first
> >(the latest CSD; I'm using version 5.10.23; I think it's the latest).
> >Perhaps you can cleanup enough of your OS2*.INI files with UniMaint,
> >using that first, then maybe checkini will work.
>
> >You should use a layered approach to clean your INI files. In general use
> >UniMaint first, then checkini and finally cleanini. Since your files
> >appear to be very dirty (years?? months?? of use without cleaning) you
> >will have to go slowly. I recommend making a RELIABLE backup of both INI
> >files and the desktop (C:\Desktop\*.*, for example), first, before you
> >use any of the cleaning programs. Make sure you can reliably restore
> >these files from a floppy diskette or maintenance partition bootup. In
> >using either checkini or cleanini, if either program gives you a lot of
> >INI file errors or problems, you should have checkini or cleanini repair
> >your files a little at a time.
>
> >When you finally get the files clean, use all 3 programs, UniMaint,
> >checkini and finally cleanini often (maybe 2 or 3 times a week in your
> >case) to keep them clean and trouble free.
>
> >I don't know if any of this is helping you??
>
> >HCMotin
> >_______________________________________________________________________________________________
>
> =====================================================
>
> 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".
=====================================================
>> Next Message >>
Return to [ 14 |
December |
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.
|