Browse Prior Art Database

Method for Implementing Directory-Limit Functions in Windows File Manager

IP.com Disclosure Number: IPCOM000115853D
Original Publication Date: 1995-Jul-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 59K

Publishing Venue

IBM

Related People

Spelce, DC: AUTHOR

Abstract

The invention provides a method for implementing directory limit functions in the Windows* 3.1 File Manager, giving Windows clients on an OS/2** LAN Server network an integrated method to check directory-limit information for drives redirected to HPFS386 volumes where directory limits have been enabled.

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

Method for Implementing Directory-Limit Functions in Windows File
Manager

      The invention provides a method for implementing directory
limit functions in the Windows* 3.1 File Manager, giving Windows
clients on an OS/2** LAN Server network an integrated method to check
directory-limit information for drives redirected to HPFS386 volumes
where directory limits have been enabled.

      To accomplish this, the directory limit interface is developed
as a File Manager Extension, which is a Dynamic-Link Library (DLL)
designed to hook into the File Manager each time File Manager is
started by the user.  Windows 3.1 Application Programming Interface
(API) is used to create a new menu item within the File Manager, and
the OS/2 LAN Server 4.0 APIs are used to retrieve directory limit
information about the currently-selected drive.  Using this design,
the interface is dependent only on the Windows network driver
(DLSNET.DRV for DOS LAN Services).

      The program appends a menu item, named Directory Limit, to the
Disk popup menu, using the FMExtensionProc Windows API and uses the
FM_GETDRIVEINFO message to obtain drive information from the active
File Manager window.  The File Manager returns information about the
currently-selected drive in an FMS_GETDRIVEINFO structure, which
contains one field pointing to the UNC name of the redirected drive.
This information is used to make the appropriate directory-limit API
calls (NetDASDGetInfo, NetDASDCheck) to retrieve i...