Novell Cool Solutions

ShellOwnedFiles



By:

May 10, 2004 7:29 pm

Reads:3,128

Comments:0

Score:Unrated

Print/PDF

License:
Free

Download shell_owned_files

Free, subject to same Novell Cool Tools disclaimer at https://www.novell.com/coolsolutions/tools/disclaimer.html.

Important Note: This work is based extensively on excellent work by Michael Dunn and Matthijs Hollemans published at The Code Project http://www.codeproject.com/shell/.

As long as I can remember, NetWare has possessed great capabilities for preventing users from running amok on its file systems by easily allowing admins to restrict volume space by user. But from the user’s perspective, the only way we have been able to find to allow them to effectively view and/or manage the files they own is through NDIR. Nowadays, this is a stretch for most. So this .dll implements the Windows Explorer COM extensions required to support an additional context menu entry and (Windows 2K+ only) column displays wired to eDirectory. Using it, users can easily view the owners of files in NetWare folders and ‘filter’ a Windows Explorer search result to include only files they own.

To install, place the .dll in a convenient spot and register it with regsvr32 [qualifiers] [path]ShellOwnedFiles.dll. Tested on NetWare 5 and 6/Client 4.8 on Windows 2000 only. Beware of performance implications for large/and or remote folders. There is no graceful way to stop the filtering of large search results. Code is smart enough to ignore non NetWare folders. Language is not configurable; currently supports English only (sorry).

Use instructions are included in the enclosed ReadMe.html.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...


Categories: Uncategorized

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS