Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Installing and Removing Locked Files

IP.com Disclosure Number: IPCOM000108333D
Original Publication Date: 1992-May-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 1 page(s) / 20K

Publishing Venue

IBM

Related People

Dobbelstein, S: AUTHOR [+3]

Abstract

A solution to the problem of copying over or deleting files that are locked by processes running with the IBM OS/2* Operating System is to install a device driver into CONFIG.SYS that will do the copying, moving and/or deleting on the next reboot. The device driver is installed early enough in CONFIG.SYS so that it can copy over, move or delete the files before they are locked by OS/2. A clean-up program is also installed in CONFIG.SYS to take care of directories that cannot be removed by the device driver and to remove the device driver and itself from CONFIG.SYS. * Trademark of IBM Corp.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 100% of the total text.

Installing and Removing Locked Files

       A solution to the problem of copying over or deleting
files that are locked by processes running with the IBM OS/2*
Operating System is to install a device driver into CONFIG.SYS that
will do the copying, moving and/or deleting on the next reboot.  The
device driver is installed early enough in CONFIG.SYS so that it can
copy over, move or delete the files before they are locked by OS/2.
A clean-up program is also installed in CONFIG.SYS to take care of
directories that cannot be removed by the device driver and to remove
the device driver and itself from CONFIG.SYS.
*  Trademark of IBM Corp.