Re: Migrating from PCS to CA for Win95

At 12:18 PM 5/31/97 +0000, ThomasMcA@usa.net wrote:
>We have quite a few remote PCs (using Win 3.1) that are currently 
>using Extended DOS PC Support. All of these will soon be upgraded to 
>Win95. 
>How do we upgrade them to Client Access for Win95? Is it a multi-step 
>process, maybe? (PCS  to  16-bit CA  to  32-bit CA???) I don't even 
> [snip]

You can upgrade using the CD as well. During part of the process, it asks
you if you are upgrading, and asks for the path of your "control" file. If
you're upgrading from Extended DOS, point it to c:\pcs\config.pcs. If
you're upgrading from 16-bit CAWin, point it to c:\cawin\pcs.ini.

HOWEVER, it's easier/quicker to just do a scratch install. The upgrade is a
multi-step process (first installs the basic connections, then a reboot to
connect to the IFS, more install from , then Rumba-to-PC5250 migration). In
our experience, as much time as you will take checking to make sure
everything migrated correctly, you can do a scratch install just as quickly
or quicker.

The Win95/NT CA is not as simple an install/upgrade as the old Extended DOS
to Enhanced Win3.x upgrade was. I like the new client's integration with
Windows 95/NT better, but setup is more than a wee bit kludgey.

Jeff Gumm
Kansas Dept of Health & Environment
Topeka, KS
jgumm@kdhe.state.ks.us
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *