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 [ 06 | October | 2005 ]

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


Date: Thu, 6 Oct 2005 21:54:16 PDT7
From: Tom Brown <thombrown@san.rr.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: CHKDSK /F then what ?

Content Type: text/plain

Peter,

1. You need a program called pmchklog.exe to reead the log files. It was
on an IBM website, probably gone now. Hobbes? Google!
2. Every invocation of chkdsk overwrites to log file, so if you have a
problem, SAVE the log file under some other name or directory. FWIW, a
CHKDSK.LOG with a length of 24 bytes is produced by an error-free run of
chkdsk.
3. Files named FILExxxx.CHK are files (or fragments) that chkdsk has
saved after it found a problem. You have to look at chkdsk as it is
running or look at the log with pmchklog.exe to try to determine what
the FILExxxx.CHK really are. You can also use an editor to open the file
to see if you can guess what they are. :-)) Good luck!

My suggestion would be to upgrade to JFS.

Peter Skye wrote:
> CHKDSK /F creates chkdsk.log in the root directory and sometimes creates
> FILE0000.CHK etc files also.
>
> These files aren't text. How do I analyze them to see what they
> contain, and is there some sort of repair I'm supposed to perform based
> on their contents?
>
> - Peter

--
Tom Brown, Catherder
thombrown at san dot rr dot com
Member SCOUG, V.O.I.C.E. & SDAA

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

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
"postmaster@scoug.com".

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


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

Return to [ 06 | October | 2005 ]



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.