home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!icdoc!ibmassc!hursley.ibm.com!stirling
- From: stirling@hursley.ibm.com
- Newsgroups: comp.os.os2.misc
- Subject: Re: BACKUP's and the Desktop
- Message-ID: <Jul27.102706.46781@aixssc.ibm.co.uk>
- Date: 27 Jul 92 10:24:18 GMT
- References: <26JUL199218454803@vmsb.is.csupomona.edu>
- Sender: stirling@hursley.ibm.com
- Reply-To: ian@vnet.ibm.com
- Organization: IBM UK Labs Ltd, Hursley, England
- Lines: 45
- News-Software: NewsKit 1.5 - LaMail
-
- In <26JUL199218454803@vmsb.is.csupomona.edu>, cvadrtbc@vmsb.is.csupomona.edu (Srikanth Viswanathan) writes:
- >
- >In article <ednstras.711934727@kraken>, ednstras@kraken.itc.gu.edu.au (Michael Strasser) writes...
- >>cvadrtbc@vmsb.is.csupomona.edu (Srikanth Viswanathan) writes:
- >>
- >>>In article <92202.102131BRYAN@wvnvm.wvnet.edu>, Jerry Bryan <BRYAN@wvnvm.wvnet.edu> writes...
- >>>>between the INI files and desktop directories. Remember that INI files
- >>>>are hard to backup with standard facilities such as BACKUP and COPY because
- >>>>they are always open. You have to run the backup out of CONFIG.SYS
- >>>>before they are opened, which in turn means you have to boot to back them
- >>>>up. I hate to boot when it really is not necessary. The other concern
- >>
- >>>You really don't have to. Someone on Fidonet a long time ago, posted
- >>>this very useful tip for backuping INI files:
- >>
- >>>CALL=C:\OS2\XCOPY C:\OS2\*.INI C:\BACKUP\*.INI
- >>
- >>This method is also described in the third redbook (on PM and WPS). The
- >>method given there has
- >>
- >> RUN=C:\OS2\XCOPY C:\OS2\OS*.INI C:\OS2\INSTALL\
- >>
- >>(Can some please explain the difference between CALL and RUN in CONFIG.SYS?).
- >
- >Both of my suggestion and your work, but your suggestion is better because
- >it uses RUN instead of CALL. I think CALL just runs it and waits for that
- >process to end before it continues to the rest of the config.sys (that's
- >why you are able to put a CALL=C:\CMD.EXE and it will load before the WPS).
- >RUN however, runs the programs and then continues, it doesn't wait for the
- >process to end, in other words, it multitasks this process, so you could
- >have like 10 RUN statements in your config.sys and OS/2 will run them all
- >at the same time. At least that's the way I understood this. Can anyone
- >confirm or shoot me down on this?
- >
- >Srikanth
-
- The method using CALL is the best. Srikanth, you are correct in your comparison
- between RUN and CALL. If you use RUN however, you have a risk that the
- files might be already locked when the RUN program is executed. This cannot
- happen with CALL.
-
- Cheers,
- Ian Stirling Internet: ian@vnet.ibm.com
- CICS/ESA Systems Facilities Bitnet: ian at vnet
- IBM UK Labs Ltd, Hursley, England IBMIPnet: ian@stirling.hursley.ibm.com
-