wrote:
> I do notice that as eCS 1.2 boots, the text is
> almost half a character
> off the screen to the left. It's still readable,
> but not quite
> correctly aligned. I think this is something to do
> with SNAP, and
> changing my screen resolution.
Colin,
I have something sort of like that, seen during most
bootups (but, I think, not always), and also in Text
(full screen OS/2 or DOS) sessions, or when I fire up
my DOS word processor. I also think it has something
to do with SNAP, but don't really know what to do
about it, so I put up with it for now. A couple of
systems I'll be working on before long are likely to
require Panorama VESA, rather than SNAP, so we'll see
if this glitch occurs there also. But I'm guessing it
will likely be a different set of gltiches.
> However, the resulting system knows nothing about
> what I've set up over
> the past several years. There's no NTFS, no
> SeaMonkey, no OpenOffice
> 2.4, etc., etc. So I was thinking, maybe I should
> copy the eCS 1.2
> system to the new bootable volume, and try a
> migration-type install. If
> I made the new volume JFS, can I do that? And can I
> make eCS 1.2 copy
> itself in its entirety to this new drive G:? Or do
> I maybe need to
> install yet another eCS 2.0 to let me manipulate my
> C: and G: drives data?
>
> Suggestions appreciated,
> Colin
Colin,
I expect to be doing some migration experiments like
this too, in due course. Ray has come to the
conclusion that your greatest chance of success with
eCS installs (particularly the more complicated ones,
like those involving a migration) is on a fresh hard
drive where this is the only partition . . . and I
have some reason to think he is correct. Once this
(hopefully) succeeds, there should be ample options to
transplant the result elsewhere. My suggestion would
be to *copy* your 1.2 partition to a fresh drive (via
DFSEE), then use that as the target to migrate the 2.0
install over top of. This can be repeated later,
with variations, in case disaster strikes. That way,
"whatever falls apart in Vegas, stays in Vegas", if
you know what I mean.
At least, that is how I plan to do it. I may also
finally try out the Portable Backup migration function
one was supposed to be able to do via UniMaint, though
I hold out less hope of that working. That one was
supposed to let you change drive letter assignments in
the process of so doing . . . otherwise I don't know
if you could manage that without breaking a lot of
critical dependencies. The JFS deal -- I dunno, but
maybe better not trying to make too many huge changes
in a single pass ?
Just my .02c.
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 [ 25 |
March |
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.
