|
You could write a Visual Basic program to replace STARTPCS.BAT. or there is a shareware product called WinBatch that I could email you if you like... ---------- > From: Tom McArthur <ThomasMcA@usa.net> > To: MIDRANGE-L@midrange.com > Subject: Client Access for Win95 > Date: Thursday, May 29, 1997 7:15 PM > > Using Client Access for Win95, is there a way to execute > (automatically, at the time the connection is made) a batch file that > lives in a Shared Folder? > > As a PC administrator, using the old PC Support, I was able to use > the Shared Folders (I: Drive) as a network drive and a pseudo-backup > medium. > > Since every PC executed STARTPCS.BAT, it was easy to add a CALL to a > generic batch file that lived on the I: Drive. This batch file backed > up their system files (INIs, CONFIG.SYS, etc.) once a day; it also > allowed me to do remote installs, updates, file copies, etc. > > If a remote user had a problem w/ a Lotus spreadsheet or a > WordPerfect document, I could edit the generic batch file to copy the > file from their hard drive to the I: Drive. I could then open the > file myself, and walk them through their problem/question. > > If they had a problem w/ Windoze, I could look at the backup of their > configuration files to understand their setup, or even to see the > problem right away by looking at their backed up CONFIG.SYS & > AUTOEXEC.BAT files. > > The beauty of this was that everything was maintainable here at the > corporate location. They couldn't remove the CALL to the generic > batch file because a master copy of STARTPCS was maintained on the I: > Drive. I could modify/tweak the process easily because the batch file > lived on the I: Drive. > > Is there any way to do this? > > TIA > > Tom > *************************************************** > Tom McArthur > E-Mail: ThomasMcA@usa.net > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > * 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 * > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 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.