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 [ 23 | January | 2006 ]

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


Date: Mon, 23 Jan 2006 15:22:37 PST8
From: J R FOX <jr_fox@pacbell.net >
Reply-To: scoug-help@scoug.com
To: < "scoug-help@scoug.com" > scoug-help@scoug.com >
Subject: SCOUG-Help: 1.2R Migration Failure

Content Type: text/plain

Today I finally got to where I was ready to try the
1.2R migration install, over top of the secondary eCS
1.1 (P:) that has served as a
much-more-than-Maintenance partition on my Shuttle
system. I'd have to call the result a major failure.
My first impression is that the ever-improved (?)
installer is still not nearly good enough, and the
Migration install option apparently blows. (Ray, I
hope your attempt went much better.)

1st. issue: The CONFIG line

IFS=P:\OS2\JFS.IFS /LW:5,20,4 /AUTOCHECK:*

is still a dealbreaker. The boot sequence takes an
early vacation here, and never returns. I'm going to
guess that it is choking on the NTFS partitions that
belong to the Dark Side. Okay, so I REMmed that line
out again, as usual. (I've never used JFS anyway.)

2nd. issue: Peer install still fails. Were they
supposed to have improved on this, since the 1.2 GA
build ? I can look to see if the Error report is any
different this time (don't think so), and I'll be glad
to furnish whatever files to whomever.

3rd. issue: clearly another incomplete install, even
discounting Peer. Just *how* incomplete I can't yet
say, because SNAP did not go on, and the plain VGA 800
x 600 display is not suitable for doing very much.
Even for a base install, the desktop has very little
on it. There is a Previous Desktop, but I don't wish
to explore it at this resolution. (Nor do I know how
to substitute it permanently.)

My guess is that I'd find a number of other things
either missing or non-functional.

I don't think I messed this up in how I did the
install, having observed a few of these by now . . .
but that is subject to revision. My system is not
supposed to be particularly exotic. If these things
are true, then I'm inclined to say this installer
still ain't ready for primetime, and I wouldn't expect
to attract any potential converts with it.

Now the question is: Should I scrub this partition and
restore the prior eCS 1.1 image, or is what's on there
readily fixable without an excessive amount of work ?

Jordan

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

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 [ 23 | January | 2006 ]



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.