|
> 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. Thank you for the suggestion. > 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 I like this option better. Can I upgrade these remote PCs from PCS to CA for Win 3.1 remotely? Is there a command to execute on the 400 that puts CA into QDLS so these PCS-attached PCs can get to it? Thanks. Tom * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 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 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.