dave@cs.arizona.edu (Dave Schaumann) (05/03/90)
Does anyone know of a program that can tell why a disk icon is present on the WB screen? I have never heard of such a thing, but it would be mighty useful for those pesky icons that won't go away, but have no discernable reason for staying. I suspect there is no such thing (seeing as I have never heard of such a thing) In this case, I may write it myself over the summer. As far as I know, these are the reasons why a disk icon is present on the WB screen: o The disk is physically in a drive o There is an 'assign' to some directory on the disk o A window on the disk is opened. o A running program has a lock on a file/directory on the disk Ideally, the program (as run from a shell) would function like: WB1.3> why_viz disk2: The program "foobar" has a lock on disk2:foo/bar If you know of a program to do this, or know of some reason an icon is present I missed, or have any useful comments, please email. Be warned, though, this account goes away 5/11/90... Dave Schaumann | "Strange women lying in ponds distributing swords dave@cs.arizona.edu | is no basis for a system of government!" FidoNet: 1/300/4 | -M. Python
UH2@psuvm.psu.edu (Lee Sailer) (05/04/90)
In article <284@caslon.cs.arizona.edu>, dave@cs.arizona.edu (Dave Schaumann) says: > >In this case, I may write it myself over the summer. As far as I know, these >are the reasons why a disk icon is present on the WB screen: > > o The disk is physically in a drive > o There is an 'assign' to some directory on the disk > o A window on the disk is opened. > o A running program has a lock on a file/directory on the disk > This is really just a instance of "A running program...", but another reason is that from a CLI you have CD'd to a directory on the disk. I guess the CLI has a lock on the directory, but I thought this was worth mentioning since it is easy to forget that the CLI is a "running program". lee