Ullrich_Fischer@mindlink.UUCP (Ullrich Fischer) (02/13/91)
This is an update to my previous posting regarding a problem on a netware 386 drive in getting NCD to show the entire directory tree. We have release 3.1a. There are 4 physical volumes on the system. 2 40 Mb Conner drives mirrored as SYS:, one CDC WREN VI drive (VOL31:) and another CDC WREN VI drive (VOL32:). All the drives are on a single SCSI cable driven by a Novell DCB board. VOL32: has 8 subdirectories under the root directory. Each of these subdirectories has a number of subdirectories under it. Norton Change Directory NCD 4.5 and NCD 5.0 will show only the subdirectory tree beginning with the first of these subdirectories. The other subdirectories directly under the root do not appear. This problem only happens on this one volume. The name of the subdirectory which does appear is BACKUPS. Other volumes on our internet have just as complex directory structures. Since my last post, I have called NORTON. They were interested but had not heard of a similar problem. I also tried Norton's FS /S (File size listing with included subdirectories) on the volume and found the same problem. Only files under the BACKUPS subdirectory subtree were shown. The DOS 4.01 TREE command had the same problem. NDIR and DIR and MSDOS 3.3 TREE worked fine and showed all the directories on the drive. I have no problem accessing any of the files on the volume. NCOPY /S only copies the BACKUPS subtree to another volume: i.e. MAP W:=VOL32: MAP V:=VOL31: V: cd \ ncopy w:*.* /s results in only w:\backups and its subtree getting copied to V: The problem seemed to go away temporarily when I added yet another subdirectory tree to W: drive (). It re-appeared when I removed that subtree. I don't believe this is a problem with NORTON's NCD etc. Does anyone know what the NCD, TREE 4.01, FS, and NCOPY do differently than NDIR, DIR, MSDOS 3.3 TREE when it comes to examining the directory tree on a network volume? We're using NET3.COM 3.01. I haven't tried using release D of NET3 yet. I've tried renaming the BACKUPS directory to BA using NCD, then re-scanning the volume but the problem did not go away.