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 [ 15 | April | 2008 ]

<< Previous Message <<


Date: Tue, 15 Apr 2008 21:42:06 -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 <4804176E.6000109@roadrunner.com>, on 04/14/08
> at 08:21 PM, Colin Campbell said:
>
> Hi,
>
>
>> Each time I boot eCS 1.2, CHKDSK runs against the G: drive and
>> pronounces it fine.
>>
>
> Don't do that. The eCS 1.2 JFS is incompatible with the eCS 2.0 bootable
> JFS.
>
OK, I didn't mean to. I was surprised when I saw that eCS 1.2 was
checking my new JFS volume. Does the older JFS code mess up the
"bootable" nature of the volume?

I guess eCS 1.2 just installed JFS support without asking, even though
I'd never had a JFS volume. 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.
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.
> Edit your eCS 1.2 config.sys to not run chkdsk on your 2.0 volume or
> replace the eCS 1.2 UJFS.DLL with the eCS 2.0 UJFS.DLL.
>
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:*)?

That is what I did, and I no longer see the CHKDSK messages for the JFS
volume.

I see that both JFS.IFS and UJFS.DLL are different. For now, I'm
leaving eCS 1.2 versions in place.

I've reinstalled eCS 2.0 rc4, so I'll see if I can keep it up and running.

> Steven
>
As always, thanks for the help! This seems like a trap that I just fell
right into. Maybe there needs to be a warning about adding eCS 2.0 to a
PC where eCS 1.2 still resides. I didn't see any warnings in the README
for 2.0....
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".

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


<< Previous Message <<

Return to [ 15 | April | 2008 ]



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.