SCOUG-HELP Mailing List Archives

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

Date:	Wed, 16 Apr 2008 17:55:24 -0700
From:	Colin Campbell <cmcampb@roadrunner.com >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: eCS 2.0 Didn't Last Long.

Content Type: text/plain

Steven Levine wrote:
> In <480583EE.6000407@roadrunner.com>, on 04/15/08
> at 09:42 PM, Colin Campbell said:
>
> Hi,
>
>
>> OK, I didn't mean to.
>>
>
> I know that.
>
>
>> I was surprised when I saw that eCS 1.2 was
>> checking my new JFS volume.
>>
>
> It's a known issue that been discussed many times on many mailing lists
> and newsgroups. There's also FAQ items and the 2.0 readme mentions it,
> IIRC.
>
I read the README from 2.0, and searched it for JFS references. It
didn't warn me about a problem. I looked at eComStation.com's FAQ area,
and read the eCS 2.0, eCS General, and eCS Generic Software sections.
CHKDSK's /AUTOCHECK option is discussed, but I found no warnings about
older eCS versions messing up bootable JFS.
>
>> Does the older JFS code mess up the
>> "bootable" nature of the volume?
>>
>
> What does your experience tell you? :-)
>
> The IBM JFS CHKDSK marks the volume as a data volume because that's what
> is was required to do by the designers.
>
>
>> I guess eCS 1.2 just installed JFS support without asking, even though
>> I'd never had a JFS volume.
>>
>
> Yes.
>
>
>> I did look at the JFS volume from eCS 1.2,
>> and copy a file or two from Ray's earlier response onto the JFS volume.
>>
>
> This is not a problem.
>
>
>> That all seemed to work, though I still got the failure message. > Run
>> chkdsk from the eCS 2.0 install CD and all should be well. >
>> I gave this a shot from the management console, then rebooted, and I
>> still got the failure.
>>
>
> That should have fixed it. Did you neglect to add the /F switch?
>
I think I totally fouled that up - I used the CHKDSK option on the pull
downs in the management console, where the process is semi-gui (sticky?).
> BTW, recent versions of dfsee can fix non-bootable bootable JFS volumes.
>
>
>> I'm guessing it's this line that I need to fiddle in eCS 1.2's
>> CONFIG.SYS: IFS=C:\OS2\JFS.IFS /LW:5,20,4 /AUTOCHECK:*
>> Would I just remove the last part (/AUTOCHECK:*)?
>>
>
> Change to * to reference the volumes you want to check. Typically, you do want to check any of the non-bootable JFS volumes.
>
Well, since there are no JFS volumes I want to check, I have removed it
for now, leaving the original line as a remark.
>
>> I see that both JFS.IFS and UJFS.DLL are different. For now, I'm
>> leaving eCS 1.2 versions in place.
>>
>
> OK. This is not a problem.
>
>
>> I've reinstalled eCS 2.0 rc4, so I'll see if I can keep it up and
>> running.
>>
>
> OK. A man with time on his hands.
>
It didn't take too long, and you can start it and walk away for a good
part of the "easy" install.
> Steven
>
>
You were unusually gentle with me in these very helpful replies....
What have I done to deserve this sort of treatment?
Colin

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

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

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

Return to [ 16 | April | 2008 ]

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.