Re: Migrating from PCS to CA for Win95 (again)

Since CAwin95 is a 32 bit program you will not be able to install Client
Access until after Win95 is installed on the remote machines.  But, once
you have Win95 installed the DOS and Windows 3.1 versions of Client Access
will not work at all or will not have access to shared folders.

What I would suggest you do is create a CaWin95 installation shared folder
on the 400 and have each user download the entire folder to their local
hard drive.  They will need to leave it alone until Win95 is installed on
the PC.  Once Win95 is installed you can run the CaWin95 setup program from
the local disk.

To create the installation folder on the 400 use a Win95 PC with Client
Access95 already installed.  Create a folder on the 400 and name it CAW95. 
Next map a drive letter on the PC to the folder on the 400 (it will be
something like \\as400\QDLS\CAW95).  Now run the Create Install Diskettes
program from the Accessories folder in Client Access.  The Create Install
Diskettes allows you to specify a diskette drive as well as a drive path. 
Select minimum install and enter the drive letter of the mapped drive you
created above.  This will copy just the files needed for basic connection
to the AS/400 from Win95 (about 12mb).  

We've used this approach to upgrade our remote users to Win95 and CAWin95
(we created a Win95 installation dir on the 400 and had the users download
the folder to their local disk).  It's slow getting the files downloaded
and it requires some free disk on the remote PC but it sure beats putting
floppy disks into a PC.

Rob Ward
M-C Industries, Inc.
(913) 273-3990
rward@mcind.com
http://www.mcind.com 
----------
> From: Pete Massiello <PMassiello@OS-Solutions.com>
> To: MIDRANGE-L@midrange.com
> Subject: Re: Migrating from PCS to CA for Win95 (again)
> Date: Tuesday, June 03, 1997 7:21 AM
> 
> 
> Tom McArthur wrote:
> > 
> > <<SNIP>> 
> > I have 12 or 15 *remote* PCs that I need to upgrade to CA for Win95.
> > Making 12 or 15 copies of the 15 disks needed for CA isn't a viable
> > solution. Since all of the PCs are already connected to the AS/400, I
> > want to MIGRATE them to CA.
> > How do I do this? What INSTALL program do I run off of Shared
> > Folders? I don't see CA there; do I need to run a command on the 400
> > to copy QCA400 to QDLS (Shared Folders)???
> > 
> > Since DOS & Win31 can't run 32-bit CA code, I'm guessing that the
> > migration will be a multi-step process. What programs do I run for
> > each step?
> > 
> > SUMMARY: Since using disks isn't very practical, how do I migrate
> > *remote* PCs from PCS to CA for Win95?
> > 
> > Thanks, and sorry for the original ambiguity.
> > 
> > Tom
> > 
> Tom,  
> 
>     You may want to give this a shot.  Instead of creating the 12-15
> install disks, you might want to create the install disks on a Shared
> Folder (not an IFS directory, because only the new clients can access
> that), but create a folder in the QDLS directory. Then when you make
> install disks, instead of writing to A:, you write to this new
> directory.  Now all you need to do is execute the "setup" command in the
> folder from each of the remote PCs.  This will be much slower than
> creating disks for each client.
> 
>     If you had clients that were on Win 3.1 of Client Access, then they
> could point to the new IFS directories, and you would execute
> QCA400\WIN32\INSTALL\IMAGE\SETUP.EXE 
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *