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

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


Date: Sun, 14 Jul 2002 12:42:27 PST7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Troubleshoot a boot hang?

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:
>
> the blue screen stays up and I never get the desktop.

I had this problem for a while; I just replaced by OS2.INI and
OS2SYS.INI files from the last backup and everything would work again.
This isn't a "desktop restore" but it fixed the problem here.

The problem started here shortly after CHECKINI (WPTOOLS) wouldn't run
any more (it would hang trying to fix the two OS2*.INI files).
Eventually I got UNIMAINT to run which fixed whatever CHECKINI was
hanging on, and the problem went away.

If you restore the two OS2*.INI files from a backup, you *have* to boot
to a different partition (or to floppy) -- and make *sure* your IDE
drivers are updated before you do so if you're on a large partition (the
old drivers didn't like large partitions). (The latest IDEDASD package
contains files dated 25-Apr-2002.)

The reason for booting to a floppy or different partition is that on
bootup OS/2 reads the OS2*.INI files into memory and keeps them there,
occasionally rewriting them to disk. So if you boot and then replace
the files that are on the partition you booted to, they'll soon be
overwritten by the old bad files that are still in memory. Since you
can't boot, I guess you'll have to boot to floppy or a different
partition.

- 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 [ 14 | 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.