said:
Hi,
>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. (In fact, looking at things on eCS 1.2,
>where I have the screen set to 1280 x 1024, I think I chose 1280 x 960
>by mistake on eCS 2.0.)
That's probably it. Depending on your monitor, these things can be
adjusted. SNAP includes utilities for this too.
>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.
It's worth a try. See below.
>If
>I made the new volume JFS, can I do that?
Yes, but it will require a bit of manuel editing.
>And can I make eCS 1.2 copy
>itself in its entirety to this new drive G:?
Yes. See below.
>Or do I maybe need to
>install yet another eCS 2.0 to let me manipulate my C: and G: drives
>data?
This is a good idea regardless. This can be your maintenance volume.
If you are feeling lucky, try this. If all goes well, the result will be
eCS 1.2 booted from a JFS volume and you can try the migrate.
- Save a copy of the config.sys from G:.
- Save copies of UJFS.DLL and JFS.IFS from G:.
- Save a copy of OS2BOOT from G:.
- Delete all the files on G:. Do not reformat.
- Xcopy all the files from C: to G:.
- Copy the saved UJFS.DLL and JFS.IFS back to G:.
- Copy the saved OS2BOOT back to G:.
At this point you have all the files you need in place. The eCS 1.2
config.sys that is now on G: may not be quite right for booting from JFS
so you may need to edit it. Use the saved G:\config.sys as a reference.
Make sure that JFS.IFS and HPFS.IFS load in the same order as the working
2.0 install.
This will be something like:
DEVICE=C:\OS2\BOOT\UNICODE.SYS
IFS=C:\OS2\JFS.IFS /LW:5,20,4 /AUTOCHECK:*
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:4 /AUTOCHECK:*
It's OK if LOG.SYS loads before the IFSs.
Now you need to adjust the drive letters
- Hide volume C:.
- Rename volume G: to volume C:.
- Reboot.
If all goes well your eCS 1.2 copy will boot from the JFS volume and you
can try the migration install. If not, we can figure out what I forgot to
mention.
I recommend backing up the volume before trying the migrate. It will be
easier to restore and try again if the migrate fails.
BTW, your production eCS 1.2 is safely hidden away so if all else fails,
use make it volume C: again and it will be ready to go.
Steven
--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 3.00 beta 11pre #10183 eCS/Warp/DIY/14.103a_W4 etc.
www.scoug.com irc.ca.webbnet.info #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
"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.
