SCOUG-HELP Mailing List Archives
Return to [ 14 |
November |
2002 ]
<< Previous Message <<
>> 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.
=====================================================
Hi Wayne,
Why don't you setup a Maintenance Partition with BootOS2 ?
I suggest you create a small logical partition for it and do add
this
Partition to your Bootmanager !
Like this you are much faster for your maintenance and service
tasks !!
As for my environment it looks like following:
HDD1:
WS222_D Bootable : Primary FAT
512
Startable : Primary
BOOT MANAGER 7
WS222_A Bootable : Primary HPFS
1208
WS222_F Bootable C: Primary HPFS
1208
HDD2:
Disaster Bootable D: Primary HPFS
1004
None E: Logical
HPFS 5906
None F: Logical
HPFS 3373
None G: Logical
HPFS 8809
Booting from D: enables the service to one of the primary C:
partition.
If HDD1 is really having some problems ...
... my Disaster parttion isn't on the same troublesome HDD ...
... security reason ;-)
It's a peanut and done in less than half an hour ...
... and you will manage much more comfortable some system
troubles
if they really do happen !
Cheers, svobi
waynec@linkline.com on 14.11.2002 10.17.07
Please respond to scoug-help@scoug.com
To: scoug-help@scoug.com
cc:
Subject: SCOUG-Help: Power failure... chkdsk
Some time back, I'm not sure exactly when, I began having
problems when I
have to do an unscheduled reboot without a normal shutdown,
...for instance
if I have a power failure (or occasionally when I have a lockup
that seems
to be connected with my Mozilla browser getting tangled up with
Netscape).
Today was such a day: I forgot the computer was running when I
cycled the
circuit breakers while working on an appliance problem.
Formerly, an automatic chkdsk was launched during reboot and the
system
would then continue on and come up fine. Lately that automatic
chkdsk
complains that it can't find the root system file (I think that's
what it
calls it, I forgot to write it down), then it says it's searching
the drive
for it, then it says it's searched 100% of the drive and it just
hangs there
forever (after issuing that message).
I can boot from the Warp4 diskettes and run chkdsk off them and
it runs
fine, with this message every time:
"chkdsk corrected an allocation error for file
OS2\HELP\_CACHE0.DB"
(whatever that is)
Occasionally there might be another allocation error before it
runs to
normal completion, and then I can reboot from the hard drive
without further
problems.
Not a big deal, I can live with the extra 15 minutes or so that
it takes to
reboot from diskettes on these rare occasions, but I'm puzzled as
to why it
suddenly started having this problem.
Anybody have any comments?
Thanks,
Wayne
************************************************************
*** >>> Say NO to HTML in Mail and News <<< ***
*** ++++++++++++++++++++++++++++++++++++++++++++++++ ***
*** >>> AGAINST TERROR +++ AGAINST WAR <<< ***
************************************************************
=====================================================
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 |
November |
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.
|