SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, 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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 20 | July | 2002 ]

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


Date: Sat, 20 Jul 2002 01:45:57 PST7
From: Peter Skye <pskye@peterskye.com >
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.
=====================================================

Wayne Cypress wrote:
>
> >I run checkini like this:
>
> > CHECKINI /C /S /Y:2 /W
>
> I'll try it out tomorrow

Make sure you rename the existing OS2*SV.INI files before
running CheckIni again, since it will overwrite them.

I simply add the date-time stamp to the name, thusly:

OS2SV.INI-20020720-0152

One benefit of this is that after you've accumulated
a few of these you can *see* if they're getting
smaller -- just run a DIR.

> I assumed that the operating system is using a copy of the
> ini file(s), and I guess now I'm not sure what checkini
> alters, the copy in memory or the copy on the hard drive.

CheckIni alters OS2*.INI by saying "change this". The WPS
makes the actual changes.

The INI files are very simple. They are like a 3-column
spreadsheet. The first column is titled Application and
is the general purpose of that particular line in the
spreadsheet (for example, "MyFinancialPrograms"). The
second column is titled Key and is the specific name for
that particular line (for example, "MyTaxReturnFor2001").
The third column is the Data (for example,
"C:\Finance\Taxes\1040-2001.txt").

It looks like this:

Application Key Data
=================== ================== ==============================
MyFinancialPrograms MyTaxReturnProgram C:\Finance\Taxes\DuckTax.exe
MyFinancialPrograms MyTaxReturnProgram C:\Finance\Taxes\1040-2000.txt
MyFinancialPrograms MyTaxReturnFor2001 C:\Finance\Taxes\1040-2001.txt

When CheckIni runs, it reads every line in this INI
"spreadsheet" and checks what it finds. If, for
example, it finds that there *isn't* any file called
C:\Finance\Taxes\1040-2001.txt then it says to the WPS,
"DeleteThisLine MyFinancialPrograms:MyTaxReturnFor2001".
The WPS is then supposed to look in the INI file (or at
its option in the copy which it keeps in memory), find
the line whose first two columns match
MyFinancialPrograms:MyTaxReturnFor2001, and delete that line.

Simple, yes? As for why it doesn't always work, who knows.

> I think the first time I ran checkini, I simply shut down
> and rebooted afterwards. When the stuff I'd asked to be
> deleted was called out again the next time I ran checkini,
> I thought perhaps I NEEDED to reset the WPS

CheckIni resets the WPS as its final step. It gives you a
prompt on the screen, something like "Reset Workplace Shell
(Y/N)?".

Resetting the WPS is just a way to get it to write the changes,
which are held in memory, to the OS2*.INI files on the hard
drive. If you reset the WPS this will happen. If you do a
Shutdown this will happen. If you simply wait a few minutes
this will happen (the WPS has a timer and "occasionally" writes
any changes to the hard drive). If you reboot without doing a
Shutdown then the changes may not have been copied to the
OS2*.INI files yet. (If you do a cold boot or have a power
failure while the file is being written then you'll need to
restore the OS2*.INI files from a backup 'cause they'll be
scrambled.)

- Peter

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

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



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.