ruben@ut-ngp.UUCP (Ruben Ramirez-Mitchell) (04/16/85)
I have some problems with VFILE.CMD (version 1.2). When I run it under
MPM-816 (in a Compupro system with a Q540 Hard disk) it hangs the system
when I try to log into C5:, B6: or B10: (from any drive or user area).
I also hangs when the program is invoked from C5, B6 or B10. I can abort
from another console but the system starts getting flakey after this.
The previous version (1.1) works very well. Has anybody noticed this type of
problem with VFILE (1.2)?
I had been using version 1.2 for some time in my home system and never noticed
anything amiss, but I had never tried to access these drives and areas with it.
Most of the time I use other disk programs and these user areas have very
little activity.
The problem showed up when checking a new Compupro (MPM-816) system I
installed in my lab. By pure chance I tried VFILE in C5 and the system hanged.
Since it was consistent I checked all the other drives and user areas and
found B6 and B10. Assuming the problem was in the system we started checking
the hardware. Couldn't find anything wrong. Finally decided to try my home
system hard disk with the new mainframe and the problem showed up.
Then I checked my home system with VFILE and same thing happened.
Ruben Mitchell
ruben@ut-ngp.arpa
--
Ruben Mitchell
Cell Research Institute
University of Texas
Austin, Texas 78712
ruben@ut-ngp.ARPA