SCOUG-HELP Mailing List Archives

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

Date:	Sun, 2 Jan 2005 16:00:08 PST8
From:	"Steven Levine" <steve53@earthlink.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: eCS 1.2 install failure

=====================================================
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 <480-2200510223551484@M2W084.mail2web.com>, on 01/02/05
at 03:05 PM, "jr_fox@pacbell.net" said:

>Well, you know, if there is *any* way to find a non-standard or
>_original_ result, I'm your guy !

It's OK. I was starting to feel a bit like the Maytag guy.

>have to attempt it more than once. In that case, once I get the
>bugtracker URL, I can follow up on that.

You should already have it. When you log onto the ecomstation site, there
should be a link to the bugtracker.

>> We need more info, but error 3 is usually path not found. We need to
>> figure out which path.

>O.K. 'Path Not Found' seems so fundamental. I'm wondering how that
>happens.

Same way folks kill each other in cars. Every car is a bit different.
Accidents happen. Nothings perfect.

>This seems to imply that it *could* be a sufficient launching pad for
>successfully completing the install . . .

Could be? It has been. There would be no need for resume.cmd to exist
unless it was possible, in some cases, to restart and complete the
install.

>might require the sort of hands-on, command line type stuff you needed to
>intervene with to finesse the 1.1 installs for this box (?)

Depends on the failure. It's easy enoungh to open a command line session
if it is needed.

>Sure. I've got little to lose at this point, and with 1/9 looking iffy
>for me, I might as well give it a shot, or two.

I haven't had any reports of bad CDs, but one never knows. Have you
tested the CD for errors?

>My thinking there was that the 1.1 *had* a _working_ TCP/IP, MPTS, Peer,
>whatever. If those setups remained intact, although with various updated
>files,

That's a very big assumption and an incorrect assumption. What migrate
attempts to preserve is your settings not any existing program files. The
program files are always replaced. It is simply too complex and error
prone to do it any other way.

>If the
>_regular_ re-install attempt(s) should also fail, maybe a Migration run
>would then be worth a try ?

A migration might be worthwhile, but not for the reason you state. The
benefit of a migration is you retain much of your previous configuration.
With LVM and some free drive space, you can do this without distrurbing
your current boot volume:

- create a volume
- xcopy or clone boot volume to new volume
- hide original boot volume
- give new volume same letter as original boot volume
- make sure it can boot OK etc.
- do a migration install
- test etc.

If you have problems, just use LVM to switch back to the original boot
volume.

HTH,

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.60b #10183 Warp4/FP15/14.100c_W4
www.scoug.com irc.fyrelizard.com #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".

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

Return to [ 02 | January | 2005 ]

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.