|
SCOUG-HELP Mailing List ArchivesReturn to [ 03 | May | 2005 ]<< Previous Message << >> Next Message >>
Continuing from a recent thread on 4OS2-- 4OS2 is working as my default command processor, but there is an annoying, reproducible bootup problem. Bootup progresses normally through loading the desktop background and running startup.cmd at which point it sits there with a diamond, clockface cursor. After about 1 minute, a few seconds of HD activity occurs, but nothing more--ever. If I then CAD to inititate a reboot, bootup completes normally--the desktop is populated immediately after startup.cmd runs. But if I CAD to reboot too soon, i.e., before the HD activity, the reboot stalls at the same point. This two-step bootup is required whether the system has been up 1 minute or overnight. Seems weird, but it's reproducible. Bootup before installing 4OS2 worked normally every time. The system is SMP ecs 1.2 with 4OS2 v3.04f.
I probably haven't got something right in the 4OS2 setup, but I don't see anything in the help or 4os2.txt. Not using 4start or 4exit files as, from the manual, these aren't needed if4os2 is setup as the default command processor.
How do I go about tracking down the cause of this problem?
Ben A
--
=====================================================
To unsubscribe from this list, send an email message
For problems, contact the list owner at
=====================================================
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.
|