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 [ 25 | January | 2003 ]

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


Date: Sat, 25 Jan 2003 08:53:45 PST8
From: Harry Chris Motin <hmotin@attglobal.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: CHKDSK/SYS3175

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.
=====================================================

Steven,

Thanks for your reply. Yes, I am very certain that my boot diskettes are
the same level as my OS. I spent a lot of time, a couple of years ago,
making REXX scripts that create boot disks that use the files on my hard
drive. In other words, when the "Create Utility Diskette" program comes
up, I'm able to check the "use newer files on the hard drive" option.
Once more, when I use the utility diskettes the kernel version level is
identical to my normal OS (Warp 4, level 14.085).

I'm thinking that the problem may have to do with the amount of memory I
have, versus the size of the partition that you are trying to CHKDSK.
Let me give you some statistics on my system:

1. CHKDSK from bootable floppies:

Partition Size, GB % Used Time Needed to complete

C:\ 8.0 26.7 (2.1GB) approx 1 minute

D:\ 36.3 2.2 (0.8GB) immediate SYS3175 error

E:\ 30.7 68.6 (21.0GB) > 60 minutes?? (never finished)

2. CHKDSK from fully up system:

C:\ 8.0 26.7 (2.1GB) cannot do (locked drive)

D:\ 36.3 2.2 (0.8GB) cannot do (locked drive)

E:\ 30.7 68.6 (21.0GB) approx 1 minute

F:\ 30.7 0.6 (0.02GB) approx 1 minute

I am aware that running CHKDSK from a fully up system is a little
different than from floppies. The process is different (as evidenced by
the difference in completion times on E:\). I am also aware that running
CHKDSK on a partition, while fully up and running, could be dangerous
for the files on that partition.
HCM

___________________________________________________________________________________________

Steven Levine wrote:
>
> =====================================================
> 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.
> =====================================================
>
> In <3E3216C5.A879DEDF@attglobal.net>, on 01/24/03
> at 09:23 PM, Harry Chris Motin said:
>
> >When I try to run CHKSYS on D:\, after booting from floppies, I get
> >absolutely nowhere. I get a SYS3175 error. As a result I cannot run
> >CHKDSK on D:\ at all, unless I take some drastic steps.
>
> Are you absolutely sure the diskettes are updated to the same level as
> your production boot? You are running large drives and older versions of
> chkdsk might stumble.
>
> >If I try to run it from a fully booted system, I get the message that D:\
> >is locked by another process (I believe its the system's knowledge and
> >use of the SWAPPER directory on D:\). Next, I took everything off D:\,
>
> Any open file on the drive will cause this.
>
> >I checked this out on the Internet and at least one other person
> >experienced the same thing. However, he did not discover a reason why or
> >a fix for it. I would like to know if anyone has had similar problems,
> >or has an answer to it.
>
> We can discuss options and workarounds after you have verified the content
> of your boot diskettes.
>
> Steven
>
> --
> ---------------------------------------------------------------------
> "Steven Levine" MR2/ICE 2.35 #10183 Warp4/FP15/14.085_W4
> www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
> ---------------------------------------------------------------------
>
> =====================================================
>
> 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".
>
> =====================================================

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

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 [ 25 | January | 2003 ]



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.